Reply
Thread Tools
Posts: 13 | Thanked: 5 times | Joined on Jan 2010
#41
Originally Posted by olighak View Post
The two hid modules are not installed. The other 3 are. So Nokia likely did remove the keyboard support.

Any tips on getting them back or installing them separately?

I'm quite new at this, but I've reflashed a few times so I am not too afraid at trying this and that.

Jan can you do sudo lsmod in X-Terminal and see if hid and hidp are also missing from your list of installed modules?
They weren't inserted into my kernel either, but "modprobe hid" and "modprobe hidp" inserted them readily. So the modules themselves aren't missing.

Best regards, Jan
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#42
It appears that they kernel will still support it. But something appears to have changed in the substrate that starts up bluetoothd. But I don't know enough about this to figure it out. (The init system on Maemo is different than Debian and I don't know what is starting and configuring bluetoothd.) Perhaps someone else who knows more can help.
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#43
Originally Posted by jtkim View Post
They weren't inserted into my kernel either, but "modprobe hid" and "modprobe hidp" inserted them readily. So the modules themselves aren't missing.

Best regards, Jan
Is that the actual command you write? modprobe and the module name? I am getting a modprobe not found error.

Last edited by olighak; 2010-01-24 at 02:54.
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#44
The Limux modprobe command takes a kernel module name as its argument and installs that module and all dependent modules.

But my guess is that that alone won't help. Most of the time things are set up so that modules are loaded automatically when needed. So my guess is that the init scripts for bluetoothd have changed to not start hid.
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#45
Originally Posted by olighak View Post
1. Plug your phone up to your computer and select Mass Storage mode. Open the .tar up in Winzip or another program that opens Zip files. Extract the contents to your desktop.

2. After extracting the .tar you should have a directory called xkb-chinook on your desktop. Copy that directory into the tmp folder on your N900 (which you find as a mass storage drive in windows explorer)
It is safer and easier to do this directly on the N900 rather than a Windows desktop by:

1. copying the file xkb-chinook.tar from my earlier post to /tmp on your N900.
2. then do

$ sudo gainroot
# cd /tmp
# tar xf xkb-chinook.tar
# mv -i /tmp/xkb-chinook /usr/share/X11/.
# exit

There are several reasons you want to do the above as root on a Unix/Linux machine on a Unix/Linux file system (such as ext2, ext3, ...). Among them, to preserve file/directory uids, gids, and permissions (and ctimes and mtimes while you are at it), as well as symlinks.
 
Posts: 13 | Thanked: 5 times | Joined on Jan 2010
#46
Originally Posted by olighak View Post
Is that the actual command you write? modprobe and the module name? I am getting a modprobe not found error.
You need to be root for them to work. They live in /sbin and that directory is not in the PATH of user.

The modprobe program is part of the module-init-tools package. My guess is that that's always installed but if /sbin/modprobe doesn't exist on your system, that's the package you need to install.

This won't solve the bluetooth keyboard problem, though.

Best regards, Jan
 
Posts: 65 | Thanked: 21 times | Joined on Feb 2008
#47
Originally Posted by qobi View Post
...(The init system on Maemo is different than Debian and I don't know what is starting and configuring bluetoothd.)
Code:
$ ls /etc/event.d/blue*
/etc/event.d/bluetooth-sysinfo  /etc/event.d/bluetoothd
The init system is called upstart: http://www.google.com/search?btnG=Go...arch&q=upstart

HTH
__________________
Just another perl hacker coding python in a bottle.
 
Posts: 121 | Thanked: 54 times | Joined on Oct 2007 @ New York, US
#48
qobi, you are the man!

Using your latest instructions I got my Stowaway ThinkOutside "Sierra" BT keyb to work w/ the N900, PR1.1 !!

The thing that I (somehow) missed, is that I have to type something on the INTERNAL keyboard ! So, other users, pls keep this in mind.
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#49
Originally Posted by dnastase View Post
qobi, you are the man!

Using your latest instructions I got my Stowaway ThinkOutside "Sierra" BT keyb to work w/ the N900, PR1.1 !!

The thing that I (somehow) missed, is that I have to type something on the INTERNAL keyboard ! So, other users, pls keep this in mind.
? Are you sure you are running 1.1, firmware from week 51?

If you follow the discussion and check whether hid and hidp modules are installed on your device, are they?

Did you upgrade OTA or flash to that firmware?
 
Posts: 121 | Thanked: 54 times | Joined on Oct 2007 @ New York, US
#50
Originally Posted by olighak View Post
? Are you sure you are running 1.1, firmware from week 51?

If you follow the discussion and check whether hid and hidp modules are installed on your device, are they?

Did you upgrade OTA or flash to that firmware?
Yes: 2.2009.51-1.002, upgraded OTA (app manager).

/home/user # lsmod | grep -i hid
hidp 12544 0
hid 31940 1 hidp
l2cap 21060 17 hidp,rfcomm,bnep
bluetooth 53596 10 hidp,rfcomm,sco,bnep,l2cap,hci_h4p

Did not do anything special about the modules/bluetooth. It's how it is after a reboot.
 

The Following User Says Thank You to dnastase For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 00:23.