Re: 2.6.4 and i2c-keywest
On Mon, 2004-03-22 at 20:00, Alain Perry wrote:
> Hi list,
> I recently compiled a 2.6.4 kernel from mainstream.
> I first had compiled the radeonfb driver as a module, which turned out
> to be a big mistake, so I compiled again, setting it as static.
> Now, nearly everything is fine. However, I'm using a PB 15" and I can't
> use the i2c devices anymore.
> This is the state of my modules when boot sequence is complete:
> sensei@electron:~$ lsmod | grep i2c
> i2c_dev 11680 4
> i2c_keywest 11492 0
> sensei@electron:~$ cat /dev/i2c-0
> cat: /dev/i2c-0: Remote I/O error
> sensei@electron:~$ cat /dev/i2c-1
> cat: /dev/i2c-1: Remote I/O error
> I can "modprobe -r" i2c-dev and i2c-keywest with no problem, however, if
> I try to "modprobe" i2c-keywest back in, the modprobe process seems to
> wait forever and is invincible (with normal "kill" means anyway).
> If I then open a new terminal, and try to "cat" one of the i2c devices,
> I get the same result as for the modprobe process...
> I think I am going to try to build it again with i2c-keywest statically
> linked, but I'd like to have a clue if it's a good idea... I don't
> really want my kernel to hang while booting...
I'm not sure if this can help:
Profile, Links: http://profiles.yahoo.com/wolfgangpfeiffer