problems with cd/dvd drives fedora core 6

Antonio Olivares olivares14031 at yahoo.com
Sat Mar 24 15:09:09 UTC 2007


--- Tim <ignored_mailbox at yahoo.com.au> wrote:

> On Thu, 2007-03-22 at 14:52 -0700, Antonio Olivares
> wrote:
> > I do not know, why but this machine only has KDE,
> and it was working
> > fine.  Suddenly the weird messages starting
> appearing and I tried to
> > open k3b and it hung.  There were no devices found
> /dev/hdc
> > and/or /dev/hdd since there are two drives one
> DVD/+R-R+RW-RW and a cd
> > +r.  I could not even boot live linux cd's when
> before there were no
> > problems.
> 
> The last sentence points to it being a problem with
> your hardware.
> "Booting" a CD has nothing to do with an OS on your
> hard drive.
> 
> I'd try:
> 
> Carefully going through your BIOS settings.
> Swapping the power connector to your DVD for an
> unused one.
> Swapping the ribbon lead to the DVD for a new one.
> Removing the plug-in cards and re-inserting them. 
> Likewise, firmly
> pressing any socketed chips into their sockets.
> Swapping the DVD-ROM.
> Swapping the power supply.
> Suspecting the motherboard, itself.
> 
> If you move the box around, you can walk cards out
> of their sockets.
> Most cases aren't that rigid, some are so poor you
> can twist a board
> until you crack it.  And if you've been plugging and
> unplugging hardware
> without taking anti-static precautions, that may
> lead to hardware
> failure, and *not* instantly.
> 
> -- 
> (This box runs FC6, my others run FC4 & FC5, in case
> that's
>  important to the thread.)
> 
> Don't send private replies to my address, the
> mailbox is ignored.
> I read messages from the public lists.
> 
> 
> -- 
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> 

Following your advice, I could boot into a linux live
again. One of the drives is failing while the other
was not connected all the way.  

Linux version 2.6.20 (root at slax) (gcc version 3.4.6)
#2 SMP Wed Feb 7 17:26:47 G
MT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size:
000000000009fc00 end: 000000000009
fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size:
0000000000000400 end: 00000000000a
0000 type: 2
copy_e820_map() start: 00000000000f0000 size:
0000000000010000 end: 000000000010
0000 type: 2
copy_e820_map() start: 0000000000100000 size:
0000000017ef0000 end: 0000000017ff
0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 0000000017ff0000 size:
0000000000003000 end: 0000000017ff
3000 type: 4
copy_e820_map() start: 0000000017ff3000 size:
000000000000d000 end: 000000001800
0000 type: 3
copy_e820_map() start: 00000000ffff0000 size:
0000000000010000 end: 000000010000
0000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00
(usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000
(reserved)
......... much more stuff here ........
hdc: DVD DC 16X8X5, ATAPI CD/DVD-ROM drive
hdd: RW-241040, ATAPI CD/DVD-ROM drive
......... much more stuff here ........
hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB
Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache,
UDMA(33)

loading up k3b also freeses and thus points to a bad
drive.  One line from dmesg in slax makes me wonder,
it does not show up on Fedora's dmesg

pci_set_power_state(): 0000:00:0b.0: state=3, current
state=5
pci_set_power_state(): 0000:00:0b.0: state=3, current
state=5


Thanks for helping out,

Antonio 



 
____________________________________________________________________________________
Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367




More information about the fedora-list mailing list