public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: sb-400 audigy prob
Date: Sat, 11 Aug 2007 12:58:43 -0400	[thread overview]
Message-ID: <200708111258.43546.gene.heskett@gmail.com> (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

-- 
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...

             reply	other threads:[~2007-08-11 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11 16:58 Gene Heskett [this message]
2007-08-11 17:57 ` sb-400 audigy prob Alistair John Strachan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200708111258.43546.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox