Yes, this should be fixed now, in the new image I'll be uploading tonight.
Ok, thanks a thousand times already.
Don 't forget to populate /dev with the necessary device files (at least sda, urandom and random).
I'm a bit puzzled by this, as udev should have created them, and according to the Geentoo udev guide
should be needed, but nevertheless, I have included the following in the Genlink image:
GenLSPro / # ls -al /mnt/share/Genlink/ROOTFS_mods/OVERWRITE_ROOT/dev
drwxr-xr-x 4 root root 56 Feb 20 2007 .
drwxr-xr-x 16 root root 4096 Sep 9 21:33 ..
lrwxrwxrwx 1 root root 15 Dec 28 2007 MAKEDEV -> ../sbin/MAKEDEV
crw-rw---- 1 root tty 5, 1 Dec 28 2007 console
prw------- 1 root root 0 Dec 28 2007 initctl
crw-rw---- 1 root root 1, 3 Dec 28 2007 null
drwxr-xr-x 2 root root 8 Dec 6 2006 pts
drwxr-xr-x 2 root root 8 Dec 6 2006 shm
crw------- 1 root root 4, 1 Dec 28 2007 tty1
Could it be that those missing devices are due to the kernel configuration of the kernel you booted?
Also make sure you pull in a subversion OTHER than 1.5.0. It doesn 't like the installed Neon version (although it 's higher than the required one). I recommend subversion 1.5.1, that worked for me.
Ok, I will take care of this.
I 'm also still puzzled why your default kernel (2.6.22) + the 2.6.26 wouldn 't boot in EM mode. They completely ignored either rootfs_booting/rootfs_ok files and the 3x poweroff procedure.
Actually, I think it's the stuff in the initrd which handles all this, and I can confirm that I had my LSPro in EM mode several times before I re-added the code to reset this counter, in /etc/conf.d/local. So I'm puzzled, too...
Speaking of kernels: now that I 've finally successfully pulled in the orion5x overlay and emerged the orion5x sources, how do I go about with building the kernel? I mean, do you have a good working .config and an up-to-date procedure on how to create uImage.buffalo? Over here
is a procedure on how to do it on Debian, but I guess it must be possible on a Gentoo PC to do it with crossdev, yes?
Yes, I could provide some .config files, and yes, I followed that procedure on gentoo, too, and also integrated that patching stuff in the ebuilds (noticed the dependencies pulled in?), that way you only crosscompile your kernel and end up with the uImage by issuing something like
ARCH=arm CROSS_COMPILE=armv5tejl-softfloat-linux-gnueabi- INSTALL_MOD_PATH="$ROOT" make uImage modules
Last thing: I 'm always getting this warning when emerging
WARNING: repository at /mnt/xtra/gentoo/portage_overlays/local/my_overlay+patches is missing a repo_name entry
Yes, that's a left-over of my own local overlay, I will fix this by providing either the necessary repo_name file, or commenting the overlay out.
Once again, thanks a lot for the feedback!