acpi/amd64 power saving

Well, it's not a secret that no suspend features are supported on amd64. This is pretty depressing, my notebook even supports S4BIOS and I have to do a lengthy shutdown and boot instead. And let's face it, FreeBSD boots slowly, because nothing happens in parallel and often the time spent during boot is time spent waiting for something, like a network coming up, which is not necessarily required for everything that follows, so other things could be done at the same time.
 
kamikaze said:
Well, it's not a secret that no suspend features are supported on amd64. This is pretty depressing, my notebook even supports S4BIOS and I have to do a lengthy shutdown and boot instead. And let's face it, FreeBSD boots slowly, because nothing happens in parallel and often the time spent during boot is time spent waiting for something, like a network coming up, which is not necessarily required for everything that follows, so other things could be done at the same time.

I agree 100% with this. I'm on a AMD64 laptop too and this is a major letdown for me, the only one coimbined with no 3D (but I fully understand that 3D is a driver/manufacturer issue).

I'm not one of those people who constantly put their laptop to sleep but it's very useful every now and then.

Also.. 100% spot on about the boot process. It needs parallelization, even basic like the debian "shell" method.
 
for linux, i know few good project:
initng - this was pretty easy to setup
kyuba - successor of elinit (which was almost great, almost because at time i tried it, it had bugs on my box..., however it was superfast. configuring einit was a little difficult). don't know anything about kyuba, haven't been using linux in ages...

I was able to boot linux in about 9-12s with enint (from when i press space in grub, to point i get X)

I wonder what would it take to port them to FreeBSD
 
I would guess it's not possible. The most time consuming part is the hard waredetection. So the hardware detection of the kernel had to be made parallel. The second part that can consume lots of time, depending on the individual setup, is the rc-startup process. Since it already tracks dependencies it should be possible to do this.
 
The rc boot section needs parallelization. Some daemons/services even block because they wait for net etc. all this could be parallelized away.

Also, the windows logic of "loading while user types password" isn't really bad either.
 
I've seen talk of parallising rc. It would be a nice feature I think. There are some things that can make bootup quicker:

* disable geom_label and stop using labels in fstab - speeds up kernel load
* enable background_dhclient in rc.conf - removes block during network initialisation if you're using dhcp
 
I find geom labels very useful, because they allow me to take a HD out of a machine and put it into another one where it boots without changes.

When my last notebook broke, I put the HD into a USB-case and was able to continue running the system from USB without troubles on most computers.
 
I had background dhclient for some time, but I run freenet6 straight after dhcp, so I still haven't had IP, but freenet6 wanted to run, and couldn't due to lack of internet connection. Since I preffer not to run background dhclient.
 
Does anyone know about any progress lately? I'm talking about suspend/resume, which is way more important to me than fast booting.
 
Back
Top