Re: 8.04 release candidate delayed until Friday
On Wed, Apr 16, 2008, Alexandre Strube <[EMAIL PROTECTED]> wrote: > Dear developers, > > Owing to some setbacks getting the set of final packages built for > inclusion > on the release candidate images, the 8.04 RC will be pushed back a day to > Friday, April 18. > > This delay is not expected to impact the schedule of the final release. > Thank you! I just dist-upgraded hardy and the machines doesn't boot anymore - gotta figure out tomorrow what happened to file a bug... [] Alexandre Strube [EMAIL PROTECTED] unnamed Same problem here .. something has the fsck failing and just cycling through the reboot endlessly. regards, -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: 8.04 release candidate delayed until Friday
Paul S said the following on 04/17/2008 11:50 AM: > On Wed, Apr 16, 2008, Alexandre Strube <[EMAIL PROTECTED]> wrote: > > Thank you! I just dist-upgraded hardy and the machines doesn't boot anymore > - gotta figure out tomorrow what happened to file a bug... > > [] > Alexandre Strube > [EMAIL PROTECTED] > unnamed > > Same problem here .. something has the fsck failing and just cycling > through the reboot endlessly. Solved here. I had to boot to recovery and do fsck manually and accept all fixes, now I'm back in hardy. Not sure why so many things got borked on the ext3.. regards, Paul -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Automatic fsck
I've been bitten bad by e2fsck where it's borked my system such that I've had to reinstall. Since I don't want to be forced into that again, I'm trying to disable it permanently and take my chances on losing a file here or there. However, I can't seem to shut it off. So far, I've used tune2fs -c0 -i 0 to shut it off (interval and count are disabled .. see confirmation below). That didn't work. Next I used dpkg-divert to move e2fsck out of my path and rebuild the initramfs with update-initramfs, but it still runs on boot (I can't figure out how it got a copy of e2fsck). I have to use Esc to abort it. What's the trick to disable it on hardy?? paul :~$ sudo tune2fs -l /dev/mapper/vgsda12-lvrootsda12 tune2fs 1.40.8 (13-Mar-2008) Filesystem volume name: Last mounted on: Filesystem UUID: 8bbf135a-ecb3-4c7d-b9a6-d96fd953b657 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 892928 Block count: 3568640 Reserved block count: 178432 Free blocks: 792705 Free inodes: 602839 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 871 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 256 Filesystem created: Sat Jul 19 19:29:03 2008 Last mount time: Sun Aug 10 14:41:31 2008 Last write time: Sun Aug 10 14:41:31 2008 Mount count: 29 Maximum mount count: -1 Last checked: Wed Jul 30 19:53:55 2008 Check interval: 0 () Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode:8 First orphan inode: 869173 Default directory hash: tea Directory Hash Seed: 74af1ac9-4826-4a95-a594-b99f15b0a883 Journal backup: inode blocks paul :~$ dpkg-divert --list | grep e2fs local diversion of /sbin/e2fsck to /diverted/sbin/e2fsck -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
can't build modules on 2.6.28 jaunty
I've been running jaunty for a couple months and been unable to build the alsa driver module. I also tried buiding it from alsa-project source package and have the same failure. I had filed a bug against alsa-source, but am wondering if it's really a kernel (or kernel headers) bug. Can someone suggest how to trouble shoot? The launchpad bug link is https://bugs.launchpad.net/bugs/313481 TIA -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
rt2870sta versus rt2800
It looks like linus has committed changes in the wifi ralink driver in the final release of 2.6.31. But, karmic's kernel still includes the binary built rt2870sta (and rt2860sta). I have the hardware and would like to test this new code. Do the kernel dev's know about the change or do I need to submit a wish bug or something to get it on the list. regards, -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: rt2870sta versus rt2800
Paul S said the following on 09/15/2009 10:44 PM: > like to test this new code. Do the kernel dev's know about the change > or do I need to submit a wish bug or something to get it on the list. I just found the answer in bug 423767. disregard -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
new artwork difficult to discern active window
Under the old clearlooks, the active window had a different titlebar color than inactive windows. As much as I like the new color combo in lucid, it's difficult to use it because everything is too similar between inactive and active windows. I can't tell you how many times I've already closed the wrong window by mistake. Sorry to have to say, but I am already going to another theme. I'm sure I'm not the only one with this problem. Also, if you're right handed, it's a nuisance to have to move the mouse to the top left to close a window. thanks, though for at least trying .. paul -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: compiz & recent machines outside 1st world
Alexandre Strube said the following on 10/12/2007 07:13 PM: > except nvidia and ati (with SEVERAL exceptions), they mostly suck with What does "suck" mean specifically. I'm wondering if all the "delays" built into the standard configuration of compiz are making you think it's slow. This was my situation. So, I opened up the config program and went through all the menus and reduced the delays. Now things are zippy and I'm happy, although still not quite as zippy as no compiz. > system to a state as good as feisty. In fact, when EVERY window opens You can confirm whether you have compiz off by searching through your processes. Use "ps aux" in a terminal and scroll the output for any compiz .. "ps aux | grep compiz" will also help but it doesn't show everything. > is not enough to move a window. What does "move a window" mean? Are you talking about something that can be fixed by reducing the delays in compiz config manager? HTH -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/14/2008 10:23 AM: >> watching over it at all? if so, please let me know what i can do to >> help with debugging and stuff. > > Yes, I'm looking after it. I also would like to see suspend and hibernate finally work, so I upgraded to hardy to try it too. I'm a kde user, so may have some different issues. For example, I can do "sudo pm-suspend" at the terminal and it works, but kde-power-manager does nothing when I select suspend from it's menu. Also, I notice some problem that may be related to artsd failing after 2nd and higher suspends, so I added a script to /etc/pm/sleep.d/ to stop and restart all sound programs and it seems to fix it, although I need more testing. But, I'm not a coder, so someone who is might fix it in artsd. Are you the contact for these kubuntu issues as well as the ubuntu lead? Is it too early to start feedback on this stuff now, or should we continue? Do you want us to feedback on this list or start bugs? regards, Paul -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matt Price said the following on 01/14/2008 02:10 PM: > hmmm... fooling around, i find that i can suspend pretty reliably from > the command line > > sudo pm-suspend > > but that the gnome-power-manager dialog reliably fails to resume; this > despitethe fact that it seemsto be using pm-suspend, as it writes a > suspend log to /var/log/pm-suspend. not sure what's going on there. maybe coincidence, but this sounds similar to my experience with kde-power-manager. Suspend / resume working from konsole with "sudo pm-suspend" , but not working from kde-power-manager menu or from logout -> suspend (using kdm, not gdm). But, here it's only with suspend, as hibernate works from kde-power-manager menu. I also notice that my sleep button on my usb keyboard no does not work on hardy (but did on gutsy). The other multimedia keys work ok on hardy as well as gutsy. Not sure why just the sleep quit. It calls suspend, not hibernate. So, with both operating systems not working, could it be the underlying hal system that's not functioning correctly? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/14/2008 06:42 PM: > On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote: > >> sudo pm-suspend > > Right, so it sounds more like the issue here is that we're passing > quirks that are breaking your system. For reference, the quirks that are > used by default on Ubuntu are currently: > > --quirk-dpms-on > --quirk-vbestate-restore > --quirk-vbemode-restore > --quirk-vga-mode3 > --quirk-vbe-post > --quirk-reset-brightness > > If you pass those, does it fail? If so, can you try to figure out which > one is causing it? > I've tried this twice and it succeeded both times: paul :~$ sudo pm-suspend --quirk-dpms-on --quirk-vga-mode3 --quirk-reset-brightness --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore I must admit I am surprised because I have an nvidia driver 169.07 and always thought it did not support use of vbetools. In fact the nvidia-glx-new README says: o Some distributions use a tool called vbetool to save and restore VGA adapter state. This tool is incompatible with NVIDIA GPUs' Video BIOSes and is likely to lead to problems restoring the GPU and its state. Disabling calls to this tool in your distribution's init scripts may improve power management reliability. But the proof is in the success. By the way, I don't see --quirk-reset-brightness in the pm-suspend man page??? Still no idea why kde-power-manager can't start a suspend -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Paul S said the following on 01/14/2008 08:17 PM: > Still no idea why kde-power-manager can't start a suspend Here's an idea .. maybe some of the old acpi-support suspend is still active. I just tried adding a logger line to /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux to print out the $QUIRKS: # We only support pm-utils if [ -x "/usr/sbin/pm-suspend" ] ; then logger "pm-suspend quirks are $QUIRKS" /usr/sbin/pm-suspend $QUIRKS RET=$? Since kde-power-manager won't work and my usb keyboard sleep button doesn't work, I tried the Fn-Esc key combo on the laptop, which is the suspend key combo. The laptop suspended and resumed fine. Now, when I look at /var/log/messages, there is no line from the logger that I inserted above. Also, when I look at /var/log/pm-suspend.log, it never changed from the previous suspend. So, it appears something else is functioning to suspend, other than pm-utils via hal. I did an upgrade from gutsy. Maybe my system still has something installed that it shouldn't. If you want, I could probably do a fresh install from hardy alpha 3 .. let me know if you think it's necessary. regards, -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/15/2008 07:12 AM: > On Mon, Jan 14, 2008 at 09:17:29PM -0500, Paul S wrote: > >> Since kde-power-manager won't work and my usb keyboard sleep button >> doesn't work, I tried the Fn-Esc key combo on the laptop, which is the >> suspend key combo. The laptop suspended and resumed fine. Now, when I >> look at /var/log/messages, there is no line from the logger that I >> inserted above. Also, when I look at /var/log/pm-suspend.log, it never >> changed from the previous suspend. So, it appears something else is >> functioning to suspend, other than pm-utils via hal. > > Yeah, something's clearly catching that. Can you try changing > /etc/acpi/events/sleepbtn to call sleepbtn.sh and not sleep.sh? > paul :/etc/acpi/events$ cat sleepbtn # /etc/acpi/events/sleepbtn # Called when the user presses the sleep button event=button[ /]sleep action=/etc/acpi/sleep.sh changed: paul :/etc/acpi/events$ sudo nano sleepbtn paul :/etc/acpi/events$ cat sleepbtn # /etc/acpi/events/sleepbtn # Called when the user presses the sleep button event=button[ /]sleep action=/etc/acpi/sleepbtn.sh but same result .. /var/log/pm-suspend.log does not change, suspend / resume work only from laptop Fn-Esc, not kde-power-manager menu or usb keyboard sleep button and no "logger" message in /var/log/messages. Do I need to reboot after changing that file? If so, I did not. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/15/2008 09:00 AM: > acpid needs restarting, so rebooting is the easiest way to do that. If > Fn+Esc no longer works, there's some sort of KDE issue. This is not good. I had a kernel update so had to reboot anyway. Now I find that even Fn-Esc does not work. The only way to suspend is by konsole with "sudo pm-suspend" and it still works ok. The kde-power-manager menu "suspend" does not work. either nor the keyboard "sleep" button. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/15/2008 01:59 PM: > On Tue, Jan 15, 2008 at 09:30:13AM -0500, Paul S wrote: > >> This is not good. I had a kernel update so had to reboot anyway. Now >> I find that even Fn-Esc does not work. The only way to suspend is by >> konsole with "sudo pm-suspend" and it still works ok. The >> kde-power-manager menu "suspend" does not work. either nor the keyboard >> "sleep" button. > > Ok. Sounds like KDE is failing to respond to the sleep button signal. > I'm afraid I've no expertise beyond this point. > Ok, I switched over to gdm and gnome and have similar problems. It suspends but does not resume. So, I've been trying to work it out in a terminal. What I've discovered is that I can enter this and it works: sudo pm-suspend --quirk-dpms-on --quirk-vga-mode3 --quirk-reset-brightness --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore However, when I hit the suspend button, hal initiates the quirks in this different order: --quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode3 --quirk-vbe-post --quirk-reset-brightness so, if I try it in a terminal, it suspends but does not resume (same result as suspend button): sudo pm-suspend --quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode3 --quirk-vbe-post --quirk-reset-brightness Now, I believe the problem is that my nvidia driver does not support the vbetool. But, why it works in the different order is puzzling to me. Did you know that order matters? Also, I have tried and successfully resumed from: paul :~$ sudo pm-suspend --quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode3 --quirk-reset-brightness and successfully from: paul :~$ sudo pm-suspend --quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode3 --quirk-reset-brightness --quirk-vbe-post This makes me think that --quirk-vbe-post is the problem, but only is ok in certain orders. I'm not sure I have enough time to try all the combinations? Also, I have gone back to kdm and kde and have the same experience in the terminal, so there's not a problem in kde Now that I know that, is there someplace I can config which quirks are called and in what order? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/15/2008 05:42 PM: > I can't see how this can happen - the same environment variables are set > in both cases independent of the ordering. Is this repeatable? > Yes, many times. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matthew Garrett said the following on 01/15/2008 06:02 PM: > Though, having said that, I have found various issues - I've just > uploaded a new pm-utils. It'd be nice to know if it worked for you. > OK, I'm updating daily, so when it hits the repos I'll get it, unless you have an advance copy you can send me. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matt Price said the following on 01/15/2008 05:35 PM: > paul, how did you find out that the suspend button initiates quirks in > the order you describe? I edited /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux and added a line to log the value of $QUIRKS when it was called, as follows: # We only support pm-utils if [ -x "/usr/sbin/pm-suspend" ] ; then logger "pm-utils quirks are $QUIRKS" /usr/sbin/pm-suspend $QUIRKS RET=$? then, after suspending, I just grepped /var/log/messages for "quirks" and it was there, like this: paul :~$ grep quirks /var/log/messages Jan 15 09:32:10 localhost logger: pm-suspend quirks are --quirk-dpms-on --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode3 --quirk-vbe-post --quirk-reset-brightness then, I copied the quirks options and pasted into a terminal after "sudo pm-suspend" and found it fails to resume (screen stays black) >> Now that I know that, is there someplace I can config which quirks are >> called and in what order? >> >> > take a look > at /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux & related > scripts -- the $QUIRK variable is built up in these scripts > progressively; all you would need to do is to alter the order in which > that's done. you might also want to submit a patch or at least > bugreport to upstream, as i imagine no one's especially wedded to the > order of those quirks. I see this section: # Make a suitable command line argument so that the tools can do the correct # quirks for video resume. # Passing the quirks to the tool allows the tool to not depend on HAL for data. QUIRKS="" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_BIOS" = "true" ] && QUIRKS="$QUIRKS --quirk-s3-bios" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_MODE" = "true" ] && QUIRKS="$QUIRKS --quirk-s3-mode" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_SUSPEND" = "true" ] && QUIRKS="$QUIRKS --quirk-dpms-suspend" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_ON" != "false" ] && QUIRKS="$QUIRKS --quirk-dpms-on" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBESTATE_RESTORE" != "false" ] && QUIRKS="$QUIRKS --quirk-vbestate-restore" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBEMODE_RESTORE" != "false" ] && QUIRKS="$QUIRKS --quirk-vbemode-restore" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VGA_MODE_3" != "false" ] && QUIRKS="$QUIRKS --quirk-vga-mode3" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBE_POST" != "false" ] && QUIRKS="$QUIRKS --quirk-vbe-post" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RADEON_OFF" = "true" ] && QUIRKS="$QUIRKS --quirk-radeon-off" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RESET_BRIGHTNESS" != "false" ] && QUIRKS="$QUIRKS --quirk-reset-brightness" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_NONE" = "true" ] && QUIRKS="$QUIRKS --quirk-none" but this script requires you to know the value of each of the variables, and I haven't been able to find those variables anywhere. I can usually follow bash scripts, but have no experience with C/C++ code, which may be where they are set. Do you know? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Paul S said the following on 01/15/2008 07:18 PM: > Matt Price said the following on 01/15/2008 05:35 PM: >> take a look >> at /usr/share/hal/scripts/linux/hal-syspem-power-suspend-linux & related >> scripts -- the $QUIRK variable is built up in these scripts >> progressively; all you would need to do is to alter the order in which >> that's done. you might also want to submit a patch or at least >> bugreport to upstream, as i imagine no one's especially wedded to the >> order of those quirks. > > I see this section: > > # Make a suitable command line argument so that the tools can do the > correct > # quirks for video resume. > # Passing the quirks to the tool allows the tool to not depend on HAL > for data. > QUIRKS="" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_BIOS" = "true" ] && > QUIRKS="$QUIRKS --quirk-s3-bios" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_MODE" = "true" ] && > QUIRKS="$QUIRKS --quirk-s3-mode" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_SUSPEND" = "true" ] && > QUIRKS="$QUIRKS --quirk-dpms-suspend" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_ON" != "false" ] && > QUIRKS="$QUIRKS --quirk-dpms-on" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBESTATE_RESTORE" != "false" ] && > QUIRKS="$QUIRKS --quirk-vbestate-restore" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBEMODE_RESTORE" != "false" ] && > QUIRKS="$QUIRKS --quirk-vbemode-restore" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VGA_MODE_3" != "false" ] && > QUIRKS="$QUIRKS --quirk-vga-mode3" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBE_POST" != "false" ] && > QUIRKS="$QUIRKS --quirk-vbe-post" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RADEON_OFF" = "true" ] && > QUIRKS="$QUIRKS --quirk-radeon-off" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RESET_BRIGHTNESS" != "false" ] && > QUIRKS="$QUIRKS --quirk-reset-brightness" > [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_NONE" = "true" ] && QUIRKS="$QUIRKS > --quirk-none" ok, now I get it .. since these are based on not being false, they are set. and "sudo lshal | grep quirk" shows that they are not set to false. So, I just have to rearrange the order of these lines like so, and it works: [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_BIOS" = "true" ] && QUIRKS="$QUIRKS --quirk-s3-bios" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_S3_MODE" = "true" ] && QUIRKS="$QUIRKS --quirk-s3-mode" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_SUSPEND" = "true" ] && QUIRKS="$QUIRKS --quirk-dpms-suspend" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_DPMS_ON" != "false" ] && QUIRKS="$QUIRKS --quirk-dpms-on" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RESET_BRIGHTNESS" != "false" ] && QUIRKS="$QUIRKS --quirk-reset-brightness" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VGA_MODE_3" != "false" ] && QUIRKS="$QUIRKS --quirk-vga-mode3" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBE_POST" != "false" ] && QUIRKS="$QUIRKS --quirk-vbe-post" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBEMODE_RESTORE" != "false" ] && QUIRKS="$QUIRKS --quirk-vbemode-restore" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_VBESTATE_RESTORE" != "false" ] && QUIRKS="$QUIRKS --quirk-vbestate-restore" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_RADEON_OFF" = "true" ] && QUIRKS="$QUIRKS --quirk-radeon-off" [ "$HAL_PROP_POWER_MANAGEMENT_QUIRK_NONE" = "true" ] && QUIRKS="$QUIRKS --quirk-none" Now this is fine for my dell with nvidia driver, but I hope it works for others too. regards, -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: tracking down suspend/hibernate bugs?
Matt Price said the following on 01/15/2008 10:08 PM: >> Now this is fine for my dell with nvidia driver, but I hope it works for >> others too. >> > didn't catch this, what model is your dell? mine is latitude d820, if > you're the same maybe we've identified a laptop-specific bug. I have an E1505 (aka 6400) with nvidia 7300 go video. regards, -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
