Skip to contentSkip to conversation

sb-400 audigy prob

DISCUSSION Gene Heskett 2 participants 2 messages Aug 11, 2007

lore
Share & tools
lore
#0 lore raw

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@coyote 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

Signature · 6 lines
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...
#1 lore raw
Quoted 18 lines · 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-

Quoted 3 lines

But I have a line in my rc.local that reloads the sound fonts:
[root@coyote 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.

Quoted 15 lines

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.

Signature · 4 lines
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.