Linux Mint 16 - Lock Screen Firmware Bug
2014-04
After playing around with a lot of dual-boot configurations, I've recently decided to ditch Windows (8.1) altogether and have installed Linux Mint.
I am running Mint 16 Petra with MATE Desktop
This issue hasn't caused any harm that I know of, and hasn't really interfered with anything.
When I lock my laptop, or just close the lid, I open it up to find a few lines being spat out at me saying I have a firmware bug. They are quickly replaced by the dialog box requesting for my password to unlock the computer, but I have managed to take a picture of the errors.
They are a series of errors that say:
[*some numbers*] [Firmware Bug]: cpu *X*, try to use APIC500 (LVT offset 0)
for vector *some hex*, but the register is already in use for vector *more hex*
on another cpu
- It seems the some numbers are different each time
- The X is either cpu 1, 2, or 3 (in sequence for each line)
- The first set of hex is always 0x400
- The second set of hex is always 0xf9
My Laptop:
- TOSHIBA Satellite S855D Version PSKG2U-028005
- AMD A10-4600M APU with Radeon HD Graphics
- Kernel: 3.11.0-12-generic x86_64 (64 bit, gcc: 4.8.1)
- Bios: Insyde Version: 6.30
Has anyone had experience with this? Need anymore info on the computer or distro?
More info here
Seems it is a BIOS bug that is very common on AMD platforms.
How do you install the Asus USB-N13 wireless adapter, 802.11b/g/n model onto mint 11 64bit CD version. The driver/firmware is not included by default...
It appears there is a driver available directly from Asus, and is available for Linux. One is just a driver, while the other includes some sort of client.
Just extract the file, then cd
into the directory. Run ./configure
along with make
and make install
Find the bin file, this might be it, but I can't test anymore, you can then use sudo nautilus
to move it into the firmware folder, then reboot.
Warning: The driver causes your OS to hang occasionally and does not work properly. I advise you to get a new wireless adapter. I guess that's why the driver wasn't included out of the box...