Re: Debian 4.0r3 for s/390, network install problem

[Jorge Ventura <jorge.ventura@fusemail.com>]

Yes,
I was excited in your first message because the image I was using was not the same from
the repository I was trying to install, but after get the right image, the problem persist
and I don't understand.

What I am doing is:
1. I did a download of ISO dvd-1 for Linux Debian/S390.
2. Prepare a local repository with this DVD. The idea with
    the local repository is to track the log in the Linux 390 and
    in the repository.
3. Configure the repository with Apache2 and sign Release file
    to have Release.gpg signed by me. This is necessary for network install.
4. Do IPL with the following parameters at hercules.cfg (I am using hercules-3.0.5):
     000C    3505    ./rdr/linux_vm ./rdr/parmfile ./rdr/root.bin autopad eof
   All files come from DVD.
5. Configure the network during the Linux 390 IPL until receive the following message:

Start SSH

To continue the installation, please use an SSH client to connect to the IP
address 192.168.2.5 and log in as the "installer" user.

The fingerprint of this SSH server's host key is:
2c:b3:d5:ef:ba:1d:46:6c:3b:1d:43:68:6e:73:3a:53

Please check this carefully against the fingerprint reported by your SSH
client.
 Press enter to continue!

6. I do ssh installer@192.168.2.10 and receive the terminal to
    continue the installation.
7. Go to shell and install my archive.gpg to force the installation
   accept my local repository. The repository is made using the
   DVD-1 for S390. I did this repository for i386 in the same way and works fine.

/usr/share/keyrings # rm archive.gpg
/usr/share/keyrings # wget http://192.168.2.103/debian-1/trustedkeys.gpg
Connecting to 192.168.2.103[192.168.2.103]:80
trustedkeys.gpg      100% |**************************************************************|  1176       00:00 ETA
/usr/share/keyrings # mv trustedkeys.gpg archive.gpg

8. Now, I am ready to continue the installation from "Star menu" and the system
    ask me for "[!] Choose a mirror of the Debian archive" and I answer
    "enter information manually" to 192.168.2.103.
   After this point, I get the following messages in the syslog of Linux 390:

Jun 29 20:38:20 choose-mirror[694]: DEBUG: command: wget -q http://192.168.2.103/debian-1//dists/etch/Release -O - | grep ^Suite: | cut -d' ' -f 2
Jun 29 20:38:20 choose-mirror[694]: DEBUG: command: wget -q http://192.168.2.103/debian-1//dists/stable/Release -O - | grep ^Codename: | cut -d' ' -f 2
Jun 29 20:38:20 choose-mirror[694]: INFO: codename set to: etch
Jun 29 20:38:20 choose-mirror[694]: DEBUG: command: wget -q http://192.168.2.103/debian-1//dists/stable/main/binary-s390/Release -O - | grep Architecture
Jun 29 20:38:20 anna-install: Queueing udeb etch-support for later installation
Jun 29 20:38:20 main-menu[644]: DEBUG: resolver (libc6): package doesn't exist (ignored)
Jun 29 20:38:21 main-menu[644]: INFO: Menu item 'download-installer' selected
Jun 29 20:38:22 net-retriever: gpgv: Signature made Sat Jun 28 12:15:43 2008 UTC using DSA key ID D6518C9D
Jun 29 20:38:26 net-retriever: gpgv:
Jun 29 20:38:26 net-retriever: Good signature from "Jorge Ventura (Ventura) <jorge.ventura@fusemail.com>"
Jun 29 20:38:26 net-retriever:
Jun 29 20:38:26 anna[739]: WARNING **: no packages for kernel in archive

The installation do not go ahead from this point and ask me for another repository.

I tried to install from a remote repository and it's worse, the installation stop without any
message.

I hope you can understand my problem.

Thank you for interest in help me,
Ventura

   




Frans Pop wrote:

On Sunday 29 June 2008, Ventura wrote:
  

I am trying to do a network install of Debian 4.0r3 and unfortunately
I am receiving a message about modules unavailable.
    

Can you please explain what the hell you're playing at?

You sent the same message to the Hercules mailing list and I replied to 
that with suggestions how to investigate and solve the problem.

Afterwards you (at least I assume it was you) sent me a private reply that 
that helped you solve the problem, but now you're sending the same 
message again to Debian mailing lists...

Not amused,
FJP