| View previous topic :: View next topic |
| Author |
Message |
CCC_037
n00b
Joined: 14 Dec 2012
Posts: 22
|
 Posted: Wed Dec 19, 2012 4:23 pm Post subject: |
 |
|
| The kernel does not see the Fn- keypress. I tried running dmesg, waiting ten seconds, pressing Fn-, waiting ten seconds, then running dmesg again; timestamps showed a roughly 20 second gap with nothing in. Running the same test with the "increase screen brightness" command logged that keypress as expected. |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54214
Location: 56N 3W
|
| Posted: Wed Dec 19, 2012 5:46 pm Post subject: |
|
|
CCC_037,
That's useful knowledge. Fn- never gets to the kernel. That does not mean that its not generated.
Longshot: lets suppose that hardware and documentation differ, the why doesn't matter.
Press and hold Fn, now try every key in turn to see if some other Fn key combination turns on the 3G.
This key combination may or may not reach the kernel.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54214
Location: 56N 3W
|
| Posted: Wed Dec 19, 2012 6:18 pm Post subject: |
|
|
CCC_037,
I missed | Code: | [*] Maintain a devtmpfs filesystem to mount at /dev
[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs |
Did you spot that?
Both options are needed to boot.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
CCC_037
n00b
Joined: 14 Dec 2012
Posts: 22
|
| Posted: Thu Dec 20, 2012 12:40 pm Post subject: |
|
|
| NeddySeagoon wrote: | CCC_037,
I missed | Code: | [*] Maintain a devtmpfs filesystem to mount at /dev
[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs |
Did you spot that?
Both options are needed to boot. |
Hmmm. Funny; it booted fine without those options set. Nonetheless, I set them, recompiled and rebooted into the new kernel, before running the following test.
| NeddySeagoon wrote: | CCC_037,
That's useful knowledge. Fn- never gets to the kernel. That does not mean that its not generated.
Longshot: lets suppose that hardware and documentation differ, the why doesn't matter.
Press and hold Fn, now try every key in turn to see if some other Fn key combination turns on the 3G.
This key combination may or may not reach the kernel. |
In order to test this, I used the following method. I first ran:
| Code: | lspci -vvv > pci
lsusb -vvv > usb |
After every key combination, I then ran the following command:
| Code: | | lsusb -vvv > usb_new && lspci -vvv > pci_new && diff usb usb_new && diff pci pci_new |
If it turns up on the pci or usb busses, this should reveal it. (I typed it in once, and then used up/enter to re-run it).
There was no sign of the 3G device at any point.
lspci -vvv printed the following to stderr every time:
| Code: | | pcilib: sysfs_read_vpd: read failed: Connection timed out |
This happened with the "Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289" device. (I think that's my card reader).
Other results:
- The camera button added a USB webcam to the output of lsusb
- The bluetooth button added an unrecognised USB device (Bus 003 Device 011: ID 8087:07da Intel Corp. ) which, on inspection of lsusb -vvv, appears to be a bluetooth communications device.
- Fn+WinKey and Fn+RtClkKey each shunted me to a different terminal, and I had to use ctrl-alt-F1 to get back to where I was.
- Usually, Fn+(character) would output (character) on the command line. This was not the case for the (minus/underscore) key (it was the case for the other minus key, the one that's not supposed to turn on the 3G)
- Fn+1 and Fn+2, strangely, output nothing on the command line (for the 1 and 2 on the upper row of numbers). All other numbers were output on the command line, including all in the number pad (when NumLk was on; I tried with NumLk both on and off).
- Fn+(Numpad 0) with NumLk off (Ins) caused the following up-arrow to act a little differently to usual. (it output ^[[A onto the command line) Tests show that using (Ins) without the Fn key has the same effect.
- Occasionally, for no immediately apparent reason, the line "AFStatus: TP-" in the output of lspci -vvv changed to "AFStatus: TP+". This does not appear to have been related to any specific key combination. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54214
Location: 56N 3W
|
| Posted: Thu Dec 20, 2012 5:04 pm Post subject: |
|
|
CCC_037,
Thats a very through test.
Are you able to boot with System Rescue CD or some other recent live distro?
I'm fairly sure its not a distro issue as the installed software can do nothing unless it gets a keypress.
Install dmidecode, it will print out lots of information about your system thats embedded in your BIOS, its useful but not always 100%.
Pastebin the output of dmidecode - its quite large, with both the webcam and the 3G on and off. I know the 3G won't actually turn on but we need to know if the turning things on and off hides them from dmidecode, (It should not).
This leaves two things - a BIOS update
A hardware failure.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
CCC_037
n00b
Joined: 14 Dec 2012
Posts: 22
|
| Posted: Fri Dec 21, 2012 9:14 am Post subject: |
|
|
| NeddySeagoon wrote: | | Are you able to boot with System Rescue CD or some other recent live distro? |
I'm on holiday at the moment, and don't have any blank CDs with me, so I unfortunately can't test this for a while.
| NeddySeagoon wrote: | | I'm fairly sure its not a distro issue as the installed software can do nothing unless it gets a keypress. |
If it can be turned on entirely from software (as appears to be the case) then it should, in theory at least, be possible to substitute some other keypress or command; though I don't know how to go about that.
| NeddySeagoon wrote: | Install dmidecode, it will print out lots of information about your system thats embedded in your BIOS, its useful but not always 100%.
Pastebin the output of dmidecode - its quite large, with both the webcam and the 3G on and off. I know the 3G won't actually turn on but we need to know if the turning things on and off hides them from dmidecode, (It should not). |
With both camera and 3G turned off, I got this output. With camera and 3G turned on (individually or together), I got exactly the same output (checked using diff). |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54214
Location: 56N 3W
|
| Posted: Fri Dec 21, 2012 2:18 pm Post subject: |
|
|
CCC_037,
Enjoy your Holiday. If you get bored, System Rescue CD can be put on a USB stick and booted from there.
The interesting bit is :- | Code: | System Slot Information
Designation: J_MINI1
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:02:01.0
Handle 0x0016, DMI type 9, 17 bytes
System Slot Information
Designation: J3G1
Type: x1 PCI Express
Current Usage: Available
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:1c.3 |
It shows your two miniPCIe slots and claims that one is empty. This data is a part of the BIOS, and needs to be taken with a pinch of salt.
| Code: | However the Bus Address: 0000:02:01.0
Bus Address: 0000:ff:1c.3 |
are probably correct. Neither of these appear in your lspci or lspci -n output.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
