You are not logged in.

#1 2010-04-29 13:56:37

MadCat_X
Member
Registered: 2009-10-08
Posts: 189

Omnibook module not working since 2.6.33.3

Hello folks,

I've just updated my system to Xorg 1.8 and the recent kernel. I use custom built kernel with ck patches and slightly altered config which has been working just fine till the recent update to 2.6.33.3. I recompiled the omnibook module I obtain from omnibook-svn AUR package like I always do, but when I try to load the module, I get "SIGKILL" message in the terminal. My dmesg output looks like this.

omnibook: Driver version 2.20090707-trunk.
omnibook: Forced load with EC type 12.
omnibook: Begin table match of ac feature.
omnibook: Returning table entry nr 0.
omnibook: Begin table match of battery feature.
omnibook: Returning table entry nr 0.
BUG: unable to handle kernel paging request at 000000000000b800
IP: [<ffffffff8116b577>] strnlen+0x7/0x40
PGD b0143067 PUD b487e067 PMD 0 
Oops: 0000 [#1] PREEMPT SMP 
last sysfs file: /sys/devices/platform/coretemp.0/temp1_input
CPU 0 
Pid: 6325, comm: modprobe Tainted: P           2.6.33.3-ARCHMOD #1 KSRAA/Qosmio X300
RIP: 0010:[<ffffffff8116b577>]  [<ffffffff8116b577>] strnlen+0x7/0x40
RSP: 0018:ffff8800b8725bd0  EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffffffff81545d20 RCX: 0000000000000000
RDX: 000000000000b800 RSI: ffffffffffffffff RDI: 000000000000b800
RBP: ffffffff81545942 R08: 00000000ffffffff R09: 00000000ffffffff
R10: ffff8800b8725d68 R11: 0000000000000000 R12: 000000000000b800
R13: 0000000000000000 R14: 00000000ffffffff R15: 00000000ffffffff
FS:  00007fbe549d5700(0000) GS:ffff880028200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000000b800 CR3: 00000000b4a17000 CR4: 00000000000406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 6325, threadinfo ffff8800b8724000, task ffff88009f948ca0)
Stack:
 ffffffff8116c104 ffffffffa0bd288e 0000000000000004 00000000ffffffff
<0> ffffffff81545942 ffffffff81545d20 ffffffff8116ce46 00000000ffffffff
<0> ffffffff8116bfd9 ffff8800b8725d68 ffffffff00000000 ffffffffa0bd288c
Call Trace:
 [<ffffffff8116c104>] ? string+0x34/0xf0
 [<ffffffff8116ce46>] ? vsnprintf+0x4a6/0xbd0
 [<ffffffff8116bfd9>] ? number+0x2b9/0x2f0
 [<ffffffff81166130>] ? idr_get_empty_slot+0x110/0x2d0
 [<ffffffff8116d679>] ? vscnprintf+0x9/0x20
 [<ffffffff81036a18>] ? vprintk+0xf8/0x470
 [<ffffffff81166444>] ? ida_get_new_above+0x154/0x1d0
 [<ffffffff81166692>] ? idr_pre_get+0x52/0x90
 [<ffffffff812c547b>] ? printk+0x40/0x45
 [<ffffffffa0bda151>] ? omnibook_probe+0x10d/0x3c0 [omnibook]
 [<ffffffff811f8bb4>] ? driver_probe_device+0x84/0x180
 [<ffffffff811f8d50>] ? __device_attach+0x0/0x60
 [<ffffffff811f79cc>] ? bus_for_each_drv+0x5c/0x90
 [<ffffffff811f8a85>] ? device_attach+0x85/0x90
 [<ffffffff811f8315>] ? bus_probe_device+0x25/0x40
 [<ffffffff811f6312>] ? device_add+0x4d2/0x5c0
 [<ffffffff811fa568>] ? platform_device_add+0xe8/0x1b0
 [<ffffffffa0bda439>] ? omnibook_module_init+0x0/0x117 [omnibook]
 [<ffffffffa0bda527>] ? omnibook_module_init+0xee/0x117 [omnibook]
 [<ffffffff81000324>] ? do_one_initcall+0x34/0x1a0
 [<ffffffff8106681c>] ? sys_init_module+0xdc/0x250
 [<ffffffff81002deb>] ? system_call_fastpath+0x16/0x1b
Code: 00 00 00 00 31 c0 80 3f 00 74 14 48 89 f8 66 0f 1f 44 00 00 48 ff c0 80 38 00 75 f8 48 29 f8 f3 c3 0f 1f 00 31 c0 48 85 f6 74 2c <80> 3f 00 74 27 48 ff ce 48 89 f8 eb 0c 0f 1f 40 00 48 ff ce 80 
RIP  [<ffffffff8116b577>] strnlen+0x7/0x40
 RSP <ffff8800b8725bd0>
CR2: 000000000000b800
---[ end trace a738b63e64c99f80 ]---
note: modprobe[6325] exited with preempt_count 2
CE: hpet increasing min_delta_ns to 33750 nsec

The /proc/omnibook directory is present, but there are only the "ac" and "battery" entries which is completely insufficient. What's most surprising is that both of these entries give me correct info. i.e. "cat /proc/omnibook/battery" tells me how is the batt charged and stuff. I used to have "wifi", "bluetooth", "thorttling" and possibly few other entries there which are just gone now and I'd really like to get them back. I have GCC 4.5 as a default compiler BTW. Anyone with the same issue?

Offline

#2 2010-05-01 11:52:06

MadCat_X
Member
Registered: 2009-10-08
Posts: 189

Re: Omnibook module not working since 2.6.33.3

OK, since I really need this thing to be working, I tried compiling completely vanilla kernel and reverting any changes I made in .config, but it is still a no go. Right now I'm suspecting GCC 4.5 for compiling the omnibook module wrong.
Is there anyone who can confirm that the omnibook module is working for him on 2.6.33.3? Thank you...

Offline

#3 2010-05-08 20:43:05

Inso
Member
Registered: 2009-11-10
Posts: 13

Re: Omnibook module not working since 2.6.33.3

I got the same problem. If anyone has a fix, thanks a lot...

Maybe we could try to compile it with GCC 4.4 ?

Offline

#4 2010-05-08 21:49:55

MadCat_X
Member
Registered: 2009-10-08
Posts: 189

Re: Omnibook module not working since 2.6.33.3

One of my desperate attempts to get it working involved getting GCC 4.3 from AUR and using it to compile the module.. no luck! I tried messing around with the CFLAGS, no luck again. What model of laptop you have Inso, perhaps it's something specific to certain models? Anyway, I finally gave up on this. Good news is that WiFi and Bluetooth works out of the box, so you don't really need omnibook module anymore. The only reason I want this working so badly is that this module can disable pretty stupid CPU throttling Im experiencing.

BTW, I filed a bug report here, so you might post your findings there and maybe someone will eventually fix it...

Last edited by MadCat_X (2010-05-08 21:51:10)

Offline

#5 2010-05-08 21:56:35

Inso
Member
Registered: 2009-11-10
Posts: 13

Re: Omnibook module not working since 2.6.33.3

sad

I need it too, because my fans or working at 100% without this module. I got my wifi out of the box, but my battery is being consume so fast...

I have a Toshiba A300D.

Offline

Board footer

Powered by FluxBB