Ludovic Brenta <[EMAIL PROTECTED]> writes: > Stefan Seyfried <[EMAIL PROTECTED]> writes: >> On Thu, Sep 13, 2007 at 09:30:54PM +0200, Rafael J. Wysocki wrote: >>> On Thursday, 13 September 2007 20:58, Tim Dijkstra wrote: >>> > Hi guys, >>> > >>> > I got this report, any ideas? >>> >>> Yes (I have this box :-)). >>> >>> Use a newer kernel. >>> >>> As far as I remember, everything later than 2.6.22 should work >>> (except for some broken -mm releases). >> >> Generally (maybe we should put this into some README :-), the Kernel >> should be as new as the whitelist entry date. > > I upgraded my kernel to linux-image-2.6.22-2-amd64 (= 2.6.22-4). > Then, as previously, I did "s2ram --vbe-post --vbe-save" as root. The > symptoms remain unchanged, i.e. the screen remains black (backlight > off) and the machine is not visible on the network after resuming from > s2ram. (However, the upgrade did make a difference in that s2disk now > works: I'll close #433873).
Second try: s2ram --force without --vbe_save or --vbe_post WORKS! Is the hints file wrong, or did I misunderstand it? -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
