This is a discussion on modules don't load after crash within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> i plugged my printer into my parallel port when the computer was turned on and linux froze, so i ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| i plugged my printer into my parallel port when the computer was turned on and linux froze, so i rebooted and fscked was forced. when i finally got back into the os, neither my sound blaster live module or my nic module get loaded, as they should at boot up. i can load my nic mod with 'modprobe sis900' and setup ifconfig and route and i can then get on the internet, however neither sound nor network modules load at bootup. nic mod is loaded in /etc/rc.d/rc.netdevice and the sound mod is loaded from rc.modules. when i execute /etc/rc.d/rc.netdevice, the nic mod is loaded with no problem, however when i execute /etc/rc.d/rc.modules, i get this: Module dependencies up to date (no new kernel modules found). ../rc.modules: line 682: syntax error: unexpected end of file not sure if that's a problem or not. how would i got about fixing this? i don't even know what runs those scripts to begin with. btw, other scripts in /etc/rc.d do get loaded like rc.local and such i'm running a slackware v9.1 with a kernel 2.4.18. everything was fine until my system crashed and so far, those are the only 2 problems i've found i'd appreciate any help, -- lucas ------------------------- Perl Coder since 2001 shift || die; ------------------------- |
| |||
| On Sun, 19 Sep 2004 11:40:18 GMT, lucas <aolblowz@yahoo.com> wrote: >i plugged my printer into my parallel port when the computer was turned on >and linux froze, so i rebooted and fscked was forced. when i finally got >back into the os, neither my sound blaster live module or my nic module get >loaded, as they should at boot up. i can load my nic mod with 'modprobe >sis900' and setup ifconfig and route and i can then get on the internet, >however neither sound nor network modules load at bootup. >Module dependencies up to date (no new kernel modules found). >./rc.modules: line 682: syntax error: unexpected end of file > >not sure if that's a problem or not. how would i got about fixing this? i >don't even know what runs those scripts to begin with. btw, other scripts >in /etc/rc.d do get loaded like rc.local and such > >i'm running a slackware v9.1 with a kernel 2.4.18. everything was fine >until my system crashed and so far, those are the only 2 problems i've >found > >i'd appreciate any help, Reinstall the modules and/or kernel is always a foolproof way to fix corrupted modules. You are lucky you didn't damage your parallel port circuits. -- I'm not really a human, but I play one on earth. http://zentara.net/japh.html |
| |||
| lucas wrote: > i plugged my printer into my parallel port when the computer was turned on > and linux froze, so i rebooted and fscked was forced. when i finally got > back into the os, neither my sound blaster live module or my nic module get > loaded, as they should at boot up. i can load my nic mod with 'modprobe > sis900' and setup ifconfig and route and i can then get on the internet, > however neither sound nor network modules load at bootup. > > nic mod is loaded in /etc/rc.d/rc.netdevice and the sound mod is loaded from > rc.modules. when i execute /etc/rc.d/rc.netdevice, the nic mod is loaded > with no problem, however when i execute /etc/rc.d/rc.modules, i get this: > > Module dependencies up to date (no new kernel modules found). > ./rc.modules: line 682: syntax error: unexpected end of file > > not sure if that's a problem or not. how would i got about fixing this? i > don't even know what runs those scripts to begin with. btw, other scripts > in /etc/rc.d do get loaded like rc.local and such > > i'm running a slackware v9.1 with a kernel 2.4.18. everything was fine > until my system crashed and so far, those are the only 2 problems i've > found > > i'd appreciate any help, You have to look at line 682 to see what is there. Perhaps cut and paste the pertinent section to here. It sounds like a script somewhere was trying to update your rc.modules, perhaps a udev script, when your system froze. Perhaps it wasn't frozen you weren't patient enough and just shut down, some of the startup scripts can take a while. But, to the point, you will need to fix this file. mAineAc |
| |||
| Thanks for your posts. I took a look at /etc/rc.d/rc.modules and looked at the end of the file, didnt' see anything suspicious. I then scrolled to see if i could see anything wrong. I finally did. One of the if commands didn't finish with a 'fi'. When I put that in there to finish the if command and rebooted, everything worked. Kind of odd that it affected my nic mod. Thanks for your help. -- lucas ------------------------- Perl Coder since 2001 shift || die; ------------------------- |
| |||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In alt.os.linux.slackware, lucas dared to utter, > I took a look at /etc/rc.d/rc.modules and looked at > the end of the file, didnt' see anything suspicious. > One of the if commands > didn't finish with a 'fi'. When I put that in there to finish the if > command and rebooted, everything worked. Kind of odd that it affected my > nic mod. Not odd at all matey an' if ye understood the nature o' the monster that be known as /bin/bash ye'd know that ye must have a fi ta end ye if;then statement. Without it the shell hasn't a way o' knowin' when ta stop! Ye'll be stuck there all day if'n ye haven't a fi for ye if. - -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBTai2lKR45I6cfKARAtZqAJ9BUfQHnJZRfBzHeMjeA6 E3LKawqACgtBLk fNl84Fv0zKBKcLZdlT2/wu4= =uZdq -----END PGP SIGNATURE----- |
| ||||
| pgp trash troll delete Hicks, Alan 188 Shady Dale Dr Lizella, GA 31052 478-935-8132 +Alan Hicks+ <alan@lizella.network> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In alt.os.linux.slackware, lucas dared to utter, >> I took a look at /etc/rc.d/rc.modules and looked at >> the end of the file, didnt' see anything suspicious. >> One of the if commands >> didn't finish with a 'fi'. When I put that in there to finish the if >> command and rebooted, everything worked. Kind of odd that it affected my >> nic mod. > > Not odd at all matey an' if ye understood the nature o' the monster > that be known as /bin/bash ye'd know that ye must have a fi ta end ye > if;then statement. Without it the shell hasn't a way o' knowin' when ta > stop! Ye'll be stuck there all day if'n ye haven't a fi for ye if. > > - -- > It is better to hear the rebuke of the wise, > Than for a man to hear the song of fools. > Ecclesiastes 7:5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQFBTai2lKR45I6cfKARAtZqAJ9BUfQHnJZRfBzHeMjeA6 E3LKawqACgtBLk > fNl84Fv0zKBKcLZdlT2/wu4= > =uZdq > -----END PGP SIGNATURE----- |