linux-kernel - 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-next>] [day] [month] [year] [list]

Message-Id: <200708111258.43546.gene.heskett@gmail.com>
Date:	Sat, 11 Aug 2007 12:58:43 -0400
From:	Gene Heskett <gene.heskett@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: sb-400 audigy prob

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

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.

Hints gratefully checked out here folks.

Thanks

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I don't wanna argue, and I don't wanna fight,
But there will definitely be a party tonight...
-
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/