Henry W. Peters wrote, on 11/03/11 14:50: > > > On 03/10/2011 06:09 PM, Giuliano Pochini wrote: >> >> The bug I told you was about volume control. This is a completely different >> thing. And this is strange because the listed hw params are fine. Did the >> kernel write anything interesting in the logs ? Try "dmesg" right after >> the failed aplay. >> >> >> > Hard to say if this is the whole of the output, as the 'dmesg' part was > cut off of it (i.e., at the top) by the terminal. But in any case, this > is what I got after doing the 'aplay' as you suggested. > > Regards, > Henry > > > > [ 770.072069] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 770.128291] ata4.00: configured for UDMA/100 > [ 770.129025] ata4: EH complete > [ 772.003253] ata4.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 > [ 772.003278] ata4: hard resetting link > [ 772.320073] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 772.376259] ata4.00: configured for UDMA/100 > [ 772.376975] ata4: EH complete [edit] This looks like a SATA cable problem, that can cause further problems if you are building software or installing packages. Shut down the pc including removing the power cord, take static electricity precautions (at a minimum ground your hands against metal parts of the pc case), then remove and re-seat the sata cable both at the the hard disk end and at the motherboard end. Arthur. ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
