Talk:MeeGo 1.0 Netbook VirtualBox

Which version of VirtualBox are you using? I'm running the latest (3.2.2) and getting a segfault for VBoxClient. Anything that I can check? Thanks

--DavidE 12:02 pm, 7 June 2010 (UTC)DavidE

Thank you for instructions.

I did whatever is written, but now have a problem during reboot:

/etc/rc3.d/S04dkms_autoinstaller: line 62: log_daemon_msg command not found.

Similar stuff with log_action_begin_msg command not found & log_action_end_msg command not found.

Any hint how to resolve it?

--Gour 09:33, 2 June 2010 (UTC)Gour

I guess DKMS tried to guess distribution. Since MeeGo uses /etc/meego-release to show itself, every init script relying on thos files will fail. I know that VMAdditions startup scripts fail at least. My guess would be to add a symlink /etc/redhat-release => /etc/meego-release

--Marcin Sołtysiak 10:00, 2 June 2010 (UTC)

I've created /etc/redhat-release symlink, but still no luck. :-(

--Gour 13:46, 2 June 2010 (UTC)

yum install meego-lsb helps (adding that to the wiki page). log_daemon_msg etc. are functions that are defined in /lib/lsb/init-functions.

--Jarkko Sakkinen

Thank you. It helped...Now VMAdditions starts seemingly OK, but attempt to do init 5 gives me the (old) respawning too fast error. Any clue?

--Gour 06:55, 3 June 2010 (UTC)

Looks like its missing a frame buffer. The kernel has intel 810 chipset, but not vesa. Would having a vesa fb show the UX? I tried to reconfigure the kernel, but failed miserably.

--

There is /etc/inittab which do actions for different runlevels. Level 5 tries to start moblin-dm, it also automatically respawns it if program is terminated.

System can be started on runlevel 3 more convenient manner by adding init kernel option in /boot/extlinux/extlinux.conf: init=/sbin/init 3

</--Aetelani 20:46, 3 June 2010 (UTC)>

I get respawning error when I try init 5 after booting into console.

--Gour 05:55, 4 June 2010 (UTC)

hangs on installing bootloader

I've tried this a couple of times using slightly different variations on the couple of available options and with both available versions (Chrome & no Chrome). It always hangs at "Installing bootloader ...".

Any suggestions?

Running F12 and the version of VirtualBox available from Oracle/Sun as opposed to the version available from Fedora.

cold it be that the virtualBox does not expose framebuffer device ?

so the driver fails to load and the device is then missing ?