[gentoo-user] sound driver

[gentoo-user] sound driver

[James]

Hello,

I've got a clevo portable runing a 2.6.9-r4 kernel. Upon boot, I get this
popup (kde) message:

X Informational - artsmessage 

Source server information message:
Error while initialzing the sound driver:
Device: default can be opened for playback (no such file or directory)
The sound server will continue, using the null output device.


What did I miss, in the kernel? something in kde configs/desktop setting?

Alsa, Jack and a host of audio software is installed but nothing works. I
can get kscd to play a cd, it reads the name of the song, says it's at 
40% percent volume, but no sound. I'm not certain I've activated everything
in the kernel.

lspci -v shows:

0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound
Controller (rev a0)
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0402
        Flags: bus master, medium devsel, latency 173, IRQ 5
        I/O ports at 1c00
        I/O ports at 1800 [size=128]
        Capabilities: [48] Power Management version 2


Any ideas are most welcome.....

James


--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[james]

> I've got a clevo portable runing a 2.6.9-r4 kernel. Upon boot, I get this
> popup (kde) message:
> 
> X Informational - artsmessage 
> Source server information message:
> Error while initialzing the sound driver:
> Device: default can be opened for playback (no such file or directory)
> The sound server will continue, using the null output device.

Well I managed to clear up this message, by changing the permissions
on /mnt/cdrom to 777....

But I still get no sound. I can control the cdrom via KsCD, even ejecting
the cdrom, but no sound, regardless of what cdplayer app I use.

James


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Glenn Enright]

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

On Sun, 05 Dec 2004 16:02, james wrote:
> > I've got a clevo portable runing a 2.6.9-r4 kernel. Upon boot, I get this
> > popup (kde) message:
> >
> > X Informational - artsmessage
> > Source server information message:
> > Error while initialzing the sound driver:
> > Device: default can be opened for playback (no such file or directory)
> > The sound server will continue, using the null output device.
>
> Well I managed to clear up this message, by changing the permissions
> on /mnt/cdrom to 777....
>
> But I still get no sound. I can control the cdrom via KsCD, even ejecting
> the cdrom, but no sound, regardless of what cdplayer app I use.
>
> James
>
>
Ok. Sounds like you are on the right track... 

1. has the system had sound working before? (Perhaps under a different 
kernel?) Then check to see if you have the right kernel modules loaded. This 
seems unlikely because your programs aparently think its all go.

2. Run Kmix and make sure your sound levels are NOT zero.

3. The kde sound server is enabled in Control Center under Sound & 
Multimedia/System Sound. Make sure the server is started. If you are able to 
get sound from the test button, but system sounds still wont work look for 
knotifyrc under you homedir in ~/.kde/share/config, and change the 'UseArts' 
Feild to true, then back to the sound server to restart it. This is a known 
bug in kde bugzilla. which I suffered from :p. (NB sometimes if you do 
strange things it will reset itself to False. you will have to manually fix 
it again.)

No luck? Try logging out and back in after changes? Hows that?

-- 

I understand why you're confused.  You're thinking too much.
  -- Carole Wallach.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: sound driver

[James]

> Glenn Enright <elinar <at> ihug.co.nz> writes:
> Ok. Sounds like you are on the right track... 
> 
> 1. has the system had sound working before? (Perhaps under a different 
> kernel?) Then check to see if you have the right kernel modules loaded. This 
> seems unlikely because your programs aparently think its all go.
No, have never gotten sound working under gentoo(only linux tried) on this
new portable.

> 
> 2. Run Kmix and make sure your sound levels are NOT zero.

yes it about midspan....seems ok.
> 
> 3. The kde sound server is enabled in Control Center under Sound & 
> Multimedia/System Sound. Make sure the server is started. 

Enable sound system is selected, but the 'test button' does nothing.

> If you are able to 
> get sound from the test button, but system sounds still wont work look for 
> knotifyrc under you homedir in ~/.kde/share/config, and change the 'UseArts' 
> Feild to true, 

[Misc]
LastConfiguredApp=Atlantik

[StartProgress]
Arts Init=true
KNotify Init=true
Use Arts=true


> then back to the sound server to restart it. This is a known 

Not sure how to restart it... So I'll just exit the session and 
log back in?


> bug in kde bugzilla. which I suffered from :p. (NB sometimes if you do 
> strange things it will reset itself to False. you will have to manually fix 
> it again.)
> 
> No luck? Try logging out and back in after changes? Hows that?
> 





--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[james]

Glenn Enright <elinar <at> ihug.co.nz> writes:

> No luck? Try logging out and back in after changes? Hows that?
> 

Well I tried everything, and logged out, rebooted and loggeb back in
still no sound. Everything appears to work, just no sound....

james



--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Glenn Enright]

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

On Sun, 05 Dec 2004 18:31, james wrote:
> Glenn Enright <elinar <at> ihug.co.nz> writes:
> > No luck? Try logging out and back in after changes? Hows that?
>
> Well I tried everything, and logged out, rebooted and loggeb back in
> still no sound. Everything appears to work, just no sound....
>
> james
>
>
>
> --
> gentoo-user@gentoo.org mailing list
can you post the result of 'lsmod' please and describe your sound hardware?
-- 

Dying is a very dull, dreary affair.  My advice to you is to have
nothing whatever to do with it.
  -- W. Somerset Maughm, his last words

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: sound driver

[Glenn Enright]

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

