Hello,
I checked if alsa and stuff is working on other kernels - it seems it is
working brilliantly! Mic and sound works fine!
So the problem would be with the latest kernel. I removed it while being on
previous one and installed it again, but the problem is still present.
Then I tried to do all
Well depending on HOW it was obtained. The short answer is that the
kernel primarily installs to only TWO locations.
/lib/modules/`uname -r`/
and
/boot/
So check for the #.##.## of your kernel version in those locations.
Also note a few symlinks /boot/config / boot/system /boot/kernel that
In article
aanlktikpolrugqhvu0y-p5xzpyra8-m8enokds3xd...@mail.gmail.com,
James Shatto wwwshad...@gmail.com wrote:
Basically the same way. To redo your kernel. dpkg --purge --force-all
apt-get install. Just make sure that you DO NOT do it to the kernel
that you are currently running.
On Sat, 2011-02-12 at 23:15 +, Marcin Szyniszewski wrote:
Though I think that those two No such file or directory notices are
no
good...
And after the reboot... surprise surprise... nothing works :(((
Does that mean that we run out of options? :(
Please help!
Best,
*mszynisz*
hi
Thank you all for the replies! Very appreciated! :)
$ sudo modprobe [module]
FATAL: Error inserting snd
(/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd
WARNING: Error inserting
As I suspected, the modules aren't loaded so alsa isn't even running.
Hence your original open error(s).
How did you install alsa? Not that I think it is your issue, but it
could be. If you boot with lilo, you need to re-install lilo after
creating a new kernel. Even if it's technically the
Like my previous speaker already told: the modules cannot be loaded because
other modules are missing. Either you don't have modules installed at all
(which most certainly means you have a wrong kernel image running) or the
module loader cannot resolve the dependencies. To check if the module
On Sat, Feb 12, 2011 at 16:26, James Shatto wwwshad...@gmail.com wrote:
As I suspected, the modules aren't loaded so alsa isn't even running.
Hence your original open error(s).
How did you install alsa? Not that I think it is your issue, but it
could be. If you boot with lilo, you need to
$ sudo dpkg -l '*alsa*'
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Description
On Sat, Feb 12, 2011 at 22:50, James Shatto wwwshad...@gmail.com wrote:
Well there's the old school ways. When all else fails, re-install.
Fortunately in linux that's not as dreaded as it sounds
$ sudo dpkg --purge --force-all alsa alsa-base alsa-firmware-loaders
alsa-oss alsa-source
On Sat, 12 Feb 2011, Marcin Szyniszewski wrote:
On Sat, Feb 12, 2011 at 16:26, James Shatto wwwshad...@gmail.com wrote:
$ sudo depmod -a
$ sudo modprobe snd-hda-intel
WARNING: Error inserting snd_timer
(/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd-timer.ko): Unknown
symbol in
On Sat, 12 Feb 2011, James Shatto wrote:
$ sudo dpkg -l '*alsa*'
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Basically the same way. To redo your kernel. dpkg --purge
--force-all apt-get install. Just make sure that you DO NOT do it
to the kernel that you are currently running. Which might mean
installing an older kernel as a safe recovery and boot to that before
recovering the kernel you want to
In article
AANLkTikA=hHDEy3pCsamVvgye7u9=_4pqqw_pscjb...@mail.gmail.com,
Marcin Szyniszewski mszyn...@gmail.com wrote:
Is the file /usr/bin/alsamixer present, or /sbin/alsa ?
Or the /usr/share/alsa directory?
You should have these or equivalents IIUC.
/usr/bin/alsamixer is present
Most times when I get something like that it has to do with the
/dev/'s not being present. Could be that udev isn't running on your
box. Or isn't configured for alsa. It could also be something else
like snd-pcm-oss not auto loading. And it's friends, snd-mixer-oss
snd-seq-oss. Basically
Did you issue alsamixer as the command or the full pathname? If the former,
maybe something is wrong with your path/environment setup.
I used it as both. Nothing works :/
I am wondering if your OS install hasn't actually loaded the modules
correctly for your hardware.
Everything worked
I also use ubuntu (10.04) and it came to happen that the system didn't load the
modules automatically any more. I don't know why that happened or where this
loading is prohibited. Just try to load the module manually and see if that
works. If so, you could also post this on a ubuntu mailing
Note that * is a wildcard. So /dev/dsp* is any devices that start
with /dev/dsp.
It looks like you don't have the modules loaded.
# modprobe snd-hda-intel
$ sudo modprobe snd-hda-intel
(depending on your distro / $ is user / # is root)
It might be /etc/init.d/alsasound or other named thing
On Fri, 11 Feb 2011, James Shatto wrote:
Note that * is a wildcard. So /dev/dsp* is any devices that start
with /dev/dsp.
It looks like you don't have the modules loaded.
/dev/dsp and /dev/audio are the oss sound drivers, not alsa. alsa has an oss
emulation module, which will create those
Except that your web browser likely defaults the OSS, not ALSA. And
OSS emulation IS part of alsa. Even if you have to launch an
application with aoss to use the alsa sound drivers. It's probably
not native alsa, but it is coded as part of alsa's drivers, and
therefor part of alsa. But yeah,
In article
AANLkTim2OVgoU=6vwjeoxfopf86gft7x-f09lvazu...@mail.gmail.com,
Marcin Szyniszewski mszyn...@gmail.com wrote:
$ alsamixer
cannot open mixer: No such file or directory
[snip other details]
Is the file /usr/bin/alsamixer present, or /sbin/alsa ?
Or the /usr/share/alsa directory?
Is the file /usr/bin/alsamixer present, or /sbin/alsa ?
Or the /usr/share/alsa directory?
You should have these or equivalents IIUC.
/usr/bin/alsamixer is present and gives:
cannot open mixer: No such file or directory
/sbin/alsa also is present. Gives the usual:
Usage: /sbin/alsa
Hello,
I have a big problem with my sound. SystemPreferencesSound doesn't
work at all.
I'm working on Ubuntu 10.10, Acer 6930G. Soundcard probably hda-intel.
Interesting things from terminal:
$ alsamixer
cannot open mixer: No such file or directory
$ alsaconf
alsaconf: command not found
$ locate
23 matches
Mail list logo
