[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[SOLVED] Re: inserting kernel modules on startup



On 24/07/14 01:21 PM, Gary Dale wrote:
On 24/07/14 12:57 PM, Michael Biebl wrote:
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.

root@transponder:/home/garydale# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since Thu 2014-07-24 06:17:41 EDT; 6h ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Main PID: 342 (code=exited, status=0/SUCCESS)

Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'lp' Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'ppdev' Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'parport_pc' Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'fuse' Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'firewire_sbp2' Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'loop'
Jul 24 06:17:41 transponder systemd[1]: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable


The radeon kernel module is not being loaded. insmod readeon works.

I added the radeon line back in 2012 when the drm was new. Having it in /etc/modules was never a problem. I was wondering if it might have been blacklisted so I checked /etc/modprobe.d and it doesn't seem to be. However I note the fglrx driver is listed. It blacklists radeon. I haven't used the fglrx driver in some time because it's a real pain in the butt when running Jessie.

root@transponder:/home/garydale# ls -l /etc/modprobe.d/
total 40
-rw-r--r-- 1 root root 1222 Aug 15  2013 alsa-base.conf.dpkg-bak
-rw-r--r-- 1 root root 157 Feb 3 2012 blacklist-cups-usblp.conf.dpkg-bak
-rw-r--r-- 1 root root  127 Oct  5  2012 dkms.conf
-rw-r--r-- 1 root root  410 Jun 28 07:28 fbdev-blacklist.conf
-rw-r--r-- 1 root root   65 Sep 25  2010 fglrx-driver.conf
-rw-r--r-- 1 root root   23 May 14  2010 i915-kms.conf
-rw-r--r-- 1 root root   16 Nov 15  2011 libpisock9.conf
-rw-r--r-- 1 root root   51 May 10 19:22 modesetting.conf
-rw-r--r-- 1 root root  119 Sep  1  2013 oss-compat.conf
-rw-r--r-- 1 root root   26 Jul 15  2010 radeon-kms.conf

OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the radeon kernel module to load. I have no idea why this just started happening. I would have thought that a blacklist in a module that wasn't being used would be ignored, as seems to have been the case up to very recently.


Reply to: