mkinitrd problem
Hello, This is Max from Milan, Italy. I'm trying to compile a new kernel (2.6.14.5) downloaded from kernel.org, of course. I've a Ubunt 5.10 with kernel 2.6.12.10. I've created my .config, i've made make...make modulesmake modules_install. So far so good. But when i try to create my initrd.img with mkinitrd, these errors are visualized: In /boot dir i exec mkinitrd -o initrd.img-2.6.14.5 and these messages appares find: warning: you have specified the -mindepth option after a non-option argument -type, but options are not positional (-mindepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -mindepth option after a non-option argument -type, but options are not positional (-mindepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. and my initrd.img file is not created. Please, Could you help me? Thanks in advance. Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Poll: debian/powerpc woody users ...
Hi, ... Debian still supports woody (as old_stable) for security releases. Still the kernel situation for woody was even worse than the sarge situation, as there where many different kernel version for all those subarches. I am wondering if there are still powerpc woody users out there, and if so, what kernel they are running, and which subarch (oldworld, newworld, prep, etc). And also if a security update would be worthwhile, over assistance to migrate to a sarge 2.4.27 kernel for example. Also, i would be interested in the reasons why you still run woody now that sarge is up, and your approximate time frame for a woody-sarge migration. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#345918: Possible solution
On Wed, Jan 04, 2006 at 08:30:11PM -0800, Jurij Smakov wrote: Since currently we don't have a clear policy on packaging the kernel modules (even though incidents like this get me more and more motivated to start working on one), I just prepare the python modules in linux-2.6 to provide a reference implementation. I will provide further informations after I finally implemented toolchain dependencies from the config, which is needed for automatic building of modules. it is arguable whether it's a bug of linux-headers or the zaptel-source package. It is one in the linux-headers package. I think we should be flexible and support both ways for installation, especially taking into account that the fix is pretty easy: adding a file 'localversion' containing the string -1-686 to the /usr/src/linux-headers-2.6.15-1-686/ directory fixes the problem. This is already fixed in trunk and should go into 2.6.15-2. Bastian -- The sight of death frightens them [Earthers]. -- Kras the Klingon, Friday's Child, stardate 3497.2 signature.asc Description: Digital signature
Re: mkinitrd problem
Hi Sve, thanks for your advices. In fact mkinitramfs runs better than mkinitrd now i just have an error message during boot, just after uncompressing initrd image: PCI: Failed to allocate I/O resource #7:[EMAIL PROTECTED] for :00:1e.0 but after les than a second my linux starts correctly. i don't know how that boot message is important or dangerous. Max Sven Luther wrote: On Thu, Jan 05, 2006 at 09:19:29AM +0100, Max Gregis wrote: Hello, This is Max from Milan, Italy. I'm trying to compile a new kernel (2.6.14.5) downloaded from kernel.org, of course. I've a Ubunt 5.10 with kernel 2.6.12.10. /me wonders if the ubuntu mailing lists are so unfriendly that you couldn't ask there :) I've created my .config, i've made make...make modulesmake modules_install. So far so good. But when i try to create my initrd.img with mkinitrd, these errors are visualized: In /boot dir i exec mkinitrd -o initrd.img-2.6.14.5 mkinitrd is no more supported for kernels bigger than 2.6.12, please use initramfs-tools or yaird. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346070: linux-image-2.6.15-1-k7: USB sound card stopped working after update to 2.6.15
Package: linux-image-2.6.15-1-k7 Version: 2.6.15-1 Severity: normal After updating to 2.6.15 my USB sound card (m-audio audiophile usb) stopped working. The USB device seems to be recognized as before: dmesg | tail -2 usb 2-1: new full speed USB device using ohci_hcd and address 4 usb 2-1: config 1 interface 5 has no altsetting 3 and snd_usb_audio is loaded. Using lsmod I can't see any difference to the modules loaded before (2.6.14). The device is selectable in the ALSA output plugin of the player as before, and the music player (beep media player) plays without complaining. Still there is no sound :-( . (the sound card uses software volume control, so it shouldn't be the usual mixer problem?) I saw changes in the changelog concerning USB audio, still I don't know how to make it work again. Regards, Florian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-k7 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-k7 recommends: ii libc6-i6862.3.5-11 GNU C Library: Shared libraries [i -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344515: kernel module ip2100 crashes when loading firmware on amd64-system
Hello, the ipw2100 module will be disabled for all architectures but i386 in the next linux-2.6 2.6.15 upload. The driver looks broken on 64bit architectures; if it gets ever fixed, it will be reactivated. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Bug#343686: debsums: checksums mismatch + bug #343048 again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 05 Jan 2006 22:55:07 +0800 LUK ShunTim [EMAIL PROTECTED] wrote: I did *not* cc the bug list as the email is quite large, over 100k. Please do not post me privately about non-secret bugs. I have a strong interest in working in the open. I understand if this can be confusing: Some get furious when you make too much noise in bugreports, others (like me) when you don't. Besides, I did not request those lengthy details - on the contrary I suggested this to be a non-bug. And if you were to play nice with lengthy details for bugreports you could either compress it or put it somewhere on the web and only refer to it with a URL. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDvToPn7DbMsAkQLgRAr/RAKCCwg/vyGsJYxhG5Vu0pK79MUglNACgnxCy ao5PNUFeBecfkyWspgsOxA4= =86+S -END PGP SIGNATURE-
Bug#337974: i2o controller probe failed err -110
Sven: Sven Luther wrote: On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote: Oh, and BTW, this is : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344767 Thanks for all the great feedback! I noticed the BTS for the aforementioned ends with: tags 344739 patch tags 344767 patch Does that mean that the grub in unstable fixes the issue? b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to use initrd command
Jon Miller wrote: I'm attempting to upgrade Debian 3.1 kernel version 2.4 to the latest 2.6 version. I understand I need to add a initrd command somewhere in this. How do I pass this command and when (a link to a document would be a big help). Thanks Jon If you are installing a debian kernel image, apt-get will manage to install any additional needed packages The question the installer comes with, is about the /etc/lilo.conf file: you have to make to find this section : # Boot up Linux by default. # default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 it may look slightly different, but it'll be something like this now, for a debian kernel image it has to become like this # Boot up Linux by default. # default=Linux image=/vmlinuz label=Linux initrd=/initrd.img read-only # restricted # alias=1 it is a good idea to keep a menu item of the existing kernel in there (with image=/vmlinuz.old) to ensure you can boot into your existing kernel in case something is not yet set up proparly with the new one. the /vmlinuz and /vmlinuz.old are usually symlinks to the real kernel image in /boot, like /boot/vmlinuz-2.6.8.051231 - anyway, a file with vmlinuz and a specific version in the name HTH, Joris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346107: linux-image-2.6.15-1-686: missing acpi sleep support
Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Severity: important Hi, after upgrading I am not able to suspend to ram anymore (/proc/acpi/sleep is missing). Suspending was working fine with previous linux-image-2.6.12 Ciao Ciao Marco -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Versions of packages linux-image-2.6.15-1-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.5-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: * linux-image-2.6.15-1-686/preinst/overwriting-modules-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/depmod-error-initrd-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/bootloader-error-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/bootloader-test-error-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-686/preinst/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/abort-install-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/abort-overwrite-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/lilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-dir-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/already-running-this-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/initrd-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/depmod-error-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/create-kimage-link-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/removing-running-kernel-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345934: linux-image-2.6.15-1-686: postinstal failure observed here also
Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Followup-For: Bug #345934 I also noted: -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.15-1-686.postinst line 579. The new kernel is installed and usable, but the package remains listed as partly installed and attempts to complete installation each time I add or update packages with aptitude. Regards, Arthur. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.15-1-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.5-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: linux-image-2.6.15-1-686/preinst/overwriting-modules-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/depmod-error-initrd-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/bootloader-error-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/bootloader-test-error-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-686/preinst/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/abort-install-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/abort-overwrite-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/lilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-dir-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/already-running-this-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/initrd-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/depmod-error-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/create-kimage-link-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/removing-running-kernel-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346107: linux-image-2.6.15-1-686: missing acpi sleep support
* Marco Presi (Zufus) wrote: after upgrading I am not able to suspend to ram anymore (/proc/acpi/sleep is missing). What's wrong with /sys/power/state? Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Suggestion for 2.6.15 or greater kernel revision
Hello: I would like to make a suggestion regarding the configuration of any kernel that is of revision 2.6.15 or greater. The suggestion is that I would like you to please have the kernel configured so that the SATA ATAPI support is on by default. Currently, the 2.6.15 general kernel from www.kernel.org has the default for the SATA ATAPI support set to off. I feel this needs to be changed because there is the possibility that some newer systems will have only a serial SATA ATAPI CD-ROM drive and not a PATA (IDE) CD-ROM drive. In order to be able to install Debian on a system with a SATA ATAPI CD-ROM drive, you would need to have both the installer kernel as well as the operating kernel configured with the SATA ATAPI support set to on. The SATA ATAPI support is set by a variable that is set in the drivers/scsi/libata-core.c file. The variable, atapi_enabled, is set in line 81. Currently the line is: int atapi_enabled = 0; It should be: int atapi_enabled = 1; Thank you. Truly, Mark Allyn
Re: Suggestion for 2.6.15 or greater kernel revision
On Thu, Jan 05, 2006 at 11:34:16AM -0800, Allyn, Mark A wrote: The suggestion is that I would like you to please have the kernel configured so that the SATA ATAPI support is on by default. snipp longrant we'll change it once upstream considers the support to be stable. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346123: linux-image-2.6.15-1-686: modprobe of kernel module asus_acpi failed, gives an oops
Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Severity: normal modprobe of kernel module asus_acpi failed, gives an oops Package: linux-image-2.6.15-1-686 Information from syslog: Jan 5 19:01:13 mogli.reincke.private kernel: Asus Laptop ACPI Extras version 0.29 Jan 5 19:01:13 mogli.reincke.private kernel: Unable to handle kernel NULL pointer dereference at virtual address Jan 5 19:01:13 mogli.reincke.private kernel: printing eip: Jan 5 19:01:13 mogli.reincke.private kernel: e0bc537c Jan 5 19:01:13 mogli.reincke.private kernel: *pde = Jan 5 19:01:13 mogli.reincke.private kernel: Oops: [#1] Jan 5 19:01:13 mogli.reincke.private kernel: Modules linked in: asus_acpi binfmt_misc lp thermal fan button ac battery autofs4 ipv6 nls_iso8859_1 nls_cp437 vfat fat speedstep_centrino freq_table processor cpufreq_ondemand cpufreq_conservative sr_mod sbp2 scsi_mod eth1394 ipw2200 ieee80211 ieee80211_crypt yenta_socket rsrc_nonstatic firmware_class ohci1394 ieee1394 pcmcia_core 8139cp 8139too mii joydev psmouse serio_raw parport_pc parport snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd rtc ehci_hcd i2c_i801 shpchp pci_hotplug ide_cd cdrom intel_agp agpgart i2c_core uhci_hcd soundcore usbcore snd_page_alloc ext3 jbd mbcache ide_disk generic ide_generic piix ide_core evdev mousedev Jan 5 19:01:13 mogli.reincke.private kernel: CPU:0 Jan 5 19:01:13 mogli.reincke.private kernel: EIP:0060:[e0bc537c]Not tainted VLI Jan 5 19:01:13 mogli.reincke.private kernel: EFLAGS: 00010203 (2.6.15-1-686) Jan 5 19:01:13 mogli.reincke.private kernel: EIP is at asus_hotk_get_info+0x184/0x771 [asus_acpi] Jan 5 19:01:13 mogli.reincke.private kernel: eax: d696be00 ebx: dfef3c00 ecx: 0002 edx: 0003 Jan 5 19:01:13 mogli.reincke.private kernel: esi: edi: e0c2eaf0 ebp: d355fa80 esp: c42c9f44 Jan 5 19:01:13 mogli.reincke.private kernel: ds: 007b es: 007b ss: 0068 Jan 5 19:01:13 mogli.reincke.private kernel: Process modprobe (pid: 9692, threadinfo=c42c8000 task=cd529a70) Jan 5 19:01:13 mogli.reincke.private kernel: Stack: 5105 cc48 0010 d355fa80 dfef3c00 e0c2f1ea dfef3c84 Jan 5 19:01:13 mogli.reincke.private kernel: e0bc5a2d dfef3c00 e0c309c0 e0c309c0 c01dbc2b dfef3c00 dfef3c00 Jan 5 19:01:13 mogli.reincke.private kernel: dfef3820 c01dbcc8 dfef3c00 e0c309c0 e0c30aa0 6128 b7ef1b02 c42c8000 Jan 5 19:01:13 mogli.reincke.private kernel: Call Trace: Jan 5 19:01:13 mogli.reincke.private kernel: [e0bc5a2d] asus_hotk_add+0x90/0x14c [asus_acpi] Jan 5 19:01:13 mogli.reincke.private kernel: [c01dbc2b] acpi_bus_driver_init+0x2b/0x4f Jan 5 19:01:13 mogli.reincke.private kernel: [c01dbcc8] acpi_driver_attach+0x39/0x5f Jan 5 19:01:13 mogli.reincke.private kernel: [e0bc5b45] asus_acpi_init+0x5c/0x88 [asus_acpi] Jan 5 19:01:13 mogli.reincke.private kernel: [c0129ee1] sys_init_module+0xa5/0x164 Jan 5 19:01:13 mogli.reincke.private kernel: [c0102a75] syscall_call+0x7/0xb Jan 5 19:01:13 mogli.reincke.private kernel: Code: 08 68 d3 f0 c2 e0 e8 34 0f 55 df 5e 5f a1 f0 0b c3 e0 ba 03 00 00 00 bf f0 ea c2 e0 89 d1 c7 40 14 12 00 00 00 8b 75 08 49 78 08 ac ae 75 08 84 c0 75 f5 31 c0 eb 04 19 c0 0c 01 85 c0 75 11 a1 Jan 5 19:01:55 mogli.reincke.private ntpd[5729]: synchronized to 192.168.100.1, stratum 11 Search on internet gives information about an existing patch: http://www.int21.de/samsung/p30-2.6.14.diff which is also discussed in the folowing thread on lkml http://www.uwsg.iu.edu/hypermail/linux/kernel/0512.1/1751.html -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.15-1-686 depends on: ii module-init-tools 3.2.2-1tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.15-1-686 recommends: pn libc6-i686none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346107: linux-image-2.6.15-1-686: missing acpi sleep support
On Thursday 05 Jan 2006 18:25, Norbert Tretkowski wrote: * Marco Presi (Zufus) wrote: after upgrading I am not able to suspend to ram anymore (/proc/acpi/sleep is missing). What's wrong with /sys/power/state? Currently klaptopdaemon for one only works with /proc/acpi/sleep. In this particular case it seems (Bug#337502) a fix will be coming in the KDE 3.5 packages. -- Jim Hague - [EMAIL PROTECTED] Never trust a computer you can't lift. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346107: linux-image-2.6.15-1-686: missing acpi sleep support
severity 346107 normal reassign 346107 klaptopdaemon merge 337502 346107 thanks * Jim Hague wrote: On Thursday 05 Jan 2006 18:25, Norbert Tretkowski wrote: * Marco Presi (Zufus) wrote: after upgrading I am not able to suspend to ram anymore (/proc/acpi/sleep is missing). What's wrong with /sys/power/state? Currently klaptopdaemon for one only works with /proc/acpi/sleep. In this particular case it seems (Bug#337502) a fix will be coming in the KDE 3.5 packages. Not a kernel bug, reassigning to klaptopdaemon and merging with #337502. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346141: linux-image-2.6.15-1-k7-smp: the package doesn't configure
Package: linux-image-2.6.15-1-k7-smp Version: 2.6.15-0bpo1 Severity: grave Justification: renders package unusable I downloaded this package from backports.org, to install it on a Sarge. I first see the following warning message: -- Configuring linux-image-2.6.15-1-k7-smp You are installing a kernel with an initrd image You are attempting to install an initrd kernel image (version 2.6.15-1-k7-smp) on a machine currently running kernel version 2.4.31-k7-smp. I have been unable to find a suitable tool for generating initrd images (I looked at the list mkinitramfs mkinitrd.yaird) This will break the installation, unless such tools are also being installed right now in the same run. (This means, one from the following list yaird (= 0.0.11-8) | initramfs-tools (= 0.35) | linux-initramfs-tool,) Ok -- Then at console: -- Could not find mkinitramfs mkinitrd.yaird. at /var/lib/dpkg/tmp.ci/preinst line 236, STDIN line 9. Done. Unpacking replacement linux-image-2.6.15-1-k7-smp ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . Setting up linux-image-2.6.15-1-k7-smp (2.6.15-0bpo1) ... Running depmod. Finding valid ramdisk creators. Failed to find suitable ramdisk generation tool for kernel version 2.6.15-1-k7-smp on running kernel 2.4.31-k7-smp in mkinitramfs mkinitrd.yaird dpkg: error processing linux-image-2.6.15-1-k7-smp (--install): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.15-1-k7-smp -- It seems to complain that it can't find mkinitrd.yaird, but I installed yaird from the same source and mkinitrd.yaird is located in /usr/sbin. My /etc/kernel-img.conf is original, it doesn't contain any ramdisk= directive. This is supposed to install fine on a sarge, but it doesn't. Is it a packaging bug, or is there anything (undocumented) missing ? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-k7-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-k7-smp depends on: ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool 0.0.12-2bpo1 Yet Another mkInitRD -- debconf information: linux-image-2.6.15-1-k7-smp/postinst/old-initrd-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/abort-install-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/depmod-error-initrd-2.6.15-1-k7-smp: false linux-image-2.6.15-1-k7-smp/prerm/would-invalidate-boot-loader-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/elilo-initrd-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/bootloader-error-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-k7-smp/postinst/kimage-is-a-directory: linux-image-2.6.15-1-k7-smp/preinst/already-running-this-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/depmod-error-2.6.15-1-k7-smp: false linux-image-2.6.15-1-k7-smp/preinst/abort-overwrite-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/initrd-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/failed-to-move-modules-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/bootloader-initrd-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/overwriting-modules-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/prerm/removing-running-kernel-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/old-dir-initrd-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/create-kimage-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/bootloader-test-error-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/old-system-map-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/lilo-initrd-2.6.15-1-k7-smp: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346141: linux-image-2.6.15-1-k7-smp: the package doesn't configure
reassign 346141 yaird severity 346141 important merge 341524 346141 thanks * Fabien COUTANT wrote: You are attempting to install an initrd kernel image (version 2.6.15-1-k7-smp) on a machine currently running kernel version 2.4.31-k7-smp. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341524 In short, yaird doesn't work on kernel 2.4. Known limitation in yaird, and not a bug in the kernel. As a workaround, update to 2.6.8-2-k7-smp first. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346028: linux-2.6: Hangs while attempting to purge
Sven Luther wrote: Ok, 2.6.15 is arrived. I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then to purge it and the operation failed. But now, it doesn't hang as stated in the bug reports, but fails with an error: Indeed, this is a grub RC bug, which need to fix their grub-update call from /etc/kernel/*.d/grub or whatever scripts. Ok, i have also read the other your mails regards the grub bug. But i would inform you that the /etc/kernel/ folder (that you have requested us to post in the previous messages) doesn't exist on my system... Regards. Cesare. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346028: linux-2.6: Hangs while attempting to purge
On Fri, Jan 06, 2006 at 01:32:13AM +0100, Cesare Leonardi wrote: Sven Luther wrote: Ok, 2.6.15 is arrived. I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then to purge it and the operation failed. But now, it doesn't hang as stated in the bug reports, but fails with an error: Indeed, this is a grub RC bug, which need to fix their grub-update call from /etc/kernel/*.d/grub or whatever scripts. Ok, i have also read the other your mails regards the grub bug. But i would inform you that the /etc/kernel/ folder (that you have requested us to post in the previous messages) doesn't exist on my system... Mmm, then i am out of my depth, and i think it is best you follow up with Manoj, since it is a kernel-package issue. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346141: [Yaird-devel] Bug#346141: linux-image-2.6.15-1-k7-smp: the package doesn't configure
On Thu, Jan 05, 2006 at 04:03:27PM -0800, Steve Langasek wrote: unmerge 346141 reassign 346141 linux-2.6 severity 346141 serious severity 343147 serious merge 346141 343147 thanks On Fri, Jan 06, 2006 at 12:33:53AM +0100, Norbert Tretkowski wrote: reassign 346141 yaird severity 346141 important merge 341524 346141 thanks * Fabien COUTANT wrote: You are attempting to install an initrd kernel image (version 2.6.15-1-k7-smp) on a machine currently running kernel version 2.4.31-k7-smp. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341524 In short, yaird doesn't work on kernel 2.4. Known limitation in yaird, and not a bug in the kernel. As a workaround, update to 2.6.8-2-k7-smp first. Yes, it's a known limitation in yaird, one that isn't likely to be fixed any time soon given that yaird depends heavily on sysfs on the host system. So why do the official 2.6.15 packages in unstable still depend on yaird | initramfs-tools, instead of initramfs-tools | yaird? Marked as serious, because I don't believe it's acceptable to release 2.6 kernels for etch without a clear and automated upgrade path from sarge (i.e., 2.4). svn already has initramfs-tools | yaird, as will 2.6.15-2 when it is uploaded. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346141: [Yaird-devel] Bug#346141: linux-image-2.6.15-1-k7-smp: the package doesn't configure
On Fri, Jan 06, 2006 at 01:48:13AM +0100, Sven Luther wrote: So why do the official 2.6.15 packages in unstable still depend on yaird | initramfs-tools, instead of initramfs-tools | yaird? Marked as serious, because I don't believe it's acceptable to release 2.6 kernels for etch without a clear and automated upgrade path from sarge (i.e., 2.4). svn already has initramfs-tools | yaird, as will 2.6.15-2 when it is uploaded. Ok, an easy closure for the changelog then. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#346159: linux-source-2.6.15.tar.bz2 contains patch log, in file named sven
Package: linux-source-2.6.15 Version: 2.6.15-1 linux-source-2.6.15.tar.bz2 contains a file named sven, which contains a patch application log: $ tar xvvjf /usr/src/linux-source-2.6.15.tar.bz2 [...] -rw-r--r-- root/root 2059 2006-01-03 01:18:51 linux-source-2.6.15/sven [...] $ head linux-source-2.6.15/sven patching file arch/ppc/Kconfig patching file arch/ppc/amiga/Makefile patching file arch/ppc/amiga/amiints.c patching file arch/ppc/amiga/bootinfo.c patching file arch/ppc/amiga/cia.c patching file arch/ppc/amiga/config.c patching file arch/ppc/amiga/time.c patching file arch/ppc/configs/apus_defconfig patching file arch/ppc/kernel/Makefile Hunk #1 succeeded at 353 with fuzz 2. - Josh Triplett signature.asc Description: OpenPGP digital signature
Bug#346161: linux-source-2.6.15: serial card (fourport) stopped working
Package: linux-source-2.6.15 Severity: wishlist I have a fourport serial card, it is correctly detected and configured with the kernel from package linux-image-2.6.12-1-686-smp. The detected ports are ttyS4 - ttyS7 (ttyS0/1 is standard serial ports, ttyS2/3 not assigned). With 2.6.15 it works if the (max) number of serial ports is changed from 4 to 8 in the kernel configuration: CONFIG_SERIAL_8250_NR_UARTS=8 I don't know if this change in behaviour was intended (2.6.12 works with my card when this parameter set to it's default value of 4, 2.6.14 and 2.6.15 don't). -- System Information: Debian Release: potato APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346173: linux-image-2.6.15-1-686: kernel BUG at mm/swap.c:49! (possibly fglrx related)
Package: linux-image-2.6.15-1-686 Version: 2.6.15-1 Severity: normal Since upgrading to kernel 2.6.15 (from 2.6.14) I now get this kernel message consistently when running fgl_glxgears (provided by fglrx driver package) or standard glxgears. It may be an error with the binary fglrx driver, but given the specific reference to mm/swap.c:49 I thought I should post the bug report here. As you can see, below is 4th time since reboot that I ran a GL program: kernel BUG at mm/swap.c:49! invalid operand: [#4] Modules linked in: fglrx binfmt_misc ipv6 nsc_ircc lp button ac battery pcmcia iptable_mangle iptable_nat ip_nat ipt_REJECT ipt_limit ipt_state ip_conntrack nfnetlink ipt_LOG ipt_ULOG iptable_filter ip_tables cpufreq_powersave cpufreq_conservative cpufreq_ondemand acpi_cpufreq freq_table ibm_acpi hdaps nvram joydev evdev ipw2200 irtty_sir sir_dev ieee80211 ieee80211_crypt irda yealink firmware_class crc_ccitt parport_pc parport mousedev yenta_socket rsrc_nonstatic pcmcia_core snd_intel8x0m snd_pcm_oss snd_intel8x0 snd_mixer_oss snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd intel_agp agpgart i2c_i801 shpchp pci_hotplug rtc i2c_core soundcore snd_page_alloc psmouse serio_raw pcspkr floppy usbhid ext3 jbd mbcache ide_cd cdrom ehci_hcd uhci_hcd e1000 usbcore thermal processor fan ide_disk ide_generic piix ide_core CPU:0 EIP:0060:[c01378be]Tainted: PB VLI EFLAGS: 00210256 (2.6.15-1-686) EIP is at put_page+0x4e/0x69 eax: ebx: c16d1c40 ecx: c16d1c40 edx: c16d1c40 esi: f09ea0e0 edi: 0020 ebp: b7438000 esp: f0aadde4 ds: 007b es: 007b ss: 0068 Process fgl_glxgears (pid: 11671, threadinfo=f0aac000 task=f37fc550) Stack: c013b0cf c16d1c40 c16d1c40 dfceb200 b7438000 f27f0b74 b7439000 f27f0b74 c013b219 c031e43c f0ebb1d4 f27f0b74 b7438000 b7439000 f0aade64 f27f0b74 b7438000 f0ebb1d4 b7439000 f0aade98 c013b2cf Call Trace: [c013b0cf] zap_pte_range+0x166/0x1dc [c013b219] unmap_page_range+0xd4/0xe3 [c013b2cf] unmap_vmas+0xa7/0x153 [c013ebe6] exit_mmap+0x4f/0xb3 [c011448a] mmput+0x1c/0x60 [c0117d60] do_exit+0x173/0x2ed [c0117f69] sys_exit_group+0x0/0x11 [c011eb03] get_signal_to_deliver+0x25d/0x26d [c01028be] do_signal+0x52/0xd6 [c0113708] default_wake_function+0x0/0x12 [f8881b5b] ehci_work+0x48/0xa2 [ehci_hcd] [c0124ecd] autoremove_wake_function+0x0/0x3a [c0155d01] do_ioctl+0x45/0x56 [c01476fc] vfs_write+0xaf/0x138 [c0147824] sys_write+0x3b/0x64 [c0102969] do_notify_resume+0x27/0x36 [c0102b06] work_notifysig+0x13/0x19 Code: 00 5b 69 27 c0 83 42 04 ff 0f 98 c0 84 c0 74 35 8b 4a 30 89 54 24 04 ff e1 8b 02 89 d1 f6 c4 40 74 03 8b 4a 0c 8b 41 04 40 75 08 0f 0b 31 00 5b 69 27 c0 83 42 04 ff 0f 98 c0 84 c0 74 07 89 d0 1Fixing recursive fault but reboot is needed! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.48 tools for generating an initramfs ii module-init-tools 3.2.2-1tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.5-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: * linux-image-2.6.15-1-686/preinst/overwriting-modules-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/depmod-error-initrd-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/bootloader-error-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/bootloader-test-error-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-686/preinst/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/abort-install-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/abort-overwrite-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/lilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-dir-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/already-running-this-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/initrd-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/depmod-error-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/create-kimage-link-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/removing-running-kernel-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?
Bug#343686: debsums: checksums mismatch + bug #343048 again
Jonas Smedegaard wrote: On Thu, 05 Jan 2006 22:55:07 +0800 LUK ShunTim [EMAIL PROTECTED] wrote: I did *not* cc the bug list as the email is quite large, over 100k. Please do not post me privately about non-secret bugs. I have a strong interest in working in the open. Hello Jonas, As you said, there is no secret at all. :-) I understand if this can be confusing: Some get furious when you make too much noise in bugreports, others (like me) when you don't. Besides, I did not request those lengthy details - on the contrary I suggested this to be a non-bug. Thanks for your opinion but that's something I, as an ordinary user and reporter of (probable) bugs, not fully competent to judge. And if you were to play nice with lengthy details for bugreports you could either compress it or put it somewhere on the web and only refer to it with a URL. I *have* thought about all these options and I've chosen this course action which IMO is reasonable, under the current circumstances. And I'm sure package maintainers would provide sufficient information to the bug list after the investigation. Your opinion is noted and this will be the last you hear (directly) from me on this topic. Thank you for your patience and good day, ST -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
