Acpi Compliant Bios
Clara Vanliere
USB is GPT formatted?
I see following options in your BIOS >> Enable ACPI Auto Configuration (Default is disabled at optimized, and enabled at Fail safe - so you can try loading fail safe instead and see if that helps, or enable while on optimized if you can see this option)
The disable enable acpi auto configuration in award bios is for to hide or show the sleep s1 s3 options and gpu repost after sleeping. All the manufacturers have this disable so the user can control them manually.
Sound card is audigy rx?
@Lost_N_BIOS First time i see the same option to not have the same value:
I believe this value must be the same. It cant be in one folder s3+s1 and in the other folder only s1.
The 2 optimal codes must be the same when run the pc for first time.
A u can see in my photos the sleep in the 2 sections has different value. The one has s3+s1 and in the the other photo like the one u posted has the value s1.
In the folder below main that is the active bios code has s3+s1, and under acpi the sleep otpion is only s1.
This options must be identical.
The enable disable acpi is only there because if it is disabled it hides only the below options from user. It has no other meaning.
right, windows xp was the last Microsoft os to support multiple (standard, apm ahci, multiprocessor and so on) hal, whereas in vista and later they only support single and multi processor ahci hal and in 7 is worse
still that's not the biggest problem, assuming you can get it to work, you need to take in account the incompatibility
there's no support at all for pre-pci devices, no support for game port and it'll lack support for anything, and it'll be slow
you could try, but acpi isn't only a bios thing, the motherboard must support and have all the necessary electronics for it to work
clover only "emulates" an uefi environment, so that an os that needs that can boot, or like windows, that needs to be in uefi mode to be able to install it that way
Well, I looked into it, but reports vary, so it might be r4111 being the latest that has 32bit support in the compiled package.
Anyway, haven't tried it myself, so I guess google is your friend ? or duckduckgo or ...
I have a desktop from 2014 with an ASUS motherboard with an AMD10 processor and 16GB of Ram (i mean it was previously compatible hardware). The bios is from American Megatrends dated 2013. I started with Ubuntu 14.04 LTS and moved on to 16.04 LTS then 18.04LTS ( which caused a lot of problems so i reinstalled with 20.04 LTS) in June 2022 I reinstalled my PC with 22.04 LTS. I never had any ACPI error during the Boot process.
Since october 2022 my PC has been playing up with ACPI errors during the Ubuntu boot process that flashed by and I couldnt read and it died around last christmas. worse imho it has killed a 2 TB (3.5") HDD but my system disk an SSD is still working, but i cannot be sure about that.
Before my holidays in september my PC started without playing up, i mean before i couldnt get a cupper while booting, from october onward i could go away and take a shower while waiting for my PC to boot.I have Ubuntu 22.04 on a stick and it doesnt matter if I boot from the stick or the SSD it takes time, bloody much time.
So I can categorically deny that the ACPI error problem is linked to new hardware, imho itś linked to the way ubuntu 22.04 is looking at ACPI and i expect an update after june 2022 is the cause of the problem.
my next step is to go back to Ubuntu 20.04 LTS As a test i pout and iso image of the 20.04.1 LTS that i downloaded in 2020 on a disk and booted, and lo and behold no ACPI errors ....this begs the question what happened with the UBUNTU between 20.04.1 and 22.04 that might cause the ACPI boot problems on hardware that was compatible befor the advent of 22.04 ?
One of the solutions is to change the Grub config file and add noacpi, acpi strict or whatrever. but i cannot get that done:
please can someone describe how I can do thias after booting from a flahdrive/usb stick , how I get to that /etc/default/grub file on the SSD, how I can edit it and how to save it , then how to pass it through the grub2 executable from a system that doesnot boots only from a bootable USB stick
If you cannot get into the system you can go to recovery mode by hitting ESC right after BIOS to get into grub and then go to Advanced options and select the recovery linux image. From there you should be able to drop into a root terminal.
You should have rw, but I am not super familiar with it on Ubuntu 20.04, if you dont have RW you can remount the drive by doing mount to list your mounts and find your root mount to remount as rw. to remount it you need to do mount -o remount,rw and if it is not / you can do chroot .
We have some PowerEdge CS24 servers that won't run Windows Server 2008. Both installer and cloned images promptly BSOD on boot with an error The BIOS in this system is not fully ACPI compliant. I noticed the ones that did work had a newer bios version. So I've set about looking for bios firmware updates for these servers.
First looked at the motherboard for a specific model number, but I did not find one. A search on Google resulted in a Dell manual for PowerEdge C1100 that says Regulatory Model: CS24-TY. The provided bios updates for that system (Red Hat version) failed, but at least returned a potentially useful error message:
I installed CentOS 5 on one of the machines to run the Dell Server Update Utility version 5.5, however it failed to detect any known devices, and the server log includes messages such as this is not a Dell Machine.
So in this scenario, we have a set of identical machines running either of two different versions of bios firmware. The older version has a defect, so one workaround is to simply use the newer bios version as a replacement. That means we need a utility to dump the firmware contents on one machine, and then flash it onto the others. I'm sure there's several applicable tools, but I ended up stumbling onto one provided by Intel.
Intel includes a DOS based firmware flashing tool called AFUDOS.EXE with some of their firmware packages. I didn't find a definitive place to obtain this tool, so I just used the one included with this driver. AFUDOS didn't need any dependencies, so I just thew it on a bootable FreeDOS usb drive I made with Rufus. Then it's simply a matter of booting the machines and running the tool. The tool has a built in check that will cancel any firmware flashing if the binary is the wrong size. Still, be advised that you may run the risk of damaging your equipment if you use this tool improperly.
This is certainly an extreme solution that probably won't be applicable to many other situations. Unfortunately it seems David Houde's intuition was correct in this case. Dell doesn't provide any firmware updates for these particular machines. I'm glad that I found any solution at all. I just finished building a new Microsoft Deployment Toolkit server and these machines were not able to run WinPE for the same reason. But with this workaround, it's all working now!