[SOLVED] problem booting slackware 14.1 on virtualbox

tapa · 12-10-2015, 08:31 AM

so i'm trying to get slackware 14.1 running on virtualbox. installation process finishes without any problems, but when i try to boot it up, it stops with "? rest_init+0x70/0x70" (that's the first problem...). there's a lot of threads with the same problem and each concludes away with a statement that there's something wrong with lilo. so, i go for lilo. reinstallation from slack live cd setup goes ok but gives no result. so, i went for manual reconfiguration via chrooting from live cd and got stuck with something like "cannot chroot, cannot execute /bin/bash: no such file..." (...and that's the second one). google says that happens when one tries to chroot from a live cd with different architecture, but i'm using the same cd that i installed the system from. would be grateful for solutions and explanations (or at least a couple links with ones) on those two issues.

Drakeo · 12-11-2015, 04:25 AM

start Vbox then choose your slackware. Then click settings. click storage. now select you cdrom and choose your slackware install disk click ok. now start it the install disk will start. now read how to boot your hard drive boot huge.s or huge-smp what ever your using. read how to boot the system in a pinch. type it in. now press enter. you are now actually booting into the system. fix what ever is broken with lilo or install grub.

Code:

If you need to pass extra parameters to the kernel, enter them at the prompt
below after the name of the kernel to boot (huge.s etc).

In a pinch, you can boot your system from here with a command like:

boot: huge.s root=/dev/sda1 rdinit= ro 

In the example above, /dev/sda1 is the / Linux partition.

To test your memory with memtest86+, enter memtest on the boot line below.

This prompt is just for entering extra parameters.  If you don't need to enter
any parameters, hit ENTER to boot the default kernel "huge.s" or press [F2] 
for a listing of more kernel choices.

tapa · 12-23-2015, 05:36 PM

i've tried that also, same error. the problem was eventually solved by reinstalling vbox v.5 (i've had 3.1.6 before and ubuntu 10 and it didn't want to upgrade to v.5 there, so i'd upgraded to ubuntu 14 and it ran instantly). thanks anyway.