Bug#492571: hook-functions: manual_add_modules(): doesn't work with mawk
Package: initramfs-tools
Version: 0.92e
Severity: important
See manual_add_modules() in /usr/share/initramfs-tools/hook-functions:
awk '/^insmod/ { print $2 }'
That line works as expected when your awk is `gawk`, but produces no output
with `mawk`. This leaves the system unbootable (in my case) because none of
the kernel drivers are copied to the ramfs image. Easy workaround is to
replace it with this:
grep '^insmod' | sed -r '/insmod\s+//'
-- Package-specific info:
-- /proc/cmdline
root=UUID=5c884208-2607-40e2-b304-33e971c3b6b0 ro
-- /proc/filesystems
cramfs
xfs
fuseblk
-- lsmod
Module Size Used by
xt_tcpudp 7808 1
iptable_filter 7552 1
ip_tables 24680 1 iptable_filter
x_tables 24712 2 xt_tcpudp,ip_tables
video 23440 0
button 13472 0
ac 10376 0
battery15496 0
ipv6 296840 8
fuse 50608 1
dm_snapshot21704 0
dm_mirror 26240 0
dm_mod 64112 2 dm_snapshot,dm_mirror
loop 23044 0
pcmcia 45976 0
firmware_class 15360 1 pcmcia
joydev 15616 0
wlan_scan_sta 18176 0
ath_rate_sample17152 1
snd_hda_intel 311968 2
snd_pcm_oss48288 0
snd_mixer_oss 21376 1 snd_pcm_oss
tifm_7xx1 12672 0
snd_pcm89992 2 snd_hda_intel,snd_pcm_oss
tifm_core 16264 1 tifm_7xx1
ath_pci99632 0
snd_timer 28424 1 snd_pcm
yenta_socket 31756 1
rsrc_nonstatic 16128 1 yenta_socket
pcmcia_core46628 3 pcmcia,yenta_socket,rsrc_nonstatic
wlan 206496 4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 222576 3 ath_rate_sample,ath_pci
i2c_nforce210624 0
snd65896 9
snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 13088 1 snd
psmouse45468 0
pcspkr 7680 0
snd_page_alloc 15376 2 snd_hda_intel,snd_pcm
i2c_core 31488 1 i2c_nforce2
k8temp 10496 0
serio_raw 11780 0
tsdev 13312 0
evdev 15232 5
xfs 497864 1
ide_cd 44832 0
cdrom 39848 1 ide_cd
usbhid 32704 0
hid31360 1 usbhid
amd74xx19888 0 [permanent]
generic10372 0 [permanent]
ide_core 147728 3 ide_cd,amd74xx,generic
ata_generic13188 0
forcedeth 52872 0
ehci_hcd 37900 0
ohci_hcd 25860 0
thermal19600 0
processor 39912 1 thermal
fan 9992 1
sata_nv25860 2
libata132528 2 ata_generic,sata_nv
sd_mod 33280 3
scsi_mod 164536 2 libata,sd_mod
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = yes
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initramfs-tools depends on:
ii cpio 2.9-13 GNU cpio -- a program to manage ar
ii findutils 4.4.0-2utilities for finding files--find,
ii klibc-utils 1.5.11-3 small utilities built with klibc f
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii udev 0.114-2/dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.9.2-3 Tiny utilities for small and embed
initramfs-tools suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#485465: sometimes brightness OK (lowest) at boot
Maybe a burglar alarm can be attached to the brightness, so that whenever it is tampered with, a syslog entry will be made, so we can tell what programs try to meddle with the brightness setting. H If you are confortable recompiling the kernel, I can send you a patch with H that burgar alarm. Just tell me exactly which kernel you're using. (Too bad stock kernels here on sid, $ apt-cache policy $@ linux-image-2.6.25-2-686: Installed: 2.6.25-7 don't have such a feature, as I dare not get deeper than stock kernels.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492581: linux-image-2.6.25-2-686: Does not halt an EeePC 701
Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 Severity: normal I'm running this kernel on my EeePC 701. When I tell the system to halt it shuts down almost everything (the screen goes off) and then hangs. It leaves one LED on and produces some heat as the only indications that it's not off. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467454: some modules unnecessarily built-in
On Sat, Jul 26, 2008 at 01:52:27PM -0700, Martin Michlmayr wrote: P.S. Riku posted an interesting message asking whether we could replace the versatile flavour with a more popular ARM arch that is also emulated by qemu. That would either be the pxa zauruses or omap2. But that could be a bit steep change for so close to freeze. -- rm -rf only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#420434: ieee80211-source: new upstream version 1.2.17
* Sumit Madan [EMAIL PROTECTED] [2007-04-22 12:06]: Package: ieee80211-source Version: 1.1.14-1 Daniel, this is in Debian now, right? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414932: Processed: Re: Bug#414932: linux-image-2.6.18-4-ixp4xx: xfs partition from x86 system can not be used on arm
Martin Michlmayr [EMAIL PROTECTED] writes: * Eric Sandeen [EMAIL PROTECTED] [2008-06-21 10:50]: It was just recently added to the xfs cvs tree. Message to the list was TAKE 982930 - fix dir2 shortform structures on ARM old ABI * Niv Sardi [EMAIL PROTECTED] [2008-06-23 15:12]: http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=7a9ba9bb899933293604a2b3c5ca4f40ad5a92a8 This fixes the issue, and should be pushed in the next kernel.org xfs. It seems there hasn't been a pull request for xfs for 2.6.27 yet and rc1 will happen soon. Any idea when there'll be a pull request? It should be happening in the next days, we're having some weird behaviours with the [EMAIL PROTECTED], and trying to get those sorted out. Cheers, -- Niv Sardi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
