DebianThis forum is for the discussion of Debian 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.
Also, here's my output from 'ifup eth0' in Debian:
PHP Code:
dhcp-128-194-69-142:/home/alex# ifup eth0 Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved.
Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html
sit0: unknown hardware address type 776 eth0: unknown hardware address type 24 sit0: unknown hardware address type 776 eth0: unknown hardware address type 24 Listening on LPF/eth0/<null> Sending on LPF/eth0/<null> Sending on Socket/fallback/fallback-net DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2 No DHCPOFFERS received. No working leases in persistent database.
From Debian-- 'ifconfig eth0'
Also, now when Debian boots up it successfully configures the ethernet
interface, or so it says. But the output below shows dropped pakets.
PHP Code:
eth0 Link encap:UNSPEC HWaddr 00-0D-61-00-00-79-78-16-00-00-00-00-00-00-0$ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:5 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I looked at my etc/network/interfaces files in Ubuntu to compare it to Debian when this problem first arose.
Anyways, I already had the iface....lines in the files.
I've also tried running the ifup eth0 command from Debian-->my first post has the output from that there.
**I asked a friend of mine what he thought about my problem. I used modprobe for my marvell ethernet adapter-- sk98lin. Now I think maybe need to change the permissions (chmod) of something, like say that modules.??? Does this make sense?
so are there any errors showing in /var/log/dmesg in relation to detecting the ethernet controller ?
the reason I ask is that when you show ifconfig for the debian box the encapsulation is UNSPECIFIED and the MAC address for he card is borked (wrong).. it looks as though the system is not detecting your hardware properly.. you can set all the static IP's you want and renew DHCP all day long and it's not going to work until you fix the fundamental problem of the hardware not being detected properly..
Quote:
Ubuntu
Link encap:Ethernet HWaddr 00:0D:61:7C:53:AD
Debian
Link encap:UNSPEC HWaddr 00-0D-61-00-00-79-78-16-00-00-00-00-00-00-0$
Those HW addresses should be identical.. not just he manufacturer ID portion (the first three octets)
What does lspci show ? (does it list the correct network card in your machine ?
Is the proper module for that card being loaded ?
is your system detecting a firewire port as an network interface controller and your ethernet controller has moved from eth0 to eth1 ? (happened to me on Debian already.. )
Review /var/log/dmesg for entries related to the Network card detection. post any relevant lines
eth0 = ieee1394 = FIREWIRE port there is your issue..
the system thinks the Firewire port is eth0 so you need to figure out what module is actually needed for your NIC and ensure it is being loded. at which point the Marvel controller should come up as eth1.
Looks like DaneM hit it on the head with the module needed.. sk8lin
Just curious what kernels you are running in the 2 OS's is Debian using an older kernel or are you up to 2.6.15 ? that may explain why Ubuntu can use it but Debian isn't.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.