RE: [Redhat-s390-list] lcs problems

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

 



Title: lcs problems
Never mind,  I checked the /etc/modules.conf and found that the wrong device address was in there for the 2216, it was from a previous installation. I should've reformatted the dasd when I installed the latest stuff.  Thanks, John
 
 

John Schmidt
johns@attachmate.com

-----Original Message-----
From: John Schmidt
Sent: Wednesday, August 08, 2001 12:43 PM
To: 'redhat-s390-list@redhat.com'
Subject: [Redhat-s390-list] lcs problems

Hello, I have successfully installed the latest system, minimal,  and can IPL my DASD but my network is failing. I am trying to use the lcs module for a 2216, which works fine on the initrd image, but I get these errors when I boot the installed system:

Aug  7 08:54:42 redhat390 ifup: /lib/modules/2.2.19-0.12vrdr/net/lcs.o:
Aug  7 08:54:42 redhat390 ifup: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters

Aug  7 08:54:42 redhat390 ifup: Device does not seem to be present, delaying eth0 initialization.
Aug  7 08:54:42 redhat390 ifup: init_module: Device or resource busy
Aug  7 08:54:42 redhat390 ifup: /lib/modules/2.2.19-0.12vrdr/net/lcs.o: insmod /lib/modules/2.2.19-0.12vrdr/net/lcs.o failed

Aug  7 08:54:42 redhat390 ifup: /lib/modules/2.2.19-0.12vrdr/net/lcs.o: insmod eth0 failed
Aug  7 08:54:42 redhat390 network: Bringing up interface eth0:  failed

Any ideas?  
Thanks, John


John Schmidt
johns@attachmate.com


[Index of Archives]     [Fedora General Discussion]     [LKML]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Linux s390]     [Gimp]     [Yosemite News]

  Powered by Linux