Newsgroup: it.comp.os.linux.sys
Titolo: The drive appears confused

ho di tanto in tanto problemi col masterizzatore, e da dmesg leggo questo:
 PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Disabled
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 3
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: No IRQ known for interrupt pin A of device 0000:00:11.1 - using IRQ
255
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even
'acpi=off'
vesafb: framebuffer at 0xd0000000, mapped to 0xe0809000, size 16384k
vesafb: mode is 800x600x16, linelength=1600, pages=67
vesafb: protected mode interface info at c000:544d
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
devfs: 2004-01-31 Richard Gooch (
rgo...@atnf.csiro.au
)
devfs: boot_options: 0x1
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
spurious 8259A interrupt: IRQ7.
isapnp: No Plug & Play device found
bootsplash 3.1.3-2003/11/14: looking for picture.... silentjpeg size 14856
bytes, found (800x600, 14808 bytes, v3).
Console: switching to colour frame buffer device 92x32
pty: 1024 Unix98 ptys configured
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
ACPI: No IRQ known for interrupt pin A of device 0000:00:11.1 - using IRQ
255
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:pio
hda: ST94011A, ATA DISK drive
hda: IRQ probe failed (0xfffffdfa)
hdb: IRQ probe failed (0xfffffdfa)
hdb: IRQ probe failed (0xfffffdfa)
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: DVD+RW RW8160, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 >
Console: switching to colour frame buffer device 92x32
mice: PS/2 mouse device common for all mice
.......
ide-cd: cmd 0x3 timed out
hdc: lost interrupt
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
ide-cd: cmd 0x3 timed out
hdc: lost interrupt
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
PPP BSD Compression module registered
PPP Deflate Compression module registered
ide-cd: cmd 0x3 timed out
hdc: lost interrupt
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
ho provato varie distrubuzioni fedora core 2, madrake 10, suse 9.1 ma
l'errore si ripete con tutte, da quel che leggo su google non sono il
solo, ma non trovo suluzioni, mi potete dare una mano??
Grazie!!
-- 
questo articolo e` stato inviato via web dal servizio gratuito 
http://www.newsland.it/news
 segnala gli abusi ad 
ab...@newsland.it

 hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01)
Potrebbe essere un cavo molle, o magari il masterizzatore che sta' andando
a pallino.
Davide
-- 
"I'd love to go out with you, but it's my parakeet's bowling night."

 Davide
ma, con win va tutto benissimo, ad ogni modo, anche se fosse un difetto
hardware, non esiste un modo per aggirare il problema??


 hardware, non esiste un modo per aggirare il problema??
Piu' che aggirarlo, ricompilare il kernel col supporto
giusto per il tuo chipset, IMHO.
bye G.L.
-- 
« E' assolutamente evidente che l'arte del cinema
  si ispira alla vita, mentre la vita si ispira alla TV »
(Woody Allen)

 bye G.L.
cavolo, sono non sono un esperto e mi trovo un pò "a piedi", ho un chipset
VIA, mi puoi indicare un buon indirizzo dove trovare le istruzioni per
ricompilare il kernel???


 ricompilare il kernel???
Cerca il Kernel-Howto.
