Accelerometer problems - Page 2 - maemo.org

Active Topics

Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 10 hrs ago
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 11 hrs ago
Maemo repository (3)
to Community by torsen - 3 days, 3 hrs ago
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days ago
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 7 hrs ago
more...

Page 2 of 2

< Prev

Thread Tools

benjo	2009-12-20 , 02:29
Posts: 4 \| Thanked: 0 times \| Joined on Dec 2009	#11

Originally Posted by kwotski

Or before restart, try

lsmod | grep lis302

lsmod lists the loaded kernel modules (=drivers).

Did this before restart - response was

lis302dl 6784 0

Not sure what that means, although maybe it means the driver exists? What does 6784 0 mean?

Originally Posted by kwotski

What you might try is restart the N900 and then run the command

dmesg | grep lis302

from x-teminal (you might need to be root) This might show startup messages to do with that driver.

Did this after restart. Got no message at all (not even an error message) - just went straight to the next line where i can enter another command.

Originally Posted by kwotski

Alternatively

dmesg | more

and visually inspect to see if you can see any messages related to the lis302dl driver (that's the name of the accelerometer chip I think)

Did this, went through the massive list of message about all sorts of components and drivers and their status but no mention of the lis302dl driver.

Does this mean my phone doesn't have the driver for the accelerometer? If yes, how do I get it?

Quote & Reply |

benjo	2009-12-20 , 02:36
Posts: 4 \| Thanked: 0 times \| Joined on Dec 2009	#12

omg it's working now! I read back my response and realised that the message before restart seemed to be different to after restart, so i tried attitude and it worked. Then tried Bounce and that worked too.

I'm not sure if it was anything i did in x-terminal, or if it was just the restart, but it's working now so I'm very relieved. Thanks kwotski for your help.

Ben

Quote & Reply |

kwotski	2009-12-20 , 03:16
Posts: 236 \| Thanked: 223 times \| Joined on Oct 2009 @ NE UK	#13

Glad to hear it's working, I guess the restart did the trick.

The lsmod output means the driver called lis302dl is loaded, taking up 6784 bytes of ram, and used by no other drivers.

The dmesg thing - I was just guessing you might see some signon by the driver. My own N900 has been up too long to check how it signs on. Usually, the driver name would appear when it loads or if there are problems (which I thought you might see, TBH

)

I guess something upset it and the driver conked out, which was fixed by your rebooting. The special files I refered to in my other post should be there now, I expect?