Am 24.04.2013 20:57, schrieb Victor McAllister: > On 4/22/2013 9:53 AM, KP Kirchdoerfer wrote: >> Hi all; >> >> while I'm pretty satisfied with the current state of 5.0, I'm puzzled by >> boot pb's reported by users >> >> Victor on leaf-user and pojibing in TRAC ticket #83. >> >> Both reported that either 3.x or 4.2 worked for them. And for both there >> is no solution yet. This is unsatisfying, and as long as we don't have a >> solution, it may be a sign of a more genral problem - either in the code >> or in our docs. > > I still haven't gotten Bering 5 to boot on an ALIX13 > > This is my syslinux.cfg: > > SERIAL 0 19200 > DISPLAY syslinux.dpy > TIMEOUT 0 > APPEND reboot=bios console=ttyS0,19200n8 VERBOSE=1 > DEFAULT /syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw > root=/dev/ram0 LEAFCFG=/dev/sda1:vfat > > It will boot until it tries to find leaf.cfg and then fails. > > ***** > If I remove the leading slashes initrd=initrd.lpr,initmod.lrp it says > cannot find ramdiskimage: initrd.lrp and sits there with the Bering logo. > **** > I syslinuxed the compact flash with a bering 5 cd, which I believe had > syslinux version 4 on it.
Victor; I just tried with the 5.x geode image (and not any ISO image), set up a pxe-boot environment with dnsmasq, tftpd-hpa and vsftpd and pxeinstall4.tgz (git clone git://git.code.sf.net/p/leaf/packages leaf-packages) I copied the files from the geode image to /srv/ftp (a vsftpd configuration parameter), the kernel and syslinux.* into /srv/ftp/syslinux. The syslinux.cfg looks like: SERIAL 0 38400 DISPLAY syslinux.dpy TIMEOUT 0 APPEND reboot=bios console=ttyS0,38400n8 VERBOSE=1 DEFAULT /syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda1:vfat You'll need the leading slashes, if the kernel end in the /syslinux directory, they should be removed if you put the kernel into /. So my previous advice was not correct, sorry. Try to keep your serial line speed in sync with your Alix bios etc.. I have had to change the minicom configuration during the process, but that's easily done, if needed. If you managed to install the packages above, reboot the alix board and configure it's bios to boot via pxe. pxeinstall will boot, login as root (pls note we do not provide an editor there, so if you want to change syslinux.cfg you'll have to do on your host). Partition your CF and make it bootable: fdisk /dev/sda d -> delete partition o - n - create new partition p - primary 1 ENTER - start at sector 1 +500M - create a partition with 500MB (AFAIK 1GB is the maximum, otherwise it fails to boot) a - make a partition bootable 1 - select first partition w - write changes to disc and sync mkfs.vfat /dev/sda1 syslinux /dev/sda1 dd if=/usr/bin/mbr.bin of=/dev/sda bs=512 count=1 Get the files from the host and move it to CF: cd /tmp wget ftp://192.168.1.10/* (-> replace with the IP of your host) mount /dev/sda1 /mnt cp * /mnt rm * wget ftp://192.168.1.10/syslinux/* (-> same as above) mkdir /mnt/syslinux cp * /mnt/syslinux umount /mnt reboot Don't forget to stop dnsmasq on your host. After reboot it boots the 5.x version. I've tested with a given pxe-installation setup in less then ten minutes. I do believe you can reuse most of your old configuration, which is saved in configdb.lrp; but you may let other readers know, if and where it failed if you test this. kp ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
