Is it fixed now? There are two fixes that had been released, but my
laptop still doesn't wake up.
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Hi,
vlowther [2008-03-25 23:15 -]:
> Yes. The default in pm-utils is to not touch the video card across a
> hibernate/resume cycle, but you can tell pm-utils to use the quirks
> passed from HAL. We may as well not break expected behaviour for those
> who do need to use quirks when hibernating
Yes. The default in pm-utils is to not touch the video card across a
hibernate/resume cycle, but you can tell pm-utils to use the quirks
passed from HAL. We may as well not break expected behaviour for those
who do need to use quirks when hibernating.
--
[Hardy] HAL breaks pm-utils quirks and re
Hi vlowther,
vlowther [2008-03-24 18:35 -]:
> The patch applied to the HAL suspend script should also be applied to
> the HAL hibernate and HAL suspend-hybrid scripts.
OK for suspend-hybrid, but for hibernate as well? are you sure?
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://
The patch applied to the HAL suspend script should also be applied to
the HAL hibernate and HAL suspend-hybrid scripts.
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This bug was fixed in the package pm-utils - 0.99.2-3ubuntu3
---
pm-utils (0.99.2-3ubuntu3) hardy; urgency=low
* Drop 96-video-quirk-ignoring.patch again. It is incomplete (since we need
to do the same on the suspend side) and does not really fit here (if
pm-utils gets quirk
... never mind, the second (0.5.11...ubuntu2) update fixed this somehow.
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Hi Johne,
I am not really sure since your problem seems to have come up much earlier,
while my wireless has been working since feisty and just broke on the hal
update - and could be unbroken by reinstalling an earlier version of hal...
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://
Hey Bernhard,
I've opened up a bug that I am relatively sure is related
https://bugs.launchpad.net/ubuntu/+bug/200064
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
(re comment #27)
That sounds like it should be a new bug.
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
For some reason the fix to hal seems to have broken my wireless lan connection
(Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) on
iwl3945). I could restore it to working condition by reinstalling a (cached)
version of 0.5.10 (hal and libhal)
a) does this make sense?
b) do I h
The fix as published is incomplete. If you are ignoring quirks while
resuming, you should ignore them while suspending.
** Changed in: pm-utils (Ubuntu)
Status: Fix Released => In Progress
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You recei
The fix applied in pm-utils is incomplete. You should also ignore quirks while
suspending the system if you are going to ignore them when resuming.
The following code block also needs to be applied to the 20video file at the
beginning of the suspend_video function:
++if [ -d /sys/modul
This bug was fixed in the package hal - 0.5.11~rc2-1ubuntu1
---
hal (0.5.11~rc2-1ubuntu1) hardy; urgency=low
* Update our git snapshot from March 01 to current 0.5.11-RC2, which brings
a few bug fixes.
- Adds properties for tablet PCs (LP: #90451)
- Fixes operation on Ma
Bernhard Gehl [2008-03-21 12:12 -]:
> Why not put something in like "25-kernel-quirk-pm-checkdefaults.fdi" which
> 1) matches for the pm-quirks and exits if any (including the ".none") quirks
> are set
> 2) matches for the ati/nvidia/intel drivers and exits if one of these is used
That's the
Fixed in hal bzr head, will upload soon.
** Changed in: hal (Ubuntu)
Status: In Progress => Fix Committed
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
(re comment # 19)
If it's crazy debugging features you want, and you are comfortable
running bleeding-edge code, I maintain a .deb of the pm-utils
development series @ http://fnordovax.org/~victor/PmUtils/
But yes, in an ideal world HAL would handle finding the right quirks and
inform pm-utils to
This bug was fixed in the package pm-utils - 0.99.2-3ubuntu2
---
pm-utils (0.99.2-3ubuntu2) hardy; urgency=low
* Add debian/patches/96-video-quirk-ignoring.patch: Ignore resume video
quirks when using the proprietary nvidia or fglrx drivers, or Intel >=
915G, since they are
Is it absolutely necessary to implement the "sensible defaults" in the
code of hal/pm-utils or wouldn't it be possible to use fdi files for
that?
Why not put something in like "25-kernel-quirk-pm-checkdefaults.fdi" which
1) matches for the pm-quirks and exits if any (including the ".none") quirks
(re: comment no. 14)
For the short term, having these quirk workarounds as part of pm-utils
is doable.
Longer term, though, there are two goals to work towards:
1) Make HAL fdi rules flexible enough to deal with things besides system
mfgr/make/model when deciding what quirks to apply. At a mini
I tried the nvidia thing (with fglrx). No luck either, the lshal | grep quirk
returns nothing.
The pm-suspend.log only tells about suspending, it doesnt even say anything
about starting resuming. It must be maybe a kernel issue. Maybe i should try
installing the kernel 2.6.22 from gutsy and see
Another discussion result with Matthew: instead of doing complicated
vendor/process ID matching for Intel, it should be sufficient to just
test for /sys/module/i915. It it is not yet 100% clear whether this will
also do the right thing on i830 and i855 (which also use that module
now), waiting for
For the record, lsmod | grep -qw nvidia -> test -d /sys/module/nvidia
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
What packages? xserver-xorg-video-intel shouldn't be providing a
config.d file, since the functionality is in the kernel and not in the
driver. The kernel can't provide it, because you can install multiple
kernel versions simultaneously and they can't all provide the file. The
logical place to put
The output of lshal |grep quirk will tell you if hal knows of any quirks
that should be applied to your system.
Also, the outputs of lsmod and a copy of /var/log/pm-suspend.log (if it
exists) would come in handy.
You can also try the workaround I used in bug# 180378 (download the 99
-non-free-nvi
I don't know for sure whether i am also a victim of this bug. However, I always
used to be able to do suspend untill now hardy alpha 6. I have a packard bell
laptop MZ057. In other word a strange model.
pm-suspend --quirk-vbestate-restore this command also didn't work.
I tried to suspend with ju
After a more in-depth discussion we clarified the situation now. The
problem is that many of the machines which do not have any FDI rules at
all need some of the quirks to circumvent some kernel problems (the
quirks mentioned in the affected patch).
So, this is what should happen:
(1) laptop mod
To do (#3) with the current ubuntu pm-utils, you should arrange for the
appropriate driver package to drop a file in /etc/pm/config.d. Bug#
180378 has the solution I used to use for my system.
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received
Step (3) needs to be done in pm-utils., since this dynamic driver check
cannot be expressed in FDI rules.
** Changed in: pm-utils (Ubuntu)
Sourcepackagename: gnome-power-manager => pm-utils
Assignee: (unassigned) => Martin Pitt (pitti)
Status: Invalid => In Progress
--
[Hardy] HAL br
We just discussed this in the desktop team meeting. It is a "damned if
you do, damned if you don't" situation, but we decided to drop this
patch for the following reasons:
* Upstream FDI rules should be quite good nowadays, other distributions aren't
reportedly much worse wrt. suspend/resume tha
I'm currently discussing this with Matthew Garret via email. I'm
currently trying to understand what's necessary to drop that patch and
maintain behaviour compatibility to previous releases.
It's quite clear to me that we can't and shouldn't break upstream
behaviour eternally. We should rather add
It's still invalid for g-p-m. The bug is in the hal package.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Invalid
--
[Hardy] HAL breaks pm-utils quirks and resuming
https://bugs.launchpad.net/bugs/198808
You received this bug notification because you are a member of Ub
Confirmed while doing development on pm-utils:
On my system:
lshal |grep quirk -> power_management.quirk.vbestate_restore = true
(bool)
However, pm-suspend is called with the following parameters:
--quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore
--quirk-vga-mode3 --quirk-vbe-
33 matches
Mail list logo
