lenovo 3000 n100 custom bios

As one may know, Lenovo 3000 n100 has broken DSDT ACPI table, and as result it reports battery status incorrectly, i.e. BIOS says 'hey, battery status is 20%!', but actually it's 0%, and laptop will shutdown in few minutes. Lenovo engineers were stupid enought to hardcode some values instead of querying smart battery. You can easily check if your laptop is affected:

$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 5200 mAh
last full capacity: 5200 mAh

See? 'design capacity' and 'last full capacity' are hardcoded. Also BIOS reports incorrect values for 'present rate' and 'present voltage' in /proc/acpi/battery/BAT1/state. Here's how these values should look like:

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate: 1875 mA
remaining capacity: 4378 mAh
present voltage: 12285 mV

$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 5183 mAh
last full capacity: 4517 mAh

In July'09 I wrote a post how to fix it via custom DSDT, but it requires kernel patching and it's not easy/userfriendly, especially in non-source-based distros. And I pretty sure it's not possible in MS Windows (tm)

Last night I got BIOS for my laptop fixed (at last!). I've used Phoenix BIOS editor to perform modifications, main problem was PBE fails to disassemble DSDT table (ad.exe crashes), but workaround is easy - PBE unpacks bios into Program Files/Phoenix Bios Editor/TMP, just take ACPI0.aml from it, disassemble/modify/compile it via iasl, and put it back into this directory. Then just build BIOS and flash it via phlash16 from freedos liveusb :) That's it! No need in putting custom DSDT table into kernel (or initramdisk for old kernels - but it is not working anymore - patch was rejected by kernel developers).

You can take fixed bios here. It can be used with Lenovo 3000 N100 with AD codec (not suitable for laptops with realtek codec).

Disclaimer: I'm not responsible for any damage you can done to your laptop by following these instructions/flashing my custom BIOS

Comments

Post a Comment

Popular posts from this blog

Access point with Raspberry Pi and rtl8192cu dongle

On Thursday ethernet ports (WAN and LAN1-4) in my Asus WL500GPv1 router have completely died, so I needed a replacement. Hopefully, recently I've got Raspberry Pi, so I decided to use it as a router. I've got TP-LINK TL-WN821NC USB stick from local store which is based on RTL8192CU chipset. Unfortunately, its driver doesn't work with vanilla hostapd, but requires patched ancient version of hostapd from Realtek . I'm using Archlinux on my rpi and I've found manual how to setup AP using this USB stick  here , but I don't want to overwrite binaries from repository packages, since it's not a sane way, and it can (and will) be broken by hostapd update. So I prepared a package, here's source package (just unpack it and build with makepkg directly on rpi), and here's binary package for armv6h (you can install it with pacman -U). I can't put PKGBUILD in AUR, since there's no stable hosting for Realtek's hostapd. If anyone is willing to host
Read more

Wayland and software rendering

Image
Recently I spent few evenings for hacking wayland . I like idea of wayland - rendering is done completely on client (in whatever way), compositor (server part) is responsible in rendering buffers from clients on the screen. Issue for me was rendering part of weston (reference compositor for wayland) - it uses GLES for compositing, but I want to try wayland and weston on devices without hw acceleration (pure software rendering), and running software GL on PXA270@312MHz does not sound like a good idea, does it? :) So I asked on #wayland@irc.freenode.org if it possible to implement software renderer, Kristian Høgsberg (khr) responded that in master branch of weston repo there's a nice abstraction of renderer, so it's possible to implement pixman renderer. So I did :) weston with x11-backend and pixman renderer khr and pq from #wayland were very helpful, and described place of renderer in wayland architecture, here're some points renderer just performs rendering of
Read more

OLED brightness in Linux

Recently I've got a new laptop with OLED panel only to find out that brightness control for OLED panels is not yet supported in Linux. Archlinux wiki page mentions using gamma ramp for controlling perceived brightness using hackish userspace tools (icc-brightness), so my first thought was to implement a hack for i915 driver to expose backlight interface that actually adjusts gamma ramp. So I went to #dri-devel to ask around whether this idea sounds too crazy and it turned out that there are better ways than using gamma ramp. Basically if you use gamma ramp you essentially reduce dynamic range, i.e. if you have 8 bits per pixel at 50% brightness you would get 7 bit, at 25% - 6 bit and that will result in banding artefacts at low brightness levels. To overcome that issue OLED panels actually have an interface to control brightness. There are at least 2 competing "standards" - VESA and Intel proprietary. First one is already supported by i915 driver while latter is not. Unfo
Read more