[Bug 1492778] Re: kde crashes when turning powering on display port monitor
It affects me too with Intel NUC 5i5RYH.I have a WORKAROUND (read till the end of this post). I have it plugged to a TV by HDMI. Everytime the TV is switched off, X crashes with libqxcb.so errors in syslog, though the problem is not in libqxcb.so. The problem is that xrandr looses all screen displays!! Nasty stuff. I found out about that by compiling a custom libqxcb and writing log messages to a file. This did not happen in 14.04. Of course it won't affect laptops because they have always at least one display connected. It also doesn't affect most desktop monitors, because when they are in standby, they don't signal that they are off in the HDMI cable signals. (pin 19). It only affects computers on which all of their monitors or TVs get turned off without turning the computer off, and those monitors or TVs assert HDMI pin 19. My TV isn't even off, it is in standby and it asserts pin 19, which crashes linux. Please look for HDMI PIN 19 (Hot plug detect) in the web for more information. It has caused problems in windows too in the past. I have a nasty quick and dirty WORKAROUND: Every time I reboot it or switch it on, I wait for X to start on the TV I have to: 1) Wait for the UI to start. Login. 2) In a console in the UI (such as konsole, yakuake, etc.), run this: xrandr --output VIRTUAL1 --mode 1920x1080 --same-as HDMI1 xrandr --addmode VIRTUAL1 1920x1080 xrandr --output HDMI1 --primary 3) Now, if you run: xrandr you'll see that there is an additional display called VIRTUAL1 I tried and failed to make this sequence of commands automatic upon login in. Something about the timing about which they have to be run, when the full desktop has already been loaded I guess. Please someone let me know if these xrandr commands can be made automatic. I'm getting "cranky" about having to run them every time the HTPC has to reboot or looses power and switch it on again. Cheers!! --Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492778 Title: kde crashes when turning powering on display port monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1492778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492778] Re: kde crashes when turning powering on display port monitor
I mean, It is mind boggling because the main reason I got an Intel NUC was to pair it with a TV.. but it turns out that linux crashes when the TV goes to standby or OFF mode. OR HDMI gets unplugged. I think the nvidia driver always makes sure that there is always at least one virtual or mock screen so that libraries don't crash. I think. Cheers! --Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492778 Title: kde crashes when turning powering on display port monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1492778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492778] Re: kde crashes when turning powering on display port monitor
I forgot to add: in my tracing of libqxcb, I found that this library conflates screens with outputs. When there are no more Outputs connected, it returns 0 screens. Traditionally an X screen could exist independently of its outputs. The actual packages that will need to work to fix this very important issue are: libqxcb (Qt5) xserver-xorg-video-intel(or intel graphics driver) xrandr Patching libqxcb is not enough. The crash happens later in the chain of events if so (I tried and tried). It seems plasma and Qt5 cannot function without outputs. Other graphic environments "solve" this by always providing at least one mock or virtual output, when all physical monitors have been unplugged or asserted HotPlug pin 19 of HDMI. --Juan Manuel Cabo -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1492778 Title: kde crashes when turning powering on display port monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1492778/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
Indeed the issue of not having a supported driver for the GTX 750ti is gone! I now have "nvidia-340-updates" in Ubuntu/Kubuntu LTS 14.04 This new nvidia driver version was added in 14.04 as of a few weeks ago. The ticket can be closed, except for maybe that the matching of devices to graphics drivers done through VID:PID is too restrictive, and I think the real issue will reappear when new products come out. This makes little sense if linux is to win desktop gaming or HTPC some day (don't get me started on what happens when my Intel Graphics broadwell HTPC gets the TV turned off... X crashes in kubuntu 15.04). I guess this bug report can be closed. I don't have this specific problem anymore on 14.04. Thanks! Cheers! --Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
Thanks jaunmanuel for finding the fix and sharing the knowledge about how you found it. I'll add redirecting 'aplay' temporarily to a script to my list of debugging techniques :-) :-) Nice to hear! Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
To Martin Pitt: Thank you very much for the fix. I manually applied that commit to my sl_modem.py and it of course works. Restarting the computer, or running ubuntu-drivers list doesn't result in a second instance of pulseaudio. Also, the duplicate bug: USB microphone inputs not detected by Pulseaudio https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282 is of course fixed for me too with that fix (the two pulseaudio instances raced each other for opening the /dev/snd/... devices). Thanks! Cheers! Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
OMG! Has anyone besides the OP reproduced the issue on these drives? I'm not even sure that his FS corruption, in this particular instance, is because of the hardware layer: The Original Poster (Ritesh), states in post #31 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/comments/31) that he is using an encryption layer below EXT4 for the root partition. It is totally NOT recommended to use TRIM or DISCARD together with a software encryption level solution, and it might be causing the problems that the OP encountered. The ext4 errors problems are easy to explain (fs corruption due to messing with empty space on which the encryption solution relied). The read error problems, could also be easily explained: a corrupted filesystem which has corrupted pointers to invalid regions of the disk, will provoke ata read errors. All this is because the encryption layer might store internal info on more blocks than the EXT4 fs reports. Fstrim/discard only looks at used blocks from the EXT4 filesystem's perspective. The result is that one could end up trimming a block used by LUKS (dm-crypt), and corrupt a little or a lot of data, depending on luck. (unless luks/dm-crypt guarantees that all used blocks are also mapped by EXT4). Cheers, Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
On saturday I made some tests and found the root CAUSE of the issue, and
the SOLUTION.
The reason aplay is called, is because it is used to enumerate sound cards,
(with the -l argument as in aplay -l), by ubuntu-drivers, to find ye-old
software modems.
The ubuntu-drivers-common package scripts are called by the
kubuntu-driver-manager
package scripts on login to KDE's desktop. Aplay is also called when going to
AdditionalDrivers
or running ubuntu-drivers list.
The reason why the pulseaudio process created by 'aplay' remains running, is
because aplay and thus
pulseaudio receive an empty environment (no environment variables).
Since pulseaudio receives an empty environment, it cannot know from which
session or
DISPLAY it was called, and whether another pulseaudio is already running for
that session.
Because of that, we end up with two different pulseaudio processes, and thus
one interferes with the
other, producing device busy errors while plugging our USB
headsets/mics/webcams,
resulting in them not getting fully recognized.
The solution is as follows: Edit this file:
/usr/share/ubuntu-drivers-common/detect/sl-modem.py
and replace this line:
aplay = subprocess.Popen(['aplay', '-l'], env={},
with this line:
aplay = subprocess.Popen(['aplay', '-l'],
By removing the named 'env={}' argument, the aplay -l receives the environment
and can distinguish the correct pulseaudio process.
Another way to workaround this, but quick and dirty, is to simply add a line:
return None
right above the aplay line, with the same spacing (indentation level),
to disable looking for software modems at login if you don't plan on
using dial-up modems :-)
Details:
I obtained the process list by adding redirecting 'aplay' temporarily to a
script, which had a sleep 30 delay, so
that I could get it in ps axf.
The process list at the time of calling aplay is:
\_ init --user
[...]
\_ dbus-daemon --fork --session
--address=unix:abstract=/tmp/dbus-l0CdfJrRGy
| \_ [dbus-daemon] defunct
[...]
\_ python3 /usr/lib/kde4/libexec/DriverManager_DBus
\_ /usr/bin/aplay -l
\_ /usr/bin/pulseaudio --start --log-target=syslog
Looking by the process number, for the second pulseaudio instance,
cat /proc//environ
is empty.
I found by tracing the python calls that the file which runs aplay is:
/usr/share/ubuntu-drivers-common/detect/sl-modem.py
(if I skip/comment the call to aplay on that file, the issue dissapears).
The file sl-modem.py belongs to the package:
ubuntu-drivers-common
and the DriverManager_DBus script which runs at logon belongs to the
package:
kubuntu-driver-manager
which explains why this issue only affects us Kubuntu users, but in reality,
it also affects all Ubuntu users, because any time they enter the
driver manager (either by softwarke-properties-gtk or Additional Drivers, or
by running ubuntu-drivers list in the console) they are going to get a
duplicate process for pulseaudio until they restart.
Many Thanks to all the guys in this thread: you pointed me in the right
direction.
My Zoom H2n is now correctly recognized with the solution I explained at the
top of this post.
Maintainers:
Please evaluate if removing 'env={}' from the aplay line at the sl-modem.py
file
of the ubuntu-drivers-common package is a worthy and safe patch so that
everyone benefits.
Cheers,
Juan Manuel Cabo
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
impossible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
I'm sorry that the previous post was too long.
This is the summary:
1) aplay -l gets called with an empty environment by a script in
ubuntu-drivers-common which Kubuntu runs at startup, through the
DriverManager_DBus.
aplay -l doesn't find a pulseaudio and creates a new one (through libasound),
because it has no environment and no way to know the session on which
pulseaudio is already running.
2) The solution is to: Edit this file:
/usr/share/ubuntu-drivers-common/detect/sl-modem.py
and replace this line:
aplay = subprocess.Popen(['aplay', '-l'], env={},
with this line:
aplay = subprocess.Popen(['aplay', '-l'],
NOTE TO MAINTAINERS: please evaluate if this solution is safe and sound, and if
so, create a patch so that everyone benefits, and can have USB sound devices
usable again (no more device busy errors while having an spurious extra
pulseaudio instance).
Cheers,
Juan Manuel Cabo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
impossible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325282] Re: USB microphone inputs not detected by Pulseaudio on Kubuntu Trusty
*** This bug is a duplicate of bug 1296425 *** https://bugs.launchpad.net/bugs/1296425 I found the root cause and wrote it in comments 21 and 22 of the duplicate bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1296425 SUMMARY: ubuntu-drivers-common scripts (sl-modem.py) are calling aplay -l with an empty environment, thus aplay -l creates a new pulseaudio process instead of using the session's pulseaudio, which interferes with sound card recognition (device busy errors). There is a one liner fix in the comment. Kubuntu calls ubuntu-drivers-common scripts on login to KDE, but the issue affects also Ubuntu users if they run any program that calls those scripts, until they restart. Cheers, Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325282 Title: USB microphone inputs not detected by Pulseaudio on Kubuntu Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
** Attachment added: Output of lspci -v -nn https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1351699/+attachment/4168339/+files/lspci_v_nn.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
Output of lspci -v -nn and a screenshot has been attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351699] [NEW] Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
Public bug reported: I'm on Ubuntu 14.04 (Trusty), up to date, on a computer with an NVidia GTX 750ti graphics card. I also tested on Utopic with a live daily dvd and the problem persists. The list under Additional Drivers is empty for my NVidia GTX 750ti video card: Also, running: ubuntu-drivers list or ubuntu-drivers devices produces an empty output. Running: software-properties-gtk --open-tab=4 or kcmshell4 kcm_driver_manager shows no drivers found (not even the open source driver). I'll attach a screenshot here to show this. I had to workaround by installing the nvidia-331-updates package manually by console, which works very well for my video card. Though I worry about people not so familiar with the console. The empty list happens because the ubuntu-drivers command insists on making a perfect VID:PID match with each driver, and also because the specific modalias for making that match, is missing from nvidia-331 deb package. The corresponding modalias for my NVidia 750ti is (as obtained from running ubuntu-drivers debug): pci:v10DEd1380sv1458sd362Dbc03sc00i00 Which means that this should be included in the driver package description for my card to be matched by the Additional Drivers backend: pci:v10DEd1380sv*sd*bc03sc*i* wich is currently missing from the Modaliases list in the description of the .DEB nvidia packages. That is the modalias required to make a match for the 750ti card. There are two possible solutions: - A) Please ask the maintainer(s) of nvidia packages to add that modalias to the DEB package of nvidia-331 and nvidia-331-updates packages B) OR Please ask the developers of ubuntu-drivers-common package to match nvidia drivers by VID instead of insisting that the VID and PID both match perfectly. A lot of cards are left without drivers that way (not even noveau is matching my card currently). Important Details If I look at the current list of modaliases in the nvidia drivers, by running: apt-cache show 'nvidia*' | grep -i modaliases I cannot find my NVidia 750ti, which has a VID equal to 10DE, and a PID equal to 1380. I should be able to find the string v10DEd1380. This causes the detection routine in ubuntu-drivers-common, to never match a driver (I found that routine is at /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py), because the product id code for my 750ti is missing from all the drivers, and because ubuntu-drivers-common started to require a perfect match (both vendor id and product id). The routine is called: packages_for_modalias(). There is a very big list of nvidia cards that COULD be affected by the same problem (empty AdditionalDrivers), not just my 750ti. This can be verified by looking at all the product ids for nvidia cards, and comparing to the modaliases present in the nvidia drivers packages: The PCI ID Repository http://pci-ids.ucw.cz/read/PC/10de and looking at the current full list of modaliases with: apt-cache show 'nvidia*' | grep -i modaliases For instance, the NVidia 780ti and NVidia 780 are both missing too: apt-cache show 'nvidia*' | grep Modaliases | grep d1007 apt-cache show 'nvidia*' | grep Modaliases | grep d1008 (produces empty results) Though a NVidia GT 610 that I have in an old computer of mine, can be found, and does show a list in Additional Drivers: apt-cache show 'nvidia*' | grep Modaliases | grep d104A (shows a long modalias line matching for nvidia-304 and nvidia-331 packages for the old GT 610). Please make Additional Drivers selector work for my NVidia GTX 750ti video card. FYI: This video card was released by nvidia in february 2014. Your help will be appreciated! Cordially, Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-drivers-common 1:0.2.91.5 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Aug 2 17:49:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-08-01 (1097 days ago) InstallationMedia: Kubuntu 11.04 Natty Narwhal - Release amd64 (20110427) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to trusty on 2014-05-12 (82 days ago) ** Affects: kubuntu-driver-manager (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty utopy ** Attachment added: Screenshot of empty additional drivers list and lspci
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
** Tags removed: utopy ** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
$ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) $ lspci -v -nn | grep NVIDIA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fbc] (rev a1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351699] Re: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331.
Navigating nvidia's website, I found that the 750ti was officially suported starting from the linux driver version 334.21: 334.21 March 3, 2014 Linux x64 (AMD64/EM64T) Display Driver-Release Highlights http://www.nvidia.com/download/driverResults.aspx/73666/en-us Now, the newest driver package available for Trusty is: 331.38, and the newest nvidia package available for Utopy is: 331.89. They both work with my Geforce GTX 750ti card, though they are older than the first one to mention support for the 750ti (version 331.89 vs 334.21), and don't contain the matching modalias, so no driver is listed. I understand if us users cannot be recommended to run the available drivers for ubuntu, but I still think it is a bug to show an empty driver selection list in Additional Drivers, with no message to correctly reflect what is happening, or no possibility to select a 3D enabled driver by GUI, even if not the recommended one. In summary: My 750ti works perfectly with 331.38, and I think it is a bug not to show any drivers for selection even if not recommended, and not to give a proper message to us user. Instead we get just a blank list. Best wishes, Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351699 Title: Additional Drivers / Driver Manager shows no drivers for NVidia GTX 750ti - Missing modalias in nvidia-331. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1351699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Breaking News! A fix in the form of a kernel patch has now been posted to the linux- acpi and linux-kernel mailing list: [PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems http://marc.info/?l=linux-acpim=139359680828880w=2 That kernel patch was made by Kieran Clancy and tested by me and others. -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Breaking News! A fix in the form of a kernel patch has now been posted to the linux- acpi and linux-kernel mailing list: [PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems http://marc.info/?l=linux-acpim=139359680828880w=2 That kernel patch was made by Kieran Clancy and tested by me and others. -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Many thanks juanmanuel for identifying the cause for this long running issue and for working diligently to find the fix. You're welcome, it fills me with joy reading all this good feedback!! -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
This is a NEW and BETTER patch created by Kieran Clancy on the kernel bugzilla to do the same that my workaround did, but in a more proper way, and from the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 I also tested it this weekend, and it works (I forced the issue to happen again, and then saw it being resolved automatically by a kernel compiled with this patch). The most salient advantage over the previous patch is that it also unstucks the EC when the computer starts (in addition to sleep resume). This is more fool proof and suits more use cases. It also checks the laptop model. Lets hope more people test this patch so that it can be included some day in the kernel. ** Patch added: BETTER_ec_kernel_patch.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3994501/+files/BETTER_ec_kernel_patch.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Joseph: The best kernel patch so far was made by Kieran Clancy (see post #18 here). His patch is attached to a kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=44161 in comment 149. I'm just the author of the userspace workaround (post #3, #4, #14) that started it all (see the other issue here https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 comments 102 onwards) . It is a standalone program that unstucks the EC. On the other hand, Kieran's kernel patch now does the same in a cleaner way from inside the kernel. In my humble opinion, Kieran Clancy's patch can be included in the kernel. I don't know whether Kieran will submit it. Cheers! -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
UPDATED v2: Safer because it obtains the EC ports automatically from /proc/ioports, and it micro-pauses between queries, so that the EC returns each event only once. This replaces the little program in #3. This is the program I made, that unstucks the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: samsung_fix_ec_events_v2.c https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3993249/+files/samsung_fix_ec_events_v2.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
UPDATED v2: Safer because it obtains the EC ports automatically from /proc/ioports, and it micro-pauses between queries, so that the EC returns each event only once. This replaces the little program in #3. This is the program I made, that unstucks the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: samsung_fix_ec_events_v2.c https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+attachment/3993277/+files/samsung_fix_ec_events_v2.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
** Description changed: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. - 4) echo disable /sys/firmware/acpi/interrupts/gpe17 - plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) - echo enable /sys/firmware/acpi/interrupts/gpe17 + + OR: + 1) echo disable /sys/firmware/acpi/interrupts/gpe17 + 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) + 3) echo enable /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. - WORKAROUND: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 . + WORKAROUND (kernel patch 1): + https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 + + BETTER WORKAROUND (kernel patch 2): + https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . I downloaded trusty-desktop-amd64.isofrom that link, and tested with my Series 5 NP530U3C, and the issue still persist in the latest ubuntu. So, latest ubuntu is the same. Here is what I did: 1) Downloaded ISO image 2) Put it in a 2GB pendrive using 'unetbootin' to transfer it there. 3) Booted up, selected Try ubuntu without installing. 4) Started acpi_listen, I see that plugging and unplugging are recognized as events. 5) Suspended the laptop by closing the lid. 6) Unplugged, plugged, unplugged. (8 actions or more) while suspended. 7) Resumed from sleep. 8) Now events are NOT produced anymore and the laptop got into problem state. Closing the lid doesn't suspend the laptop. The battery icon says charging even though the ultrabook is unplugged from the wall. No surprise there. Still UNFIXED in latest ubuntu (the ISO file has a date of 2014-02-22 in that download site). Another way to get the laptop into problem state would be to let it discharge or charge by 16% while suspended in S3 sleep. Christopher: Should I file a new bug report? -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
Script that calls the program found in the other attachment after resume from sleep. ** Attachment added: 99samsung_fix_ec_events https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992107/+files/99samsung_fix_ec_events -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
Attached DSDT of a Samsung Series 5 NP530U3C ultrabook with the same problem. Bios version is latest: P14AAJ ** Attachment added: DSDT_SamsungSeries5-NP530U3c-AB1_WithBios_P14AAJ.dsl https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992105/+files/DSDT_SamsungSeries5-NP530U3c-AB1_WithBios_P14AAJ.dsl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
This is the program I made, that unstucks the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: samsung_fix_ec_events.c https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992106/+files/samsung_fix_ec_events.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] [NEW] LID close and AC and battery status events not produced anymore on samsung ultrabook.
Public bug reported: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias:
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
(sorry, the link is: http://www.zenstep.com.ar/samsung-linux ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
This is a patch created by Lan Tianyu on the kernel bugzilla to do the same that my workaround did, but in a more proper way, and from the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 I tested it: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 and it works. Lets hope more people test this patch so that it can be included some day in the kernel. ** Bug watch added: Linux Kernel Bug Tracker #44161 http://bugzilla.kernel.org/show_bug.cgi?id=44161 ** Patch added: ec_kernel_patch.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992108/+files/ec_kernel_patch.patch ** Description changed: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061 + + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no
[Bug 971061] Re: acpi reports battery state incorrectly
Christopher: I created the new issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589 -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
More description about this issue found I posted in blog format here: http://www.zenstep.com.ar/samsung-laptop -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I also wanted to put all the info in one place, so I made this blog here: http://www.zenstep.com.ar/samsung-linux Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Christopher: you changed my description of the bug, and in doing so, confused the two different ways to force the issue to show up. You listed the second way as a fourth item of the first way, when it is a different way. Take a look at the original description. -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
This is not a bug in acpi (Ubuntu) as this is just a software package that displays information. Instead, this would be a bug in the linux kernel (ex. samsung-laptop.c) for not handling the laptop lid logic correctly. No, you are confounding two issues. This is a buggy behaviour in samsung's EC embedded controller when going to sleep and resuming, that can only be fixed in linux kernel ACPI handling of it ( linuxkernel/drivers/acpi/ec.c ). There is a patch ready in the kernel bugzilla, that adds a few lines to acpi/ec.c, that I personally tested and confirmed that does the same as my userspace workaround (unstuck the samsung ACPI embedded controller): https://bugzilla.kernel.org/show_bug.cgi?id=44161 (comments 133 and 135) samsung-laptop.c has nothing to do with ACPI or the LID detection or this bug. samsung-laptop.c uses a SABI interface. The reason samsung-laptop.c came up, was because that file disables keyboard backlight under certain conditions, and some people said that now that the LID and AC status works with my fix, that now keyboard backlight was the only thing missing for linux compatibility. I just brought up samsung-laptop.c to point to how to fix that last, separate, independant remaining problem of keyboard backlight. LID detection and AC status detection, is handled by standard ACPI drivers in these laptops. So, this _is_ a bug that is fixed by patching ACPI's drivers/acpi/ec.c. (or by my userspace program that pokes two EC ports, post #103). Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I'm sorry, yes, its not a bug in the userspace acpi program, rather a problem that can be fixed by the kernel ACPI or a userspace workaround (post #103). Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
The keyboard backlight issue is separate from this issue, and is not a hardware problem. Rather, that the linux devs decided to disable the samsung-laptop.c module in the kernel when you boot with UEFI, as a preventive measure when it still wasn't clear how linux interacted with that famous samsung uefi bug. Looking in: http://lxr.free-electrons.com/source/drivers/platform/x86 /samsung-laptop.c I see that the following lines prevent the module from being initialized when you use UEFI, and so keyboard backlighting isn't enabled: 1548 if (efi_enabled(EFI_BOOT)) 1549 return -ENODEV; If those two lines were introduced as a preventive measure or as a real fix for the famous samsung UEFI bug, I don't know. I have a series 5 NP530U3C which doesn't have backlighting. DO NOT uncomment those lines and recompile the kernel, unless some expert on that old famous UEFI bug says its ok to do so. But again, it is a separate issue and it's clear that the lack of keyboard backlighting is a software thing and not related to the bugs fixed here by my workaround, by unblocking the EC embedded controller. The workaround fix I posted in posts #101 through #103 fixes the problem state that the laptop gets into from a bad suspend/resume, in which LID close events are not generated, and AC plugged in status is ignored, and battery charge changed events are not generated (and maybe some temperature alert / changed issues too). And of which one could only got out by hitting the reset button through the hole in the back while turned off. Cheers! -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Yes! you're right! Looking at the DSDT I see that there are two fields, LUXH and LUXL declared in the EC operation region, which I can only guess by their name are for an ambient light sensor -- in the models that have it (mine doesn't have it). Maybe some light sensor change event wasn't produced in the problem state. So, one more thing added to the list of fixes! Thanks for illuminating us!!! ;-) -- Juan Manuel Cabo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I'm very glad!! You're welcome all of you! Nothing beats the feeling of having the whole laptop work properly !!! Can't believe this bug affected so many samsung models. So far I've seen: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B) Samsung Series 9 (models NP900X3F, NP900X4B) Does the NP900X4B work with the fix too? I'm glad that my research was successful, It's like having a brand new laptop all over again (mine is the NP530U3C). -- Juan Manuel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
(Also confirmed in this thread Samsung NP900x4c ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Following the link: https://bugzilla.kernel.org/show_bug.cgi?id=44161 I read that someone noted that AC was reported correctly after suspend, even though the EC events were consumed by the little program on resume. I'll reply here to that since I don't have an account there: The reason is because the DSDT method called _WAK (short for AWAKE), is called when resuming from sleep. If you look at the code in the DSDT, you'll see that this method checks to see if AC, LID, and Battery have changed since suspend, and issues the corresponding Notify() calls, thus producing the relevant events, when waking up, independently of the EC. -- Juan Manuel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I want to give thanks to Kieran Clancy for commenting on the kernel bugzilla, lets hope that they incorporate the fix so that non-tech-saavy people can benefit too. I just registered in the kernel bugzilla to post a summary of the problem. https://bugzilla.kernel.org/show_bug.cgi?id=44161 I guess the best place to incorporate a fix would be as I said previously, at the function acpi_ec_unblock_transactions_early() which is called at the right time in the resume process (and despit its name it doesn't unblock nothing currently). THat function is in sleep.c which already incorporates quircks for different models and can judge whether to query the events (though it would be harmless to do the query on models without the problem, it is a standard query of events). -- Juan Manuel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
99samsung_fix_ec_events ** Attachment added: Script that calls the program found in the other attachment after resume from sleep. https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+attachment/3985591/+files/99samsung_fix_ec_events -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
This program unstucks the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: This program unstucks the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+attachment/3985590/+files/samsung_fix_ec_events.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027368] Re: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close
For those of you with a Samsung laptop showing this problem, please see this issue: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 in particular my last two posts. I think a kernel patch can be made to flush the events (LID, AC plug/unplug, etc) from the Embedded Controller, at resume, in the same way that I do it with my C program that I attached to that issue for Samsung laptops (and maybe others with the problem). TL;DR: If the events don't get flushed (queried), the GPE of the EC is never triggered again (chicken and egg situation), my little program queries the events and unstucks the EC immediatly. After that, LID and AC plugged events are reported normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027368 Title: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1027368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89860] Re: /proc/acpi/button/lid/*/state always says open
For those of you with a Samsung laptop showing this problem, please see this issue: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 in particular my last two posts. I think a kernel patch can be made to flush the events from the embedded controller, at resume, in the same way that I do it with my C program that I attached to that issue for Samsung laptops (and maybe others with the problem). TL;DR: If the events don't get flushed (queried), the GPE of the EC is never triggered again (chicken and egg situation), my little program queries the events and unstucks the EC immediatly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/89860 Title: /proc/acpi/button/lid/*/state always says open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/89860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
FINALLY!! I found the exact problem _and_ a SOLUTION!!! (NOTE: see
attached program)
The problem is that Samsung's embedded controller stops sending GPE
events if it still is waiting for previous GPE events to be queried from
it.
It will remain in that state until one hits the reset hole in the back
of the latop, or flashes a bios, or queries the events.
--- But how will the OS query the events if the GPE interrupt isn't
produced anymore? Classic chicken and egg.
So I made a small program that does just that -- it queries events from
the EC until there are no more to query. AND IT WORKED!! This restores
the normal behavior, and AC, Battery and LID events start to be produced
again. One would ideally run it after resume from sleep. I based it
after observing normal behavior in linuxkernel/drivers/acpi/ec.c, and
afterwards behaviour with laptop in problem state.
Following is the program (I will attach it too). You can either:
1) Run it by hand after resume from sleep.
2) Or Automatically run it from /usr/lib/pm-utils/sleep.d/99-your-
script-here (you can use 95led as basis).
3) Or Insert this code in the linux kernel at the beginning of the
acpi_ec_unblock_transactions_early() function in
linuxkernel/drivers/acpi/ec.c and recompile the kernel. The cmd and
data ports are known in ec.c so they don't need to be hardcoded there.
PS: Other things that I already tried that didn't fix it:
1) Please note that I already tried commenting acpi_disable_all_gpes()
from linuxkernel/drivers/acpi/sleep.c and this didn't have an effect (I
guess unreplied events were already accumulated in the EC prior to resume).
2) I also tried reverting to calling acpi_enable() on sleep.c instead of
setting the ACPI_BITREG_SCI_ENABLE. No effect, issue still resurfaced after
some suspends.
3) I also tried commenting out the call to
acpi_ec_unblock_transactions_early() in sleep.c, but no effect.
PS2: Another way to force the embedded controller to be in a problem state that
I discovered, is to:
1) echo disable /sys/firmware/acpi/interrupts/gpe17
2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
3) echo enable /sys/firmware/acpi/interrupts/gpe17
Following are the two files with fixes which I'll attach too:
NOTE: you must check that embedded controller ports are 0x62 and 0x66
looking in your DSDT. RUN AT YOUR OWN RISK!!!
samsung_fix_ec_events.c --
#include stdio.h
#include unistd.h
#include sys/io.h
/* Compile with:
*gcc -o samsung_fix_ec_events samsung_fix_ec_events.c
* Run as:
*sudo ./samsung_fix_ec_events
* You may copy it to /usr/local/bin and then call it
* automatically after resume from sleep with a /usr/lib/pm-utils/sleep.d
script:
*sudo cp ./samsung_fix_ec_events /usr/local/bin/
*/
/* Constants: */
enum ec_command {
/* Standard command for querying LID, Battery and AC events: */
ACPI_EC_COMMAND_QUERY = 0x84,
/* ATTENTION: PLEASE edit the following two according to your DSDT.
* For Samsung Series 5 NP530U3C, they are 0x62 and 0x66 respectively.
* They seem to be the same for many other samsung models, but if you
don't check
* them first in the H_EC._CRS section of your DSDT, you run it at YOUR OWN
RISK: */
EC_DATA_PORT = 0x62,
EC_COMMAND_PORT = 0x66
};
int main (int argc, char** argv) {
char status = 0;
char data = 0;
int count = 0;
if (iopl(3)) {
printf(Error: Permission to read/write to EmbeddedController port not
granted.\n);
return 1;
}
/* Query AC, Battery, LID, etc. events until there are no more.
* This clears them for the EC so that it can send them again in the
future, thus unblocking the EC. */
do {
outb(ACPI_EC_COMMAND_QUERY, EC_COMMAND_PORT);
status = inb(EC_COMMAND_PORT);
data = inb(EC_DATA_PORT);
/* printf(CommandQuery 0x84, status=0x%x, data=0x%x\n, status, data);
*/
} while (data != 0 ++count 1); /* Note: No less than a thousand
max count */
printf(EmbeddedController GPE events flushed. New events can be
produced now.\n);
return 0;
}
END samsung_fix_ec_events.c --
- 99samsung_fix_ec_events --
#!/bin/sh
# NOTE: Put this file in: /usr/lib/pm-utils/sleep.d/99samsung_fix_ec_events
#
# On some samsung laptops (series 5 2012, series 9 2011, etc) , if many EC
# GPE events are produced during sleep (AC plugged/unplugged, battery % change
# change, LID open/close, etc), and they are not queried, the
# EmbeddedController stops sending them and this creates a chicken and egg
# situation, that can only be resolved either by hitting the reset button in
# the back while powered off, or by simply forcing a query for the events here
after resume.
case $1 in
hibernate|suspend)
;;
[Bug 971061] Re: acpi reports battery state incorrectly
I made further tests, and can now RULE OUT completely Intel Rapid Start from being a factor. So please IGNORE my previous post. But, I found the cause of the problem!, (but not the solution... yet): I found that the problem manifests when doing many things (16 or more) that would produce an ACPI event, while the laptop is suspended. If so, the motherboard's Embedded Controller stops sending events. If, while in sleep, you unplug or plug the laptop 8 times, then the problem manifests. Each time that you plug or unplug the laptop's PSU, a pair of ADP1 (AC power event) BAT1 (Battery event) events are produced (signals _Q51 or _Q52 (AC) and _Q53 and _Q54 (battery) of the DSDT are executed, which notify the devices ADP1, BAT1 and the CPUs). So that is two GPE events per plug or unplug, for a total of 16 if you plug/unplug 8 times. Also, if the laptop is unplugged while suspended, an event is produced each time that the battery percentage changes (_Q53 and _Q54). So, if you leave it unplugged and suspended for 8 hours or more (assuming 2% battery drop per hour), the problem then manifests. If it was plugged, and it charges 16% or more of battery, the problem manifests. LID close/open events count too. The only way that you can ensure that the problem will not manifest, is by having the battery at 100% before suspending, and leaving it plugged in, and without opening/closing the lid too many times. In my tests, no matter how many days suspended, this never produced the lid-not- detected-battery-not-detected-syndrome, which can only be gotten out of by turning the computer off, unplugging it, and hitting the reset button through the small hole in the back. This is clearly a problem with the embedded controller trying to report AC/Battery/LID events while the computer is asleep, and having some kind of internal buffer get full (16 events). REPRODUCING THE PROBLEM QUICKLY: The easier way to reproduce the problem, is: 1) Suspend the computer 2) Unplug PSU, plug, unplug, plug, unplug, plug, unplug, plug (8 actions each produces 2 GPE events). 3) Resume. Then, you can see that plugging or unplugging the PSU isn't detected, and LID close is ignored. I ruled out the following things, which DON'T produce an effect: 1) Battery Life Extension enabled or disabled. Crossing 80% battery charge while sleep. No effect. 2) Intel Rapid Start. Enabled or disabled, partition or no partition. intel_irst module and wakeup_time and wakeup_events parameters don't have an effect. 3) How many suspends without restarting doesn't have an effect. 4) Wifi on or off. Downloading or not. 5) FAN spinning with CPU temp above 70, no effect. (doesn't help nor make it worse). 6) acpi_osi=!Windows 2012 acpi_osi=Windows 2009, etc. No effect. 7) Changing /sys/module/acpi/parameters/ec_delay or ec_storm_threshold no effect (though interesting to research further, only tried 20ms and 2048 respectively; the defaults are 500ms and 8 respectively). I still haven't found a workaround or solution. I studied the DSDT of my NP530U3C, looking for a way to disable or mask the EmbeddedController events (AC, battery, LID). I overwrote a method through /sys/kernel/debug/acpi/custom (the \_SB.LID0._LID method) to try different things, like toggling the ECON variable (Embedded Controller ON) but no effect. I also compared the embedded controller ram region while the laptop was in the problem state, and while it was problem-free, by inserting the ec_sys module and looking at the output of hexdump -Cv /sys/kernel/debug/ec/ec0/io before and after. I could see there that the lid and AC and battery charge are the correct values, its just that no GPE event is generated when they change. I currently have two hypothesis: 1) It might be that the events should get masked out before going to sleep, so that the embedded controller ignores them during sleep and this is not happening for some reason. 2) It might be that if the embedded controller has too many events queued, then when resuming some kind of race condition occurs in a way that a lock or a queue gets messed up and only a reset-through-small-hole-in-the-back can fix. Maybe the Linux kernel should wait a bit after resuming before serving those events? TL;DR: The embedded controller gets messed up after 16 GPE events (AC, or battery % drop, or LID) during sleep, and when it comes back doesn't report events anymore. The DSDT signals _QXX are not received anymore. The problem never manifests if I suspend with: 1) 100% charge 2) PSU Plugged in and left that way. 3) Don't close/open the lid no matter how many hours or days, then the problem will never manifest, since % of battery doesn't change and no lid events are produced during sleep (note that a lid event takes about 10 seconds to be produced after closing/opening the lids, by design). If I unplug it, and
[Bug 971061] Re: acpi reports battery state incorrectly
Attached DSDT of a Samsung Series 5 NP530U3C ultrabook with the same problem. Bios version is latest: P14AAJ ** Attachment added: Attached DSDT of a Samsung Series 5 NP530U3C ultrabook with the same problem. Bios version is latest: P14AAJ. https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+attachment/3984824/+files/DSDT_SamsungSeries5-NP530U3c-AB1_WithBios_P14AAJ.dsl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
PS: My laptop has a 24GB SSD (alongside a 500GB HDD), in which there was originally two partitions (one used by Samsung ExpressCache, the other one I guess used by Intel Rapid Start). and... I reformated the SSD partition to install linux there when I bought it. Lucky I kept the layout: Device Boot Start End Blocks Id System /dev/sdb120483745791918727936 73 Unknown /dev/sdb23745792046895103 4718592 84 OS/2 hidden C: drive Maybe the BIOS/chipset expects an SSD partition with such and such id (84) to have suspend work properly?? (see https://communities.intel.com/message/175742 ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Hello!! After reading all the comments, and many tests of my own, I can conclude the following: 1) Kernel version / linux distro doesn't affect the issue. 2) It is a problem specific to suspending. If you don't suspend, you don't loose power monitoring/lid close. 3) There are two temporary fixes (let me contribute (B) here): A) Unplug laptop, then hit reset button through small hole in the back, then re-plug power to the laptop. B) Or: Reflash BIOS, any version, even the same one over (see my post at http://forum.notebookreview.com/samsung/683727-where-lid- closure-sensor-series-5-ultra-np530u3c.html#post9455595 in particular, please observe the /n switch of the flash utility mentioned in my post). The (B) method explains why the problem goes away with a new BIOS update (the flashing tool clears the bios internal options (see sflash.exe /n switch) Either fix is temporary and will return with an unlucky suspend/resume from sleep. 4) It is a BIOS problem, triggered by suspending in linux (and it got triggered by suspending in windows twice too in my case). The bios stops sending certain events (power, lid), because its state is corrupted somehow. When the laptop is in this state, dual booting windows has symptoms too (no lid detection, and unplug/replug events are reflected in windows' tray icon many seconds later, instead of instantaneously, as if by polling). Turning it off and on has no effect. Draining the battery has no effect. Toggling all options in the bios screen has no effect. The only fix is to do as in (3). Now, Samsung uses some technology to have a mixed sleep, with the capability to hibernate after a threshold (time? battery-low?). It has to do with Intel Rapid Start and Samsung Optimized power plan mode. After reading the comments, I theorize that it's related to the fact that samsung expects some kind of hook to be present for when the laptop decides to quit regular sleep and ask Samsung/Intel's windows drivers to enter a deeper pseudo hibernation. (See option Samsung Optimized power plan in Samsung Easy Settings in windows). I guess that both linux devs and samsung devs should work together to either: provide the second sleep hook, or a new bios that doesn't corrupt itself when not present. Will this never get fixed? Will the same behavior happen with next generation Samsung models? Or some other model/brand that has intel rapid start? BTW, I have a NP530U3C and been dealing with this issue as all of you guys. I hope this gets fixed since it is a nice ultrabook at a nice price, and this is the only problem that keeps me from fully enjoying it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
(let me add that I think the reason that it also happened to me by suspending in windows too, is that I disabled/uninstalled samsung's optimized power plan and intel rapid start, as I usually disable or uninstall the extras). I think that there is something in the bios that expects to be able to go to deep sleep, and its state is corrupted somehow if it doesn't. Here is some excerpt from some Intel Rapid Start literature: Power Manager refers to Intel Rapid Start Technology as 30 Day Standby. The 30 Day Standby uses a special Hibernation partition on the SSD to capture the contents of system memory. The benefit is a longer battery life (compared to standard Sleep mode) and shorter resume time (compared to standard Hibernate mode). To enable 30 Day Standby, the user will need to create a special Hibernation partition on the SSD and also to install Power Manager. I guess that the laptop first goes into normal sleep, keeping the RAM powered. And then wakes up briefly to serialize the RAM to an SSD partition if it was sleeping for a while, or with lower battery, to be able to remove power to the RAM. Either that, or maybe it expects the OS to have serialized the RAM to the internal SSD to already have the RAM,, and a hook to wake up. IDK. It's my best guess. PS: I dual boot win7 and Kubuntu 13.10. I have the Samsung NP530U3C running bios P14AAJ. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771788] Re: nVidia driver activated and apparently being used but reported as not being used by jockey-gtk
Hi M2-player #76, Definitely we have the same problem... by now I'm running on Ubuntu 10.04 but without nvidia graphics, anyway it's working with Extra in visual effects. I think we'll have to wait to get Unity :( -- Bob #75, as M2-player said, this is what I meant : http://i52.tinypic.com/161fcwz.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771788 Title: nVidia driver activated and apparently being used but reported as not being used by jockey-gtk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771788] Re: nVidia driver activated and apparently being used but reported as not being used by jockey-gtk
same problem. I've tried the live usb 11.04 with no problems, but after I install it, unity can't start and my xorg.conf is basic, then I checked the nvidia proprietary drivers and it shows activated but not in use. - Dell vostro 3500 - Nvidia Geforce G 310M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771788 Title: nVidia driver activated and apparently being used but reported as not being used by jockey-gtk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
