On Wed, May 5, 2010 at 10:41 AM, Frans Pop <elen...@planet.nl> wrote:
> reassign 580265 linux-2.6 2.6.32-9
> thanks
>
> On Tuesday 04 May 2010, Gmail Notifier wrote:
>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
>> Network Connection [8086:10f0] (rev 06)
>>         Subsystem: Intel Corporation Device [8086:0037]
>>         Kernel driver in use: e1000e
>>
>> Comments/Problems:
>>
>> Did not find my e1000e network interface, even after selecting it
>> explicitly from the list. After installing without using a net
>> connection, a simple "modprobe e1000e" and "dhclient" made the net
>> connection work. The following were added automaticly to /etc/modules
>> by the installation:
>>
>> e100
>> e1000
>> e1000e
>>
>> But booting with these in /etc/modules did not make the network
>> interface work. Had to do "modprobe e1000e" manually after each boot.
>
> This sounds like a kernel issue. Reassigning to the kernel team.
>
> Cheers,
> FJP
>

I have a correction to make, it was only the DHCP part that didn't
work when booting into the installed kernel. The e1000e driver is
loaded correctly, and the other (incorrect) drivers can't be seen when
doing "lsmod". The detection in the installation is still broken
though.

If it's any help, the installed kernel is 2.6.32-trunk-amd64, and the
one used on the USB key is 2.6.30-2-amd64. The network also worked
fine with the installed kernel being 2.6.32-3-amd64. I remember
reading that Linus and Molnar had problems with this driver in one of
the latest kernels, maybe updating the USB key kernel would fix it.

When making the USB key I used the boot.img.gz from
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
and the netinstall image
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/k2w63ae10171005050312y9798ebb6wcb65af4f79f7e...@mail.gmail.com

Reply via email to