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 A
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
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
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
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 Controlle
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 w
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
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 NP9
(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:
ht
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
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=44
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 sams
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
> 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
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
> 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 la
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 yo
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-N
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.
** Attac
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 wit
(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
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 i
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 repo
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
Tit
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/9
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 receive
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
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
** 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:
> 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
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
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 is
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 dr
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
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 scr
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 imp
** 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.
http
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 -
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
** 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 modali
$ 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
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/driverResul
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/com
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 detec
> 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 Ubun
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 scr
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 libaso
*** 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 scrip
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 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
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:
-
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-acpi&m=139359680828880&w=2
That kernel patch was made by Kieran Clan
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-acpi&m=139359680828880&w=2
That kernel patch was made by Kieran Clan
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 notificati
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/16
55 matches
Mail list logo
