|
Bugzilla – Full Text Bug Listing |
| Summary: | X server crashes machine | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Reinhard Max <max> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
X server configuration
X serve log file Log file after adding the "dri" module. |
||
|
Description
Reinhard Max
2005-10-05 10:20:43 UTC
Could you attach config and logfile of Xserver? Thanks. Created attachment 51474 [details]
X server configuration
BTW, the crash also happens when I remove the config file and start sax2.
Created attachment 51475 [details]
X serve log file
Try adding 'Load "dri"' to Modules section. For other via users this prevented the Xserver from crashing. BTW, adding this should be default for SaX2. Loading "dri" didn't change the behaviour of the X server, but it caused two additional kernel modules to be loaded, "via", and "drm". They added the following lines to /var/log/messages: [drm] Initialized drm 1.0.0 20040925 via: module not supported by Novell, setting U taint flag. ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [drm] Initialized via 2.6.3 20050523 on minor 0: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: reserved bits set in mode 0x1f000a17. Fixed. agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode I will also attach the new server log file. Created attachment 51488 [details]
Log file after adding the "dri" module.
Hmm. Loading the "drm" and "via" kernel module is absolutely correct, when you enable DRI (which was necessary for others to prevent Xserver from crashing during console switch). Are you sure you want a 1600x1200 resolution (94.0 kHz, 75.0 Hz)? I'm afraid that for now you need to use the fbdev driver. :-( --> sax2 -r -m 0=fbdev Is there anything wrong with that resolution/frequencies combination? I've been using it for many years with different graphics cards on this 21" monitor without problems. And as said before, I haven't changed the configuration since 9.3, where it worked just fine, so something got broken either in the kernel modules or X drivers for 10.0. My current workaround is to use the vesa driver (sax2-vesa), but it gives me only low refresh rates. Does the fbdev driver have any advantages over vesa? IIRC it has the disadvantage that the X resolution is fixed to the resolution of the frame buffer console. Ok. The configuration for 1600x1200 simply looked different in the config file. I don't think it's a kernel problem. One option would be to use the via X driver module of 9.3. You're right, for a 1600x1200 resolution you probably need the vesa driver, since the gfx card might not support this resolution via framebuffer. Yes, it works when I use the via module from 9.3. Hmm ... Another try would be the new Xserver + modules from STABLE. This time you need to install the complete package (xorg-x11-server). I set this to LATER for now. Needs to be investigated again with 10.1 Preview. reopen for retest ... Could you try again with 10.1 Beta or X.Org 6.9? Thanks. I am already running that machine successfully with X.Org 6.9 :) Great! Then let's close this as FIXED now. :-) |