Control: reassign -1 kmod Control: retitle -1 modprobe(8) does not document precedence of module parameter settings On Sun, 2014-11-02 at 11:51 +0100, Frederik Himpe wrote: > Package: src:linux > Version: 3.16.5-1 > Severity: normal > > Since a few weeks, I experience the problem that my screen stays blank as soon > as KMS is supposed to be activated. I have to boot with radeon.modeset=0 > parameter to prevent this problem from happening. > > I'm using this graphics card: > 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] > > When I manually try to modprobe radeon after booting with radeon.modeset=0, I > get this error: > modprobe: ERROR: could not insert 'radeon': Invalid argument > [ 132.951583] [drm:radeon_init] *ERROR* No UMS support in radeon module! > > This error shows up even with a file /etc/modprobe.d/radeon.conf with this > contents: > options radeon modeset=1 > > However, when I run > # modprobe radeon modeset=1 > it works successfully: [...] If you specify a module parameter on the kernel command line, that overrides the configuration files (but not the modprobe command line). Anyway, this is not controlled by the kernel but by modprobe. The behaviour of modprobe doesn't seem to be properly documented so I'm reassigning this accordingly. Ben. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson
Attachment:
signature.asc
Description: This is a digitally signed message part