UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to install ubuntu warty warthog on an IBM eserver xSeries 300, and I can't get any network connection. I've checked my cables and tried using both ethernet ports, but it can't obtain an ip via dhcp. I know my router is working correctly because my ubuntu desktop works. The device and the switch show connectivity for the server. When I open the Computer > System Configuration > Networking gui, it shows my network device "Ethernet LAN card" and says its device eth0, but dosn't show eth1. When I try to click the "activate" checkbox, it checks it, and then it unchecks it (like the activate didn't work?) I'm so used to network devices "just working" under all the distros I've used I don't even know where to go for debug information on this. any help is greatly apreciated
Are they the same chipset? You need to figure out which physical device is getting detected. Usually dmesg will show which driver initialized which device (eth0 , eth1). If both nics are the same chipset it becomes difficult to tell which one is actually operational, because the kernel probes for only 1 card by default, and its the one that the kernel 'finds' first, which varies across reboots. You can tell the kernel which card to probe first however, using the kernel command line.
Also, some systems use 'dhclient' rather than 'dhcpcd'. See if that works...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.