On zo, 2014-11-02 at 15:59 +0000, Ben Hutchings wrote: > 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.
Yes, I understand this behaviour, however: - why does modprobe radeon without any option (nor at the shell command line, nor somewhere in /etc/modprobe.d) complain about invalid argument, and that UMS is not supported? - why does my system just give me a blank screen if I don't explicitly start it with the modeset=0, while it was working fine for years with KMS? This is the main problem for me. -- Frederik Himpe <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
