Tuesday, 16 November 2010

VirtualBox piix4_smbus Error

VirtualBox 3.2.10 gives me the following error message when booting Ubuntu 10.10:-
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

47 comments:

  1. worked perfectly... thanks

    ReplyDelete
  2. Thanks for this help.

    ReplyDelete
  3. Very 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.

    Thanks!

    Regards,
    Bikkel.

    ReplyDelete
  4. Worked perfectly! Linux Mint is now running 100% perfectly in VirtualBox without that nag message. Thank you.

    ReplyDelete
  5. thanks for your timely help!!

    ReplyDelete
  6. Hi !
    Was facing the same problem. I'm a first time user of linux, was thinking of reinstalling ubuntu.

    But you saved the day !
    thanks!

    ReplyDelete
  7. Sounds 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 ...

    Anyone 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

    ReplyDelete
  8. Oh. Running Oracle VB 4.0.2 on a Samsung N220 netbook with 2Gb under Win 7 Starter.

    (My intention is to move to Meerkat entirely once I become familiar enough with it on the VB ...)

    flashfletch

    ReplyDelete
  9. [...] 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 [...]

    ReplyDelete
  10. Thanks for the solution :)
    Helped make my VM boot screen cleaner.

    ReplyDelete
  11. [...] 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 [...]

    ReplyDelete
  12. Works perfectly, thanks a bunch!

    That error message was extremely annoying.

    ReplyDelete
  13. 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.

    ReplyDelete
  14. blacklist: command not found

    Using Ubuntu 10.10

    ReplyDelete
  15. @apveening, read step #2 carefully.

    ReplyDelete
  16. Excellent work, my bootscreen is now pruned nicely.

    Thanks a lot for the post.

    Cheers

    ReplyDelete
  17. [...] @ Reply Hi there, Check out the following link: http://finster.co.uk/2010/11/16/virt...4_smbus-error/ [...]

    ReplyDelete
  18. Works perfectly, thanks a lot!

    ReplyDelete
  19. [...] Credits: http://finster.co.uk/2010/11/16/virtualbox-piix4_smbus-error/ This entry was posted in Uncategorized. Bookmark the permalink. [...]

    ReplyDelete
  20. In Arch Linux, replace step 3 with:

    # mkinitcpio -p linux

    Check https://wiki.archlinux.org/index.php/Mkinitcpio for more information.

    ReplyDelete
    Replies
    1. Thanks. For me however worked these steps:

      1. # vim /etc/modprobe.d/modprobe.conf
      2. Add this line to this file:
      blacklist i2c_piix4
      2. # mkinitcpio -p linux

      Delete
  21. Thanks Pedro just as you say I changed the step3 with your command and it worked for Arch Linux.

    ReplyDelete
  22. where 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

    ReplyDelete
  23. I 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

    ReplyDelete
  24. Thanks a lot. Worked perfectly (Ubuntu running on VM Virtual Box). Boot now is OK.

    ReplyDelete
  25. Under 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
  26. *** just perfect *** thx! ***

    ReplyDelete
  27. how to check module and intrafms? NO idea

    ReplyDelete
  28. ...worked perfectly for me, too.
    Thank you very much!

    ReplyDelete
    Replies
    1. Sorry can u teach me how to type all the things step by step?

      Delete
    2. Press 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.

      Delete
  29. pLs help how to what should i do... where can i type the codes?

    ReplyDelete
  30. Shawn hie, did you get the instructions, if you did , kindly share them
    thanks

    ReplyDelete
    Replies
    1. 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.
      Please Help !

      Delete
  31. Hi,

    I 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?

    ReplyDelete
  32. 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. !!!

    ReplyDelete
  33. These 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.

    ReplyDelete
  34. Thank you very much, it worked perfectly !!!

    ReplyDelete
  35. for centOS replace step 3 with dracut --force

    ReplyDelete