On Sun, 05 Dec 2004 19:21, Glenn Enright wrote:
> On Sun, 05 Dec 2004 18:31, james wrote:
> > Glenn Enright <elinar <at> ihug.co.nz> writes:
> > > No luck? Try logging out and back in after changes? Hows that?
> >
> > Well I tried everything, and logged out, rebooted and loggeb back in
> > still no sound. Everything appears to work, just no sound....
> >
> > james
> >
> >
> >
> > --
> > gentoo-user@gentoo.org mailing list
>
> can you post the result of 'lsmod' please and describe your sound hardware
duh just rereead your first post :) just the lsmod please

if you type 'dmesg | less' on the command prompt you should see some reference 
to the SIS sound driver loading? if there are error messages, what are they?

-- 

Tagline, you're it!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: sound driver

[james]

> Glenn Enright <elinar <at> ihug.co.nz> writes:

> > can you post the result of 'lsmod' please and describe your sound hardware
nothing, I guess this is bad?
<snip>
lsmod
Module                  Size  Used by


Also, googling reveales some similar problems with 2.4 kernels, where
/etc/modules.conf was inadequte. I not sure this is related

> if you type 'dmesg | less' on the command prompt you should see some reference 
> to the SIS sound driver loading? if there are error messages, what are they?

grep sis:

sisfb: Options <NULL>
i2c-sis96x version 1.0.0
sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x8100

grep SiS:

ACPI: FADT (v001 SiS    M650     0x06040000 PTL  0x000f4240) @ 0x3fdfaf8c
Enabling SiS 96x SMBus.
agpgart: Detected SiS 646 chipset
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ehci_hcd 0000:00:03.3: Silicon Integrated Systems [SiS] USB 2.0 Controller
ohci_hcd 0000:00:03.0: Silicon Integrated Systems [SiS] USB 1.0 Controller
ohci_hcd 0000:00:03.1: Silicon Integrated Systems [SiS] USB 1.0 Controller (#2)
ohci_hcd 0000:00:03.2: Silicon Integrated Systems [SiS] USB 1.0 Controller (#3)
sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x8100
  #2: SiS SI7012 at 0x1c00, irq 5
  #3: SiS SI7013 Modem at 0x1400, irq 5

grep SIS:
Uncovering SIS962 that hid as a SIS503 (compatible=1)
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller

grep sound:
<is empty>

grep Sound:
Advanced Linux Sound Architecture Driver Version 1.0.6 (Sun Aug 15 07:17:53 2004
UTC).






--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Glenn Enright]

[-- Attachment #1: Type: text/plain, Size: 2679 bytes --]

On Tue, 07 Dec 2004 02:29, james wrote:
> > Glenn Enright <elinar <at> ihug.co.nz> writes:
> > > can you post the result of 'lsmod' please and describe your sound
> > > hardware
>
> grep sound:
> <is empty>
>
<warning: long message>

Right. Looks like there is no sound support in your kernel. We can fix 
that :). There are two options. Recompile your otherwise perfectly good 
kernel and choose the alsa modules you need (can be guess work sometimes :p. 
Or alternatively emerge -avD alsa-drivers, which will have the latest version 
of all the sound support you need. Note that this is equivaslent to a lot of 
the stuff you find in the alsa howto on their site.

I suggest you try the latter and if that works you can unmerge it and fiddle 
around to get the kernel modules correct whenever you feel like it ;). You 
may find the emerge pulls in some other stuff. Just make a note of what it is 
and any instructions that may be given. Since you already have alsasound in 
your runlevel then that done.

Go to /etc/modules.d and edit the file alsa. Once youve finished it should 
look something like the following. The <<< are my addition. Look at them :)

# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore

##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
##  ALSA portion
alias snd-card-0 snd-intel8x0                 <<<< This is where you specify
                                              <<<< the correct module for your
                                              <<<< sound hardware. Look in the 
                                              <<<< /lib/modules/<kernelversion>
                                              <<<< under kernel/drivers for 
                                              <<<< options.
## alias snd-card-1 snd-ens1371
##  OSS/Free portion
alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1


# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
##  OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss


alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=1

-- 

BOFH Excuse #20:

divide-by-zero error

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: sound driver

[james]

> Glenn Enright <elinar <at> ihug.co.nz> writes:

> can you post the result of 'lsmod' please and describe your sound hardware?


lspci -v reveals:
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound
Controller (rev a0)
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0402
        Flags: bus master, medium devsel, latency 173, IRQ 5
        I/O ports at 1c00
        I/O ports at 1800 [size=128]
        Capabilities: [48] Power Management version 2





--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Christoph Eckert]

> X Informational - artsmessage
>
> Source server information message:
> Error while initialzing the sound driver:
> Device: default can be opened for playback (no such file or
> directory) The sound server will continue, using the null
> output device.

Have you ever configured sound?

If not, as root, do the following:

* alsaconf
* /etc/init.d/alsasound start
* Log out and back in again: Is there sound?

If so, do a

rc-update add boot alsasound


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Mike Noble]

Christoph Eckert wrote:
>>X Informational - artsmessage
>>
>>Source server information message:
>>Error while initialzing the sound driver:
>>Device: default can be opened for playback (no such file or
>>directory) The sound server will continue, using the null
>>output device.
> 
> 
> Have you ever configured sound?
> 
> If not, as root, do the following:
> 
> * alsaconf
> * /etc/init.d/alsasound start
> * Log out and back in again: Is there sound?
> 
> If so, do a
> 
> rc-update add boot alsasound
> 
> 
>  Best regards
> 
> 
>     ce
> 
> --
> gentoo-user@gentoo.org mailing list

Also make user that you have the volume turned up with your favorite
mixer (I use kmix).  By default many times this is turned down.

