Re: Re: how to make a bootable linux on doc

Re: Re: how to make a bootable linux on doc

[cytang]

Thanks to all replies .
These days I have read some materials about how to
make a bootable system on a floppy. According to them
,I must do like the following:
make a kernel --> make a mini file system->compress
the file system -> try to converge them 
but after many efforts ,I can not manage it
successfully .
I dont konw whether their method on a floppy can be
applied to my doc .
So, Could you do me a favor to give me some help or
materials about how you manage to make such a
filesystem ?
 


>Marius is correct - both LILO and patched GRUB can
>make the DOC Millennium bootable.  8MB is more than
enough space for a small system.
>I used a package called "Peewee Linux" (GPL-license)
>to set up my DOC Mil.  

> Marius is correct - both LILO and patched GRUB can
> make the DOC Millennium 
> bootable.  8MB is more than enough space for a small
> system.
> 
> I used a package called "Peewee Linux" (GPL-license)
> to set up my DOC Mil.  
> It currently uses 2.2 kernels, but it is possible to
> use a custom kernel -- 
> in my case, a 2.4.18 with the MTD drivers.
> 
> Mark



_________________________________________________________
Do You Yahoo!? 
摊开你的掌心 让我看看你
http://sweepstakes.yahoo.com/2002cnuser

lilo problem :dont know how to handle device ox5d01

[cytang]

lilo problem : sorry, dont know how to handle device
ox5d01

After I have make a mini system on my doc , I want to
make doc the boot disk.
I have get the doc-lilo from m-sys . but when I run
"doc-lilo -r /mnt/nftla1 " , I will get the erro
reported:
" sorry, dont know how to handle device ox5d01 "

So , I turn to lilo-mtd which can be found in
mtd-snapshot. 
This time , I run "./lilo-mtd -v -r /mnt/nftla1 " 
however , I get another erro:
" RSN; /dev/nftla1 is not a whole disk device "

the following may be some helpful 
1. my mtd code is 20020501 snapshot
  my linux is redhat 7.1 ,my doc is doc2000 ,32 m
2.
 fdisk /dev/nftla
 p
 the output is :
 Device      Boot  start   end  Blocks  id system
 /dev/nftla1  *    1       1001 32030   83 Linux 
3.fdisk /dev/nftla1
 p
 the output is :
 Device      Boot  start   end  Blocks  id system



_________________________________________________________
Do You Yahoo!? 
摊开你的掌心 让我看看你
http://sweepstakes.yahoo.com/2002cnuser

Why cannot boot off my doc 2000 ?

[cytang]

I have make a new kernel which can support doc . and I
have make a mini system on my doc like the following 
/doc/{bin,etc,sbin,lib,dev,proc,var,usr,mnt}, and
copied files I needed in respective directories

I mount the /dev/nftla1 on /doc .
my /doc/etc/lilo.conf is :

boot=/dev/nftla
install=/boot/boot.b-mtd
map=/boot/map-doc
disk=/dev/nftla
bios=0x80
prompt
delay = 50
timeout = 50
image = /boot/bzImage-doc
label = linuxondoc
root = /dev/nftla1
read-only

run:  lilo-mtd  -v -C /doc/etc/lilo.conf -r /doc

Patched LILO for M-Systems' DiskOnChip 2000
LILO version 21, Copyright 1992-1998 Werner
Almesberger

Ignoring entry 'install' 
Ignoring entry 'map'
Reading boot sector from /dev/nftla
Merging with /boot/boot.b-mtd
              ~~~~
Boot image: /boot/bzImage-doc
             ~~~~
Added linuxondoc *
/boot/boot.5D00 exists - no backup copy made.
~~~~~
Writing boot sector.

It seemed ok .but above why not /doc/boot?

If i remove my harddisk , I still cannot boot from my
doc . just get  "boot failure " .
why ?  Is something I did wrong ?  or I miss something
?


_________________________________________________________
Do You Yahoo!? 
摊开你的掌心 让我看看你
http://sweepstakes.yahoo.com/2002cnuser

Re: Why cannot boot off my doc 2000 ?

[Brian J. Fox]

   From: =?gb2312?q?cytang?= <cytang_cn@yahoo.com.cn>
   Date: Fri, 24 May 2002 23:39:26 +0800 (CST)

   run:  lilo-mtd  -v -C /doc/etc/lilo.conf -r /doc

   Boot image: /boot/bzImage-doc
		~~~~
   Added linuxondoc *

   It seemed ok .but above why not /doc/boot?

Because you specified "-r /doc" to lilo, which says to chroot to /doc
before starting to do anything.

In fact, a simple "lilo-doc -r /doc" will do the right thing for you.

   If i remove my harddisk , I still cannot boot from my
   doc . just get  "boot failure " .

That means that the DoC isn't bootable.  Maybe the first partition
isn't "active". 

Brian
== The Difference Between Cultures: ==
    Einigkeit und Recht und Freiheit
    Liberte', E'galite', Fraternite'
    Sex, drugs and rock'n'roll

Re: Why cannot boot off my doc 2000 ?

[cytang]

after many experiments, I think maybe two possiblity
lead to it .
NO 1:
I miss a step :
dupdate /win:{address} /s:doc42.exb /first, 
so I boot from a DOS floppy. 
but this time, when I run "dinfo" ,it  tells me  no
diskonchip found in system . 
I am sure before my new kernel support doc , I can use
"dinfo" to view information of doc on DOS,but now I
can't .
but even now ,I still can find it in my new kernel .
run dmesg , I can find diskonchip found on 0xdc000
,and I can read/write/mount /dev/nftla1 .
however I run "dformat /win:dc000 " ,I get "no
diskonchip 2000R found at c000:0" 
NO 2:
 something is wrong with lilo-mtd in my steps. 
In the "patches" in mtd-snapshot , I find
lilo-mtd.tar.gz.
the following is my steps
  tar zxvf lilo-mtd.tar.gz 
  then I get 3 files : lilo-mtd
,boot.b-mtd,lilo21-mtd-patch
  I dont use lilo21-mtd-patch. because I dont know
what use is it for .so  I just use lilo-mtd and
boot.b-mtd
 my step is :
  lilo-mtd -v -C /etc/doc-lilo.conf -i boot.b-mtd -m
/boot/map -r /doc  
  #doc is my mount point
  nothing bad is reported . 
the output I have descript it in the above page->
http://lists.infradead.org/pipermail/linux-mtd/2002-May/005064.html


_________________________________________________________
Do You Yahoo!? 
摊开你的掌心 让我看看你
http://sweepstakes.yahoo.com/2002cnuser

Re: Why cannot boot off my doc 2000 ?

[Ilguiz Latypov]

On Sat, 25 May 2002, [gb2312] cytang wrote:

> run dmesg , I can find diskonchip found on 0xdc000
> ,and I can read/write/mount /dev/nftla1 .
> however I run "dformat /win:dc000 " ,I get "no
> diskonchip 2000R found at c000:0" 

<offtopic>
Does dformat needs the segment address which is the absolute address 
divided by 16?  If this is true, perhaps /win:dc00 might work.
</offtopic>

Ilguiz