I am trying to IPL RHEL 3 Update 9 on a LPAR with one IFL, 3GB storage, 4* 
3390-3 DASD, OSA-Express card(one port - not shared with other LPARS).

This is what I am getting during the HMC install:


The first prompt is for the "kind of network device" I intend to use:  (ctc, 
escon, icuv, eth, his, tr)

I reply "eth0" here.

Then I reply to the qeth,addr1,addr2,addr3,0,0

It asks for the add_parms (and does not like it when I bypass it), so I reply 
it:

add_parms,0x10,addr1,addr3,portname:OSA3F00



Enter IP address of Linux quest

xxx.yyy.zzz.ppp



Enter network address of the new Linux quest

xxx.yyy.zzz.ppp



Enter the IP of your ctc/escon/iucv point-to-point partner:

??????????????????????????



It does not like if I just press enter - it needs something here.



Now, as you noticed, I specified eth0 , when the  expected entries were 
ctc,escon,icuv,eth



When I try it with "eth" (and not "eth0" like before), it gets further and ask 
the rest of the network parms, but it breaks with these messages:



/tmp/qeth.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including 
invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

SIOCSIFADDR: No such device

Qdio: loading QDIO base support version 2 ($Revision: 1.145.4.1 $/$Revision: 
1.5.7.4.1 $)

Qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.337.4.6 $/$Revision: 
1.113.4.2 $/$Revision: 1.42 $:VLAN)

qeth: allocated 0 spare buffers

eth0: unknown interface: No such device

SIOCSIFNETMASK: No such device

SIOCGIFADDR: No such device

SIOCSIFBROADCAST: No such device

SIOCSIFBRADDR: No such device

eth0: unknown interface: No such device



Enter your DNS servers

ddd.fff.org

Enter DNS search domains.

blah-blah-blah



lo                                            link encap: Local Loopback

                                                inet addr: 127.0.0.1  Mask: 
255.0.0.0

                                                UP LOOPBACK RUNNING   MTU:16436 
 Metric:1

                                                RX packets:0  errors:0  
dropped:0  overruns:0  frame:0

                                                TX packets:0  errors:0  
dropped:0  overruns:0  carrier:0

                                                collisions:0  txqueuelen:0

                                                RX bytes:0  (0.0 b)   TX 
bytes:0  (0.0 b)

Kernel IP routing table

Destination        Gateway              Genmask                             
Flags     Metrics  Ref  Use  Iface

127.0.0.1              0.0.0.0                   255.255.255.255                
UH          0              0        0        lo

Starting  portmap

Connect now to xxx.yyy.zzz.ppp to start the installation.

Journal Block Device driver loaded



I still cannot ping the network address.



So, I am not sure what is going on.

When I reply "eth", it responds that it cannot find the eth0 device and when I 
reply "eth0" it needs a point-to-point IP address.



What is the problem here, any ideas?




________________________________

GHC Confidentiality Statement

This message and any attached files might contain confidential information 
protected by federal and state law. The information is intended only for the 
use of the individual(s) or entities originally named as addressees. The 
improper disclosure of such information may be subject to civil or criminal 
penalties. If this message reached you in error, please contact the sender and 
destroy this message. Disclosing, copying, forwarding, or distributing the 
information by unauthorized individuals or entities is strictly prohibited by 
law.

----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to