playing/ripping audio cds
in [Debian]
|
From: Ron Johnson on 24 Mar 2010 13:40 On 2010-03-24 12:08, Rick Pasotto wrote: > On Wed, Mar 24, 2010 at 10:46:11AM -0500, Ron Johnson wrote: >> On 2010-03-24 09:37, Rick Pasotto wrote: >>> On Tue, Mar 23, 2010 at 03:39:53PM -0500, Ron Johnson wrote: >>>> On 2010-03-23 15:21, Rick Pasotto wrote: >>>>> Additional problem: I aborted the ripping because it caused the monitor >>>>> to turn off and then back on every few seconds. For the past few weeks >>>>> the monitor has been occasionally cycling off and then on but only >>>>> occasionally. While ripping with grip the cycling was constant. >>> I tried again with grip and the results were worse. The monitor cycled >>> off and on so fast it finally gave up and stayed off. I had to reboot. >> That's too weird. Anything in syslog, dmesg or /var/log/messages? > > Thanks for reminding me. I hadn't looked. Yes, I'm getting lots of > errors on /dev/hda. Here are some examples: > > Mar 24 12:17:49 niof kernel: [69407.680380] VFS: busy inodes on changed media or resized disk hda > Mar 24 12:17:49 niof kernel: [69407.696160] VFS: busy inodes on changed media or resized disk hda > Mar 24 12:17:49 niof kernel: [69407.716151] VFS: busy inodes on changed media or resized disk hda Seems like autofs isn't properly telling the kernel that media has changed. > and > > Mar 24 12:19:53 niof kernel: [69532.316244] hda: command error: status=0x51 { DriveReady SeekComplete Error } > Mar 24 12:19:53 niof kernel: [69532.316256] hda: command error: error=0x50 { LastFailedSense=0x05 } > Mar 24 12:19:53 niof kernel: [69532.316262] hda: possibly failed opcode: 0xa0 > Mar 24 12:19:53 niof kernel: [69532.320570] end_request: I/O error, dev hda, sector 9144696 > Mar 24 12:19:53 niof kernel: [69532.320579] __ratelimit: 505 callbacks suppressed > Mar 24 12:19:53 niof kernel: [69532.320585] Buffer I/O error on device hda, logical block 1143087 > Mar 24 12:19:53 niof kernel: [69532.320596] Buffer I/O error on device hda, logical block 1143088 > > Archive dvds I've burned and commercial dvds both load but then shortly > the monitor cyclying begins and I eject the disk as quickly as I can. > >> What kind of video do you have? On-board? > > Yes. The Xorg.log shows: Device "KM4M-V on-board video" > Which probably shares system RAM. I bet the busy system is somehow saturating the memory channel(s), thus causing the flickering. -- "History does not long entrust the care of freedom to the weak or the timid." Dwight Eisenhower -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BAA4C75.6000002(a)cox.net
From: Rick Pasotto on 24 Mar 2010 13:50 On Wed, Mar 24, 2010 at 12:31:33PM -0500, Ron Johnson wrote: > On 2010-03-24 12:08, Rick Pasotto wrote: > >On Wed, Mar 24, 2010 at 10:46:11AM -0500, Ron Johnson wrote: > >>On 2010-03-24 09:37, Rick Pasotto wrote: > >>>On Tue, Mar 23, 2010 at 03:39:53PM -0500, Ron Johnson wrote: > >>>>On 2010-03-23 15:21, Rick Pasotto wrote: > >>>>>Additional problem: I aborted the ripping because it caused the monitor > >>>>>to turn off and then back on every few seconds. For the past few weeks > >>>>>the monitor has been occasionally cycling off and then on but only > >>>>>occasionally. While ripping with grip the cycling was constant. > >>>I tried again with grip and the results were worse. The monitor cycled > >>>off and on so fast it finally gave up and stayed off. I had to reboot. > >>That's too weird. Anything in syslog, dmesg or /var/log/messages? > > > >Thanks for reminding me. I hadn't looked. Yes, I'm getting lots of > >errors on /dev/hda. Here are some examples: > > > >Mar 24 12:17:49 niof kernel: [69407.680380] VFS: busy inodes on changed media or resized disk hda > >Mar 24 12:17:49 niof kernel: [69407.696160] VFS: busy inodes on changed media or resized disk hda > >Mar 24 12:17:49 niof kernel: [69407.716151] VFS: busy inodes on changed media or resized disk hda > > Seems like autofs isn't properly telling the kernel that media has > changed. Is there something that I can do about that? > >and > > > >Mar 24 12:19:53 niof kernel: [69532.316244] hda: command error: status=0x51 { DriveReady SeekComplete Error } > >Mar 24 12:19:53 niof kernel: [69532.316256] hda: command error: error=0x50 { LastFailedSense=0x05 } > >Mar 24 12:19:53 niof kernel: [69532.316262] hda: possibly failed opcode: 0xa0 > >Mar 24 12:19:53 niof kernel: [69532.320570] end_request: I/O error, dev hda, sector 9144696 > >Mar 24 12:19:53 niof kernel: [69532.320579] __ratelimit: 505 callbacks suppressed > >Mar 24 12:19:53 niof kernel: [69532.320585] Buffer I/O error on device hda, logical block 1143087 > >Mar 24 12:19:53 niof kernel: [69532.320596] Buffer I/O error on device hda, logical block 1143088 > > > >Archive dvds I've burned and commercial dvds both load but then shortly > >the monitor cyclying begins and I eject the disk as quickly as I can. > > > >>What kind of video do you have? On-board? > > > >Yes. The Xorg.log shows: Device "KM4M-V on-board video" > > Which probably shares system RAM. I bet the busy system is somehow > saturating the memory channel(s), thus causing the flickering. This problem is *very* recent. Currently htop shows 465/946MB of system RAM and only 91/1906MB of swap having been used. -- "If a thousand men were not to pay their tax bills this year, that would not be a violent and bloody measure, as it would be to pay them, and enable the State to commit violence and shed innocent blood. This is, in fact, the definition of a peaceable revolution, if any such is possible." -- Henry David Thoreau Rick Pasotto rick(a)niof.net http://www.niof.net -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100324174911.GF4850(a)niof.net
From: Ron Johnson on 24 Mar 2010 14:10 On 2010-03-24 12:49, Rick Pasotto wrote: > On Wed, Mar 24, 2010 at 12:31:33PM -0500, Ron Johnson wrote: >> On 2010-03-24 12:08, Rick Pasotto wrote: >>> On Wed, Mar 24, 2010 at 10:46:11AM -0500, Ron Johnson wrote: >>>> On 2010-03-24 09:37, Rick Pasotto wrote: >>>>> On Tue, Mar 23, 2010 at 03:39:53PM -0500, Ron Johnson wrote: >>>>>> On 2010-03-23 15:21, Rick Pasotto wrote: >>>>>>> Additional problem: I aborted the ripping because it caused the monitor >>>>>>> to turn off and then back on every few seconds. For the past few weeks >>>>>>> the monitor has been occasionally cycling off and then on but only >>>>>>> occasionally. While ripping with grip the cycling was constant. >>>>> I tried again with grip and the results were worse. The monitor cycled >>>>> off and on so fast it finally gave up and stayed off. I had to reboot. >>>> That's too weird. Anything in syslog, dmesg or /var/log/messages? >>> Thanks for reminding me. I hadn't looked. Yes, I'm getting lots of >>> errors on /dev/hda. Here are some examples: >>> >>> Mar 24 12:17:49 niof kernel: [69407.680380] VFS: busy inodes on changed media or resized disk hda >>> Mar 24 12:17:49 niof kernel: [69407.696160] VFS: busy inodes on changed media or resized disk hda >>> Mar 24 12:17:49 niof kernel: [69407.716151] VFS: busy inodes on changed media or resized disk hda >> Seems like autofs isn't properly telling the kernel that media has >> changed. > > Is there something that I can do about that? I'd google that error message. >>> and >>> >>> Mar 24 12:19:53 niof kernel: [69532.316244] hda: command error: status=0x51 { DriveReady SeekComplete Error } >>> Mar 24 12:19:53 niof kernel: [69532.316256] hda: command error: error=0x50 { LastFailedSense=0x05 } >>> Mar 24 12:19:53 niof kernel: [69532.316262] hda: possibly failed opcode: 0xa0 >>> Mar 24 12:19:53 niof kernel: [69532.320570] end_request: I/O error, dev hda, sector 9144696 >>> Mar 24 12:19:53 niof kernel: [69532.320579] __ratelimit: 505 callbacks suppressed >>> Mar 24 12:19:53 niof kernel: [69532.320585] Buffer I/O error on device hda, logical block 1143087 >>> Mar 24 12:19:53 niof kernel: [69532.320596] Buffer I/O error on device hda, logical block 1143088 And those messages too. >>> Archive dvds I've burned and commercial dvds both load but then shortly >>> the monitor cyclying begins and I eject the disk as quickly as I can. >>> >>>> What kind of video do you have? On-board? >>> Yes. The Xorg.log shows: Device "KM4M-V on-board video" >> Which probably shares system RAM. I bet the busy system is somehow >> saturating the memory channel(s), thus causing the flickering. > > This problem is *very* recent. Currently htop shows 465/946MB of system > RAM and only 91/1906MB of swap having been used. > It's not the *amount* of RAM, it's the *throughput*. -- "History does not long entrust the care of freedom to the weak or the timid." Dwight Eisenhower -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BAA5362.6090708(a)cox.net
From: Ingo Kasten on 24 Mar 2010 15:20 Sorry for just putting in another thought, maybe I am wrong: During upgrade of the kernel and/or udev the devices are sometimes newly recognized. This makes udev create "new" devices , too. It doesn't matter as far the devices are mounted by uuid in fstab, but cdrom and dvd aren't mounted this way. So you might have a look at /etc/udev/rules.d/70-persistent-cd.rules . If there is listed more than one physical device with creating symlinks to more than one /dev/cdrom* you should rename that file and restart. Udev will create a new file with the correct symlinks, which your applications can deal with again. Can't explain it in a better way ;-) . Regards Ingo -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4baa5f10$0$7651$9b4e6d93(a)newsspool1.arcor-online.net
From: Rick Pasotto on 25 Mar 2010 12:00 On Wed, Mar 24, 2010 at 07:50:55PM +0100, Ingo Kasten wrote: > Sorry for just putting in another thought, maybe I am wrong: > > During upgrade of the kernel and/or udev the devices are sometimes newly > recognized. This makes udev create "new" devices , too. > It doesn't matter as far the devices are mounted by uuid in fstab, but > cdrom and dvd aren't mounted this way. > So you might have a look at /etc/udev/rules.d/70-persistent-cd.rules . > If there is listed more than one physical device with creating symlinks > to more than one /dev/cdrom* you should rename that file and restart. > Udev will create a new file with the correct symlinks, which your > applications can deal with again. Can't explain it in a better way > ;-) . OK. Did that and got a slightly different rules file. Initial testing was encouraging but that was just a delay in the onset of the monitor cycling. The grip help talks about making sure that IDE devices use SCSI emulation as the 2.4 kernels didn't support dma for IDE. Has that changed for the 2.6 kernels? Just checked the archives for the grip-users mailing list and saw a post saying that grip was no longer being maintained in debian. Further investigation led me to cdda2wav (for which grip is evidently a front end). Looks like I can use that directly from the command line without any problem so that will be what I will do. Thanks for your responses. -- "Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others." -- Edward Abbey Rick Pasotto rick(a)niof.net http://www.niof.net -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100325155911.GE9623(a)niof.net
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: Monitoring AutoFS in SNMP Next: rkhunter mails to root: should I worry? |