Mike

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Dave Erickson]

On Sun, 2004-12-05 at 08:55 -0800, Mike Noble wrote:
> Christoph Eckert wrote:
> >>X Informational - artsmessage
> 
> Also make user that you have the volume turned up with your favorite
> mixer (I use kmix).  By default many times this is turned down.
> 
> Mike

Indeed! On my systems, PCM 1 is always muted after a reboot.

-- 
Dave Erickson <linuser@esox.us>


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Christoph Eckert]

Am Sonntag 05 Dezember 2004 18:21 schrieb Dave Erickson:

> Indeed! On my systems, PCM 1 is always muted after a
> reboot.

On mine, *everything* is muted after reboot.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Bastian Balthazar Bux]

Christoph Eckert wrote:

>Am Sonntag 05 Dezember 2004 18:21 schrieb Dave Erickson:
>
>  
>
>>Indeed! On my systems, PCM 1 is always muted after a
>>reboot.
>>    
>>
>
>On mine, *everything* is muted after reboot.
>
>
> Best regards
>
>
>    ce
>
>--
>gentoo-user@gentoo.org mailing list
>
>
>  
>
the ones that save alsa mixer settings is:
/etc/init.d/alsasound  stop

hope it help

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Christoph Eckert]

> the ones that save alsa mixer settings is:
> /etc/init.d/alsasound  stop

This script call alsactl store and during boot alsactl 
restore.

Confisung: As soon as I call these two commands manually, it 
works. But it doesn't work during boot process.

Anyway, I have some more problems with audio stuff, and this 
is one of the minor things ;-) .

Thanks a lot anyway.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Kathy Wills]

Christoph Eckert wrote:

>
>
>On mine, *everything* is muted after reboot.
>
>  
>
To have sound when I reboot, I have the following in my 
/etc/conf.d/local.start file:

/usr/sbin/alsactl restore

Kathy


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Nick Rout]

On Sun, 05 Dec 2004 21:49:06 -0600
Kathy Wills <kathywills@brannanorwills.com> wrote:

> Christoph Eckert wrote:
> 
> >
> >
> >On mine, *everything* is muted after reboot.
> >
> >  
> >
> To have sound when I reboot, I have the following in my 
> /etc/conf.d/local.start file:
> 
> /usr/sbin/alsactl restore
> 
> Kathy

the alsasound service saves and restores your mixer controls.

(well it depends on a setting in /etc/conf.d/alsasound)


> 
> 
> --
> gentoo-user@gentoo.org mailing list

-- 
Nick Rout <nick@rout.co.nz>


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Kathy Wills]

Nick Rout wrote:

>On Sun, 05 Dec 2004 21:49:06 -0600
>Kathy Wills <kathywills@brannanorwills.com> wrote:
>
>  
>
>>Christoph Eckert wrote:
>>
>>    
>>
>>>On mine, *everything* is muted after reboot.
>>>
>>> 
>>>
>>>      
>>>
>>To have sound when I reboot, I have the following in my 
>>/etc/conf.d/local.start file:
>>
>>/usr/sbin/alsactl restore
>>
>>Kathy
>>    
>>
>
>the alsasound service saves and restores your mixer controls.
>
>(well it depends on a setting in /etc/conf.d/alsasound)
>
>
>  
>
I'm using a pure udev system. I had to put the above in the local.start 
file in order for the sound not to be muted on a reboot.

-- 
Kathy Wills

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Genealogy Web Site: http://www.brannanorwills.com               +
+                                                                   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Nick Rout]

On Sun, 05 Dec 2004 22:07:53 -0600
Kathy Wills <kathywills@brannanorwills.com> wrote:

> >
> >the alsasound service saves and restores your mixer controls.
> >
> >(well it depends on a setting in /etc/conf.d/alsasound)
> >
> >
> >  
> >
> I'm using a pure udev system. I had to put the above in the local.start 
> file in order for the sound not to be muted on a reboot.
> 
> -- 
> Kathy Wills


Interesting, I wonder why?

is alsasound in your boot runlevel?


-- 
Nick Rout <nick@rout.co.nz>


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Kathy Wills]

Nick Rout wrote:

>
>is alsasound in your boot runlevel?
>
>
>  
>
Yes, it is and has been ever since I started using alsa.

-- 
Kathy Wills

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Genealogy Web Site: http://www.brannanorwills.com               +
+                                                                   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Holly Bostick]

Kathy Wills wrote:
> Nick Rout wrote:
> 
>>
>> is alsasound in your boot runlevel?
>>
>>
>>  
>>
> Yes, it is and has been ever since I started using alsa.
> 
Now, weirdly, I am also running a pure udev system, and I do not have 
this problem (of muted sound), but to get that, rather than using 
/etc/conf.d/local.start, I have alsasound in both boot and default 
runlevels.

That's the only way it seems to work right (possibly because I 
modularize many of the various alsa components, so they aren't actually 
loaded when/if alsasound runs at the boot level).

Dunno, but I must say I prefer that to using /etc/conf.d/local.start.

HTH,

Holly

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Kathy Wills]

Holly Bostick wrote:

> Now, weirdly, I am also running a pure udev system, and I do not have 
> this problem (of muted sound), but to get that, rather than using 
> /etc/conf.d/local.start, I have alsasound in both boot and default 
> runlevels.
>
> That's the only way it seems to work right (possibly because I 
> modularize many of the various alsa components, so they aren't 
> actually loaded when/if alsasound runs at the boot level).
>
> Dunno, but I must say I prefer that to using /etc/conf.d/local.start.
>
> HTH,
>
> Holly

