On Sun, 2010-12-26 at 09:02 -0800, Arjan van de Ven wrote:
> On 12/25/2010 6:02 PM, Giuseppe Dia wrote:
> > Hi all,
> > I'm trying to make the Omnibook driver
> > (http://sourceforge.net/apps/mediawiki/omnibook/index.php?title=Main_Page
> > last version from git) more Meego 1.1 netbook friendly. Compiling and
> > installing is flawless, and it works (hot keys, blue tooth works on my
> > Toshiba nb200) but the original driver doesn't have the MODULE_ALIAS
> > macro defined, so it's not loaded at boot.
> > As far as I know (correct me if I'm wrong), there's no /etc/modules or
> > other explicit way to load a module at boot in meego and I understand
> > that module loading in meego should be done just by enumeration by
> > kernel only.
> >
> >
>
> if it's machine specific you can always use the DMI entries to match the
> specific machine
> this is done by for example the thinkpad fan drivers, and a series of
> others....
>
> they do it like this:
>
>
> /*
> * DMI matching for module autoloading
> *
> */
> #define IBM_BIOS_MODULE_ALIAS(__type) \
> MODULE_ALIAS("dmi:bvnIBM:bvr" __type "ET??WW*")
Thanks! The module now loads automatically at boot. I added the relevant
module_alias and it's ok.
I also added the relevant entry in the dmi lookup section of the driver
so that the netbook no longer needs a /etc/modprobe.d entry.
Still the bluetooth panel does not work after boot, as
from /var/log/messages you see the omnibook module loading, then this:
[...]
[ 24.677324] bluetoothd[412]: segfault at 0 ip b7435a70 sp bfee2ed8
error 4 in
libc-2.11.90.so[b73b9000+194000]
[ 24.677359] bluetoothd/412: potentially unexpected fatal signal 11.
[ 24.677366] code at b7435a70: 66 0f 74 06 66 0f d7 d0 83 c6 10 85 d2
75 2d 66
[ 24.677397] Modules linked in: omnibook ath9k battery ath9k_common
uvcvideo ath9k_hw joydev
[ 24.677418]
[ 24.677427] Pid: 412, comm: bluetoothd Not tainted
2.6.35.3-12.1-netbook #1 KAVAA/TOSHIBA NB200
[ 24.677436] EIP: 0073:[<b7435a70>] EFLAGS: 00010246 CPU: 1
[ 24.677446] EIP is at 0xb7435a70
[ 24.677453] EAX: 00000000 EBX: b75bdff4 ECX: 00000000 EDX: 00000000
[ 24.677460] ESI: 00000000 EDI: 00000020 EBP: bfee2f38 ESP: bfee2ed8
[ 24.677468] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
[ 24.677477] Process bluetoothd (pid: 412, ti=f693c000 task=f69b11b0
task.ti=f693c000)
[...]
Unloading and loading manually the driver with modprobe makes the
bluetooth panal available again.Anyone can see a reason?
I can't say if the bluetoothd issue is Meego related or still a flaw in
the driver. I'm going to see if this code can be useful to the original
author, and I'd love to see the omnibook module in the meego kernel.
GD
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
