I'm planning to open a new kernel bug (or reopen that older one) in the near future. Although freak007 was able to fix theirs with a HP BIOS update it was not a dv5, and there is no such magic bullet available yet. Additionally, the dv5 suspend / resume works 100% under Vista so we know that it is not entirely the fault of HP, there is clearly a way of getting to work without a BIOS update.
I did notice the other day a difference in how Ubuntu and Vista deal with the Suspend / Resume feature:
Ubuntu puts the laptop into a suspend state that requires the power button to be pressed for resume to be triggered, whereas Vista only requires a keystroke to reactivate. Perhaps the suspend state that Ubuntu uses is just not the right one for a dv5.
I'm planning to open a new kernel bug (or reopen that older one) in the near future. Although freak007 was able to fix theirs with a HP BIOS update it was not a dv5, and there is no such magic bullet available yet. Additionally, the dv5 suspend / resume works 100% under Vista so we know that it is not entirely the fault of HP, there is clearly a way of getting to work without a BIOS update.
I did notice the other day a difference in how Ubuntu and Vista deal with the Suspend / Resume feature:
Ubuntu puts the laptop into a suspend state that requires the power button to be pressed for resume to be triggered, whereas Vista only requires a keystroke to reactivate. Perhaps the suspend state that Ubuntu uses is just not the right one for a dv5.
Does anyone else find this to be so?