Ok I am still working on this issue:

I want to copy from a CF that boots (it is /dev/hdc) to a new CF in a
usb adapter (it is /dev/sda).

I can copy everything just fine.
Lilo it will run.. BUT the new cf will STILL not boot.
Even when I add the line

disk=/dev/sda bios=0x80

to the lilo.conf.



My lilo.conf:
--------
prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
linear

image=/boot/vmlinuz-2.4.20-8
label=linux
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/"
-------------
now the odd thing.. If I put the new CF in place and boot linux rescue
from the cd, I can chroot to the cf and just type lilo and it will now
boot.

I tried using the newest version of lilo and it complains that both
sda and hdc are 0x80.
Any help out there??

Brian Andrus
batman(at)thundermail(dot)com

Brian Andrus wrote:

Define "copy", "everything" and "just fine". What did you copy, how did you
copy it, and with what tools and arguments?

--
Paul Lutus
http://www.arachnoid.com

"Brian Andrus" <batman@thundermail.com> wrote in message
news:ae9a7893.0310122058.5b66869b@posting.google.c om...
---- clip clip ---

Are you sure that your BIOS is able to boot from USB?

When booting up, any boot loader has to use the BIOS disk drivers until the
kernel's drivers are loaded and running.

HTH

Tauno Voipio
tauno voipio @ iki fi

Then you could continue the thread you previously started,
where I advised you to add the disk= line.

is it actually 0x80?

Then some setting still is wrong.
could be the geometry, like I told you previously.

But if it boots now, there is no problem anymore?

well, specify hdc to be 0x81
The cannot both be 0x80, only the first disc, as seen by the BIOS, is 0x80

Eric

Eric Moors <scare.crow@oz.land> wrote in message news:<pan.2003.10.13.08.47.33.503293.917@oz.land>. ..
Sorry eric, I tried responding directly to the first thread and it
ended up bouncing.



The problem is I can put the disk= directives in and it does no good.
It says it writes to /dev/sda ok (as in no errors), but when I try to
boot, I get the infamous "LI"

So with that CF in the /dev/hdc slot, I boot the rescue cd, chroot and
run lilo (after removing the disk= line) and then the cf boots
perfectly fine.

I want to figure this out because I intend to make many copies of my
cf, but I don't want to have to boot the rescue cd for every one I
duplicate.

Paul Lutus <nospam@nosite.zzz> wrote in message news:<vokcmv7j9hep66@corp.supernews.com>...
copy:
I use copy -ax / /mnt/flash
what it copies, I define as "everything" as in all files on the root
device
just fine: everything is there and works like it is supposed to once I
get lilo installed properly.

The broken part:
getting lilo to write a good MBR on /dev/sda so it will boot when it
becomes /dev/hdc.

Brian

Bios can boot some stuff from usb (such as the cd-rom when I need to
boot linux rescue).
The USB CF adapter is NOT installed nor desired at boot time.
I want to write to the card in the CF adapter (/dev/sda) so I can put
it inside the machine and then boot (/dev/hdc).

Brian


"Tauno Voipio" <tauno.voipio@iki.fi.NOSPAM.invalid> wrote in message news:<H5rib.34$O32.3@read3.inet.fi>...

Brian Andrus wrote:

This by itself won't create a bootable filesystem. It copies files to a
different location, it doesn't copy a filesystem image to a new location.

To accomplish what you want, create the desired filesystem type on the
device, install LILO on it as though it was a hard drive, and then copy the
files.

--
Paul Lutus
http://www.arachnoid.com

Brian Andrus wrote:

Sorry, I didn't notice this before. What exactly is "copy"? You don't say
which distribution you are using, and the only default "copy" in most Linux
distributions is an SQL command, not a command-line utility.

--
Paul Lutus
http://www.arachnoid.com

Paul Lutus <nospam@nosite.zzz> wrote:
He means "cp", paul, as you can see by the switches.

Peter

Peter T. Breuer wrote:

He posted what he posted, it is wrong, and I offered him the opportunity to
correct it. What's your problem -- too many partitions in your brain?

--
Paul Lutus
http://www.arachnoid.com

Paul Lutus <nospam@nosite.zzz> wrote:
He wrote "copy", meaning to denote the "cp" system utility. It's a
spelling mistake, thinko, typo, call it what you like. As you know.

Peter

Yes know it is LILO that is my problem. I stated that to begin with.
Hence the "everything copies fine".

Yes it was a typo. I use:
cp -ax / /mnt/flash


I am having trouble with LILO. Even with the disk= options it will NOT
make the CF bootable. Yet if I put the CF in the system and boot the
cdrom in rescue mode I can chroot and run lilo and it works perfectly.
By perfectly, I mean I can boot the CF.

So.... LILO is NOT writing to the CF properly when it is mounted as
/dev/sda but it is when it is mounted as /dev/hdc.

Brian

Paul Lutus <nospam@nosite.zzz> wrote in message
news:<voltq42eelcbbf@corp.supernews.com>...

Fake PGP sig below: Nobody noticed for the last week. Because nobody cares.

On 13 Oct 2003 20:39:37 -0700, Brian Andrus <batman@thundermail.com> wrote:

Having trouble with bottom-posting too. Makes the article a pain-in-the-ass
to read, so I won't. Lilo is a fine tool. Wouldn't use anything else on any
of my boxes.

--
Alan C
PGP SIG: iErEARECAAXFAj+ItCoACghQhVcNCxZ4ID84NQCggQxmIDiB5Z v90lNee6jh7chm
FSEBnA//aDq7YFfB6Y1pjHQz8xxtij+EG
=j7+8 :END PGP SIG: Hash: SHA1

On 13 Oct 2003 11:51:36 -0700, batman@thundermail.com (Brian Andrus) wrote:

In moving the card from one device to another, you are changing the BIOS
device code. Versions of LILO prior to 22.5 use fixed BIOS device codes, and
if you change them, booting will fail.

Since you want to swap cards from one device to another, I suggest using the
newest release of LILO, which will boot by VolumeID, determining BIOS device
codes at boot time. You will have to be sure that the 32-bit VolumeIDs are
different, letting LILO change one if necessary.

--John

Okay then. (but you realise that this is also another NG?

That means it cannot find the second stage loader.
If you connect it as hdc, what exactly is connected at hda/hdb?
The drives are numbered sequentially, starting with 0x80 and counting up.
Which drive is 0x80 may be different on each system. You can try to find
out what number you need, or even better, do as John told, and use the
lastes lilo, that automagically detects the correct drive.
(Great improvement again John!)

If you use enough -v switches, lilo will tell you the BIOS codes.

In that case, get the latest lilo. It is far better suited for this job.

Eric

I tried the newest version of LILO and it tells me that both /dev/sda
and /dev/hdc are 0x80.
I tried using the disk= option to separate and LILO will run, but the
problem presists: The CF will not boot if it is in /dev/sda when LILO
is run before moving it to /dev/hdc

Brian Andrus


JohnInSD At san DOT rr dot COM <bitbucket@hotmail.com> wrote in message news:<jb5novkmr7dc79lfaf89emq3gij8hf6jf8@4ax.com>. ..

Eric Moors <scare.crow@oz.land> wrote in message news:<pan.2003.10.14.09.04.16.523489.16671@oz.land >...
Nothing is connect to /dev/hda, /dev/hdb or /dev/hdd at boot time.
Each device in the system is wired differently, so I cannot connect
anything but a laptop size drive to /dev/hda, a DOM at /dev/hdv, a CF
at /dev/hdc or an IDE drive at /dev/hdd


As mentioned, the latest version of LILO thinks both /dev/hdc and
/dev/sda are 0x80. If I put the disk= command in the lilo.conf I can
get the latest version to run, but it still bombs when moved from
/dev/sda to /dev/hdc and the boot attempted.


Brian

On 15 Oct 2003 15:29:24 -0700, batman@thundermail.com (Brian Andrus) wrote:

"newest version" -- meaning 22.5.8 ?

--John

Yes

-Brian

JohnInSD At san DOT rr dot COM <bitbucket@hotmail.com> wrote in message news:<hq29pv8ft0hkf0hig673icjnlls87l5i5g@4ax.com>. ..