Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: important

The xircom_tulip_cb has been completely configured out of the debian
2.6.18 kernel (to the point it's not even commented out in the
/boot/config-2.6.18-4-686 file), presumably as it is sometimes thought
it has been deprecated in favour of the newer xircom_cb (I *think*
xircom_tulip_cb is still in upstream -- at least it was there in the
2.6.18 source I downloaded some time ago).

Unfortunately, xircom_cb doesn't work in a lot of places where
xircom_tulip_cb does.  In my Inspiron 4000 for instance, the newer
driver simply drops packets all over the place, and errors out others.
NFS becomes unusable.  I have found in the past that this card has to
be put over to half duplex mode to make it more reliable (in its
current state, I get better throughput if I connect the machine to a
10MB HD hub, rather than my 10/100 FD switch!).  The xircom_tulip_cb
driver comes with MII abilities and and hence be configured to talk
HD.  The newer driver can't be.  I modprobe mii first before
modprobing xircom_cb, and still nothing.  There's nothing in the
source for the newer driver, whereas there was in the older one (dunno
whether drivers are meant to do their own mii)

I'm not the only person with this problem:

http://lists.infradead.org/pipermail/linux-pcmcia/2005-April/001814.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.2/1049.html
(damn, I remember reading a thread about this in the past, but can't
find it now)

Since the new module is picked by default because of udev/whatever, I
don't think there is any need to explicitly not compile the older
module as a module, particularly since not doing so breaks some
peoples setups.


Please reconsider.

Ta.


-- System Information:
Debian Release: 4.0
  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.18-4-686
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.13     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85f      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.18-4-686 recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false
  linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false
  linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/kimage-is-a-directory:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to