Processed: Merge
Processing commands for [EMAIL PROTECTED]: forcemerge 347914 383534 Bug#347914: linux-image-2.6.14-2-686: Cannot purge config files while removing Bug#383534: linux-image-2.6.14-2-k7: can't purge cleanly Bug#365109: dpkg --purge linux-image-xx always fails. Forcibly Merged 347914 365109 383534. 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]
Updating linux-2.6 in testing (to 2.6.17)
Hi, 3 days ago Frederik Schueler mentioned the following item for then's today in his Kernel schedule proposal for Etch: start migration of 2.6.17 kernel and udebs to testing I asked him on #d-kernel precisely what was being done about this but got no answer. I didn't see anything happen and currently linux-2.6 is still frozen. Today I saw a linux-2.6.16 upload, which I found suspicious since I can't see its use if 2.6.17 is about to transition to testing. I mentioned this on #d-release, and resulting discussion with vorlon made me realize that it's possible that the Linux team wouldn't necessarily feel responsible for requesting a linux-2.6 update, as according to him, the reason it was frozen in the first place was to keep 2.6.17 from clobbering 2.6.16 in etch before beta3. Since I'm afraid that the Linux team isn't doing anything to update linux-2.6 in testing and that nothing else feels responsible for doing so, I'm initiating the discussion. I request the release team to force a linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are raised until then. If you have an objection, please raise it on debian-release only (dropping d-boot and d-kernel). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Updating linux-2.6 in testing (to 2.6.17)
On Sat, Aug 19, 2006 at 03:04:08AM -0400, Filipus Klutiero wrote: Since I'm afraid that the Linux team isn't doing anything to update linux-2.6 in testing and that nothing else feels responsible for doing so, I'm initiating the discussion. I request the release team to force a linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are raised until then. I certainly won't be doing this; someone needs instead to show me that it's safe and correct to push linux-2.6 in at this time, and to either address or account for the RC bugs currently listed as open against linux-2.6. -- 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#383730: initramfs-tools: incompatible with udev 0.097-1
hello vagrant, thanks for feedback. On Fri, Aug 18, 2006 at 05:33:05PM -0700, Vagrant Cascadian wrote: well, happy to try out the shiny new ltsp packages, it seems like there may be an incompatibility with initramfs-tools and the new udev: Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/thermal.ko): No such device this is usual in qemu as it has no acpi support. udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek those are harmless. with many more similar lines. i tested it with udev 0.093-1 from etch, and that seemed to work just fine. thanks for all your work on initramfs-tools! :) you may want to look at 383555, fixed klibc is on mentors. oh, you might want to know i booted using: qemu -hda /dev/zero -m 100 -kernel /opt/ltsp/i386/boot/vmlinuz -initrd \ /opt/ltsp/i386/boot/initrd.img \ -nographic \ -append 'nfsroot=10.0.2.2:/opt/ltsp/i386 root=/dev/nfs ip=dhcp console=ttyS0,38400' hehe, that looks like a patched initramfs-tools? :) btw i looked at your nfs patches they make have usage of busybox, aka cut. i'd prefer the core to be klibc clean, so i couldn't just merge them, need to check how it can be done with klibc-utils only. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383743: pointer doesn't work
hello bdale, On Fri, Aug 18, 2006 at 11:01:42PM -0600, Bdale Garbee wrote: Upgrading to this kernel version on my HP nc6220 notebook left me with a completely non-working pointer in X. Tried various things, didn't really learn anything useful before getting frustrated and falling back to a prior kernel version, which works fine. Looked like there was no input from the mouse driver at all, though? Bdale isn't that the latest udev regression, which udev version are you running? you need either latest klibc 1.4.19-2 from mentors (hope it will land soon) or fix /usr/share/initramfs-tools/scripts/init-bottom/udev by using rm -rf instead of nuke. then rebuild initramfs: update-initramfs -u -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, Aug 18, 2006 at 07:46:56PM -0400, Nathanael Nerode wrote: Sven Luther wrote: On Thu, Aug 17, 2006 at 10:07:42AM -0700, [EMAIL PROTECTED] wrote: Maks - On Thu, Aug 17, 2006 at 06:05:30PM +0200, maximilian attems wrote: Something about [bug #242866] seems broken, however, because RC-buggy linux-2.6 packages keep making it into testing. Is it obvious how to keep this from happening, without starting a new bug attached to linux-2.6? if you feel like it reassign it, Bugs merged and assigned to linux-2.6. Thanks, I think the kernel pseudo-package is mostly obsolete: it should be reserved for bugs affecting multiple kernels. This bug doesn't affect freebsd, hurd, etc. It does affect linux-2.4 and linux-2.2, but those are scheduled for removal before etch anyway. So actually, I'd like to suggest running through the bugs against 'kernel' and reassigning them to linux-2.6 or closing them as appropriate. Does that seem like a reasonable thing to do when I'm bored and not feeling up to programming, or would there be some complaint about it. Yes, it is the best thing. We should also ask the BTS admin's to assign new bugs to kernel pseudo package directly to linux-2.6, this is i believe possible. snip anyway if you want to improve the legal situtation use: http://wiki.debian.org/KernelFirmwareLicensing dilinger succeeded in various firmware relicensing thanks to his quest to the vendors. feel free to pick up. Broadcom tg3 relicensing alone took over two years. This is a lovely thing to do, and I am *very very* impressed with dilinger's diligence and his success (I tried but failed to contact anyone at Broadcom). dgrs I have to disagree on this, between the moment i contacted broadcom, and the solution, there was at most 2-3 months or so. and qla2xxx are the only other drivers he had *any* success with, according to the wiki page. I am afraid we need a shorter-term solution. Well, we didn't really pursue any of the other drivers. That makes 3 out of 3 we really pursued though, and they can all be handled in parallel. The real problem is stuff like the acenic driver, where the copyright holder is lost. Altough we could try to gather a position statement by various possible copyright holders, where they claim not to hold copyright of this part, or something and then add this and wait until someone complains, showing our good faith and best effort, and then asking whoever complains to clarify the copyright. For each offending file, there are three possible solutions: 1. Get the author to release source code under a DFSG-free license 2. Move the firmware to non-free, patching the driver to use request_firmware() 3. Delete the driver and firmware entirely. 4. Move the whole friver to non-free, without major patching. 5. Reverse engineer the needed firmware, and create a trully free driver. AFAIK, the best outcome yet from the relicensing discussions on http://wiki.debian.org/KernelFirmwareLicensing is to properly permit the redistribution of the binary, without source code. Indeed, but even that was laughed at back then when we started at it, and you should have seen the reaction of LKML when i mentioned it there. Not to mention the reaction I originally got from the netdev maintainers, which was rather more hostile than being 'laughed at'. I think a lot of Err, i was laughed at by some people here, the LKML was indeed a bit more hostile than that. people genuinely believed that you could license an unsourced binary under the GPL I can't imagine *why* they believed that, though. snip That's fine for debian non-free, and a necessary step for making option (2) above work properly. Until and unless the entire Linux kernel is moved to non-free, such relicensing doesn't solve the fundamental bug. Indeed. I agree that option (3) is bad, but I still recommend it for the short term. It's the quickest path to a legal and For the short term, 4. is a better solution. Right. If a driver really can't build out-of-tree comfortably, (4) may not be feasible and (3) or (2) may be necessary, but let's cross that bridge if we come to it. What can I do to help with (4)? :-) SC-conforming Linux release, and it will bring people out of the closet to volunteer to work on (2). I think (2) is the actual goal, but maybe not one that can be finished before the proposed etch freeze -- especially since most of the blobs need to be relicensed before they can be made part of firmware-nonfree. Indeed, which is because we could also consider : 6. Pass another GR to allow debian/etch to release as is, provided we If the GR includes a commitment to include a statement regarding this violation of the SC in the *release notes*, then I would be satisfied with this from a freeness point of view: at least Debian would be advertising its failure to
Processed: merging 383403 242866
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 merge 383403 242866 Bug#242866: drivers containing firmware blobs Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Bug#243022: ymfpci_image.h: Sourceless microcode without permission to redistribute Merged 242866 243022 383403. 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 383403
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 tags 383403 - confirmed Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: upstream sid d-i etch confirmed help sarge-ignore Bug#242866: drivers containing firmware blobs Bug#243022: ymfpci_image.h: Sourceless microcode without permission to redistribute Tags removed: confirmed 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#383725: linux-image-2.6.16-2-686: 2.6.17 works
Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Followup-For: Bug #383725 I confirm that 2.6.17 is not affected by this bug. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 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#383730: initramfs-tools: incompatible with udev 0.097-1
udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek those are harmless. I am getting the same thing. Furthermore X fails to start, reporting that it cannot find the mouse at /dev/input/mice. I then have to restart udev, unplug the mouse(usb) and plug it in again, and /etc/init.d/ kdm restart This gets me into X, however the audio device is also not found, so no sound. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383725: marked as done (linux-image-2.6.16-2-686: cannot halt properly Thinkpad T22)
Your message dated Sat, 19 Aug 2006 14:39:02 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#383725: linux-image-2.6.16-2-686: 2.6.17 works has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Severity: normal Hello, I see a clear regression here after upgrading from 2.6.15 to 2.6.16. The kernel now doesn't shutdown cleanly the power on my laptop, a IBM Thinkpad T22. It used to work real nice on 2.6.15, but now, the machine just sits there after the Shutting down drives: sda (probably not the exact wording, i don't clearly remember, but it's usually the last thing on the console before the shutdown). I can safely poweroff the machine by pressing the power key for 5 seconds, but it's a bit annoying. Usually, i just suspend to disk this machine, using an ugly hack (echo disk /sys/power/state). This is also affect in that I need to poweroff the same way as a shutdown, ie. by pressing the power key. The machine resumes as normal. Available for debugging/testing with right tools/instructions... a. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true ---End Message--- ---BeginMessage--- On Sat, Aug 19, 2006 at 01:54:59PM +0200, The Anarcat wrote: Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Followup-For: Bug #383725 I confirm that 2.6.17 is not affected by this bug. thanks for verification, thus closing bug report. -- maks ---End Message---
Bug#383730: initramfs-tools: incompatible with udev 0.097-1
On Sat, Aug 19, 2006 at 10:23:36PM +1000, Ben Hay wrote: udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek those are harmless. I am getting the same thing. Furthermore X fails to start, reporting that it cannot find the mouse at /dev/input/mice. I then have to restart udev, unplug the mouse(usb) and plug it in again, and /etc/init.d/ kdm restart This gets me into X, however the audio device is also not found, so no sound. repeating myself: install latest libklibc and klibc-utils from incoming.debian.org, than regenerate your initramfs with update-initramfs -u best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Updating linux-2.6 in testing (to 2.6.17)
On Sat, Aug 19, 2006 at 03:04:08AM -0400, Filipus Klutiero wrote: Hi, 3 days ago Frederik Schueler mentioned the following item for then's today in his Kernel schedule proposal for Etch: start migration of 2.6.17 kernel and udebs to testing snip/ Since I'm afraid that the Linux team isn't doing anything to update linux-2.6 in testing and that nothing else feels responsible for doing so, I'm initiating the discussion. I request the release team to force a linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are raised until then. If you have an objection, please raise it on debian-release only (dropping d-boot and d-kernel). Being afraid is normal behaviour when _no_ informatiion is available. A common reason for not providing information is we are working on it. In other words: A discussion to force a release does not help. Things that do help: * Find a way to help * Find out what the current status is * Find out where to see progress HtH Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383743: pointer doesn't work
On Sat, 2006-08-19 at 10:07 +0200, maximilian attems wrote: isn't that the latest udev regression, which udev version are you running? Don't know. My udev version is 0.097-1 you need either latest klibc 1.4.19-2 from mentors (hope it will land soon) or fix /usr/share/initramfs-tools/scripts/init-bottom/udev by using rm -rf instead of nuke. then rebuild initramfs: update-initramfs -u Yep, the edit and rebuilt initramfs option fixed the problem. Thanks! Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383730: initramfs-tools: incompatible with udev 0.097-1
On Sat, Aug 19, 2006 at 10:11:10AM +0200, maximilian attems wrote: hello vagrant, thanks for feedback. of course :) On Fri, Aug 18, 2006 at 05:33:05PM -0700, Vagrant Cascadian wrote: well, happy to try out the shiny new ltsp packages, it seems like there may be an incompatibility with initramfs-tools and the new udev: Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/thermal.ko): No such device this is usual in qemu as it has no acpi support. oh, i've been ignoring that one for so long i didn't even see it :) udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek those are harmless. ok... with many more similar lines. i tested it with udev 0.093-1 from etch, and that seemed to work just fine. thanks for all your work on initramfs-tools! :) you may want to look at 383555, fixed klibc is on mentors. i didn't find the klibc packages(just sources), but switching the nuke command with rm -rf seemed to work for me, as suggested in the bug report. oh, you might want to know i booted using: qemu -hda /dev/zero -m 100 -kernel /opt/ltsp/i386/boot/vmlinuz -initrd \ /opt/ltsp/i386/boot/initrd.img \ -nographic \ -append 'nfsroot=10.0.2.2:/opt/ltsp/i386 root=/dev/nfs ip=dhcp console=ttyS0,38400' hehe, that looks like a patched initramfs-tools? :) no, it selects BOOT=nfs using a conf.d snippet for ltsp, but the extra root/ip options don't seem to break anything. the console option works fine, too. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383629: marked as done (linux-image-2.6.17-2-686: ipw2200 module cannot load its firmware)
Your message dated Sat, 19 Aug 2006 17:33:52 +0200 with message-id [EMAIL PROTECTED] and subject line Duplicate #383555 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: normal When I run 'modprobe ipw2200' I have this output in /var/log/messages: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1 ipw2200: Copyright(c) 2003-2006 Intel Corporation ACPI: PCI Interrupt :02:02.0[A] - GSI 18 (level, low) - IRQ 201 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 ipw2200: Unable to load firmware: -2 ipw2200: failed to register network device ACPI: PCI interrupt for device :02:02.0 disabled ipw2200: probe of :02:02.0 failed with error -5 The ipw2200 firmware 3.0 is installed in /lib/firmware and it was working with linux-image-2.6.17-1-686. Regards, -- 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.17-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.74 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-17 Yet Another mkInitRD Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-2 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: * linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: ---End Message--- ---BeginMessage--- Duplicate #383555 thanks -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales ---End Message---
Bug#380649: initramfs-tools: new patch for nfsroot= handling
Package: initramfs-tools
Version: 0.75
Followup-For: Bug #380649
attached patch should use plain ol' shell parameter expansion instead of
cut to support the more complete nfsroot handling.
also available in my bzr branch, amongst the other patches:
http://llama.freegeek.org/~vagrant/bzr-archives/initramfs-tools/vagrant-initramfs-tools
live well,
vagrant
--- scripts/nfs 2006-08-19 10:54:48.0 -0400
+++ ../vagrant-initramfs-tools/scripts/nfs 2006-08-19 10:37:12.0
-0400
@@ -17,6 +17,17 @@
. /tmp/net-${DEVICE}.conf
if [ x${NFSROOT} = xauto ]; then
NFSROOT=${ROOTSERVER}:${ROOTPATH}
+ elif [ x${NFSROOT} != x ]; then
+ # support nfsroot option from linux sources
Documentation/nfsroot.txt:
+ # nfsroot=[server-ip:]root-dir[,nfs-options]
+ if [ x${NFSOPTS} = x ]; then
+ NFSOPTS=-o ${NFSROOT#*,}
+ fi
+ NFSROOT=${NFSROOT%%,*}
+ if [ ${NFSROOT#*:} = $NFSROOT ]; then
+ # get rootserver from dhcp
+ NFSROOT=${ROOTSERVER}:${NFSROOT}
+ fi
fi
if [ x${NFSOPTS} = x ]; then
Bug#380649: initramfs-tools: new new patch for nfsroot= handling
sorry, i failed to test one of the cases, this patch should fix it.
really.
still need to implement the ip= options... will work on that another
day.
live well,
vagrant
--- scripts/nfs 2006-08-19 12:36:07.0 -0400
+++ ../vagrant-initramfs-tools/scripts/nfs 2006-08-19 12:33:53.0
-0400
@@ -17,6 +17,17 @@
. /tmp/net-${DEVICE}.conf
if [ x${NFSROOT} = xauto ]; then
NFSROOT=${ROOTSERVER}:${ROOTPATH}
+ elif [ x${NFSROOT} != x ]; then
+ # support nfsroot option from linux sources
Documentation/nfsroot.txt:
+ # nfsroot=[server-ip:]root-dir[,nfs-options]
+ if [ x${NFSOPTS} = x ] [ ${NFSROOT#*,} != ${NFSROOT}
] ; then
+ NFSOPTS=-o ${NFSROOT#*,}
+ fi
+ NFSROOT=${NFSROOT%%,*}
+ if [ ${NFSROOT#*:} = $NFSROOT ]; then
+ # get rootserver from dhcp
+ NFSROOT=${ROOTSERVER}:${NFSROOT}
+ fi
fi
if [ x${NFSOPTS} = x ]; then
Bug#383743: marked as done (pointer doesn't work)
Your message dated Sat, 19 Aug 2006 19:52:14 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#383743: pointer doesn't work has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: important Upgrading to this kernel version on my HP nc6220 notebook left me with a completely non-working pointer in X. Tried various things, didn't really learn anything useful before getting frustrated and falling back to a prior kernel version, which works fine. Looked like there was no input from the mouse driver at all, though? Bdale ---End Message--- ---BeginMessage--- On Sat, Aug 19, 2006 at 08:03:22AM -0600, Bdale Garbee wrote: On Sat, 2006-08-19 at 10:07 +0200, maximilian attems wrote: isn't that the latest udev regression, which udev version are you running? Don't know. My udev version is 0.097-1 you need either latest klibc 1.4.19-2 from mentors (hope it will land soon) or fix /usr/share/initramfs-tools/scripts/init-bottom/udev by using rm -rf instead of nuke. then rebuild initramfs: update-initramfs -u Yep, the edit and rebuilt initramfs option fixed the problem. Thanks! Bdale ok thanks for the confirmation that this a dup of 383555, fixed by klibc from incoming, which should hit unstable soonest. thus closing. best regards -- maks ---End Message---
Processed: retitle 383481 to nvidiafb contains obfuscated source code, DFSG violation?
Processing commands for [EMAIL PROTECTED]: retitle 383481 nvidiafb contains obfuscated source code, DFSG violation? Bug#383481: nvidiafb is not in the preferred form of modification either Changed Bug title. 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: Re: Bug#383807: Missing PCI IDs in the sata_via driver
Processing commands for [EMAIL PROTECTED]: reassign 383807 linux-2.6 Bug#383807: Missing PCI IDs in the sata_via driver Bug reassigned from package `linux-2.6' to `linux-2.6'. thanks 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#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
On Fri, Aug 18, 2006 at 04:18:58PM -0700, James Bottomley wrote: On Fri, 2006-08-18 at 12:39 -0400, Kyle McMartin wrote: The problem is because they both claim support for the same PCI Ids: That's this fix, isn't it? http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=b2b3c121076961333977f485f0d54c22121df920 James added the stable Maintainers to cc, please consider this patch for the next revision. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#383807: Missing PCI IDs in the sata_via driver
Processing commands for [EMAIL PROTECTED]: reassign 383807 linux-2.6 Bug#383807: Missing PCI IDs in the sata_via driver Bug reassigned from package `installation-reports' to `linux-2.6'. thanks 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]
Re: Bug#383807: Missing PCI IDs in the sata_via driver
reassign 383807 linux-2.6
thanks
On Saturday 19 August 2006 19:46, Julien Louis wrote:
I was unable to install Debian from both daily build d-i iso image and
etch d-i beta3 release due to missing PCI IDs in the sata_via driver.
Can you consider adding the following pci id to the sata_via driver :
1106:0591
The ubuntu dapper kernel include them and seems to work fine with the
following line :
{ 0x1106, 0x0591, PCI_ANY_ID, PCI_ANY_ID, 0, 0, vt6420 },
pgpdGAofcKgMf.pgp
Description: PGP signature
Bug#383849: linux-image-2.6.16-2-686: Problem with atkbd.c
Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Severity: important When i use the i8k module for Dell Latitude laptops with this kernel and 2.6.17 and move the mouse or press a key i'm getting a lot of errors like this: Jul 30 16:01:13 localhost kernel: atkbd.c: Use 'setkeycodes 00 keycode' to make it known. Jul 30 16:01:13 localhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). Jul 30 16:01:13 localhost kernel: atkbd.c: Use 'setkeycodes 00 keycode' to make it known. Jul 30 16:01:13 localhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). Jul 30 16:01:13 localhost kernel: atkbd.c: Use 'setkeycodes 00 keycode' to make it known. And the machine becomes unusable. The module works fine in 2.6.8-2-686 -- System Information: Debian Release: testing APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=es_CO, LC_CTYPE=es_CO (charmap=ISO-8859-1) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.72 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: pn libc6-i686none (no description available) -- debconf information: linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kingston pendrive does not work in Debian
On Sun, Jun 18, 2006 at 10:42:54PM +0200, Laszlo Boszormenyi wrote: On Sun, 2006-06-18 at 21:53 +0200, [EMAIL PROTECTED] wrote: Package: kernel Version: Which version do you use? Own or from package? Thanks Laszlo. The kernel.org bug report says Debian's 2.6.15. Tomek: Can you try the 2.6.16 kernel from sid to see if the problem goes away? I'm unaware of any patches in the Debian kernel that are likely to change this behavior. -- dann frazier Hi. Sorry for replying so late, but I've just noticed that someone replied to my mail... (I should have subscribed to the list, now I have) I have now the 2.6.16-2 kernel (from testing) and the problem went away:) but I have also a 2.6.17.4 from kernel.org (which I prefer to use as my graphics card's driver does not work properly with kernels 2.6.17) and the problem is present with this kernel... So maby it is a kernel configuration problem, which maby have changed from 2.6.15 to 2.6.16 in debian's kernels? And I don't remember which config file I used (the one from debian's 2.6.15 or from debian's 2.6.16) to generate the configuration for 2.6.17.4. I will try 2.6.17.9 (as it is the newest) with the kernel config from debians 2.6.16 and let you know about the results. Tomek Kazmierczak >On Sun, Jun 18, 2006 at 10:42:54PM +0200, Laszlo Boszormenyi wrote: > On Sun, 2006-06-18 at 21:53 +0200, [EMAIL PROTECTED] wrote: > > Package: kernel > > Version: > Which version do you use? Own or from package? >Thanks Laszlo. >The kernel.org bug report says Debian's 2.6.15. >Tomek: Can you try the 2.6.16 kernel from sid to see if the problem >goes away? I'm unaware of any patches in the Debian kernel that are >likely to change this behavior. >-- >dann frazier Hi. Sorry for replying so late, but I've just noticed that someone replied to my mail... (I should have subscribed to the list i think...) I have now the 2.6.16-2 kernel (from testing) and the problem went away:) but I have also a 2.6.17.4 from kernel.org (which I prefer to use as my graphics card's driver does not work properly with kernels < 2.6.17) and the problem is present with this kernel... So maby it is a kernel configuration problem, which maby have changed from 2.6.15 to 2.6.16 in debian's kernels? And I don't remember which config file I used (the one from debian's 2.6.15 or from debian's 2.6.16) to generate the configuration for 2.6.17.4. I will try 2.6.17.9 (as it is the newest) with the kernel config from debians 2.6.16 and let you know about the results. Tomek Kazmierczak
Re: remove unused 2.4 images
On Fri, Aug 18, 2006 at 06:55:26PM +0200, maximilian attems wrote: retitle 376771 RM: kernel-image-2.4.27-2-* -- RoM thanks in accordance with the d-i team any 2.4 kernel-image package can be removed from unstable for all archs except i386 and m68k (both legacy archs :-P) this includes the following list of kernel-images: Package kernel-image-2.4.27-2-s390 Package kernel-image-2.4.27-2-s390-di Package kernel-image-2.4.27-2-s390-tape Package kernel-image-2.4.27-2-s390-tape-di Package kernel-image-2.4.27-2-s390x Package kernel-image-2.4.27-2-sparc32 Package kernel-image-2.4.27-2-sparc32-di Package kernel-image-2.4.27-2-sparc32-smp Package kernel-image-2.4.27-2-sparc64 Package kernel-image-2.4.27-2-sparc64-di Package kernel-image-2.4.27-2-sparc64-smp Package kernel-image-2.4.27-bast Package kernel-image-2.4.27-bast-di Package kernel-image-2.4.27-lart Package kernel-image-2.4.27-lart-di Package kernel-image-2.4.27-netwinder Package kernel-image-2.4.27-netwinder-di Package kernel-image-2.4.27-r3k-kn02 Package kernel-image-2.4.27-r3k-kn02-di Package kernel-image-2.4.27-r4k-ip22 Package kernel-image-2.4.27-r4k-ip22-di Package kernel-image-2.4.27-r4k-kn04 Package kernel-image-2.4.27-r4k-kn04-di Package kernel-image-2.4.27-r5k-cobalt Package kernel-image-2.4.27-r5k-cobalt-di Package kernel-image-2.4.27-r5k-ip22 Package kernel-image-2.4.27-r5k-ip22-di Package kernel-image-2.4.27-r5k-lasat Package kernel-image-2.4.27-riscpc Package kernel-image-2.4.27-riscstation Package kernel-image-2.4.27-sb1-swarm-bn Package kernel-image-2.4.27-sb1-swarm-bn-di Package kernel-image-2.4.27-xxs1500 the following meta packages: Package kernel-image-2.4-generic Package kernel-image-2.4-s390 Package kernel-image-2.4-s390x Package kernel-image-2.4-smp Package kernel-image-2.4-sparc32 Package kernel-image-2.4-sparc32-smp Package kernel-image-2.4-sparc64 Package kernel-image-2.4-sparc64-smp I assume this also includes: kernel-patch-2.4.27-s390 | 2.4.27-2 | unstable | source, all the -di packages were already included in #383546, the arm image in #383553, and so was the, here unmentioned, arm patch. kernel-patch-2.4.27-mips is also not mentioned? And what to do with kernel-patch-2.4.27-apus, kernel-patch-2.4-fasttraks150, kernel-patch-2.4-grsecurity and kernel-patch-2.4-lowlatency? So, you mention (excluding those packages already removed), source-package based: kernel-image-2.4.27-s390 kernel-image-2.4.27-sparc kernel-latest-2.4-alpha kernel-latest-2.4-s390 kernel-latest-2.4-sparc kernel-patch-2.4.27-mips I assume you also mean: kernel-patch-2.4.27-s390 kernel-patch-2.4.27-mips And I have no idea about: kernel-patch-2.4.27-apus kernel-patch-2.4-fasttraks150 kernel-patch-2.4-grsecurity kernel-patch-2.4-lowlatency Can you please provide a complete list, or if the original list *was* complete, confirm that? --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: remove unused 2.4 images
On Sun, 2006-08-20 at 04:12 +0200, Jeroen van Wolffelaar wrote: And I have no idea about: kernel-patch-2.4.27-apus kernel-patch-2.4-fasttraks150 kernel-patch-2.4-grsecurity kernel-patch-2.4-lowlatency I'm the maintainer of kernel-patch-2.4-grsecurity , and it should be removed too. Will file a RoM somewhen. Regards, Laszlo/GCS signature.asc Description: This is a digitally signed message part
