Skip to contentSkip to conversation

Correction for the PA-RISC/Linux Boot HOWTO at ESIEE's web site.

parisc-linux Rafael Herrera 5 participants 5 messages Jan 11, 2002 – Jan 15, 2002

lore
Share & tools
lore
#0 lore raw

I'm booting a 715/80 workstation using a PC with SuSE 7.2. Trying to follow the examples to configure bootp/tftp at

http://mkhppa1.esiee.fr/parisc-linux-boot/parisc-linux-boot/preparation.html

I could not get it to boot.

This distribution sets the daemons as follows:

tftp    dgram  udp  wait  root  /usr/sbin/tcpd  in.tftpd -s /tftpboot
bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -c /tftpboot

This a chroot setup, so the example /etc/bootptab in the web page will not work.

The configuration that worked for me is the following:

parisc:hd=/:\
                :ht=ethernet:\
                :ha=0800093BF206:\
                :ip=192.168.0.8:\
                :bf=lifimage:\
                :sm=255.255.0.0:\
                :to=7200:

Where the bootable kernel image was the lifimage created using "make palo" (The web page description is ambiguous as to what image to use: vmlinux or lifimage)

Also the purpose of the parameter "rp" in the example bootptab is not clear in the example. Its purpose is to specify a root filesystem to mount, but the lifimage has that parameter set from palo Makefile.

Signature · 1 line
     Rafael
#1 lore raw

[parisc-linux] gcc bug

Hi All,

On my palinux box I got this gcc error while compiling a source code.

$ gcc -c -g -O3 c2.c
c.c: In function `string_match_1':
c.c:406: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

Where should I submit this? since it happen on a palinux box I dunno if the gcc maitainer does have such a box?

Thanx in advance,
Phi

--
mailto:[email protected]
WTEC HP-UX kernel debugging tools

#2 lore raw

Re: [parisc-linux] gcc bug

Quoted 1 line · phi 4369 wrote:

Where should I submit this?

iirc, the error output tells one where to submit the bug report. Perhaps that has changed.

Quoted 2 lines

since it happen on a palinux box I dunno if the
gcc maitainer does have such a box?

J. David Anglin is HPPA co-maintainer and he watches this list. And yes - he has several parisc boxes.

thanks,
grant

#3 lore raw

Re: [parisc-linux] gcc bug

Quoted 2 lines
Quoted 1 line · phi 4369 wrote:

Where should I submit this?

File it in gnats:
<http://gcc.gnu.org/cgi-bin/gnatsweb.pl>.

The more information that you can provide the better. One of the first things to do is generate preprocessed source, then run cc1 under a debugger to find where the segementation fault occurred.

Quoted 2 lines
Quoted 2 lines

since it happen on a palinux box I dunno if the
gcc maitainer does have such a box?

However, I don't yet have a working palinux system and neither does Jeff Law as far as I am aware. If the problem is generic, then with luck it can be fixed fairly easily. However, the odds are that the problem is specific to palinux.

One of the problems that we face is that the deb version of gcc has been quite heavily hacked for parisc-linux, and thus it isn't supportable. I hope that we can get one of the standard releases or the mainline code working as soon as possible. There are still problems with gdb and binutils on palinux (eg., passing floats in dynamic calls, etc).

Dave

Signature · 2 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)
#4 lore raw

[parisc-linux] New Version!! (was Correction for the PA-RISC/Linux Boot HOWTO at ESIEE's web site.)

In reply to Rafael Herrera

Hi all,

As Rafael Herrera did, I would like your feedback from my new
version of PA-RISC/Linux Boot HOWTO.
http://mkhppa1.esiee.fr/parisc-linux-boot/parisc-linux-boot/index.html

-I added a complete chapter about compiling a kernel for HP PA-RISC system. -I did a complete review of the text b/c of the progress of the port -I added a note for users that are not using Debian that you should blame the absence of standard for the default parameters more than the guy who did this howto :-)
(b/c there are a lot of distro for Linux and that's great but I can't do a step by step for each of them :-) )

Please, if you have any comment to make about this text, could you reply to me because I would like update the version of Linuxdoc with a minimum of errata.

Thomas.
ESIEE Team