Hello, I'm seeing the same problem. With the pre 2.4.7 kernel betas I had no trouble. However, once I tried the 2.4.7 kernel I noticed a problem, and once the 2.4.9 installer came out I saw the problem I was seeing with the 2.4.7 kernel in the installer. I hope that the following information is some use. The device isn't being shown at startup, however /proc/chandev is showing the device: 0x10 0x1731 0x05 0x1732 0x05 0 no no not_operational,no_path,revalidate,device_gone 0x10 0x1731 0x01 0x1732 0x01 0 no no not_operational,no_path,revalidate,device_gone and irq devno type type model type model pim chpids use reg. ====================================================================== ========= 0x0000 0x0e00 0x10 0x1731 0x01 0x1732 0x01 0x80 0xfaffffffffffffff no no 0x0001 0x0e01 0x10 0x1731 0x01 0x1732 0x01 0x80 0xfaffffffffffffff no no 0x0002 0x0e02 0x10 0x1731 0x01 0x1732 0x01 0x80 0xfaffffffffffffff no no when I try to insmod the drivers: # insmod -f /lib/qdio.o # insmod -f /lib/qeth.0 # # cat /proc/modules # So.. the insmod returns no errors, and the module doesn't load. I have a feeling I'm probably missing something, but I'm confused as to what it is. Thanks for any input and assistance. -Ryan On Wed, 17 Oct 2001, Post, Mark K wrote: > Albert, > > I'll echo here what I said to Greg Smith in the Linux-390 mailing list: > - - - - - > Make sure that the device is being detected during IPL. You should see > something like this: > Detected device 2928 on subchannel 0000 -PIM =80,PAM =80,POM =FF > but with f830, etc. > > Also, I'll tell you what I tell everyone... Since the scripts hide any > error messages that come back from the "insmod -f" command, try issuing it > yourself manually. In your case that would be: > insmod -f lcs-2.4.7-s390-2.o devno_portno_pairs=0xf830,2 > - - - - - > > Substitute your values for the module name and device number, and report > back what you see. > > Mark Pot > > -----Original Message----- > >From: Albert S Delaney [mailto:delaney@lsu.edu] > Sent: Wednesday, October 17, 2001 4:39 PM > To: redhat-s390-list@redhat.com > Subject: [Redhat-s390-list] OSA-Express not recognized with Beta kernel > of Oct 4,2001 and IBM OCO modules > > > We're trying to install the S/390 Linux beta iso images dated Oct 4 from > Red Hat's ftp site in an LPAR on a 9672-R35. We're able to IPL the first > CD from the hardware management console and go through the dialog just > fine. We're specifying the LCS driver so we can access our OSA-Express > interface (emulated ethernet) using its device number and the appropriate > IP address, netmask, broadcast, network, and gateway values. > > We then get errors stating the device is not found: > > SIOCSIFADDR: No Such Device > eth0: unknown interface: No Such Device > SIOCSIFNETMASK: No Such Device > SIOCSIFBRDADDR: No Such Device > eth0: unknown interface: No Such Device > SIOCADDRT: No Such Device > SIOCADDRT: No Such Device > > We're sure our values are correct since they work just fine when going > through the SuSE install using the same values. > > We included the latest IBM OCO modules for LCS and QDIO/QETH into the > initrd and tapeinrd images per the docs and in fact can see them just fine > when we finally get to the "#" prompt. We've also tried manually loading > the modules with insmod. Either way an ifconfig only shows the lo device. > Eth0 doesn't exist. Same symptoms if we try the QDIO/QETH modules with our > gigabit interface (which also works with our SuSE installation). > > I guess my question is whether anyone has used an OSA-Express card (or > gigabit for that matter) successfully with the beta images. Any > suggestions/comments/hurled stones are welcome. > > Al Delaney > > > _______________________________________________ > Redhat-s390-list mailing list > Redhat-s390-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-s390-list > > _______________________________________________ > Redhat-s390-list mailing list > Redhat-s390-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-s390-list >
