piix4_smbus 0000.00.07.0: SMBus base address uninitialized - upgrade bios or use force_addr=0xaddr
This error is caused by VM having no smbus but Ubuntu always trying to load the module. It doesn't affect anything but is a bit annoying - to fix...
1. Check module is being loaded
lsmod | grep i2c_piix4
2. If so, blacklist it in /etc/modprobe.d/blacklist.conf, by adding the following to the end of the file:-
blacklist i2c_piix4
3. Update the initramfs
update-initramfs -u -k all
worked perfectly... thanks
ReplyDeleteThanks for this help.
ReplyDeleteVery interesting topics you have. You and I share the same interests. I'm always looking for blogs like this. I've added your RSS feed to my Reader.
ReplyDeleteThanks!
Regards,
Bikkel.
Fantastic!!
ReplyDeleteWorked perfectly! Linux Mint is now running 100% perfectly in VirtualBox without that nag message. Thank you.
ReplyDeleteGreat, thanks!
ReplyDeleteThanks, it worked!
ReplyDeletethanks for your timely help!!
ReplyDeleteHi !
ReplyDeleteWas facing the same problem. I'm a first time user of linux, was thinking of reinstalling ubuntu.
But you saved the day !
thanks!
super thanks!
ReplyDeleteSounds great, and simple -- except I'm just moving from Windows to Maverick Meerkat (Ubuntu 10.10) and I have NO IDEA how/where to make these changes! I wouldn't even call myself a newbie ...
ReplyDeleteAnyone care to guide me through it ... or point me to a place that will help me get there (without having to learn everything about linux before I can do it ;-) )
Thanks guys
flashfletch
Oh. Running Oracle VB 4.0.2 on a Samsung N220 netbook with 2Gb under Win 7 Starter.
ReplyDelete(My intention is to move to Meerkat entirely once I become familiar enough with it on the VB ...)
flashfletch
[...] on functionality, but it possibly had an impact on speed of boot.I managed to find the answer here:http://finster.co.uk/2010/11/16/virtualbox-piix4_smbus-error/Essentially, you do the following:Start a terminalsudo vi /etc/modprobe.d/blacklist.confAdd the line [...]
ReplyDeleteThanks for the solution :)
ReplyDeleteHelped make my VM boot screen cleaner.
[...] un pò sul web mi sono imbattuto in questo blog, anche se è riferito a VirtualBox, il principio di fondo è lo stesso, quindi ho seguito le [...]
ReplyDeleteWorks perfectly, thanks a bunch!
ReplyDeleteThat error message was extremely annoying.
Thanks for the guide. I've used the same steps on Ubuntu 10.10 x86 and x64 virtual machines in virtualbox. Fixed the nag message on both.
ReplyDeleteblacklist: command not found
ReplyDeleteUsing Ubuntu 10.10
@apveening, read step #2 carefully.
ReplyDeleteExcellent work, my bootscreen is now pruned nicely.
ReplyDeleteThanks a lot for the post.
Cheers
[...] @ Reply Hi there, Check out the following link: http://finster.co.uk/2010/11/16/virt...4_smbus-error/ [...]
ReplyDeleteWorks perfectly, thanks a lot!
ReplyDelete[...] Credits: http://finster.co.uk/2010/11/16/virtualbox-piix4_smbus-error/ This entry was posted in Uncategorized. Bookmark the permalink. [...]
ReplyDeletethx!
ReplyDeleteIn Arch Linux, replace step 3 with:
ReplyDelete# mkinitcpio -p linux
Check https://wiki.archlinux.org/index.php/Mkinitcpio for more information.
Thanks. For me however worked these steps:
Delete1. # vim /etc/modprobe.d/modprobe.conf
2. Add this line to this file:
blacklist i2c_piix4
2. # mkinitcpio -p linux
cool
ReplyDeleteThanks Pedro just as you say I changed the step3 with your command and it worked for Arch Linux.
ReplyDeletewhere do i type these? im using damn small linux as a firewall and VB for Ubuntu when i try to install Ubuntu i get that right underneath the Name and d/l bar on screen then it goes into install mode everything goes well until i either power down for my VB too save or when i skip that and install all my updates it stall on smd client then i just freezes and i have to repeat everything over
ReplyDeleteI don't know how to do this , when i start my VM and begin installing ubunto 12.04 it shows me this error message , so I don't know to do any of your steps
ReplyDeleteThanks a lot. Worked perfectly (Ubuntu running on VM Virtual Box). Boot now is OK.
ReplyDeleteUnder Arch Linux (maybe others) you can also do this by adding modprobe.blacklist=i2c_piix4 to your kernel command line in /boot/grub/menu.lst
ReplyDelete*** just perfect *** thx! ***
ReplyDeletehow to check module and intrafms? NO idea
ReplyDelete...worked perfectly for me, too.
ReplyDeleteThank you very much!
Sorry can u teach me how to type all the things step by step?
DeletePress the "space bar" and "e" keys simultaneously when you start loading the virtual machine. Use "nano /etc/modprobe.d/blacklist.conf" command and put "blacklist i2c_piix4" line.
DeletepLs help how to what should i do... where can i type the codes?
ReplyDeleteShawn hie, did you get the instructions, if you did , kindly share them
ReplyDeletethanks
Hi Deeman, I dont know about Shawn, But I am also trying for this answer. When exactly to type these commands ? After UBUNTU Installs and typing this commands in a Terminal - but for me - linux installed does not let me log in to.
DeletePlease Help !
Hi,
ReplyDeleteI am working with Virtual-Box4.18.2 and I installed 2 virtual machines to try, UBUNTU12.04 server and UBUNTU 10.04 server.
What I am trying to do is install an server application I have on the VBOX HARDDISK. This application is on a bootable CD, when I boot from the CD, and run the installation I get this messege and get thrown out of the installation.
In my case these steps did not solve my issue. Any idea what might be the issue?
Most of you give thaks for another's help, a few of us ask for your help, nobody is willing to help us in how/where to use those commands. !!!
ReplyDeleteThese instructions were for removing the warning message during booting, and are only useful if your machine can boot and you can get to a terminal window.
ReplyDeletebut where we type this commands
ReplyDeleteThank you very much, it worked perfectly !!!
ReplyDeletefor centOS replace step 3 with dracut --force
ReplyDelete