[parisc-linux] woody install on 720/50

[parisc-linux] woody install on 720/50

[Albert Strasheim]

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

Hello all,

After applying Jurij's latest patch, and creating a new Debian bootdisk
lifimage with it, I booted it up and tried the Debian install again.

I tried a CD-ROM install first, but the installer refused to mount my
CD-ROM for some reason, even though it was detected as a possible device
to boot from.

Next I tried a network install using my i386 box (with co-ax network
card to connect to the 720) as a web server. According to the
access.log, the drivers.tgz and rescue.bin very retrieved without
problems. When it tried to extract the rescue.bin, it croaked with a 
message saying "Bad address." When I tried to retrieve the images a
second time, the installer croaked.

The box still responds to pings, but not much else.

Any ideas on the "Bad address" problem?

Regards,

Albert

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [parisc-linux] woody install on 720/50

[Albert Strasheim]

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Hello,

On Tue, 02 Oct 2001, Hamish Moffatt wrote:

> On Mon, Oct 01, 2001 at 05:54:25PM +0200, Albert Strasheim wrote:
> > After applying Jurij's latest patch, and creating a new Debian bootdisk
> > lifimage with it, I booted it up and tried the Debian install again.
> 
> Hmm, is that easy to do? I need to build a new kernel from the CVS
> sources for my D350, and it would be easiest to build a new CD
> to boot from rather than to boot the new kernel over the network.

I've think I've tried to convey the following command to you in about 3
different threads across 2 mailing lists :-)

Get palo-latest.tar.gz (about 62 KB) from puffin.external.hp.com,
compile that, cross-compile your kernel and then run the following:

(linux/ contains the kernel and palo/ contains the bootloader)

palo/palo/palo -f /dev/null -k linux/vmlinux -r root.bin -s lifimage \
  -b palo/iplboot -c "0/linux HOME=/ root=/dev/ram initrd=0/ramdisk"

What this does is the following:

palo takes the kernel (vmlinux (with Jurij's patches in my case)), the
latest Debian rootdisk (root.bin), puts them together and creates a
lifimage for you to boot via rbootd or tftpd (depending on your model).

Tada!

Have fun,

Albert

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [parisc-linux] woody install on 720/50

[Albert Strasheim]

[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]

Hello,

The palo README has some information on this. I quote:

                     Creating ISO9660 Bootable CD-ROMs

   Bootable CDs are often used for installation. In short the process is:
    1. Master your CD image but don't burn it. The image MUST containthe
       kernel(s), iplboot, and ramdisk file (if used).
    2. Run palo to make the image bootable:
        ./palo  -k path/to/vmlinux \
                -b iplboot \
                -c '0/vmlinux ....' \
                -C your-iso-image
       -C   tells   palo   to  prepare  a  CD-ROM  image.  'iplboot' and
       'path/to/vmlinux'  must  be exactly the same files (same contents)
       you  previously  copied  into  the future root file system or palo
       will  fail.  I usually point those paths at the exact files in the
       directory from which I mastered the CD just to be sure.
    3. Burn the CD and boot it.

   CD-ROM support at the moment is a bit of a hack. Here's how it works.

Read the README for some more info. I haven't tried this since my
(probably VERY old) SCSI CD-ROM drive won't read RW discs.

Regards,

Albert

On Tue, 02 Oct 2001, Hamish Moffatt wrote:

> On Tue, Oct 02, 2001 at 01:27:23AM +0200, Albert Strasheim wrote:
> > I've think I've tried to convey the following command to you in about 3
> > different threads across 2 mailing lists :-)
> 
> Err, yeah, you have. Sorry about that. Thanks for being patient :-)
> 
> > Get palo-latest.tar.gz (about 62 KB) from puffin.external.hp.com,
> > compile that, cross-compile your kernel and then run the following:
> > 
> > (linux/ contains the kernel and palo/ contains the bootloader)
> > 
> > palo/palo/palo -f /dev/null -k linux/vmlinux -r root.bin -s lifimage \
> >   -b palo/iplboot -c "0/linux HOME=/ root=/dev/ram initrd=0/ramdisk"
> > 
> > What this does is the following:
> > 
> > palo takes the kernel (vmlinux (with Jurij's patches in my case)), the
> > latest Debian rootdisk (root.bin), puts them together and creates a
> > lifimage for you to boot via rbootd or tftpd (depending on your model).
> 
> I'd particularly like to boot from CD if possible. The network boot
> is possible, but less convenient. Is it possible (and not unreasonably
> difficult) to create a new CD with the new kernel?
> 
> 
> thanks
> Hamish
> -- 
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [parisc-linux] woody install on 720/50

[Jochen Friedrich]

Hi Albert,

> Next I tried a network install using my i386 box (with co-ax network
> card to connect to the 720) as a web server. According to the
> access.log, the drivers.tgz and rescue.bin very retrieved without
> problems. When it tried to extract the rescue.bin, it croaked with a
> message saying "Bad address." When I tried to retrieve the images a
> second time, the installer croaked.

I don't know about this installer problem as i did the install manually
before. After applying the patch, the programs ls, tar, etc started
working OK and i just successfully performed the apt-get update/upgrade
:-)

Cheers,
Jochen

Re: [parisc-linux] woody install on 720/50

[Albert Strasheim]

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

Hello all,

An update on my 720/50. I've managed to get the install as far as
downloading all the packages. But when it starts extracting the first
package, base-files, it hangs. This is on 2.4.9-pa39.

Aside, when installing it seems one should create the palo
partition, create and initialise the swap partition, create and
initialise the ext2 partition. Now optionally set up the hostname and
networking, and then move directly to the installation of the base
system. This got me as far as getting all the packages downloaded, as
mentioned above.

I've booted a fresh nfsroot again, and as John Marvin mentioned a few
days ago, ls still hangs randomly, although it doesn't seem to depend on
the directory. On a previous boot I managed a ls -lR /, but now a simple
ls / hangs the system.

Any suggestions on how I proceed from here? What is still missing from
the kernel and what can I do to help fix it? :-)

Regards,

Albert

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [parisc-linux] woody install on 720/50

[Matthew Wilcox]

On Fri, Oct 05, 2001 at 10:20:28PM +0200, Albert Strasheim wrote:
> Any suggestions on how I proceed from here? What is still missing from
> the kernel and what can I do to help fix it? :-)

nothing's missing from the kernel -- the compiler needs to get fixed.

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] woody install on 720/50

[Albert Strasheim]

Hello,

On Fri, 05 Oct 2001, Matthew Wilcox wrote:

> On Fri, Oct 05, 2001 at 10:20:28PM +0200, Albert Strasheim wrote:
> > Any suggestions on how I proceed from here? What is still missing from
> > the kernel and what can I do to help fix it? :-)
> 
> nothing's missing from the kernel -- the compiler needs to get fixed.

Okay, I seem to recall now that you mentioned this. :-) What needs to
get done to "prove" that is a compiler bug. I'm willing to take it up
with the GCC people once I know what to tell them. :-)

Regards,

Albert

[parisc-linux] new vmlinux!!!

[Gururaj Ananthateerta]

I have 3 partitions on primary disk
   Device Boot    Start       End    Blocks   Id  System
/dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
/dev/sda2            96       339    249856   82  Linux swap
/dev/sda3           340      8683   8544256   83  Linux

I am doing some modifications to the code and trying to boot with a new
linux.
I placed my vmlinux in /boot, but the palo doesn't seems to recognize my
kernel.

Any suggestions.

Guru

Re: [parisc-linux] new vmlinux!!!

[Ralf Hildebrandt]

On Mon, Mar 11, 2002 at 02:56:25PM -0800, Gururaj Ananthateerta wrote:
> I have 3 partitions on primary disk
>    Device Boot    Start       End    Blocks   Id  System
> /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> /dev/sda2            96       339    249856   82  Linux swap
> /dev/sda3           340      8683   8544256   83  Linux
> 
> I am doing some modifications to the code and trying to boot with a new
> linux.
> I placed my vmlinux in /boot, but the palo doesn't seems to recognize my
> kernel.

How does the palo.conf look like?
What happens if you run palo?

-- 
Ralf Hildebrandt (Im Auftrag des Referat V A)   Ralf.Hildebrandt@charite.de
Charite Campus Virchow-Klinikum                 Tel.  +49 (0)30-450 570-155
Referat V A - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
Why you can't find your system administrators:
The admin is suffering so bad from sleep deprivation that they may as well not be there for all the sense you can make of the words they are saying. 

Re: [parisc-linux] new vmlinux!!!

[Grant Grundler]

Gururaj Ananthateerta wrote:
> I have 3 partitions on primary disk
>    Device Boot    Start       End    Blocks   Id  System
> /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> /dev/sda2            96       339    249856   82  Linux swap
> /dev/sda3           340      8683   8544256   83  Linux

partitions are fine.

