| Anonymous | Login | Signup for a new account | 11-10-2008 11:18 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001460 | [BusyBox] Kernel Module Support | major | always | 08-12-07 13:23 | 08-16-07 03:40 | ||||
| Reporter | clausmuus | View Status | public | ||||||
| Assigned To | integrator | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 1.4.x | ||||||
| Summary | 0001460: module autoloading dont work | ||||||||
| Description |
I have the same problem as 0001350 I Use version 1.6.0 To locate the problem, I have replaced the command modprobe by a shell script that dump the command line parameters in a file and calls than the modprobe command. By this I can see that the kernel call the modprobe command as follow: modprobe -p -- symbol:MODULNAME_attach where by MODULNAME will be replaced by the name of the module to load. |
||||||||
| Additional Information |
As a quick fix for the problem I will write a shell script that replace the bad arguments against such, that will be understand by the modprobe command and call this with the new arguments by the script. But I hope, that this Problem will be fix in the Busybox itself. |
||||||||
| Attached Files |
 busybox-r19514.symbols-aliases.patch [^] (1,091 bytes) 08-15-07 07:44 |
||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0002655) vda 08-13-07 04:17 |
Please give more info: which kernel version, what do you do to trigger autoload, which commandline is passed to modprobe (give exact example, not "MODULNAME"), what busybox modprobe says with this command line, what "standard" modprobe says (and does - do "strace -o modprobe.log modprobe ..." and attach log file to the bug report). On my system, /bin/modprobe is a link to busybox and everything seems to work. That's why I need more info from you. |
|
(0002661) clausmuus 08-13-07 13:52 |
The kernel version is 2.6.20 To trigger a modul autoload I load a DVB-driver: modprobe dvb-ttpci This load some modules. One of this modules (I don't know witch, but I will try to detect it) is the trigger for the load of the firmware of the dvb card: stv0297 and sp8870 I will post the exact modullist and call of modprobe later, if I have access to my dvb-PC. But it can be, that the first time I can do this, is the next weekend. I use the actual v4l driver, and the firmware will only triggered if a dvb card is detect. In this case the kernel call this: modprobe -p -- symbol:stv0297_attach modprobe -p -- symbol:sp8870_attach You can also trigger a autoload if you build a kernel with the ext2 filesystem as a modul. The mount of such a ext2 filesystem will trigger the autoload of the ext2 modul. But in this case the kernel call this: modprobe -p -- ext2 You can see, the kernel don't do for every kind of modul the same, and I don't know the reason. The script I wrote to fix the problem is this (called modprobe): #!/bin/sh eval /bin/busybox modprobe `echo $@ | sed 's/-- symbol:\(.*\)_attach/\1/'` And the script that only log the modprobe call is this: #!/bin/sh echo $* >> /tmp/modprobe.log /bin/busybox modprobe $* |
|
(0002664) vda 08-14-07 12:59 |
What busybox modprobe says when you do this: modprobe -p -- symbol:stv0297_attach modprobe -p -- symbol:sp8870_attach modprobe -p -- ext2 What is the error message? |
|
(0002665) clausmuus 08-14-07 13:23 |
Excuse me, there was a misspelling in my last posts. The kernel don't use the option -p but the kernel use -q for quite. But the rest of my post are right. The call of: modprobe -q -- ext2 result in nothing, no output, no error. The call of: modprobe -q -- symbol:stv0297_attach results in: modprobe: module symbol:stv0297_attach not found modprobe: failed to load modul symbol:stv0297_attach and the exit status (echo $?) is: 1 The call of: modprobe -q -- stv0297 result in nothing, no output, no error. |
|
(0002666) integrator 08-15-07 07:44 edited on: 08-15-07 07:44 |
I think I've found the problem. busybox modprobe does not scan /lib/modules/`uname -r`/modules.symbols for additionnal aliases. Fix attached. Yann E. MORIN. |
|
(0002667) integrator 08-15-07 07:55 |
clausmuus, Tests here are OK. Can you check wether this also fixes it for you? |
|
(0002668) clausmuus 08-15-07 08:00 |
Hi integrator, thank you for your help. I will check this today when I'm at home (in two hours) and tell you the result of my tests. |
|
(0002669) clausmuus 08-15-07 15:34 |
Ok, now I have check the patch, and it works fine. Thank you very much!! |
|
(0002670) vda 08-16-07 03:40 |
Applied to svn, thanks Yann! |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 08-12-07 13:23 | clausmuus | New Issue | |
| 08-12-07 13:23 | clausmuus | Status | new => assigned |
| 08-12-07 13:23 | clausmuus | Assigned To | => BusyBox |
| 08-12-07 13:24 | clausmuus | Issue Monitored: clausmuus | |
| 08-13-07 04:17 | vda | Note Added: 0002655 | |
| 08-13-07 13:52 | clausmuus | Note Added: 0002661 | |
| 08-14-07 07:52 | integrator | Assigned To | BusyBox => integrator |
| 08-14-07 12:59 | vda | Note Added: 0002664 | |
| 08-14-07 13:23 | clausmuus | Note Added: 0002665 | |
| 08-15-07 07:44 | integrator | Note Added: 0002666 | |
| 08-15-07 07:44 | integrator | File Added: busybox-r19514.symbols-aliases.patch | |
| 08-15-07 07:44 | integrator | Note Edited: 0002666 | |
| 08-15-07 07:55 | integrator | Note Added: 0002667 | |
| 08-15-07 07:55 | integrator | Status | assigned => feedback |
| 08-15-07 08:00 | clausmuus | Note Added: 0002668 | |
| 08-15-07 15:34 | clausmuus | Note Added: 0002669 | |
| 08-16-07 03:40 | vda | Status | feedback => closed |
| 08-16-07 03:40 | vda | Note Added: 0002670 | |
| 08-16-07 03:40 | vda | Resolution | open => fixed |
| Copyright © 2000 - 2006 Mantis Group |  |
