Toshiba Portege R100 no more acpi support under 9.10

Bug #471934 reported by betzi
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Today i installed Ubuntu Karmic Koala 32bit 9.10. To add manually some files (with triggers to some acpi events from my fn-keys) in /etc/acpi/event i wanted to read the acpi_event numbers of the keys, but when i started "acpi_listen" in a terminal, no acpi_events came up while pushing the FN combinations. Only FN-F5 is triggered to an video event and listed in acpi_listen. In 8.10 (and earlier) everything worked fine... How can i solve this problem? The machine is a Toshiba Portege R100.

Tags: hw-specific
Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information as separate attachments:
 * Output of uname -a
    * uname -a > uname.txt
 * Output of sudo lspci -vvnn
    * sudo lspci -vvnn > lspci.txt
 * Output of sudo dmidecode
    * sudo dmidecode > dmidecode.txt
 * Try to suspend/hibernate and then restart the system and attach /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * cp -r /proc/acpi /tmp
    * tar -cvjf ~/acpi.tar.bz /tmp/acpi
    * attach acpi.tar.bz from your home directory

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
betzi (s-betzinger) wrote :
Revision history for this message
betzi (s-betzinger) wrote :
Revision history for this message
betzi (s-betzinger) wrote :
Revision history for this message
betzi (s-betzinger) wrote :
Revision history for this message
betzi (s-betzinger) wrote :
Revision history for this message
Victor Vargas (kamus) wrote :

Thanks betzi, have you tried to pass "lapic" parameter to kernel boot?

Revision history for this message
betzi (s-betzinger) wrote :

Thanks Kamus for fast response! I tested lapic paramter under 9.04 and earlier versions of ubuntu, but my machine does not support lapic (heading to some google hits, too). Do you need any logfiles with lapic set as a boot parameter?

Revision history for this message
RivalComp (rival) wrote :

Same history here. :( Jaunty had no problem, Karmic has no response to ACPI events. Installed "toshutils", "toshset", "fnfxd" and "acpi-support".

Revision history for this message
betzi (s-betzinger) wrote :

Hi RivalComp BT.,
do you get ACPI-events pushing the fn-key combinations while "acpi_listen" is running? Can you post the same logs i posted for better analyses of the problem?
Thanks a lot!

Changed in linux (Ubuntu):
assignee: nobody → betzi (s-betzinger)
Revision history for this message
RivalComp (rival) wrote :

Hi, I only get ACPI event when:

pushing Fn-F5: video VGA 00000080 00000000
closing lid: button/lid LID 00000080 00000003
opening lid: button/lid LID 00000080 00000004
from battery1: battery BAT1 00000080 00000001
from battery2: battery BAT2 00000080 00000001

Now I resumed from standby mode, and screen lighting is very dark (I think it's on minimum), and I can't change it.

<off>
The other thing is that resuming from standby causes the desktop zooming in the top left corner, so I have to change to text mode terminal Ctrl-Alt-F1 and change back to X Alt-F7. There is a line "set gfxpayload=1024x768x16" before "linux" command, so everything is fine until I go to standby mode and resume from that. Text mode terminal switches back to 640x480x8, which causes the zoom issue.
</off>

I'm going to attach those logs now...

Revision history for this message
RivalComp (rival) wrote :
Revision history for this message
RivalComp (rival) wrote :
Revision history for this message
RivalComp (rival) wrote :
Revision history for this message
RivalComp (rival) wrote :
Revision history for this message
RivalComp (rival) wrote :

Sorry, my previously attached kern.log contained only the last session, I cut too much from it. This has more details...

Revision history for this message
RivalComp (rival) wrote :
Revision history for this message
betzi (s-betzinger) wrote :

RivalComp,
i attached my running xorg.conf. With this xorg.conf, the standby resolution problem should be solved.

Revision history for this message
RivalComp (rival) wrote :

I've tried adding "lapic" to /etc/default/grub: GRUB_CMDLINE_LINUX="vga=791 lapic"
after restarting there is no change in the user experience :)

Only changes I've found are the following in the kern.log:

[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[ 0.000000] APIC: disable apic facility
[ 0.000000] nr_irqs_gsi: 16

changed to:

[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- reenabling.
[ 0.000000] Found and enabled local APIC!
[ 0.000000] nr_irqs_gsi: 16

Revision history for this message
RivalComp (rival) wrote :

Thank you betzi, your xorg.conf had two lines: one of them solved my X resolution problem: Option "DPMS" and Screen 0. But text mode terminal still switching back to 640x480 after resuming from standby mode. But it's not a problem when lid lighting is working only at minimum power after resuming from standby. I have to use normal shut down...

Revision history for this message
WIlson Morgado (wilsonblogue) wrote :

Same problem here. My Fn keys don't work.

Revision history for this message
betzi (s-betzinger) wrote :

Are there no more suggestions from the ubuntu-development team?
With every new release of ubuntu the support for Toshiba Portege R100 is reduced.
Can you at least tell us why the ACPI Support under Karmic Koala is not given anymore? Can the problem be solved with a manipulated self compiled kernel?
Please give us any suggestions you have to test it with our notebooks. I wanna use Ubuntu 9.10 with my machine...

Revision history for this message
RivalComp (rival) wrote :

I hope I could use my R100 notebook with newer Ubuntu releases, but as betzi said there are more and more bugs and failures that don't allow to use it normally with this Linux distro.

The last Ubuntu release was around version 7 or early 8 that could use most of this notebook's features (mainly ACPI functions, hotkeys, standby and hibernating). A 1GHz Pentium M CPU and a 32MB Trident VGA aren't so powerful, but are enough for internet browsing, mailing, photo editing and viewing, HTML coding... and has long (~6 hours) battery life, like those new netbooks. I've upgraded it with a 1,8" 80GB HDD, draft n mini-PCI wifi, and +1GB DDR RAM... so I love it, and I'd like to use it as long as possible. I would prefer freedom, so I prefer linux. Now I have to use Windows to get full compatibility... :(

If there are some hope to fix incompatibility problems with this R100 and other older Toshiba models, let us know...

Gary M (garym)
tags: added: hw-specific
tags: added: regression-potential
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
assignee: betzi (s-betzinger) → nobody
tags: removed: regression-potential
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.