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

Re: usb issues in sarge: scanner, multicard



On Wed, Aug 17, 2005 at 10:02:02AM +0200, Bob Vloon wrote:
> >> BTW: I assume that the IRQ- messages are harmless, but I might be proven
> >> wrong..
> 
> AR> I have the feeling that they are related to the problem, because it
> AR> happens always when I connect anything to a usb port for the first
> AR> time after rebooting. After that first time, no more reaction from the
> AR> kernel. 
> 
> Ah. Oh :) And you're using the 2.6.8 in Sarge.. Hmm. There are two things I
> can come up with:
> 
>  1. if it's an IRQ problem, try disabling a conflicting component in your
>     system (you will have to go into your BIOS, or blatantly pull out some
>     card) - if it is about conflicting hardware, of course). 
>     Are the messages (in /var/log/syslog) preceeded by something like "irq
>     XX: nobody cared"?
>  2. try the 2.4.xx kernel, which might not have this problem, or upgrade the
>     kernel to a newer one.
> 
> However, it detects you scanner on boot-up, so I'm wondering why the scanner
> doesn't get the correct permissions.. So when you're still up to it, I'm
> still curious for those messages :)
> 

It was a kernel problem, I had not thought of that. I went ahead,
grabbed a kernel image from sid, installed it (2.6.11) and all usb
and scanner permissions problems dissapeared. But now there is no
sound, I tried to find any info in kern.log, syslog, but didn't see any
reference to alsa. However, I noticed that a message flashed on the
screen as it booted, something like: alsainit failed, not exactly
sure. No sound, but aumix and gnome mixer show volume to 100%!

I think that a note about this problem with the kernel in sarge must
be posted as installation note, and may be in the website some link to
a newer 2.6.x kernel, because I assume that there will be a bunch of
people with similar problems. (Sarge, kernel people, I hope you read
this)

Thanks, and looking forward to more input to solve the sound issue
(emu10k1). 

AR



Reply to: