If the radeon kernel module isn't loaded, starting Xorg gives me a black screen and I need to do a hard reboot (reset).
I've a HD4650 radeon, so it's r600 driver. This didn't happen with my old Radeon 9250, but I did upgrade X and kernel at the same time (to have r600 support), so not sure if it's related to hardware or to more recent X.
I'm using Debian GNU/Linux with 64-bits kernel and 32-bits userland and :
- xserver-xorg-video-radeon version 1:6.13.0-2
- xserver-xorg version 1:7.5+6
- libgl1-mesa-dri version 7.8.1-1
- kernel 2.6.33-2-amd64
Please attach your xorg log and dmesg output.
Created attachment 35828 [details]
Xorg log with no manual loading of radeon module
Created attachment 35829 [details]
Xorg log with manual loading of radeon module
Created attachment 35830 [details]
dmesg log with no manual loading of radeon module
Created attachment 35831 [details]
dmesg log with manual loading of radeon module
I managed to get the logs using network (since without the radeon module, I have black screen and I get a system freeze whenever I try to switch to text console).
It seems that when I don't load the radeon module manually from /etc/modules, it gets loaded automatically later in the boot process, and Xorg isn't happy with that.
Maybe a timing issue ?
Are you trying to use ums rather than kms? You need to disable kms if you want to use ums. (boot with radeon.modeset=0). If you want to use kms, the drm must be loaded before starting X.
Well, I understand KMS won't work without the radeon module loaded, but it shouldn't crash, it should give an error message. Starting X with KMS enabled but module not loaded should either fail with an error message or fallback to UMS, but it shouldn't freeze the computer.
The weird part is that even if I don't load the module, it gets loaded automatically when X starts, but I still have a crash.
It's not a major bug since manually loading radeon fixes it, but it's still annoying when you have a crash and not clear hint on how to fix it.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/127.