OK, so do I feel stupid. I guess that in all of the re-attempts, I got my syslinux.cfg files mixed up and was booting from CF, but immediately pointing to /dev/fd0u1680 for everything. So, now I have the following excerpt from my bootup:
... 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=xx 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... hda: 250368 sectors (128 MB) w/1KiB Cache, CHS=978/8/32 Partition check: hda: hda1 hda: hda1 hda: hda1 VFS: busy inodes on changed media. LINUXRC: Installing - root: /dev/hda1 etc: /dev/hda1 local: /dev/hda1 modules: /dev/hda1 shorwall: /dev/hda1 weblet: /dev/hda1 - Finished. ... Does the "Partition check:" look right? Should it have "hda: hda1" three times in succession? Should VFS report that there were "busy inodes on changed media"? Thanks for all of the support to date!!! Rob -----Original Message----- From: Rob Fegley Sent: Tuesday, July 02, 2002 9:54 PM To: [EMAIL PROTECTED] Cc: Darren Hammond Subject: RE: [leaf-user] Futile attempts to boot from CF-IDE I've noticed that the suggestion is always to format with a DOS boot disk, or alternately to use a Linux boot disk and format with "-t msdos" operative. I think that I noticed that this format, even once booted and mounted, only observes the legacy DOS 8.3 filename construct. Can anyone validate this belief? If so, that sucks! And, why would it not be desirable to format and, subsequently, mount this CF partition(s) as "ext2" or "ext3" to see all of the benefits of those format types? I realize that by using a 128MB CF, I've somewhat strayed from the "spirit" of LEAF and LRP, but I'm hoping to achieve an almost completely solid-state (no moving parts, except PS and CPU fans; without HDs and other heat generators, will case fans really be necessary?) gateway "appliance". To do that, I need more .lrp packages to be available than will fit on any floppy. However, I don't need all of the bloat that comes with the more mainstream distros of Linux/BSD/Sun. I really like what LEAF has allowed me to do thus far, having used both the Eigerstein and Bering variants, but my needs would put me at about 3 floppies worth of .lrp packages, which will cause me to need to be available any time the box re-boots, to have 3 floppy drives, or to go to CD, ZIP, or JAZ. At the point that I crossed over 2 floppies worth of packages is when I wanted to go CF, never mind it's performance smokes any physical medium. I'm more looking for comments at this point than for answers to any specific questions! Any contribution is appreciated! Rob Fegley -----Original Message----- From: Darren Hammond [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 12:25 PM To: [EMAIL PROTECTED] Subject: Re: [leaf-user] Futile attempts to boot from CF-IDE Rob I think someone else already mentioned it, but the latest version of syslinux I can get to work on my system (64MB compactflash on a 33MHz 486 / 16MB RAM) is 1.48. If I use anything after then, I get the "Unable to lock drive for exclusive access" message as well. I always assumed that it was to do with the age of my BIOS. The other thing that happened to me was I used linux fdisk to create two partitions and forgot to make one active. I also used fdisk /mbr from a dos boot disk to clear the master boot record before using lock c: syslinux -s c: The box I was using had been running smoothwall prior to this. Also, there's two references to hda1 in syslinux.cfg on the same line, right? boot=/dev/hda1:msdos PKGPATH=/dev/hda1. Just checking - I suspect you've done both. Darren On Tuesday 02 Jul 2002 3:37 pm, Rob Fegley wrote: > Yes, I forgot to mention that I did this. > > -----Original Message----- > From: Manfred Schuler [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 01, 2002 11:39 PM > To: Rob Fegley > Cc: [EMAIL PROTECTED] > Subject: Re: [leaf-user] Futile attempts to boot from CF-IDE > > > Did you change the boot=/dev/fd0u1680:msdos in syslinux.cfg > to boot=/dev/hda1:msdos ? > > Manfred > > Rob Fegley schrieb: > > 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=xx 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=978/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 ------------------------------------------------------- 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek No, I will not fix your computer. 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek No, I will not fix your computer. 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