Thanks, I'll have to try that to. Did you just add rc-update alsasound 
default along with the alsasound boot to get it working like this?

-- 
Kathy Wills

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Genealogy Web Site: http://www.brannanorwills.com               +
+                                                                   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Holly Bostick]

Kathy Wills wrote:
> Holly Bostick wrote:
> 
>> Now, weirdly, I am also running a pure udev system, and I do not have 
>> this problem (of muted sound), but to get that, rather than using 
>> /etc/conf.d/local.start, I have alsasound in both boot and default 
>> runlevels.
>>
>> That's the only way it seems to work right (possibly because I 
>> modularize many of the various alsa components, so they aren't 
>> actually loaded when/if alsasound runs at the boot level).
>>
>> Dunno, but I must say I prefer that to using /etc/conf.d/local.start.
>>
>> HTH,
>>
>> Holly
> 
> 
> Thanks, I'll have to try that to. Did you just add rc-update alsasound 
> default along with the alsasound boot to get it working like this?
> 

Well, yes. There isn't actually a limit as to how many runlevels you can 
set using rc-update add, it would seem; I noticed that when I did an 
rc-update show and realized that "local" appears in two runlevels 
(default and nonetwork). So you can just do an rc-update add alsasound 
boot default and add it to both, if it's not currently enabled (if it's 
already in one of the runlevels you attempt to add, you will of course 
get a failure to add it to that runlevel).

I actually did this originally by accident, I think-- I had first 
installed alsasound to boot like it says to do, and then later I thought 
something was wrong (I had messed around with modularizing the drivers 
or something), and didn't do an rc-update show first (or didn't see 
alsasound, if I did). I couldn't remember which runlevel it was 
"supposed" to be in, so I installed it to default, which went fine, as 
it was not installed to the default runlevel at that time. So there it 
was in both, and (except for my current snd-seq-oss problem, which I 
think I know how to fix), I've never had any problems with it the way 
you would expect if it was "wrong" to do-- no errors that I've noticed 
in either run; certainly no errors in the 'default' run (where you would 
think to see them).

I do think that this works because some ALSA modules really prefer to be 
modules under udev, but some flatly cannot-- for example, snd-seq-oss 
cannot be a module (despite what the Help says), but snd-seq (on which 
snd-seq-oss depends), can. So some parts of a complete ALSA install 
cannot be put in /etc/modules.autoload.d/kernel-2.6, where udev prefers 
to have them (because statically compiled modues are loaded before udev 
is running, so it can't create devices for them).

So the first run loads the forced static compiles, and the second run 
loads the modules.

That's my theory, anyway ;-) .

Holly

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Tero Grundström]

On Mon, 6 Dec 2004, Holly Bostick wrote:

> I do think that this works because some ALSA modules really prefer to be
> modules under udev, but some flatly cannot-- for example, snd-seq-oss
> cannot be a module (despite what the Help says), but snd-seq (on which
> snd-seq-oss depends), can. So some parts of a complete ALSA install
> cannot be put in /etc/modules.autoload.d/kernel-2.6, where udev prefers
> to have them (because statically compiled modues are loaded before udev
> is running, so it can't create devices for them).
>
> So the first run loads the forced static compiles, and the second run
> loads the modules.

FYI,

I've had alsa compiled 100% static in kernel - worked perfectly.

I now have:

- alsa compiled 100% as modules
- nothing in /etc/modules.autoload.d/kernel-2.6
- alsasound added only to bootlevel

Works perfectly.

--
T.G.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Holly Bostick]

Tero Grundström wrote:
> On Mon, 6 Dec 2004, Holly Bostick wrote:
> 
> 
>>I do think that this works because some ALSA modules really prefer to be
>>modules under udev, but some flatly cannot-- for example, snd-seq-oss
>>cannot be a module (despite what the Help says), but snd-seq (on which
>>snd-seq-oss depends), can. So some parts of a complete ALSA install
>>cannot be put in /etc/modules.autoload.d/kernel-2.6, where udev prefers
>>to have them (because statically compiled modues are loaded before udev
>>is running, so it can't create devices for them).
>>
>>So the first run loads the forced static compiles, and the second run
>>loads the modules.
> 
> 
> FYI,
> 
> I've had alsa compiled 100% static in kernel - worked perfectly.
> 
> I now have:
> 
> - alsa compiled 100% as modules
> - nothing in /etc/modules.autoload.d/kernel-2.6
> - alsasound added only to bootlevel
> 
> Works perfectly.
> 
  Yes, of course you have, Tero-- you seem to be one of the fortunate 
few whose computer always works as advertised, under all conditions.

You lucky dog, you ;-) .

Holly


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Tero Grundström]

On Mon, 6 Dec 2004, Holly Bostick wrote:

> > FYI,
> >
> > I've had alsa compiled 100% static in kernel - worked perfectly.
> >
> > I now have:
> >
> > - alsa compiled 100% as modules
> > - nothing in /etc/modules.autoload.d/kernel-2.6
> > - alsasound added only to bootlevel
> >
> > Works perfectly.
> >
>   Yes, of course you have, Tero-- you seem to be one of the fortunate
> few whose computer always works as advertised, under all conditions.
>
> You lucky dog, you ;-) .

Well, don't know about that... I've also had problems with alsa with
some old udev versions. Thats why I compiled alsa static in the kernel
at one point.

However I really feel that your way of setting up alsa is overly
complicated. And that will only confuse people, especially newbies.
IMO, there must be something else wrong with the setup.

