What does "dmesg" give you?  That is normally where the errors show up that
are masked by the startup scripts.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Pinion
Sent: Tuesday, May 18, 2004 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: lcs devices under gentoo for s390


OK, I can't figure out what the problem is, here is the boot log and after
that are the config files that I have updated.

* Calculating module dependencies...
  [ ok ]
 * Using /etc/modules.autoload.d/kernel-2.6 as config:
 *   Loading module lcs...
  [ ok ]
 *   Loading module tape_34xx...
  [ ok ]
 * Autoloaded 2 module(s)
 * Bringing lo up...
  [ ok ]
 * Initializing random number generator...
  [ ok ]
INIT: Entering runlevel: 3
 * Starting metalog...
  [ ok ]
 * Setting DNS domainname to bhset.org...
  [ ok ]
 * Bringing eth0 up (172.30.102.17)...
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device
  [ !! ]
 * ERROR:  Problem starting needed services.
 *         "netmount" was not started.
 * ERROR:  Problem starting needed services.
 *         "xinetd" was not started.
 * Starting local...  [ ok ]
This is linux390.unknown_domain (Linux s390 2.6.5) 19:18:17 linux390 login:
----------------------------------------------------------------------------
----


/etc/modules.conf has an entry of
  alias eth0 lcs

/etc/modprobe.conf has an entry of
  alias eth0 lcs

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

Reply via email to