DebianThis forum is for the discussion of Debian 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.
You should have a module called cmi8738 or something like that. Have a look through the directory /lib/modules/`uname -r`/kernel/sound/ (and any subdirectories) for files with the ".o" extension. There should be one corresponding to your sound card (I remember from your kernel config you compiled it so it should be there) and will be called something like your sound card's chipset (eg "cmi8738.o"). If you find something like that then type "modprobe cmi8738" (notice the ".o" extension is not used with this function) from any directory. Once you have done that, make sure all your playback volume levels are set high and try to play a piece of music. If that works add the line "cmi8738" to your /etc/modules file and it will be loaded automatically on start up.
PS: the soundcore module is required aswell but you need a card-specific one also to get sound working fully.
If you find the sound a little poor quality, you can also download and install the alsa drivers from www.alsa-project.org.
I loaded cmpci.o and ac97_codec.o.
I run sndconfig, it found the audio chip but it tells me "An error occured while writing the config file".
and, another question: when I launch xmms it needs a plugin to use audio. Which plugin I need to select?
I've never used sndconfig. Once you load those modules you should be OK and not need to do any more config apart from volume levels and the like. However, if you know the location of where it's trying to save the config file to you may be able to change the permissions or run the program as root.
As for xmms, it shouldn't need a plugin for audio. It's an audio program. I've heard some distros make it so that by default xmms can't play back mp3's but you're using debian and I've never seen anything like that under debian. Maybe unstable is different (I run testing). All I can suggest is have alook through the packages that start with "xmms" and see if there's an mp3 plugin (I assume you're playing mp3's?). To do this type: dpkg -l xmms* and see what comes up.
I restarted my linux box and the audio didn't work yet. Then I did chmod 666 /dev/dsp, I reloaded cmpci and ac97_codec modules and everything now work!! I saw that soundcore module now use cmpci
I would see cpu temperature so I've aptgetted lm_sensors
But when I launch "sensors-detect" (as root, of course) this is the message:
Quote:
This program will help you to determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively.
You need to have installed lm-sensors modules before you can use
some functions of this utility.
Also, you need to be `root', or at least have access to
the /dev/i2c[-/]* files for some things.
If you have patched your kernel and have some drivers built-in you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
BIOS vendor (ACPI): ASUS
System vendor (DMI): System Manufacturer
BIOS version (DMI): ASUS A7S333 ACPI BIOS Revision 1005
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-sis645' for device 00:00.0: Silicon Integrated Systems SIS745
Use driver `i2c-sis645' for device 00:02.0: Silicon Integrated Systems 85C503/5513 (LPC Bridge)
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-sis645' (say NO if built into your kernel)? (YES/no):
modprobe: Can't locate module i2c-sis645
Loading failed... skipping.
Load `i2c-sis645' (say NO if built into your kernel)? (YES/no):
modprobe: Can't locate module i2c-sis645
Loading failed... skipping.
Do you now want to be prompted for non-detectable adapters? (yes/NO):
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no):
modprobe: Can't locate module i2c-dev
Loading failed, expect problems later on.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect line 3607, <STDIN> line 5.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.