[gobolinux-users] Cannot boot 013 because of squashfs problems.

[Joey Korkames]

I've never tried "bumping" a mail-list thread before....apologies if
this is out of line. The last two users troubled by this glitch failed to document
their respective success/failure on this matter and I aim to see it fixed for good.

Original problem:
http://lists.gobolinux.org/pipermail/gobolinux-users/2006-November/thread.html#3833

Purported solution:
http://gobolinux.org/index.php?page=known_issues_013

>
>       SMP problems with SquashFS
>
> /isolinux/kernel initrd init=/linuxrc ramdisk_size=4096 root=/dev/ram0 
> video=vesafb:off Boot=LiveCD ide=nodma

1. the initd syntax is wrong

/isolinux/kernel initrd=initrd init=/linuxrc ramdisk_size=4096
root=/dev/ram0 video=vesafb:off  Boot=LiveCD

On testing with my dual-core AM2 AMD64 rig....

Kernel Oops errors on things from udev, to modprobe, etc...always after
booting the initrd

then I tried:

/isolinux/kernel initrd=initrd init=/linuxrc ramdisk_size=4096
root=/dev/ram0 video=vesafb:off noapic nosmp Boot=LiveCD

A little better, but not enough - still oops'ing.

Then I tried:

/isolinux/kernel initrd=initrd init=/linuxrc ramdisk_size=4096
root=/dev/ram0 video=vesafb:off noapic nolapic nosmp apic=off Boot=LiveCD

Huzzah. i got a good zsh prompt.

I have two more AM2's back at the office (all 3 mobos are ASUS, but
these two have NForce chipsets) that I'll test the 013 LiveCD with as well.

This whole thing was chalked up to a SquashFS bug - is there a proper
reference to this bug as reported on their end so they can get it fixed (or so Gobo can
at least upgrade out of/around it on its next release...)?


Thanks
joey