You are not logged in.

#1 2012-10-13 03:02:02

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

[Solved] BAT* devices not detected after BIOS update

I updated by Toshiba L750D (PSK36A) to BIOS 2.1 from BIOS 2.0 using Windows.

I'm now back inside my preference OS, Arch Linux, however it seems there are no BAT devices at all in /sys/class/power_supply/ (there used to be a BAT1). Hence, I can no longer detect my battery life.

I thought it may be an Arch Linux problem so I downloaded and booted the Ubuntu CD to see if it made a difference but the same problem was observed on Ubuntu so I assume its a linux-wide problem with my laptop after the bios update. I tried flashing the new BIOS a few more times - doesn't make a difference. Unfortunately I cannot downgrade.

Are there any obvious solutions I can try?

---

I attempted this fix but never got past compiling the new DSDT because I got 110 errors;
http://techinterplay.com/fix-toshiba-ba … linux.html

I'm not sure that article is relevant, as I was unable to find the text he mentioned to search for in my models DSDT.

---

Update: 8 Nov 2012, this is still occurring and I'm still looking for a fix sad

---

Issue solved, scroll down to bottom.

Last edited by kvanberendonck (2012-11-11 02:10:30)

Offline

#2 2012-10-13 03:12:19

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

Was the battery there in windows?  Also, typically you can downgrade, it is just not simple like the windows based upgrade.

Offline

#3 2012-10-13 03:18:11

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

Yes, the battery was there before/after in Windows.

I have the knowledge to downgrade, however the file is obscure and Toshiba removed it from their site. I contacted support and they refused to give it to me. Searched the internet for a few hours and found no traces of any mirror.

Offline

#4 2012-10-13 03:20:50

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

They refused to give it to you... that is really rediculous.  I'd like to apologize for Toshiba being so f*cking stupid about that.

Offline

#5 2012-10-13 03:26:59

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

WonderWoofy wrote:

They refused to give it to you... that is really rediculous.  I'd like to apologize for Toshiba being so f*cking stupid about that.

Yeah, it sucks. I definitely won't be buying Toshiba ever again. I heard Lenovo has excellent Linux support, might consider getting one in 6 months or so if I find a cheap ideapad.

Up until now though, I've had endless problems. The Fn keys don't send scancodes, KMS doens't work with either propriety or open source, dual-head crashes on my APU even after correct setup, only sound device recognized in alsa is the pcspkr "blip" device.. etc. While I can live with the other issues, I can't live without a battery because I actually take my laptop to uni lectures and such. Windows doesn't spin down the hdd and hence makes too much noise for the people around me :\

Offline

#6 2012-10-13 03:31:00

Trilby
Forum Moderator
From: Massachusetts, USA
Registered: 2011-11-29
Posts: 13,690
Website

Re: [Solved] BAT* devices not detected after BIOS update

kvanberendonck wrote:

I heard Lenovo has excellent Linux support...

Sorry for going a bit OT - but I wanted to say this has not been my experience.  Lenovo's are wonderful computers and there are many reasons to buy one, but customer service for Linux users is not one of them in my experience.  I've been told by their reps that they refuse to offer any advice or service if I no longer have windows installed.  They also admitted to knowing about a major flaw in their hardwarebios/firmware but they chose not to correct it because it is only a problem for linux users.

Last edited by Trilby (2012-10-13 03:32:18)


InterrobangSlider
• How's my coding? See this page.
• How's my moderating? Feel free to email any concerns, complaints, or objections.

Offline

#7 2012-10-13 03:34:27

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

Wow, that does sound pretty crappy.  I will tell you that I love my thinkpad.  I even have the low end Edge E430, and it is pretty amazing.  The only thing is that they use realtek quite a bit.  While this isn't a problem for the ethernet (there is the relevent package in the repos), the Thinkpad b/g/n wifi card uses the infamous rtl8192ce module.  And you know what the three amigos say about that... its in famous.  But seriously, it was terrible, I then had to flash a none whitelisted bios so that I could install my own card.  Lenovo only allows lenovo authorized wifi cards to work.  But it works great with an Intel card now.  Also the card reader is realtek, and there is no native module for that, but fortunately there is a module you can build from the realtek site.  All in all though, it is great, and the couple of times I have had to call support, I tell them I use linux, and because they cannot log into my machine, they just trust what I tell them.  It is pretty amazing.

Edit: Wow, I have had the exact opposite experience than Trilby.  I ahve had to call twice, once for my battery, once for a power adapter, so admittedly, it was not really issues with the machine itself.  But they just ask me what is wrong, find out I am a linux user, and say "Oh, well, we will just send you the part then..."

Last edited by WonderWoofy (2012-10-13 03:40:53)

Offline

#8 2012-10-13 03:46:28

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

Thanks for the vendor advice guys smile

Still looking for a solution to the battery problem though. The laptop is only 12 months old, and given that I paid a packet for it back when APU's were first released, I'm not ready to throw it out yet :\

Offline

#9 2012-10-13 04:45:41

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,690

Re: [Solved] BAT* devices not detected after BIOS update

Can you post the output of dmesg | grep ACPI    ??


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#10 2012-10-13 04:59:32

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

ewaller wrote:

Can you post the output of dmesg | grep ACPI    ??

kyle@kyle-laptop ~ dmesg | grep ACPI
[    0.000000] BIOS-e820: [mem 0x00000000cf486000-0x00000000cf88efff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000cfbbf000-0x00000000cfebefff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000cfebf000-0x00000000cfef5fff] ACPI data
[    0.000000] ACPI: RSDP 00000000000fe020 00024 (v02 TOSQCI)
[    0.000000] ACPI: XSDT 00000000cfef5120 0007C (v01 TOSQCI TOSQCI00 00000001      01000013)
[    0.000000] ACPI: FACP 00000000cfef4000 000F4 (v04 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: DSDT 00000000cfede000 112E5 (v01 TOSQCI TOSQCI00 F0000000 ACPI 00040000)
[    0.000000] ACPI: FACS 00000000cfc97000 00040
[    0.000000] ACPI: HPET 00000000cfef3000 00038 (v01 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: APIC 00000000cfef2000 00084 (v02 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: MCFG 00000000cfef1000 0003C (v01 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: ASF! 00000000cfef0000 000A5 (v32 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: BOOT 00000000cfedd000 00028 (v01 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: SLIC 00000000cfedc000 00176 (v01 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: WDRT 00000000cfedb000 00047 (v01 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: MSDM 00000000cfeda000 00055 (v03 TOSQCI TOSQCI00 00000001 ACPI 00040000)
[    0.000000] ACPI: SSDT 00000000cfed9000 00E28 (v01 AMD    POWERNOW 00000001 AMD  00000001)
[    0.000000] ACPI: SSDT 00000000cfed7000 0193D (v02    AMD     ALIB 00000001 MSFT 04000000)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: PM-Timer IO Port: 0x408
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x10228210 base: 0xfed00000
[    0.005191] ACPI: Core revision 20120320
[    0.005342] ACPI: Forced DSDT copy: length 0x112E5 copied locally, original unmapped
[    0.275625] PM: Registering ACPI NVS region [mem 0xcf486000-0xcf88efff] (4231168 bytes)
[    0.275717] PM: Registering ACPI NVS region [mem 0xcfbbf000-0xcfebefff] (3145728 bytes)
[    0.277613] ACPI: bus type pci registered
[    0.285292] ACPI: Added _OSI(Module Device)
[    0.285296] ACPI: Added _OSI(Processor Device)
[    0.285297] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.285299] ACPI: Added _OSI(Processor Aggregator Device)
[    0.285300] ACPI: Added _OSI(Linux)
[    0.287480] ACPI: EC: Look up EC in DSDT
[    0.328586] ACPI: Executed 1 blocks of module-level executable AML code
[    0.333711] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via cmdline
[    0.334386] ACPI: Interpreter enabled
[    0.334389] ACPI: (supports S0 S3 S4 S5)
[    0.334404] ACPI: Using IOAPIC for interrupt routing
[    0.340413] ACPI: EC: GPE = 0x3, I/O: command/status = 0x66, data = 0x62
[    0.340624] ACPI: No dock devices found.
[    0.340630] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.340779] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.367355] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.367488] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PB2_._PRT]
[    0.367521] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PB4_._PRT]
[    0.367545] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PB5_._PRT]
[    0.367613] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
[    0.367677]  pci0000:00: >Requesting ACPI _OSC control (0x1d)
[    0.367680]  pci0000:00: >ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[    0.367681] ACPI _OSC control for PCIe not granted, disabling ASPM
[    0.375952] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376034] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376110] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376163] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376204] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376235] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376268] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376300] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 12 14 15) *0
[    0.376629] PCI: Using ACPI for IRQ routing
[    0.388090] pnp: PnP ACPI init
[    0.388113] ACPI: bus type pnp registered
[    0.388383] pnp 00:00: >Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[    0.388482] system 00:01: >Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.388640] pnp 00:02: >Plug and Play ACPI device, IDs PNP0103 (active)
[    0.388760] pnp 00:03: >Plug and Play ACPI device, IDs PNP0200 (active)
[    0.388819] pnp 00:04: >Plug and Play ACPI device, IDs PNP0c04 (active)
[    0.388910] pnp 00:05: >Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.388963] pnp 00:06: >Plug and Play ACPI device, IDs PNP0800 (active)
[    0.389048] pnp 00:07: >Plug and Play ACPI device, IDs PNP0303 (active)
[    0.389133] pnp 00:08: >Plug and Play ACPI device, IDs TOS0200 SYN1000 SYN0002 PNP0f13 (active)
[    0.389261] system 00:09: >Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.389348] system 00:0a: >Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.389762] pnp: PnP ACPI: found 11 devices
[    0.389764] ACPI: ACPI bus type pnp unregistered
[    1.799341] ACPI: bus type usb registered
[    6.119883] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler
[    6.162801] ACPI: acpi_idle registered with cpuidle
[    6.189958] ACPI: Power Button [PWRB]
[    6.190091] ACPI: Lid Switch [LID]
[    6.190142] ACPI: Power Button [PWRF]
[    6.550426] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000011) is beyond end of object (20120320/exoparg2-418)
[    6.550437] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UBIX] (Node ffff880203e8a168), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550443] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIX] (Node ffff880203e8a0f0), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550449] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _BIX (20120320/battery-419)
[    6.595368] ACPI: AC Adapter [ACAD] (on-line)
[    6.747736] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[    6.758044] ACPI: Thermal Zone [THRM] (55 C)
[    6.758620] ACPI: Video Device [VGA1] (multi-head: yes  rom: no  post: no)
[    7.772864] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
[    7.876001] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMBS.SMB0 1 (20120320/utaddress-251)
[    7.876019] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   19.440618] ACPI: Power Button [PWRB]
[   19.441155] ACPI: Lid Switch [LID]
[   19.441886] ACPI: Power Button [PWRF]
kyle@kyle-laptop ~ 

