Red Hat Bugzilla – Bug 15664
Beta 5 Xconfigurator and i810 Video.
Last modified: 2014-03-16 22:15:35 EDT
Dell Optiplex GX100/GX110
i810 Chip set.
Xconfigurator 4.3.38-1, 4.3.35-1, and 4.3.40-1.
If 1MB VRAM is selected, 640x480 24bpp works, but nothing in 16bpp works
in any case. Xconfigurator may crash on exit, leaving a
black screen and a mouse. If it does not crash, the mouse will still
remain in the terminal and usually cause erratic highlighting and
return characters when moved (without pressing any buttons).
The mouse is set to generic PS/2 whereas there was a MS Intellimouse
attached. Setting it to Intellimouse does not fix this problem.
At 1MB, choosing 16bpp causes "there is something wrong with the
X configuration" error. If 16bpp ever works in Xconfigurator,
it causes a crash of X with the drm library claimed to be at version
1.1.0 and expected 1.0.x.
This was with a Dell D1025TM Trinitron monitor.
4MB is the proper VRAM setting but Xconfigurator defaulted to 1. At 4MB I
tested the config.
Picking a single or multiple modes in 8 or 24bpp worked fine. If at least
5 modes were
selected 16bpp worked and all modes were workable (switched with ctrl-alt-
arrow). If any less
were selected, Xconfigurator would say that there was something wrong with
In addition, the size of the virtual desktop was 1280x1024 under these
modes. Picking other modes,
the desktop was the size of the screen.
We have the hardware, will check.
This defect is considered MUST-FIX for Winston Gold-release
The "cant start X multiple times" issue is an XFree86 issue, as is the drm. When
it comes to memory, this is what i810 returns to kudzu. Reassigning to Bill.
Please use RC 1 and an updated d Xconfigurator 4.3.45 from
http://people.redhat.com/teg/xc/ - this fixes the problem here.
Video is working but, can not be set to 24 bit 1600x1200 it will automatically
defaults back to 1280x1024.
Try specifying 32 MB...
OK - verified. Just tell it "32 MB" and it will work. It uses a bit more memory
since 3D is enabled, which is why this resolution is shown but doesn't work.
I should have added that to the bug we did try 32 meg and it failed.
Hmm... I'll look into that. Right now, that machine is busy installing.
Reopening so I don't forget it....
BTW: Tried increasing the number in the file even more, manually?
Hmmm... it segfaults in 24bpp 1600x1200 now.
*** This bug has been marked as a duplicate of 16296 ***