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

SOLVED: Re: IRQ conflict?! (was Re: Trouble with Alsa 0.9.6-5, 2.4.22 AC97 ...)



On Tue, 2003-11-11 at 14:30, Ron Johnson wrote:
> On Tue, 2003-11-11 at 12:56, Alan Chandler wrote:
> > On Tuesday 11 November 2003 15:50, Ron Johnson wrote:
> > > On Tue, 2003-11-11 at 09:28, Ron Johnson wrote:
> > > > On Tue, 2003-11-11 at 08:20, Kjetil Kjernsmo wrote:
> > > > > On Tuesday 11 November 2003 14:07, Ron Johnson wrote:
> > > > > > # apt-get -u install kernel-source-2.4.22
> > > > > > # cd /usr/src
> > > > > > # tar xvfj kernel-source-2.4.22.tar.bz2
> > > > > > # ln -sf  <startled pause>
> > > > > >
> > > > > :-)
> > > > > :
> > > > > > Hey, look what's in /usr/src!!!  Never noticed that....
> > > > > >
> > > > > > alsa-driver.tar.bz2
> > > > > >
> > > > > > I guess I'll have to take a look at that.
> > > > >
> > > > > Yup!
> > > > >
> > 
> > I just upgraded a basically kde system to use alsa. It was difficult but I got 
> > there in the end.
> > 
> > The main problem appears to be that the alsa packages cut out during 
> > installation because there appears to be a conflict between it and what was 
> > there before.  I had already got some files in both /etc/modutils and in /
> > etc/devfs related to my emu10k1 device.
> > 
> > I was also running the update (via aptitude) in a kde konsole window, which 
> > meant that the old sound system was being held on to by kde.
> > 
> > In the end, I got rid of my references in /etc/modules and /etc/devfs, dropped 
> > into console mode and killed off kde
> > 
> > I then reran dpkg-reconfigure alsa-base again.  I might even have had to 
> > reboot to get the permissions in /dev/snd and /dev/sound set correctly, can't 
> > exactly remember.
> > 
> > Anyway - all working now
> 
> Ah, lucky you.  When trying to do "# modprobe  snd-via82xx", I'm 
> getting this error in /var/log/syslog :
> <snip> kernel: ALSA ../alsa-kernel/pci/via82xx.c:1897: unable to \
>       grab IRQ -19
> 
> # cat /proc/interrupts
>            CPU0       
>   0:   92801266    IO-APIC-edge  timer
>   1:     475234    IO-APIC-edge  keyboard
>   2:          0          XT-PIC  cascade
>   8:          1    IO-APIC-edge  rtc
>   9:          0    IO-APIC-edge  acpi
>  12:    4838014    IO-APIC-edge  PS/2 Mouse
>  14:    3880253    IO-APIC-edge  ide0
>  15:        420    IO-APIC-edge  ide1
>  18:    2915153   IO-APIC-level  eth0
>  19:          2   IO-APIC-level  ohci1394
> NMI:          0 
> LOC:   92802586 
> ERR:          0
> MIS:          0
[snippage]

After looking in /var/log/dmesg (plain old dmesg is useless after
so long an uptime), I see that the ACPI on my mobo is buggy.

Rebooting with the "acpi=off" option fixed it.

-- 
-----------------------------------------------------------------
Ron Johnson, Jr. ron.l.johnson@cox.net
Jefferson, LA USA

"Democracy is woman's greatest invention. Indeed, it even
reflects her character: purposeless, irrational, subject to
public opinion and passing fashions, rambling, confused,
underhanded, scheming, in love with its own purity."
Unknown



Reply to: