Date: Mon, 13 Dec 1999 16:45:20 -0600 (CST) From: Ryan Thompson <ryan@sasknow.com> To: Daniel Schrock <djab@enteract.com> Cc: freebsd-questions@freebsd.org Subject: Re: CD question Message-ID: <Pine.BSF.4.10.9912131544450.67794-100000@sasknow.com> In-Reply-To: <009701bf458d$69313100$0200a8c0@olivia>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Daniel;
I've posted this to freebsd-questions, as well.
On Mon, 13 Dec 1999, Daniel Schrock wrote:
> I apologize as this has nothing to do with your problem, but is more of a
> question of how to get the CD-rom to mount.
>
> here is part of dmesg that I get:
>
> .
> .
> wdc1 at 0x378 irq 7 flags 0x40 on isa
> wdc1: unit 0 (atapi): <WPI CDS-32X/ERe 2.0>, removable, dma, iordy
> .
> .
> acd0: read_toc failed
> acd0: read_toc failed
Please include your FULL dmesg output; in particular, you haven't included
any output from the acd detection phase .... So I'm left to wonder if you
simply omitted it from your message, or if it didn't come up at all
(suggesting that support was disabled or acd0 wasn't detected (in which
case you should have seen an acd0: not found.. type of message)). Also,
see below Re: [ (1) Information ]
> I removed mcd, scd, and matcd from the kernel, as the cd-rom is not any of
> those types,
Make sure that you did NOT remove acd. :-) As you are, by self-admission,
a newbie, I'm assuming you did NOT build a new kernel, but merely went
through the visual config at bootup, right? If you DID build a new
kernel, you might give GENERIC another go and see if you can mount then.
(If you're not familiar with what I mean by 'building a kernel', suffice
to say it's something you should read in the FreeBSD handbook when you're
more familiar with the system).
> and I've tried:
> ./MAKEDEV wcd0
Also, if you haven't done so, make sure you sh MAKEDEV acd0. See below.
> since it is a standard IDE (ATAPI) cd-rom
> using (as root):
> mount_cd9660 /dev/wcd0c /cdrom
> and
> mount_cd9660 /dev/acd0c /cdrom
Hmm... Are you sure it's on /dev/acd0c, and not acd0a? Couldn't hurt to
verify that.
Also, one common snag people run in to is using incorrect jumper settings
or cable positions when trying to fire up their CD-ROM drives. If the
drive is alone on an IDE channel, put it at the end of the IDE cable, and
jumper the CD for "single drive" mode (often, this means removing the
jumper completely, or hanging it across unconnected pin pairs). Leaving
it set to "master" is incorrect 9 times out of 10.
If the drive is sharing an IDE channel with another device such as a hard
drive, ensure that the CD drive is set to slave and is on the "middle"
cable position. Also, make sure you've got your pin orientations
straight, and everything is well seated. :-)
This may or may not fit your problem, and for you might go without saying,
but many people become careless when installing or configuring new drives.
And, as yet another common fallacy, just because Windoze reads from a
CD-ROM doesn't mean it's set up correctly :-)
> both give me :
> acd0: read_toc failed
> acd0: read_toc failed
I think I first saw these "read_toc failed" messages in 3.0-R. While
they're bothersome, and can be turned off in syslogd, they have never
appeared to have an adverse effect on my systems.
> mount_cd9660: Input/output error
>
> ls -l in /dev gives me:
> lrwxrwxr-x 1 root wheel 5 Dec 6 09:45 wcd0a -> acd0a
> lrwxrwxr-x 1 root wheel 5 Dec 6 09:45 wcd0c -> acd0c
Right. Again, please include more complete information. Those are just
symlinks to actual devices, so you haven't really shown me anything there
:-) Send me the result of `ls -la /dev/wcd* /dev/acd*`.
As an aside, you should probably be using mount -t cd9660 as opposed to
mount_cd9660. I also suggest you use the acd* entries as opposed to the
wdc*. The wdc's are just symlinks to the acd's, anyway.
> The discs I'm trying to read are the FreeBSD discs, which are brand new,
> delivered a few weeks ago.
> The drive is a Wearnes Peripheral International 32x cd-rom (model #
> CDS-32x)
> capable of reading all the standard formats (cd-r, cd-rw, audio, etc.)
Never heard of it, but if it's ATAPI, it should work. Again, a more
complete dmesg would be very helpful.
> During install, everything was read from it just fine, saying blah, blah,
> blah read from acd0 @ such and such k/sec.
Okay... That's a good sign, then. I'd check your /dev tree more carefully
and try `sh MAKEDEV acd0`.
> Do you see anything wrong with this? I'm at a loss on how to get it to
> mount as I am an extreme newbie to FreeBSD.
> Any advice would be wonderful.
>
> Also would it be possible to send me your config relating to the cd-rom for
> comparison purposes?
>
> Thank you very much and , once again, I apologize for this not relating to
> your problem. I wish I could help you, hopefully in the future I will be
> able to.
>
> Daniel Schrock
> djab@enteract.com
>
(1) Information...
In your case, I (and many others) could be of a lot more help if you
included more complete information regarding your problem. In particular:
- Full `dmesg` output:
- Unless I missed it, you didn't mention which FreeBSD release or
source build you're running. I assume, if you got new CDs, you're
using 3.3-RELEASE. Correct me if I'm wrong.
- There was no indication of the kernel reporting on 'acd' devices.
Two possibilites:
a) You simply omitted them from your message
b) You omitted them from your kernel configuration. (That would
be a Bad Thing :-)
- Full `ls -la /dev/acd* /dev/wdc*` results
- Can you play or stat an audio CD with cdcontrol -f /dev/acd0a or
/dev/acd0c? Even if you don't have a sound card, you can still get your
CD spinning and report the number of tracks, if you've got the device
node set up correctly. Even if you're not a music buff, you have to
appreciate the diagnostic significance of cdcontrol :-)
- Try some different CDs. The FreeBSD ones should work OK, but I bet
you'd be mighty peeved if you spent days sweating over a problem caused
by a goofed disc :-) If you've got any DOS data CDs laying around,
those are generally a good bet. Just don't try and install anything off
of them, ok? :-)
---
Ryan Thompson <ryan@sasknow.com>
50% Owner, Technical and Accounts
Phone: +1 (306) 664-1161
SaskNow Technologies http://www.sasknow.com
#106-380 3120 8th St E Saskatoon, SK S7H 0W2
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912131544450.67794-100000>