← Back to team overview

kernel-packages team mailing list archive

[Bug 642801] Re: at boot get piix4_smbus error, Ubuntu installed in VirtualBox


** Tags removed: biot-stop-nagging
** Tags added: bot-stop-nagging

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  at boot get piix4_smbus error, Ubuntu installed in VirtualBox

Status in “linux” package in Ubuntu:

Bug description:
  Binary package hint: debian-installer

  at very first live CD boot I get a "piix4_smbus [...] smbus have address unintialized - upgrade BIOS or use force_addr=0xaddr" error.
  Then after the first reboot it disappears.

  Ubuntu 10.10 is the beta made available around August the 31st. It is
  installed in a VIrtual Box 3.2.6 OSE r63112 (latest from PPA at that

  Only non-conventional Guest installation I did was to disable the
  VT-x/AMD-V functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: debian-installer (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic
  Uname: Linux 2.6.35-19-generic i686
  Architecture: i386
  Date: Sun Sep 19 15:32:55 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
   Bus 001 Device 002: ID 80ee:0021  
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
   total       used       free     shared    buffers     cached
   Mem:       1025720     395568     630152          0      33580     196272
   -/+ buffers/cache:     165716     860004
   Swap:       305148          0     305148
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=7f35e3bf-3eae-4290-a029-0790ec7ef8bc ro quiet splash
  SourcePackage: debian-installer
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to: