Skip to contentSkip to conversation

Checking module parameters

DISCUSSION David Wagner 5 participants 5 messages Jan 17, 2009 – Jan 18, 2009

lore
Share & tools
lore
#0 lore raw

Is there a way to tell what options have been applied to a currently loaded kernel module?

I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created a file /etc/modprobe.d/local containing:
options libata force=1.5Gbps
However my SATA drive gets loaded at 3Gbps. I'm trying to figure out how to debug this so that I can tell whether the option got correctly applied to the libata module, and if not, how to force the SATA link to 1.5Gbps. Any suggestions or ideas?

(I can't set libata.force=1.5Gbps as a kernel argument because on my Fedora kernel, libata is loaded as a module rather than built into the kernel. I can't run "modprobe libata force=1.5Gbps" by hand because I've got SATA drives, so the libata module is automatically loaded before I get shell access.)

#1 lore raw
Quoted 2 lines · David Wagner

Is there a way to tell what options have been applied to a currently loaded kernel module?

/sys/module/[module name]/parameters/ (if i remember correctly)

Quoted 8 lines

I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created a file /etc/modprobe.d/local containing:
options libata force=1.5Gbps
However my SATA drive gets loaded at 3Gbps. I'm trying to figure out how to debug this so that I can tell whether the option got correctly applied to the libata module, and if not, how to force the SATA link to 1.5Gbps. Any suggestions or ideas?

Quoted 5 lines

(I can't set libata.force=1.5Gbps as a kernel argument because on my Fedora kernel, libata is loaded as a module rather than built into the kernel. I can't run "modprobe libata force=1.5Gbps" by hand because I've got SATA drives, so the libata module is automatically loaded before I get shell access.)

This may not work if libata module is loaded from initrd.

#2 lore raw
In reply to David Wagner
Quoted 11 lines · David Wagner

Is there a way to tell what options have been applied to a currently loaded kernel module?

I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created a file /etc/modprobe.d/local containing:
options libata force=1.5Gbps
However my SATA drive gets loaded at 3Gbps. I'm trying to figure out how to debug this so that I can tell whether the option got correctly applied to the libata module, and if not, how to force the SATA link to 1.5Gbps. Any suggestions or ideas?

Quoted 5 lines

(I can't set libata.force=1.5Gbps as a kernel argument because on my Fedora kernel, libata is loaded as a module rather than built into the kernel. I can't run "modprobe libata force=1.5Gbps" by hand because I've got SATA drives, so the libata module is automatically loaded before I get shell access.)

Rebuilding the initrd with that option set should cause the initrd to pass the option into the libata module when the initrd script loads it. Unfortunately the current Fedora mkinitrd is broken such that this doesn't work. I'm rather disappointed by the lack of response to this bug as it seems like it should be easily resolved and causes serious problems with debugging certain issues, as you've found. Anyone know who needs to be hit with a clue-by-four to get this fixed?

https://bugzilla.redhat.com/show_bug.cgi?id=457870

#3 lore raw
In reply to David Wagner
Quoted 3 lines · David Wagner <daw <at> cs.berkeley.edu> writes:

(I can't set libata.force=1.5Gbps as a kernel argument because on my Fedora kernel, libata is loaded as a module rather than built into the kernel.

That used to be true until module-init-tools-3.5 , i.e. you can in Fedora 10 and rawhide.

Cheers

#4 lore raw
In reply to David Wagner
Quoted 5 lines

(I can't set libata.force=1.5Gbps as a kernel argument because on my Fedora kernel, libata is loaded as a module rather than built into the kernel. I can't run "modprobe libata force=1.5Gbps" by hand because I've got SATA drives, so the libata module is automatically loaded before I get shell access.)

Best to ask on the Fedora lists for fedora specific config help. If I remember rightly you need to update the module options in the initrd...

Alan