You are not logged in.
Pages: 1
Hello archers !
Here are some problems that are not mentioned in the wiki pages. Maybe because
I got a very recent version which had bios 212 pre-installed.
Backlight
/sys/class/backlight/asus-nb-wmi is not working, just like in this thread where
a user recommends to debug the bios.
But I'm sure that's not necessary, because Ubuntu 12.10 populates
/sys/class/backlight/intel_backlight which works. Note that Ubuntu 12.10 does
load asus-nb-wmi too, but does not populate /sys/class/backlight/asus-nb-wmi.
Question: how to enable /sys/class/backlight/intel_backlight instead of
/sys/class/backlight/asus-nb-wmi ?
Resuming from suspend
Resuming works fine on Ubuntu, on arch the screen stays black and I have two
options:
Either Ctrl+Alt+Shift+F1 then Ctrl+Alt+Del to reboot,
Either wait ten minutes, and move the mouse, the screen will auto
activate.
I have analysed Ubuntu's /etc/pm settings and there is nothing special. This
might be related to the backlight issue.
Xorg is stuck on vesa
USing lshw -c video, I figured out that i915 driver was properly used on Ubuntu
12.10:
*-display
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:43 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64)
But not on Arch:
*-display UNCLAIMED
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller cap_list
configuration: latency=0
resources: memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64)
The diff:
--- lshw.arch 2012-10-30 11:29:39.780596439 +0100
+++ lshw.ubuntu 2012-10-30 10:26:59.600001471 +0100
@@ -1,4 +1,4 @@
- *-display UNCLAIMED
+ *-display
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
@@ -7,6 +7,6 @@
version: 09
width: 64 bits
clock: 33MHz
- capabilities: msi pm vga_controller cap_list
- configuration: latency=0
- resources: memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64)
+ capabilities: msi pm vga_controller bus_master cap_list rom
+ configuration: driver=i915 latency=0
+ resources: irq:43 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64
The intel driver is properly installed and loaded by Xorg:
>>> pacman -Q xf86-video-intel
xf86-video-intel 2.20.12-1
>>> cat /var/log/Xorg.0.log | grep -i intel
[ 24.996] (==) Matched intel as autoconfigured driver 0
[ 24.996] (II) LoadModule: "intel"
[ 24.996] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 24.999] (II) Module intel: vendor="X.Org Foundation"
[ 25.000] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
[ 25.003] (II) VESA(0): VESA VBE OEM: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
[ 25.003] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[ 25.003] (II) VESA(0): VESA VBE OEM Product: Intel(R) Sandybridge/Ivybridge Graphics Controller
[ 25.094] (II) VESA(0): VESA VBE OEM: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
[ 25.094] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[ 25.094] (II) VESA(0): VESA VBE OEM Product: Intel(R) Sandybridge/Ivybridge Graphics Controller
[ 25.301] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event6)
[ 25.301] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event7)
Internal microphone
I've seen it reported as "working ootb" on both arch and ubuntu. But the
reports where quite old and may not be using bios 212.
Anyway, I have no idea what the problem is. I reported in on
ubuntu's launchpad and alsa-users, but got
nothing so far.
All information is in ubuntu's launchpad report.
I think that the first 3 problems might be related. Any help is appreciated.
Last edited by isnull (2012-10-30 10:49:29)
Offline
i have the version ux32vd and bios 206 :
sudo lshw -c video
*-display UNCLAIMED
description: 3D controller
product: NVIDIA Corporation
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f7000000-f707ffff
*-display
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:43 memory:f7400000-f77fffff memory:d0000000-dfffffff ioport:f000(size=64)
i have installed only the last intel driver and add in /etc/mkinitcpio.conf
MODULES="i915"
after mkinitcpio -p linux
my kernel is:
Linux 3.6.3-1-ARCH #1 SMP PREEMPT Mon Oct 22 10:23:56 CEST 2012 x86_64 GNU/Linux
for screen blacklight i use the setting in kde -> energy management, or https://aur.archlinux.org/packages.php?ID=62812 and remap the fn+key in kde settings and works
for the keybord blacklight https://aur.archlinux.org/packages.php? … ight&SeB=x the instruction are in the wiki ux31a
pass your kernel i915.enable_backlight=1, but the default i have
# pwd
/sys/class/backlight/intel_backlight
#ls
ls
actual_brightness bl_power brightness device max_brightness power subsystem type uevent
but i haven't /sys/class/backlight/asus-nb-wmi
dmesg |grep wmi
[ 12.533669] wmi: Mapper loaded
[ 13.080849] asus_wmi: ASUS WMI generic driver loaded
[ 13.660001] asus_wmi: Initialization: 0x1
[ 13.660027] asus_wmi: BIOS WMI version: 7.9
[ 13.660061] asus_wmi: SFUN value: 0x4a2877
[ 13.660991] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input12
[ 13.750593] asus_wmi: Backlight controlled by ACPI video driver
Offline
For backlight, it is documented in detail in UX31A page in the wiki.
For i915, what are your kernel boot parameter ? for me in /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="quiet add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
Offline
pass your kernel i915.enable_backlight=1
It claims that this option is not recognized, and continues booting.
uname -a:
Linux zen 3.6.3-1-ARCH #2 SMP PREEMPT Mon Oct 22 12:55:44 CEST 2012 i686 GNU/Linux
For backlight, it is documented in detail in UX31A page in the wiki.
Absolutely. I've tried every solution several time but none work for me, with 212 bios:
xorg-xbacklight outputs "No outputs have backlight property"
asus-screen-brightness complains that /sys/class/backlight/intel_backlight does not exist, i changed it to /sys/class/backlight/asus_nb_wmii and it "works": changes /sys/class/backlight/asus-nb-wmi/brightness value, but no effect on the actual screen brightness (like in the other thread mentioned in my first post ...)
fix backlight method bugs
Actually, I bet all frontends to backlight are going to use /sys/class/backlight, but i can't get something working in there. So I don't think trying a multitude of GUIs is going to help - not to mention that I'm on plain Xorg + dwm.
dmesg|grep wmi
>>> dmesg |grep wmi
[ 2.298513] wmi: Mapper loaded
[ 2.358638] asus_wmi: ASUS WMI generic driver loaded
[ 2.360472] asus_wmi: Initialization: 0x1
[ 2.360494] asus_wmi: BIOS WMI version: 7.9
[ 2.360526] asus_wmi: SFUN value: 0x4a2877
[ 2.361757] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input5
[ 2.473092] asus_wmi: Disabling ACPI video driver
If i remove acpi_backlight="vendor" (setting that is *needed* on ubuntu), then the last line is like yours:
[ 2.804048] asus_wmi: Backlight controlled by ACPI video driver
But:
/sys/class/backlight is empty
xbacklight still complains that no output has a backlight
For i915, what are your kernel boot parameter ?
Here it is:
GRUB_CMDLINE_LINUX_DEFAULT="add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nomodeset nmi_watchdog=0"
I added i915 to initramfs but it doesn't help ...
Thanks for answering. But I'm stuck again...
Last edited by isnull (2012-10-31 08:16:26)
Offline
Ok, sorry I got it wrong... Not sure I can help you much then.
It looks it is an acpi problem. It may be related to the bug that makes backlight keys not working and your version of the bios.
- Have you tried rmmod/modprobe asus_nb_wmi and/or asus_wmi ?
- Have you tried the screen backlight fix ?
Offline
Ok, sorry I got it wrong... Not sure I can help you much then.
It looks it is an acpi problem. It may be related to the bug that makes backlight keys not working and your version of the bios.
Ok, I'm trying kernel 3.7-rc1 then. Thanks for the great link !!
- Have you tried rmmod/modprobe asus_nb_wmi and/or asus_wmi ?
Yes, but then I checked my Ubuntu system and found out that Ubuntu loads these modules too, and that they don't conflict with /sys/class/backlight/intel_backlight - when boot parameter acpi_backlight=vendor.
- Have you tried the screen backlight fix ?
Yes, and it didn't work ...
- first, you can see that the IDGM address for UX31A bios 212 is "????" in the README
- I tried and it failed so i reported the issue
- also i think this is just a fix for the backlight buttons ... it probably assumes that you've got acpi backlight working !
Offline
The ???? for 2.12 is due to the fact that I don't have a UX31A to extract this value. This has to do someone with this Zenbook and a working system, since yours seems to be flaky. Try acpi_call in ubuntu. My guess is that it works, since the asus-nb-wmi modue seems to get loaded correctly on your zenbook. With this, I could update the readme in the gitrepo for the IGDM address on bios 2.12. I guess it is the same as on 2.11 anyway, since on the UX32VD it didn't change between 2.11 and 2.12 either.
Unfortunately, it is not easy to get to the ground of this. I'm a bit at a loss here. I can't explain why the asus-nb-wmi module isn't loaded. It did work since kernel 3.4.9 or so on each bios configuration which I heard of. Can you try it without the nomodeset bootparameter. On my UX32VD, I couldn't get graphical support with nomodeset enabled.
> If i remove acpi_backlight="vendor" (setting that is *needed* on ubuntu), then the last line is like yours:...
Afaik, you don't need acpi_backlight="vendor" on the ux31a. At least, on the UX32VD if I append this parameter, backlight control doesn't work, since the asus-nb-wmi hasn't implemented backlight control (at least that is what I understand, if I undestood the source code correctly).
So summarized: Remove the acpi_backlight=vendor parameter, try without nomodeset (I'm not sure about this one). Post the kernel messages that get printed when you load asus-nb-wmi manually. If this doesn't help diagnose the problem, I guess it remains to enable debug messages in the acpi subsystem and whatever you get out of asus-wmi/nb-wmi + dsdt debugging.
Offline
FTR: Systemd hangs just before presenting the tty with kernel
3.7rc3. So that didn't work.
I build and tried acpi_call on Ubuntu: same result.
At the next boot, i used grub live editor to remove nomodeset and
acpi_backlight=vendor. My screen went black as I expected after 1
second, but 10 seconds later it presented my with the tty login. I
logged in and /sys/class/backlight/intel_backlight was there. I was
so excited i removed nomodeset and acpi_backlight from grub, and
rebooted. But then, the initial result was there again: with
nomodeset -> screen stays black. I waited 5 minutes and it was still
black. I tried again and again, same result...
The screen just stays black with nomodeset. Same with ubuntu.
Correct me if I'm wrong, but fixbacklight will just fix the
backlight button ?
Loading asus-nb-wmii manually:
[ 391.544315] asus_wmi: Initialization: 0x1
[ 391.544444] asus_wmi: BIOS WMI version: 7.9
[ 391.544634] asus_wmi: SFUN value: 0x4a2877
[ 391.547493] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input10
[ 391.607395] Registered led device: asus::kbd_backlight
[ 391.611817] asus_wmi: Backlight controlled by ACPI video driver
I'll send the debug logs when I get them but I have to do some work first ...
Thanks for answering !
Last edited by isnull (2012-10-31 15:11:12)
Offline
Now it works with nomodeset. I have no idea what I did to change that. But THANKS !!
/sys/class/backlight/intel_backlight works
acpi_call still doesn't.
This solved: brightness (i'll control it through a dwm keybinding) and direct rendering.
Still problematic: microphone (not working on ubuntu), suspend (working on ubuntu)
Again, THANKS YOU ROCK !!
Last edited by isnull (2012-10-31 15:31:27)
Offline
I tried acpi_call on my UX31A and it failed also:
# echo '\aslb' > /proc/acpi/call
# cat /proc/acpi/call
Error: AE_BAD_PARAMETER#
And I have an older version of the bios (version 204).
edit:
Oct 31 16:18:18 localhost kernel: [ 290.140273] acpi_call: Module loaded successfully
Oct 31 16:18:56 localhost kernel: [ 327.739285] acpi_call: Calling slb
Oct 31 16:18:56 localhost kernel: [ 327.739296] acpi_call: Cannot get handle: Error: AE_BAD_PARAMETER
That error is raised in acpi_call.c line 108.
Last edited by bzhb (2012-10-31 15:50:16)
Offline
FTR: I got the nomodeset problem again. When I don't reboot correctly from X (ie. my hackings fail and I have to hard reboot or stuff like that), I have to plugin the computer to AC and boot with nomodeset. Then, I can reboot without nomodeset and everything is fine. This has got to be a PM problem.
This is how I fixed keys with dwm:
static const char *volup[] = { "amixer", "--quiet", "set", "Master", "1+", NULL };
static const char *voldown[] = { "amixer", "--quiet", "set", "Master", "1-", NULL };
static const char *voltoggle[] = { "amixer", "--quiet", "set", "Master", "toggle", NULL };
static const char *brightup[] = { "sudo", "asus-screen-brightness", "up", NULL };
static const char *brightdown[] = { "sudo", "asus-screen-brightness", "down", NULL };
static const char *kbrightup[] = { "sudo", "asus-kbd-backlight", "up", NULL };
static const char *kbrightdown[] = { "sudo", "asus-kbd-backlight", "down", NULL };
static Key keys[] = {
/* modifier key function argument */
{ MODKEY, XK_p, spawn, {.v = dmenucmd } },
{ MODKEY|ShiftMask, XK_Return, spawn, {.v = termcmd } },
{ MODKEY, XK_F3, spawn, {.v = kbrightdown } },
{ MODKEY, XK_F4, spawn, {.v = kbrightup } },
{ MODKEY, XK_F5, spawn, {.v = brightdown } },
{ MODKEY, XK_F6, spawn, {.v = brightup } },
{ MODKEY, XK_F10, spawn, {.v = voltoggle } },
{ MODKEY, XK_F11, spawn, {.v = voldown } },
{ MODKEY, XK_F12, spawn, {.v = volup } },
I have sudo with nopasswd (since I had machine + SSD password enabled) so I didn't bother with permissions.
Also, running pm-suspend from CLI doesn't work, but it seems to suspend and resume all right when the LID closes so that's good.
Thanks again everybody !!
Only issue left: the microphone.
Last edited by isnull (2012-10-31 18:19:05)
Offline
What PM tools are you using? Laptop-mode Tools maybe? I noticed some strange behaviour when I enable laptop-mode tools in the daemon array, which doesn't happen, if I start laptop-mode manually after booting.
Beside that, wow... the 2.12 Bios on the UX31A seems to be veeeery buggy. Have you already tried a kernel from the 3.5 branch? Maybe it helps.. and kudos to your analysis regarding the connection between hard reset and nomodeset. There is definitely something seriously wrong with 2.12. Can you dump the dsdts etc. and upload it somewhere? Maybe I find the time to debug this baby. But don't get your hopes too high in the near future, I don't have the time atm to debug the dsdt for days (I spent almost a week of debugging to get to the ground of the backlight buttons problem in the summer holiday).
Offline
pm-utils 1.4.1-5
laptop-mode-tools 1.61.2
Note that it doesn't only happens on hard reboot, sometimes it happens when rebooting before entering an X session ...
Is there any problem with hard reboot on your machine too ?
I disassembled the dsdt fine, still much to read before I can move forward.
This was rather intriguing:
In history people used to override their DSDT to workaround BIOS or even kernel
bugs. This is a bad idea, the override functionality is for short
term workarounds and mainly for debugging! Please always report such bugs to
bugzilla.kernel.org or post to linux-acpi@vger.kernel.org if unsure.
Last edited by isnull (2012-11-01 22:33:52)
Offline
Could you upload your dsdts somewhere? I will take a look at it, maybe they removed/renamed the \aslb command .. idk. Try to disable lapop-mode tools in the daemons array (if you still use the rc.conf .. or in systemd .. w/e). In my case, when I enabled laptop-mode in the rc.conf on boot... most of the time when I boot, the one of the backlight sysfs files isn't created. Idk why, but when I enable laptop-mode manually after booting, it works as intended (at least that was with previous kernel versions, mayne this is fixed now). However, I need your extracted dsdts, If you want me to take a look at it.
Offline
I uploaded my dsdt: https://github.com/jpic/UX31A-dsdt
I came up with a fixed version, loaded via grub ...
But I'm not quite sure about my fixes, this didn't enable Fn keyboard/screen brightness keys, does that mean my fixes "doez not work" ?
Thanks again for your support.
Last edited by isnull (2012-11-02 10:57:42)
Offline
What did you fix exactly? The compiler errors/warnings? If you fixed those, you still won't get back your backlight keys (at least not without initializing the CADL region). To be honest, you might as well just wait until kernel 3.7 is released (they merged the fix from which I derived the memory manipulation version into kernel 3.7, or patch the current 3.6 kernel with this one). If you patch kernel 3.6 with the merged 3.7 fix, you don't need to tinker around in the bios to find out how to get the IGDM base-address (provided the fix doesn't fail due to the same problem which makes 'echo '\aslb' > /proc/acpi/call' fail on your zenbook).
Offline
Yes, I fixed compiler errors/warnings. Thanks for your help, I'm waiting for 3.7. I hope that it will fix alsa issues too.
Thanks for your support !
Will update the topic.
Offline
Thanks! I removed nomodeset from GRUB configuration and now I can change brightness on 3.7.0-1-mainline (I have UX32VD with 212 BIOS).
Heeeeeey cat!!!
Offline
Do you have the internal mic working ? Question also directed to other UX31A 212 bios archers....
Last edited by isnull (2012-11-13 11:21:18)
Offline
Do you have the internal mic working ? Question also directed to other UX31A 212 bios archers....
Yes, I am using GNOME Shell.
Heeeeeey cat!!!
Offline
Thanks for answering.
As of kernel 3.6.8, i still have:
- boot without nomodeset might prevent backlight & backlight commands to work, need to close the lib and re-open to get backlight commands to work
- microphone still not working.
It would be great if another archer with the same exact laptop (UX31A bios 212) could confirm this.
Last edited by isnull (2012-11-30 07:49:09)
Offline
[EDIT]
SOLVED:
I realized that I had NetworkManager.service enabled and running, which blocked the wireless card.
Thank you karol for giving a direction!
[/EDIT]
Hello,
I am not sure if this is the right place for this question, however, I have wireless network problem on my UX31A:
During installation wlan0 did not go up until I passed
# rfkill unblock all
which set "Soft blocked" to "no" on all the following entries:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: asus-wlan: Wireless LAN
Soft blocked: yes
Hard blocked: no
2: asus-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
Now that I have an up-to-date install,
# ip link set wlp2s0 up
does nothing and return no error message.
Checking by
# rfkill list all
all I see is:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
So, no asus-wlan and asus-bluetooth entries.
Also Fn+F2 does nothing and the wireless indicator LED on F2 never turns on.
I am not sure if this is related to the problem but the asus_wmi module appears to be loaded.
Could anyone help me out?
Thanks
Last edited by shugoshin (2013-05-17 13:03:12)
Offline
Seems to be similar to https://bbs.archlinux.org/viewtopic.php?id=163279
Offline
Pages: 1