smile

Offline

#11 2012-10-13 05:15:39

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,690

Re: [Solved] BAT* devices not detected after BIOS update

...
[    6.550426] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000011) is beyond end of object (20120320/exoparg2-418)
[    6.550437] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UBIX] (Node ffff880203e8a168), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550443] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIX] (Node ffff880203e8a0f0), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550449] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _BIX (20120320/battery-419)
....
[    7.772864] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
[    7.876001] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMBS.SMB0 1 (20120320/utaddress-251)
[    7.876019] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
....

Well, those are the interesting lines.  I was ensuring that the toshiba_acpi module is loading.  It looks like it is.

I think your problem is related to the lines at 6.5504 seconds.  Unfortunately, I have no suggestions where to go from there sad


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#12 2012-10-13 05:27:59

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

ewaller wrote:
...
[    6.550426] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000011) is beyond end of object (20120320/exoparg2-418)
[    6.550437] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UBIX] (Node ffff880203e8a168), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550443] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIX] (Node ffff880203e8a0f0), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550449] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _BIX (20120320/battery-419)
....
[    7.772864] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
[    7.876001] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMBS.SMB0 1 (20120320/utaddress-251)
[    7.876019] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
....

Well, those are the interesting lines.  I was ensuring that the toshiba_acpi module is loading.  It looks like it is.

