| Summary: | some kernel oopses apparently caused by the radeon driver | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Elmar Stellnberger <estellnb> | ||||||||||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
| Severity: | normal | ||||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 7.5 (2009.10) | ||||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||||
| OS: | Linux (All) | ||||||||||||||
| Whiteboard: | |||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Elmar Stellnberger
2011-01-10 07:27:34 UTC
Created attachment 41841 [details] [review] warn of hang #3 Created attachment 41842 [details]
/var/log/messages of hang #3
remove the vesa fb driver or vga= from your grub config. Vesa fb does not appear on the kernel command line; lsmod | grep -i fb or vesa does not return anything either (as booted with the radeonhd driver). Why should vga=0x375 disturb? I want to have it for a higher resolution in text mode. - and the initial graphics mode setup has worked well. (In reply to comment #4) > Vesa fb does not appear on the kernel command line; lsmod | grep -i fb or vesa > does not return anything either (as booted with the radeonhd driver). > Why should vga=0x375 disturb? I want to have it for a higher resolution in > text mode. - and the initial graphics mode setup has worked well. the drm fb driver will automatically take care of the higher res console. vga= is not compatible with the drm fb. Yes; and how to make sure that vesa fb does not get loaded (and how to check for it)? Well; the oopses didn`t seem to go without vga=0x375, -> see hang #4. Created attachment 41855 [details]
warn of hang #4
Created attachment 41856 [details]
Xorg.0.log of hang #4
Created attachment 41857 [details]
/var/log/messages of hang #4
This time the hang was more complete than usual. The mouse did not move at all any more (no more reaction on input any more) instead of just moving in slow hulking steps. Please do also keep the vga=0xNNN option supported! I really don`t want to do without since I do or often have to work without X - and working with a 80x25 text console is really no pleasure. - If X is broken, please don`t also take me the text console! Your system looks pretty screwed up. It looks like you have fglrx loaded in addition to vga/vesa console and the kms driver. The vga= option is not valid with any native framebuffer drivers it's a vesa option. When kms is active, it controls the hardware directly rather than the vga console driver. If you want to specify a mode, use something like: video=1280x1024-24@60, etc. Closing as this is most certainly a user configure issue, please properly remove flgrx, don't build ati framebuffer and don't use vga option, instead use videomode option thought by default kms should pickup an high resolution. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.