[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

TuxTops 20U: CDR and PCMCIA problems



I've purchased an Amethyst 20U (Compal 20U OEM) with the optional
docking base unit containing a floppy and cdrom.  

I'm running Debian GNU/Linux, kernel:

    GNU/Linux version 2.2.18pre21 (root@shrink) (gcc version 2.95.2
    20000220 (Debian GNU/GNU/Linux)) #1 Thu Jan 25 18:40:22 PST 2001


The CDROM is producing the following errors either after a power
suspend via APM, *OR* after simply having been in operation for a period
of time.  The problem is decidedly intermittent.

    Jan 30 15:05:11 ego kernel: end_request: I/O error, dev 16:00 (hdc), sector 0
    Jan 30 15:05:11 ego kernel: hdc: status error: status=0x50 { DriveReady SeekComplete }
    Jan 30 15:05:11 ego last message repeated 3 times
    Jan 30 15:05:11 ego kernel: hdc: ATAPI reset complete
    Jan 30 15:05:11 ego kernel: hdc: status error: status=0x50 { DriveReady SeekComplete }
    Jan 30 15:05:11 ego last message repeated 3 times
    Jan 30 15:05:11 ego kernel: hdc: ATAPI reset complete
    Jan 30 15:05:11 ego kernel: hdc: status error: status=0x50 { DriveReady SeekComplete }
    Jan 30 15:05:11 ego kernel: end_request: I/O error, dev 16:00 (hdc), sector 0
    Jan 30 15:05:11 ego kernel: hdc: status error: status=0x50 { DriveReady SeekComplete }
    Jan 30 15:05:11 ego last message repeated 3 times
    Jan 30 15:05:11 ego kernel: hdc: ATAPI reset complete
    Jan 30 15:05:11 ego kernel: hdc: status error: status=0x50 { DriveReady SeekComplete }
    Jan 30 15:05:11 ego last message repeated 3 times
    Jan 30 15:05:11 ego kernel: hdc: ATAPI reset complete
    Jan 30 15:05:21 ego kernel: hdc: lost interrupt

Is this a configuration problem, a docking port problem (I *think* the
damned thing's securely attached -- no problems with the floppy, and the
CDR is otherwise powered and responsive).  This is, BTW, a CDROM drive.
*NOT* CD-writable or DVD.  Just plain old CDR.

...I'm running WindowMaker, and have 'wmcdplay' and 'mountapp', either
or both of which may be periodically probing the CDR.  Not sure if this
is relevant, think it could be.


----------------------------------------
Other problem:

With PCMCIA, I get the following message when issuing the 'cardmgr'
command:

    Jan 30 15:15:45 ego cardmgr[2886]: starting, version is 3.1.22
    Jan 30 15:15:45 ego cardmgr[2886]: open_sock(socket 0) failed: Permission denied
    Jan 30 15:15:45 ego cardmgr[2886]: no sockets found!
    Jan 30 15:15:45 ego cardmgr[2886]: exiting

cardmgr is from the pmcia-cs Debian package:

    Package: pcmcia-cs
    Priority: extra
    Section: base
    Installed-Size: 533
    Maintainer: Brian Mays <brian@debian.org>
    Architecture: i386
    Version: 3.1.22-0.1potato

I've read elsewhere that order matters in configuring PCMCIA devices --
does it matter that the system otherwise already has networking running?
I've got a PCMCIA fax/modem, but use the onboard NIC (eepro100) for
LAN-based networking.


I talked to Danny ARM Computers Tuesday afternoon (TuxTops support
and OEM (?) vendor).  He's unfamiliar with GNU/Linux, couldn't offer any
support other than troubleshooting the hardware, making sure it's
plugged in, etc.

Thanks.

-- 
Karsten M. Self <kmself@ix.netcom.com>    http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?       There is no K5 cabal
  http://gestalt-system.sourceforge.net/         http://www.kuro5hin.org

Attachment: pgprS55WlT1B1.pgp
Description: PGP signature


Reply to: