Hi.
I tried to do Debian netinstall from minimum iso image in my brother's pc.
My Network Interface card is Intel 82578DC GIGABYTE Network Connection. The installer gives a list of drivers to install but I don't know what to do.
Should I download and install from first CD/DVD? Will it have appropriate drivers then?
Please suggest me.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Debian testing netinstall doesn't detect NIC/drivers.
- Laxman Neupane
- Posts: 93
- Joined: 2010-03-08 11:16
Re: Debian testing netinstall doesn't detect NIC/drivers.
Support for that network adapter was only added to the Linux kernel relatively recently http://kerneltrap.org/mailarchive/linux ... /2/5855413 This is well after Debian Lenny was released. So yes you will need to use the full CD1 or DVD1. After that you would need to install a newer kernel such as the one available from backports. Perhaps you can use a wireless network adapter to do this or you could use another computer or operating system to download the backports kernel and install it using 'dpkg -i <package_name>'
Wisdom from my inbox: "do not mock at your pottenocy"
-
- Posts: 416
- Joined: 2007-03-19 18:11
- Location: my desk, Warsaw, Poland
Re: Debian testing netinstall doesn't detect NIC/drivers.
Or, you can try a testing Debian installer, in case you want to setup a desktop system running Debian testing/unstable. cdimage.debian.org.
[url=irc://irc.freenode.net/debian]Find me on #debian at irc.freenode.net[/url] | Linux permission HOWTO | Shorewall firewall | Virtual web hosting
- Laxman Neupane
- Posts: 93
- Joined: 2010-03-08 11:16
Re: Debian testing netinstall doesn't detect NIC/drivers.
julian67 wrote:Support for that network adapter was only added to the Linux kernel relatively recently http://kerneltrap.org/mailarchive/linux ... /2/5855413 This is well after Debian Lenny was released. So yes you will need to use the full CD1 or DVD1. After that you would need to install a newer kernel such as the one available from backports. Perhaps you can use a wireless network adapter to do this or you could use another computer or operating system to download the backports kernel and install it using 'dpkg -i <package_name>'
Thanks Julian. But, if I install the newer kernel for lenny, will it have any effect on stability?
Moreover, if I install the testing branch, will the kernel version there have support for the card?
- Laxman Neupane
- Posts: 93
- Joined: 2010-03-08 11:16
Re: Debian testing netinstall doesn't detect NIC/drivers.
thewanderer wrote:Or, you can try a testing Debian installer, in case you want to setup a desktop system running Debian testing/unstable. cdimage.debian.org.
Hi.
I downloaded the testing installer and while starting the installation, it too doesn't detect the Ethernet. Does the kernel of testing branch also not have the support for the card yet?
Re: Debian testing netinstall doesn't detect NIC/drivers.
The backports kernel should make no difference to stability.
I was surprised the testing installer didn't recognise your network adapter so I did a little digging. I think I found the reason and what to do about it, but no guarantees. I think the Intel network adapters which use the e1000 driver (that includes yours) often/always require non-free firmware in order to work. Debian doesn't officially distribute any non-free software/firmware which means it won't be found in the installer or the main repository even though it may be present in the vanilla kernel source from kernel.org. But there is a non-free package of commonly needed non-free firmwares in non-free backports (and in squeeze and sid). If I were you I would install using the regular CD1 or DVD1 and then obtain the packages firmware-linux, firmware-linux-free, and firmware-linux-nonfree and install them using 'dpkg -i <package_name>' and I would expect the network adapter to then be recognised on a reboot.
Another possibility to check before proceeding: if you have any live Linux CDs which do work with your adapter you can boot them and check which driver your network adapter uses and by unloading and reloading the module (driver in windows speak) and looking at the output of dmesg you should also be able to see exactly which firmware it requires. To find out which driver a device uses (on a Debian based system) you can run To unload and reload a kernel driver you need to be root and run then run the command 'dmesg' and you should see the name of the firmware and it being loaded. I would guess that the latest Ubuntu beta CD would be useful for this as it is Debian based and Ubuntu routinely include non-free firmware in their CDs.
I was surprised the testing installer didn't recognise your network adapter so I did a little digging. I think I found the reason and what to do about it, but no guarantees. I think the Intel network adapters which use the e1000 driver (that includes yours) often/always require non-free firmware in order to work. Debian doesn't officially distribute any non-free software/firmware which means it won't be found in the installer or the main repository even though it may be present in the vanilla kernel source from kernel.org. But there is a non-free package of commonly needed non-free firmwares in non-free backports (and in squeeze and sid). If I were you I would install using the regular CD1 or DVD1 and then obtain the packages firmware-linux, firmware-linux-free, and firmware-linux-nonfree and install them using 'dpkg -i <package_name>' and I would expect the network adapter to then be recognised on a reboot.
Another possibility to check before proceeding: if you have any live Linux CDs which do work with your adapter you can boot them and check which driver your network adapter uses and by unloading and reloading the module (driver in windows speak) and looking at the output of dmesg you should also be able to see exactly which firmware it requires. To find out which driver a device uses (on a Debian based system) you can run
Code: Select all
lspci -k
Code: Select all
# modprobe -r <driver_name> && modprobe <driver_name>
Wisdom from my inbox: "do not mock at your pottenocy"