Re: F7 kernel 2.6.22.1-27/33 resume issue w/ Acer TM6460

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dave,

On Sun, 2007-07-29 at 23:12 +1000, David Timms wrote:
> Patrick wrote:
> > *** resent with proper date/time. apologies for taking you back to '88 ***
> ...
> ...
> > The results of booting with various parameters are:
> > 
> > Boot param	     result
> > ----------------------------------------------------------------------
> > vga=792		      no working resume
> > vga=normal	      no working resume
> > maxcpus=1	      no working resume
> > noapic		      no working resume
> > nolapic		      no working resume
> > noapic nolapic	      no working resume
> > nolapic_timer	      no working resume
> > nohz=off	      no working resume
> > ec_burst=1	      no working resume
> > nolapic ec_burst=1    no working resume
> > acpi=noirq ec_burst=1 no working resume
> My understanding is that you need to also try:
> pm-suspend --quirk-xxx
> each quirk alone, and then again with each other. This amounts to 
> hundreds of combinations.

I tried all the ones listed in various combinations:

[root@localhost ~]# pm-suspend --help
pm-action [options]

Options can change how the supend or hibernate is done.

Possible actions are:

  --quirk-dpms-on
  --quirk-dpms-suspend
  --quirk-radeon-off
  --quirk-s3-bios
  --quirk-s3-mode
  --quirk-vbe-post
  --quirk-vbemode-restore
  --quirk-vbestate-restore
  --quirk-vga-mode3

However they all seem related to kicking the gfx back into gear while my
issue is about the harddisk not activating again. Nevertheless I tried
them and it did not make a difference.

> I looked at the existing quirks list, and found a few nb's from the same 
> manufacturer {or with same chipset/video}, noted and tried those quirks. 
> After 15 tries, I had not had success.

Same here :(

> I wish you better luck. {if not set gnome-power-manager to just turn 
> backlight off at lid close and suspend activation.

I think we need more than luck. Hopefully the regression will get fixed
soon.

> I wonder if a quirk can be written to disable suspend on machines that 
> are found to be problematic, so that we don't lose information by default.

That would not be a bad idea. Perhaps bugzilla an RFE?

Thank you for you suggestions.

Regards,
Patrick

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux