Re: [leaf-user] Floppy Image Problems

2002-12-01 Thread Chris Cranford 
If someone could explain how I could unzip this file on my windows box, edit
it's contents manually and then update the archive with the minor changes, I
think it would ease my problems.  I'm beginning to suspect my drive on my
LRP machine is bad when writing data to the disk; however doesn't appear to
have issues when reading the data.

Chris

- Original Message -
From: Chris Cranford [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, December 01, 2002 2:51 AM
Subject: [leaf-user] Floppy Image Problems


 I have downloaded the v1.0 stable windows executable file and ran it on a
 windows machine to format and copy the necessary LRP packages to a floppy
 disk.  When I boot on the disk for the first time, everything is fine;
 however once I have added a few new modules (*.o files in
/boot/lib/modules)
 and backed up my initrd.lrp package, I see read errors when writing the
new
 lrp image to the disk.

 If anyone can help me out here I'd be greatful.  So far, this has happened
 with 7 diskettes and I'm beginning to doubt the fact it's the disks that
are
 the problem as the diskettes have worked fine in the past.

 Thanks for any help on the matter!
 Chris




 ---
 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] Floppy Image Problems

2002-12-01 Thread Jeff Newmiller 
On Sun, 1 Dec 2002, Chris Cranford wrote:

 If someone could explain how I could unzip this file on my windows box, edit
 it's contents manually and then update the archive with the minor changes, I
 think it would ease my problems.

a) the format is not zip ... it is gzipped tar

b) you need to be able to edit textfiles with LF newlines... you should be
able to use Cygwin for this.

c) I am pretty sure you have to use compression level 9 when
re-compressing... use cygwin's gzip.

Native windows tools have a very poor track record with such tasks...

 I'm beginning to suspect my drive on my
 LRP machine is bad when writing data to the disk; however doesn't appear to
 have issues when reading the data.

I think this is unlikely... much more likely is that the ramdisk or floppy
has insufficient free space or you are trying to backup while the disk is
mounted. If you can read the oversize disk, you should be able to write to
it.

 
 Chris
 
 - Original Message -
 From: Chris Cranford [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, December 01, 2002 2:51 AM
 Subject: [leaf-user] Floppy Image Problems
 
 
  I have downloaded the v1.0 stable windows executable file and ran it on a
  windows machine to format and copy the necessary LRP packages to a floppy
  disk.  When I boot on the disk for the first time, everything is fine;
  however once I have added a few new modules (*.o files in
 /boot/lib/modules)
  and backed up my initrd.lrp package, I see read errors when writing the
 new
  lrp image to the disk.
 
  If anyone can help me out here I'd be greatful.  So far, this has happened
  with 7 diskettes and I'm beginning to doubt the fact it's the disks that
 are
  the problem as the diskettes have worked fine in the past.
 
  Thanks for any help on the matter!
  Chris
 
 
 
 
  ---
  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
 

---
Jeff NewmillerThe .   .  Go Live...
DCN:[EMAIL PROTECTED]Basics: ##.#.   ##.#.  Live Go...
  Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/BatteriesO.O#.   #.O#.  with
/Software/Embedded Controllers)   .OO#.   .OO#.  rocks...2k
---



---
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] Floppy Image Problems

2002-12-01 Thread Lee Kimber 
At 02:51 AM 12/1/2002 -0500, you wrote:

I have downloaded the v1.0 stable windows executable file and ran it on a
windows machine to format and copy the necessary LRP packages to a floppy
disk.  When I boot on the disk for the first time, everything is fine;
however once I have added a few new modules (*.o files in /boot/lib/modules)
and backed up my initrd.lrp package, I see read errors when writing the new
lrp image to the disk.

If anyone can help me out here I'd be greatful.  So far, this has happened
with 7 diskettes and I'm beginning to doubt the fact it's the disks that are
the problem as the diskettes have worked fine in the past.

Thanks for any help on the matter!
Chris


If the error is something like Could not mount device then your disk is 
still mounted from when you added the new modules and you need to unmount 
it first. (You'll have to reboot and start again once this has happened, I 
think)

If the backup seems to go OK with some packages and then starts producing 
errors along the lines of Could not save... (or similar), then it is 
because your disk is full.

You can hopefully avoid this by removing unneeded modules before backing 
up. Look for modules that are in /lib/modules but which are commented out 
in /etc/modules and remove them from /lib/modules.





---
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

[leaf-user] Re: Can't see my NICs / pci-scan.o? Eureka!

2002-12-01 Thread Minh Duong 

Christian,

You don't put your NIC driver modules in
/boot/lib/modules.  /boot/lib/modules is for
components that are to be booted before everything
else (i.e. cd rom drivers).  You need to put your NIC
modules in /lib/modules.

Minh

--
 Message: 2
 Date: Sat, 30 Nov 2002 21:54:31 -0800 (PST)
 From: Christian Hoss [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: [leaf-user] Can't see my NICs / pci-scan.o?
 Eureka!
 
 Rechecked my configuration, decided to take the
 cable
 modem offline 20 minutes instead of the previous 5 -
 I
 am now answering this off my windows box thru the
 firewall.  Thanks to all who helped...
 
 __
 Do you Yahoo!?
 Yahoo! Mail Plus - Powerful. Affordable. Sign up
 now.
 http://mailplus.yahoo.com
 
 


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.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

[leaf-user] Problem: Bering DOC in latest stable version

2002-12-01 Thread John Mullan 
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

RE: [leaf-user] Problem: Bering DOC in latest stable version

2002-12-01 Thread S Mohan 
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

2002-12-01 Thread John Mullan 
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

[leaf-user] Bering 1.0 libm.lrp

2002-12-01 Thread Homer Parker 
What file do I need to alter to fix this? 

Copying wireless.lrp Please wait: Back-up of wireless complete
cat: /var/lib/lrpkg/libm.list: No such file or directory
Creating libm.lrp Please wait: \tar: /tmp/EXCLUDE: No such file or
directory
rm: cannot remove `/tmp/EXCLUDE': No such file or directory

New Package:
-rw-r--r--1 root root   20 Dec  2 02:50 /tmp/libm.lrp
Old Package:
-rwxr-xr-x1 root root39619 Nov 22 00:12
/var/lib/lrpkg/mnt/libm.lrp
Filesystem   1k-blocks  Used Available Use% Mounted on
/dev/hda1 3908  2592  1316  66% /var/lib/lrpkg/mnt

I've just been saying no, but it's only a matter of time before I goof...
This is a stock lrp, so the archive needs fixed as well...

--- 
Homer Parker

http://www.homershut.net
telnet://bbs.homershut.net




msg11377/pgp0.pgp
Description: PGP signature

[leaf-user] How to add Static Route on Bering RC3

2002-12-01 Thread Thitiporn Pornpirunrak 
Hi all,
 I would like to add static route on my bering box. I try to add them on Network 
Configuration menu and interfaces like this

eth1 .

up ip route add 192.168.11.0 via 192.168.11.1 eth1

 But after i restart my firewall i didn't see that route please tell me why...

thanx.†+,~w­zf¢–+,¦‰ì¢·o$áŠyyézW(™ëhç¤…æ¯zxm¶Ÿÿ¶§’ž‘ÊþÇåy§î±êæj)bž  
b²Ù^iû¬z¹b²Û,¢êÜyú+éÞ¶m¦Ïÿ–+-²Ê.­ÇŸ¢¸ë–+-³ùb²Ø§~åy§î±êÒDP†Ûiÿù^iúk¢7œ¶Šàþ››ýÚýÚ™©Úêÿv‡w_=Öf

RE: [leaf-user] How to add Static Route on Bering RC3

2002-12-01 Thread Andrew Braund 
Once you had edited the file in Network Configuration, did
you then backup the etc package?
b:3

HTH
Andrew Braund

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Thitiporn
 Pornpirunrak
 Sent: Monday, 2 December 2002 13:41
 To: LeafUser
 Subject: [leaf-user] How to add Static Route on Bering RC3


 Hi all,
  I would like to add static route on my bering box. I try to add
 them on Network Configuration menu and interfaces like this

   eth1 .
   
   up ip route add 192.168.11.0 via 192.168.11.1 eth1

  But after i restart my firewall i didn't see that route please
 tell me why...

 thanx.N1y5i
 X22
 u)gYig=i6Z~XHzG{f:G(
 x
 Ky'1j
 K2
 qg.zX6~X6K:7~
 zw~X6O
 Kzf:GIB'y'.rZzowswrfj}Z   ]wX



---
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] How to add Static Route on Bering RC3

2002-12-01 Thread Brad Fritz 

Thitiporn,

It would be nice if you posted in plain text to ask your questions
rather than base64 encoding them.  Plain text is easier for many of
us to read and reply to.  Anyway, on to your route question...

Thitiporn wrote:

   I would like to add static route on my bering box. I try to add
  them on Network Configuration menu and interfaces like this
  [..]
  up ip route add 192.168.11.0 via 192.168.11.1 eth1

On Mon, 02 Dec 2002 14:18:38 +1030 Andrew Braund wrote:

 Once you had edited the file in Network Configuration, did
 you then backup the etc package?
 b:3

You should also check the syntax of the command by running it
manually:

  homefw: -root-
  # ip route add 192.168.11.0 via 192.168.11.1 eth1
  Error: either to is duplicate, or eth1 is a garbage.

You might want:

  ip route add 192.168.11.0/24 via 192.168.11.1 dev eth1
   ^^^  ^^^
assuming you are trying to add a network route for a /24 network.
If you don't already have an interface defined in the 192.168.11.0
network, you will probably need:

  ip route add 192.168.11.1 dev eth1

or similar first.  There should be several posts in the leaf-user
archive[1] on static routes under Bering if you need more or more
complete examples.

--Brad

[1] http://www.mail-archive.com/leaf-user%40lists.sourceforge.net/



---
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

2002-12-01 Thread Brad Fritz 

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

[leaf-user] updated DiskOnChip Bering UG chapter

2002-12-01 Thread Brad Fritz 

Bering Crew,

I updated the Installing and booting Bering from a M-Systems
DiskOnChip user's guide chapter for Bering 1.0-stable.  Is it
possible to incorporate the changes into the official UG?  The
changes were primarily to update the modules paths and to
remove the step that described the bug fixes that are already
in 1.0-stable.

The DocBook XML is at
  
http://cvs.sf.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/devel/bradfritz/bering_contrib/doc/budiskonchip.xml?rev=HEADcontent-type=text/xml


Everyone,

I have posted an HTML version at
  http://fritzfam.com/brad/leaftmp/budiskonchip.html

if you would like to read the document before it makes it into
the Bering UG.  As always, comments and suggestions welcome.

--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