Re: problems ripping cds
himba <[email protected]>
| Newsgroups | gmane.comp.audio.cd-paranoia.general |
|---|---|
| Message-ID | <[email protected]> |
Jack Pistachio wrote: > What is your ide chipset? Many have had similar problems > (inluding myself) on via chipsets. See archived messages. > If you have a promise controller on the same mb, try using > that. > - jackp > I have another news that might be interesting to users with VIA chipsets. On my notebook I have also VIA chipset and lspci returns: 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) what seems to be the same that I have on desktop box (see my previous post). The good news is that I can rip audio cds on my notebook with no hassle!!!! I'm using scsi emulation on dvd/cd-rw combo drive in notebook as well. rgds.himba > > > --- himba <[email protected]> wrote: > >>hello >> >>I was courios about audio CD ripping under linux and ran >>into cdparonia >>project. I'm runing Suse9 and have currently installed a >>CDROM and CDRW >>ATAPI devices. Both are using ide-scsi module. I can get >>CD track info, >>but I can't rip none of my audio CDs. The light on device >>is lit, but >>kernel log has several reports: >>.... >>Jan 12 16:56:10 xodus kernel: scsi : aborting command due >>to timeout : >>pid 517, scsi0, channel 0, id 0, lun 0 UNKNOWN(0xbe) 00 >>00 00 00 00 00 >>00 07 f8 00 00 >>Jan 12 16:56:10 xodus kernel: hdc: lost interrupt >>Jan 12 16:56:10 xodus kernel: ide-scsi: The scsi wants to >>send us more >>data than expected - discarding data >>Jan 12 16:56:10 xodus kernel: ide-scsi: [[ be 0 0 0 0 0 0 >>0 7 f8 0 0 ] >>Jan 12 16:56:10 xodus kernel: ] >>Jan 12 16:56:10 xodus kernel: ide-scsi: expected 16464 >>got 18816 limit 16464 >>Jan 12 16:56:10 xodus kernel: ide-scsi: transferred 7056 >>of 9408 bytes >>Jan 12 16:57:10 xodus kernel: scsi : aborting command due >>to timeout : >>pid 520, scsi0, channel 0, id 0, lun 0 UNKNOWN(0xbe) 00 >>00 00 00 21 00 >>00 0d f8 00 00 >>Jan 12 16:57:10 xodus kernel: hdc: lost interrupt >>Jan 12 16:57:10 xodus kernel: hdc: irq timeout: >>status=0xd0 { Busy } >>Jan 12 16:57:10 xodus kernel: hdc: ATAPI reset complete >>Jan 12 16:57:10 xodus kernel: hdc: irq timeout: >>status=0x80 { Busy } >>Jan 12 16:57:10 xodus kernel: hdc: ATAPI reset complete >>Jan 12 16:57:10 xodus kernel: hdc: irq timeout: >>status=0x80 { Busy } >>.... >> >>I'm using SCSI emulation. >> >>Is there a way to remedy this? >> > > > __________________________________ > Do you Yahoo!? > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > http://hotjobs.sweepstakes.yahoo.com/signingbonus > --- >8 ---- > List archives: http://www.xiph.org/archives/ > Paranoia homepage: http://www.xiph.org/paranoia/ > To unsubscribe from this list, send a message to '[email protected]' > containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered. > --- >8 ---- List archives: http://www.xiph.org/archives/ Paranoia homepage: http://www.xiph.org/paranoia/ To unsubscribe from this list, send a message to '[email protected]' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.