| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added bug |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'BootDmesg.txt' (BootDmesg.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'CurrentDmesg.txt' (CurrentDmesg.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'Dependencies.txt' (Dependencies.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'HalComputerInfo.txt' (HalComputerInfo.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'LsUsb.txt' (LsUsb.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'Lspci.txt' (Lspci.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'ProcCpuInfo.txt' (ProcCpuInfo.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'ProcInterrupts.txt' (ProcInterrupts.txt) |
| 2008-11-11 08:34:26 |
Margate |
bug |
|
|
added attachment 'ProcModules.txt' (ProcModules.txt) |
| 2008-11-11 08:51:57 |
Margate |
description |
I have a few keys where the most important is Fn-F1 (wireless) where don't work
Doing research on my wifi I found out that I can't turn wifi on with Fn-F1.
lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
Looking at the output from "watch 'cat /proc/interrupts'" key presses increased the i8042 counter for the following key combinations
Fn-F1 Wireless, No interrupt received
Fn-F2 (No function)
Fn-F3 Audio on/off, Working
Fn-F4 Audio Down, Working
Fn-F5 Audio Up, Working
Fn-F6 Toggle mouse, Working
Fn-F7 Toggle Webcam, Working
Fn-F8 Lower Screen Light (not happening, but interrupt received)
Fn-F9 Raise Screen Light (not happening, but interrupt received)
Fn-F10 Switch Display, No interrupt received
Fn-F11 Fan, No interrupt received
Fn-F12 Standby, Working
Using xev don't provide much information, except for focusout on funcions there make onscreen notification like Audio
I know there a lots of wifi related issues, but this labtop is the only one there don't give a interrupt when i press the wireless key and that point to kernel i think. :o))
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: fglrx
Package: linux-image-2.6.27-7-generic 2.6.27-7.16
ProcCmdLine: User Name=UUID=1fba9a6d-c254-4796-9526-82f99478256a ro quiet splash
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=da_DK.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-7.16-generic
SourcePackage: linux |
I have a few keys where the most important is Fn-F1 (wireless) there don't work
Doing research on my wifi I found out that I can't turn wifi on with Fn-F1.
lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
Looking at the output from "watch 'cat /proc/interrupts'" key presses increased the i8042 counter for the following key combinations
Fn-F1 Wireless, No interrupt received
Fn-F2 (No function)
Fn-F3 Audio on/off, Working
Fn-F4 Audio Down, Working
Fn-F5 Audio Up, Working
Fn-F6 Toggle mouse, Working
Fn-F7 Toggle Webcam, Working
Fn-F8 Lower Screen Light (not happening, but interrupt received)
Fn-F9 Raise Screen Light (not happening, but interrupt received)
Fn-F10 Switch Display, No interrupt received
Fn-F11 Fan, No interrupt received
Fn-F12 Standby, Working
Using xev don't provide much information, except for focusout on funcions there make onscreen notification like Audio
I know there a lots of wifi related issues, but this labtop is the only one there don't give a interrupt when i press the wireless key and that point to kernel i think. :o))
in /var/log/syslog
setkeycodes on e071/e072 happens when i press Fn-F6 (Mouse toggle)
setkeycodes on e029 happens when I press Fn-F10 (Screen)
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: fglrx
Package: linux-image-2.6.27-7-generic 2.6.27-7.16
ProcCmdLine: User Name=UUID=1fba9a6d-c254-4796-9526-82f99478256a ro quiet splash
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=da_DK.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-7.16-generic
SourcePackage: linux |
|
| 2008-11-11 10:47:49 |
arno_b |
linux: status |
New |
Incomplete |
|
| 2008-11-11 10:47:49 |
arno_b |
linux: bugtargetdisplayname |
linux (Ubuntu) |
acpi (Ubuntu) |
|
| 2008-11-11 10:47:49 |
arno_b |
linux: bugtargetname |
linux (Ubuntu) |
acpi (Ubuntu) |
|
| 2008-11-11 10:47:49 |
arno_b |
linux: statusexplanation |
|
|
|
| 2008-11-11 10:47:49 |
arno_b |
linux: title |
Bug #296663 in linux (Ubuntu): "Fn-F1 (wireless does not work on FSC Amilo Pa 3515" |
Bug #296663 in acpi (Ubuntu): "Fn-F1 (wireless does not work on FSC Amilo Pa 3515" |
|
| 2008-11-11 21:22:22 |
arno_b |
acpi: status |
Incomplete |
New |
|
| 2008-11-12 11:54:49 |
Chris Coulson |
acpi: bugtargetdisplayname |
acpi (Ubuntu) |
hal-info (Ubuntu) |
|
| 2008-11-12 11:54:49 |
Chris Coulson |
acpi: bugtargetname |
acpi (Ubuntu) |
hal-info (Ubuntu) |
|
| 2008-11-12 11:54:49 |
Chris Coulson |
acpi: statusexplanation |
|
This is not a bug in the acpi source package, as that only contains some utilities for inspecting parameters from the ACPI subsystem.
Your dmesg shows a lot of unrecognised keys. As your wlan is likely to be one of these, I'm reassinging to hal-info for now, as this is usually solved by adding HAL quirks for your laptop. Could you please attach the output of "lshal" to this bug report, and also do the following:
1) Open a terminal and run "tail -f /var/log/kern.log"
2) Press your non-functioning key.
3) Copy the output from the terminal to this bug report. It should be similar to the following output, and will enable us to identify which scancode belongs to your wlan key:
[ 1007.886000] atkbd.c: Unknown key released (translated set 2, code 0xf2 on isa0060/serio0).
[ 1007.886014] atkbd.c: Use 'setkeycodes e072 <keycode>' to make it known. |
|
| 2008-11-12 11:54:49 |
Chris Coulson |
acpi: title |
Bug #296663 in acpi (Ubuntu): "Fn-F1 (wireless does not work on FSC Amilo Pa 3515" |
Bug #296663 in hal-info (Ubuntu): "Fn-F1 (wireless does not work on FSC Amilo Pa 3515" |
|
| 2008-11-12 11:55:04 |
Chris Coulson |
hal-info: status |
New |
Incomplete |
|
| 2008-11-12 11:55:04 |
Chris Coulson |
hal-info: statusexplanation |
This is not a bug in the acpi source package, as that only contains some utilities for inspecting parameters from the ACPI subsystem.
Your dmesg shows a lot of unrecognised keys. As your wlan is likely to be one of these, I'm reassinging to hal-info for now, as this is usually solved by adding HAL quirks for your laptop. Could you please attach the output of "lshal" to this bug report, and also do the following:
1) Open a terminal and run "tail -f /var/log/kern.log"
2) Press your non-functioning key.
3) Copy the output from the terminal to this bug report. It should be similar to the following output, and will enable us to identify which scancode belongs to your wlan key:
[ 1007.886000] atkbd.c: Unknown key released (translated set 2, code 0xf2 on isa0060/serio0).
[ 1007.886014] atkbd.c: Use 'setkeycodes e072 <keycode>' to make it known. |
|
|
| 2009-07-07 19:54:26 |
Manoj Iyer |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2010-06-14 22:56:06 |
Jeremy Foshee |
tags |
apport-bug |
apport-bug kj-expired |
|
| 2010-06-14 22:56:12 |
Jeremy Foshee |
linux (Ubuntu): status |
Incomplete |
Expired |
|
| 2011-03-25 18:52:24 |
George Giannakidis |
removed subscriber George Giannakidis |
|
|
|
