Bug 298131
Summary: | anaconda fails to start VESA mode with Synaptics | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Michal Babej <mbabej> |
Component: | xorg-x11-drv-vesa | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | desktop-bugs, jlaska, smohan, xgl-maint |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-08 16:19:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Michal Babej
2007-09-20 14:09:59 UTC
Greetings Michal, Can you attach logs from the anaconda environment when you experience this issue? /tmp/anaconda.log /tmp/syslog /tmp/X* /tmp/ramfs/* Created attachment 201081 [details] contents of /tmp you can find more related information + backtrace in bug #296721, first three attachments Attaching the X.log file (/tmp/ramfs/X.log). Created attachment 201101 [details]
/tmp/ramfs/X.log
In the future, just attach the log files directly to the bug report. It's
easier to look at things that way. Thanks.
From X.log: (EE) I810(0): No Video BIOS modes for chosen depth. Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x4a0921] 1: /lib64/libc.so.6 [0x2aaaabc2e0a0] 2: /usr/lib64/xorg/modules/drivers/i810_drv.so [0x2aaaadbb89a2] 3: /usr/lib64/xorg/modules/drivers/i810_drv.so [0x2aaaadbbcff8] 4: /usr/bin/Xorg(InitOutput+0x9cc) [0x461c5c] 5: /usr/bin/Xorg(main+0x26f) [0x4323cf] 6: /lib64/libc.so.6(__libc_start_main+0xf4) [0x2aaaabc1b8a4] 7: /usr/bin/Xorg(FontFileCompleteXLFD+0x231) [0x4318a9] Fatal server error: Caught signal 11. Server aborting Reassigning to xorg-x11 component. re comment #4: yep, sorry for that. re comment #5: To make it clear - the X.log & XConfig.test from anaconda are while running Xorg + *i810*, not vesa. I've filed a separate bug on that one (comment #2), this bug is on Xorg + *vesa* + anaconda. After anaconda runs Xorg + i810 and it fails, it tries Xorg + vesa, but apparently the logs from 2nd Xorg run are not there. And as i mentioned when i opened this bug, the *same* config file works in normal installation while it does not work in anaconda stage2 (i got that config file by replacing "i810" with "vesa" in /tmp/XConfig.test). The relevant backtrace is here : https://bugzilla.redhat.com/attachment.cgi?id=199881 so, the issue here is : Xorg + vesa + Synaptics + installed RHEL 5.1 beta = works Xorg + vesa + Synaptics + anaconda = FAIL -> text install only Xorg + vesa + anaconda = works so i can only guess it's something missing / wrong in stage2.img ? Created attachment 202041 [details]
VESA configuration for Xorg in anaconda - created by me from original XConfig.test
Created attachment 202071 [details]
X.log from Xorg + vesa + synaptics + anaconda run (ran by me from vt2 during stage 2)
Ancient bug, closing. The X log here is just X's stdout, not the actual log, so there's really nothing to go on. Please reopen with the complete X log if this is still an issue in current builds of RHEL5. |