I've tried defining it as hsi1, that doesnt't seem to work either.
Here's the OSA definitions:
cp q osa
OSA 0880 ATTACHED TO TCPIP 0880
OSA 0881 ATTACHED TO TCPIP 0881 <--- GB Ethernet adapter
OSA 0882 ATTACHED TO TCPIP 0882
OSA 0ED0 ATTACHED TO TCPIP 0ED0
OSA 0ED1 ATTACHED TO TCPIP 0ED1 <--- Hipersocket device owned by VM
itself (so they tell me)
OSA 0ED2 ATTACHED TO TCPIP 0ED2
OSA 0ED3 ATTACHED TO CALHOUN 0ED3
OSA 0ED4 ATTACHED TO CALHOUN 0ED4 <---- Doesn't work/Won't initialize
OSA 0ED5 ATTACHED TO CALHOUN 0ED5
OSA 0ED6 ATTACHED TO ITASCA 0ED6
OSA 0ED7 ATTACHED TO ITASCA 0ED7 <--- Works. Interface comes up
OSA 0ED8 ATTACHED TO ITASCA 0ED8
OSA 0ED9 ATTACHED TO PEPIN 0ED9
OSA 0EDA ATTACHED TO PEPIN 0EDA <--- Works. Interface comes up
OSA 0EDB ATTACHED TO PEPIN 0EDB
OSA 0EDC ATTACHED TO PHALEN 0EDC
OSA 0EDD ATTACHED TO PHALEN 0EDD <---- have not attempted to configure
OSA 0EDE ATTACHED TO PHALEN 0EDE
A little more about this: Calhoun, Itasca and Pepin (Minnesota lakes, BTW)
were the original 3 defined. Phalen, was added to the range of devices
recently. Calhoun was 'burned down' and re-built with more dasd, but the
device definitions were the same.
Boot produces this message at IPL
hsi0 ifup: Could not get a valid interface name: -> skipped
I also see this message several times, throughout the day.
Aug 27 09:00:00 calhoun modprobe: modprobe: Can't locate module
char-major-10-224
Robert J
Brenneman
<[EMAIL PROTECTED] To
om> [EMAIL PROTECTED]
Sent by: Linux on cc
390 Port
<[EMAIL PROTECTED] Subject
IST.EDU> Re: Hipersockets weirdness
08/26/2004 01:55
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Try hsi1 - since hipersockets and osa-express use the same driver, it
appears as another instance of the same type of device.
It could also be that youre starting the address sequence on an odd
number, try devices 0ED4-ED6
Jay Brenneman
Linux Test and Integration Center
T/L: 295 - 7745
Extern: 845 - 435 - 7745
[EMAIL PROTECTED]
Linux on 390 Port <[EMAIL PROTECTED]> wrote on 08/26/2004 02:29:57
PM:
> I thought I Had this down, but apparently not.....
>
> I built a new Linux guest and I'm trying to get the thing to talk to a
> hipersocket.
>
> The devices 0ED3,0ED4,0ED5 , show up in /proc/chandev and
/proc/subchannels
>
>
> The Chandev entries:
>
> Initialised Devices
> read write data read write data chan port dev dev
> memory read msck write msck data msck
> irq irq irq devno devno devno type no. ptr name
> usage(k) status status status
>
=====================================================================================================================
> 0x0003 0x0004 0x0005 0x9000 0x9001 0x9002 0x10 0 0x02022800 eth0
> 8192 good good good
>
> Total device memory usage 8192k.
>
> channels detected
> chan cu cu dev dev in
> chandev
> irq devno type type model type model pim chpids use
> reg.
>
===============================================================================
> 0x0000 0x0ed3 0x10 0x1731 0x05 0x1732 0x05 0x80 0xed00000000000000 no
> no
> 0x0001 0x0ed4 0x10 0x1731 0x05 0x1732 0x05 0x80 0xed00000000000000 no
> no
> 0x0002 0x0ed5 0x10 0x1731 0x05 0x1732 0x05 0x80 0xed00000000000000 no
> no
> 0x0003 0x9000 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0100000000000000 yes
> yes
> 0x0004 0x9001 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0100000000000000 yes
> yes
> 0x0005 0x9002 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0100000000000000 yes
> yes
>
>
> The Subchannels entries
>
> calhoun:/etc/sysconfig/network # cat /proc/subchannels
> Device sch. Dev Type/Model CU in use PIM PAM POM CHPIDs
> ---------------------------------------------------------------------
> 0ED3 0000 1732/05 1731/05 80 80 FF ED000000 00000000
> 0ED4 0001 1732/05 1731/05 80 80 FF ED000000 00000000
> 0ED5 0002 1732/05 1731/05 80 80 FF ED000000 00000000
>
> The entry in /etc/sysconfig/network for hsi0 (ifcfg-hsi0)
>
> indicates:
>
> calhoun:/etc/sysconfig/network # cat ifcfg-hsi0
> BOOTPROTO='static'
> BROADCAST='192.168.252.255'
> DATA_CHANNEL=''
> IPADDR='192.168.252.14'
> NETMASK='255.255.255.0'
> NETWORK='192.168.252.0'
> PORTNAME=''
> READ_CHANNEL=''
> REMOTE_IPADDR=''
> STARTMODE='onboot'
> UNIQUE=''
> WIRELESS='no'
> WRITE_CHANNEL=''
>
>
>
> The only difference I can see betweent the two guest is that one has the
> hipersocket devices on the 'working' sytem initialized.
>
> Should I suspect a VM configuration problem? Any ideas welcome
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
