>>> On Fri, Apr 6, 2007 at 4:17 PM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: -snip- > The only messages are the qdio and qeth driver version messages, I'll > copy them below (anyone know how to copy text out of the java System > Messages applet from the HMC? I've tried a bunch of things with no > luck...). > qdio: loading QDIO base support version 2 ($Revision: 1.86 $/$Revision: > 1.57: 1.57 $/$Revision 1.26 $) > > and > > qeth: loading qeth S/390 OSA- Express driver
If the driver had detected anything, you would have seen a whole lot more than that. This is what I get for my virtual HiperSocket LAN NIC: qeth: Device 0.0.4000/0.0.4001/0.0.4002 is a Guest LAN Hiper card (level: V524) with link type GuestLAN Hiper (no portname needed by interface). qeth: set adapter parameters not supported on device 0.0.4000. qeth: Hardware IP fragmentation not supported on hsi0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPv6 not supported on hsi0 qeth: Broadcast enabled qeth: Using SW checksumming on hsi0. qeth: Outbound TSO not supported on hsi0 If you can, I would try re-IPLing the starter system, and not letting the script do any network setup. Then, do a modprobe qdio and modprobe qeth (or whatever you have to do to get the modules loaded, I'm not familiar with the CentOS 4.4 kernel module layout). Without any parameters, the driver should auto-detect _all_ QDIO capable devices. If it doesn't find any, you probably don't have any defined for that LPAR. Again, dmesg will show you what, if anything, the driver finds. Mark Post ---------------------------------------------------------------------- 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
