![]() | ||||||||||
Messages in this thread |
On 10/3/05, Adrian Bunk <bunk@stusta.de> wrote: > Where are hardware issues with suspend to disk? > Actually, very few currently [AFAIK, on my hardware]. However, at least in the past, my r200 card wasn't useable after resume from suspend without patches to XFree86. I know people had trouble with the fglrx drivers not supporting suspend-to-disk. [I believe current r300 drivers work fine, but I do not have personal confirmation.] I have a machine that used to have issues because I was using a keyboard and no mouse. When I resumed, the keyboard didn't work. If I had a mouse plugged in, suspend/resume worked fine. Here's a link to my mail to LKML about this issue: http://marc.theaimsgroup.com/?l=linux-kernel&m=112139506118959&w=2 As new hardware is introduced and drivers have to be written or reverse-engineered and kinks worked out, bugs like these will crop up again and again. [That is, unless manufacturers become more open about their hardware. From my perspective, they are becoming more closed. ATI, for example.] If processes could be suspended to disk independantly of the "physical state" of the machine, it would avoid issues like these. You could "suspend-to-disk", install a new video/sound/network card and then resume as though nothing happened. (Ignoring issues with TCP, of course.) Neat. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-03 18:55 [from the cache] ©2003-2008 | ||||||||||