* [parisc-linux] XFree86 on B180
From: Joël Soete @ 2001-08-03 10:26 UTC (permalink / raw)
To: parisc-linux, debian-hppa
Hi all,
To test Xfree86, I install following packages:
xserver-xfree86_4.0.3-4_hppa.deb
xserver-common_4.0.3-4_hppa.deb
xterm_4.0.3-4_hppa.deb
xlibmesa3_4.0.3-4_hppa.deb
xlib6g_4.0.3-4_all.deb
xfree86-common_4.0.3-4_all.deb
xfonts-scalable_4.0.3-4_all.deb
xfonts-base_4.0.3-4_all.deb
xfonts-75dpi_4.0.3-4_all.deb
xfonts-100dpi_4.0.3-4_all.deb
xlibs_4.0.3-4_hppa.deb
libxaw7_4.0.3-4_hppa.deb
libfreetype6_2.0.2.20010514-1_hppa.deb
xdm_4.0.3-4_hppa.deb
xbase-clients_4.0.3-4_hppa.deb
libxaw6_4.0.3-4_hppa.deb
xutils_4.0.3-4_hppa.deb
On the B180 I use the same XF86config as on 712/80, the one from Thomas
Bogendoerfer available at:
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-June/012928.html
(I also changed "repeat_type=ms3" to "repeat_type=" in /etc/gpm.conf to
make mouse working correctly)
With kernels 2.4.0-32 and 2.4.6 xdm failed because:
"(EE) No devices detected.
Fatal server error:
no screen found.
..."
With the last kernel 2.4.7-pa1, it failed: on the console a lot of "kernel
BUG at init.c:731!"
Thanks in advance for all advises,
Joel
PS: I also try to boot with palinux-0.9.2 CD on a B2000 but the kernel
panic at the boot time (sorry no more info)
**********************************************************************
This e-mail and any attachments to it may contain confidential information which is strictly intended for the use of the authorised recipient. If you have received this e-mail in error, please delete it and notify the sender by replying to this e-mail.
Thank you for your co-operation.
**********************************************************************
^ permalink raw reply
* Re: [parisc-linux] Problems with Installing of 0.9.2 on HP 715/100
From: Martin Eisfeld @ 2001-08-03 9:26 UTC (permalink / raw)
To: parisc-linux
Hello,
here are the full putput from serial terminal (terminalemulation with
hyperterminal from winnt).
Most of it was not displayed on the monitor attached to the hp9000.
Bye,
Martin Eisfeld
0x04.1081
0x04.1080
0x04.1082
0x04.1086
0x04.1087
0x04.108A
0x04.108B
0x04.108C
0x04.1083
0x04.10D1
0x04.10D2
0x04.2090
0x04.2091
0x04.209F
0x04.2096
0x04.2094
0x04.2095
0x06.C201
0x04.10DA
0x04.10D7
0x04.10D8
----------------------------------------------------------------------------
BootRom Version 1.2
Memory Size: 256 MB
----------------------------------------------------------------------------
(c) Copyright 1990-1994, Hewlett-Packard Company.
All rights reserved
Press <ESCAPE> to stop boot sequence.
0x04.2097
0x04.2098
0x04.2099
0x04.209A
0x04.209B
0x04.1091
0x04.1092
0x04.1093
0x04.1094
0x04.1095
0x04.1096
0x04.1090
0x04.108D
0x04.10D4
0x04.10D9
0x04.4080
0x04.4081
0x04.4082
0x06.C2EA
0x06.C2EF
0x04.300C
0x04.300C
0x04.300B
----------------------------------------------------------------------------
Command Description
------- -----------
Auto [boot|search] [on|off] Set/show auto mode
Boot [pri|alt [isl]] Boot from primary or alternate
path
Boot [scsi|eisa.<slot>[.<addr>]] [isl] Boot from SCSI or EISA
Boot lan[.<addr>] [install] [isl] Boot from LAN
Chassis [on|off] Set/show chassis codes display
mode
DefaultSS Reboot and set EEPROM to default
values
Diagnostic [on|off] Set/show diagnostic boot mode
Fastboot [on|off] Set/show fast boot mode
Help Show this command menu
Information Show system information
LanAddress Show LAN station addresses
Monitor [<DEV>[.<type>]] Set/show graphics monitor type
(<DEV>=graphics|graphics_<1|2>)
Path [pri|alt [<DEV>[.<addr>]]] Set/show boot source path
(<DEV>=lan|scsi|eisa.<slot>)
Path [console [<DEV>[.<parm>]]] Set/show boot console path
(<DEV>=<RS232>|<GRAPH>
<RS232>=rs232|rs232_2
<parm>=<baud>.<length>.<parity>
<GRAPH>=graphics|graphics_<1|2>
<parm>=<monitor>)
Path [keyboard [hil|ps2]] Set/show boot keyboard path
Pim [hpmc|toc|lpmc] Show PIM info
Search [ipl] [scsi|eisa] Show potential boot devices
Search [ipl] [lan [install]] Show potential boot LAN devices
Secure [on|off] Set/show security mode
----------------------------------------------------------------------------
BOOT_ADMIN> boot scsi.2.0
0x06.C740
Attempting to boot.
Loading Initial Program Loader
0x06.C580
IPL successfully loaded
Booting
0x06.C7FF
palo ipl 0.92 root@spqr Mon Jun 25 23:03:13 CEST 2001
0/vmlinux32 2853588 bytes @ 0x6ad6800
0/vmlinux64 3585851 bytes @ 0x6d8f800
0/ramdisk 1991209 bytes @ 0x70fb000
Command line: 'root=/dev/ram console=ttyS0 TERM=vt102'
Kernel: partition 0 file /vmlinux
Ramdisk: partition 0 file /ramdisk
Warning: kernel name doesn't end with 32 or 64... Guessing Annoyance:
Firmware d
oes not support PDC_MODEL_CAPABILITIES call
32
ELF32 executable
Entry 00100000 first 00100000 n 4
Segment 0 load 00100000 size 1606948 mediaptr 0x1000
Segment 1 load 0028a000 size 468472 mediaptr 0x18a000
Segment 2 load 00300000 size 8192 mediaptr 0x1fd000
Segment 3 load 0034bea8 size 80688 mediaptr 0x1ffea8
Loading ramdisk 1991209 bytes @ 0fe09000...
branching to kernel entry point 0x00100000
Set default PSW W bit to 0
0x02.CBF0
0x02.503F
GRs
0x00000000
0x00000000
0xF4100000
0x00000001
0xF5000000
0x00000003
0x00000001
0xF0024328
0x0000000D
0xF0305698
0xF4300000
0x00000000
0x00080BEF
0x00010000
0x00000005
0x00000032
0x00000000
0x00283BAB
0x00000001
0x00000000
0x00000000
0xF0024000
0x00000500
0x0B00002D
0x00000001
0x00000000
0x00283BAB
0x1028A010
0x00000001
0xF0305698
0x003058D8
0x007793E8
CRs
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x000000C0
0x0000001C
0x00000000
0x00000000
0x00105800
0xFFFFFFFF
0xF153AA4B
0x00000000
0x00778944
0xB3202000
0x00000000
0x00778964
0x00007F00
0x80000000
0x002A6000
0x002A6000
0xFFFFFEFF
0x0900DEEE
0xAAAAAAAA
0xF0002000
0x00000000
0x0000001F
SRs
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
OTHER
0x00000000
0x00778948
0x20000000
0x9E000004
0x00000000
0x00000000
0x00000000
0x00310000
0x00000000
0x00000000
0x00000000
0xF0305710
0xFFFBE000
0x00000000
0x00000002
0x301048E6
0x3B6A561A
0x02.CBFB
Dumping Stack from 00304000 to 003058d8:
Dumping Stack from 10292000 to 10292700:
2000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2020 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2040 00000000 00000000 00000000 0029e000 00000000 00000000 00000000
00000000
2060 00000000 00000000 00000000 0010c8a4 00000000 00000000 00000000
00000000
2080 00007f00 00000000 f4100000 00000001 f5000000 00000003 00000001
f0024328
20a0 0000000d f0305698 f4300000 00000000 00080bef 00010000 00000005
00000032
20c0 00000000 00283bab 00000001 00000000 00000000 f0024000 00000500
0b00002d
20e0 00000001 00000000 00283bab 1028a010 00000001 f0305698 003058d8
007793e8
2100 00000002 301048e6 3b6a561a 00000000 00000000 00000000 00000000
00000000
2120 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2140 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2160 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2180 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
21a0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
21c0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
21e0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2200 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2220 00000000 00000000 00778944 00778948 0000001f 00000000 00000000
00000000
2240 00000000 0000001c b3202000 00000000 00778964 00000000 00000000
00000000
2260 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2280 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
22a0 00000000 00000000 00000000 10106750 00000000 00000000 00000000
00000000
22c0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
22e0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2300 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2320 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2340 00000000 00000000 0000001f 00296000 002a6000 f0012870 00000000
00000000
2360 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2380 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
23a0 00000000 00000000 00000000 10102220 00000000 00000000 00000000
00000000
23c0 00000000 00000000 00000001 10292080 00000000 00000000 00000000
f0002840
23e0 00310000 00000037 f0305698 0000000d f0002848 00000000 00000000
00000001
2400 10292080 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2420 00000000 00000000 00000000 10102614 00000000 00000000 00000000
00000000
2440 102565e4 00000001 10292080 00000000 00000000 00000000 00000000
00000000
2460 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2480 00000000 00000000 00000000 00000000 00000000 003058d8 00304000
10256774
24a0 00000000 00000000 00000000 10102568 00000000 00000000 00000000
00000000
24c0 0004000e 10337010 10102614 00304000 003058d8 10256000 00000000
f0002848
24e0 0000000d f0305698 00000037 00310000 f0002840 00000000 00000000
f0305710
2500 10292080 00283bab 00000002 00000000 00000000 f0105800 01c9c380
00000060
2520 00000001 00000001 1029f3c0 1028a010 0000002a 00000000 10292700
00000000
2540 000d081f 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2560 00000000 00000000 00000000 00000000 00000000 00000000 40800000
00000000
2580 7fffffff 7fffffff 7f7fffff ffffffff 7f7fffff ffffffff 00000000
00000000
25a0 00000000 00000000 41800000 00000000 00000010 00000010 00000000
00000000
25c0 7fffffff 7fffffff 41000000 00000000 40800000 00000000 7fffffff
7fffffff
25e0 41000000 00000000 7fffffff 7fffffff 40800000 00000000 41000000
00000000
2600 40300000 00000000 40200000 00000000 40200000 00000000 41800000
7fffffff
2620 40000000 00000000 40000000 00000000 40800000 00000000 41000000
00000000
2640 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
2660 00000000 00000000 10102574 10102578 0000001f 00000000 00000000
00000000
2680 00000000 0000001f 0c701093 00000000 00304008 00000000 00000000
00000000
26a0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
26c0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
26e0 00000000 00000000 00000000 10106750 00000000 00000000 00000000
00000000
Kernel Fault: Code=15 regs=102924c0 (Addr=00304008)
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001000000000000001110
r0-3 00000000 10337010 10102614 00304000
r4-7 003058d8 10256000 00000000 f0002848
r8-11 0000000d f0305698 00000037 00310000
r12-15 f0002840 00000000 00000000 f0305710
r16-19 10292080 00283bab 00000002 00000000
r20-23 00000000 f0105800 01c9c380 00000060
r24-27 00000001 00000001 1029f3c0 1028a010
r28-31 0000002a 00000000 10292700 00000000
sr0-3 00000000 00000000 00000000 00000000
sr4-7 00000000 00000000 00000000 00000000
IASQ: 00000000 00000000 IAOQ: 10102574 10102578
IIR: 0c701093 ISR: 00000000 IOR: 00304008
ORIG_R28: 00000000
^ permalink raw reply
* Re: [parisc-linux] dev-packages
From: Andrew Shugg @ 2001-08-03 5:25 UTC (permalink / raw)
To: parisc-linux
In-Reply-To: <Pine.BSF.4.30.0108030645560.38503-100000@noc.zabbadoz.net>
Quoth Bjoern A. Zeeb:
> On Thu, 2 Aug 2001, Matthew Wilcox wrote:
> > They're all available in the debian archive. I don't think we have
> > plans to produce any more CDs until the Debian Woody release (probably
> > December).
>
> Could you point me to some URL (incl. subdir) please ?
If you've got apt configured (/etc/apt/apt.conf, /etc/apt/sources.list)
then you don't need to worry about finding things directly. After doing
an 'apt-get update' to fetch the current Packages files and rebuild the
local package database, you can say 'apt-cache search foo' and it will
show you all the packages called foo or with foo in their description.
A simple 'apt-get install foo-dev' will download and install the foo-dev
package and any other package it may require according to its
dependencies.
For more info & discussion on actual Debian issues rather than the
actual development of the hppa-linux kernel and toolchain have a look at
the debian-hppa mailing list (on the Debian website).
Andrew.
--
Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/
"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there? Well I'd like to meet him. I could do with a good laugh."
^ permalink raw reply
* Re: [parisc-linux] Linux on R947X?
From: robert.holmberg @ 2001-08-03 5:13 UTC (permalink / raw)
To: parisc-linux
Stan Sieler wrote:
>> I believe we are talking about a 947RX which is the MPe equivalent of
the
>> G30.
> Yes.
Checking the label of the box, yes. My memory must have failed me.. :) It
is running MPe/iX, but I'm not touching it. Maybe I shouldn't be, but VMS
and SCO-Unix have left me scared to death of vendor-specific OSes.
> And, of course, you're giving up a lot more turning an HP 3000 into a
Linux
> box than you are when turning an HP 9000 into a Linux box :-)
Yes, the only time its been down in the last three years was a month ago
when the serverroom cooing failed and the power was cut when the
temperatute rose too much. I seriously wonder if the W2K servers supposed
to replace it will even get close to this kind of reliability.
> Seriously, if he has a 947RX, he might be able to resell it.
If we won't be able to use it after it goes out of production service this
fall, this would be the general idea, yes. Who would be buying and what
should they be paying?
> As far as selling a 922? It's a very old HP 3000, and has little or no
> market value :( (By "little or no", I mean: you'll be lucky to sell it
for $50.)
I know it isn't exactly worth its weight in anything else than sweat
(carrying it), but how about the sex appeal? That must count for something!
:-)
Robert.
^ permalink raw reply
* Re: [parisc-linux] dev-packages
From: Bjoern A. Zeeb @ 2001-08-03 4:56 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: parisc-linux
In-Reply-To: <20010802221905.C20250@parcelfarce.linux.theplanet.co.uk>
On Thu, 2 Aug 2001, Matthew Wilcox wrote:
> They're all available in the debian archive. I don't think we have
> plans to produce any more CDs until the Debian Woody release (probably
> December).
Could you point me to some URL (incl. subdir) please ?
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
^ permalink raw reply
* Re: [parisc-linux] Linux on R947X?
From: Grant Grundler @ 2001-08-03 0:23 UTC (permalink / raw)
To: CARSON,KEVIN (HP-Canada,ex1); +Cc: robert.holmberg, parisc-linux
In-Reply-To: <B9957F974955D411829400D0B74FF27A04BF7875@xtor01.canada.hp.com>
"CARSON,KEVIN (HP-Canada,ex1)" wrote:
> I believe we are talking about a 947RX which is the MPe equivalent of the
> G30.
Ok.
> This presents two problems. The hardware is identical to the G30 but
> everything that I have read in the PA-Linux project is that support for
> these machines will be a long time coming, if ever.
So far, no one inside HP has volunteered to make it happen.
If someone external wants to sign an NDA for device docs and make it
happen, that might be possible.
> The second problem is
> that the firmware is different for MPe than HP-UX.
At some point MPE systems were only different from HPUX systems
by changing the model string. G30 is a "nova-class" machine and
might predate this.
thanks,
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
^ permalink raw reply
* Re: [parisc-linux] dev-packages
From: Matthew Wilcox @ 2001-08-02 21:19 UTC (permalink / raw)
To: Bjoern A. Zeeb; +Cc: parisc-linux
In-Reply-To: <Pine.BSF.4.30.0108022303200.38503-100000@noc.zabbadoz.net>
On Thu, Aug 02, 2001 at 11:06:15PM +0200, Bjoern A. Zeeb wrote:
> is there any chance to get more/all dev-packages on the next ISOs or
> place them somewhere on ftp.
> Couldn't find them anywhere (except those that are in isos).
>
> This would avoid lots of bootstrapping work.
>
> (especially looking for pam and X -dev packages at the moment ;)
They're all available in the debian archive. I don't think we have
plans to produce any more CDs until the Debian Woody release (probably
December).
--
Revolutions do not require corporate support.
^ permalink raw reply
* [parisc-linux] dev-packages
From: Bjoern A. Zeeb @ 2001-08-02 21:06 UTC (permalink / raw)
To: parisc-linux
Hi,
is there any chance to get more/all dev-packages on the next ISOs or
place them somewhere on ftp.
Couldn't find them anywhere (except those that are in isos).
This would avoid lots of bootstrapping work.
(especially looking for pam and X -dev packages at the moment ;)
Thanks a lot.
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
^ permalink raw reply
* Re: [parisc-linux] Problems with Installing of 0.9.2 on HP 715/100
From: Bjoern A. Zeeb @ 2001-08-02 21:03 UTC (permalink / raw)
To: Martin Eisfeld; +Cc: parisc-linux
In-Reply-To: <3B693F62.E1E701F7@hedd.de>
On Thu, 2 Aug 2001, Martin Eisfeld wrote:
> Hello everyone,
> I have a big proplem of installing PA-RISC Linux 0.9.2 on a HP9000 Model
> 715/100.
>
> I have downloaded the cd-image palinux-0.9.2.iso.gz from
[snip]
> Then the the maschine reboots.
>
> I have tried to boot the cd on to different hp9000 model 715/100. The
> result is everytime the same.
Hi,
I also had problems with 0.92iso (and 0.91iso).
palinux-0.9-32serial.iso then worked for me and the machine is up and
running for days.
Why 0.91/2 doesn't work I still don't know :(
Hope that helps.
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
^ permalink raw reply
* Re: [parisc-linux] Fwd: [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd)
From: Bjorn Helgaas @ 2001-08-02 20:24 UTC (permalink / raw)
To: Grant Grundler, 'Richard Hirst'; +Cc: parisc-linux
In-Reply-To: <200108021632.KAA20911@puffin.external.hp.com>
> > Is this an issue for parisc as well?
>
> I'm pretty sure parisc port has already addressed this since insmod
> works. Talk to Richard Hirst since he's done most of the kernel modules
> support.
insmod works fine on ia64 as well. The problem they tripped over was that
ksymoops running native on ia64 and using /proc/ksyms failed, while a
running ksymoops on ia32 (cross debug mode) with ia64 debug info and
System.map worked fine.
ismod uses the descriptor address (which ia64 currently puts in
/proc/ksyms), while ksymoops requires the code address.
^ permalink raw reply
* Re: [parisc-linux] Linux on R947X?
From: Stan Sieler @ 2001-08-02 19:11 UTC (permalink / raw)
To: "CARSON,KEVIN (HP-Canada,ex1)"
Cc: 'Grant Grundler', robert.holmberg, parisc-linux
In-Reply-To: <B9957F974955D411829400D0B74FF27A04BF7875@xtor01.canada.hp.com>
Re:
> I believe we are talking about a 947RX which is the MPe equivalent of the
> G30.
Yes.
> these machines will be a long time coming, if ever. The second problem is
> that the firmware is different for MPe than HP-UX. Conversion from a 947RX
AFAIK, the firmware should be 100% identical. The only diference I'm aware of
is the model string and the OS-license info in stable storage.
And, of course, you're giving up a lot more turning an HP 3000 into a Linux
box than you are when turning an HP 9000 into a Linux box :)
Seriously, if he has a 947RX, he might be able to resell it.
As far as selling a 922? It's a very old HP 3000, and has little or no
market value :(
(By "little or no", I mean: you'll be lucky to sell it for $50.)
--
Stan Sieler sieler@allegro.com
www.allegro.com/sieler/wanted/index.html www.sieler.com
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: Matthew Wilcox @ 2001-08-02 18:42 UTC (permalink / raw)
To: LaMont Jones; +Cc: parisc-linux
In-Reply-To: <20010802040435.818241872C@security.hp.com>
On Wed, Aug 01, 2001 at 10:04:34PM -0600, LaMont Jones wrote:
> I started to play with getting the hppa assembly code in guile-core to work
> on pa-linux, but ran into challenges with %farg[0-3], which aren't defined
> by the assembler...
I already discussed this in detail with the maintainer; details of the
discussion can be found in the BTS. I'm disappointed you decided to
waste your time on this without reading that discussion or talking to me.
> I'm about to upload a source NMU of guile-core, which has qt/md/hppa*-linux.?
> in it. If someone wanted to take that the rest of the way, I'd be happy to
> upload it...
No, don't do this, it's completely unnecessary.
--
Revolutions do not require corporate support.
^ permalink raw reply
* RE: [parisc-linux] Linux on R947X?
From: CARSON,KEVIN (HP-Canada,ex1) @ 2001-08-02 16:50 UTC (permalink / raw)
To: 'Grant Grundler', robert.holmberg; +Cc: parisc-linux
I believe we are talking about a 947RX which is the MPe equivalent of the
G30.
This presents two problems. The hardware is identical to the G30 but
everything that I have read in the PA-Linux project is that support for
these machines will be a long time coming, if ever. The second problem is
that the firmware is different for MPe than HP-UX. Conversion from a 947RX
to a G30 might be available but it wouldn't matter, one could probably pick
up a used G30 or newer for less $$ than the conversion would cost.
Kevin
> -----Original Message-----
> From: Grant Grundler [mailto:grundler@puffin.external.hp.com]
> Sent: Thursday, August 02, 2001 9:25 AM
> To: robert.holmberg@idobath.com
> Cc: parisc-linux@lists.parisc-linux.org
> Subject: Re: [parisc-linux] Linux on R947X?
>
>
> robert.holmberg@idobath.com wrote:
> > I have not found any indication that anyone
> > has gotten Linux to work on a R947X at all,
> ....
>
> I've never heard of "R947X".
> Do you mean HP 9000 R-470?
> What does HPUX "model" or "uname -a" command say?
> Is this machine already registered in the HW database?
>
> grant
>
> Grant Grundler
> parisc-linux {PCI|IOMMU|SMP} hacker
> +1.408.447.7253
>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
>
^ permalink raw reply
* Re: [parisc-linux] Linux on R947X?
From: Grant Grundler @ 2001-08-02 16:25 UTC (permalink / raw)
To: robert.holmberg; +Cc: parisc-linux
In-Reply-To: <OF037B89B3.C54112C3-ONC2256A9C.001F38E3@LocalDomain>
robert.holmberg@idobath.com wrote:
> I have not found any indication that anyone
> has gotten Linux to work on a R947X at all,
....
I've never heard of "R947X".
Do you mean HP 9000 R-470?
What does HPUX "model" or "uname -a" command say?
Is this machine already registered in the HW database?
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
^ permalink raw reply
* [parisc-linux] Fwd: [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd)
From: Bjorn Helgaas @ 2001-08-02 15:11 UTC (permalink / raw)
To: parisc-linux
Is this an issue for parisc as well?
---------- Forwarded Message ----------
Subject: [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd)
Date: Thu, 02 Aug 2001 13:38:40 +1000
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@linuxia64.org
FYI. Followups to linux-kernel@vger.kernel.org please, the initial
problem is IA64 specific but the fix is a generic one for all
architectures that require special processing, it needs to be discussed
on l-k. I would have used Bcc: to ia64 but this list rejects Bcc mail.
------- Forwarded Message
The IA64 use of descriptors for function pointers has bitten ksymoops.
For those not familiar with IA64, &func points to a descriptor
containing { &code, &data_context }. System.map contains the address
of the code, /proc/ksyms contains the address of the descriptor.
insmod needs the descriptor address, ksymoops and debuggers need the
code address, /proc/ksyms needs to contain both addresses, with one of
them prefixed by a special character.
EXPORT_SYMBOL() cannot distinguish between &function and &data.
Telling everybody that they must type EXPORT_SYMBOL_FUNCTION or
EXPORT_SYMBOL_DATA is not an option, the second symbol has to be
automatically added after linking vmlinux and modules. I want to fix
this problem in user space, with no changes to to kernel code. My
proposal for kernel 2.5 is :-
* In System.map and /proc/ksyms, label foo addresses the code, not the
descriptor. Label &foo addresses the function descriptor.
* foo has symbol versions, &foo does not.
* In kernel build, all objects that export symbols are post processed
immediately after they are compiled. On most architectures the post
process is a no-op. On IA64 it runs a program from modutils that
identifies exported function pointers and modifies the ksymtab and
kstrtab, see below.
* At run time, insmod does its normal address fixup processing first,
including checking for symbol versions. If the existing code
succeeds without unresolved symbols, insmod modifies the address
fixup so a reference to foo is resolved to &foo, iff both foo and
&foo are in /proc/ksyms.
This has the benefit that all the changes are in modutils plus a small
change to the kernel build, no other user space tools are affected.
Most user space programs expect foo to address the code, not the
descriptor, AFAIK it is only insmod that needs the descriptor. This
change will also affect any code that tries to front end functions from
modules but IMNSHO code should not be doing that. If this breaks
binary only modules - tough.
One problem that always has to be addressed with modutils is version
skew between user space and the kernel. With this approach, if you
build a new kernel with old modutils then the post processing program
will not be available so ksyms has the old format and the old insmod
behaviour applies, ksymoops will get errors but the kernel will still
run. With a new modutils but an old kernel you get the old behaviour.
The only way you can get problems with version skew is to compile a
kernel on one machine with new modutils and install on another machine
with old modutils, modules will oops. I don't see this as a problem,
the IA64 population is fairly small, in any case gcc cross compile for
IA64 has problems right now.
The new modutils supplied program (/usr/bin/modules_post) will look
through the __ksymtab section for an object. For each exported symbol,
look at the data it references. If that data contains two relocatable
addresses, one pointing to a text symbol, the other to a data symbol
and the text symbol has the same name as the exported symbol then this
is a descriptor. Change the exported symbol name to &foo and add an
exported symbol foo that points to the code.
Note: This is modutils 2.5 stuff. modules_post needs to use BFD which
current modutils does not use, this adds a new requirement when
compiling modutils. Using BFD is the only way I can handle all
the relocation types, especially in cross compile mode. It may
or may not get backported to modutils 2.4, probably not.
ksymoops on IA64 2.4 will just have to live with lots of
warnings.
------- End of Forwarded Message
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
-------------------------------------------------------
^ permalink raw reply
* [parisc-linux] Problems with Installing of 0.9.2 on HP 715/100
From: Martin Eisfeld @ 2001-08-02 11:54 UTC (permalink / raw)
To: parisc-linux
Hello everyone,
I have a big proplem of installing PA-RISC Linux 0.9.2 on a HP9000 Model
715/100.
I have downloaded the cd-image palinux-0.9.2.iso.gz from
parisc-liux.org, i have decompressed it with gzip on a linux-machine and
burned it with Nero 5.5 on a NT-machine.
When i poweron the hp, i press ESC until i'm in the boot-admin-menu.
Therefrom i boot with
'boot scsi.2.0' (the scsi-id of the cd-rom is 2)
from the cd.
Then a window comes which says
"Attempting to boot."
Then the cd boots. There are lots of different messages.
One warning comes:
"warning: Kernelname doesn't end with 32 or 64"
After that, other messages came on my screen.
The last message is:
"Set default PSW W bit to 0".
Then the the maschine reboots.
I have tried to boot the cd on to different hp9000 model 715/100. The
result is everytime the same.
Bye,
Martin Eisfeld
^ permalink raw reply
* [parisc-linux] 715/80 not booting (kernel crashes)
From: S Looman @ 2001-08-02 9:03 UTC (permalink / raw)
To: parisc-linux
Hi,
Just got a 715/80 box from a friend and started playing with it, but HP-UX
sucks and wanted to install linux on it.
I downloaded the iso-image yesterday and booted it.
The cd boots, starts loading the kernel 'n stuff. But then it panics.
It has the same dump as this email:
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-July/013193.html
I guess using another kernel should fix it, but I can't build any kernel...
Can anybody give me a kernel (or suggestions)?
Thx,
Steven
PS.
Sorry for using hotmail
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: Alan Modra @ 2001-08-02 6:48 UTC (permalink / raw)
To: LaMont Jones, parisc-linux
In-Reply-To: <20010802151415.O5233@bubble.sa.bigpond.net.au>
On Thu, Aug 02, 2001 at 03:14:15PM +0930, Alan Modra wrote:
> Hmm, I wonder if you've found a gcc bug?
Curiousity got the better of me, and I dug up copy of the ABI. Looks
like gcc is doing the right thing.
"Floating-Point (32 Bits, single-precision): One word, callee cannot assume
a valid floating-point number.
Floating-Point (64 Bits, double-precision): Two words, double word aligned
(high order word in odd arg word). This may create a void in the argument
list. 64-bit floating-point value parameters mapped to the first and second
double-words of the argument list should be passed in farg1 and farg3,
respectively. farg0 and farg2 are never used for 64-bit floating-point
parameters. Callee cannot assume a valid floating-point number."
Makes a weird sort of sense when you realise that the register args have
a mapping to stack slots, and there are only 4x32 bits of stack space,
or 2 doubles.
Alan
^ permalink raw reply
* Re: [parisc-linux] Linux on R947X?
From: robert.holmberg @ 2001-08-02 5:49 UTC (permalink / raw)
To: parisc-linux
>> Any hope of getting the Lotus Domino webserver up and running under
>> PARISC-LINUX on a R947X? The server is going to be replaced soon, and we
>> have played with the thought of using it as a local test environment for
>> deployment of Domino web applications.
>According to the Domino website
>(http://www.lotus.com/home.nsf/welcome/domino), they only support
>Linux on x86.
I should have thought of that. I have not found any indication that anyone
has gotten Linux to work on a R947X at all, so I also meant to ask if at
least this is possible. We can run the test environment on any NT server,
but it would be nice to continue using such a reliable machine as the old
HP for something useful. Paying for a HPUX lisence is not exactly in our
interest, though..
>They do have a version for HPUX so if we were to get
>the HPUX emulation working again, there's a possibility it might work.
>Nobody has much interest in the HPUX emulation right now, so I wouldn't
>count on it happening any time soon.
So this idea of ours is somewhat ... optimistic. I'm actually just working
here for the summer and was asked to find out if this was at all possible.
We have a 922LX as well, nut unfortunately the company has decided to try
and sell this one. I'd buy it myself if it weren't for its size and weight.
>On the other hand if you happen to be a big corporate customer and could
>persuade them to port Domino to a different platform... :-)
Not THAT big. :=)
Robert
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: Alan Modra @ 2001-08-02 5:44 UTC (permalink / raw)
To: LaMont Jones; +Cc: parisc-linux
In-Reply-To: <20010802044946.6B4FC1872C@security.hp.com>
On Wed, Aug 01, 2001 at 10:49:45PM -0600, LaMont Jones wrote:
> > > So fix the assembler! gas/config/tc-hppa.c:pre_defined_registers
> > Dunno which regs they are, and don't have a current runtime arch doc at
> > home.
>
> This code seems to think that four args are passed in regs, but the code
> that cc generates appears to only pass two doubles in regs. Likewise,
> are the FR's numbered the same? (The names were rather funky on hp-ux,
> due to legacy issues...)
Hmm, I wonder if you've found a gcc bug?
#if 1
#define FP float
#else
#define FP double
#endif
extern FP f1 (FP a);
extern FP f2 (FP a, FP b);
extern FP f3 (FP a, FP b, FP c);
extern FP f4 (FP a, FP b, FP c, FP d);
int main (void)
{
return f1 (1.) + f2 (1., 2.) + f3 (1., 2., 3.) + f4 (1., 2., 3., 4.);
}
With FP as float, I get fr4L, fr5L, fr6L, fr7L used in that order for
floating point args. With FP as double, I get fr5, fr7, stack args.
Weird, but then the pa ABI _is_ weird. I think you do need to check
that ABI document.
Alan
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: Alan Modra @ 2001-08-02 5:00 UTC (permalink / raw)
To: LaMont Jones; +Cc: parisc-linux
In-Reply-To: <20010802044401.89CE11872C@security.hp.com>
On Wed, Aug 01, 2001 at 10:44:00PM -0600, LaMont Jones wrote:
> > On Wed, Aug 01, 2001 at 10:04:34PM -0600, LaMont Jones wrote:
> > > I started to play with getting the hppa assembly code in guile-core to work
> > > on pa-linux, but ran into challenges with %farg[0-3], which aren't defined
> > > by the assembler...
> > So fix the assembler! gas/config/tc-hppa.c:pre_defined_registers
>
> Dunno which regs they are, and don't have a current runtime arch doc at
> home.
>
> How close is the calling convention between hp-ux and pa-linux?
Practically identical. farg0..3 is fr4..7 from memory, and I think they
are in that order. Test it out by writing a little C code, and
compiling with -S.
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: LaMont Jones @ 2001-08-02 4:49 UTC (permalink / raw)
To: LaMont Jones; +Cc: Alan Modra, parisc-linux, lamont
In-Reply-To: <20010802044401.89CE11872C@security.hp.com>
> > So fix the assembler! gas/config/tc-hppa.c:pre_defined_registers
> Dunno which regs they are, and don't have a current runtime arch doc at
> home.
This code seems to think that four args are passed in regs, but the code
that cc generates appears to only pass two doubles in regs. Likewise,
are the FR's numbered the same? (The names were rather funky on hp-ux,
due to legacy issues...)
lamont
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: LaMont Jones @ 2001-08-02 4:44 UTC (permalink / raw)
To: Alan Modra; +Cc: LaMont Jones, parisc-linux, lamont
In-Reply-To: <20010802140922.M5233@bubble.sa.bigpond.net.au>
> On Wed, Aug 01, 2001 at 10:04:34PM -0600, LaMont Jones wrote:
> > I started to play with getting the hppa assembly code in guile-core to work
> > on pa-linux, but ran into challenges with %farg[0-3], which aren't defined
> > by the assembler...
> So fix the assembler! gas/config/tc-hppa.c:pre_defined_registers
Dunno which regs they are, and don't have a current runtime arch doc at
home.
How close is the calling convention between hp-ux and pa-linux?
lamont
^ permalink raw reply
* Re: [parisc-linux] libqthreads and hppa-linux
From: Alan Modra @ 2001-08-02 4:39 UTC (permalink / raw)
To: LaMont Jones; +Cc: parisc-linux
In-Reply-To: <20010802040435.818241872C@security.hp.com>
On Wed, Aug 01, 2001 at 10:04:34PM -0600, LaMont Jones wrote:
> I started to play with getting the hppa assembly code in guile-core to work
> on pa-linux, but ran into challenges with %farg[0-3], which aren't defined
> by the assembler...
So fix the assembler! gas/config/tc-hppa.c:pre_defined_registers
^ permalink raw reply
* [parisc-linux] libqthreads and hppa-linux
From: LaMont Jones @ 2001-08-02 4:04 UTC (permalink / raw)
To: parisc-linux; +Cc: LaMont Jones
I started to play with getting the hppa assembly code in guile-core to work
on pa-linux, but ran into challenges with %farg[0-3], which aren't defined
by the assembler...
I'm about to upload a source NMU of guile-core, which has qt/md/hppa*-linux.?
in it. If someone wanted to take that the rest of the way, I'd be happy to
upload it...
lamont
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox