Skip to contentSkip to conversation

vesa fb in -bk gives too many console lines

DISCUSSION Greg KH 2 participants 2 messages Apr 17, 2003

lore
Share & tools
lore

Greg KH

author
#0 lore raw

Hi,

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?

Here's the relevant portions of the boot messages:

vesafb: framebuffer at 0xd5000000, mapped to 0xf080d000, size 4096k
vesafb: mode is 1024x768x8, linelength=1024, pages=4
vesafb: protected mode interface info at c000:0310
vesafb: scrolling: redraw
========================================
Display Information (EDID)
========================================
EDID Version 1.3
Manufacturer: VSC Model: 8f00 Serial#: 16843009
Year: 2001 Week 20
Display Characteristics:
Analog Display Input: Input Voltage - 0.700V/0.300V Configurable signal level
Sync: Separate Composite Serration on
Max H-size in cm: 37
Max V-size in cm: 27
Gamma: 2.86
DPMS: Active yes, Suspend yes, Standby yes
RGB Color Display
Chromaticity: RedX: 0.638 RedY: 0.325
GreenX: 0.276 GreenY: 0.596
BlueX: 0.143 BlueY: 0.066
WhiteX: 0.283 WhiteY: 0.297
First DETAILED Timing is preferred
Display is GTF capable
Standard Timings

      1280x1024@85Hz
      1280x1024@60Hz
      1152x864@75Hz
      1024x768@85Hz
      800x600@85Hz
      640x480@85Hz
      1600x1200@60Hz
      1600x1200@75Hz
   Supported VESA Modes
      720x400@70Hz
      720x400@88Hz
      640x480@60Hz
      640x480@67Hz
      640x480@72Hz
      640x480@75Hz
      800x600@56Hz
      800x600@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@87Hz (interlaced)
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      1152x870@75Hz
      Manufacturer's mask: 0

Detailed Monitor Information
157 MHz 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync

Serial No : 320012039515
HorizSync : 30-95 KHz
VertRefresh : 50-180 Hz
Max Pixelclock: 200 MHz
Monitor Name : A90-2
========================================
fb0: VESA VGA frame buffer device
Console: switching to colour frame buffer device 160x64

thanks,

greg k-h

p.s. nice boot messages, I know now that the usb code will stop taking the heat for abusing the kernel log :)

#1 lore raw
Quoted 9 lines · Greg KH

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.

Quoted 1 line

Here's the relevant portions of the boot messages:

<snip zillions of EDID junk>

Quoted 2 lines

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