[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Redhat-s390-list] OSA detection problem with Roswell beta 3



I neglected to mention that we did try to insmod the modules. It seemed to
accept
 everything we through at it (including typos) without outputting any
errors. After we
insmod'd, we ifconfig'd the settings, and got the exact error messages that
I earlier sent in.

Michael Lambert





Sent by:  "Post, Mark K" <mark post eds com>







To:
      "'Michael K Lambert'" <mlambe7 lsu edu>
cc:



Subject:
      RE: [Redhat-s390-list] OSA detection problem with Roswell beta 3



      Michael,

      The only thing I can suggest is as before: try doing it "by hand" to
      see
      what error messages come out.  The scripts swallow all that stuff and
      you
      never get to see it.

      Mark Post

      -----Original Message-----
      From: Michael K Lambert [mailto:mlambe7 lsu edu]
      Sent: Friday, October 05, 2001 3:49 PM
      To: redhat-s390-list redhat com
      Subject: [Redhat-s390-list] OSA detection problem with Roswell beta 3


      I downloaded the latest iso's of Red Hat for the s390, inserted the
      newest
      lcs, qdio and qeth OCO modules (the latest versions) into initrd.img
      and
      attempted to install the OS according to the README procedures.

       We booted from the CD at the hardware managment console and answered
      the
       questions about network device, domain name, gateway, etc.
      Unfortunately,
       we were met with the following string of messages:

       "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"

       Our machine has both an ATM and a OSA Express card, so we made
      multiple
       attempts to get either card to work in every configuration that we
      could
       think of, but every time we got the same results.

       I'm glad to see that the "unresolved symbol tasklet_hi_schedule" has
      been
       dealth with, but we still are stuck with a mainframe that we cannot
       communicate with. If anyone has any suggestions, they would be
      greatly
       appreciated.

       Michael Lambert


      _______________________________________________
      Redhat-s390-list mailing list
      Redhat-s390-list redhat com
      https://listman.redhat.com/mailman/listinfo/redhat-s390-list
 -






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]