> I am doing some modifications to the code and trying to boot with a new
> linux.
> I placed my vmlinux in /boot, but the palo doesn't seems to recognize my
> kernel.

What do you mean by "doesn't seems to recognize"?
any specific error msg?

does palo.conf point to that kernel?
or did you interact with palo to tell it to load that image?
"file /boot/vmlinux" says what?

you don't have to answer the above - just stuff to think about.

grant

Re: [parisc-linux] new vmlinux!!!

[Paul Bame]

> Gururaj Ananthateerta wrote:
> > I have 3 partitions on primary disk
> >    Device Boot    Start       End    Blocks   Id  System
> > /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> > /dev/sda2            96       339    249856   82  Linux swap
> > /dev/sda3           340      8683   8544256   83  Linux
> 
> partitions are fine.

Actually they're not.  This is a frequent install problem and I've
replied off the list about it.  The root partition passes the 2G limit
and Gururaj now has a small /boot I think.

	-P

Re: [parisc-linux] new vmlinux!!!

[Gururaj Ananthateerta]

Paul Bame wrote:

> > Gururaj Ananthateerta wrote:
> > > I have 3 partitions on primary disk
> > >    Device Boot    Start       End    Blocks   Id  System
> > > /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> > > /dev/sda2            96       339    249856   82  Linux swap
> > > /dev/sda3           340      8683   8544256   83  Linux
> >
> > partitions are fine.
>
> Actually they're not.  This is a frequent install problem and I've
> replied off the list about it.  The root partition passes the 2G limit
> and Gururaj now has a small /boot I think.
>

>         -P

yes you are right,
thanks
grant clarified this in his previous mail.

Re: [parisc-linux] new vmlinux!!!

[Gururaj Ananthateerta]

I figured out my mistake.

First my partitions weren't correct. I created
an F0 partition, and swap and an ext2 for /.

boot partition was missing, rather it was i /. As / is not mounted
during the early stages of boot (my guess) the palo used to scream at
me.

Secondly, a strange observation.  Partitions are created in the following
order seems to have have some problem  during from /boot/vmlinux.

50 MB of  FO partition
50 MB of /boot
256 MB of swap
remaining for /

Problem is solved if partitions are created in the following order.

/dev/sda1             1        95     97264   83
Linux                           /boot
/dev/sda2            96       119     24576   f0  Linux/PA-RISC boot
/dev/sda3           120       363    249856   82  Linux swap
/dev/sda4           364      8683   8519680   83  Linux                    /

Doesn't make much sense.

One more thing to add, I am doing all this stuff on a N-Class.

Guru








Grant Grundler wrote:

> Gururaj Ananthateerta wrote:
> > I have 3 partitions on primary disk
> >    Device Boot    Start       End    Blocks   Id  System
> > /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> > /dev/sda2            96       339    249856   82  Linux swap
> > /dev/sda3           340      8683   8544256   83  Linux
>
> partitions are fine.
>
> > I am doing some modifications to the code and trying to boot with a new
> > linux.
> > I placed my vmlinux in /boot, but the palo doesn't seems to recognize my
> > kernel.
>
> What do you mean by "doesn't seems to recognize"?
> any specific error msg?
>
> does palo.conf point to that kernel?
> or did you interact with palo to tell it to load that image?
> "file /boot/vmlinux" says what?
>
> you don't have to answer the above - just stuff to think about.
>
> grant

Re: [parisc-linux] new vmlinux!!!

[Grant Grundler]

Gururaj Ananthateerta wrote:
> First my partitions weren't correct. I created
> an F0 partition, and swap and an ext2 for /.

That's right - my bad.
(Not having a good day today)

> /dev/sda1             1        95     97264   83
> Linux                           /boot
> /dev/sda2            96       119     24576   f0  Linux/PA-RISC boot
> /dev/sda3           120       363    249856   82  Linux swap
> /dev/sda4           364      8683   8519680   83  Linux                    /

If your / (sda3 in the previous example) *ends* before 2GB,
you don't need a /boot partition. Several boot/install howto's
describe this problem. I didn't catch it in your original mail.

> > Gururaj Ananthateerta wrote:
> > > I have 3 partitions on primary disk
> > >    Device Boot    Start       End    Blocks   Id  System
> > > /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> > > /dev/sda2            96       339    249856   82  Linux swap
> > > /dev/sda3           340      8683   8544256   83  Linux
> >
> > partitions are fine.

NOT!

BTW, take a look at
	http://www.parisc-linux.org/hardware/supported.html

hth,
grant