[alsa-devel] Backported sbxfi driver (UNTESTED!)

Takashi Iwai tiwai at suse.de
Thu Oct 23 23:30:14 CEST 2008


At Thu, 23 Oct 2008 18:32:19 +0100,
Jason Harvey wrote:
> 
> Takashi Iwai wrote:
> > At Thu, 23 Oct 2008 17:23:22 +0100,
> > Jason Harvey wrote:
> >   
> >> Takashi Iwai wrote:
> >>     
> >>> Fixed and uploaded now.
> >>> It might take some time until the changes are sync'ed.
> >>>   
> >>>       
> >> Thanks, downloaded, patched fine.
> >> Attached dmesg_modprobe.txt shows output before playing anything.
> >>
> >> No sound now using  the oss workaround "echo mplayer 0 0 direct > 
> >> /proc/asound/card0/pcm0p/oss"
> >> Mplayer starts but doesn't increment shows 0% 0seconds etc etc, it can 
> >> be interrupted ctrl-c, the PC remains functional, just no sound.
> >> dmesg_after.txt is the tail end of dmesg after interrupting mplayer, I 
> >> trimmed it as the first couple seven lines repeat for about 330K in the 
> >> original log :)
> >> Instant reboot when trying mplayer without the oss workaround.
> >>     
> >
> > OK, so the patch doesn't help, and it brings another problem.
> > What about debug=2?  This will give much less log, I guess.
> >   
> debug=2 is still too big to see the start of playback.
> If I can get the buffer big enough to find the beginning I'll post it :)

That'll be good.

> >> aplay -Dplug:dmix:0 wn.wav still works.
> >> Trying mplayer after aplay freezes the machine with no output onto the 
> >> console.
> >>     
> >
> > Even with OSS proc hack?
> >   
> Yes, if I aplay first it locks up entirely when I issue OSS proc hack 
> then run mplayer.
> Without running aplay I can get a dmesg but mplayer makes no sound.
> I've put the debug=1 output along with the commands etc below.

Just to be sure: is it the driver with my patch or without the patch?
The patch seems broken anyway, so abandon it, and check only without
the patch from now on.


thanks,

Takashi


More information about the Alsa-devel mailing list