I am brand new to linux (just downloaded it last night) and so far it has been a nightmare. I think most of my problems are due to the fact that I have a broadcom 4400 onboard nic and their support for linux is seriously lacking.

ok so my problem is I want to run a bnetd server for me and my friends and I cant find a windows build of it any more (I think its illegal in windows or some crap like that) but I cant get connected to my cable internet (dhcp).

this is what I have done so far I downloaded debian (latest version 7 cds jigdo isos) burned it to cd.

installed windows xp so I can get support and resources

set up a fat 32 partition so I can transfer files from windows to linux

installed debian kernel 2.4.18

this kernel doesnt support my broadcom nic

compiled kernel 2.6.4 says it supports my nic but doesnt

downloaded a driver module from broadcom bcm4400<blah version blah>.tar.gz

mounted my fat32 drive coppied it over to /usr/src

set up a link to my kernel source ln -s /usr/src/kernel-2.6.4 linux

untared the driver to /usr/src/bcm4400/src

compiled it (make)

tested it by loading it insmod bcm4400.o seemed to work fine said something about eth0 pressent or some crap


then make install

then reran lilo /sbin/lilo

restarted the comp something comes up at startup now about eth0 bcm4400 broadcom type blah blah blah (looks like its working)

checked to see if I have a dhcp client dpkg -l dhcp-client its there latest version

but for some reason I still cant access the debian security updates and I cant even find anywhere where it tells me what my ip address is except for one file dhclient.conf says my ip is 127.0.0.1 which is crap because this is just seemingly a default Ip it gave me not one that it got from my dhcp server also everything else in this dhclient.conf file is commented out for some reason but I dont know how to set the rest of it up or even what it is for. also interestingly my /etc/network/interfaces file only has a loopback adapter set up it doesnt even mention my eth0.

this is really bothering me I would really like to get connected to the internet. I imagine that my whole problem is probably that I couldnt run the network setup part of the debian install because it wouldnt find my nic. Im sure I am missing something simple, but I can use any advice I can get or a good how to page (which I havent been able to find so far)

set up a fat 32 partition so I can transfer files from windows to linux

how is that going to help? Linux fstype is ext3/ext2

127.0.0.1 which is crap because this is just seemingly a default Ip it gave me not one that it got from my dhcp server also

127.0.0.1 is the loopback address. apparently you dont know enough about networking to run a DHCP client.

PEACE OUT HOMIE
-FucKn' AutOPSY-

Well Autospy In case you didnt understand my network doesnt work in linux, so I had to download my new kernel sources and my driver for my broadcom network card in windows. the fact that linux is ext3 is completely irrelevant because it can read my fat32 partition and I am able to copy my files from windows to where I want them in linux simply by mounting that partition. this helps because now I have a driver for my network card. and yes you do have a talent for stating the obvious. of course 127.0.0.1 is for my loopback adapter. thus my statement "my my /etc/network/interfaces file only has a loopback adapter set up it doesnt even mention my eth0." if you were paying attention and actually here to help you may have noticed that this is the root of my problem and the reason why I am seeking assistance. apparently you dont know enough about reading comprehension to make an intelligent reply, so why bother posting?

try adding :

auto eth0
iface eth0 inet dhcp

to your /etc/network/interfaces files.. then ifdown eth0 ... then ifup eth0

see if it will go out and look for an IP from your ISP..


If you still have probs, try downloading debian "Sarge" netinstall CD.. it has DHCPC built in.. and it installs only what you want.. (option).. little note.. Sarge is their "unstable" version... but I have had it running for over 2 months, no problems.


Jesse