Versions of packages kernel-image-2.6.8-1-k7 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
ii initrd-tools 0.1.73 tools to create initrd image for p
ii module-init-tools 3.1-pre5-6 tools for managing Linux kernel mo
-- no debconf information
On 2 different systems with the same (sid) Debian distribution the
connection speed is limited to (more or less) 100 Kbit/s when using
100 Mbit/s Ethernet cards.
I have tried 2 different network cards on a machine and another card
on a different machine (all 100 Mb/s cards) but with the same result.
When I start the SAME systems (choosing from Lilo boot menu) the kernel
2.6.7-1-k7 all works as expected (connection at 100 Mbit/s), whereas
when I started the kernel 2.6.8-1-k7 the connection is 1000 times slower.
I don't know if the problem is common to the other flavours of the 2.6.8-1
kernel.
Package: kernel- image-2. 6.8-1-k7
Version: 2.6.8-1
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=C
Versions of packages kernel- image-2. 6.8-1-k7 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
ii initrd-tools 0.1.73 tools to create initrd image for p
ii module-init-tools 3.1-pre5-6 tools for managing Linux kernel mo
-- no debconf information
On 2 different systems with the same (sid) Debian distribution the
connection speed is limited to (more or less) 100 Kbit/s when using
100 Mbit/s Ethernet cards.
I have tried 2 different network cards on a machine and another card
on a different machine (all 100 Mb/s cards) but with the same result.
When I start the SAME systems (choosing from Lilo boot menu) the kernel
2.6.7-1-k7 all works as expected (connection at 100 Mbit/s), whereas
when I started the kernel 2.6.8-1-k7 the connection is 1000 times slower.
I don't know if the problem is common to the other flavours of the 2.6.8-1
kernel.
Thank you,
Arcangelo Labianca
<email address hidden>, <email address hidden>