From: Albert Strasheim <fullung@ilink.nis.za>
To: Joerg Hartmann <j.hartmann@reinarts.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] init error on a 720
Date: Mon, 3 Dec 2001 19:26:07 +0200 [thread overview]
Message-ID: <20011203192606.A499@dogbert.localdomain> (raw)
In-Reply-To: <200112030820.JAA20988@post.webmailer.de>
[-- Attachment #1: Type: text/plain, Size: 4816 bytes --]
Hello Joerg,
I got my 720/50 up and running with 2.4.9-pa70 or thereabouts.
2.4.14-pa2 also worked fine. Haven't had time to test the newest kernel
yet. I suggest you check the parisc-linux archives. I was quite verbal
in my quest to get my 720/50 going. :-)
Basically, I did the following:
1. Enable the serial console
2. Create a new nfsroot by hacking the debootstrap scripts on my i386. I
had to use some special debs here, but I believe they are now in
unstable.
3. Cross-compile the latest kernel using xc-latest, and make a lifimage
with palo.
4. Netboot the lifimage with bootpd/rbootd and mount the nfsroot created
in step 2 read-write.
5. fdisk and mke2fs the partitions (remember the partition for palo!) I
wanted to install on.
6. Manually walk through the debootstrap and install all the packages I
required on the new mounted partition (you use a chroot sometimes).
7. Install palo.
8. Reboot. apt-get update. apt-get upgrade.
Or you could just wait for the 0.9.3 ISO which is out/will be out
shortly.
Regards,
Albert
On Mon, 03 Dec 2001, Joerg Hartmann wrote:
> Hello Guru's,
>
> as you guess, i like to install Linux on a HP Workstation.
> It is an hp9000 model 720.
> And here the problem starts - on some websites is stated that pa-risc
> linux will never work on 720's on some other sites i can read it does !
> Maybe it depends - but on what ?
>
> So i took the 0.9.2 iso-image from www.parisc-linux.org and tried an
> installation. After switching to serial console i could see the kernel
> coming up until it has to start "init" - than it loops forever with
>
> handle_interruption() pid=1 command='init'
>
> On the list archive i found, that some other people had the same problem,
> even with 720 models. But i could not find a solution which works for me.
> If there is one , could you please tell me where to RTFM ?
>
> Here are some hardware infos :
>
> Found devices:
> 1. Coral SGC Graphics (10) at 0xf8000000, versions 0x4, 0x0, 0x77, 0x0,
> 0x0
> 2. Cobra Core BA (11) at 0xf082f000, versions 0x4, 0x0, 0x70, 0x0, 0x0
> 3. Cobra Core SCSI (10) at 0xf0825000, versions 0x4, 0x0, 0x71, 0x0, 0x0
> 4. Cobra Core LAN (802.3) (10) at 0xf0826000, versions 0x4, 0x0, 0x72,
> 0x0, 0x0
> 5. Cobra Core HIL (10) at 0xf0821000, versions 0x4, 0x0, 0x73, 0x0, 0x0
> 6. Cobra Core RS-232 (10) at 0xf0823000, versions 0x4, 0x0, 0x75, 0x0, 0x0
> 7. Cobra Core RS-232 (10) at 0xf0822000, versions 0x4, 0x0, 0x75, 0x0, 0x0
> 8. Cobra Core Centronics (10) at 0xf0824000, versions 0x4, 0x0, 0x74,
> 0x0, 0x0
> 9. Cobra (720) (0) at 0xfffbe000, versions 0x200, 0x0, 0x4, 0x0, 0x81
> 10. Cobra (1) at 0xfffbf000, versions 0x13, 0x0, 0x9, 0x0, 0x0
> That's a total of 10 devices.
> CPU(s): 1 x PA7000 (PCX-S) at 50.000000 MHz
>
> And there is a second problem with the scsi bus :
>
> sim700: Configuring 53c700 (SCSI-ID 7) at f0825100, IRQ 86, options 1
> scsi0: Revision 0x0
> scsi0: test 1 completed ok.
> scsi0 : LASI/Simple 53c7xx
> scsi0: Unable to abort command for target 0
> scsi0: Unable to send Bus Device Reset for target 0
> scsi0: Unable to do SCSI bus reset
> scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> scsi0: istat = 0c, sstat0 = 00, sstat1 = 00, dstat = 00
> scsi0: dsp = 0b8f8058 (script[0x0016]), dsps = 0b8f8cee, target = 0
> scsi0: Failing command for ID0
> scsi0: Unable to abort command for target 0
> scsi0: Unable to abort command for target 1
> scsi0: Unable to send Bus Device Reset for target 1
> scsi0: Unable to do SCSI bus reset
> scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> scsi0: istat = 0c, sstat0 = 00, sstat1 = 00, dstat = 00
> scsi0: dsp = 0b8f8058 (script[0x0016]), dsps = 0b8f8cee, target = 0
> scsi0: Failing command for ID0
> Vendor: IBM Model: CDRM00203 !K Rev: BZ33
> Type: CD-ROM ANSI SCSI revision: 02
> Vendor: HP Model: HP35480A Rev: TI00
> Type: Sequential-Access ANSI SCSI revision: 02
> Vendor: HP Model: 97560 Rev: 0BW2
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 5, lun 0
> SCSI device sda: 2647080 512-byte hdwr sectors (1355 MB)
> Partition check:
> sda: unknown partition table
>
> I realy hope you can point me to the right direction.
> If i can not get linux up and running on that box, this computer will be
> put in the waste basket :-(
>
> regards
> Jörg Hartmann
> --
> Joerg Hartmann
> j.hartmann@reinarts.de
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-12-03 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 8:24 [parisc-linux] init error on a 720 Joerg Hartmann
2001-12-03 11:21 ` Thomas Marteau
2001-12-03 17:26 ` Albert Strasheim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011203192606.A499@dogbert.localdomain \
--to=fullung@ilink.nis.za \
--cc=j.hartmann@reinarts.de \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox