LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-06-2005, 09:03 AM   #1
shadkong
Member
 
Registered: Apr 2005
Location: Guangzhou, China
Distribution: Slackware 10.2
Posts: 114

Rep: Reputation: 15
What does this sentence mean?


Just now I shutdown the slackware 10.1 by "halt". At first, there is all OK. Last it shows "Power down", and then "sbpcd-0 [04]:No drive found." What does this last sentence mean? Does it mean something wrong?
 
Old 04-06-2005, 09:34 AM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
it means that the sound blaster cd rom driver was unable to find any crap old SB cards with onboard support for CD roms.... somehow i doubt you have your cdrom connected via an long obselete sound card architecture! either 1) ignore or 2) remove the sbpcd.(k)o driver module from your kernel totally.
 
Old 04-06-2005, 09:47 AM   #3
shadkong
Member
 
Registered: Apr 2005
Location: Guangzhou, China
Distribution: Slackware 10.2
Posts: 114

Original Poster
Rep: Reputation: 15
What is "sbpcd.(k)o driver module" and what is sbpcd? Can you tell me something about it? I am really a newbie. Thanks!
 
Old 04-06-2005, 09:58 AM   #4
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
i just did.... it's a driver to run cdrom's connected to soundblaster cards. it's ooooooooooold
 
Old 04-06-2005, 03:09 PM   #5
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,300

Rep: Reputation: 90
Just ignore it, it doesn't bite.
 
Old 04-06-2005, 10:23 PM   #6
MMYoung
Member
 
Registered: Apr 2004
Location: Arkansas
Distribution: Ubuntu 8.10
Posts: 365

Rep: Reputation: 30
You can add sbpcd to /etc/hotplug/blacklist and you won't ever see that message again.

HTH,
MMYoung
 
Old 04-06-2005, 10:33 PM   #7
shadkong
Member
 
Registered: Apr 2005
Location: Guangzhou, China
Distribution: Slackware 10.2
Posts: 114

Original Poster
Rep: Reputation: 15
I found it does not happen every time, why?
 
Old 04-07-2005, 02:50 AM   #8
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
does it matter?
 
Old 04-07-2005, 05:05 AM   #9
shadkong
Member
 
Registered: Apr 2005
Location: Guangzhou, China
Distribution: Slackware 10.2
Posts: 114

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by acid_kewpie
does it matter?
No.
 
Old 04-07-2005, 06:42 AM   #10
killerbob
Member
 
Registered: Oct 2004
Location: Ottawa, ON
Distribution: Slackware
Posts: 662

Rep: Reputation: 31
Quote:
I found it does not happen every time, why?

... alright, here's the long and detailed answer.

A long time ago, in a galaxy far, far away... well, not quite, but around the same era that these came out, computers started shipping with sound cards. Among the more popular were SoundBlaser, ProAudio Spectrum, and Gravis Ultrasound. We'll ignore the on-chip soundcards that came with Commodore computers. These were all 8-bit soundcards, btw. Sound playback was there, but by modern standards it was pretty crappy.

Then CreativeLabs introduced the SoundBlaster 16 around 1987. Overnight, it became the de facto standard sound card, because unlike all of the competitors, it was 16-bit. It also had a whole bunch of extras in it that made it essential to the power computer, namely a special bus controller on the card that could control CDROM drives. Back in those days, IDE didn't really exist, and a hard drive controller couldn't handle the 1X and 2X CDROM drives that were being made. In fact, you needed a separate expansion card that could have cost upwards of $100 to be able to install a CDROM.

Creative realised that most people would probably only want one CDROM, not two, and so they put a bastardised CDROM controller on the SB16. It worked. Why spend $100 for a CDROM controller, when you could spend $75 for a sound card, and get a free CDROM controller with it?

Anyway, fast-forward 15 years, and sound cards are still being made with the same chip as the SB16, but CDROM drives have become a whole lot cheaper and can be controlled with the same controller that handles the hard drive. I still have an old SB16 with an on-card CDROM controller lying around somewhere, but I can't remember the last computer I used it in. Linux, however, still maintains support for elderly computer hardware, because Linus realised that whole lot of linux users are using it because they want computing on the cheap. That means supporting hardware that you could pick up for $5 at your local computer recyclers, which would include stuff like an SB16. And it's a good choice, because I *have* installed Linux from one of those CDROM drives using LoadLin.




Anyway, in your case, for one reason or another, the kernel seems to be loading the SB16 CDROM drivers. Don't ask me why, because I'm a hardware geek, not a software geek. What I can tell you is that in the default kernel distribution configuration, support for those old CDROM drives is off by default. This error message appearing is probably one of the reasons, but a better reason might be that it's a fair bet that you aren't running an old 1X or 2X CDROM in this day and age. For one reason or another, the CDROM driver is being loaded by hotplug sometimes. You've probably got some hardware that responds sorta like this. As somebody before me said, adding a line for sbpcd to /etc/hotplug/blacklist will probably fix the problem.


As for what it actually means, it's a nothing error, just like the complaints about ide_scsi and agpgart modules if, like me, you compiled those modules directly into the kernel instead of module-izing them. You're safe to ignore it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
can sed edit individual characters/portions of a sentence? TGWDNGHN Linux - Software 10 10-18-2005 04:50 AM
Removing a preceding pattern from each sentence ganninu Programming 2 12-11-2003 07:15 AM
I Think M$ has the order of this sentence Mixed up, don't you think! ;) shassouneh General 14 06-02-2002 07:43 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:24 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration