Re: cdrom: lost interrupt
Erik Steffl wrote: system: hdc: TDK CDRW321040B, ATAPI CD/DVD-ROM drive Linux jojda 2.4.17 #1 Wed Mar 13 01:33:28 PST 2002 i686 unknown debian unstable the cdrom is a cd r/rw writer problem: when I try to rip the audio it doesn't work much (it works VERY slowly, hours per songs) and I get the following messages in /var/log/syslog: Mar 29 00:47:12 localhost kernel: hdc: lost interrupt what works: reading raw cd using cat /dev/cdrom|od (it cannot read certain part of CD but I guess that's the feature of filesystem) reading data CDs, when I mount data CD I can read it to my heart content (and more) writing CD: so far I only tried to burn one data CD which worked without any problems, CD is readable. other info: the same problem occurs with another CD-ROM drive and also when I connect cdrom to ide0 (as slave, /dev/hdb). Hardrive connected to both ide0 and ide1 works without any problems. I also tried to turn off dma and 32 bit access, no change. I don't see any IRQ conflict, ide1 is on 15, nothing else is on 15 (as listed by BIOS and /proc/interrupts). Is it possible that it's a HW problem considering that data cd reading and buring works? I mean those use IRQs too (and I see the numbers rising when I read data CD and cat /proc/interrupts). Could it be some kernel problem? I mean how could the interrupt be lost when trying to read audio but not when reading data? I don't really know what the difference is, anybody can shed some light on this? This is a shot in the dark, but reminds me of a problem I had with my first CD-R drive. It turned out to be a DMA problem in the end. I first noticed it in Windows 98, when I couldn't burn anything, but when I switched to Linux, it worked...somewhat. The basic problem is that some chipsets (VIA-Apollo for example) dont handle DMAs like the Intel chipsets do. Linux was a bit better about handling this than Windows. Things REALLY started working fine in Windows when I turned off DMA, and in Linux when I re-compiled my kernel against my SPECIFIC chipset. There was a separate config option for it in the make config. It is entirely possible that the lost interrupts is a red-herring...dunno. I also could be just a end result of something else going wrong. Anyway, I would suggest you look into your BIOS and update if possible, and check out the chipset site for some info. I found out the solution to my problem at the VIA web site. My CD-R also had a BIOS update available that I could flash. All seemed to be part of the solution. Just some additional thoughts on the hw side for you to chew on... Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrom: lost interrupt
system: hdc: TDK CDRW321040B, ATAPI CD/DVD-ROM drive Linux jojda 2.4.17 #1 Wed Mar 13 01:33:28 PST 2002 i686 unknown debian unstable the cdrom is a cd r/rw writer problem: when I try to rip the audio it doesn't work much (it works VERY slowly, hours per songs) and I get the following messages in /var/log/syslog: Mar 29 00:47:12 localhost kernel: hdc: lost interrupt what works: reading raw cd using cat /dev/cdrom|od (it cannot read certain part of CD but I guess that's the feature of filesystem) reading data CDs, when I mount data CD I can read it to my heart content (and more) writing CD: so far I only tried to burn one data CD which worked without any problems, CD is readable. other info: the same problem occurs with another CD-ROM drive and also when I connect cdrom to ide0 (as slave, /dev/hdb). Hardrive connected to both ide0 and ide1 works without any problems. I also tried to turn off dma and 32 bit access, no change. I don't see any IRQ conflict, ide1 is on 15, nothing else is on 15 (as listed by BIOS and /proc/interrupts). Is it possible that it's a HW problem considering that data cd reading and buring works? I mean those use IRQs too (and I see the numbers rising when I read data CD and cat /proc/interrupts). Could it be some kernel problem? I mean how could the interrupt be lost when trying to read audio but not when reading data? I don't really know what the difference is, anybody can shed some light on this? BTW cd ripping works fine under windows, even though I've read that it doesn't mean much 'cause windows often pools hw instead of using IRQ. The web search revealed nothing interesting, only that most people who have lost interrupt problem can't even mount the CD. This is what /proc/interrupts says (I haven't used the CD since I rebooted and I cannot use it now since there's no CD inside and I am not around): jojda:/home/erik# cat /proc/interrupts CPU0 0: 15518706 XT-PIC timer 1: 8968 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 0 XT-PIC SoundBlaster 8: 1 XT-PIC rtc 9: 0 XT-PIC usb-uhci, usb-uhci 10: 33210 XT-PIC eth1 11: 530613 XT-PIC eth0 12: 39386 XT-PIC PS/2 Mouse 14: 593071 XT-PIC ide0 15: 21 XT-PIC ide1 NMI: 0 LOC: 15518583 ERR: 0 TIA! erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrom lost
Well- I am running slink (2.1) on a thinkpad laptop. I use a docking station with a scsi card and cdrom to install, and wanted to add a couple of packages. I have done this before without difficulty, but this time I cannot get to the cdrom as scd0 or cdrom on mnt or dev. There is nothing in fstab or mtab which appears to have anything at all to do with the cdrom, or the scsi hard drive I want to use for backing up files. (I haven't modified these files.) Why is this? -- Koyote that which does not kill us, makes us quote Nietzsche. Don Webb