BTW, when was the last time you actually tried to setup alsa the simple
way, as instructed in the docs?


--
T.G.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Holly Bostick]

Tero Grundström wrote:
> On Mon, 6 Dec 2004, Holly Bostick wrote:
> 
> 
>>>FYI,
>>>
>>>I've had alsa compiled 100% static in kernel - worked perfectly.
>>>
>>>I now have:
>>>
>>>- alsa compiled 100% as modules
>>>- nothing in /etc/modules.autoload.d/kernel-2.6
>>>- alsasound added only to bootlevel
>>>
>>>Works perfectly.
>>>
>>
>>  Yes, of course you have, Tero-- you seem to be one of the fortunate
>>few whose computer always works as advertised, under all conditions.
>>
>>You lucky dog, you ;-) .
> 
> 
> Well, don't know about that... I've also had problems with alsa with
> some old udev versions. Thats why I compiled alsa static in the kernel
> at one point.
> 
> However I really feel that your way of setting up alsa is overly
> complicated. And that will only confuse people, especially newbies.
> IMO, there must be something else wrong with the setup.
> 
> BTW, when was the last time you actually tried to setup alsa the simple
> way, as instructed in the docs?
> 

You've got me; this setup was hacked together under an old udev version, 
where compiling all the modules statically simply did not work for me, 
and I have updated udev about 3 times since then.

But I didn't mean to imply my workaround was anything but that, nor that 
the problem I had been working around still existed. I don't know, to be 
honest. I've been too busy hotfixing PAM/login/DISPLAY issues, 
reconfiguring my system to use KDE programs because GNOME/CORBA/gconf 
broke out of the blue for reasons unknown, and I'm trying to bail the 
boat and avoid a complete reinstall (which would be even more of a pain 
than all the emerge -e s and emerge --newuse s that I've been doing for 
the past two weeks, but it's getting to be a photo finish in terms of 
which strategy is more tedious at this point). Atm, I'm just glad that I 
have sound, given the general instability I've got going on, and 
checking to see if alsasound would continue to work if I did it "right" 
is just not high on my list of priorities right now. So I've left it as 
it was.

But you probably are correct that I could now configure alsasound 
"properly" and it would continue to work. I just changed some kernel 
modules anyway and recompiled, so I might as well fix alsasound too 
before I reboot (got the end of an emerge -e gnome-light going; 2 
packages left, so it will be a bit before I reboot).  So thanks for 
reminding me ;-) .

Holly


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Peter Ruskin]

On Monday 06 December 2004 13:53, Holly Bostick wrote:
> So there it
> was in both, and (except for my current snd-seq-oss problem,
> which I think I know how to fix), I've never had any problems
> with it the way you would expect if it was "wrong" to do-- no
> errors that I've noticed in either run; certainly no errors in
> the 'default' run (where you would think to see them).
>
> I do think that this works because some ALSA modules really
> prefer to be modules under udev, but some flatly cannot-- for
> example, snd-seq-oss cannot be a module (despite what the Help
> says), but snd-seq (on which snd-seq-oss depends), can.

Hi Holly,

Have you looked at this?
http://bugs.gentoo.org/show_bug.cgi?id=72099

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.51-r3. kernel-2.6.9-gentoo-r9.
i686 AMD Athlon(tm) XP 3200+.  gcc(GCC): 3.3.4.
KDE: 3.3.1.    Qt: 3.3.3.
========================================================================

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Holly Bostick]

Peter Ruskin wrote:
> On Monday 06 December 2004 13:53, Holly Bostick wrote:
> 
>>So there it
>>was in both, and (except for my current snd-seq-oss problem,
>>which I think I know how to fix), I've never had any problems
>>with it the way you would expect if it was "wrong" to do-- no
>>errors that I've noticed in either run; certainly no errors in
>>the 'default' run (where you would think to see them).
>>
>>I do think that this works because some ALSA modules really
>>prefer to be modules under udev, but some flatly cannot-- for
>>example, snd-seq-oss cannot be a module (despite what the Help
>>says), but snd-seq (on which snd-seq-oss depends), can.
> 
> 
> Hi Holly,
> 
> Have you looked at this?
> http://bugs.gentoo.org/show_bug.cgi?id=72099
> 

Thanks, Peter-- I knew there was something going on with snd-seq-oss, 
but couldn't remember what.

I actually haven't upgraded module-init-tools for that reason, but I 
still get a message that the sequencer module fails to load during boot. 
System boots otherwise fine, but not having a sequencer, or kinda half 
having one makes things yet a bit more flaky on my system (and my system 
is truly flakey enough atm without this as well).

But I appreciate being reminded of the details of that particular 
circumstance. I'm having a bit of trouble atm keeping track of all the 
broken things and why.  I side with the guy who said his computer hates 
him and he was going to take it out and shoot it.... everything was 
going just fine before it took one step too far ;-( ... and left no 
footprints....

Holly

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] sound driver

[Christoph Eckert]

> the alsasound service saves and restores your mixer
> controls.

Yeah, I find:

cat /etc/init.d/alsasound | grep alsactl
# This script requires /usr/sbin/alsactl and /usr/bin/aconnect 
programs
alsactl=/usr/sbin/alsactl
        elif [ -x $alsactl ]; then
                        $alsactl -f $asoundcfg restore 
${CARDNUM}
                eerror -e "ERROR: Cannot find alsactl, did you 
forget to install media-sound/alsa-utils?"
        if [ -x $alsactl ]; then
                $alsactl -f $asoundcfg store
                eerror -e "ERROR: Cannot find alsactl, did you 
forget to install media-sound/alsa-utils?"

