@markds
I've been trying out bootsplash with nomodeset on Porteus
this is a dead end.
intel, nouveau (and soon radeon) DDX drivers requires kernel modesetting to work in GUI.
i would give up with bootsplash unless your distro is intended to work in text mode only.
The sgn file in the 64 bit is porteus-v2.0-x86_64.sgn, but linuxrc in the initrd.xz is looking for porteus-v2.0-i486.sgn.
our initrd is slightly different between 32/64 bit archs so you can't mix them
I built kernel 3.7.3 for Porteus as well using the same patches, and included the lib/modules/3.7.3 into 000-kernel.xzm, then added a new syslinux menu item to boot my 3.7.3 vmlinuz and I keep getting "Cannot read <module>.xzm - corrupted module?" for all the base modules and all the other modules.
i have just pushed 3.7.4 kernel update and all is fine so my guess is that your kernel was compiled incorrectly.
there was a change in kernel 3.7.x line which introduced 'uapi' directory and probably this is the reason.
here is updated script for getting aufs patch:
Code: Select all
#!/bin/sh
dest=/home/ftp/storage/kernel/aufs3.patch
mkdir /tmp/aufs$$
cd /tmp/aufs$$
git clone git://aufs.git.sourceforge.net/gitroot/aufs/aufs3-standalone.git aufs3-standalone.git
cd aufs3-standalone.git
# uncomment line below to get aufs for stable kernel
git checkout origin/aufs3.7
# uncomment line below to get aufs for latest -rc kernel
#git checkout origin/aufs3.x-rcN
mkdir ../a ../b
cp -r {Documentation,fs,include} ../b
rm ../b/include/uapi/linux/Kbuild 2>/dev/null || rm ../b/include/linux/Kbuild
cd ..
diff -rupN a/ b/ > $dest
# extra patches:
cat aufs3-standalone.git/*.patch >> $dest
# fix broken Kbuild:
cat >> $dest << EOF
--- a/include/uapi/linux/Kbuild
+++ b/include/uapi/linux/Kbuild
@@ -66,6 +66,7 @@ header-y += atmppp.h
header-y += atmsap.h
header-y += atmsvc.h
header-y += audit.h
+header-y += aufs_type.h
header-y += auto_fs.h
header-y += auto_fs4.h
header-y += auxvec.h
EOF
# cleanup:
rm -r /tmp/aufs$$
echo && echo "latest patch created as $dest"
please tweak 'dest=' variable.
I did note that the lib/modules in the initrd.xz was empty, is this supposed to be right?
yes. everything we need is compiled directly into porteus kernel: aufs, squashfs, fuse, filesystems, usb drivers, etc (i see no point loading them at every boot while i know i will need them)
this dir is filled in with modules only when doing PXE boot as compiling all ethernet drivers into kernel would make it too much bloated.
When I boot up with the USB stick, the system says its reading the porteus data from /mnt/sda1/porteus - so the usb stick is being set as sda
When the system is booted up into porteus, this is no longer the case. The usb stick becomes /dev/sdb and the hard drive of the PC is now sda.
afaik this is not possible as devices never gets renamed no matter what you do.
vmlinuz and initrd could be loaded from usb stick but your system booted from hard drive (first matching *.sgn file is ok for linuxrc)
to confirm please view /var/log/porteus-livedbg and check 'Booting device:'
to make sure you are booting from usb please use 'from=/dev/sdb1' cheatcode.
Please add [Solved] to your thread title if the solution was found.
