qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HPPA support for IGNITE-UX install discs


From: Helge Deller
Subject: Re: HPPA support for IGNITE-UX install discs
Date: Mon, 21 Sep 2020 16:46:48 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0

On 21.09.20 05:41, Philippe Mathieu-Daudé wrote:
> Cc'ing the HPPA team.

CC'ing parisc linux development list.

> On 9/20/20 9:42 PM, Keith Monahan via wrote:
>> HI there,
>>
>> In QEMU 5.1.50 (also tried 4.2.1) built from source, I have a particular
>> IGNITE-UX disk associated with an HP Logic Analyzer 16700A that I'm
>> trying to boot and install. It's based on HP-UX 10.20. The regular LA
>> hardware shows up via uname as "HP-UX no_hostn B.10.20 C 9000/779
>> 2008038539 32-user license" I've seen reference to 9000/779/rock. This
>> should be fairly similar to the B132L/B160L.

The 9000/779 seems to be like an RDI PrecisionBook:
https://www.openpa.net/systems/rdi_precisionbook.html
which is quite similiar to a B160L.

There is even an entry for your logic analyzer:
https://www.openpa.net/systems/hp_16600_16700_logic_agilent.html

>> While SeaBIOS identifies the attached virtual drive, and the specified
>> CDROM boots, the install init script fails to find any IO devices, and
>> so no installation can occur.
>>
>> Other HP-UX 10.20 Ignite-UX disks work without issue in the same qemu
>> environment with the same command line options.
>>
>> A successful run has the "Scanning system for IO devices..." take a few
>> seconds, followed by a "Querying disk device" message for each of the
>> devices it sees. That whole process takes 30 seconds or so in emulation.
>>
>> A bad run immediately goes from "Scanning system..." to "There were no
>> disk devices found during the scan."
>>
>> I have noticed that the "install/init" Revision on one that works is a
>> 10.3, but the failing one is 10.124. Not sure if this telltale or not.
>>
>> Anyone super familiar with this type of install disk? Or how the boot
>> process works with HP-UX CDs in general? What gets loaded first? How can
>> I find this script and/or executable that's evaluating the readiness of
>> the drives? My thoughts are that I could "update" via editing the ISO,
>> which both mount easily in Linux.

In qemu the B160L emulation isn't complete yet.
The SCSI disc is emulated by a "virtual built-in" PCI SCSI card, while
the original B160L has a NCR 53C710 SCSI chip internal in the LASI controller.
Additionally the LASI emulation isn't complete either.
My assumption is, that your Install CD for the analyzer will only detect
real LASI/53C710 chips and ignore the virtual PCI card. That's why it doesn't
detect any discs.

>> But I'm open to thoughts, including redirection to a different more
>> appropriate mailing list! :)
>>
>> Thanks for any general advice.
>> Keith
>>
>>
>> I'm invoking like this:
>>
>> ./qemu-system-hppa -boot d -serial mon:stdio -drive
>> if=scsi,bus=0,index=6,file=./hpux.img,format=raw -D /tmp/foo -nographic
>> -m 512 -d nochain -cdrom ./HP16700_cdrom.iso -net nic,model=tulip  -net tap

You could drop the "nochain", it slows things down.
Without "nographic" the STI framebuffer might work.

>> and see this:
>>
>>   Primary boot path:    FWSCSI.6.0
>>   Alternate boot path:  FWSCSI.2.0

both are on the virtual PCI card...

>>   Console path:         SERIAL_1.9600.8.none
>>   Keyboard path:        PS2
>>
>> Available boot devices:
>> 1. DVD/CD [lsi 00:00.0 2:0 Drive QEMU QEMU CD-ROM 2.5+]
>> 2. lsi 00:00.0 6:0 Drive QEMU QEMU HARDDISK 2.5+
>>
>> Booting from DVD/CD [lsi 00:00.0 2:0 Drive QEMU QEMU CD-ROM 2.5+]
>>
>> Booting...
>> Boot IO Dependent Code (IODC) revision 153
>>
>> HARD Booted.
>>
>> ISL Revision A.00.38  OCT 26, 1994
>>
>> ISL booting  hpux (;0):INSTALL
>>
>> Boot
>> : disc(8/0/0/0.2.0;0):INSTALL
>> 4999156 + 446464 + 361504 start 0x184268
>> No BTLB entries found for processor 0
>> vuseg=1a5a000
>>
>>     System Console is on the Built-In Serial Interface
>> Networking memory for fragment reassembly is restricted to 49061888 bytes
>>     Swap device table:  (start & size given in 512-byte blocks)
>>         entry 0 - auto-configured on root device; ignored - no room
>> WARNING: No dump device configured.  Dump is disabled.
>> Starting the STREAMS daemons.
>>     9245XB HP-UX (B.10.20) #1: Sun Jun  9 06:31:19 PDT 1996
>>
>> Memory Information:
>>     physical page size = 4096 bytes, logical page size = 4096 bytes
>>     Physical: 524288 Kbytes, lockable: 404768 Kbytes, available: 465588
>> Kbytes
>>
>> =======  09/19/20 16:01:14 EDT  HP-UX Installation Initialization. (Sat
>> Sep 19
>>          16:01:14 EDT 2020)
>>          @(#) Ignite-UX Revision 1.32
>>          @(#) install/init (opt) $Revision: 10.124 $
>>        * EISA configuration has completed.  Following the completion of a
>>          successful HP-UX installation, please check the
>> "/etc/eisa/config.err"
>>          file for any EISA configuration messages.
>>        * Scanning system for IO devices...
>> NOTE:    There were no disk devices found during the scan.  Make sure
>> that the
>>          destination disks are connected and powered on.  You may choose to
>>          scan for more disk drives from next menu on the console.
>> WARNING: Could not verify access to LAN interface: 8/0/1/0
>> ERROR:   could not find source device 8/0/0/0 in ioscan output

That's strange.... I think 8/... might be LASI.

>> Would you like to switch source to network? (y/[n]): y
>>
>>
>> Hardware Summary:         System Model: 9000/778/B160L
>>   +---------------------+----------------+-------------------+ [ Scan
>> Again  ]
>>   | Disks: 0  (  0.0GB) |  Floppies: 0   | LAN cards:   1    |
>>   | CDs:   0            |  Tapes:    0   | Memory:    512Mb  |
>>   | Graphics Ports: 0   |  IO Buses: 1   |                   | [ H/W
>> Details ]
>>   +---------------------+----------------+-------------------+

I'm not an HP-UX expert.
Maybe it's possible to install HP-UX from another install CD and
install the Analyzer packages afterwards?

Helge



reply via email to

[Prev in Thread] Current Thread [Next in Thread]