View Single Post
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#41
Originally Posted by Estel View Post
so, it seems that kp49 is "broken" in part concerning "evil" i2c path, and nobody found this up to date? Interesting, and quite ironically. I haven't been using kp49, so I can't confirm this - can anyone knowledgeable check how kp49 behaves here?
I can't comment on anything regarding bq27x00_battery (since I don't use the module/KP), except for what I've already stated (kernel-bfs not differentiating from kernel-power). The following however appears to be false:

Originally Posted by Estel View Post
Module is indeed loaded "out of the box"
Code:
Nokia-N900:~# uname -r
2.6.28.10-bfs7
Nokia-N900:~# lsmod | grep bq
Nokia-N900:~#
Maybe some application is modprobing the module?

Originally Posted by werks View Post
very good so far, no issues for me except for 1.

with touch screen vibration on, its not consistant. the length and strength(?) varies.
Hadn't noticed this myself since I've got touch screen vibration feedback disabled. Thanks for reporting!

Originally Posted by XeonDead View Post
In the previous thread of kernel-bfs, there was a some sort of solution - to install fcam-drivers-bfs with dpkg --auto-deconfigure, so it will not delete packages, just deconfigures. In my case, fcam-drivers-bfs only conflicts with fcam-drivers, not replaces and not provides it, so blessn900 appears to be broken(but fCam works fine).
fcam-drivers-bfs does provide and replace fcam-drivers. The command "dpkg -l | grep fcam" will show both packages, but when you run "apt-get remove fcam-drivers" you'll see that fcam-drivers isn't installed . I've renamed the fcam-drivers-bfs package to just fcam-drivers to avoid any dependency issues. The first post has been updated to include this new fcam-drivers package.
I haven't contacted the fcam-drivers maintainer yet, I will do that tomorrow. I'll keep everyone updated on this one

Originally Posted by XeonDead View Post
Update:
Uh-oh, i have just got an unexpected reboot. What even could cause it?
Are you sure the reboot is kernel-bfs related? What were you doing when this happened (you didn't happen to be doing some very I/O intensive stuff, did you?)?

--

I've also recompiled lxp's bleeding-edge wl1251 wifi driver for kernel-bfs. Look for the link in the first post of this thread if you'd like to use them .

Last edited by iDont; 2011-10-04 at 19:48.
 

The Following 8 Users Say Thank You to iDont For This Useful Post: