Normally, when a driver activates, some messages show up in the kernel ring buffer. Doing a "dmesg" command will display the contents of the buffer. There might be some hints there as to why the driver is failing.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, October 18, 2004 8:45 AM To: [EMAIL PROTECTED] Subject: Re: V?lasz: SLES9 installation problem I tried option 3, but it couldn't access the devices. Gadi -----Original Message----- From: Istvan Nemeth [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: V?lasz: SLES9 installation problem Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.18 13:55:46 időpontban: > > I went back to the main menu and chose option 2 (Ethernet OSA). (This > worked in SLES8). I entered my first device address (1200) and waited. I guess you have to choose option 3: "OSA-Gigabit Ethernet or OSA-Express Fast Ethernet"... Istvan Nemeth ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
