Re: updated kernel leaves me without sound! : Ubuntu 7.04

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Sounds good but I've been rebooting the whole time.  At exactly which
point do I need to reboot to ensure that I get it right?

Thanks,

Martin

On 14/06/07, Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> On 6/14/07, mQ - Martin Quested <martinquested@xxxxxxxxx> wrote:
> > I was running Alsa version 1.0.13 on Ubuntu Edgy, with an nVidia MCP51
> > chip using the hda-intel driver.  When I upgraded to the current
> > version of Ubuntu Feisty, the sound wasn't there.  The system actually
> > told me there was no soundcard present.
> >
> > Yet lspci continued to report that the sound card was there.
> >
> > I tried sudo aptitude reinstall linux-image-`uname -r` and then
> > re-installing Alsa, I tried versions 1.0.12, 1.0.13, 1.0.14 and a
> > couple of the 14rc versions - all as instructed on the wikis and
> > elsewhere.
> >
> > At the point where I modprobe the driver I run into problems.  I've
> > tried both hda-intel and intel8x0.  With intel8x0 I get no response,
> > just a return to the prompt.  With hda-intel I get an error message:
> >
> > FATAL: Error inserting snd_hda_intel
> > (/lib/modules/2.6.20-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko):
> > Unknown symbol in module, or unknown parameter (see dmesg)
> >
>
> Usually this message means you tried to load new alsa modules without
> unloading the old ones first.  Easiest fix is to reboot.
>
> > aplay -l continues to tell me there is no sound card present.
> >
> > Is that the sort of detail you need?
> >
> > All help gratefully received.  Thanks.
> >
> > MQ
> >
> > > From: Lee Revell <rlrevell@xxxxx> - 2007-06-01 21:42
> > >On 6/1/07, Matthew Patenaude <mnglfiddle@xxxxx> wrote:
> > > > Has anyone had a similar problem?
> > > >
> > > > My auto updates in Ubuntu Feisty upgraded my kernel to 2.6.20.16 from
> > > > .......15 and when I restarted I no longer have sound! I restarted and
> > > > pressed esc to get to my Grub options and chose the older kernel and it
> > > > booted up with sound, no problem.
> > > >
> > > > Question is: why did it do that? and should I ditch the new kernel (and
> > > > how), or is there a simple way to get the new kernel to load alsa correctly?
> > >
> > > Please try to get more information. You have not provided enough to
> > > debug the problem. asound.state, etc.
> > >
> > > Lee
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux