linux-kernel - Re: sb-400 audigy prob

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200708111857.01355.alistair@devzero.co.uk>
Date:	Sat, 11 Aug 2007 18:57:01 +0100
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sb-400 audigy prob

On Saturday 11 August 2007 17:58:43 Gene Heskett wrote:
> Greetings;
>
> Running 23-rc2 since it came out, I've just discovered I have only the
> system beep for sound. From lspci:
> 01:08.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
>         Subsystem: Creative Labs Unknown device 1001
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32 (500ns min, 5000ns max)
>         Interrupt: pin A routed to IRQ 12
>         Region 0: I/O ports at c000 [size=64]
>         Capabilities: [dc] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> But I have a line in my rc.local that reloads the sound fonts:
> [root@...ote rulesdujour]# sfxload /usr/music/SoundFonts/CT4MGM.SF2
> No AWE synth device is found

I'm not 100% sure, but (at least) Debian has two programs "sfxload" 
and "asfxload", which work with OSS and ALSA respectively. I've found that 
both can work, but the former will only work with OSS emulation loaded. If 
you have an "asfxload", I would try it instead.

> This occurred once before and a reboot fixed it, so I'm going to try it
> again. BRB
>
> About 4 reboots later, it finally works again, after it had hung in udev,
> and apparently did an auto reboot while I was looking for my flashlight.  I
> had selected in that case to boot to 2.6.22-rt9 since 2.6.23-rc1 didn't
> work either and udev had hung after spitting out that useless screenfull of
> missing attributes messages like it always does, (when do we get rid of
> that?) and it had been hung in udev for about 3 minutes before I got up and
> left to find my flashlight.  On arrival with light in hand, I found the
> same screenfull of udev messages and assumed it was still hung, but as I
> was crawling under the desk I heard the speakers thump like they do when
> udev finds the device, and the boot continued.  I didn't realize it had
> spontainiously rebooted till I saw the login message said 2.6.23-rc2, the
> grub default.

Not that it explains any of this, of course. I hope you can reproduce it.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/