here is what I get
Code:
root@burnt:~# dmesg | grep omnibook
[ 1851.498000] omnibook: Driver version 2.20060921.
[ 1851.498000] omnibook: Toshiba Satellite M40 detected.
[ 1851.501000] omnibook: Enabling all hotkeys.
[ 1851.507000] omnibook: Enabled features: bluetooth display hotkeys version dmi lcd wifi.
bluetooth
if enabled in windows, then works pretty well
Code:
matteo@burnt:~$ sudo hcitool dev
Password:
Devices:
hci0 aa:bb:cc:dd:ee:ff
matteo@burnt:~$ sudo hcitool scan
Scanning ...
11:22:33:44:55:66 Shiny dog
omnibook lets me shotdown it but then it doesn't wake up anymore
Code:
root@burnt:~# echo 0 > /proc/omnibook/bluetooth
root@burnt:~# echo 1 > /proc/omnibook/bluetooth
root@burnt:~# cat /proc/omnibook/bluetooth
Bluetooth adapter is present and disabled.
display
Code:
root@burnt:~# cat /proc/omnibook/display
Internal LCD: port enabled
External VGA: port disabled
External TV-OUT: port disabled
I don't have the hardware to test it with right now
hotkeys
Code:
root@burnt:~# cat /proc/omnibook/hotkeys
Fn hotkeys are enabled.
Stick key is disabled.
Press Fn twice to lock is disabled.
Dock events are enabled.
Fn + F5 hotkey is enabled.
it seems like working, but xev doesn't catch any..
dmi
root@burnt:~# cat /proc/omnibook/dmi
BIOS Vendor: TOSHIBA
BIOS Version: Version 1.10
BIOS Release: 09/26/2005
System Vendor: TOSHIBA
Product Name: Satellite M40
Version: PSM42E-01E00MIT
Serial Number: X5130222Q
Board Vendor: TOSHIBA
Board Name: Version A0
lcd
works very well
Code:
root@burnt:~# echo 1 > /proc/omnibook/lcd
root@burnt:~# echo 7 > /proc/omnibook/lcd
but I would love to bind it to Fn keys, since they do not work
wifi
works
Code:
root@burnt:~# cat /proc/omnibook/wifi
Wifi adapter is present and disabled.
Wifi Kill switch is on.
root@burnt:~# echo 1 > /proc/omnibook/wifi
root@burnt:~# echo 1 > /proc/omnibook/wifi
root@burnt:~# cat /proc/omnibook/wifi
Wifi adapter is present and enabled.
Wifi Kill switch is on.
root@burnt:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=20.4 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=272 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=3.22 ms
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 3.223/98.567/272.054/122.874 ms
root@burnt:~# echo 1 > /proc/omnibook/bluetooth
root@burnt:~# cat /proc/omnibook/bluetooth
Bluetooth adapter is present and disabled.
I think I should definitely try the svn version.
About the garbled thing, I would start another thread because in my opinion it is a different topic. I can tell you that I always had it, since breezy when I didn't know about omnibook. If it happens at after boot, you can ctrl+alt+f1 - ctrl+alt+f7 as many times as you need to see X properly.