|
http://linmodems.technion.ac.il/archive-fourth/msg00498.html [Date Prev][Date Next][Date Index] module autoloading under 2.6
RE: The autoloading is different on kernel 2.6 (at least on Debian). 1) you should create your module configuration files in /etc/modprobe.d/ 2) update them using 'update-modules' 3) the last command groups all the module configuration options in one file placed at /lib/modules/modprobe.conf (the /etc/modprobe.conf file includes automatically /lib/modules/modprobe.conf) 4) now, all the options modules are read from that file ------------------------- THANK YOU. Luca, That indeed solves the autoloading problem!!! I was completlely oblivious to this modules management transition in 2.4 -> 2.6, But now have found the documentation in # man modprobe.conf With respect to the minor issue of /dev/modem. Without the devfs: # ls -l /dev/modem lrwxrwxrwx 1 root root 11 Jan 26 23:30 /dev/modem -> /dev/ttyLT0 When the devfs (obsolete under 2.6.n) is used in 2.4.n kernels driver ports are co-created with loading of the modules, and eliminated with removal of modules. This economizes greatly on Port Name Space. In particular. # modprobe lt_serial 1) loads the drivers 2) creates /dev/tts/LT0 3) and a symbolic link /dev/ttySLT0 --> /dev/tts/LT0 which serves in the wvdialconf trial and if the devfsd service is installed and a /etc/devfs/conf.d/ltmodem.conf specification file 4) /dev/modem --> /dev/tts/LT0 Conversely, RMMODing the modem drives also delets /dev/tts/LT0 and its symbolic links. MarvS Luca Capello wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hello, > >on 02/28/04 19:23, Marvin Stodolsky wrote: > > >>There is still in /etc/modules.conf >>alias char-major-62 lt_serial >>alias /dev/tts/LT0 lt_serial >>alias /dev/modem lt_serial >>----------- >>which sufficed for autoloading drivers under 2.4.n kernels, BUT >> >> >about autoloading on kernel 2.6, maybe you forgot my post about >'slmodem' on kernel 2.6: >http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:12857:200401:hfbalgjggngcldpeibmn > >The autoloading is different on kernel 2.6 (at least on Debian). >1) you should create your module configuration files in /etc/modprobe.d/ >2) update them using 'update-modules' >3) the last command groups all the module configuration options in one >file placed at /lib/modules/modprobe.conf (the /etc/modprobe.conf file >includes automatically /lib/modules/modprobe.conf) >4) now, all the options modules are read from that file > >This is the same on kernel 2.4, but the module configuration files are >in /etc/modutils/ and the whole file is /etc/modules.conf, as you can >see from a 'less /etc/modules.conf': >===== >### This file is automatically generated by update-modules" ># ># Please do not edit this file directly. If you want to change or add ># anything please take a look at the files in /etc/modutils and read ># the manpage for update-modules. ># >### update-modules: start processing /etc/modutils/0keep ># DO NOT MODIFY THIS FILE! ># This file is not marked as conffile to make sure if you upgrade modutils ># it will be restored in case some modifications have been made. ># ># The keep command is necessary to prevent insmod and friends from ignoring ># the builtin defaults of a path-statement is encountered. Until all other ># packages use the new `add path'-statement this keep-statement is essential ># to keep your system working >===== > >or, from /lib/modules/modprobe.conf: >===== ># This file is automatically generated by update-modules, please do not ># edit it directly. ># If you want to change or add anything here please read /etc/modprobe.conf, ># the files in /etc/modprobe.d/ and the manpage for update-modules(8). >===== > >So, you should fix your problem with /etc/modprobe.d/ files before trying the >module autoloading on kernel 2.6. > > > >># wvdial >>--> WvDial: Internet dialer version 1.54 >>--> Cannot open /dev/modem: No such device >>--> Cannot open /dev/modem: No such device >>--> Cannot open /dev/modem: No such device >> >>OR with the Debian dialer utitlity pon >># pon >>stodolsklap:~# lsmod >>Module Size Used by >>ppp_generic 24784 0 >>slhc 7360 1 ppp_generic >>rtc 11800 0 >>----------- >>the modem drivers do NOT autoload. >> >> ><cut> > > >>Through which this message is sent. >>So only the module autoloading has to be fixed >> >> > >On my Debian and 2.6.3 (sorry for all the loaded modules, I can't unload them, >as I'm using them...): > >- - cat /etc/modprobe.d/slmodem >alias /dev/slamr0 slamr >alias /dev/modem slamr > >- - cat /lib/modules/modprobe.conf | grep sl >alias /dev/sound sound-slot-1 >alias tty-ldisc-1 slip >alias slip0 slip >alias slip1 slip >alias snd-slot-0 snd-card-0 >alias sound-slot-0 snd-slot-0 >alias snd-slot-1 snd-card-1 >alias sound-slot-1 snd-slot-1 >### update-modules: start processing slmodem ### >alias /dev/slamr0 slamr >alias /dev/modem slamr >### update-modules: end processing slmodem ### > >- - lsmod >Module Size Used by >ndiswrapper 55816 0 >snd_seq_oss 34816 0 ><cut all the other ALSA modules> >soundcore 10336 2 snd >thermal 18960 0 >fan 5516 0 >button 8216 0 >battery 12300 0 >processor 25904 1 thermal >ac 6540 0 >asus_acpi 10776 0 >uhci_hcd 32524 0 >ehci_hcd 37508 0 >joydev 10432 0 >evdev 9600 1 >radeon 117420 0 >ati_agp 8588 0 >agpgart 31528 1 ati_agp > >- - ls -l /dev/slamr0 >crw------- 1 root root 212, 0 Jan 1 1970 /dev/slamr0 > >- - lsmod >Module Size Used by >slamr 316548 0 >ndiswrapper 55816 0 >snd_seq_oss 34816 0 ><cut all the other ALSA modules> >soundcore 10336 2 snd >thermal 18960 0 >fan 5516 0 >button 8216 0 >battery 12300 0 >processor 25904 1 thermal >ac 6540 0 >asus_acpi 10776 0 >uhci_hcd 32524 0 >ehci_hcd 37508 0 >joydev 10432 0 >evdev 9600 1 >radeon 117420 0 >ati_agp 8588 0 >agpgart 31528 1 ati_agp > >- - rmmod slamr > >- - ls -l /dev/modem >ls: /dev/modem: No such file or directory > >IMHO the last error is due to the 'devfs', I've no other explanations about it >(but ATM I don't know how to correct it). Maybe you can create the symlink >/dev/modem to the correct character file (/dev/tts/LT0 ?) and then it may be >work. Anyway, IMHO if you try to start 'wvdial' calling '/dev/tts/LTO' it should >automatically load 'lt_serial'. I've a 'slmodem', so I can't... Anyway, if I >call 'slmodemd /dev/slamr0' it automatically load 'slamr', so it should be as >above even for the 'wvdial' (not in my case, as I need to start 'slmodemd' >before). Could you try to confirm it, please? > >I hope having helped you ;-) > >Thx, bye, >Gismo / Luca >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.4 (GNU/Linux) >Comment: Using GnuPG with Debian - http://enigmail.mozdev.org > >iD8DBQFAQQ8nVAp7Xm10JmkRArDSAJ0WqV8f2j4Wd66DGnXJEUc/ZQ1YvwCffWdd >DRhet+7AoO4BoBLKTrIqndU= >=jl7n >-----END PGP SIGNATURE----- > > >
|
