Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
# ifup eth0
Ignoring unknown interface eth0=eth0.
This looks like an issue related to udev persistent device naming.
Further info:
- The ctc module was loaded:
# lsmod
Module
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
The new kernel properly loads the network modules, the later is used to
On Qui, 2006-03-16 at 16:41 +0100, Ivan Warren wrote:
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
# ifup eth0
Ignoring unknown interface eth0=eth0.
This looks like an issue related to udev persistent device naming.
Thanks Bastian.
On Thursday 16 March 2006 17:29, Bastian Blank wrote:
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying
to manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
Yes,
On Thu, Mar 16, 2006 at 07:23:40PM +0100, Frans Pop wrote:
I see that the experimental kernel image does not depend on
sysconfig-hardware. Should it (to ensure that users upgrading from Sarge
will have it installed)?
Hmm. It is no dependency as the kernel can work without. Also it needs a
On Thu, Mar 16, 2006 at 07:33:59PM +0100, Bastian Blank wrote:
Hmm. It is no dependency as the kernel can work without. Also it needs a
converter for chandev to the new config format.
Which will only work automaticaly in the easiest config: only one
device/type as there is not longer any order.
(CC to d-s390 as there may be people who can provide additional
information.)
On Friday 02 December 2005 22:58, you wrote:
can you please retest if that device gets created?
OK. I've done some testing and made some progress.
First, the following modules need to be available in the initrd:
-
Some additional info.
I've done my research from a system (Hercules emulator) running 2.4.27.
For 2.4.27, the dasd modules are built into the kernel. The option to set
the dasd devices is therefore passed from the zipl bootloader.
The dasd= option in the [debian_26] section was of course
Am Sonntag 04 Dezember 2005 16:31 schrieb Frans Pop:
Reason is that dasd_mod needs an option to tell it which dasd devices
should be used. I've written a script that creates a config file for
modprobe in /etc/modprobe.d/.
The script is a first approximation and probably needs cleaning up.
9 matches
Mail list logo
