Re: Problem with nfs and initramfs-tools
On Thu, 10 Jan 2008, Andre Timmermann wrote:
> When u use the parameter ip=::dhcp on the commandline, the following
> command will be executed by the
> nfs-script /usr/share/initramfs-tools/scripts/nfs:
>
> ipconfig -d ::dhcp
>
> This loops forever because one interface will not come up due to a
> missing network-cable.
fixed in unstable ipconfig klibc 1.5.9-1,
please try it out
> Adding "-t 10" kills ipconfig after 10 tries.
> ipconfig -t 10 -d ::dhcp
couldn't reproduce that would continue to loop for me.
> After that sourceing /tmp/net-${DEVICE}.conf will overwrite the nfs
> setting from the kernel-commandline with the setting gathered from the
> dhcp-server. And again, this could be desired or not ;)
> Our DHCP-Server does not know anything about the nfs-root because it is
> needed exclusively by the rescuesystem.
hmmm that depends on your nfs boot params, can you please post yours,
where you were seeing this?
> In addition ${DEVICE} seemes to be hardcoded in the initramfs.conf. If
> initramfs.conf says eth0 and the interface is eth1 it will not be
> sourced.
>
> I have put it like this:
>
> for i in `ls /tmp/net-*.conf`; do . $i; done
>
> as I know that there is only one nic which will be configured.
this should be possbile to pass as boot param afair.
thanks for your feedback and patience.
best regards
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 473136
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 473136 + pending Bug#473136: linux-image-2.6.24-1-iop32x: Can't found /dev/rtc : not hardware clock There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 462677
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 462677 + pending Bug#462677: rm assert error on arm: ((status) == RM_OK || (status) == RM_USER_DECLINED || (status) == RM_ERROR) Tags were: moreinfo unreproducible Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473136: linux-image-2.6.24-1-iop32x: Can't found /dev/rtc : not hardware clock
OK, so the problem is that you use the IQ31244 support, and the IQ31244 doesn't have RTC. I suggest you use the kernel support for EM7210 instead, which should be closer to the EM7220 than the IQ31244. I will activate support for EM7210 for 2.6.25. Since your boot loader obviously tells the kernel it's a IQ31244 rather than a EM7220, you have to prepand a couple of bytes to set the machine id to that of EM7220 (or, rather, EM7210, which is supported in the kernel). The machine ID for EM7210 is 1212, so 0x04bc. devio > header 'wl 0xe3a01c04,4' 'wl 0xe38110bc,4' and then cat header vmlinux* > new-kernel should work. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473136: linux-image-2.6.24-1-iop32x: Can't found /dev/rtc : not hardware clock
Martin Michlmayr a écrit :
> OK, so the problem is that you use the IQ31244 support, and the
> IQ31244 doesn't have RTC. I suggest you use the kernel support for
> EM7210 instead, which should be closer to the EM7220 than the IQ31244.
> I will activate support for EM7210 for 2.6.25.
The RTC in EM7210 and EM7220 is not exactly the same. In the EM7210 :
/*
* EM7210 RTC
*/
static struct i2c_board_info __initdata em7210_i2c_devices[] = {
{
I2C_BOARD_INFO("rtc-rs5c372", 0x32),
.type = "rs5c372a",
},
};
In the EM7220 :
rtc-rs5c372 0-0032: assuming rs5c372b
rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.4
There is no difference between rs5c372b and rs5c372a ?
PS : I'm sorry for the fail of reply-to...
Bug#473331: linux-image-2.6.24-1-amd64: dma engine support missing
Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 Severity: normal Hello, It looks like DMA engine support is missing in the 2.6.24 kernel. Only the Intel I/O AT driver is available, and thus unusable. 2.6.23 was ok. The following config options seem to be missing: CONFIG_DMADEVICES=y CONFIG_DMA_ENGINE=y CONFIG_NET_DMA=y Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473206: Acknowledgement (linux-image-2.6.24-1-686: please enable kernel .config support for all x86 images)
Sorry, something went wrong with my previous post. I just wanted to ask the kernel team to enable # grep IKCONFIG config-2.6.24-1-amd64 CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y for all x86 kernel packages like it is the case for amd64. Thanks, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473075: linux-image-2.6.24-1-686: Won't boot, seems root fs not mounted
Hmm, uphill battle both ways, I've noticed this type of behavior on Debian kernel since Sarge. A new kernel will re-shuffle device order from SCSI being the sda/boot device to SATA, while upgrading kernel-images. Now with Lenny, 2.6.24 I have the same issue with LCD built-in USB card readers getting assigned sda/boot device over AHCI SATA. The only solution is to figure out the devices responsible for module load and manually modify the initramfs sequence. Andrew Nady -- How much net work could a network work, if a network could net work? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#471461: linux-modules-extra-2.6: Please add sfc modules
Ben Hutchings wrote: > Bastian Blank wrote: > > On Fri, Mar 28, 2008 at 04:31:11PM +, Ben Hutchings wrote: > > > You should not invoke kbuild directly on the > > > module source directory. > > > > This is the prequisite to build it as part of linux-modules-*. > > OK. Why doesn't it do what module-assistant does? > > I could add a static config.h and extraversion.h to the package as we don't > need to worry about versions with backported changes in Debian, unlike some > other distributions I could mention. I have done this in package version 2.2.0063-2. > However we're switching to a more > autoconf-like way of detecting kernel features, which will mean that in future > it's essential to run a script before compiling any source files. I'll try > using the filechk rules in kbuild to do this. I have successfully done this in the development tree, so unless it turns out to cause problems for other build configurations this should work without patching in future. Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473206: Acknowledgement (linux-image-2.6.24-1-686: please enable kernel .config support for all x86 images)
On Sun, Mar 30, 2008 at 12:37:53AM +0100, Daniel Reichelt wrote: > Sorry, something went wrong with my previous post. > > I just wanted to ask the kernel team to enable > > # grep IKCONFIG config-2.6.24-1-amd64 > CONFIG_IKCONFIG=y > CONFIG_IKCONFIG_PROC=y > > for all x86 kernel packages like it is the case for amd64. > Thanks, IKCONFIG is a waste of mem, was more thinking of disabling it. we have anyway a standardized location acroos distro in /boot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465812: marked as done (linux-image-2.6.22-3-686: [Regression] LuKS passphrase not accepted anymore)
Your message dated Sun, 30 Mar 2008 04:25:41 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#465812: has caused the Debian Bug report #465812, regarding linux-image-2.6.22-3-686: [Regression] LuKS passphrase not accepted anymore to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 465812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465812 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.22-3-686 Version: 2.6.22-6.lenny1 Severity: critical Justification: breaks the whole system Setup my system with etch, whole root encrypted, seperate partition for / and /home inside LuKS LVM. Can enter my LuKS passphrase on boot but it's not accepted. Does not happen with 2.6.22-2. Does also happen with all 2.6.24 linux-images from unstable (some message about via_padlock_* modules failing to load with 2.6.24, i have an ATI based board). -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.22-3-686 depends on: ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.22-3-686 recommends: ii libc6-i6862.7-6 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.22-3-686/prerm/would-invalidate-boot-loader-2.6.22-3-686: true linux-image-2.6.22-3-686/preinst/overwriting-modules-2.6.22-3-686: true linux-image-2.6.22-3-686/postinst/kimage-is-a-directory: linux-image-2.6.22-3-686/postinst/old-system-map-link-2.6.22-3-686: true linux-image-2.6.22-3-686/postinst/old-dir-initrd-link-2.6.22-3-686: true linux-image-2.6.22-3-686/preinst/bootloader-initrd-2.6.22-3-686: true linux-image-2.6.22-3-686/prerm/removing-running-kernel-2.6.22-3-686: true linux-image-2.6.22-3-686/postinst/bootloader-test-error-2.6.22-3-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.22-3-686/preinst/lilo-initrd-2.6.22-3-686: true linux-image-2.6.22-3-686/preinst/elilo-initrd-2.6.22-3-686: true linux-image-2.6.22-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.22-3-686/postinst/old-initrd-link-2.6.22-3-686: true linux-image-2.6.22-3-686/preinst/initrd-2.6.22-3-686: * linux-image-2.6.22-3-686/preinst/already-running-this-2.6.22-3-686: linux-image-2.6.22-3-686/postinst/depmod-error-2.6.22-3-686: false linux-image-2.6.22-3-686/postinst/bootloader-error-2.6.22-3-686: linux-image-2.6.22-3-686/preinst/failed-to-move-modules-2.6.22-3-686: linux-image-2.6.22-3-686/preinst/abort-install-2.6.22-3-686: linux-image-2.6.22-3-686/preinst/abort-overwrite-2.6.22-3-686: linux-image-2.6.22-3-686/postinst/depmod-error-initrd-2.6.22-3-686: false linux-image-2.6.22-3-686/postinst/create-kimage-link-2.6.22-3-686: true --- End Message --- --- Begin Message --- On Tue, 04 Mar 2008, Ritesh Raj Sarraf wrote: > Please ignore all my reports in regard to this bug. > I am an idiot. > 2 days of vacation had indeed made me forget my password. > > Ritesh > ok thus closing, thanks for your feedback. --- End Message ---
Bug#469312: initramfs-tools: awk reports syntax error in update-initramfs
On Tue, 04 Mar 2008, Joe Pfeiffer wrote:
> Attempting to run update-initramfs is giving me the following result:
>
> snowball:552$ sudo update-initramfs -u 2.6.22-3-k7
> update-initramfs: Generating /boot/initrd.img-2.6.22-3-k7
> awk: /^md/2/{print substr($5, 1, 3)}
> awk:^ syntax error
>
can you still reproduce this?
did you copy the hole message?
can you please paste the output of
sh -x update-initramfs -u
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of linux-modules-extra-2.6_2.6.24-6_i386.changes
linux-modules-extra-2.6_2.6.24-6_i386.changes uploaded successfully to localhost along with the files: linux-modules-extra-2.6_2.6.24-6.dsc linux-modules-extra-2.6_2.6.24-6.tar.gz atl2-modules-2.6.24-1-486_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6-486_2.6.24-6_i386.deb aufs-modules-2.6.24-1-486_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6-486_2.6.24-6_i386.deb btrfs-modules-2.6.24-1-486_2.6.24+0.13-6_i386.deb btrfs-modules-2.6-486_2.6.24-6_i386.deb drbd8-modules-2.6.24-1-486_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6-486_2.6.24-6_i386.deb gspca-modules-2.6.24-1-486_2.6.24+01.00.20-6_i386.deb gspca-modules-2.6-486_2.6.24-6_i386.deb kqemu-modules-2.6.24-1-486_2.6.24+1.3.0~pre11-6_i386.deb kqemu-modules-2.6-486_2.6.24-6_i386.deb loop-aes-modules-2.6.24-1-486_2.6.24+3.2c-6_i386.deb loop-aes-modules-2.6-486_2.6.24-6_i386.deb lzma-modules-2.6.24-1-486_2.6.24+4.43-6_i386.deb lzma-modules-2.6-486_2.6.24-6_i386.deb r6040-modules-2.6.24-1-486_2.6.24+0.17-6_i386.deb r6040-modules-2.6-486_2.6.24-6_i386.deb redhat-cluster-modules-2.6.24-1-486_2.6.24+2.20080229-6_i386.deb redhat-cluster-modules-2.6-486_2.6.24-6_i386.deb squashfs-modules-2.6.24-1-486_2.6.24+3.3-6_i386.deb squashfs-modules-2.6-486_2.6.24-6_i386.deb unionfs-modules-2.6.24-1-486_2.6.24+2.2.3-2.6.24-6_i386.deb unionfs-modules-2.6-486_2.6.24-6_i386.deb virtualbox-ose-modules-2.6.24-1-486_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-modules-2.6-486_2.6.24-6_i386.deb virtualbox-ose-guest-modules-2.6.24-1-486_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-guest-modules-2.6-486_2.6.24-6_i386.deb atl2-modules-2.6.24-1-686_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6-686_2.6.24-6_i386.deb aufs-modules-2.6.24-1-686_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6-686_2.6.24-6_i386.deb btrfs-modules-2.6.24-1-686_2.6.24+0.13-6_i386.deb btrfs-modules-2.6-686_2.6.24-6_i386.deb drbd8-modules-2.6.24-1-686_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6-686_2.6.24-6_i386.deb gspca-modules-2.6.24-1-686_2.6.24+01.00.20-6_i386.deb gspca-modules-2.6-686_2.6.24-6_i386.deb kqemu-modules-2.6.24-1-686_2.6.24+1.3.0~pre11-6_i386.deb kqemu-modules-2.6-686_2.6.24-6_i386.deb loop-aes-modules-2.6.24-1-686_2.6.24+3.2c-6_i386.deb loop-aes-modules-2.6-686_2.6.24-6_i386.deb lzma-modules-2.6.24-1-686_2.6.24+4.43-6_i386.deb lzma-modules-2.6-686_2.6.24-6_i386.deb r6040-modules-2.6.24-1-686_2.6.24+0.17-6_i386.deb r6040-modules-2.6-686_2.6.24-6_i386.deb redhat-cluster-modules-2.6.24-1-686_2.6.24+2.20080229-6_i386.deb redhat-cluster-modules-2.6-686_2.6.24-6_i386.deb squashfs-modules-2.6.24-1-686_2.6.24+3.3-6_i386.deb squashfs-modules-2.6-686_2.6.24-6_i386.deb unionfs-modules-2.6.24-1-686_2.6.24+2.2.3-2.6.24-6_i386.deb unionfs-modules-2.6-686_2.6.24-6_i386.deb virtualbox-ose-modules-2.6.24-1-686_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-modules-2.6-686_2.6.24-6_i386.deb virtualbox-ose-guest-modules-2.6.24-1-686_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-guest-modules-2.6-686_2.6.24-6_i386.deb atl2-modules-2.6.24-1-686-bigmem_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6-686-bigmem_2.6.24-6_i386.deb aufs-modules-2.6.24-1-686-bigmem_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6-686-bigmem_2.6.24-6_i386.deb btrfs-modules-2.6.24-1-686-bigmem_2.6.24+0.13-6_i386.deb btrfs-modules-2.6-686-bigmem_2.6.24-6_i386.deb drbd8-modules-2.6.24-1-686-bigmem_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6-686-bigmem_2.6.24-6_i386.deb gspca-modules-2.6.24-1-686-bigmem_2.6.24+01.00.20-6_i386.deb gspca-modules-2.6-686-bigmem_2.6.24-6_i386.deb kqemu-modules-2.6.24-1-686-bigmem_2.6.24+1.3.0~pre11-6_i386.deb kqemu-modules-2.6-686-bigmem_2.6.24-6_i386.deb loop-aes-modules-2.6.24-1-686-bigmem_2.6.24+3.2c-6_i386.deb loop-aes-modules-2.6-686-bigmem_2.6.24-6_i386.deb lzma-modules-2.6.24-1-686-bigmem_2.6.24+4.43-6_i386.deb lzma-modules-2.6-686-bigmem_2.6.24-6_i386.deb r6040-modules-2.6.24-1-686-bigmem_2.6.24+0.17-6_i386.deb r6040-modules-2.6-686-bigmem_2.6.24-6_i386.deb redhat-cluster-modules-2.6.24-1-686-bigmem_2.6.24+2.20080229-6_i386.deb redhat-cluster-modules-2.6-686-bigmem_2.6.24-6_i386.deb squashfs-modules-2.6.24-1-686-bigmem_2.6.24+3.3-6_i386.deb squashfs-modules-2.6-686-bigmem_2.6.24-6_i386.deb unionfs-modules-2.6.24-1-686-bigmem_2.6.24+2.2.3-2.6.24-6_i386.deb unionfs-modules-2.6-686-bigmem_2.6.24-6_i386.deb virtualbox-ose-modules-2.6.24-1-686-bigmem_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-modules-2.6-686-bigmem_2.6.24-6_i386.deb virtualbox-ose-guest-modules-2.6.24-1-686-bigmem_2.6.24+1.5.6-dfsg-6_i386.deb virtualbox-ose-guest-modules-2.6-686-bigmem_2.6.24-6_i386.deb atl2-modules-2.6.24-1-amd64_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6-amd64_2.6.24-6_i386.deb aufs-modules-2.6.24-1-amd64_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6-amd64_2.6.24-6_i386.deb btrfs-modules-2.6.24-1-amd64_2.6.24+0.13-6_i386.deb btrfs-modules-2.6-amd64_2.6.24-6_i386.deb drbd8-mod
linux-modules-extra-2.6_2.6.24-6_i386.changes ACCEPTED
Accepted: atl2-modules-2.6-486_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6-486_2.6.24-6_i386.deb atl2-modules-2.6-686-bigmem_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6-686-bigmem_2.6.24-6_i386.deb atl2-modules-2.6-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6-686_2.6.24-6_i386.deb atl2-modules-2.6-amd64_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6-amd64_2.6.24-6_i386.deb atl2-modules-2.6.24-1-486_2.6.24+2.0.3-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6.24-1-486_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6.24-1-686-bigmem_2.6.24+2.0.3-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6.24-1-686-bigmem_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6.24-1-686_2.6.24+2.0.3-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6.24-1-686_2.6.24+2.0.3-6_i386.deb atl2-modules-2.6.24-1-amd64_2.6.24+2.0.3-6_i386.deb to pool/main/l/linux-modules-extra-2.6/atl2-modules-2.6.24-1-amd64_2.6.24+2.0.3-6_i386.deb aufs-modules-2.6-486_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-486_2.6.24-6_i386.deb aufs-modules-2.6-686-bigmem_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-686-bigmem_2.6.24-6_i386.deb aufs-modules-2.6-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-686_2.6.24-6_i386.deb aufs-modules-2.6-amd64_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-amd64_2.6.24-6_i386.deb aufs-modules-2.6-xen-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-xen-686_2.6.24-6_i386.deb aufs-modules-2.6.24-1-486_2.6.24+0+20080129-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.24-1-486_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6.24-1-686-bigmem_2.6.24+0+20080129-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.24-1-686-bigmem_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6.24-1-686_2.6.24+0+20080129-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.24-1-686_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6.24-1-amd64_2.6.24+0+20080129-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.24-1-amd64_2.6.24+0+20080129-6_i386.deb aufs-modules-2.6.24-1-xen-686_2.6.24+0+20080129-6_i386.deb to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.24-1-xen-686_2.6.24+0+20080129-6_i386.deb btrfs-modules-2.6-486_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6-486_2.6.24-6_i386.deb btrfs-modules-2.6-686-bigmem_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6-686-bigmem_2.6.24-6_i386.deb btrfs-modules-2.6-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6-686_2.6.24-6_i386.deb btrfs-modules-2.6-amd64_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6-amd64_2.6.24-6_i386.deb btrfs-modules-2.6-xen-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6-xen-686_2.6.24-6_i386.deb btrfs-modules-2.6.24-1-486_2.6.24+0.13-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6.24-1-486_2.6.24+0.13-6_i386.deb btrfs-modules-2.6.24-1-686-bigmem_2.6.24+0.13-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6.24-1-686-bigmem_2.6.24+0.13-6_i386.deb btrfs-modules-2.6.24-1-686_2.6.24+0.13-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6.24-1-686_2.6.24+0.13-6_i386.deb btrfs-modules-2.6.24-1-amd64_2.6.24+0.13-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6.24-1-amd64_2.6.24+0.13-6_i386.deb btrfs-modules-2.6.24-1-xen-686_2.6.24+0.13-6_i386.deb to pool/main/l/linux-modules-extra-2.6/btrfs-modules-2.6.24-1-xen-686_2.6.24+0.13-6_i386.deb drbd8-modules-2.6-486_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6-486_2.6.24-6_i386.deb drbd8-modules-2.6-686-bigmem_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6-686-bigmem_2.6.24-6_i386.deb drbd8-modules-2.6-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6-686_2.6.24-6_i386.deb drbd8-modules-2.6-amd64_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6-amd64_2.6.24-6_i386.deb drbd8-modules-2.6-xen-686_2.6.24-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6-xen-686_2.6.24-6_i386.deb drbd8-modules-2.6.24-1-486_2.6.24+8.0.11-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6.24-1-486_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6.24-1-686-bigmem_2.6.24+8.0.11-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6.24-1-686-bigmem_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6.24-1-686_2.6.24+8.0.11-6_i386.deb to pool/main/l/linux-modules-extra-2.6/drbd8-modules-2.6.24-1-686_2.6.24+8.0.11-6_i386.deb drbd8-modules-2.6.24-1-amd64_2.6.24+8.0.
Bug#469312: marked as done (initramfs-tools: awk reports syntax error in update-initramfs)
Your message dated Sun, 30 Mar 2008 04:59:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#469312: initramfs-tools: awk reports syntax error in
update-initramfs
has caused the Debian Bug report #469312,
regarding initramfs-tools: awk reports syntax error in update-initramfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
469312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469312
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.91e
Severity: critical
Justification: breaks the whole system
Attempting to run update-initramfs is giving me the following result:
snowball:552$ sudo update-initramfs -u 2.6.22-3-k7
update-initramfs: Generating /boot/initrd.img-2.6.22-3-k7
awk: /^md/2/{print substr($5, 1, 3)}
awk:^ syntax error
The resulting initrd image apears to be corrupt -- at any rate, my
kernel panicked shortly after trying to mount it.
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=Linux ro root=902
-- /proc/filesystems
cramfs
ext3
fuseblk
-- lsmod
Module Size Used by
iptable_mangle 3136 0
iptable_filter 3264 0
ipt_MASQUERADE 3904 1
iptable_nat 7556 1
nf_nat 18348 2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 18124 2 iptable_nat
nf_conntrack 61000 4
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4
nfnetlink 6168 3 nf_nat,nf_conntrack_ipv4,nf_conntrack
ip_tables 12708 3 iptable_mangle,iptable_filter,iptable_nat
x_tables 14660 3 ipt_MASQUERADE,iptable_nat,ip_tables
binfmt_misc11400 1
via40192 2
drm76628 3 via
nfsd 204912 13
exportfs5952 1 nfsd
ppdev 8964 0
lp 11300 0
autofs420804 2
nfs 225452 0
lockd 61320 3 nfsd,nfs
nfs_acl 3840 2 nfsd,nfs
sunrpc158972 11 nfsd,nfs,lockd,nfs_acl
ipv6 239524 35
sd_mod 27584 0
fuse 42388 1
dm_snapshot16804 0
dm_mirror 21376 0
dm_mod 52672 2 dm_snapshot,dm_mirror
snd_via82xx27224 0
gameport 15304 1 snd_via82xx
snd_ac97_codec 93220 1 snd_via82xx
ac97_bus2560 1 snd_ac97_codec
snd_pcm_oss39904 0
snd_mixer_oss 15872 1 snd_pcm_oss
snd_pcm72772 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss
snd_page_alloc 9800 2 snd_via82xx,snd_pcm
snd_mpu401_uart 8384 1 snd_via82xx
snd_seq_dummy 4036 0
snd_seq_oss29760 0
snd_seq_midi8480 0
snd_rawmidi23264 2 snd_mpu401_uart,snd_seq_midi
usb_storage77440 0
parport_pc 34212 1
parport34312 3 ppdev,lp,parport_pc
evdev 9664 2
snd_seq_midi_event 7360 2 snd_seq_oss,snd_seq_midi
snd_seq46864 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 21380 2 snd_pcm,snd_seq
snd_seq_device 8012 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
shpchp 31380 0
usbhid 26144 0
hid25792 1 usbhid
snd48804 11
snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
i2c_viapro 8788 0
pcspkr 3392 0
k8temp 5824 0
soundcore 7840 1 snd
i2c_core 24000 1 i2c_viapro
rtc13144 0
pci_hotplug29568 1 shpchp
amd64_agp 12420 1
agpgart32264 2 drm,amd64_agp
pl2303 20036 0
usbserial 31976 1 pl2303
usblp 13632 0
ext3 122632 2
jbd55848 1 ext3
mbcache 8580 1 ext3
raid1 22784 1
md_mod 74196 4 raid1
ide_cd 36896 0
cdrom 33184 1 ide_cd
ide_disk 16832 7
ata_generic 7876 0
libata116912 1 ata_generic
scsi_mod 137356 3 sd_mod,usb_storage,libata
via_rhine 24136 0
mii 5696 1 via_rhine
ehci_hcd 31116 0
uhci_hcd 23376 0
Bug#459445: marked as done (initramfs-tools: update-initramfs does not consider latest kernel by default)
Your message dated Sun, 30 Mar 2008 05:01:53 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: initramfs-tools: update-initramfs does not consider latest kernel by default has caused the Debian Bug report #459445, regarding initramfs-tools: update-initramfs does not consider latest kernel by default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 459445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459445 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: initramfs-tools Version: 0.91d Severity: normal Hi, when running update-initramfs without specifying a kernel version (-k), the default version should be the latest kernel version (according to manpage). It is not in my case: $ ls /var/lib/initramfs-tools/ 2.6.22-3-amd64 2.6.23-1-amd64 $ ls /boot/initrd.* /boot/initrd.img-2.6.22-3-amd64 /boot/initrd.img-2.6.23-1-amd64 /boot/initrd.img-2.6.22-3-amd64.bak /boot/initrd.img-2.6.23-1-amd64.bak $ uname -r 2.6.23-1-amd64 # update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.22-3-amd64 Note that update_initramfs is set to "yes" in /etc/initramfs-tools/update-initramfs.conf. When changing this option to "all", the expected behaviour work. Cheers, Julien -- Package-specific info: -- /proc/cmdline root=/dev/mapper/athyr-root ro quiet pci=nommconf vga=795 -- /proc/filesystems ext3 -- lsmod Module Size Used by i915 31616 2 drm 100392 3 i915 binfmt_misc17292 1 rfcomm 49448 0 l2cap 32896 5 rfcomm bluetooth 65796 4 rfcomm,l2cap tun16384 0 ppdev 13832 0 parport_pc 42664 0 lp 17480 0 parport44428 3 ppdev,parport_pc,lp ac 10760 0 battery18064 0 ipv6 303336 24 dm_crypt 18192 0 snd_seq_dummy 8452 0 snd_seq_oss36736 0 snd_seq_midi 13376 0 snd_rawmidi30624 1 snd_seq_midi snd_seq_midi_event 12416 2 snd_seq_oss,snd_seq_midi snd_seq58752 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_seq_device 12948 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq coretemp 12544 0 w83627ehf 28168 0 hwmon_vid 7296 1 w83627ehf vboxdrv 1646592 0 loop 23428 0 snd_hda_intel 339364 0 snd_pcm_oss48288 0 snd_mixer_oss 21376 1 snd_pcm_oss snd_pcm89864 2 snd_hda_intel,snd_pcm_oss snd_timer 28552 2 snd_seq,snd_pcm button 13856 0 i2c_i801 13980 0 psmouse45596 0 intel_agp 32160 1 i2c_core 30976 1 i2c_i801 snd65640 9 snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13216 1 snd snd_page_alloc 15248 2 snd_hda_intel,snd_pcm tsdev 13440 0 iTCO_wdt 17232 0 serio_raw 11908 0 evdev 15360 4 pcspkr 7808 0 ext3 137488 3 jbd68080 1 ext3 mbcache13952 1 ext3 dm_mirror 27008 0 dm_snapshot21960 0 dm_mod 64368 10 dm_crypt,dm_mirror,dm_snapshot sd_mod 33408 3 ide_cd 44704 0 cdrom 39592 1 ide_cd ata_piix 23044 2 usbhid 34144 0 hid33152 1 usbhid ata_generic13188 0 jmicron 8576 0 [permanent] firewire_ohci 22912 0 firewire_core 49600 1 firewire_ohci crc_itu_t 6656 1 firewire_core skge 46608 0 floppy 66984 0 ahci 30468 0 libata129840 3 ata_piix,ata_generic,ahci generic10372 0 [permanent] scsi_mod 164664 2 sd_mod,libata ide_core 149904 3 ide_cd,jmicron,generic ehci_hcd 38540 0 uhci_hcd 29984 0 thermal22176 0 processor 43624 1 thermal fan10248 0 -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader
Bug#467627: initramfs-tools: Boot parameter panic=0 not compatible with break= parameter.
On Tue, 26 Feb 2008, Tim Phipps wrote: > You can't use break=??? if you use panic=0. This is because the > maybe_break function calls the panic function to get a shell. It should > be simple to fix by just setting panic=1 inside maybe_break() before > calling panic(). yep this was explicitly asked so by security guys. and it is documentated in the debian harden manual. so if you wana break either set panic to another value or errase it by hand. unless some real convincing stuff comes up to this bug report, i'll close this with documentating this behaviour in the manpage. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473358: linux-latest-2.6: kernel not compiled with current gcc
Package: linux-latest-2.6 Severity: important I've had build problems with both VMware Server and nvidia complaining of a gcc version mismatch... the current version they want to build with is gcc 4.3 , the gcc used on the current kernel version is 4.1. While changing the gcc symlink is easy enough, what's easy for me isn't going to be easy for a newbie. Can you distribute future kernel upgrades compiled with the current gcc? thanks -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (150, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
