Comments on: Hercules and Slackware (slack/390) – Part 5

By: Niels Horn

Niels Horn — Wed, 09 Feb 2011 17:28:48 +0000

Hi,

Good you got it to work

I have the same collection: Slackware64 / ARMedslack (SheevaPlug + Qemu) / Slack/390 (Hercules) !

Niels

By: BgEddy

BgEddy — Wed, 09 Feb 2011 14:58:34 +0000

Hi Neil – I’m sorry for cluttering up the blog with my comments but just to let you know – I have installed Hebe and now I an running the install in that and everything seems to work. Not sure what I was doing wrong before but now all seems good – the install is running now. So I now have ArmedSlack running in Qemu and soon hopefully will have Slack/390 under Hercules – very cool Slackware overdose! Thanks again for the help.
BgEddy

By: BgEddy

BgEddy — Wed, 09 Feb 2011 12:59:29 +0000

Yes – I have setup hercules.cnf currently contains this :
———————————————————————————————-
MAINSIZE 256
NUMCPU 1
OSTAILOR LINUX
PANRATE SLOW
ARCHMODE ESA/390

# reader
000C 3505 ./rdr/vminstall.image-2.4.26.gcc-3.3.4.img ./rdr/parmfile.txt ./rdr/initrd.gz autopad eof

# dasd
0120 3390 ./dasd/3390.SLACK.0120
0121 3390 ./dasd/3390.SLACK.0121

# network
0F00,0F01 LCS -n /dev/net/tun 192.168.1.162
———————————————————————————————-
and just for completeness – here’s my rdr/parmfile.txt
———————————————————————————————-
ramdisk_size=22528 root=/dev/ram0 ro ip=off
DASD=120-121
HOST=herc-slack.hn:eth0:192.168.1.162:1500
NETWORK=192.168.1.0:255.255.255.0:192.168.1.255:192.168.1.1
DNS=192.168.1.1
SEARCHDNS=hn
LCS=0xf00,1
CHANDEV=noauto;lcs0,0xf00,0xf01
QETHPARM=add_parms,0×04,0xf00,0xf01
———————————————————————————————-

I’m really glad you keep up with the comments here – thanks for the reply.

By: Niels Horn

Niels Horn — Tue, 08 Feb 2011 23:21:49 +0000

Hi,

Yes, I still read these comments
Did you setup the hercules.cnf file with the network adapters?
With the right hercules configuration and the steps Robert mentioned it really should “just work”…

Niels

By: BgEddy

BgEddy — Tue, 08 Feb 2011 20:32:16 +0000

Hey Niels. Great blog BTW. I have managed to get Slackware S390 working once before under Hercules but I'm trying it again and are having head scratching problems. I have tried the extra steps mentioned by Robert above but still no joy - I am forever getting networking problems when the install tests the IP addresses like this : Pinging the eth0 interface PING 192.168.1.162 (192.168.1.162): 56 data bytes 64 bytes from 192.168.1.162: icmp_seq=0 ttl=64 time=2.7 ms 64 bytes from 192.168.1.162: icmp_seq=1 ttl=64 time=0.3 ms 64 bytes from 192.168.1.162: icmp_seq=2 ttl=64 time=0.6 ms --- 192.168.1.162 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.3/1.2/2.7 ms Pinging the gateway PING 192.168.1.1 (192.168.1.1): 56 data bytes ping: sendto: Network is unreachable Pinging the DNS server(s) PING 192.168.1.1 (192.168.1.1): 56 data bytes ping: sendto: Network is unreachable I cannot ping all the interfaces needed to make this work. Correct the problem and try again. root@herc-slack:/# Any tips are much appreciated (if you still check your comments here that is). Cheers, BgEddy

By: holson

holson — Mon, 03 Aug 2009 15:45:39 +0000

You're right about these extra steps. Since I use this box for various other virtual machines (w/ qemu), I had already setup ip forwarding.
Thanks for the reminder!

By: robert

robert — Mon, 03 Aug 2009 14:48:42 +0000

First off, Phenomenal walkthrough!!!
One comment on this page: using the LCS vs. CTCI adapter, I had to manually "type up" the ethernet adapter tap0 on the Host immediately after seeing the "Starting the Slack/390 networking" message. (ifconfig eth0 20.0.0.1 netmask 255.255.255.0 up), otherwise the the host side connector would never come up.
I also had to enable ip-forwarding: "echo 1 > /proc/sys/net/ipv4/ip_forward", and I setup nat: "iptables -t nat -A POSTROUTING -j MASQUERADE", in order to get the slack-390 to finish it's network testing.