Re: Matshita CR-563 driver (sbpcd?)
Mark,
I had the EXACT same problem. It turned out that I
had a data-corruption in the .iso files I downloaded
via http from debian.uchicago.edu. I checked the md5
checksums, and they didn't match. I downloaded the
.iso files again, and this time the checksums matched.
If you need an md5sum for windoze let me know . . .
Actually, since my cd-burner at home hates to burn
more than 60mb to a disk, and I didn't want to go to
the office, what I did the 2nd time through was put
the .iso file on the debian install and "mount" it
through the loopback interface (Thanks Jamin). It was
quite kewl, actually . . .
mount -o loop /path/to/binary-i386-1.iso /mountpoint
and then ls -l /mountpoint displayed the contents of
the .iso file as if it were a mounted iso9660
filesystem . . .
Then I ran apt-setup and pointed it to a filesystem on
/mountpoint, and it found all the paackages. This let
me to the base install that got me gcc so I could
compile Roaring Penguin's pppoe, which got me on the
net. Then I did apt-setup again, removing the local
filesystems, and adding in the http sources, and
voila, was able to download and install console-apt
and memstat . . .
YMMV
Good Luck
madmac
--- Mark Fickett <throughtheye@lycos.com> wrote:
> Hello,
>
> I have (mostly) successfully installed the 2.2r6
> release of Debian (potato) from the official binary
> CDs on a Packard Bell with a Matshita CR-563 CD-ROM
> drive. I have used the sbpcd driver, letting it
> autoprobe (and also trying specifying "0x230,1" and
> "sbpcd=0x230,1" in turn). The installation then
> succesfully loads the base system from the first
> Debian CD, and the initial restart and setup goes
> well, until I try to install packages. At that
> point, it says that there is a CD in the drive, and
> sometimes even reads its title, but then says "Bad
> CD," and that although I have a CD its not a Debian
> CD.
>
> A suspicious thing that I noticed going by in the
> startup screen, however, is a line saying:
>
> sbpcd-0 [03]: Drive 0 (ID=0): CR-563 (0.81) at 0x340
> (type 0)
>
> which all seems correct except for the 0x340 (type
> 0), which doesn't change for any of the things I've
> tried giving the driver installation at the command
> line prompt.
>
> My questions then, are: is sbpcd definitely the
> right driver, and what should I be giving it (if it
> is) at the command prompt - if that's the problem?
>
> -Mark Fickett
>
>
>
_____________________________________________________
> Supercharge your e-mail with a 25MB Inbox, POP3
> Access, No Ads
> and NoTaglines --> LYCOS MAIL PLUS.
>
http://www.mail.lycos.com/brandPage.shtml?pageId=plus
>
>
>
> --
> To UNSUBSCRIBE, email to
> debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: