Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just upgraded from RH 6.2 to 7.1 and finally figured out that I needed to give the parms 0x230,1 to sbpcd during install. So it installed, but now whenever I try and mount the CDROM dmesg gives "scanning for soundblaster at 0x340". I have an append statement in lilo ="sbpcd=0x230,Soundblaster" and also tried ="sbpcd=0x230,1" but to no avail. What do I need to do to get sbpcd to look for my cd rom at 0x230? Thanks in advance,
According to here , the line append = "sbpcd=0x230,SoundBlaster" is what you are supposed to put in your lilo.conf file. Just remember, that after you edit your lilo.conf file to run /sbin/lilo as root.
Duh... I did update lilo.conf and tried lilo earlier and it couldn't write the boot record. adding boot /dev/hda helped i rebooted
and now dmesg says that it is adding the sbpcd parms. unfortunately, sbpcd is still scanning for 0x340 lasermate, 0x340 soundblaster and then saying 'uniform cd-rom driver unloaded'.. any other thoughts? Thanks.
Did you run the this command (mount -r -t iso9660 /dev/sbpcd /your/mount/point/here) ? You said that you ran the command mount -r -t iso9660 /dev/cdrom /mnt/cdrom.
I noticed that the last line of your fstab file doesn't have the two numbers that are supposed to be there. Did you leave them off?
One of your error messages says that /dev/sbpcd is an unknown device. Do an ls /dev/sbpcd* and see if sbpcd if listed. If it's not there, you'll have to make one. Could you post a copy of your lilo.conf file?
thanks for the help. Yes I tried mount -r -t iso9660 /dev/sbpcd /mnt/cdrom and get >mount: /dev/sbpcd: unknown device. I also reinstalled Linux 7.1 and it found my cdrom when I added 0x230,1 as parameters during install, but still can't find it after...
It could be that there is a problem with your kernel. I was searching the web and I found references to problems in 2.4.2 kernels concerning sbpcd. One said that if sbpcd was compiled into the kernel, it worked. But if insmod was used, sbpcd would ignore any parameters that were passed to it.
Your version appears to be ignoring parameters that are passed to it.
When I ran sbpcd on my system, it first scanned for the lasermate on 0x340. Then it scans for the soundblaster on 0x230. If I pass the parameter 0x230,1 to it, scans for soundblaster first on 0x230 then it scans again for the soundblaster on 0x230. I tried again with the parameter 0x340,1 and it scans for soundblaster on 0x340 then it scans for soundblaster on 0x230. So, on my system it appears to work.
So, it could be your kernel.
As to why it worked on the install, the install probably used a different kernel.
I was playing around and used insmod once to see what would happen.. would that change my kernel? When you run sbpcd do you just execute it from a linux terminal window? When I look in /proc/devices sbpcd doesn't show up (which was one of the hints from the CDROM HOWTO), if that's true do I need to rebuild the kernel? Also, how can I get the source on the computer from the CDROM if I can't access the CDROM? (wow-I know a lot of questions here. thanks for helping me, linuxcool...) can I copy the install kernel over my existing kernel...
The command insmod doesn't change your kernel, it just links a module to the kernel so that the kernel can use it. When you reboot your computer the module won't be available to the kernel until insmod is run again. You can have the module installed when you boot up by editing the /etc/modules.conf or the /etc/conf.modules file and add a line or lines to it.
Yes, you can run insmod from a terminal window but it must be a text screen and you must be root. No graphical interface like gnome or kde. I tried to run it in kde and after waiting a while it told me it was busy and terminated.
Use the number ' 1 '. Don't use the string ' SoundBlaster '. If the module is already installed, it will tell you it is.
Could you post a copy of your /etc/modules.conf or /etc/conf.modules file. I don't know which one you have.
You might be able to download the source code for the kernel.
As for the install kernel, I don't know if it would work with your install. If you were able to get the install kernel, you wouldn't copy it over your current kernel. You would copy it into your /boot directory and add some lines to your lilo.conf file to let you boot from either one.
thanks again for trying to help. When I tried
insmod /lib/modules/2.4.2-2/kernel/drivers/cdrom/sbpcd.o sbpcd=0x230,1
I get 3 messages about unresolved symbols: register_cdrom_Re92ea998, unregister_cdrom_R010c2aac and cdrom_fops_R4eb9a092
here's my modules.conf:
alias cdrom sbpcd
alias parport_lowlevel parport_pc
alias eth0 ne
I've also tried adding
options sbpcd sbpcd=0x230,1
in different flavors to modules.conf with no luck.
when I do a modprobe sbpcd, i get the following:
sbpcd.o: init_module: Input/loutput error
Hint: insmod errors can be caused by incorrectx modules parameters, including inavlid IO or IRQ parameters
/lib/modules.../sbpcd.o: insmod /lib/modules.../sbpcd.o failed
/lib/modules.../sbpcd.o: insmod spbcd failed
if i could ever get sbpcd to take the parameters it seems like i'd be ok...
thanks in advance,