DHCP from ifconfig??Forum: Networking Topic: DHCP from ifconfig?? started by: jimbo62 Posted by jimbo62 on June 03 2005,15:27
I just installed version 1.0.1. I have a Broadcom 4401 network adapter that DSL doesn't recognize. In other DSL versions, "modprobe b44" gets the driver loaded and "ifconfig eth0 <ip> etc, etc, etc." gets the interface up and running.The modprobe command gets the driver loaded but for some reason the usual ifconfig line doesn't work. But if I use netcardconfig and accept the DHCP option, everything works. But I would like to automate the process by adding lines to /opt/bootlocal.sh. I have searched for about an hour and I haven't found any reference to using DHCP to activate the network, except from within netcardconfig. Can someone tell me what the commands are for using DHCP to set up eth0? Thanks, jimbo Posted by Guest on June 03 2005,16:39
Just after you do modprobe, check if there is any instance of "pump" running: open XTerminal, type "sudo ps ax", and check. If there is (which is usually my problem), you have to kill it first by issuing "sudo pump -k" before doing the automatic dhcp broadcast using "sudo pump -i eth0". After issuing this last command, check your dhcp status using "sudo pump -s".
Posted by jimbo62 on June 03 2005,19:06
Thanks guest! That works. And I placed the commands in /opt/bootlocal.sh and when DSL boots up the interface gets setup and Firefox connects to the Internet without any further configuration.Is the "pump -i eth0" command exactly what the netcardconfig DHCP option does? Thanks again, jimbo Posted by gjhicks on June 20 2005,10:02
Hi,Am using DSL 1.2.1 and can not get the broadcom b44 ethernet adapter to work. Have tried the "modprobe" suggestions here and elsewhere on the forum, with the following result: It seems that, although the 'b44.o' driver module file is present, 'modprobe' can't find it - even when fully specified. Any help greatly appreciated. Regards, Geoff. Posted by Pixel on June 21 2005,00:55
I'm having the same problem, the b44 module claims "no such device", even though it's a 440x ethernet adapter... anyone have any suggestions?
Posted by rentable-hardware on July 11 2005,08:50
Hello,have same kind of Problem. have a Broadcom NetXtreme card and can not get it running. Does any one have a solution ? Frank Posted by cbagger01 on July 11 2005,16:37
Maybe you are trying the wrong driver for your card.Give the bcm5700 driver a try. It is located in the SYSTEM area of the mydsl repository. Posted by rentabel-hardware on July 11 2005,17:15
Hello,Thanks for the tip ! i downloaded the bcm5700 mydsl extension. Now i got the following question : I have a running HD install with an e1000 as a base to make a DSL Remaster. I had the problem that at my friend my remastered CD did not work, because he has such an adapter (HP Workstation). How to handle that the driver will be used / probed in my new live-cd as all other drivers ? Many thanks to all helpers ! Frank Posted by gjhicks on July 18 2005,12:20
Followed the suggestion to try the "mydsl" bcm5700 but still no luck.The Broadcom B44 works fine in Feather, so I tried copying the "b44.o" file from Feather to DSL but no difference. Is it possible that the reason it works in Feather and not DSL is that Feather uses the 2.4.27 kernel and DSL the 2.4.26 kernel? Posted by cbagger01 on July 18 2005,20:14
There is a b44.o file inside DSL, so the built-in module should work with the DSL kernel.Just typing sudo su modprobe b44 produced a "no such device" message for me (as expected since I don't actually own this network card) which is expected behavior for the driver module. Posted by ozknight on July 22 2005,00:00
I'm just guessing here but I've had a few cards that won't be detected (returning no such device) unless irq, dma and or io address are specified. I know you shouldn't have to with pci's but I'm just guessing ?
Posted by cbagger01 on July 22 2005,03:27
Usually the PCI card drivers don't need this information with PCI cards.My guess is the card is not really supported by the Broadcom 44x driver OR it is a newer card and the pci id is not listed in the driver information for this card. A good test is to download the latest version of KNOPPIX (3.9, I believe) and see if it works. If it does work, open a terminal window and type: lsmod | more and see what network driver module name was used. |