Bug 436172 - vesa: not defaulting to 800x600
vesa: not defaulting to 800x600
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vesa (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
:
Depends On:
Blocks: LTSPHARDWARE
  Show dependency treegraph
 
Reported: 2008-03-05 14:12 EST by Warren Togami
Modified: 2008-03-12 16:56 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-12 16:56:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Xorg-vesa-huge-resolution.log (50.58 KB, text/plain)
2008-03-05 14:12 EST, Warren Togami
no flags Details

  None (edit)
Description Warren Togami 2008-03-05 14:12:25 EST
<ajax> warren: i think there _is_ a bug there though.  we should be validating
modes by attempting to fit them into the monitor's sync ranges, which in that
log are only big enough for 800x600.

xorg-x11-drv-vesa-1.3.0-13.20071113.fc9.i386
X.org log in attachment is:
- Fedora 8 host
- kvm-62 -std-vga (VESA mode)
- PXE boot kernel-2.6.25-0.90.rc3.git5.fc9.i586
- NFS root boot
- X -query IPADDRESSOFHOST
- Resolution was 1920x1200, way too big.
- Login to GNOME (Fedora 8)
- Logout
- Last X client disconnected, attempted to regenerate, failed.

xrandr in that environment printed:
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 1920 x 1200
default connected
   1920x1200       0.0 
   1600x1200       0.0 
   1680x1050       0.0 
   1400x1050       0.0 
   1280x1024       0.0 
   1440x900        0.0 
   1280x960        0.0 
   1280x800        0.0 
   1152x864        0.0 
   1024x768        0.0 
   800x600         0.0 
   640x480         0.0 
   320x200         0.0
Comment 1 Warren Togami 2008-03-05 14:12:27 EST
Created attachment 296914 [details]
Xorg-vesa-huge-resolution.log
Comment 2 Adam Jackson 2008-03-12 16:56:16 EDT
This should be sorted in xserver 1.4.99.901-4

Note You need to log in before you can comment on or make changes to this bug.