Bug#340508: missing modules on s390/s390x

2006-03-21 Thread maximilian attems
severity 340508 minor retitle 340508 unclean initramfs generation on s390 stop On Thu, 16 Mar 2006, Frans Pop wrote: > I've just upgraded to latest versions and see the following (harmless) > error during upgrade: > Setting up udev (0.087-2) ... > Installing new version of config file /etc/udev/

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Bastian Blank
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

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Bastian Blank
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

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Frans Pop
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.

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Hugo Monteiro
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

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Bastian Blank
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 config

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Ivan Warren
> > 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 > Modu

Bug#340508: missing modules on s390/s390x

2006-03-16 Thread Frans Pop
On Wednesday 15 March 2006 16:38, you wrote: > waldi added s390 support to initramfs-tools as of version 0.54. > 0.55 is in incoming.debian.org and should be available in unstable > soon. klibc-1.2.4-1 has an important s390 fix. > > so testing those releases are highly welcome. > you can rebuild yo

Bug#340508: missing modules on s390/s390x

2006-03-15 Thread maximilian attems
waldi added s390 support to initramfs-tools as of version 0.54. 0.55 is in incoming.debian.org and should be available in unstable soon. klibc-1.2.4-1 has an important s390 fix. so testing those releases are highly welcome. you can rebuild your initramfs after installation of aboves packages with

Bug#340508: missing modules on s390/s390x (mkinitramfs for 2.6.14)

2005-12-04 Thread Arnd Bergmann
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. >

Bug#340508: missing modules on s390/s390x (mkinitramfs for 2.6.14)

2005-12-04 Thread Frans Pop
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 igno

Bug#340508: missing modules on s390/s390x (mkinitramfs for 2.6.14)

2005-12-04 Thread Frans Pop
(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: - d

Bug#340508: missing modules on s390/s390x

2005-12-02 Thread maximilian attems
tags 340508 moreinfo thanks On Thu, 24 Nov 2005, Maximilian Attems wrote: > On Wed, Nov 23, 2005 at 11:41:02PM +0100, Frans Pop wrote: > > Submitter reported additional information re initramfs-tools to d-s390 > > mailing list [1]. Most relevant information (console messages) duplicated > > bel

Bug#340508: missing modules on s390/s390x

2005-11-23 Thread Maximilian Attems
On Wed, Nov 23, 2005 at 11:41:02PM +0100, Frans Pop wrote: > Submitter reported additional information re initramfs-tools to d-s390 > mailing list [1]. Most relevant information (console messages) duplicated > below. ok thanks. > Freeing unused kernel memory: 120k freed > Loading, please wait.

Bug#340508: missing modules on s390/s390x

2005-11-23 Thread Frans Pop
Submitter reported additional information re initramfs-tools to d-s390 mailing list [1]. Most relevant information (console messages) duplicated below. Freeing unused kernel memory: 120k freed Loading, please wait... Begin: Initializing /dev ... /sbin/udevsynthesize: 13: /lib/udev/udevsynthesize