This actually turned out to be related to my problem. Apparently, when you
use YaST2 to configure hipersockets, it touches everything it is supposed
to EXCEPT /etc/chandev.conf
As soon as I looked at that file on the working system, I saw entries in it
for the ethernet device ID's as well as the hipersocket ID's. Duplicating
that and adjusting the device numbers assigned to the particular guest
resolved the issue.
Thanks everyone.
I would never have remember chandev.conf by myself.
Elisabeth
Puritscher
<elisabeth.purits To
[EMAIL PROTECTED]> [EMAIL PROTECTED]
Sent by: Linux on cc
390 Port
<[EMAIL PROTECTED] Subject
IST.EDU> Re: Hipersockets weirdness
08/27/2004 03:22
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Sure - you can have hsi0 and eth0 at the same time - it is the same driver
but the adapters have different types. I have this on SLES8 and SLES9
systems.
Here examples for SLES8:
in /etc/chandev.conf specify:
#
noauto;qeth0,0xff00,0xff01,0xff02
noauto;qeth0,0x3100,0x3101,0x3102;add_parms,0x10,0x3100,0x3102,portname:GB3100
#
here the output of ifconfig:
ifconfig
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:10
inet addr:192.168.9.54 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::200:0:100:10/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:6033 errors:0 dropped:0 overruns:0 frame:0
TX packets:1042 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1201916 (1.1 Mb) TX bytes:177846 (173.6 Kb)
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.168.9.54 Bcast:10.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:598 errors:0 dropped:0 overruns:0 frame:0
TX packets:1042 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:81990 (80.0 Kb) TX bytes:112448 (109.8 Kb)
Interrupt:3
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1700 (1.6 Kb) TX bytes:1700 (1.6 Kb)
The problem seem to be the wrong deviceorder - you have to start with even
device addresses
read-write-data
even-odd-whatever (and write must be read+1)
Mit freundlichen Gr��en / Best Regards
Elisabeth Puritscher
Technical Marketing Competence Center & Linux CoC
Schoenaicherstr.220, D 71032 Boeblingen, Germany
Phone: +49-7031-16-3718
Fax: +49-7031-16-3232
Internet: [EMAIL PROTECTED]
----------------------------------------------------------------------
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
