[parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[M. Grabert]

Hello there!

I'm lucky again :)))))


Finally I got my HP box bootin & running Linux *smile*

There are some minor troubles, but I think these will be fixed soon,
e.g.

smb won't compile
netware won't compile
ppp_sync won't compile
fbcon-sti won't compile (at least when I don't compile STI-console)
hwclock doesn't work (can't use /dev/rtc), 'though I seems the
   time and date is read correctly (but hwclock can't set them).
   Is this a known problem ?

I think the "do_page_fault() messages & stack traces"  (, which are
   not seen when I switch VERBOSE=no in /etc/defaults/rcS,)
   are because of some segfaults whilst running some rc-scripts.
   Hope that will be fixed in the new nfsroot.

Many segfaults in sourcing / executing rc-boot-scripts and
   shutdown-scripts. Therefore (I think) I can't reboot/shutdown
   properly (last message is: "sending all processes the TERM signal").
   At least the HP doesn't reboot. But e2fsck reports ext2 is clean.

Is the well known problem of the missing termcap fixed in the new nfsroot?

Is is enough to copy nfsroot onto the scsi disc and adopt /etc/fstab,
   or should I use base.tgz ? what's the difference ?

Mhhh. missing ftp and (open)ssh, strace in (old) nfstools. Are they in the
   new one?

Does the new xc fix major problems or is it just a a little update ?
   IMHO there was a lot done for parisc64, but also for parisc(32) ?



Some questions regarding kernel support of...

networking: can I use all the protocols like ipv6, routing, masq etc?

WAX: is it still not usable ? if not, can I use all the Linux-2.4 isa
   drivers (easily) ?

modules: are kernel modules supported (fully) on parisc ?



greetings & TIA
                  max


PS: yes, quite alot of questions, but I hope that helps others, too!

Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[Grant Grundler]

Max,
I'm going to take a shot at answering your questions.
Some I don't know the answer.

"M. Grabert" wrote:
> Hello there!
> 
> I'm lucky again :)))))
> 
> 
> Finally I got my HP box bootin & running Linux *smile*

Excellent!


> There are some minor troubles, but I think these will be fixed soon,
> e.g.
> 
> smb won't compile
> netware won't compile
> ppp_sync won't compile

People just have to work through these issues one-by-one.
Feel free to post the issues (one per e-mail) to parisc-linux.
Include error messages from the compiler and where you
got the source from.

> fbcon-sti won't compile (at least when I don't compile STI-console)

The ESIEE team in France is doing alot of work with STI interfaces.
Hopefully they could answer this.
 
> hwclock doesn't work (can't use /dev/rtc), 'though I seems the
>    time and date is read correctly (but hwclock can't set them).
>    Is this a known problem ?

No. I had wrongly assume the /dev/rtc was on the latest NFS root
tar ball (it is not). You need to create it by hand:
	# mknod /dev/rtc c 10 135

If it already exists, then...well, post the console output of hwclock
command to parisc-linux as well.

> 
> I think the "do_page_fault() messages & stack traces"  (, which are
>    not seen when I switch VERBOSE=no in /etc/defaults/rcS,)
>    are because of some segfaults whilst running some rc-scripts.
>    Hope that will be fixed in the new nfsroot.

I think so. The patch from rhirst should help alot with this though.


> Many segfaults in sourcing / executing rc-boot-scripts and
>    shutdown-scripts. Therefore (I think) I can't reboot/shutdown
>    properly (last message is: "sending all processes the TERM signal").
>    At least the HP doesn't reboot. But e2fsck reports ext2 is clean.

ditto.

> Is the well known problem of the missing termcap fixed in the new nfsroot?

yes. (afaict).


> Is is enough to copy nfsroot onto the scsi disc and adopt /etc/fstab,
>    or should I use base.tgz ? what's the difference ?

You should be able to "install" the nfsroot as outlined in
the README.INSTALL (note that the PALO command has changed slightly).

If you want to just clobber an existing root that's in use, I think that
is a bit more complicated. Installing from NFS root or onto a different
disk should be easier.

> Mhhh. missing ftp and (open)ssh, strace in (old) nfstools. Are they in the
>    new one?

only ftp is there.
ssh has been built and used. Not sure if that was openssh.
Don't know about strace.

> Does the new xc fix major problems or is it just a a little update ?
>    IMHO there was a lot done for parisc64, but also for parisc(32) ?

Don't know. amodra?


> Some questions regarding kernel support of...
> 
> networking: can I use all the protocols like ipv6, routing, masq etc?

not tested. You *should* be able to assuming they access data
with proper address alignment.

> 
> WAX: is it still not usable ? if not, can I use all the Linux-2.4 isa
>    drivers (easily) ?

Don't know. (read my .sig "^)

> modules: are kernel modules supported (fully) on parisc ?

yes. But you need to install modutils before enabling that.
modutils_2.4.1-2_hppa.deb is available from the parisc-linux.org ftp site.

hope this helps,
grant

Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253

Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[Alex deVries]

Grant Grundler wrote:
> Max wrote:
> > WAX: is it still not usable ? if not, can I use all the Linux-2.4 isa
> >    drivers (easily) ?
> 
> Don't know. (read my .sig "^)

We don't have any WAX EISA bridge work working yet... but I have docs
and it is on my to do list.

- Alex

-- 
Alex deVries, Principal Solutions Architect, The Puffins at Linuxcare
613.562.2759 tel
alex@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Putting open source to work.

Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[Richard Hirst]

On Tue, Feb 06, 2001 at 12:22:03PM -0800, Grant Grundler wrote:
> Don't know about strace.

If you check it out of our cvs and build it, it should basically
work under 32 bit kernels.  I still need to tidy up before I can
integrate though.

Richard

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions & 9000/730 success report

[Christoph Plattner]

I was definitly not able to build strace with the current tool chain
(I have built myself from Jan 13, 2001). The system calls and other
parts seem not to be compatible any more....

Richard Hirst wrote:
> 
> On Tue, Feb 06, 2001 at 12:22:03PM -0800, Grant Grundler wrote:
> > Don't know about strace.
> 
> If you check it out of our cvs and build it, it should basically
> work under 32 bit kernels.  I still need to tidy up before I can
> integrate though.
> 
> Richard
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux


-----------------------------------------------------------------
private:        christoph.plattner@dot.at
company:        christoph.plattner@alcatel.at

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions & 9000/730 success report

[Richard Hirst]

On Wed, Feb 07, 2001 at 08:59:25AM +0100, Christoph Plattner wrote:
> I was definitly not able to build strace with the current tool chain
> (I have built myself from Jan 13, 2001). The system calls and other
> parts seem not to be compatible any more....

I've removed the hack that made it work with old glibc that didn't
provide a sys_ptrace wrapper, so it should now be ok with a newer
toolchain.  So, if you could try again and let me know...

Richard

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions & 9000/730 success report

[Christoph Plattner]

Hello
	you mean, I can now check out the strace from CVS ?
And retry ??

Thanks
	Christoph

Richard Hirst wrote:
> 
> On Wed, Feb 07, 2001 at 08:59:25AM +0100, Christoph Plattner wrote:
> > I was definitly not able to build strace with the current tool chain
> > (I have built myself from Jan 13, 2001). The system calls and other
> > parts seem not to be compatible any more....
> 
> I've removed the hack that made it work with old glibc that didn't
> provide a sys_ptrace wrapper, so it should now be ok with a newer
> toolchain.  So, if you could try again and let me know...
> 
> Richard

-- 
  +--------V--------+	Christoph.Plattner@alcatel.at
  |  A L C A T E L  |	-----------------------------
  +-----------------+	Phone: +43 1 27722 3706	
         T A S		Fax:   +43 1 27722 3955

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions & 9000/730 success report

[Richard Hirst]

On Wed, Feb 07, 2001 at 02:25:50PM +0100, Christoph Plattner wrote:
> Hello
> 	you mean, I can now check out the strace from CVS ?
> And retry ??

Yes

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions & 9000/730 success report

[Alan Modra]

On Wed, 7 Feb 2001, Christoph Plattner wrote:

> I was definitly not able to build strace with the current tool chain
> (I have built myself from Jan 13, 2001). The system calls and other
> parts seem not to be compatible any more....

Did you build glibc too?  I should own up to breaking our CVS glibc with

revision 1.3
date: 2001/01/16 14:09:38

and not fixing it until

revision 1.4
date: 2001/02/05 14:58:22

Alan (Embarrassed) Modra
-- 
Linuxcare.  Support for the Revolution.

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions& 9000/730 success report

[Christoph Plattner]

Again, I have problems with strace:
-----------------------------------

(0) autoconf is ok
    automake reports errors... (I think I need that !)

configure.in: 86: `automake requires `AM_CONFIG_HEADER', not
`AC_CONFIG_HEADER'
automake: configure.in: `PACKAGE' not defined in configure.in
automake: configure.in: `VERSION' not defined in configure.in
automake: configure.in: required file `./mkinstalldirs' not found
automake: configure.in: required file `./missing' not found
automake: no `Makefile.am' found or specified


(1) The `configure' scripts reports 2 problems

bash# HOSTCC=gcc CC=hppa-linux-gcc ../configure --target=hppa-linux
--host=hppa-linux
:
:
creating Makefile
creating linux/Makefile
sed: can't read ./linux/Makefile.in: No such file or directory
creating config.h
cat: ./config.h.in: No such file or directory

(2) make fails fully ... (this is the full log of make !!)

hppa-linux-gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa
-Ilinux -I./linux -D_GNU_SOURCE  -c strace.c
defs.h:421: conflicting types for `strerror'
/usr/parisc/hppa-linux/include/string.h:229: previous declaration of
`strerror'
defs.h:424: conflicting types for `strsignal'
/usr/parisc/hppa-linux/include/string.h:306: previous declaration of
`strsignal'
strace.c:1005: conflicting types for `sys_errlist'
/usr/parisc/hppa-linux/include/stdio.h:564: previous declaration of
`sys_errlist'
strace.c:1009: parse error before '(' token
strace.c:1029: conflicting types for `sys_siglist'
/usr/parisc/hppa-linux/include/signal.h:281: previous declaration of
`sys_siglist'
make: *** [strace.o] Error 1

		
I have the glibc built cross (I built also the toolchain). The stuff was
from the
snapshot of the Jan 13th 2001 !!
The toolchain works very well !

Have I a wrong glibc version, or is strace not ready for my version yet
??

With friendly regards
	Christoph




Alan Modra wrote:
> 
> On Wed, 7 Feb 2001, Christoph Plattner wrote:
> 
> > I was definitly not able to build strace with the current tool chain
> > (I have built myself from Jan 13, 2001). The system calls and other
> > parts seem not to be compatible any more....
> 
> Did you build glibc too?  I should own up to breaking our CVS glibc with
> 
> revision 1.3
> date: 2001/01/16 14:09:38
> 
> and not fixing it until
> 
> revision 1.4
> date: 2001/02/05 14:58:22
> 
> Alan (Embarrassed) Modra
> --
> Linuxcare.  Support for the Revolution.
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions& 9000/730 success report

[Richard Hirst]

On Thu, Feb 08, 2001 at 11:42:47PM +0100, Christoph Plattner wrote:
> Again, I have problems with strace:
> -----------------------------------

Works for me, this is on a B180, latest nfsroot.tar.gz (but on local
disk), with most of the newer debs from

ftp://puffin.external.hp.com/pub/parisc/binaries/new-debs/debian/

However, I believe it worked for me before those updates also:


richard@merlin:~$ uname -a
Linux merlin 2.4.0 #2 Wed Feb 7 16:29:34 GMT 2001 parisc unknown
richard@merlin:~$ 
richard@merlin:~$ cvs checkout strace
cvs server: Updating strace
U strace/.cvsignore
U strace/COPYRIGHT
...
...
U strace/test/sfd.c
U strace/test/sig.c
richard@merlin:~$ 
richard@merlin:~$ 
richard@merlin:~$ cd strace
richard@merlin:~/strace$ autoconf
richard@merlin:~/strace$ autoheader 
richard@merlin:~/strace$ ./configure
creating cache ./config.cache
checking host system type... hppa-unknown-linux-gnu
checking for supported operating system... linux
checking for supported architecture... hppa
checking for gcc... gcc
checking whether the C compiler (gcc -D_GNU_SOURCE  ) works... yes
checking whether the C compiler (gcc -D_GNU_SOURCE  ) is a cross-compiler... no
...
...
updating cache ./config.cache
creating ./config.status
creating Makefile
creating linux/hppa/Makefile
creating config.h
richard@merlin:~/strace$ make
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c strace.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c version.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c syscall.c
syscall.c:459: warning: `decode_subcall' defined but not used
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c util.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c desc.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c file.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c ipc.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c io.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c ioctl.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c mem.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c net.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c process.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c bjm.c
bjm.c: In function `sys_query_module':
bjm.c:83: warning: int format, size_t arg (arg 4)
bjm.c:92: warning: int format, size_t arg (arg 2)
bjm.c:114: warning: int format, size_t arg (arg 2)
bjm.c:115: warning: int format, size_t arg (arg 2)
bjm.c:132: warning: int format, size_t arg (arg 2)
bjm.c:133: warning: int format, size_t arg (arg 2)
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c resource.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c signal.c
signal.c:867:2: warning: #warning NO sys_sigreturn DECODE FOR HPPA
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c sock.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c system.c
system.c: In function `sys_sysctl':
system.c:1737: warning: int format, size_t arg (arg 2)
system.c:1747: warning: int format, size_t arg (arg 3)
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c term.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c time.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c proc.c
gcc -Wall -DHAVE_CONFIG_H   -I. -Ilinux/hppa -I./linux/hppa -Ilinux -I./linux -D_GNU_SOURCE  -c stream.c
gcc  -o strace strace.o version.o syscall.o util.o desc.o file.o ipc.o io.o ioctl.o mem.o net.o process.o bjm.o resource.o signal.o sock.o system.o term.o time.o proc.o stream.o -lnsl 
richard@merlin:~/strace$ 
richard@merlin:~/strace$ 
richard@merlin:~/strace$ ./strace ./strace
execve("./strace", ["./strace"], [/* 22 vars */]) = 0
newuname({sys="Linux", node="merlin", ...}) = 0
brk(0)                                  = 0x34000
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
newfstat(3, {st_mode=S_IFREG|0644, st_size=7103, ...}) = 0
mmap(NULL, 7103, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4001c000
close(3)                                = 0
open("/lib/libnsl.so.1", O_RDONLY)      = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0J\244"..., 1024) = 1024
newfstat(3, {st_mode=S_IFREG|0644, st_size=92920, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001e000
mmap(NULL, 104028, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001f000
mprotect(0x40035000, 13916, PROT_NONE)  = 0
mmap(0x40035000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x15000) = 0x40035000
mmap(0x40037000, 5724, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40037000
close(3)                                = 0
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\2k\314"..., 1024) = 1024


etc. etc.

Richard

Re: [parisc-linux] //strace// Generic Parisc Linux Kernel Questions& 9000/730 success report

[Alan Modra]

On Thu, 8 Feb 2001, Christoph Plattner wrote:

> Again, I have problems with strace:
> -----------------------------------
> 
> (0) autoconf is ok
>     automake reports errors... (I think I need that !)

Don't run automake!  As you can see..
[snip]
> automake: no `Makefile.am' found or specified

Everything goes downhill from here.

Alan
-- 
Linuxcare.  Support for the Revolution.

Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[Thomas Marteau]

Hi Max,

	Here is the ESIEE Team answer! (Exactly what our experince told us :))
smb is one of the most famous questions of LWE Paris. So someone will
have to port it.
We do not think that it has been done yet

> smb won't compile
do not know> netware won't compile
do not know> ppp_sync won't compile

> fbcon-sti won't compile (at least when I don't compile STI-console)
The matter of frame buffer is quite complex. When we look at the code,
the fb-sti init is the first then came up the sti-console init. This
explained the snow you have on the screeen when you compile a kernel
with fbcon-sti and sti-console. This info can be out of date! If someone
has a better news , speak :)

> hwclock doesn't work (can't use /dev/rtc), 'though I seems the
>    time and date is read correctly (but hwclock can't set them).
>    Is this a known problem ?
We think also about /dev/rtc as Grant told you

> Is the well known problem of the missing termcap fixed in the new nfsroot?
Do not think so
> 
> Is is enough to copy nfsroot onto the scsi disc and adopt /etc/fstab,
>    or should I use base.tgz ? what's the difference ?
As we use the network for nfs and ftp, you have to configure the
following files:
/etc/hostname
/etc/network/interfaces
/etc/fstab
also you have to check
/dev/console for sti it should be linked to /dev/tty0
	     for serial it should be linked to /dev/ttyS0
It seems interesting to lokk into /etc/inittab 

> Mhhh. missing ftp and (open)ssh, strace in (old) nfstools. Are they in the
>    new one?
ftp packages (client/server) are available: http://www.esiee.fr/puffin
> 
> Does the new xc fix major problems or is it just a a little update ?
>    IMHO there was a lot done for parisc64, but also for parisc(32) ?
We agree but it is our reason to work, isn't it? 

Here ends what we could answer. Good Luck to all :)

ESIEE Team

Re: [parisc-linux] Generic Parisc Linux Kernel Questions & 9000/730 success report

[Helge Deller]

Hello Mr Grabert,

On Tuesday 06 February 2001 23:12, Thomas Marteau wrote:
> Hi Max,
>
> > fbcon-sti won't compile (at least when I don't compile STI-console)
>
> The matter of frame buffer is quite complex. When we look at the code,
> the fb-sti init is the first then came up the sti-console init. This
> explained the snow you have on the screeen when you compile a kernel
> with fbcon-sti and sti-console. This info can be out of date! If someone
> has a better news , speak :)

I just checked in new cleaned-up and updated code for STI console into CVS a 
few days back, which at least should compile cleanly. 
fbcon-sti belonged to the old code, which was originally written by Philipp 
Rumpf and got very outdated during all the upgrades we did from kernel 2.3.X 
to currently plain 2.4.0. Please just stand by and you will get a working STI 
console for
 - word mode ROMs,
 - byte mode ROMs,
 - monocrome STI framebuffer,
 - support for linux framebuffer fonts in STI text console,
 - (if possible: support for HP X-Servers under parisc-linux)
and much more in the future.
Please keep also in mind, that all the necessary coding is just done in my 
spare time and so it will of course take some time to get it finished. If you 
want to help speeding things up please just send patches to the list.

Greetings,

	Helge Deller