so I guess it should work, but it doesn't.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[james]

Mike Noble <mgnoble <at> cox.net> writes:

> Also make user that you have the volume turned up with your favorite
> mixer (I use kmix).  By default many times this is turned down.

Everytime I lauch kmix, is shows the volume, midspan (50%) so I do not think
this is the problem. Besides I ajust the level all the way to 100%
and get no sound. 

James


--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

> Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:

> Have you ever configured sound?
> If not, as root, do the following:
>
> * alsaconf
It complains:
"No supported PnP or PCI crd found.
Would you like to proble legacy ISA sound cards/chips?"

"No legacy drivers are available"


> * /etc/init.d/alsasound start
> * Log out and back in again: Is there sound?
<snip>
* Loading ALSA drivers...                                                [ ok ]
 * Restoring Mixer Levels
 * No mixer config in /etc/asound.state, you have to unmute your card!    [ ok ]
<snip>

>  If so, do a
> rc-update add boot alsasound
rc-update add boot alsasound
 * /sbin/rc-update: /etc/init.d/boot not found; aborting.





--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Holly Bostick]

James wrote:
>>Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:
> 
> 
>>Have you ever configured sound?
>>If not, as root, do the following:
>>
>>* alsaconf
> 
> It complains:
> "No supported PnP or PCI crd found.
> Would you like to proble legacy ISA sound cards/chips?"
> 
> "No legacy drivers are available"

The drivers for your sound card are not loaded.
> 
> 
> 
>>* /etc/init.d/alsasound start
>>* Log out and back in again: Is there sound?
> 
> <snip>
> * Loading ALSA drivers...                                                [ ok ]
>  * Restoring Mixer Levels
>  * No mixer config in /etc/asound.state, you have to unmute your card!    [ ok ]
> <snip>

This would be handled by alsaconf, or manually by you in alsamixer, but 
your card is not found or loaded so naturally alsasound has nothing to 
work with.

> 
>> If so, do a
>>rc-update add boot alsasound
> 
> rc-update add boot alsasound
>  * /sbin/rc-update: /etc/init.d/boot not found; aborting.

This last instruction was incorrectly formed; the syntax is

rc-update <action> <service> <runlevel>

So it should have been

rc-update add alsasound boot

but that won't help if alsaconf has not succeeded in finding your sound 
card in the first place.

Have you modprobed the appropriate modules for your motherboard and/or 
sound card before attempting to run alsaconf?

Holly

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Holly Bostick <motub <at> planet.nl> writes:

> > <snip>
> > * Loading ALSA drivers...                                                
[ ok ]
> >  * Restoring Mixer Levels
> >  * No mixer config in /etc/asound.state, you have to unmute your card!    
[ ok ]
> > <snip>
> 
> This would be handled by alsaconf, or manually by you in alsamixer, but 
> your card is not found or loaded so naturally alsasound has nothing to 
> work with.
>
agreed! what now?

> Have you modprobed the appropriate modules for your motherboard and/or 
> sound card before attempting to run alsaconf?

Well, bear with me, as we're covering 'new turf', here's what I found:

lspci -v shows:
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound
Controller (rev a0)
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0402
        Flags: bus master, medium devsel, latency 173, IRQ 5
        I/O ports at 1c00
        I/O ports at 1800 [size=128]
        Capabilities: [48] Power Management version 2



lsmod
Module                  Size  Used by
<so it's empty>


modprobe -c | grep sis reveals:
alias pci:v00001039d00000180sv*sd*bc*sc*i* sata_sis
alias pci:v00001039d00000181sv*sd*bc*sc*i* sata_sis

modprobe -c | grep snd reveals:
alias char-major-116-* snd
alias sound-slot-0 snd-via82xx
alias snd-card-0 snd-via82xx
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
options snd cards_limit=1

modprobe -c | grep bt
alias bt-proto-0 l2cap
alias bt-proto-2 sco
alias bt-proto-3 rfcomm
alias bt-proto-4 bnep
alias char-major-81-* bttv


Obviously, I do not really know how to use modprobe, robustly....
so flames are OK....

I could easily have something buggered up in the kernel, or
completely missing too....
James






--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Christoph Eckert]

> I could easily have something buggered up in the kernel, or
> completely missing too....

So a check for ALSA in the kernel should be the next step. The 
ALSA utils can do nothing as long there's no ALSA support in 
the kernel.

But maybe your chip isn't supported by ALSA?

Check your kernel config, build and install it anew and run 
ALSAconf. If it fails then, you'd like to disable ALSA in the 
kernel and chack out OSS support instead.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:


> > I could easily have something buggered up in the kernel, or
> > completely missing too....
> So a check for ALSA in the kernel should be the next step. The 
> ALSA utils can do nothing as long there's no ALSA support in 
> the kernel.
Alsa is in the kernel....

> But maybe your chip isn't supported by ALSA?
Nor in OSS. SiS (Silicon Integrated Systems audio chips do not
seem to be support, at least with kernel selection.

> Check your kernel config, build and install it anew and run 
> ALSAconf. If it fails then, you'd like to disable ALSA in the 
> kernel and chack out OSS support instead.

alsaconf runs, it just fails to find anything......

I'm beginning to think there is no support for SiS audio chips:
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] 
Sound Controller (rev a0)
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0402
        Flags: bus master, medium devsel, latency 173, IRQ 5
        I/O ports at 1c00
        I/O ports at 1800 [size=128]
        Capabilities: [48] Power Management version 2


James




--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Christoph Eckert]

> I'm beginning to think there is no support for SiS audio
> chips:

