** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/292256
Title:
backlight failed after suspend to ram on IBM X40
--
ubuntu-bugs mailing list
ubunt
** Changed in: pm-utils
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/292256
Title:
backlight failed after suspend to ram on IBM X40
--
ubuntu-bugs mailing list
ub
** Changed in: pm-utils
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/292256
Title:
backlight failed after suspend to ram on IBM X40
--
ubuntu-bugs mailing list
ub
This bug was fixed in the package linux - 2.6.31-20.57
---
linux (2.6.31-20.57) karmic-proposed; urgency=low
[ Kees Cook ]
* SAUCE: x86: brk away from exec rand area
- LP: #452175
[ Keng-Yu Lin ]
* SAUCE: (drop after 2.6.31) input: Add hotkey quirk for Samsung
Q210/
Jeremy, the kernel that fixes this issue for karmic is still waiting in
karmic-proposed queue; once other fixes also included in that version
are verified not to introduce regressions, then it will get released to
karmic-updates (and launchpad should auto-close that task of this
bugreport at that t
Never mind, 2.6.31-20-generic is OK again.
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
In 2.6.31-19-generic (Ubuntu Karmic Koala, 9.10), the problem seems to
be back. Could anyone confirm this?
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Marking Fix Released per comment #72 and #73
-JFo
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Karmic)
Status: Fix Committed => Fix Released
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/29225
unassigned canonical kernel team per policy.
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a
Just wanted to confirm that the new kernel also solves the bug for the samsung
q30 series. :-)
Thank you very much!
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: verification-done
** Tags removed: verification-needed
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I tested the kernel from proposed and yes, this works as it should:
backlight is enabled automatically. Good work!
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Accepted linux into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu)
Assign
** Changed in: linux (Ubuntu Karmic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Karmic)
Status: New => Fix Committed
** Changed in: hal-info (Ubuntu Karmic)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
backlight faile
** Also affects: hal-info (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Karmic)
Importance: Undecided
Status: New
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification b
** Changed in: linux (Ubuntu)
Assignee: AceLan Kao (acelankao) => (unassigned)
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Changed in: pm-utils
Status: In Progress => Invalid
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a
** Changed in: pm-utils
Status: Confirmed => In Progress
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux
Status: Confirmed => Fix Released
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Changed in: linux
Status: Unknown => Confirmed
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Patch available in upstream bug.
** Package changed: pm-utils (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=10985
Importance: Unknown
Status: Unknown
--
backlight f
All right. I had the time to test the
patchhttp://bugzilla.kernel.org/attachment.cgi?id=23409 (mentioned in my
previous post). This fixes the problem.
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a me
Here is the kernel bug, with a patch that is supposed to fix it:
http://bugzilla.kernel.org/show_bug.cgi?id=10985
I did not check the patch, maybe someone could?
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because y
Yes, I'm running a laptop; no, there's nothing strange about the
backlight in gnome-power-manager --verbose.
KMS is involved: a better workaround for me is to use i915.modeset=0 as
kernel option - no KMS, means quirks enabled, means backlight working
(with Japi's fix, that is; the 2372 type should
Shall I post my output of this as well?
By the way, here is a workaround for karmic:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/417599
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a memb
Valentijn Sessink, do you use a laptop?
what say:
gnome-power-manager --verbose
can you see anything strange about the backlight?
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs,
hope there will be a solution until karmic is coming...
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Hmm. Karmic Koala still has the bug and worse: pm-suspend
--quirk-s3-mode --quirk-s3-bios does not help anymore (so adding the
configuration to -pm-ibm.fdi is not a solution anymore). This is
just a preliminary notice, will see if I can find something that does
work.
--
backlight failed after
2009/5/20 Chow Loong Jin
> On Wed, 2009-05-20 at 01:30 +, maximi89 wrote:
> > Thanks! Chow,
> > how looks your configuration?...
> My configuration is the default. I did not change it.
> > you think this file need come with a default settings for works?
> > in my case with the default setting
On Wed, 2009-05-20 at 01:30 +, maximi89 wrote:
> Thanks! Chow,
> how looks your configuration?...
My configuration is the default. I did not change it.
> you think this file need come with a default settings for works?
> in my case with the default settings doesn't works...
> i going to make mo
Thanks! Chow,
how looks your configuration?...
you think this file need come with a default settings for works?
in my case with the default settings doesn't works...
i going to make more test, but i don't undersdtand really how i can use the
/etc/pm/config.d
refer: http://en.opensuse.org/Pm-utils
On Mon, 2009-05-18 at 21:25 +, maximi89 wrote:
> guys, edit the file of pm-utils
> /usr/lib/pm-utils/defaults
>
> maxim...@maximiliano:/usr/share/emesene$ cat /usr/lib/pm-utils/defaults
>
> ##
>
guys, edit the file of pm-utils
/usr/lib/pm-utils/defaults
maxim...@maximiliano:/usr/share/emesene$ cat /usr/lib/pm-utils/defaults
##
# DO NOT EDIT THIS FILE! #
FWIW I'm on Jaunty / 9.04 on my X40 as well now. As stated above, the
problem persists and the vbetool post solution still works.
cheers
Matthew
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member
On Fri, 2009-04-24 at 23:00 +, japi wrote:
> @hyperair:
> Okay...
> Is there anything we can do to get this fixed sometime?
> Should we all register at the freedesktop bugtracker and write that this is
> no hoax?
> I spent some hours to get this bug fixed for me and you also wrote a debdiff
>
Whoops forgot to read thep previous post. I'll see who I can poke.
--
Regards,
Chow Loong Jin
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@hyperair:
Okay...
Is there anything we can do to get this fixed sometime?
Should we all register at the freedesktop bugtracker and write that this is no
hoax?
I spent some hours to get this bug fixed for me and you also wrote a debdiff
file, so the 'final' bugfix is only a click away.
The bug is
unfortunately this still exists in Jaunty...
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
On Sun, 2009-03-29 at 13:55 +, japi wrote:
> But personally i find it a little frustrating, that we already had
> worked out a solution (inclusive .debdiff provided by Chow Loong Jin
> -
> hyperair) and it did not find its way into ubuntu...
This is probably because the upstream bug did not get
Thank you for confirming my solution.
I think the problem will be solved at the root now and soon no workarounds will
be necessary anymore (afaik).
Please have a look at
http://www.ubuntu.com/testing/jaunty/beta#Suspend/resume%20testing
The Kernel Team seems to be dealing with issues regarding s
Adding 2372 to the list, as Japi suggests, fixes the bug - for my
hardware; and as this is the same 2372 as Pieter Hintjens reports, this
might close the bug. (Note: it's still there in Jaunty)
$ lshal | grep system.hardware
system.hardware.primary_video.product = 13698 (0x3582) (int)
system
I have just come across this on a Thinkpad x40 with a fresh install
(yesterday) of Intrepid. Reading the posts above, I am using this work
around to suspend and resume:
>From gnome,
switch to a console ctrl-alt-f1
to suspend to RAM:
$ sudo pw-suspend
when it wakes up again with a dead back ligh
** Changed in: pm-utils (Ubuntu)
Assignee: hyperair (hyperair) => (unassigned)
Status: In Progress => Confirmed
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same problem here with an ASUS L1400 laptop. Video card is i830M.
lshal | grep system.hardware
system.hardware.primary_video.product = 13687 (0x3577) (int)
system.hardware.primary_video.vendor = 32902 (0x8086) (int)
system.hardware.product = 'L1400B series Notebook PC' (string)
syste
** Changed in: pm-utils
Status: Unknown => Confirmed
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** Bug watch added: freedesktop.org Bugzilla #18461
https://bugs.freedesktop.org/show_bug.cgi?id=18461
** Also affects: pm-utils via
https://bugs.freedesktop.org/show_bug.cgi?id=18461
Importance: Unknown
Status: Unknown
--
backlight failed after suspend to ram on IBM X40
https://
Thanks, hyperair. Can you please create an upstream bug for this and
discuss it there, too? If we deviate this logic from upstream
permanently, then we have a high risk of making the hal-info database
incompatible, too, so we must avoid that. Thanks!
** Changed in: hal-info (Ubuntu)
Status:
On Tue, 2008-11-11 at 20:58 +, vlowther wrote:
> On Nov 11, 2008, at 8:04 AM, hyperair <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2008-11-11 at 13:46 +, vlowther wrote:
> >>
> >> That is what I am saying -- instead of removing the entire hook, just
> >> remove the --quirk-vbe-post lines in t
On Nov 11, 2008, at 8:04 AM, hyperair <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-11-11 at 13:46 +, vlowther wrote:
>>
>> That is what I am saying -- instead of removing the entire hook, just
>> remove the --quirk-vbe-post lines in the smart_kernel_intel function
>> of
>> the 98smart-kernel-vide
On Tue, 2008-11-11 at 13:46 +, vlowther wrote:
>
> That is what I am saying -- instead of removing the entire hook, just
> remove the --quirk-vbe-post lines in the smart_kernel_intel function
> of
> the 98smart-kernel-video hook. That will cause the hook to not remove
> the --quirk-vbe-post q
On Tue, 2008-11-11 at 01:51 +, hyperair wrote:
> On Mon, 2008-11-10 at 21:32 +, vlowther wrote:
> > Please don't remove the hook -- just edit it to not remove the quirks
> > specifically needed.
> I'm a little worried that this will cause regressions on systems where
> the --quirk-vbe-post
On Mon, 2008-11-10 at 21:32 +, vlowther wrote:
> Please don't remove the hook -- just edit it to not remove the quirks
> specifically needed.
I'm a little worried that this will cause regressions on systems where
the --quirk-vbe-post is reported wrongly by HAL. Will that be an issue?
--
Chow
On Sun, 2008-11-09 at 12:02 +, japi wrote:
> I have no /var/run/video.rom and couldn't find a file with that name anywhere
> in the system.
> But why doesn't s2ram need that file?
That is only needed if you are using a g80 or later nVidia GPU. Intel
GPUS can be posted from the regualr BIOS n
On Sun, 2008-11-09 at 23:18 +, hyperair wrote:
> On Sun, 2008-11-09 at 22:52 +, Pieter Hintjens wrote:
> > Hyperair, could you summarize what I need to do on my thinkpad x40 in
> > order to test this fix?
> >
> Delete /usr/lib/pm-utils/sleep.d/98smart-kernel-video. It's not a "fix"
> but a
On Sun, 2008-11-09 at 23:18 +, japi wrote:
> Hm.. I don't get it...
> Why does 98smart-kernel-video remove these quirks which are "known to work"?
> (My laptop for example: it is listed in
> /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-samsung.fdi
> with the right quirk, vbe
On Mon, Nov 10, 2008 at 6:39 PM, hyperair <[EMAIL PROTECTED]> wrote:
> apt-cache policy pm-utils
[EMAIL PROTECTED]:~$ apt-cache policy pm-utils
pm-utils:
Installed: 1.1.2.4-1ubuntu7
Candidate: 1.1.2.4-1ubuntu7
Version table:
*** 1.1.2.4-1ubuntu7 0
500 http://be.archive.ubuntu.com in
On Mon, 2008-11-10 at 14:21 +, Pieter Hintjens wrote:
>
> You're right, the package is installed, but I have no idea how to see
> what version it is. pm-utils is not a command and "pm-suspend -v"
> does a suspend... :-)
apt-cache policy pm-utils
--
Chow Loong Jin
--
backlight failed after
What firmware version do you have?
( lshal | grep system.firmware.version )
If it's not 1UETD2WW,
I would suggest adding 2372 to the list of product prefixes on line 65 in the
20-video-quirk-pm-ibm.fdi.
(2371 is already in the list)
Thanks,
Jan
--
backlight failed after suspend to ram on IBM X4
[EMAIL PROTECTED]:~$ lshal | grep system.hardware
system.hardware.primary_video.product = 13698 (0x3582) (int)
system.hardware.primary_video.vendor = 32902 (0x8086) (int)
system.hardware.product = '2372GHG' (string)
system.hardware.serial = '99DT135' (string)
system.hardware.uuid =
On Mon, Nov 10, 2008 at 12:14 PM, hyperair <[EMAIL PROTECTED]> wrote:
> You can't not have pm-utils. That's where pm-suspend is.
You're right, the package is installed, but I have no idea how to see
what version it is. pm-utils is not a command and "pm-suspend -v"
does a suspend... :-)
Here is
On Mon, 2008-11-10 at 11:49 +, japi wrote:
> [EMAIL PROTECTED]:~$ lshal | grep quirk
> power_management.quirk.vbe_post = true (bool)
> [EMAIL PROTECTED]:~$ lshal | grep system.hardware
> system.hardware.primary_video.product = 13698 (0x3582) (int)
> system.hardware.primary_video.vendor
[EMAIL PROTECTED]:~$ lshal | grep quirk
power_management.quirk.vbe_post = true (bool)
[EMAIL PROTECTED]:~$ lshal | grep system.hardware
system.hardware.primary_video.product = 13698 (0x3582) (int)
system.hardware.primary_video.vendor = 32902 (0x8086) (int)
system.hardware.product = 'SQ
Oh I forgot to mention... everyone, please post the output of
lshal | grep system.hardware
--
Chow Loong Jin
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Mon, 2008-11-10 at 10:49 +, Pieter Hintjens wrote:
> On Mon, Nov 10, 2008 at 11:08 AM, hyperair <[EMAIL PROTECTED]> wrote:
>
> > Heh, that's strange, what did you change besides removing the hook?
> > What's your version of pm-utils and uswsusp?
>
> I installed and then removed uswsusp, be
On Mon, Nov 10, 2008 at 11:08 AM, hyperair <[EMAIL PROTECTED]> wrote:
> Heh, that's strange, what did you change besides removing the hook?
> What's your version of pm-utils and uswsusp?
I installed and then removed uswsusp, before removing the hook.
Don't have either of pm-utils or uswsusp inst
On Mon, 2008-11-10 at 10:00 +, Pieter Hintjens wrote:
> On Mon, Nov 10, 2008 at 6:20 AM, hyperair <[EMAIL PROTECTED]> wrote:
>
> > Anyway, could you post the output of this command?
> > lshal | grep quirk
>
> Empty: no quirk in the lshal output.
>
> > Also, coud you try sticking back
> > the
On Mon, Nov 10, 2008 at 11:00 AM, Pieter Hintjens <[EMAIL PROTECTED]> wrote:
> I replaced the 98smart-kernel-suspend-hook, but can no longer
> reproduce the original problem. Suspend/resume now works, shutting
> the lid, using the KDE power manager 'Suspend' option, and also using
> the pm-suspen
On Mon, Nov 10, 2008 at 6:20 AM, hyperair <[EMAIL PROTECTED]> wrote:
> Anyway, could you post the output of this command?
> lshal | grep quirk
Empty: no quirk in the lshal output.
> Also, coud you try sticking back
> the /usr/lib/pm-utils/sleep.d/98smart-kernel-suspend hook and trying
> this:
>
On Sun, 2008-11-09 at 23:38 +, Pieter Hintjens wrote:
> On Mon, Nov 10, 2008 at 12:18 AM, hyperair <[EMAIL PROTECTED]> wrote:
>
> > Delete /usr/lib/pm-utils/sleep.d/98smart-kernel-video. It's not a "fix"
> > but a temporary workaround. Either way the problem now is to make this
> > an official
On Mon, Nov 10, 2008 at 12:18 AM, hyperair <[EMAIL PROTECTED]> wrote:
> Delete /usr/lib/pm-utils/sleep.d/98smart-kernel-video. It's not a "fix"
> but a temporary workaround. Either way the problem now is to make this
> an official fix in the pm-utils package, while not causing regressions
> to tho
On Sun, 2008-11-09 at 22:52 +, Pieter Hintjens wrote:
> Hyperair, could you summarize what I need to do on my thinkpad x40 in
> order to test this fix?
>
Delete /usr/lib/pm-utils/sleep.d/98smart-kernel-video. It's not a "fix"
but a temporary workaround. Either way the problem now is to make th
Hm.. I don't get it...
Why does 98smart-kernel-video remove these quirks which are "known to work"?
(My laptop for example: it is listed in
/usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-samsung.fdi with
the right quirk, vbe-post.
The ibm x40 can be found in 20-video-quirk-pm-ibm.
Hyperair, could you summarize what I need to do on my thinkpad x40 in
order to test this fix?
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: pm-utils (Ubuntu)
Assignee: (unassigned) => hyperair (hyperair)
Status: New => In Progress
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
On Sun, 2008-11-09 at 18:11 +, japi wrote:
> lspci -nn|grep VGA
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
> Integrated Graphics Device [8086:3582] (rev 02)
>
> sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "Samsung Electronics"
> s
lspci -nn|grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
Integrated Graphics Device [8086:3582] (rev 02)
sudo s2ram -i
This machine can be identified by:
sys_vendor = "Samsung Electronics"
sys_product = "SQ30"
sys_version = "Revision 01"
bios_
On Sun, 2008-11-09 at 17:29 +, japi wrote:
> Yes, there is a file with the content:
>
> --quirk-dpms-on
> --quirk-dpms-suspend
> --quirk-vbe-post
> --quirk-vbe-post
> --quirk-vga-mode3
> --quirk-vbemode-restore
> --quirk-vbestate-restore
> --quirk-reset-brightness
> --quirk-radeon-off
>
Okay,
Yes, there is a file with the content:
--quirk-dpms-on
--quirk-dpms-suspend
--quirk-vbe-post
--quirk-vbe-post
--quirk-vga-mode3
--quirk-vbemode-restore
--quirk-vbestate-restore
--quirk-reset-brightness
--quirk-radeon-off
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.
On Sun, 2008-11-09 at 16:59 +, japi wrote:
> I just noticed, that s2ram does that switch to vt1 and back.
> I think that s2ram is run (if using uswsusp module), just not with the
> --vbe_post option (although pm-suspend is run with --quirk-vbe-post).
>
Okay, could you check if there's a
file
I just noticed, that s2ram does that switch to vt1 and back.
I think that s2ram is run (if using uswsusp module), just not with the
--vbe_post option (although pm-suspend is run with --quirk-vbe-post).
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You
Oh, that's something left from my testing in the last days...
just a file with the two lines
SUSPEND_MODULES="button uhci_hcd"
and
S2RAM_OPTS="--force --vbe_post"
in it.
Found that on the net somewhere (suse i think).
I deleted it now.
pm-suspend --quirk-vbe-post
does not work from tty1 (neither w
On Sun, 2008-11-09 at 14:53 +, japi wrote:
> Okay, sorry for that, i meant SLEEP_MODULE="uswsusp".
> Just to be sure i have used SLEEP_MODULE and SUSPEND_MODULE for the following
> tests :-) :
>
> Here is my logfile for SLEEP_MODULE="kernel":
> http://www.ziqu.de/launchpad/pm-suspend.log_kern
Okay, sorry for that, i meant SLEEP_MODULE="uswsusp".
Just to be sure i have used SLEEP_MODULE and SUSPEND_MODULE for the following
tests :-) :
Here is my logfile for SLEEP_MODULE="kernel":
http://www.ziqu.de/launchpad/pm-suspend.log_kernel.txt
and here for SLEEP_MODULE="uswsusp":
http://www.ziq
On Sun, 2008-11-09 at 14:10 +, japi wrote:
> sudo vbetool post does work.
> (i can switch to tty1 and type the command, which then switches my backlight
> on)
>
> I have now switched to pm-utils 1.1.2.4-1ubuntu8,
> but still
> sudo pm-suspend --quirk-vbe-post
> has no effect.
> (i have tried
sudo vbetool post does work.
(i can switch to tty1 and type the command, which then switches my backlight on)
I have now switched to pm-utils 1.1.2.4-1ubuntu8,
but still
sudo pm-suspend --quirk-vbe-post
has no effect.
(i have tried it with suspend_module="uswsusp" and "kernel" in
/etc/pm/config.d
Another thing I forgot to mention... if you can ssh into the computer,
try this command:
sudo vbetool post
This is the pm-utils vbe-post quirk. If it doesn't work, something is
wrong with vbetool, and the bug should be marked as affecting vbetool.
--
Chow Loong Jin
--
backlight failed after sus
On Sun, 2008-11-09 at 12:02 +, japi wrote:
> I have no /var/run/video.rom and couldn't find a file with that name anywhere
> in the system.
> But why doesn't s2ram need that file?
>
>
> > One thing I'd like to mention is that you don't have to "force" Ubuntu
> > to use s2ram, it's a choice t
I have no /var/run/video.rom and couldn't find a file with that name anywhere
in the system.
But why doesn't s2ram need that file?
> One thing I'd like to mention is that you don't have to "force" Ubuntu
> to use s2ram, it's a choice that's made
> here: /etc/pm/config.d/00sleep_module. Uncomment
One thing I'd like to mention is that you don't have to "force" Ubuntu
to use s2ram, it's a choice that's made
here: /etc/pm/config.d/00sleep_module. Uncomment the SUSPEND_MODULE line
and set it to "uswsusp".
--
Chow Loong Jin
--
backlight failed after suspend to ram on IBM X40
https://bugs.la
On Sun, 2008-11-09 at 00:18 +, japi wrote:
> pm-suspend --quirk-vbe-post has no effect.
> (or all quirks (/ hal fdi files) are ignored since intrepid)
>
> ** Changed in: pm-utils (Ubuntu)
> Sourcepackagename: None => pm-utils
>
vbe_post()
{
local rom="/var/run/video.rom"
# if
pm-suspend --quirk-vbe-post has no effect.
(or all quirks (/ hal fdi files) are ignored since intrepid)
** Changed in: pm-utils (Ubuntu)
Sourcepackagename: None => pm-utils
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notificati
Wow.. I tried so many things to get this working again.
There are bugreports about this issue everywhere.
It's even listed as a kernel bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10985
What happened?
>From what I have found out, the following thing happened:
- Ubuntu was using uswsusp / s2ra
Yeah, same issue here, looks like it's systematically reproducible. I
also occasionally get it going back to sleep directly after having woken
up.
This is driving me nuts, so would be incredibly grateful for any
fix/workaround!
--
backlight failed after suspend to ram on IBM X40
https://bugs.lau
I upgraded my X40 from Hardy Heron to 8.10, and now have the same issue,
systematically. The only workaround is to shutdown and reboot, rather
than use suspend.
--
backlight failed after suspend to ram on IBM X40
https://bugs.launchpad.net/bugs/292256
You received this bug notification because y
** Description changed:
IBM X40 Laptop, Ubuntu 8.10.
waking up works, network is up, screen image is there (but not really visible
w/o backlight). I can access the machine via ssh.
Only the backlight is off.
Upgrade from 8.04 - there it worked fine :-(.
+
+ A friend of mine has tested th
96 matches
Mail list logo
