From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: cdrom/cdr trouble or ide1 problem: BIG TROUBLE I think
Date: Mon, 27 May 2002 10:25:46 -0400 [thread overview]
Message-ID: <001d01c2058a$64997700$02263e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0205262217280.360-100000@maranatha.chartermi.net>
Hi Cheryl. What was the last version at which everything worked? If one or more of your drives aren't being recognized, then to me it sounds like hardware. I would say go back tothe version at which everything worked i.e., woodie and see if your drive is recognized. Also, try using host,target,lun as your -dev when recording. I.e., -dev=0,0,0 for my drive.
----- Original Message -----
From: Cheryl Homiak <chomiak@chartermi.net>
To: speakup <speakup@braille.uwo.ca>
Sent: Sunday, May 26, 2002 11:33 PM
Subject: cdrom/cdr trouble or ide1 problem: BIG TROUBLE I think
> Ok, I've done some upgrades in debian lately (woody to sid) but i don't think
> the problem happened when I did the upgrade. I'm afraid this may be hardware
> failure with a capital H.
> I suddenly go and am still getting "not a valid block device" for /dev/record
> and /dev/cdrom and the devices for which those are symbolic links. In my
> dmesg.txt, I do get
> ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:DMA
>
> but the cdrom and cdr aren't later recognized in the dmesg as they usually are
> and nothing is mentioned about the scsi drivers loading. to troubleshoot,
> changed back in kernel to ide/atapi with same results. The cdr (first drive on
> ide1) still opens and closes with a button push and actualy can still be read in
> DOS. The cdrom won't open unless you slide the tray open manually and doesn't
> respond to commands. Doesn't work in dOS either but I may just not have figured
> out how to load two cdrom drives in DOS.
> Worst of all, "cat /proc/interrupts" shows no irq for ide1 (it has been and
> still should be but isn't, 15). I have this terrible
> feeling it's a problem directly with my ide1 or at the very least a cable. If
> so, I am thankful it isn't ide0 so I can at least opperate my system.
> I imagine the final diagnosis will have to come from somebody opening this up
> and looking (and charging me a lot of money!) but does this sound like a
> hardware problem?
> Is there any other possible explanation that would involve fixing something on
> my OS rather than major repair?
> Thanks.
>
> Cheryl
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Kerry Hoath
` Cheryl Homiak
` Kerry Hoath
` Cheryl Homiak
` Hardware failure? was " Terry Cudney
` Alex Snow
` Kerry Hoath
` Igor Gueths [this message]
` Cheryl Homiak
` Cheryl Homiak
` Kerry Hoath
` Cheryl Homiak
` Cheryl Homiak
` Cheryl Homiak
` Kerry Hoath
` Cheryl Homiak
` Kerry Hoath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001d01c2058a$64997700$02263e18@mycomputer' \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).