Bug#464733: marked as done (linux-image-2.6.24-1-686: ipw2200 not working after upgrading from 2.6.24-2 to 2.6.24-3.)
Your message dated Tue, 12 Feb 2008 01:49:08 +0100
with message-id <20080212004908.GI5198@stro.at>
and subject line Re: Bug#464733: linux-image-2.6.24-1-686: ipw2200 not working after upgrading from 2.6.24-2 to 2.6.24-3.
has caused the Debian Bug report #464733,
regarding linux-image-2.6.24-1-686: ipw2200 not working after upgrading from 2.6.24-2 to 2.6.24-3.
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 owner@bugs.debian.org
immediately.)
--
464733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464733
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-686
Version: 2.6.24-3
Severity: important
After upgrading from 2.6.24-2 to 2.6.24-3 the following errors appears
if ipw2200 module has tryed to be loaded:
kernel: ipw2200: Failed to send TX_POWER: Command timed out.
last message repeated 4 times
kernel: ipw2200: Unable to initialize device after 5 attempts.
kernel: ipw2200: failed to register network device
kernel: ACPI: PCI interrupt for device 0000:02:04.0 disabled
kernel: ipw2200: probe of 0000:02:04.0 failed with error -5
So, my WiFi card come to be completely unusable.
Rollback to 2.6.24-2 kernel for some (unknown) reason does not helps.
Rollback to 2.6.23 image resolve the TX_POWER issue.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (300, 'stable'), (200, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=UTF-8) (ignored: LC_ALL set to ru_RU.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.24-1-686 depends on:
ii debconf [debconf-2.0] 1.5.18 Debian configuration management sy
ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-24 Yet Another mkInitRD
Versions of packages linux-image-2.6.24-1-686 recommends:
ii libc6-i686 2.7-6 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686:
linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/kimage-is-a-directory:
--- End Message ---
--- Begin Message ---
On Tue, 12 Feb 2008, Nikolay Panov wrote:
> > is that reproducible with 2.6.24-4 ?
> No, 2.6.24-4 works well.
ok cool, closing.
> > also please don't use reportbug-ng it omits vital info,
> > please stick to reportbug.
>
> I've used reportbug:
>
> [2:54 /]$ dpkg -l reportbug-ng
> No packages found matching reportbug-ng.
> [2:54 /]$ dpkg -l reportbug | tail -n 1
> ii reportbug
> 3.39 reports bugs in the Debian
> distribution
ok cool, strange you had no lsmod or dmesg attached,
anyway thanks for your report.
--- End Message ---
Reply to: