🚀 go-pugleaf

In aus.computers.linux Tim Tuck <Tim.Tuck@penrith.net> wrote:

> OH and there seems to be some serious documentation errors such as the
> the boot linux gets call linuz instead of linux.gz - or is this
> symptomatic of other problems ?

Im not sure about the alpha issue, but on ix86 systems, in the /boot
directory.. the vmlinuz file is the Compressed BOOT Image.
Whereas the vmlinux file is the uncompressed image, which is used for putting out the internal tables and sybols for things like kernel debugging, and klogd, and auto-oops resolving stuff.

---
Anthony Rumble
LinuxHelp http://www.LinuxHelp.com.au Phone: 0500 500 368
Direct 02-9712-1799 Mobile 0412-955-042  Fax 02-9712-3977

In article <39311A0E.E4BC0025@penrith.net>,
  Tim.Tuck@penrith.net wrote:
>
> Hi all,
>
> I'm having the damnedest time trying to get RH 6.2 onto my AS 200/4.
> I've determined that the X gui crashes just about anywhere in the
> install but if I quickly switch to pts1 just as I click the install
> button the install will complete. BUT...
I'd suggest you put out your mouse and try the text-based install...

> booting out of milo I get a Kernel Panic and the machine freezes.
how did you boot... ?
I had problems with booting the CD, by floppy it was no problem
(boot fd0:vmlinux.gz root=/dev/scd0)

have luck,

Chris


Sent via Deja.com http://www.deja.com/
Before you buy.

Tim Tuck (Tim.Tuck@penrith.net) wrote:

: OH and there seems to be some serious documentation errors such as the
: the boot linux gets call linuz instead of linux.gz - or is this
: symptomatic of other problems ?

A boot file name, if it is compressed or not, if it has suffix .gz or
not, etc.  is plain immaterial.  You may call it "mickeymouse" is such
fancy will strike you (but then watch for Disney lawyers knocking to
your door :-).  Some years ago first version of a loader on Alpha indeed
looked if '.gz' is present or not but this is an ancient prehistory.

BTW - a compressed form of a kernel loads faster (time differences
are really not that important :-)  as your memory and processor are
substantially faster than your disk.  Why Red Hat in recent
distributions (not only Alpha) stuck in /boot both compressed and
uncompressed versions of boot images is not something for which
I can find any rational explanation.

  Michal

p.s. If you load your boot images from a device with a file system
different than ext2 (like FAT or "pure" ISO9660, for example) you better
keep file names for that withing constraints that fs or you will have
problems to find them in a boot time.  This actually applies universally
but it is hard to create on ext2, for example, a file with a name which
ext2 does not recognize.

Michal Jaegermann wrote:

> Tim Tuck (Tim.Tuck@penrith.net) wrote:
>
> : OH and there seems to be some serious documentation errors such as the
> : the boot linux gets call linuz instead of linux.gz - or is this
> : symptomatic of other problems ?
>
> A boot file name, if it is compressed or not, if it has suffix .gz or
> not, etc.  is plain immaterial.  You may call it "mickeymouse" is such
> fancy will strike you (but then watch for Disney lawyers knocking to
> your door :-).  Some years ago first version of a loader on Alpha indeed
> looked if '.gz' is present or not but this is an ancient prehistory.
>
> BTW - a compressed form of a kernel loads faster (time differences
> are really not that important :-)  as your memory and processor are
> substantially faster than your disk.  Why Red Hat in recent
> distributions (not only Alpha) stuck in /boot both compressed and
> uncompressed versions of boot images is not something for which
> I can find any rational explanation.
>
>   Michal
>
> p.s. If you load your boot images from a device with a file system
> different than ext2 (like FAT or "pure" ISO9660, for example) you better
> keep file names for that withing constraints that fs or you will have
> problems to find them in a boot time.  This actually applies universally
> but it is hard to create on ext2, for example, a file with a name which
> ext2 does not recognize.

I have installed RH 6.2 on a 200 4/233 from the ISO image i downloaded
from a redhat mirror. I believe you have to dd the generic.img kernel
unto a floppy. I was working from milo too. Has any body been able
to get the PCMCIA support to work (yess I have the sourceforge.com
code)... but configuring has been a real pain: i'nsmod i82365.o' causes
a hang. 'insmod ds.o'  comes back saying 'file or resource busy' .

Sincerely,

J.C. Magras

ckaspro@my-deja.com wrote:

[snip]

> I'd suggest you put out your mouse and try the text-based install...
>

Did that - thanx

BUT....

The end result is the same  - a no boot system.

I did some extra sluthing and I noticed thst the /boot partion is the
only one I can read! If I do a:

ls sda5:/

I get

%
%%
%%%
%%
%%
%%%
%%%%
%%


for about 10 lines !

It would seem that the install is stuffing the FAT or somthing at the
end of the install. The other partitions look the same.

So... now I'm reinstalling 5.2 and doing an upgrade - I've run 5.2 on
this thing before so it will be interesting to see how it goes.

BTW - this box is a MUSTANG which is one of the older AS200's - I think
it maxs out at 100Mhz.


> how did you boot... ?
> I had problems with booting the CD, by floppy it was no problem
> (boot fd0:vmlinux.gz root=/dev/scd0)

my boot line for cd was as follows:

boot scd0:/kernels/generic.gz root=/dev/scd0


cheers

Tim