Maybe; there still devices ALSA cannot handle. May also be 
that there are no specs for the device, so a driver cannot be 
written.

Chack the ALSA project page, perhaps there are some hints.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

> Chack the ALSA project page, perhaps there are some hints.

Excellent idea! This looks promising, but, I'm a little confused how to proceed:

http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=
SiS&card=SiS+735.&chip=SI7012&module=intel8x0

Seems to indicate the driver choice:
 Device Drivers  --->    
Sound  --->  
<M> Sound card support                      
       Advanced Linux Sound Architecture  --->     
          PCI devices  --->
<M> Intel i8x0/MX440, SiS 7012; Ali 5455; NForce Audio; AMD768/8111

is the chipset and it is supported, as dmesg reveals:
#2: SiS SI7012 at 0x1c00, irq 5

The web page also says:

Most modern distros come with soundcore compiled as a module. You can check 
this in numerous ways. The easiest way is to type.

        modinfo soundcore

If this command returns that you have this module, then you don't need to
recompile your kernel.

When I run this command  'modinfo soundcore, I get:
modinfo soundcore
description:    Core sound module
author:         Alan Cox
license:        GPL
alias:          char-major-14-*
vermagic:       2.6.9-gentoo-r4 SMP preempt PENTIUM4 gcc-3.3
depends:

But how to make it work now?


James




--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Holly Bostick]

James wrote:
> Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:
> 
> 
> 
>>>I could easily have something buggered up in the kernel, or
>>>completely missing too....
>>
>>So a check for ALSA in the kernel should be the next step. The 
>>ALSA utils can do nothing as long there's no ALSA support in 
>>the kernel.
> 
> Alsa is in the kernel....
> 
> 
>>But maybe your chip isn't supported by ALSA?
> 
> Nor in OSS. SiS (Silicon Integrated Systems audio chips do not
> seem to be support, at least with kernel selection.

Yes they are---

ALSA:

CONFIG_SND_INTEL8X0: 
 

 
 

     Say Y here to include support for the integrated AC97 sound 
 

     device on motherboards with Intel/SiS/nVidia/AMD chipsets, or 
 

     ALi chipsets using the M5455 Audio Controller.  (There is a 
 

     separate driver for ALi M5451 Audio Controllers.) 
 

 
 

     To compile this driver as a module, choose M here: the module 
 

     will be called snd-intel8x0. 
 

 
 


OSS:

  CONFIG_SOUND_TRIDENT: 
 

 
 

     Say Y or M if you have a PCI sound card utilizing the Trident 
 

     4DWave-DX/NX chipset or your mother board chipset has SiS 7018 
 

     or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded 
 

     in SiS960 Super South Bridge and SiS540/630 Single Chipset. 
 

     The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D, 
 

     M1535+ or M1535D+ South Bridge. 
 

 
 

     Use lspci -n to find out if your sound card or chipset uses 
 

     Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands 
 

     for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID 
 

     10B9:5451 stands for ALi5451. 
 

 
 

This is kernel 2.6.10-rc2-bk7, and alsa-driver-1.0.7

So you probably want to dig out your mobo manual and see if you can get 
more information on just what chipset is at work here.

Maybe you're just using the wrong drivers.

You might also want to check if you've enabled the I2C bus for your mobo 
chipset-- I'm not quite sure what it is, but if the kernel has gone to 
so much trouble to include some special support for my mobo's particular 
version of it in the kernel, I figure I should enable it ;-) . It might 
be important, and might be some dependency of the sound drivers (or 
other similar onboard components).
 
 

HTH,
Holly

> 
> 
  > alsaconf runs, it just fails to find anything......
> 
> I'm beginning to think there is no support for SiS audio chips:
> 0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] 
> Sound Controller (rev a0)
>         Subsystem: CLEVO/KAPOK Computer: Unknown device 0402
>         Flags: bus master, medium devsel, latency 173, IRQ 5
>         I/O ports at 1c00
>         I/O ports at 1800 [size=128]
>         Capabilities: [48] Power Management version 2
> 
> 
> James
> 

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Holly Bostick <motub <at> planet.nl> writes:


> Yes they are---
> 
> ALSA:
> 
> CONFIG_SND_INTEL8X0: 
> 
>      Say Y here to include support for the integrated AC97 sound 
>      device on motherboards with Intel/SiS/nVidia/AMD chipsets, or 
>      ALi chipsets using the M5455 Audio Controller.  (There is a 
>      separate driver for ALi M5451 Audio Controllers.) 
>      To compile this driver as a module, choose M here: the module 
>      will be called snd-intel8x0. 

Well after digging round the alsa-project.org site, I have to agree with you.
http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=
SiS&card=SiS+740.&chip=SI7012&module=intel8x0

I believe the chip number is SiS 7012 but it could be the 7013. Since it's a
(clevo D470W) portable, there is no mobo book....

Here's what I did for I2C bus
I2C support  --->  
 I2C Hardware Bus support  --->  
<*> SiS 96x

And for the alsa (in case it matters) stuff:
Multimedia devices  --->
Video For Linux  --->

and Sound:
Sound  --->
<M> Sound card support 
Advanced Linux Sound Architecture  --->
<M> Advanced Linux Sound Architecture
PCI devices  ---> 
<M> Intel i8x0/MX440, SiS 7012; Ali 5455; NForce Audio; AMD768/8111


So for the 
> OSS:
> 
>   CONFIG_SOUND_TRIDENT: 
I think this OSS/trident as nothing on the system is trident stuff is
 irrelevant
