Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

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

Help finding device...

Billy SG McCarthy said:
> No, it's not true.  Dmesg tells you that the system
> recognizes there is *something* there, but you need
> the proper driver modules to make the hardware do
> stuff.  Until then, the kernel is merely relaying info
> it gets from the hardware, not actually interacting
> with it.
> --- Scott Ehrlich <scott at> wrote:
>> Custom kernel, and I always compile static-ly.
>> I would have thought that if the kernel saw the
>> device through dmesg, that
>> it would be somewhat easy to figure out the
>> corresponding /dev.   Not
>> true?

Yes, this tells you only that the kernel has found some hardware, but not neccessarily
that a driver is there to handle the hardware. If you use alsa, use lsmod to see whether
all the sound modules are loaded, especially the i810 module.

> =====
> "Whoa what I want to know, how does the song go?"
> --The Grateful Dead--
> Kindly yours,
> Billy S G McCarthy
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool. Try it!
> _______________________________________________
> Discuss mailing list
> Discuss at

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /