Yes, thanks. The modules are in the order specified. Sounds like we both solved separate halves of the problem. At this point, I cannot do the boot from DOC. I'm sure I can take care of that (from previous Dachstein experience), just so long as I can get the mounting of the DOC working.
I'm kinda stuck on the meaning of "device not configured". -----Original Message----- From: S Mohan [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 01, 2002 8:45 PM To: 'John Mullan'; [EMAIL PROTECTED] Subject: RE: [leaf-user] Problem: Bering DOC in latest "stable" version Nftla is the raw device of the chip just like had for ide1 primary hard disk. Have you loaded all the modules in the sequence as listed by Brad? It worked for me. I had problems getting DoC to work after this. I was able to mount, fdisk, syslinux etc. Post that, the system hung while booting. Remove the pkgpath declaration in syslinux.cfg on DoC and making sure nftla and nftla1 are listed in /car/lib/lrpkg/root.mount. I got to know this by reading linuxrc. HTH Mohan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John Mullan Sent: Monday, December 02, 2002 5:49 AM To: [EMAIL PROTECTED] Subject: [leaf-user] Problem: Bering DOC in latest "stable" version Well, I've spent the weekend changing from my Dachstein DHCP system on DoC to Bering PPPoe (changed ISPs) latest "stable" version I believe based on 2.4.18 kernal. It didn't take too long to implement the PPPoE feature using the Install/User guides. But the DoC part has me baffled. Currently, my Bering implementation works fine but still on floppy. After searching archives and re-reading the guides many times, my results follow: - I get the expected messages from "insmod docprobe.o" Possible DiskOnChip with unknown ChipID FF found at 0xc8000 Possible DiskOnChip with unknown ChipID FF found at 0xca000 Possible DiskOnChip with unknown ChipID FF found at 0xcc000 [..] DiskOnChip 2000 found at address 0xD8000 Ignoring DiskOnChip 2000 at 0xDA000 − already configured Ignoring DiskOnChip 2000 at 0xDC000 − already configured Ignoring DiskOnChip 2000 at 0xDE000 − already configured Possible DiskOnChip with unknown ChipID FF found at 0xe0000 Possible DiskOnChip with unknown ChipID FF found at 0xe2000 (numbers differ as I couldn't directly copy the screen results) - nftl.o module seems fine (don't get the "size != 1" error) and returns with partition check: nftla: nftla1 - DOC is recognized "cat /proc/mtd" dev: size erasesize name mtd0: 05000000 00004000 "DiskOnChip 2000" - I cannot: mount, fdisk, mkfs mkdir /flash mount -t msdos /dev/nftla1 /flash Device not configured The DOC has been "reformatted" with M-Sys version 4.2 because 5.x was not compatible. I also put an MSDOS FAT-16 on it prior to this venture but tried fdisk anyway. PROBLEM: Why is nftla, nftla1 not "configured". What am I missing and/or where should I look. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* John Mullan http://www.mullan.ca/ Personal: mailto:[EMAIL PROTECTED] Business: mailto:[EMAIL PROTECTED] ------------------------------------------------------- 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