I'm trying to get Fedora 25 installed on the Hercules v3.12, but the install fails because it can't connect to the network and drops into a dracut emergency shell. In the emergency shell if I assign an ip to the dev and set a default route then I can successfully ping other hosts. So in that respect it doesn't seem like a Hercules problem at all but I thought I'd ask here in the event some one has encountered/fixed this issue.
Hercules is configured with CTC networking
0700.2 CTCI -n /dev/net/tun -t 1500 192.168.1.171 192.168.1.170
I'm using a prm file (see below) to supply the ip option, but while its processed (based on errors I see when I muck it up), networking isn't configured properly. During the install I see the CTC driver is initialized, ctc0 is detected and then renamed to slc700, and that slc700 is connected with the remote side.
Any advice/pointers would be appreciated.
Earlier this week, after a couple of days trying, I successfully installed Fedora 25 under Hercules, though I'm using 4.0, not 3.12.
It appears that CTC's don't start correctly in Fedora 25. I was only successful with the install after I had removed anything to do with CTC, and used only LCS. Once I had a running F25 I tried to setup a CTC, but, after IPL'ing, I have to logon and do an ifup of the CTC device. The CTC device exists in the F25 system, it just doesn't have an IP address or MTU value. Your comment about having to "assign an ip to the dev" sounds like the same problem.
One other thing, F25 issued a disk i/o request that wasn't supported by 4.0, and I don't imagine is supported by 3.12. As 4.0 didn't support the request, it returned a channel program check, which stopped the install. I had to change 4.0 to add the support for the i/o request, after which things proceeded smoothly. The change has been committed to the 4.0 repository on Github.
In reply to this post by Hercules390 - General mailing list
Ian Shorter wrote:
> One other thing, F25 issued a disk i/o request that wasn't
> supported by 4.0, and I don't imagine is supported by 3.12.
> As 4.0 didn't support the request, it returned a channel
> program check, which stopped the install. I had to change
> 4.0 to add the support for the i/o request, after which
> things proceeded smoothly.
<separated for emphasis>
> The change has been committed to the 4.0 repository on Github.
Thank you, Ian.
Your change has now also been committed to my unofficial Hyperion 4.0 fork as well.
I'll be building a new set of Windows snapshots within the next few days once I apply Bob Polmanter's final set of ECPS VM Assist changes.