[Angi321]

Hello folks,

I've had Lucid 10.04 and Dharma beta3 installed and working OK.
I have upgraded to Maverick 10.10 with default kernel 2.6.35-22-generic #35 and the remote does not wake up the system anymore from standby.
I have read in many posts that reverting to 2.6.32-22 it will solve the problem and that was true under Lucid. So before using the 2.6.32-22 with proper wake-up set in "etc/rc.local" it did the job just fine.

I assumed that after few kernel releases and in fact with the new Maverick variant, this problem was solved but it seems that it is not true.
What should I do, to revert to 2.6.32-22 and forget the newly shinny 2.6.35-22?
Where are we going with this or when we should be able to use a newer kernel release and be able to wake the system from remote?

My .etc/rc.local was set to wake from remote, mouse, keyboard, etc and it did the job before. The previous and current settings are:

Code:

sudo sh -c 'echo "USB8" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB7" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB6" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB5" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB4" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB3" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB2" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB1" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB0" > /proc/acpi/wakeup'
exit 0

After restart when I do "cat /proc/acpi/wakeup" I get:

Code:

P0P2      S4    *disabled  
P0P3      S4    *disabled  
P0P1      S4    *disabled  pci:0000:00:1e.0
UAR1      S4    *disabled  pnp:00:0c
EUSB      S4    *disabled  pci:0000:00:1d.7
USBE      S4    *disabled  pci:0000:00:1a.7
P0P5      S4    *disabled  
P0P6      S4    *disabled  
P0P7      S4    *disabled  
P0P8      S4    *disabled  pci:0000:00:1c.4
P0P9      S4    *disabled  pci:0000:00:1c.5
GBEC      S4    *disabled  
USB0      S4    *enabled   pci:0000:00:1d.0
USB1      S4    *enabled   pci:0000:00:1d.1
USB2      S4    *enabled   pci:0000:00:1d.2
USB3      S4    *disabled  
USB4      S4    *enabled   pci:0000:00:1a.0
USB5      S4    *enabled   pci:0000:00:1a.1
USB6      S4    *disabled  pci:0000:00:1a.2
P0P4      S4    *disabled  pci:0000:00:1c.0

I don't understand, why USB6 port is still showing "disabled" when in rc.local is set to be enabled? Am I missing something?

Code:

htpc@htpc-linux:~$ lsusb
Bus 008 Device 002: ID 047b:0001 Silitek Corp. Keyboard
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 046d:c510 Logitech, Inc. Cordless Mouse
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have read that installing policy kit like:

Code:

sudo apt-get install hal policykit-1 devicekit-power acpid acpi-support pm-utils policykit

and other commands would fix some problems for some but not under Maverick 10.10. What is your take on this please?

[Angi321]

Nobody upgraded to Maverick having Dharma beta3 and having problems with wake up from stand-by?

[peterbo]

Same problem here, using a Shuttle XS35GT with ION2 and a "HP" InfraRed receiver which contains an IR chip from a company named FinTek.

Some people downgrade their kernel to 2.6.32 for it to work but I am still waiting and hoping for a real solution to this. If you find out how to do it in Maverick, please let me know.

[Angi321]

Apparently the 2.6.35-22 kernel was released with bugs. Hopefully the future ones will be better.

On the other line, I don't understand ubuntu: it is not windows to rush things out the door for big profits. It is a free product and if it was released yesterday or a month from now it will be pretty much the same but at least, when releasing they should make sure the bugs are almost out. That's how they build confidence. Does it make sense?