Re: [yoper-dev] Current Blacksand installer
Hi Tobias, Some small progress. Please see the inline comments. Tobias Gerschner wrote: Hi Dion, When the installation cd does boot you should be able to use Yoper on your system. It is using exactly the same kernel. To build an initrd image via yaird from the live cd into an existing system you have to do the following : 1) mount your root partition : 'mount /dev/sda1 /media/sda1' (make sure the only mount option is rw) In my last post, I couldn't get yaird to produce an image. I failed to add a -rw to the above mount. Doing this enabled me to create an initrd image. 2) copy your device node files from the live cd into the new root file system 'cp -a /dev/hd* /dev/sd* /media/sda1/dev' 3) chroot into the new installation 'chroot /media/sda1' 4) mount the kernel file systems 'mount /proc' , 'mount /sys' 5) try to rebuild the image with yaird yaird -o /boot/initrd.whatever I created the new image with a -v switch and was able to see the symbios 53c875 module included in the image. I had to use the -f cpio option as the -f cramfs appears to be for older kernels and would not work. Make sure the installation of the bootloader does really work properly. I adjusted the lilo.conf and rerun lilo. I received some complaints. proc/partitions does not match /dev name change '/dev/loop0' - '/dev/loop0' They were spelled identically, so I'm guessing something within that location got a name chage. regards and good luck Thanks, I wasn't lucky enough. The system still boots and then complains as follows. kernel panic - not syncing: VFS: unable to mount root fs on unknown-lock(8,1) Okay, I am wondering if using XFS is somehow a problem. I can try ext3 and see if I get similar behaviour. The next option I was considering was mounting the blacksand install cd and copying the kernel source and the kernel config file to my 2.1.0_4 system and building a kernel with symbios 53c875 and relevant scsi disc support into the kernel. If that fixes the problem at least we would know the scope of the problem I am having. I wonder if other people with sata and or other scsic ontrollers and the like are likely to experience this problem? This may be something for the installer to handle, perhaps by offering the user the option of selecting kernel drivers to be included in the initrd image? I appreciate your help. Cheers. D. -- Never ascribe to malice that which may adequately be explained by incompetence. - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Re: [yoper-dev] Current Blacksand installer
In regard to XFS, I just tried a reinstall and selected the ext3 file system. This yielded no change in the error. The system still boots and then complains as follows. kernel panic - not syncing: VFS: unable to mount root fs on unknown-lock(8,1) Okay, I am wondering if using XFS is somehow a problem. I can try ext3 and see if I get similar behaviour. If no one has any good ideas, I will try mounting the install cd and building a custom kernel with built in scsi support. Cheers. Dion. -- Never ascribe to malice that which may adequately be explained by incompetence. - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Re: [yoper-dev] Current Blacksand installer
Hi Tobias, Thanks for the valuable feedback. If this discussion should be moved out of the dev list, just let me know. I attempted as per your advice below. I had no problem with the tasks up to the yaird -o /boot/init-2 However yaird produces the following error. yaird error: could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.15_yos_3 evdev (fatal) manually typing /sbin/modprobe -v -n --show-depends --set-version 2.6.15_yos_3 evdev gives the following output: insmod /lib/modules/2.6.15_yos_3/kernel/drivers/input/evdev.ko Looking inside the /etc/yaird/Default/cfg file, shows that evdev is a keyboard driver and is quoted as not essential and that the system will boot without it. So I tried commenting out the evdev line. re-running yaird -o.. to make my initrd image still produces almost the same error. yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.15_yos_3 sym53c8xx (fatal) This is important, because that is the driver module for my scsi card. So, given the error is very similar, I'm wondering if this might be permissions or paths problems or a problem with yaird. I appreciate your assistance. Cheers. D. Tobias Gerschner wrote: Hi Dion, When the installation cd does boot you should be able to use Yoper on your system. It is using exactly the same kernel. To build an initrd image via yaird from the live cd into an existing system you have to do the following : 1) mount your root partition : 'mount /dev/sda1 /media/sda1' (make sure the only mount option is rw) 2) copy your device node files from the live cd into the new root file system 'cp -a /dev/hd* /dev/sd* /media/sda1/dev' 3) chroot into the new installation 'chroot /media/sda1' 4) mount the kernel file systems 'mount /proc' , 'mount /sys' 5) try to rebuild the image with yaird yaird -o /boot/initrd.whatever Make sure the installation of the bootloader does really work properly. regards and good luck -- Never ascribe to malice that which may adequately be explained by incompetence. - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Re: [yoper-dev] Current Blacksand installer
Hi Tobias, The install did move very smoothly, however I cannot boot the machine. A kernel panic occurs like this: kernel panic - not syncing: VFS: unable to mount root fs on unknown-lock(8,1) From other posts in the forums this seems to mean that the system does not have the kernel modules to support my scsi card and boot from the scsi disc. I attempted to follow some advice you gave in the forum to build an initrd image for my system after using the 2.91 disc as a rescue disc, without much success. Initially I could mount and then chroot into my scsi disc root partition, however I could not produce an initrd disc image. mkinitrd does not seem to be available. It seems we use yaird for this now, however if I chroot into my root partition and try to make the initrd image, yaird complains that it can't open files in the proc directory. yaird error: cant open /proc/bus/input/devices (fatal) If I just mount the scsi disc partition and try to build the initrd from the 2.91 cd's file system it complains that the mount point for my scsi disc is not in the fstab. yaird error: mount point not in fstab: . (fatal) Any thoughts?? Cheers. D. -- Never ascribe to malice that which may adequately be explained by incompetence. - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
[yoper-dev] Current Blacksand installer
Hi everyone, I apologise now if this is the incorrect list for this email. If it is, simply point me to the right place. I attempted to install blacksand on my backup box and couldn't make it work. My backup box is quit old, its a dual cpu mendocino celeron machine with only 256 meg of ram. The system fails to install on any of the three boot options from the opening grub? menu. The actual error -- can't take a screen shot -- is just after the kernel turns off dma on the cdrom and then declares that it cannot find the file system and drops to a very limited shell. Interestingly, when I tested this same machine in november last year with the test iso it all worked. However I do understand that blacksand is almost a completely different beast to that installer. I hope this is useful to anyone working with the installer. I am happy to try other tests and iso's if it will assist the installer team. Cheers. Dion. -- Never ascribe to malice that which may adequately be explained by incompetence. - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
