Still facing the issue with kernel 4.2.0-23-generic, gcc version 5.2.1 20151010
(Ubuntu 5.2.1-22ubuntu2), bbswitch-dkms 0.7-2ubuntu1, no bumblebee package
installed. I attach a full dmesg (from kern.log) from the boot to the freeze.
After booting, I logged into tty1 and entered the following
What else information is needed?
I have tried with the daily kernel 3.17.0-999.201409272205 and the tainting
still occurs. The syslog trace related to suspending event is slightly
different (dis_dev_get+0x15/0x40 [bbswitch] instead of
pci_bus_read_config_dword+0x64/0x90 in the initial report
$ sudo modprobe bbswitch load_state=-1
dmesg log:
[ 2780.584599] bbswitch: module verification failed: signature and/or required
key missing - tainting kernel
[ 2780.584809] bbswitch: version 0.7
[ 2780.584818] bbswitch: Found integrated VGA device :00:02.0:
\_SB_.PCI0.VGA_
[ 2780.584830]
Still apears with linux-image-3.15.0-031500rc5-generic.
For now, I stay with 3.11 kernel from kubuntu 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318040
Title:
bbswitch prevents suspend
Public bug reported:
When initiating suspend (to RAM), the kernel gets tainted. This is a
regression that appeared after upgrading from Kubuntu 13.10 to 14.04. My
computer has a discrete nVidia card (hybrid SLI system, on ASUS UL80VT).
Here is an extract from dmesg:
PM: Preparing system for mem
apport information
** Package changed: xorg (Ubuntu) = bbswitch (Ubuntu)
** Summary changed:
- Suspend does not work
+ bbswitch prevents suspend and taints kernel
** Tags added: apport-collected
** Description changed:
When initiating suspend (to RAM), the kernel gets tainted. This is a
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1318040/+attachment/4108974/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318040
dmesg just after trying to suspend
** Attachment added: dmesg-pci_bus_read_config_dword
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1318040/+attachment/4108976/+files/dmesg-pci_bus_read_config_dword
** Description changed:
When initiating suspend (to RAM), the kernel gets
The discussion continues on
https://bugzilla.kernel.org/show_bug.cgi?id=66501
** Bug watch added: Linux Kernel Bug Tracker #66501
http://bugzilla.kernel.org/show_bug.cgi?id=66501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
issue reported upstream on linux-acpi mailing list:
http://marc.info/?t=13860036283r=1w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
8086:2a42 [Asus UL80VT] Backlight control
Here is a workaround from Aaron Lu on linux-acpi: specify the backlight
option in xorg.conf.
Section Device
Identifier Default Device
Option Backlightintel_backlight
Driver intel
BusID PCI:0:2:0
EndSection
--
You received this bug notification because you are
v3.12.1 tested, as well as v3.13-rc2; bug still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
8086:2a42 [Asus UL80VT] Backlight control does not work with Intel
integrated
Tested with 3.12-saucy, same as in my last message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
8086:2a42 [Asus UL80VT] Backlight control does not work with Intel
integrated
Tested Live Lucid
http://old-releases.ubuntu.com/releases/lucid/ubuntu-10.04.4-desktop-amd64.iso.
Result: same as in Precise, that is, the screen brightness applet reacts to the
hotkeys but the screen brigthness does not change.
--
You received this bug notification because you are a member of
I also tried nvidia-319 in Raring with kernel v3.8, brightness hotkeys
don't work. So the bug seems to have been fixed between kernel v3.8 and
v3.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is the same with nouveau: hotkeys works with kernel v3.11 but not kernel
v3.8 (both tested on Raring distribution).
So the title may be modified as With Nvidia or nouveau drivers...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In my case, the purpose of this bug report was for public notification. I
don't need a backport.
It can be closed, but it don't see why as Status Invalid, I would rather close
it as Won't Fix (before Raring) or Fix commited (in Saucy).
--
You received this bug notification because you are a
** Description changed:
It used to work with the workaround suggested at
http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Screen_Brightness
which modifies asus-brn-down.sh to use the setpci method.
But I had forgotten that workaround and I suspect that upgrading to
** Changed in: linux (Ubuntu)
Status: Invalid = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225067
Title:
10de:0a74 [Asus UL80VT] With Nvidia drivers or nouveau drivers,
Christopher, I am not sure to understand your question. Did you mean,
did the problem appear before Raring if the setpci method was not used?
yes, for example, in 12.04 (comment #46).
I didn't try to disable the Intel card in a release prior to Raring, I
suppose that situation would be similar as
The bug existed on Maverick, as noticied on
http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Screen_Brightness.
However, today, Precise is the last release still supported on Desktop. I have
not tested any other release.
--
You received this bug notification because you are a
With Live Saucy, I could not success in switching from nouveau to the
nvidia driver without rebooting. By default, nouveau driver in Saucy
works with the nvidia G210M in this setup and the hotkeys for screen
brightness control work too (as well as the control itself).
I could not try the nvidia
Filed as Bug #1225067.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus UL80VT] Backlight control does not work, but there are entries
in /sys/class/backlight
To manage
Well, I could file a new report with this particular setup (BIOS
parameter SATA in mode Compatible, Intel graphics card disabled) if it
helps to fix nouveau not adjusting brightness correctly (hotkeys with
nouveau works in Precise and Saucy) . But I am not willing to keep using
this setup as the
** Attachment added: xkbcomp.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225067/+attachment/3819592/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225067
Title:
Public bug reported:
With the particular setup where only the nvidia graphics card is used
(the BIOS parameter SATA is switched from Enhanced to Compatible,
http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Nvidia_Accelerated_Graphics_Driver),
the hotkeys Fn+F5 and Fn+F6 do not
** Attachment added: lsinput.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225067/+attachment/3819591/+files/lsinput.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225067
Title:
** Attachment added: xkbmap.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225067/+attachment/3819593/+files/xkbmap.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225067
Title:
I had to install nvidia-319-updates instead of 313 to get the module compiled
for the v3.11 kernel. On v3.8 and nvidia-319-updates, the bug still exists.
With v3.11, the hotkeys trigger the KDE brightness popup and change the screen
brightness, so the bug is fixed upstream.
** Tags added:
is the purpose of testing this in Live Saucy in order to test with
nouveau instead of the nvidia module?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225067
Title:
10de:0a74 [Asus UL80VT] With
Just to correct my comment #54:
-nouveau
+i915
The goal is to fix i915 not adjusting brightness correctly.
Ideally, the nvidia card is enabled only when necessary, using either
nouveau or nvidia driver, thanks to Bumblebee (which, for Saucy and
newer, is provided by a supported Ubuntu
On my Raring, KDE, Ubuntu 3.8.0-30.44-generic, bumblebee removed, BIOS SATA
Compatible (to allow nvidia drivers to work,
http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Nvidia_Accelerated_Graphics_Driver,
note that that also disables the intel card which does not appear anymore in
Hi Christopher, I have tried ubuntu-12.04.2-desktop-amd64.iso and
ubuntu-12.04-desktop-amd64.iso: the brightness applet reacts to the
hotkeys but the brigthness of the screen does not change.
I thought it was working before 13.04 but I don't remember whether I
tweaked something. Maybe I added
I probably had tweaked my acpi script according to the information given
at
http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Screen_Brightness
which suggests to use setpci. And probably, the modified scripts
/etc/acpi/asus-brn-down.sh (and -up) were deleted during the upgrade to
I have updated the description according to my last message. I think the
bug is not a regression and it has never worked directly. It would be
nice to fix it after 3 years of existence.
** Description changed:
- Not working since the upgrade to Raring. Used to work on 12.10.
+ It used to work
** Tags removed: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus UL80VT] Backlight control does not work, but there are entries
in /sys/class/backlight
To manage
The discrete nvidia card is not disabled in BIOS. In the first lspci.txt
attached (Raring), the discrete card was disabled by the module bbswitch
(https://github.com/Bumblebee-Project/Bumblebee/wiki/Power-Management).
In the second lspci.txt attached (Live Saucy), the discrete card was not
tested, as well as v3.11-saucy: not working. Pressing the hotkeys don't display
any brightness popup and the slide in the brightness applet (through the KDE
Battery monitor) does not change the screen brightness.
Do kernel developpers need more specific debug information?
--
You received this
Was the report useful? or are other specific tests required?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus UL80VT] Backlight control does not work, but there are entries
in
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772775/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772769/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772771/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772776/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected saucy
** Description changed:
Not working since the upgrade to Raring. Used to work on 12.10.
Not working neither with linux-
image-3.9.1-030901-generic_3.9.1-030901.201305080210 from
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772778/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772773/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772772/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772768/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772777/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772774/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772770/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772782/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772780/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772781/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1178796/+attachment/3772779/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
I also tried the daily release without acpi_backlight=vendor, but backlight
control did not work.
The brightness applet reacts to the hotkeys, but the brigthness of the screen
does not change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, I'm lost. It seems not related to linux-image, as the kernel image
3.5.0-17.28 (quantal release) does not work either. So it may come from
another package update, acpi-support?
other notes:
- sudo setpci -s 00:02.0 F4.B=HH with HH between 0 and ff works.
- echo 258366
v3.11-rc3 tested, no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
[Asus UL80VT] Backlight control does not work, but there are entries
in /sys/class/backlight
To manage
v3.11-rc2 tested, no change.
dmesg files without (dmesg.0) and with acpi_backlight=vendor
(dmesg_acpi_backlight_vendor.1) are attached.
** Attachment added: dmesg.0.tar.gz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3757383/+files/dmesg.0.tar.gz
--
You
v3.11-rc1 tested, no change.
my BIOS is already ver. 214. On v3.11-rc1, key events are detected (KDE
popup) but the brightness does not change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
v3.10-rc5 tested, no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
On Asus laptop UL80VT, backlight control does not work, but there are
entries in /sys/class/backlight
To
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
On Asus laptop UL80VT, backlight control does not work, but there
v3.10-rc2 tested, still not fixed.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
On Asus laptop UL80VT, backlight control does not work,
Public bug reported:
Not working since the upgrade to Raring. Used to work on 12.10.
Not working neither with linux-
image-3.9.1-030901-generic_3.9.1-030901.201305080210 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9.1-saucy/
Hotkeys are detected, showkey -s:
Fn+F5:
0xe0 0x4c 0xe0 0xcc
** Attachment added: grep -r . /proc/acpi acpi
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672764/+files/acpi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
** Attachment added: sudo acpidump -o acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672771/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: acpixtract acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672778/+files/DSDT.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
** Attachment added: acpixtract acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672779/+files/SSDT.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
** Attachment added: iasl -d DSDT.dat
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672780/+files/DSDT.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178796
Title:
sudo fwts
Running 42 tests, results appended to results.log
sudo fwts method
Running 1 tests, results appended to results.log
** Attachment added: fwts
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672783/+files/results.log
--
You received this bug notification
dmesg | grep 'ACPI: Video'
[2.367054] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[2.373679] ACPI: Video Device [VGA1] (multi-head: yes rom: yes post: no)
** Attachment added: video
sudo dmidecode dmidecode.log
** Attachment added: dmidecode.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672790/+files/dmidecode.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
with kernel parameter acpi_backlight=vendor
ls /sys/class/backlight vendorbacklight
** Attachment added: vendorbacklight
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/+attachment/3672795/+files/vendorbacklight
--
You received this bug notification because you are a member
Reboot is required because it's a problem with a driver, which fails
when loaded and leaves the device in a bugged state, which eventually
prevents suspension.
From bug #1169984: === Alternate workaround ===
IF you have no intention to use the HDMI audio, blacklisting the HDMI audio
module will
*** This bug is a duplicate of bug 1169984 ***
https://bugs.launchpad.net/bugs/1169984
** This bug has been marked a duplicate of bug 1169984
3.8.0-18 HDMI audio regression: Either oops or opening device fails with
-ENODEV
--
You received this bug notification because you are a member
Same problem, same call trace, on Kubuntu 13.04 upgraded today from
12.10, on an Asus UL80VT laptop. It worked well before (on 12.10).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173742
Title:
For me, it is a consequence of bug #1169984 related to the HDMI audio
driver which prevents pm-powersave to terminate,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169984. You can
check /var/log/pm-powersave.log. Before the workaround, my pm-
powersave.log stopped at the nvidia hdmi audio
77 matches
Mail list logo
