On Sat, 2002-12-28 at 14:26, Michael Heironimus wrote:
> Have you tried booting with vga=ask and scanning for available modes? I
> remember doing that when I was originally playing with large consoles.
> The kernel documentation on mode numbers was a little out of date when I
> was using it, I don
On Sat, Dec 28, 2002 at 12:29:11PM +0900, Elijah wrote:
> I've tried vga=0x317 and it gave the same error :( vga=788 worked
> though, but in 800x600 resolution. What I'm looking forward to is the
> old 1040x768 resolution that I got used to with my old card... )
>
> Update:
> I've also tried out
I've tried vga=0x317 and it gave the same error :( vga=788 worked
though, but in 800x600 resolution. What I'm looking forward to is the
old 1040x768 resolution that I got used to with my old card... )
Update:
I've also tried out
vga=773 (passed an undefined mode )
vga=790 (passed an undefine
Elijah, 2002-Dec-27 22:42 +0900:
>
> I've already read what's on /usr/src/linux/Documentation/vesafb.txt
> (docs from slack) ,
> some info there is just too complicated for me, I've tried out using
> vga=0x301 , vga=scan, vga=ask etc. etc. and none could give me a better
> resolution.
> Passing t
4 matches
Mail list logo
