Onboard audio device not detected for ASUS P4S533 MB
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Rep:
Onboard audio device not detected for ASUS P4S533 MB
I recently installed Arch Linux on an old desktop machine. Everything works well except the onboard audio isn't detected at all.
I am using the 2.6.32-ARCH kernel
My lspci output is:
Code:
# lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host & Memory & AGP Controller
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS961 [MuTIOL Media IO] (rev 10)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:04.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:05.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:06.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:07.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:08.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:09.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0a.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0b.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0c.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0d.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0e.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:0f.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:10.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:11.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:12.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:13.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:14.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:15.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:16.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:17.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:18.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:19.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1a.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1b.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1c.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1d.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1e.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
00:1f.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a3)
Not really sure what the repeated listing of the modem is about...
I looked through the dmesg output and didn't see anything about audio.
Here are a couple of sections of dmesg output that looked like they could be errors (they may have more to do with the fact that my ps/2 ports aren't working; not sure):
Code:
PCI: Using ACPI for IRQ routing
pci 0000:00:04.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:04.0: BAR 0: can't allocate resource
pci 0000:00:05.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:05.0: BAR 0: can't allocate resource
pci 0000:00:06.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:06.0: BAR 0: can't allocate resource
pci 0000:00:07.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:07.0: BAR 0: can't allocate resource
pci 0000:00:08.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:08.0: BAR 0: can't allocate resource
pci 0000:00:09.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:09.0: BAR 0: can't allocate resource
pci 0000:00:0a.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0a.0: BAR 0: can't allocate resource
pci 0000:00:0b.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0b.0: BAR 0: can't allocate resource
pci 0000:00:0c.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0c.0: BAR 0: can't allocate resource
pci 0000:00:0d.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0d.0: BAR 0: can't allocate resource
pci 0000:00:0e.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0e.0: BAR 0: can't allocate resource
pci 0000:00:0f.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:0f.0: BAR 0: can't allocate resource
pci 0000:00:10.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:10.0: BAR 0: can't allocate resource
pci 0000:00:11.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:11.0: BAR 0: can't allocate resource
pci 0000:00:12.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:12.0: BAR 0: can't allocate resource
pci 0000:00:13.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:13.0: BAR 0: can't allocate resource
pci 0000:00:14.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:14.0: BAR 0: can't allocate resource
pci 0000:00:15.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:15.0: BAR 0: can't allocate resource
pci 0000:00:16.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:16.0: BAR 0: can't allocate resource
pci 0000:00:17.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:17.0: BAR 0: can't allocate resource
pci 0000:00:18.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:18.0: BAR 0: can't allocate resource
pci 0000:00:19.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:19.0: BAR 0: can't allocate resource
pci 0000:00:1a.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:1a.0: BAR 0: can't allocate resource
pci 0000:00:1b.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:1b.0: BAR 0: can't allocate resource
pci 0000:00:1c.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:1c.0: BAR 0: can't allocate resource
pci 0000:00:1d.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:1d.0: BAR 0: can't allocate resource
pci 0000:00:1e.0: BAR 0: address space collision on of device [0xb000-0xb007]
pci 0000:00:1e.0: BAR 0: can't allocate resource
serial 0000:00:04.0: can't derive routing for PCI INT A
serial 0000:00:04.0: PCI INT A: no GSI - using IRQ 10
0000:00:04.0: ttyS2 at I/O 0x1000 (irq = 10) is a 8250
serial 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
0000:00:05.0: ttyS3 at I/O 0x1008 (irq = 17) is a 16450
serial 0000:00:06.0: can't derive routing for PCI INT A
serial 0000:00:06.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:06.0: -28
serial 0000:00:07.0: can't derive routing for PCI INT A
serial 0000:00:07.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:07.0: -28
serial 0000:00:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Couldn't register serial port 0000:00:08.0: -28
serial 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Couldn't register serial port 0000:00:09.0: -28
serial 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Couldn't register serial port 0000:00:0a.0: -28
serial 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Couldn't register serial port 0000:00:0b.0: -28
serial 0000:00:0c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Couldn't register serial port 0000:00:0c.0: -28
serial 0000:00:0d.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Couldn't register serial port 0000:00:0d.0: -28
serial 0000:00:0e.0: can't derive routing for PCI INT A
serial 0000:00:0e.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:0e.0: -28
serial 0000:00:0f.0: can't derive routing for PCI INT A
serial 0000:00:0f.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:0f.0: -28
serial 0000:00:10.0: can't derive routing for PCI INT A
serial 0000:00:10.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:10.0: -28
serial 0000:00:11.0: can't derive routing for PCI INT A
serial 0000:00:11.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:11.0: -28
serial 0000:00:12.0: can't derive routing for PCI INT A
serial 0000:00:12.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:12.0: -28
serial 0000:00:13.0: can't derive routing for PCI INT A
serial 0000:00:13.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:13.0: -28
serial 0000:00:14.0: can't derive routing for PCI INT A
serial 0000:00:14.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:14.0: -28
serial 0000:00:15.0: can't derive routing for PCI INT A
serial 0000:00:15.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:15.0: -28
serial 0000:00:16.0: can't derive routing for PCI INT A
serial 0000:00:16.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:16.0: -28
serial 0000:00:17.0: can't derive routing for PCI INT A
serial 0000:00:17.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:17.0: -28
serial 0000:00:18.0: can't derive routing for PCI INT A
serial 0000:00:18.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:18.0: -28
serial 0000:00:19.0: can't derive routing for PCI INT A
serial 0000:00:19.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:19.0: -28
serial 0000:00:1a.0: can't derive routing for PCI INT A
serial 0000:00:1a.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1a.0: -28
serial 0000:00:1b.0: can't derive routing for PCI INT A
serial 0000:00:1b.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1b.0: -28
serial 0000:00:1c.0: can't derive routing for PCI INT A
serial 0000:00:1c.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1c.0: -28
serial 0000:00:1d.0: can't derive routing for PCI INT A
serial 0000:00:1d.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1d.0: -28
serial 0000:00:1e.0: can't derive routing for PCI INT A
serial 0000:00:1e.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1e.0: -28
serial 0000:00:1f.0: can't derive routing for PCI INT A
serial 0000:00:1f.0: PCI INT A: no GSI - using IRQ 10
Couldn't register serial port 0000:00:1f.0: -28
It seems like my onboard audio is getting completely overlooked.
On another note, the manufacturer (ASUS) actually provides Linux audio drivers for my motherboard (model: P4S533). I attempted to install them, but the configuration process involves using make menuconfig, make xconfig, or make config to add the drivers to the kernel (I think) and I'm still a relatively new Linux user and had no clue what I was doing...
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Original Poster
Rep:
Thank you for the prompt reply Glenn!
This is the output on my box:
Code:
# ls -la /usr/src/
total 12
drwxr-xr-x 3 root root 4096 Mar 13 18:31 .
drwxr-xr-x 9 root root 4096 Mar 13 18:31 ..
drwxr-xr-x 21 root root 4096 Mar 13 19:38 linux-2.6.32-ARCH
I think I have everything I need to compile the kernel. I have qt3, make, and gcc/g++
If I need to download the kernel source, does the exact version matter, or does it just need to be version 2.6.32?(i.e. 2.6.32.8 vs 2.6.32.10)
My goal is to install the audio drivers without affecting the rest of the system.
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Original Poster
Rep:
Alright, I created a static link to my linux-2.6.32-ARCH directory with the ln command. I changed to the linux directory(link) and I do have a Makefile.
The size of my linux-2.6.32-ARCH directory is 41M (using #du -h linux-2.6.32-ARCH)
The output of uname -a on my box is:
Code:
# uname -a
Linux myhost 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 23 19:24:08 UTC 2010 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz GenuineIntel GNU/Linux
So I guess the name of mine is:
2.6.32-ARCH
The EXTRAVERSION is blank in my Makefile initially...
Code:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 32
EXTRAVERSION =
NAME = Man-Eating Seals of Antiquity
I changed it to:
Code:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 32
EXTRAVERSION = -ARCH
NAME = Man-Eating Seals of Antiquity
I think you will need the whole source package. 40Mb is too small to contain all the files.
STEPS TO BUILD DRIVER <edit>edited by Glenn</edit><edit></edit>
================================================================================
<edit>
If you had to install the sources, do...
Code:
make oldconfig
this will make sure the settings of your installed kernel are applied to the new sources.
Now we can use the readme guide.
</edit>
1. Backup the Config.in and Makefile in the sound driver directory
(/usr/src/linux/driver/sound). <edit>To backup, just rename the files, with a new extension, like .old</edit>
The Configure.help provide help when you config driver in step
4, please backup the original one (/usr/src/linux/Document) and
copy this file.
The cmpci is document for the driver in detail, please copy it
to /usr/src/linux/Document/sound so you can refer it. Backup if
there is already one. <edit> same again, just rename with .old</edit>
2. Extract the tar file by 'tar xvzf cmpci-xx.tar.gz' in the above
directory.
<edit>cmpci-5.68.tar.gz to a dir in your /home/<user> dir, like /home/<user>/downloads or /home/<user>/build
go to that dir and copy the files to the appropriate places
Config.in and Makefile to /usr/src/linux/driver/sound
Configure.help to /usr/src/linux/Document
the folder cmpci with the files cmpci, cmpci.c to /usr/src/linux/driver/sound/
</edit>
3. Change directory to /usr/src/linux
4. Config cm8338 driver by 'make menuconfig', 'make config' or
'make xconfig' command.<edit>just use make xconfig</edit>
<edit>Make use of the find tool to quickly navigate</edit>
5. Please select Sound Card (CONFIG_SOUND=m) support and CMPCI
driver (CONFIG_SOUND_CMPCI=m) as modules. Resident mode not tested.
For driver option, please refer 'DRIVER PARAMETER'
6. Compile the kernel if necessary.
7. Compile the modules by 'make modules'.
8. Install the modules by 'make modules_install'
see how you go with that.
Regards Glenn
Last edited by GlennsPref; 03-18-2010 at 01:35 AM.
Reason: spelling
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Original Poster
Rep:
Before I begin, I don't actually have a /usr/src/linux/driver/sound directory. I have a /usr/src/linux/drivers directory (no sound/ subdirectory) and a /usr/src/linux/sound/drivers directory. Should I create a /usr/src/linux/drivers/sound directory or use the /usr/src/linux/sound/drivers directory?
Also, I don't appear to have a Config.in file or a Makefile in /usr/src/linux/sound/drivers. I have a Kconfig file.
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Original Poster
Rep:
Well, after downloading the kernel source, copying the cmpci files into the appropriate places, and going through make xconfig, I attempted to build the kernel (using the instructions found here as a guide).
When it reached the Makefile that came with the cmpci driver files, I got this error:
Code:
# make bzImage
scripts/kconfig/conf -s arch/x86/Kconfig
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
GZIP kernel/config_data.gz
IKCFG kernel/config_data.h
CC kernel/configs.o
LD kernel/built-in.o
/usr/src/linux-2.6.32.10/sound/drivers/Makefile:159: /Rules.make: No such file or directory
make[2]: *** No rule to make target `/Rules.make'. Stop.
make[1]: *** [sound/drivers] Error 2
make: *** [sound] Error 2
Isn't the use of Rules.make a convention from kernel 2.4?
If so, should I just attempt to get a Rules.make file from the net and copy it into my linux-2.6.32.10 directory?
As a side note, the kernel does build successfully with the original (dummy) Makefile in the sound/drivers directory.
v4.03 09/20/2000
1. Support Linux version 2.2.x, 2.3.x, and 2.4.x.
we might be out of luck with the package I have....
Here is more bad evidence....very old versions of linux desktops here.
Code:
3. Driver installation for various distributions:
a. Slackware 4.0
Add the 'modprobe cmpci' command in your /etc/rc.d/rc.modules
file.so you can start the driver automatically each time booting.
b. Caldera OpenLinux 2.2
Use LISA to load the cmpci module.
c. RedHat 6.0 and S.u.S.E. 6.1
a search in the Changelog refer to 2004, when the module was inserted.
Code:
* Tue Apr 20 2004 Nicolas Planel <nplanel@mandrakesoft.com> 2.6.3-10mdk
- acpi cardbus pci routing fix.
- yenta irq routing fix for TI chipset.
- oss cmpci driver update to 6.64.
- BIG isdn update.
- set max symlink to 10.
But it's not listed on my x86_64 system anywhere.
Last edited by GlennsPref; 03-18-2010 at 05:01 PM.
Reason: My bad.
This involved using make menuconfig. At that point, the kernel built successfully using make bzImage.
After that, I copied the cmpci files to the /usr/src/linux-2.6.32.10/sound/drivers directory after backing up the preexisting Makefile (Config.in did not previously exist there).
Then, I used make xconfig to add the CONFIG_SOUND module.
Unfortunately, I couldn't find the CONFIG_SOUND_CMPCI option. There was a CONFIG_SND_CMIPCI that was already selected as a module, but it was listed under PCI sound cards.
After saving in the xconfig, I entered make oldconfig and then I attempted to build the kernel again using make bzImage, which resulted in the error for the asus cmpci Makefile.
Quote:
we might be out of luck with the package I have....
Here is more bad evidence....very old versions of linux desktops here.
I got that impression too. Also, when I searched for Rules.make on the web, the results seemed to imply that Rules.make was included in kernel 2.4, but not 2.6. Specifically, this page: http://fxr.watson.org/fxr/source/Rul...v=linux-2.4.22
So, if the drivers were not updated for 2.6 am I out of luck on getting my onboard audio to work? Or is there a reasonable way to get the drivers to work in 2.6?
Another thought - I was talking to someone about this today and they seemed to be under the impression that if lshw doesn't detect the hardware, then the issue is with the hardware and not the kernel. As is the case with lspci, the output of lshw does not show an audio device.
I was a little skeptical, but could that be true?
Distribution: Arch Linux i686 w/ e17, Lubuntu (Ubuntu w/ LXDE)
Posts: 14
Original Poster
Rep:
By the way, I will be leaving for an IEEE conference tomorrow and won't be back until late on Sunday, so I won't be able to do anything with my desktop machine until Monday at the earliest.
Thank you for all of your help! I really appreciate it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.