https://bugzilla.novell.com/show_bug.cgi?id=394602 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=394602#c1 Summary: Installed Power 6 LPAR-ehea(Network driver) not detected by Yast-installer of Opensuse-11-Beta3-ppc64. Product: openSUSE 11.0 Version: Beta 2 Platform: PowerPC-64 OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugproxy@us.ibm.com QAContact: jsrain@novell.com Found By: Third Party Developer/Partner Partner ID: LTC 44938 Problem description: ==================== When tried to install Power-6 lpar, i found the installer already installed ehea - power6 network driver. But installer unable to use the driver to do NFS installation. Following is the error message received: -----------------------------Installation Log-----------------------------------

...

...

openSUSE installation program v3.1.28 (c) 1996-2008 SUSE Linux Products GmbH <<<

Starting udev... ok Loading basic drivers... ok Starting hardware detection... ok (If a driver is not working for you, try booting with brokenmodules=driver_name.) IBM Virtual SCSI 0 drivers: ibmvscsic loading ibmvscsic PORT - 2 IBM Host Ethernet Adapter drivers: ehea loading ehea No new driver updates found. *** Could not find the openSUSE Repository. Activating manual setup program.

...

...

Linuxrc v3.1.28 (Kernel 2.6.25.3-2-ppc64) <<<

Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off

3

Kernel Modules (Hardware Drivers) 1) Load ppc Modules 2) Load USB Modules 3) Load FireWire Modules 4) Load File System Modules 5) Load Unknown Modules 6) Show Loaded Modules 7) Unload Modules 8) Add Driver Update 9) Show Driver Updates

1

Load ppc Modules 1) pcnet32 : AMD PCI PCnet32 (PCI bus NE2100) 2) acenic : Alteon AceNIC/3C985/NetGear GA620 3) amd8111e : AMD8111 970eval 4) e100 : Intel PRO/100 / EtherExpr. PRO/100 5) e1000 : Intel PRO/1000 6) e1000e : Intel PRO/1000 PCI-E Gigabit 7) ixgb : Intel(R) PRO/10GbE 8) igb : Intel Gigabit Ethernet 9) ixgbe : Intel(R) 10 Gigabit PCI Express 10) bnx2 : Broadcom NetXtreme II BCM5706 11) bnx2x : Broadcom NetXtreme II BCM57710 12) tg3 : Broadcom Tigon3 Ethernet 13) olympic : IBM Olympic chipset PCI Token Ring 14) ibmveth : POWER5 Virtual Ethernet 15) spidernet : Cell Ethernet 16) s2io : S2IO 10GbE Server 17) ehea : POWER6 ehea 18) qla3xxx : QLogic ISP3XXX 19) netxen_nic : NetXen Multi port (1/10) Gigabit 20) sungem : Sun GEM, for new PowerMacs 21) tulip : DEC Tulip (DC21x4x) PCI 22) libphy : PHY library 23) iseries_veth : iSeries virtual ethernet 24) ps3_gelic : PS3 gelic ethernet 25) ps3rom : PS3 CDROM 26) ps3disk : PS3 disk storage 27) ps3vram : PS3 swap into videoram 28) mtd : mtd 29) mtd_blkdevs : mtd_blkdevs 30) mtdblock : mtdblock 31) pata_amd : AMD PATA JS20 32) pata_pdc2027x : Promise PDC20268 to PDC20277 33) pata_sil680 : SI680 PATA QS20 34) pata_sl82c105 : W82C105 PATA IDE 35) ahci : AHCI SATA driver 36) sata_sil24 : Silicon Image 3124/3132 SATA 37) sym53c8xx : Symbios 53c8xx 38) ipr : IBM Power Linux RAID adapter 39) ibmvscsic : IBM Virtual SCSI 40) lpfc : Emulex LP fibrechannel storage 41) qla4xxx : QLogic ISP 4XXX iSCSI 42) mptsas : Fusion MPT SAS Host driver 43) sata_svw : PowerMac K2 SATA 44) viodasd : legacy iSeries vio dasd 45) viocd : legacy iSeries vio cd 46) ide-cd_mod : ATAPI CD-ROM Driver 47) st : SCSI Tape Driver 48) sd_mod : SCSI Disk Driver 49) sr_mod : SCSI CD-ROM driver 50) scsi_debug : Simulate a host adapter 51) iscsi_tcp : iSCSI/TCP data-path 52) libiscsi : iSCSI library functions 53) scsi_wait_scan : wait for SCSI scan to complete

17

Module "ehea" has already been loaded. Kernel Modules (Hardware Drivers) 1) Load ppc Modules 2) Load USB Modules 3) Load FireWire Modules 4) Load File System Modules 5) Load Unknown Modules 6) Show Loaded Modules 7) Unload Modules 8) Add Driver Update 9) Show Driver Updates

^[

Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off

4

Start Installation or System 1) Start Installation or Update 2) Boot Installed System 3) Start Rescue System

1

Choose the source medium. 1) CD-ROM 2) Network 3) Hard Disk

2

Choose the network protocol. 1) FTP 2) HTTP 3) NFS 4) SMB / CIFS (Windows Share) 5) TFTP

3 Detecting and loading network drivers

*** No network device found. Load a network module first. ------------------------------------------------------------------------------- Hardware Environment: ===================== Cpu type (Power4, Power5, IA-64, etc.):Power6 ------------------------------------------------------------------------------- Reproducible: ============= Is this reproducible? Yes Describe the steps: -> Start Opensuse-11-Beta3 with nfs installation method -> Check whether ehea-power6 network driver is installed -> Proceed to use NFS method of installation (You will get the above error message that network driver is not loaded) =Comment: #1================================================= Anoop V. Chakkalakkal - 2008-05-21 08:07 EDT The discussion http://thread.gmane.org/gmane.linux.suse.ppc/1316/focus=1317 seems related. ..

As you see below, the port0 and port1 directories/symlinks are created _after_ ehea is loaded. But thats too late, the bus devices have to be there before any device driver is loaded. Thats how it is done for other bus types. Once that is implemented properly, stuff like ehea or infiniband will (most likely) work out of the box. ..

Adding eHEA guys .. Jan-Bernd/Stefan, Can any of you please take a look? =Comment: #2================================================= Jan-Bernd Themann - 2008-05-21 09:09 EDT Hi, eHEA is no PCI device. In order to detect that an eHEA port is available before the eHEA kernel module is loaded you have to scan the Open Firmware Device Tree (/dev/device-tree). There each eHEA adapter is represented as a directory starting with "lhea". Each port is then represented as a sub directory. We are not familiar how Yast works at this point, so it would be good to have someone from Novell take a look. They already solved the problem for SLES10SP2. If more information concerning the eHEA driver are required feel free to ask. Regards, Jan-Bernd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.