[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Rule-list] Fw: still stuck on sbpcd kinda
From: |
Devon |
Subject: |
Re: [Rule-list] Fw: still stuck on sbpcd kinda |
Date: |
Sun, 31 Mar 2002 23:47:58 -0500 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 31 March 2002 11:02 pm, Gordon Buzowetsky wrote:
> > insmod /lib/modules/"$version"/kernel/drivers/cdrom/cdrom.o &&
> > insmod /lib/modules/"$version"/kernel/drivers/cdrom/sbpcd.o
> > sbpcd=0x230,1
> Alrighty....but what's the difference between & and &&....? Do they not
> do the same thing??
insmod /lib/modules/"$version"/kernel/drivers/cdrom/cdrom.o &
Puts the process in the background and continues. (which may cause the
sbpcd module to attempt to load before the cdrom module has finished
loading)
insmod /lib/modules/"$version"/kernel/drivers/cdrom/cdrom.o &&
insmod /lib/modules/"$version"/kernel/drivers/cdrom/sbpcd.o sbpcd=0x230,1
(that probably needs to be all one line, or be broken with a \)
Should cause the cdrom module to load, and only after it has loaded
successfully, will the sbpcd module be loaded.
For debugging if it still doesn't work, you could try:
Create a file loadmods.sh
Put the following in the file:
########################
#! /bin/sh -vx
version=`uname -r`
insmod /lib/modules/"$version"/kernel/drivers/cdrom/cdrom.o &&\
insmod /lib/modules/"$version"/kernel/drivers/cdrom/sbpcd.o sbpcd=0x230,1
if [ "$?" -ne "0" ]; then
echo "This cdrom is a pain! Module failed to load!"
else
echo "Done."
fi
exit
###########################
Don't forget 'chmod +x' the file.
Make sure the cdrom module is NOT loaded.
'rmmod sbpcd' and 'rmmod cdrom' if need be, and run the script.
If it works, you can try putting the commands in rc.local, or just call
the script from rc.local.
The output here is:
address@hidden root]# ./loadmods.sh
#! /bin/sh -vx
version=`uname -r`
uname -r
++ uname -r
+ version=2.4.9-21
insmod /lib/modules/"$version"/kernel/drivers/cdrom/cdrom.o &&\
insmod /lib/modules/"$version"/kernel/drivers/cdrom/sbpcd.o sbpcd=0x230,1
+ insmod /lib/modules/2.4.9-21/kernel/drivers/cdrom/cdrom.o
+ insmod /lib/modules/2.4.9-21/kernel/drivers/cdrom/sbpcd.o sbpcd=0x230,1
/lib/modules/2.4.9-21/kernel/drivers/cdrom/sbpcd.o: init_module:
Input/output error
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
if [ "$?" -ne "0" ]; then
echo "This cdrom is a pain! Module failed to load!"
else
echo "Done."
fi
+ '[' 1 -ne 0 ']'
+ echo 'This cdrom is a pain! Module failed to load!'
This cdrom is a pain! Module failed to load!
exit
+ exit
Which is as expected, since I don't have a soundblaster cdrom.
- -D
- --
pgp key: http://www.tuxfan.homeip.net:8080/pgpkey.txt
Red Hat Linux 7.2 in 8M of RAM: http://www.freesoftware.fsf.org/rule/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8p+Z+eMAUbzJhSVcRArSaAJ4ljzZgOs1mULVmx2hUKAYm3BJStgCglzYS
kv12056JzuslLEuk5Y4dcUk=
=o6qz
-----END PGP SIGNATURE-----
- [Rule-list] Fw: still stuck on sbpcd kinda, Gordon Buzowetsky, 2002/03/30
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Devon, 2002/03/30
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Gordon Buzowetsky, 2002/03/30
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Devon, 2002/03/30
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Martin Stricker, 2002/03/31
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Gordon Buzowetsky, 2002/03/31
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Devon, 2002/03/31
- Re: [Rule-list] Fw: still stuck on sbpcd kinda, Gordon Buzowetsky, 2002/03/31
- Re: [Rule-list] Fw: still stuck on sbpcd kinda,
Devon <=