Am 24.07.2014 18:39, schrieb Gary Dale: > On 24/07/14 08:56 AM, Michael Biebl wrote: >> Am 24.07.2014 12:42, schrieb Gary Dale: >>> After the latest round of upgrades in Jessie, I rebooted. That's when >>> the problems started. I'm having problems getting the 3.14 kernel to >>> boot, so I'm booting from 3.13. However, that's not the big issue. >>> >>> The really annoying problem is that I have to boot to the command >>> prompt, insmod radeon, then exit back to a regular boot in order to get >>> the radeon module loaded. >>> >>> Radeon is listed in /etc/modules.conf - has been for years. However the >> Can you post your modules.conf, please >> >> > This is basically how it's looked for a long time. Up until my recent > reboot, the kernel module seems to have been loading properly. Now I > have to insert it manually when rebooting. > > > # /etc/modules: kernel modules to load at boot time. > # > # This file contains the names of kernel modules that should be loaded > # at boot time, one per line. Lines beginning with "#" are ignored. > # Parameters can be specified after the module name. > > firewire-sbp2 > loop > radeon > # usblp That looks fine. What's the status of systemctl status systemd-modules-load.service After a reboot, is the radeon kernel module not loaded at all? Or is it loaded but not functional? What about the firewire-sbp2 and loop module? Fwiw, I'm suprised you need to manually load the radeon kernel module. It should be auto-loaded afair. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature