SB400 AC'97 Sound Card
Frans
ketelaars at wanadoo.nl
Sat Aug 30 15:43:48 UTC 2008
On Sat, 30 Aug 2008 10:25:13 -0400, Keith Clark wrote:
> Frans wrote:
>> On Fri, 29 Aug 2008 14:45:57 -0400, Keith Clark wrote:
>>
>>
>>> Nigel Henry wrote:
>>>
>>>> On Friday 29 August 2008 18:53, Keith Clark wrote:
>>>>
>>>>
>>>>> How I get Ubuntu 8.04.1 to recognize my ATI SB400 AC'97 sound card?
>>>>>
>>>>> Keith
>>>>>
>>>>>
>>>>>
>>>> I don't know if I can help much, but perhaps you could provide the
>>>> output from the following commands.
>>>>
>>>> lspci -v
>>>> cat /proc/asound/cards
>>>> cat /proc/asound/version
>>>> lsmod | grep snd
>>>>
>>>> Sound is usually muted as default to protect your ears, and speakers,
>>>> so open a terminal (CLI), and as user type alsamixer. If the
>>>> soundcard has been detected, and set up, you should see a whole bunch
>>>> of mixer settings here.
>>>>
>>>> See the man page for alsamixer for useage.
>>>>
>>>> All the best.
>>>>
>>>> Nigel.
>>>>
>>>>
>>>>
>>> Ok Nigel, here you go:
>>>
>>> lspci -v:
>>>
>>>
>>>
>>
>>> 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400
>>> AC'97 Audio Controller (rev 02)
>>> Subsystem: Hewlett-Packard Company Unknown device 2a27 Flags: bus
>>> master, 66MHz, slow devsel, latency 64, IRQ 5 Memory at fe02a000
>>> (32-bit, non-prefetchable) [size=256] Capabilities: [40] Message
>>> Signalled Interrupts: Mask- 64bit-
>>> Queue=0/0 Enable-
>>>
>>>
>> Now please try the other commands and suggestions from Nigel :-)
>>
>> -Frans
>>
>>
>>
>>
> cat /proc/asound/cards
> cat /proc/asound/version
>
> Both of these commands result in No Such File or Directory
>
> lsmod | grep snd
>
> Results in nothing. No error, no result.
>
> alsamixer results in:
>
> alsamixer: function snd_ctl_open failed for default: No such file or
> directory
Thanks. Clearly there is no ALSA driver loaded. But your soundcard worked
before your "Grub boot confusion" problem, right?
I really don't know what's the matter, but you could always try "sudo
modprobe snd-atiixp" to try to load the driver manually, and then see if
the commands you used before now give different results.
Good luck!
-Frans
More information about the ubuntu-users
mailing list