> 
> This is kernel 2.6.10-rc2-bk7, and alsa-driver-1.0.7
> 
> So you probably want to dig out your mobo manual and see if you can get 
> more information on just what chipset is at work here.
do not get a mobo book with a portable
> 
> Maybe you're just using the wrong drivers.
yep, that I was, now I need a little more help to see that I get
the modules loaded correctly.
> 
> You might also want to check if you've enabled the I2C bus for your mobo 
> chipset-- I'm not quite sure what it is, but if the kernel has gone to 
> so much trouble to include some special support for my mobo's particular 
> version of it in the kernel, I figure I should enable it  . It might 
> be important, and might be some dependency of the sound drivers (or 
> other similar onboard components).

As mentioned above, I2C looks correct, according to your advice.



--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Christoph Eckert]

> yep, that I was, now I need a little more help to see that
> I get the modules loaded correctly.

I'm not that familliar with modules configuration, but I'll 
post the content of /etc/modules.d/alsa from my dell inspiron 
notebook which also has AC 97 sound:


# OSS/Free portion - card #1

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.6 ---
options snd  device_mode=0666
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
# --- END: Generated by ALSACONF, do not edit. ---

Hope this helps.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:


> I'm not that familliar with modules configuration, but I'll 
> post the content of /etc/modules.d/alsa from my dell inspiron 
> notebook which also has AC 97 sound:
> 
> # OSS/Free portion - card #1
> 
> alias /dev/mixer snd-mixer-oss
> alias /dev/dsp snd-pcm-oss
> alias /dev/midi snd-seq-oss
> 
> # --- BEGIN: Generated by ALSACONF, do not edit. ---
> # --- ALSACONF verion 1.0.6 ---
> options snd  device_mode=0666
> alias snd-card-0 snd-intel8x0
> alias sound-slot-0 snd-intel8x0


this is exactly what I have in my /etc/modules.d/alsa file.

When it boots I an error message:

FATAL Module snd_intel8x0 not found

How do I fix this?

It's selected in the kernel, not as loable option (M) but
with an asterick as part of the kernel.....

Ideas?

James


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Christoph Eckert]

> It's selected in the kernel, not as loable option (M) but
> with an asterick as part of the kernel.....

This means it is directly in the kernel instead of being an 
external module. THis is why it cannot be loaded as a module, 
I guess.

So, the question is, how to assign it to the device if it's 
directly in the kernel, and I do not know.

Perhaps it is better to reconfigure the kernel to make it a 
module (M instead of the asterisk), install it and reboot.


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:


> options snd  device_mode=0666
> alias snd-card-0 snd-intel8x0
> alias sound-slot-0 snd-intel8x0



IT"S WORKING!!!!!!!!!!!!

THANKS EVERYONE!

JAMES



--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Dennis Robertson]

James wrote:
> Christoph Eckert <mchristoph.eckert <at> t-online.de> writes:

> 
> IT"S WORKING!!!!!!!!!!!!

Following that happy ending can I ask whether anyone has managed to get
alsa to work with the Asus A7N8X deluxe on board sound? Several attempts
have produced nothing but static. OSS works OK, but using a deprecated
method is to be deprecated, I guess. I have followed the Gentoo linux 
alsa guide and the static module method
mentioned by T.G. without success (still constant static).
Regards
-- 
Dennis Robertson


--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[james]

Dennis Robertson <dencar <at> iinet.net.au> writes:

> Following that happy ending can I ask whether anyone has managed to get
> alsa to work with the Asus A7N8X deluxe on board sound? 


Well,  using 'lshw', I have a:

description: Motherboard
       product: A7V8X-X
       vendor: ASUSTeK Computer INC.
       physical id: 0
       version: REV 1.xx
       serial: xxxxxxxxxxx

that I'm going to work on audio and video (xawtv video is working) in the 
next few days/weeks/whatever. Look at the differences and see if our audio
a/v chips are the same or similar. If the are close enough, I'm willing 
to share the painful process with others......... I be using other video
cards, like the LMLBT44 (uses a BT878 chip), in this system, but the efforts may
be similar enough to warrant collaboration?

If so, start a new thread, and away we go...
Disclaimer, I'm not very smart, just stubborn as hell
(I do not quite, until things work. I also have an 
old_lady that's pretty sharp with firmware and device drivers,
so If it comes down to a driver that needs modification, that's
a doable as long as there is something similar to look at
and somebody that can architect what needs to be done, and 
how the drivers works...pain....ass(embler)-pain....
Lot's of problems in 2.6.x with devices are related to driver code
that needs tweaking......
James

James





--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: sound driver

[Christoph Eckert]

> IT"S WORKING!!!!!!!!!!!!

Aaaah, great ;-) .


 Best regards


    ce

--
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: sound driver

[James]

Holly Bostick <motub <at> planet.nl> writes:


> Yes they are---


You are correct. I think I'm very close now. I edited '/etc/modules.d/alsa'
by hand, inputing:

alias sound-slot-0 snd-card-0
alias snd-card-0 snd-intel8x0


But when the system boot, it complains during the boot process about the module 
or drivers or something 8x0 (sorry, the message echoed to the screen during 
boot is not part of dmesg....? Maybe there is a file I can look that 
exactly captures the error messages to the screen during boot?

Somehow, this name is incomplete, or the driver is missing....

I got the idea from: http://www.alsa-project.org/alsa-doc/doc-php/
template.php?company=SiS&card=SiS+740.&chip=SI7012&module=intel8x0

Any help is appreciated, I think I'm real close now....


James


--
gentoo-user@gentoo.org mailing list