![]() | |||||||||||||
Messages in this thread |
On Wed, Apr 16, 2003 at 11:25:46PM -0700, Greg KH wrote: > In the latest -bk tree, using the vesa fb driver, I get a window that is > much too big for my screen. I'm using "vga=0x0305" as a command line > option, which I've been using for years on this box, and when the fb > code kicks in, it creates a screen that has more lines than are > displayed on the monitor (text lines that is). I can see 48 lines, but > it's acting like there are more that that present. > > Is this just an operator error, in that I need to provide a different > command line option now for the size of the console screen? I've seen this happen too, and a box that worked fine with vga=791 before now gets me a screen full of garbage. I think something got broken somewhere along the lines. > Here's the relevant portions of the boot messages: <snip zillions of EDID junk> > p.s. nice boot messages, I know now that the usb code will stop taking > the heat for abusing the kernel log :) That is in the 'taking the piss' category for voluminous output. I hope its planned to be quitened down somewhat when we get closer to 2.6. AIUI, there are userspace tools that dump all that info anyway for interested parties. Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:34 [from the cache] ©2003-2008 | |||||||||||||