Your message dated Wed, 31 Dec 2008 18:25:15 +0100 with message-id <[email protected]> and subject line Re: Bug#510191: linux-image-2.6.26-1-686: madwifi compiles and works perfectly on 2.6.18 but same source fails on 2.6.26 has caused the Debian Bug report #510191, regarding linux-image-2.6.26-1-686: madwifi compiles and works perfectly on 2.6.18 but same source fails on 2.6.26 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.) -- 510191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510191 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Severity: important madwifi source code hasn't changed in 18 months: works perfectly under 2.6.18-4-686, sets up wifi0 etc. etc. and yet exactly the same source fails miserably under 2.6.26-1-686 lspci -v: 03:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01) Subsystem: Askey Computer Corp. Unknown device 7108 Flags: bus master, fast devsel, latency 0, IRQ 169 Memory at b8000000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [60] Express Legacy Endpoint IRQ 0 Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel /var/log/kern.log shows that - i _think_ - under 2.6.26 - that ath5k_pci detects the device as phy0: Dec 30 04:10:07 q1 kernel: [ 10.266466] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 Dec 30 04:10:07 q1 kernel: [ 10.266654] PCI: Setting latency timer of device 0000:03:00.0 to 64 Dec 30 04:10:07 q1 kernel: [ 10.266775] ath5k_pci 0000:03:00.0: registered as 'phy0' Dec 30 04:10:07 q1 kernel: [ 11.062370] phy0: Selected rate control algorithm 'pid' Dec 30 04:10:07 q1 kernel: [ 11.549065] ath5k phy0: Atheros AR2424 chip found (MAC: 0xa0, PHY: 0x61) that's all you get. under 2.6.26... wait.... ath_hal doesn't look like it's being loaded.... will provide further info in a follow-up report. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii initramfs-tools [linux-initra 0.87b tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i686 2.7-16 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-27 GRand Unified Bootloader pn linux-doc-2.6.26 <none> (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:
--- End Message ---
--- Begin Message ---On Tue, Dec 30, 2008 at 06:36:34PM +0000, lkcl wrote: > madwifi source code hasn't changed in 18 months: works perfectly under > 2.6.18-4-686, sets up wifi0 etc. etc. and yet exactly the same source > fails miserably under 2.6.26-1-686 Linux kernels are not for-/backward compatible on the source level. If you need that, use the published _userspace_ interfaces. Closing as no bug. Bastian -- He's dead, Jim. -- McCoy, "The Devil in the Dark", stardate 3196.1
--- End Message ---