I think your problem is related to the lines at 6.5504 seconds.  Unfortunately, I have no suggestions where to go from there sad

Thanks for the hints.

Offline

#13 2012-10-13 06:10:51

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

Sent Toshiba support an email kindly telling them that they unintentionally dropped all linux support with their latest bios update. Having a technical nature, it might actually get forwarded to the BIOS team. On the other hand, I'll probably just get rejected again and told to buy a new laptop.

Offline

#14 2012-10-13 06:23:42

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

Sorry if I implied that your only option was to buy a new laptop.  That was not my intent.  You had mentioned hearing good things about Lenovo, so I just wanted to throw my two cents in about ThinkPads.  You have a perfectly nice machine, albiet apparently a bit of a struggle with Linux.

Offline

#15 2012-10-13 06:30:49

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

WonderWoofy wrote:

Sorry if I implied that your only option was to buy a new laptop.  That was not my intent.  You had mentioned hearing good things about Lenovo, so I just wanted to throw my two cents in about ThinkPads.  You have a perfectly nice machine, albiet apparently a bit of a struggle with Linux.

Nah, nothing to do with you. Sorry for making it feel that way, mate. It's what Toshiba told me last time I emailed them, suggesting that I should have "done more research into Linux support before purchasing my laptop" and that my best option was to buy a new laptop if I wanted support.

Offline

#16 2012-10-13 06:35:38

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

They really told you that?  That is some f*cked up sh*t!  At the very least you should probably publicize such an atrocity.  Maybe subnit it to consumerist or something...

When a company tells you that you have done something wrong in purchasing their product, I think that kind of attitude should be outted.  Just my opinion.

Offline

#17 2012-10-13 09:40:14

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

WonderWoofy wrote:

They really told you that?  That is some f*cked up sh*t!  At the very least you should probably publicize such an atrocity.  Maybe subnit it to consumerist or something...

When a company tells you that you have done something wrong in purchasing their product, I think that kind of attitude should be outted.  Just my opinion.

So here's what I did,

I grabbed a friends laptop which was exactly the same and edited the bios flash tool to dump the bios instead. I then unpacked the 2.1 bios flashing tool and replaced the bios rom image in the archive with the custom backup, ran it under windows (the tool still thinking it's flashing the other ROM), bam! Managed to get myself from 2.1 to... 1.2. Better than nothing! Everything is working fine now.

Thanks all for the help wink

---

Agh! 1.2 has HUUUGE power management issues! It's terrible! Battery drains out in half the time it did before and the processor scaling doesn't work properly. I really need to get the latest BIOS working.

Last edited by kvanberendonck (2012-11-08 06:26:55)

Offline

#18 2012-10-13 12:51:12

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,117

Re: [Solved] BAT* devices not detected after BIOS update

kvanberendonck wrote:

Sent Toshiba support an email kindly telling them that they unintentionally dropped all linux support with their latest bios update. Having a technical nature, it might actually get forwarded to the BIOS team. On the other hand, I'll probably just get rejected again and told to buy a new laptop.

No, they might tell you to use windows instead of linux.

The lines:

[    6.550426] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000011) is beyond end of object (20120320/exoparg2-418)
[    6.550437] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UBIX] (Node ffff880203e8a168), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)
[    6.550443] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIX] (Node ffff880203e8a0f0), AE_AML_PACKAGE_LIMIT (20120320/psparse-536)

really point to something, also this line made me think of something else

[    0.333711] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via cmdline

You may want to give the acpi_os_name and/or acpi_osi kernel parameters a try and see if they make any difference.

The lines following lines are probably harmless, I also have them and everything works as expected (different brand machine though).

[    7.876001] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMBS.SMB0 1 (20120320/utaddress-251)
[    7.876019] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#19 2012-11-08 06:04:22

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

R00KIE wrote:

<snip>

What parameters do you suggest I try?

I'm already using acpi_osi="Linux".

Offline

#20 2012-11-08 15:15:54

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,117

Re: [Solved] BAT* devices not detected after BIOS update

What you want is to try to spoof using windows, not telling the bios you are using linux.

Ideally those options shouldn't be needed, and telling the bios you are using linux is discouraged if I remember correctly, the reason is that it may make the bios take paths that are not properly tested and might give unexpected results, I think linux is not even reported anymore in the OS interface string due to this.

From /usr/src/linux-$(uname -r)/Documentation/kernel-parameters.txt (linux-docs package):

acpi_os_name=    [HW,ACPI] Tell ACPI BIOS the name of the OS
            Format: To spoof as Windows 98: ="Microsoft Windows"

    acpi_osi=    [HW,ACPI] Modify list of supported OS interface strings
            acpi_osi="string1"    # add string1 -- only one string
            acpi_osi="!string2"    # remove built-in string2
            acpi_osi=        # disable all strings

You may have luck with acpi_os_name, you may also try to install iasl, decompile your dsdt, see which strings are being checked and try to use one of them, I'd say use one that spoofs the windows version which you know works (just an idea, I don't know if it will work or make any difference as I have never tested it and I have no experience with it).


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#21 2012-11-08 16:18:24

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] BAT* devices not detected after BIOS update

Hey kvanberendonck, I am glad to hear that you were at least able to get your old bios flashed onto your system.  I told you it was possible!  That was a very creative solution to the downgrade issue as well.  for the Thinkpad bios updater, there is a flag to run it unattended (both from windows and from the bootable flash utility), and it is not advertised, but it actually doesn't run the version saity check.  So it will simply do it.

Is there a reason why you wanted to update the bios?  Typically it is recommended to stick with what you've got unless the new bios provides new features you want or security that is necessary.  So unless the old bios version does not have the features/stuff you want, maybe sticking with the old one is the way to go? 

BTW, I think that recommendation is because there are a lot of idiotic computer users in this world.  So there is the potential liability of having users update their bios (especailly when the computer is still under warranty).

Offline

#22 2012-11-09 00:16:55

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

WonderWoofy wrote:

Hey kvanberendonck, I am glad to hear that you were at least able to get your old bios flashed onto your system.  I told you it was possible!  That was a very creative solution to the downgrade issue as well.  for the Thinkpad bios updater, there is a flag to run it unattended (both from windows and from the bootable flash utility), and it is not advertised, but it actually doesn't run the version saity check.  So it will simply do it.

Is there a reason why you wanted to update the bios?  Typically it is recommended to stick with what you've got unless the new bios provides new features you want or security that is necessary.  So unless the old bios version does not have the features/stuff you want, maybe sticking with the old one is the way to go? 

BTW, I think that recommendation is because there are a lot of idiotic computer users in this world.  So there is the potential liability of having users update their bios (especailly when the computer is still under warranty).

Hi Woofy,

Yeah, downgrading the BIOS, while fixing Linux, gave me some terrible very noticeable power management issues and a wierd fan pulse thing that happens sometimes. I can live with it, but I'm going to give patching the DSDT a shot and see if it fixes anything.

I moved the issue, kind of, to here; https://bbs.archlinux.org/viewtopic.php … 6#p1190086

It seems to be a DSDT issue, however the DSDT for my laptop seems to be ridiculously huge and complex sad

Offline

#23 2012-11-11 02:09:58

kvanberendonck
Member
Registered: 2012-08-17
Posts: 45

Re: [Solved] BAT* devices not detected after BIOS update

Offline

Board footer

Powered by FluxBB