On Wed, Jan 14, 2004 at 06:26:02PM +1030, Daniel O'Connor wrote: > On Wednesday 14 January 2004 17:29, Stijn Hoop wrote: > > On Wed, Jan 14, 2004 at 03:02:27PM +1030, Daniel O'Connor wrote: > > > In theory your BIOS could support S4BIOS which means it does most of the > > > work, but I don't think anyone has ever had that work either. > > > > I had this working on a Dell Inspiron 4150, but it turned out to be much > > slower than just rebooting the thing (about 60 seconds for reading/writing > > it all to disk vs about 30 seconds for booting). I needed to get a Dell > > utility from the website (S2D.EXE iirc) and create a suspend to disk > > partition *as the first partition on the disk*. > > OK, interesting :) > I have an Inspiron 8000 and in 4.x I could suspend to disk using the BIOS > after making an image partition. > > > And of course, resuming within X was not really supported because some > > things like the display failed to properly reinitialize, just like with S3. > > I added a vidcontrol command to switch to the console on suspend, and to X on > resume which fixed the minor glitch I got at the top of the screen. > > > In the end I decided to dedicate the space to something else. It wasn't > > worth it IMHO. An OS-based S4 might turn out to be much more useful. > > Yeah same here, the BIOS suspend is crippled because it can't do DMA (I > believe) and doesn't know what can be thrown away so it takes ages. Not to > mention the PITA factor if you upgrade the amount of RAM you have.. > I remember that when I had my laptop with S4BIOS functionality, I have to *not* disable bus arbitration before suspending, and to set the _OS to something that contains Microsoft in it. Unfortunately, I don't have anymore that laptop, and worst, it has only linux on it... -- Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care.Received on Wed Jan 14 2004 - 01:07:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:37 UTC