Rob Hopefully someone will answer with a definitive answer, but I can relate my experiences...
I found that syslinux from DOS was unreliable. I have successfully used Tom's Root-Boot disk with a few versions of syslinux. I've had better luck with the old ones for some reason (1.48 for example). I stumbled across http://www.dublerfamily.com/leaf/ which gives a good outline of how to get Dachstein going with wireless on a hard drive or CF. The 'Dachstein Utilities' disk was very useful, includes syslinux and worked just fine with Bering RC2 (wireless or otherwise). Did you change syslinux.cfg to reference hda1 for both the boot and package paths? How are you formatting the CF? Is '98 doing a FAT32 format by any chance? Since mucking about the first time to find a way of making this work, I've since acquired a CF-PCMCIA adapter card that I put in my Linux laptop. Now I can do everything from it and get a CF card loaded in a matter of a minute or two. Using mkdosfs, syslinux -s etc with Linux just seems to cause me less trouble. I also seem to recall hearing bad stories about fdisk and CF. Why not just leave it as it came from the factory? Sorry, can't give you an exact answer, hopefully something here will trigger a solution. Brock | Date: Mon, 1 Jul 2002 19:29:53 -0500 | From: "Rob Fegley" <[EMAIL PROTECTED]> | To: <[EMAIL PROTECTED]> | Subject: [leaf-user] Futile attempts to boot from CF-IDE | | Due to a link I saw on the LEAF site at SF to PC Engines, I am using one = | of the CF-IDE adapters with a 128 MB CF. I have verified that I can = | FDISK, FORMAT, and boot from it under WIN 98 (DOS). | | However, now that I want to use it as the boot medium for my LEAF = | router, it seems to be determined to keep me from doing so. | | I am running the Bering-1.0-RC3-1680 image. I have the box running = | successfully off of only a floppy. | | I have tried to do the whole trick under WIN 98 command-line to do a = | FDISK /MBR, FDISK, FORMAT C:, LOCK C:, SYSLINUX -S C:. Additionally, I = | am trying to use the newest Syslinux, ver 1.75. I have tried using and = | not using LOCK, changing the order of most of the preceding 5 tasks, and = | running Syslinux with and without the "-s" directive. | | However, in every iteration, I kept getting the message "ERROR 440D: = | Unable to lock drive for exclusive access" when trying to apply Syslinux = | (1.75). | | So, I tried going to www.bootdisk.com and downloading a DOS 6.22 image, = | along with Syslinux v1.67, to some better degree of success. | | I am able to do a "mount -t msdos /dev/hda1 /mnt" and read/write/execute = | any files on the CF, but just not able to boot from it. Now, that I've = | used MSDOS 6.22 and Syslinux v1.67, I receive the following messages = | during boot: | | /* Begin Boot Message | LINUXRC: Bering - Initrd - V1.0-rc3 | Using /boot/lib/modules/ide-mod.o | Uniform Multi-Platform E-IDE driver Revision: 6.31 | ide: Assuming 33MHz system bus speed for PIO modes; override with = | idebus=3Dxx | PIIX4: IDE controller on PCI bus 00 dev 39 | PIIX4: chipset revision 1 | PIIX4: not 100% native mode: will probe irqs later | Using /boot/lib/modules/ide-disk.o | Using /boot/lib/modules/ide-probe-mod.o | hda: Hitachi CVM2.1.0, ATA DISK drive | ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 | Mounting a 16M TMPFS filesystem... | end_request: I/O error, dev 02:2c (floppy), sector 2 | MINIX-fs: unable to read superblock | end_request: I/O error, dev 02:00 (floppy), sector 0 | end_request: I/O error, dev 02:00 (floppy), sector 0 | end_request: I/O error, dev 02:00 (floppy), sector 0 | hda: 250368 sectors (128 MB) w/1KiB Cache, CHS=3D978/8/32 | Partition check: | hda: hda1 | hda: hda1 | hda: hda1 | FAT: bogus logical sector size 20487 | VFS: Can't find a valid FAT filesystem on dev 03:00. | hda: hda1 | hda: hda1 | VFS: Can't find a Minix or Minix V2 filesystem on device 03:00. | hda: hda1 | hda: hda1 | FAT: bogus logical sector size 20487 | VFS: Can't find a valid FAT filesystem on dev 03:00. | hda: hda1 | hda: hda1 | | end_request: I/O error, dev 02:2c (floppy), sector 2 | MINIX-fs: unable to read superblock | LINUXRC: Installing - root: root(nf!) etc: etc(nf!) local: = | local(nf!) modules: modules(nf!) | shorwall: shorwall(nf!) weblet: weblet(nf!) - Finished. | cat: /var/lib/lrpkg/root.pn.links: No such file or directory | cat: /var/lib/lrpkg/rKernel panic: Attempted to kill init! | oot.log.links: No such file or d irectory | .: Can't open /var/lib/lrpkg/root.dev.own | End Boot Message */ | | Basically, what I get is that it loads the three IDE-*.O modules from = | the initrd.lrp under /boot/lib/modules, that I put there. It recognizes = | the CF as an IDE device, then everything goes to pot from there. = | However, having modified my boot floppy to see it's LRP path as = | /dev/hda1, I am able to successfully boot from floppy into INITRD, then = | load all LRPs from CF into a 16 MB Ram disk, but this is not complete in = | my mind. | | I'm at a total loss except I've thought of re-running Syslinux but with = | v1.75 on my DOS 6.22 boot disk. I've also thought that the Bering = | 1.0RC3 kernel may not have IDE enabled, but I would think that by = | loading those modules at runtime, I've taken care of that. | | Any thoughts or assistance will be greatly appreciated! | | Take Care! | | Rob Fegley | TGI Micro | http://www.tgimicro.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
