Re: [leaf-user] Problem: Bering DOC in latest stable version
OK. I quickly made the change in number (from 100 to 93) before I left for work. I now get reasonable output from 'fdisk -l /dev/nftla'. Didn't right it down but it gave size/cyl/etc. I will have to wait until I get home now to see if I can mount it. The network here won't let me SSH and I haven't added that module (won't fit on floppy, hence using DOC). Stay tuned for further results :) John Brad Fritz [EMAIL PROTECTED] To: John Mullan [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED] [EMAIL PROTECTED]Subject: Re: [leaf-user] Problem: Bering DOC in latest stable version ceforge.net 12/02/2002 09:51 PM On Mon, 02 Dec 2002 21:34:37 EST you wrote: OK. Now we are getting somewhere. First, my major is 100, not 93. That is left over from when I used Dachstein. I didn't think it would make a big difference, but then I don't know a lot about the inner workings of things. Yep, that will definitely cause problems. The lsmod output is exactly in the order you mention below (of course with a lot of other stuff preceeding it). I suspect changing the major number will fix the current problems. Your modules are probably setup correctly. I'll try changing the major number ( in /var/lib/lrpkg/root.dev.mk right?) first. Yes, /var/lib/lrpkg/root.dev.mk . There should be a pair of lines like: #Disk-On-Chip makedevs nftla b 93 0 0 4 s null 21 in it. As of Bering 1.0-stable (and probably 1.0-rc4), everything in initrd.lrp, including root.dev.mk should work out-of-the-box with DiskOnChip 2000 modules. Sounds like you're getting close. Good luck. --Brad --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en 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: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en 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
Re: [leaf-user] Problem: Bering DOC in latest stable version
I'll have to setup everything to try and do it again. Unfortunately, the system I have doesn't have a floppy so I have to do the Hard-Drive shuffle to get everything setup. I'm thinking this weekend I should have some time to plug away at this. --Pat On Tue, 3 Dec 2002, Brad Fritz wrote: Pat, On Tue, 03 Dec 2002 20:26:11 EST Pat wrote: John (and/or Brad), I've been teetering on getting this working myself. Can you suggest (or document) variances from the UserGuide? I recently updated the DoC UG chapter for Bering 1.0-stable. The HTML version is at http://leaf.sourceforge.net/devel/jnilo/budiskonchip.html When I made the updates, I tested the procedure. I am not aware of any variances. That said, I only have one 4MB DoC 2000 system so my ability to test is somewhat limited. I hope you don't run into any problems. If you do, please let me know so that I can make appropriate adjustments to the UG chapter. Also, you mentioned the size != 1 error? I've seen that recently, any suggestions on what that is and how to fix it? I've tried to use both a 16MB and 72MB Chip. Could you give me some context for this error? I am curious when it happens and would appreciate hearing anything you can tell me about the hardware and software configurations that cause it. --Brad --- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en 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
RE: [leaf-user] Problem: Bering DOC in latest stable version
I'm not all that big of an expert. Brad appears a bit more knowledgable than myself. I was running Dachstein in DoC and was configured for DHCP (Cable). When I switched to DSL I decided to go with Bering this time. The PPPoE parts was real easy. A no brainer. Just followed guide. However, I can say that, since using the guide, there is some differences but all good. The guide I used was for version prior to the 'stable' version, and most of the file changes have already been done for you. The key seems to be that you either find a newer version of the module(s) or use an older version of the M-Sys format utility/image. Since the module is likely specific to the kernal (I can't compile here) you will have to monkey with it or, like me, reformat the flash with an older verison. Aside from that, I did not follow all of the guides directions. I booted with an msdos floppy and did the higher level FAT format that way. Then I booted the LEAF/Bering floppy and did everything up until the part where you have to fdisk. I used fdisk to check for availability/validity of the DoC. This is where I got hung up. Since I previously had Dachstein on DoC, the flash driver (I think) expected a major device number of 100. I assumed that it was still valid with the drivers for Bering. WRONG. So when I changed it to 93, it worked. After mounting the Doc, I copied everything over. Edited the 'syslinux.cfg' on the DoC (not the floppy one) as suggested. This is where I again strayed from the guide. I rebooted into DOS, ran the SYSLINUX to update the boot record and ran RDEV to update the kernal. I rebooted (without floppy) and oila' instant Bering router/firewall. That was my experience. Hope this helps a little. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 8:26 PM To: John Mullan Cc: 'Brad Fritz'; [EMAIL PROTECTED] Subject: RE: [leaf-user] Problem: Bering DOC in latest stable version John (and/or Brad), I've been teetering on getting this working myself. Can you suggest (or document) variances from the UserGuide? Also, you mentioned the size != 1 error? I've seen that recently, any suggestions on what that is and how to fix it? I've tried to use both a 16MB and 72MB Chip. Thanks, Pat On Tue, 3 Dec 2002, John Mullan wrote: OK Brad, some fantastic success. I now get the expected fdisk results. However, previously I also got the expected /proc/mtd results, but now I get 'permission denied'. However I CAN mount /dev/nftla1 without trouble. I copied everything, redid SYSLINUX and RDEV and I am booting from the DoC with Bering instead of Dachstien! My next question is: what is the problem with /proc/mtd if any? Should I care because I'm not sure at this point I even know what the purpose is. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Brad Fritz Sent: Monday, December 02, 2002 8:15 PM To: John Mullan Cc: [EMAIL PROTECTED] Subject: Re: [leaf-user] Problem: Bering DOC in latest stable version On Mon, 02 Dec 2002 19:20:51 EST John Mullan wrote: Hi Brad. When I run 'fdisk /dev/nftla' it gives me 'unable to open /dev/nftla' The output of 'ls -l /dev/nftla*' should look like this: brw-rw 1 root root 93, 0 Dec 2 16:51 /dev/nftla brw-rw 1 root root 93, 1 Dec 2 16:51 /dev/nftla1 brw-rw 1 root root 93, 2 Dec 2 16:51 /dev/nftla2 brw-rw 1 root root 93, 3 Dec 2 16:51 /dev/nftla3 brw-rw 1 root root 93, 4 Dec 2 16:51 /dev/nftla4 Are your major and minor numbers (93 and 0-4) and permissions correct? If that checks out, what is the output of lsmod? Do nftl docprobe doc2000 docecc mtdcore appear in that order? As far as the existing file system on the DOC, it has always had MSDOS on it. The DOC boots fine (at least until I did syslinux. Now it starts booting into Linux but stops because it cannot find the packages and hangs. But then, it still technically has FAT on it. Any other hints? If the kernel and initrd are loading and then it hangs, that sounds a lot like a module or device config problem to me. If /proc/mtd is still: dev: size erasesize name mtd0: 0500 4000 DiskOnChip 2000 the mtdcore.o and doc*.o modules are probably fine. I would double check that nftl is properly insmoded. If you're still having problems after checking all of the above, feel free to send me the output of dmesg after booting with the DoC-enabled floppy offline. I'd be happy to compare it to mine and let you know if anything jumps out at me. --Brad --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
RE: [leaf-user] Problem: Bering DOC in latest stable version
I've used a 8MB Doc2000 on a thin client Bering rc-3, rc-4 and stable. All went thro' perfectly. I did not face/see any problem in the procedure given in the Users Guide. In fact, I had missed out Brad's instruction on removing pkgpath=/dev/xxx in syslinux.cfg and discovered it while reading linuxrc thanks to Brad's inline documentation in the hack. Mohan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Brad Fritz Sent: Wednesday, December 04, 2002 7:10 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [leaf-user] Problem: Bering DOC in latest stable version Pat, On Tue, 03 Dec 2002 20:26:11 EST Pat wrote: John (and/or Brad), I've been teetering on getting this working myself. Can you suggest (or document) variances from the UserGuide? I recently updated the DoC UG chapter for Bering 1.0-stable. The HTML version is at http://leaf.sourceforge.net/devel/jnilo/budiskonchip.html When I made the updates, I tested the procedure. I am not aware of any variances. That said, I only have one 4MB DoC 2000 system so my ability to test is somewhat limited. I hope you don't run into any problems. If you do, please let me know so that I can make appropriate adjustments to the UG chapter. Also, you mentioned the size != 1 error? I've seen that recently, any suggestions on what that is and how to fix it? I've tried to use both a 16MB and 72MB Chip. Could you give me some context for this error? I am curious when it happens and would appreciate hearing anything you can tell me about the hardware and software configurations that cause it. --Brad --- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en 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: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en 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
RE: [leaf-user] Problem: Bering DOC in latest stable version
Hi Brad. When I run 'fdisk /dev/nftla' it gives me 'unable to open /dev/nftla' As far as the existing file system on the DOC, it has always had MSDOS on it. The DOC boots fine (at least until I did syslinux. Now it starts booting into Linux but stops because it cannot find the packages and hangs. But then, it still technically has FAT on it. Any other hints? John -Original Message- From: Brad Fritz [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 12:46 AM To: John Mullan Cc: [EMAIL PROTECTED] Subject: Re: [leaf-user] Problem: Bering DOC in latest stable version John, On Sun, 01 Dec 2002 19:19:01 EST John Mullan wrote: 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 DiskOnChip 2000 found at address 0xD8000 Looks good so far. (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 Also good. I get: Using /boot/lib/modules/nftl.o NFTL driver: nftlcore.c $Revision: 1.82 $, nftlmount.c \ $Revision: 1.25 $ Partition check: nftla: nftla1 Mounting a 6M TMPFS filesystem... when I boot from the DoC. - DOC is recognized cat /proc/mtd dev: size erasesize name mtd0: 0500 4000 DiskOnChip 2000 Looks okay. - I cannot: mount, fdisk, mkfs mkdir /flash mount -t msdos /dev/nftla1 /flash Device not configured That might happen if /dev/nftla is not properly partitioned (fdisk) or /dev/nftla1 does not have an MS-DOS filesystem on it (mkfs.msdos). What happens if you try fdisk /dev/nftla instead? Can you see the MS-DOS partition from fdisk? Is it set to active? Assuming the answers are all yes, can you create an MS-DOS filesystem on the partition using: mkfs.msdos /dev/nftla1 ? If the mkfs goes well, you should definitely be able to mount /dev/nftla1 . The DOC has been reformatted with M-Sys version 4.2 because 5.x was not compatible. Unfortunately, I am not very familiar with the M-Sys utilities. I never found a need to use any of there software with my DoC. (I'm not even sure if mine was formatted with 4.2 or 5.x.) That said, if you can boot MS-DOS from the DoC the UG directions *should* work. I also put an MSDOS FAT-16 on it prior to this venture but tried fdisk anyway. Did you use Bill's fdisk or linux fdisk? What were the results? Better yet, what is the output of the linux fdisk -l /dev/nftla command? PROBLEM: Why is nftla, nftla1 not configured. What am I missing and/or where should I look. My guess is a partition or filesystem problem with the DoC. Let me know about the fdisk and mkfs.msdos results. If the problem seems to be elsewhere, I will lookup the error message you quoted in the source. --Brad --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en 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
Re: [leaf-user] Problem: Bering DOC in latest stable version
On Mon, 02 Dec 2002 19:20:51 EST John Mullan wrote: Hi Brad. When I run 'fdisk /dev/nftla' it gives me 'unable to open /dev/nftla' The output of 'ls -l /dev/nftla*' should look like this: brw-rw 1 root root 93, 0 Dec 2 16:51 /dev/nftla brw-rw 1 root root 93, 1 Dec 2 16:51 /dev/nftla1 brw-rw 1 root root 93, 2 Dec 2 16:51 /dev/nftla2 brw-rw 1 root root 93, 3 Dec 2 16:51 /dev/nftla3 brw-rw 1 root root 93, 4 Dec 2 16:51 /dev/nftla4 Are your major and minor numbers (93 and 0-4) and permissions correct? If that checks out, what is the output of lsmod? Do nftl docprobe doc2000 docecc mtdcore appear in that order? As far as the existing file system on the DOC, it has always had MSDOS on it. The DOC boots fine (at least until I did syslinux. Now it starts booting into Linux but stops because it cannot find the packages and hangs. But then, it still technically has FAT on it. Any other hints? If the kernel and initrd are loading and then it hangs, that sounds a lot like a module or device config problem to me. If /proc/mtd is still: dev: size erasesize name mtd0: 0500 4000 DiskOnChip 2000 the mtdcore.o and doc*.o modules are probably fine. I would double check that nftl is properly insmoded. If you're still having problems after checking all of the above, feel free to send me the output of dmesg after booting with the DoC-enabled floppy offline. I'd be happy to compare it to mine and let you know if anything jumps out at me. --Brad --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en 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
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 0xe 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: 0500 4000 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
RE: [leaf-user] Problem: Bering DOC in latest stable version
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 0xe 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: 0500 4000 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
Re: [leaf-user] Problem: Bering DOC in latest stable version
John, On Sun, 01 Dec 2002 19:19:01 EST John Mullan wrote: 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 DiskOnChip 2000 found at address 0xD8000 Looks good so far. (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 Also good. I get: Using /boot/lib/modules/nftl.o NFTL driver: nftlcore.c $Revision: 1.82 $, nftlmount.c \ $Revision: 1.25 $ Partition check: nftla: nftla1 Mounting a 6M TMPFS filesystem... when I boot from the DoC. - DOC is recognized cat /proc/mtd dev: size erasesize name mtd0: 0500 4000 DiskOnChip 2000 Looks okay. - I cannot: mount, fdisk, mkfs mkdir /flash mount -t msdos /dev/nftla1 /flash Device not configured That might happen if /dev/nftla is not properly partitioned (fdisk) or /dev/nftla1 does not have an MS-DOS filesystem on it (mkfs.msdos). What happens if you try fdisk /dev/nftla instead? Can you see the MS-DOS partition from fdisk? Is it set to active? Assuming the answers are all yes, can you create an MS-DOS filesystem on the partition using: mkfs.msdos /dev/nftla1 ? If the mkfs goes well, you should definitely be able to mount /dev/nftla1 . The DOC has been reformatted with M-Sys version 4.2 because 5.x was not compatible. Unfortunately, I am not very familiar with the M-Sys utilities. I never found a need to use any of there software with my DoC. (I'm not even sure if mine was formatted with 4.2 or 5.x.) That said, if you can boot MS-DOS from the DoC the UG directions *should* work. I also put an MSDOS FAT-16 on it prior to this venture but tried fdisk anyway. Did you use Bill's fdisk or linux fdisk? What were the results? Better yet, what is the output of the linux fdisk -l /dev/nftla command? PROBLEM: Why is nftla, nftla1 not configured. What am I missing and/or where should I look. My guess is a partition or filesystem problem with the DoC. Let me know about the fdisk and mkfs.msdos results. If the problem seems to be elsewhere, I will lookup the error message you quoted in the source. --Brad --- 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
