[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] [NEW] Everex Stepnote XT5000T keymap
Public bug reported: Binary package hint: udev-extras Release: Jaunty (9.04) Package tested: udev-extras-20090602+1-2~jaunty1 Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of issues in terms of some unknown and some incorrect keymaps with hal, although the Sound Up/Down/Mute and Suspend Fn keys worked out of the box in both hal and udev-extras Example snippet from syslog: --- Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released (translated set 2, code 0x7f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released (translated set 2, code 0x6f on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released (translated set 2, code 0x67 on isa0060/serio0). Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). I followed the very helpful information in /usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to create a keymap for this lappy to solve all the problematic Fn Keys :) By the way, there's a little typo in that README.keymap.txt: "cat cat /sys/class/dmi/id/product_name" <- cat twice system vendor and product j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor Everex j...@jas-everex:~$ cat /sys/class/dmi/id/product_name XT5000T Key mapping from step 3 (see attached everex-stepnote_xt5000t file) --- /lib/udev/keymaps/everex-stepnote_xt5000t ** Affects: udev-extras (Ubuntu) Importance: Undecided Status: New -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29207950/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] [NEW] Everex Stepnote XT5000T keymap
Public bug reported:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key pressed
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key released
(translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key pressed
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key released
(translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key pressed
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key released
(translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key pressed
(translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key released
(translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
laptop's video backlight dimming feature (Nvidia 7600), so I had to
install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
"/usr/bin/nvclock -S -10"
XF86MonBrightnessDown
"/usr/bin/nvclock -S +10"
XF86MonBrightnessUp
and ran `xbindkeys` and now my brightness Fn keys just work :D
and of course added `/usr/bin/xbindkeys` to gnome startup
Hope this helps, and thanks for this :)
** Affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Tags: brightness everex fn keymap keys stepnote xt5000t
--
Everex Stepnote XT5000T keymap
https://bugs.launchpad.net/bugs/400921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Attachment added: "Key mapping from step 3" http://launchpadlibrarian.net/29208296/everex-stepnote_xt5000t -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400914] Re: Everex Stepnote XT5000T keymap
*** This bug is a duplicate of bug 400921 *** https://bugs.launchpad.net/bugs/400921 erroneous post (incomplete / pasted in a haste)... marked as duplicate of the more complete bug report 400921 ** This bug has been marked a duplicate of bug 400921 Everex Stepnote XT5000T keymap ** Changed in: udev-extras (Ubuntu) Status: New => Invalid -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400914 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412375] [NEW] Fails to read registers on 32 bit
Public bug reported:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -O2 -g -Wall -O2 -o wrmsr wrmsr.c
gcc -Wall -g -O2 -g -Wall -O2 -o rdmsr rdmsr.c
Building without debian patches it is like this:
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
wrmsr wrmsr.c
gcc -Wall -g -O2 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -o
rdmsr rdmsr.c
I see the debian patch adds #define __USE_UNIX98 to the source, but that
doesn't appear to be sufficient.
---
Hope this helps..
** Affects: msr-tools (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: msr-tools
This is the same exact bug reported in debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495445
- On a 32-bit ubuntu system, trying to rdmsr 0xC0010015 or 0xC0011023 gives the
following error:
+ On a 32-bit ubuntu system, trying to rdmsr 0xc0010041 or 0xc0010042 gives the
following error:
rdmsr:pread: Invalid argument
or sometimes gives a plain old "0"...
Example:
--
r...@evrx:/root/drivers/phc# rdmsr 0xc0010042
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr 0xc0010041
rdmsr:pread: Invalid argument
r...@evrx:/root/drivers/phc# rdmsr c0010042
0
r...@evrx:/root/drivers/phc# rdmsr c0010041
0
---
My very basic python script, however, reads the offsets just fine:
---
#!/usr/bin/env python
import os
MSR_FIDVID_CTL=int(0xc0010041)
MSR_FIDVID_STATUS=int(0xc0010042)
msrfile = os.open("/dev/cpu/0/msr", os.O_RDONLY);
os.lseek(msrfile, MSR_FIDVID_STATUS, 0);##jump to where current
values lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_STATUS ---"
for v in value:
print ord(v)
os.lseek(msrfile, MSR_FIDVID_CTL, 0); ##jump to where target values
lie
value = os.read(msrfile, 8) ##read 8 bytes
print "--- MSR_FIDVID_CTL ---"
for v in value:
print ord(v)
os.close(msrfile)
---
Example Output from my python script:
---
r...@evrx:/root/drivers/phc# ./test.py
--- MSR_FIDVID_STATUS ---
0
0
8
17
30
30
17
51
--- MSR_FIDVID_CTL ---
0
30
0
0
1
0
0
0
---
- msr-tools from the 1.1.2-1 deb pkg works fine on 64 bit, just not on 32-bit...
+ msr-tools from the 1.1.2-1 pkg works fine on 64 bit, just not on 32-bit...
However, they work fine (on 32-bit) if compiled from non-debian/non-
ubuntu sources.
Quote, from the previously mentioned debian bug report on same package:
---
The defines are not being set correctly. Building the debian package it
is compiled like this:
gcc -Wall -g -
[Bug 183159] Re: Brightness-keys of FSC Laptop XA1526 don't work
Although a different manufacturer, the Fujitsu-Siemens Amilo XA 1526 is 99.9% identical to (now out of business) Everex Stepnote XT5000T laptop... Same exact motherboard, except it only doesnt come with bluetooth like the Amilo Xa 1526.. Don't know about if the keyboard layout is exactly the same, but it's probably quite similar, as the brightness Fn+F8/F9 keys also weren't working nor were being detected by xev, due to missing scancodes (`tail -f /var/log/messages` when u press them and you should see error about the scancodes missing)... Also, some media keys weren't working or were not detected correctly.. Solution was to write keymap and rule for udev (udev-extras package needed from Pitti's PPA for Jaunty 9.04) which has now been committed upstream to udev trunk for Karmic (udev-extras was merged into udev in Karmic) See bug 400921 which I submitted for more info on the fix https://bugs.launchpad.net/bugs/400921 However, gnome-power-manager isn't so friendly with the Nvidia Geforce 7600 Go on these lappys, meaning it's not able to adjust brightness, either via the Fn key combinations, nor manually via the slider for LCD backlight settings, nor does the dimming/undimming work when power is unplugged/plugged-in.. For this, you need to install a command line tool called "nvclock" to control the backlight/brightness level, and which you can also bind it to other key combination like the windows key (Mod4) + F8/F9 with xbindkeys to accomplish same purpose... I have provided details on how to do that in the said bug 400921 report Hope this helps.. Jasmine -- Brightness-keys of FSC Laptop XA1526 don't work https://bugs.launchpad.net/bugs/183159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
NOPE, NOT FIXED! Got the diff from: http://launchpadlibrarian.net/29611367/nvidia-common_0.2.11_0.2.12.diff.gz Applied the relevant changes to 0.2.11 in: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common BUT still, same problem persists: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms run-parts: executing /etc/kernel/postinst.d/nvidia-common run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30-phc1.postinst line 1186. dpkg: error processing linux-image-2.6.30-phc1 (--configure): subprocess post-installation script returned error exit status 2 ** Changed in: nvidia-common (Ubuntu) Status: Fix Released => In Progress -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292606] Re: dkms - error when installing custom kernel
@Alberto Milone I applied you attached patch to: /var/lib/dpkg/info/nvidia-common.config in addition to what I had already applied previously to: /usr/share/pyshared/NvidiaDetector/nvidiadetector.py /etc/kernel/postinst.d/nvidia-common Same problem persists... I guess Mike Stroyan has a point here... See his comment #19 He provided logical explanation for why this is happening and why it should be fixed in postinst.d/dkms and not in nvidia-common, and he quoted the debconf manual to justify his reasoning, which seems appropriate in this case.. After adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller in /etc/kernel/postinst.d/dkms as he recommended: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.30-phc1 * madwifi-hal (0.10.5.6)... madwifi-hal (0.10.5.6): Already installed on this kernel. [ OK ] * nvidia (185.18.29)... nvidia (185.18.29): Already installed on this kernel. [ OK ] * rt73-k2wrlz (3.0.3)... rt73-k2wrlz (3.0.3): Already installed on this kernel. [ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common # (success) So perhaps this bug should be changed to 'dkms' package instead of 'nvidia-common', don't you think? -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
** Description changed:
Binary package hint: udev-extras
Release: Jaunty (9.04)
Package tested: udev-extras-20090602+1-2~jaunty1
Prior to installing udev-extras from Pitti PPA, this Laptop had a lot of
issues in terms of some unknown and some incorrect keymaps with hal,
although the Sound Up/Down/Mute, LCD/display toggle, and Suspend Fn keys
worked out of the box in both hal and udev-extras
Example snippet from syslog:
---
Jul 17 21:33:32 jas-everex kernel: [ 3452.528080] atkbd.c: Unknown key
pressed (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:33 jas-everex kernel: [ 3452.674895] atkbd.c: Unknown key
released (translated set 2, code 0x7f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.685330] atkbd.c: Unknown key
pressed (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:35 jas-everex kernel: [ 3454.872654] atkbd.c: Unknown key
released (translated set 2, code 0x6f on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3457.951496] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.199592] atkbd.c: Unknown key
pressed (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:33:38 jas-everex kernel: [ 3458.270450] atkbd.c: Unknown key
released (translated set 2, code 0x67 on isa0060/serio0).
Jul 17 21:49:14 jas-everex kernel: [ 4394.577450] atkbd.c: Unknown key
pressed (translated set 2, code 0x65 on isa0060/serio0).
Jul 17 21:49:15 jas-everex kernel: [ 4394.785012] atkbd.c: Unknown key
released (translated set 2, code 0x65 on isa0060/serio0).
I followed the very helpful information in
/usr/share/doc/udev-extras/README.keymap.txt to resolve these issues and to
create a keymap for this lappy to solve all the problematic Fn Keys :)
By the way, there's a little typo in that README.keymap.txt: "cat cat
/sys/class/dmi/id/product_name" <- cat twice
system vendor and product
j...@jas-everex:~$ cat /sys/class/dmi/id/sys_vendor
Everex
j...@jas-everex:~$ cat /sys/class/dmi/id/product_name
XT5000T
Key mapping from step 3 (see attached everex-stepnote_xt5000t file)
---
/lib/udev/keymaps/everex-stepnote_xt5000t
`sudo /lib/udev/keymap input/event5 > /tmp/orig-map.txt` Output
--
http://ubuntu.pastebin.com/f1cabf855
`udevadm info --export-db > /tmp/udev-db.txt` Output
http://ubuntu.pastebin.com/fa41a52d
Rule added in file: "/lib/udev/rules.d/95-keymap.rules"
After the line: 'LABEL="keyboard_vendorcheck"'
ENV{DMI_VENDOR}=="Everex*", ATTR{[dmi/id]product_name}=="XT5000T",
RUN+="keymap $name everex-stepnote_xt5000t"
That fixed all the unknown keys (brightness up/down Fn keys, touchpad
on/off toggle Fn key, fan speed control button) and redefined web, mail,
and media buttons
Unfortunately gnome-power-manager does not offer support for this
- laptop's video backlight dimming feature (Nvidia 7600), so I had to
- install nvclock-0.8b4-1ubuntu2 to use it's native backlight controls
- feature, as there was also a bug in smartdimmer with increasing
+ laptop's video backlight dimming feature (Nvidia Geforce 7600 Go), so I
+ had to install nvclock-0.8b4-1ubuntu2 to use it's native backlight
+ controls feature, as there was also a bug in smartdimmer with increasing
backlight brightness (because the driver expects increments of 10 at
least, while smart dimmer does increments of 5)
- And as a workaround, to use my Fn brightness keys in gnome, I created a file
~/.xbindkeysrc with the following 4 lines:
+ One you installed nvclock, you can adjust your screen's brightness level
+ from command line using nvclock -S option... For more info, see `nvclock
+ -h`
+
+ Workaround to get Brightness Fn keys working in GNOME:
+
+ 1. Go to: System -> Preferences -> Keyboard Shortcuts
+
+ 2. Scroll down to the end of the list to see the category "Custom
+ Shortcuts"
+
+ 3. Click "Add" to add a custom shortcut
+ Name: Brightness Down
+ Command: /usr/bin/nvclock -S -10
+ Then click "Apply" to add it.
+
+ 4. Click "Add" to add another custom shortcut
+ Name: Brightness Up
+ Command: /usr/bin/nvclock -S +10
+ Then click "Apply" to add it.
+
+ 5. Click the text "Disabled" in the shortcut column for the "Brightness
+ Down" entry, then press Fn+F8
+
+ 6. Click the text "Disabled" in the shortcut column for the "Brightness
+ Up" entry, then press Fn+F9
+
+ Note on steps #5 and #6:
+ If your keybinding setup as described above was completed successfully in
udev (or udev-extras from P
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Forgot to add that there's another laptop, Fujitsu-Siemens Amilo Xa 1526, which is 99.9% identical to this laptop (Everex Stepnote XT5000T) and I'm pretty sure it has the same (or very similar) keyboard/media buttons layout... Unfortunately I do not have access to an Amilo Xa1526 to confirm this, but if anyone who does have it could confirm that the scancodes are the same, perhaps the FS Amilo Xa 1526 should also be added to 95-keymap.rules Cheers jasmine -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
Martin, Verified: http://www.amilo-forum.com/topic,544,-Linux-on-Amilo-Xa-1526.html#2652 One user mentions: * Hotkeys (Video, Mail, Browser, Power) * Fn+F5 : Touchpad enable/disable: Doesn't seems to work, but not realy usefull. * Fn+F8/F9 : LCD Brightness -/+ DOESNT WORK also another user reports: "edit: the fn-f5 keys arent recognized by xev." and "does the volume wheel work for anyone?" Same behavior I had with this one.. Matter of fact, I haven't gotten around to getting the volume wheel (on the front of the laptop) working... Had a bug report in ALSA from almost 2 years ago and still heard nothing back... Also, nothing from xev nor evtest (from package "joystick") nor from acpi_listen... So I'm pretty sure this is the same exact thing as this laptop, I also just looked at the (rather awkward) keyboard layout shared between this laptop and the Amilo Xa 1526, its the same.. https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 Also, bug #183159 "Brightness-keys of FSC Laptop XA1526 don't work" https://bugs.launchpad.net/bugs/183159 Which I totally even forgot I replied to 2 days ago :) (has dmidecode and other useful info) Moreover, I remember that we had some Everex Stepnote XT5000T users from hardforum modifying/hex-editing the FSC Amilo XA1526 bioses and flashing them on the XT5000T, as the BIOS has more unlocked features and the laptops are 99.9% identical, except that the Amilo XA1526 comes with extra feature of bluetooth, afaik... Hope this helps... but anyway, it doesn't concern me personally... hopefully someone will find this sometime from google and duplicate the troubleshooting... Thanks -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400921] Re: Everex Stepnote XT5000T keymap
"Apparently it's not the same layout, though:" Nods... I forgot to mention this, sorry for the late followup, and kudos to you for noticing that for yourself: from: https://www.preisroboter.de/ergebnis8281658.html&sortmode=0 you'll notice there's a bunch of different keyboards for different regions for the same Amilo Xa 1526, like UK, DE, GR, and US, etc... So I wonder if the scan-codes would differ from one version to another... Originally, I believe the Amilo Xa1526 was only sold in Europe (and possibly mid-east as well), while the Everex was only available in US / Canada (owned by FIC, now out of business, sadly) Thanks, and keep up the good work :) -- Everex Stepnote XT5000T keymap https://bugs.launchpad.net/bugs/400921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
