Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
The b44 driver is included in the vast majority of distros so you probably don't need to compile it if you did a full install. Check the output of lsmod, and if you don't see b44, then run modprobe b44 and see if that doesn't do the trick.
dear friends!
AS i said When i use the command:lsmod
I can see the b44,the result is:b44 32973 0
and i also did:
[root@localhost ~]# ls /lib/modules/2.6.18-1.2798.fc6xen/kernel/drivers/net
3c59x.ko de620.ko myri10ge pppox.ko sungem.ko
8139cp.ko dl2k.ko natsemi.ko ppp_synctty.ko sungem_phy.ko
8139too.ko dummy.ko ne2k-pci.ko r8169.ko sunhme.ko
8390.ko e1000 netconsole.ko s2io.ko tg3.ko
acenic.ko e100.ko ns83820.ko sb1000.ko tlan.ko
amd8111e.ko epic100.ko pcmcia sis190.ko tokenring
appletalk eql.ko pcnet32.ko sis900.ko tulip
atp.ko fealnx.ko phy skfp tun.ko
b44.ko forcedeth.ko plip.ko skge.ko typhoon.ko
bnx2.ko hamachi.ko ppp_async.ko sky2.ko via-rhine.ko
bonding ifb.ko ppp_deflate.ko slhc.ko via-velocity.ko
cassini.ko irda ppp_generic.ko slip.ko wireless
chelsio ixgb ppp_mppe.ko starfire.ko yellowfin.ko
de600.ko mii.ko pppoe.ko sundance.ko
There is the b44.ko too.But when i did:
[root@localhost net]# insmod b44.ko
insmod: error inserting 'b44.ko': -1 File exists
Then i try another command:modprobe b44 ,the result is:
[root@localhost net]# modprobe b44
[root@localhost net]#
There is nothing happen!
what should i do? help me,Please!
dear friends!
AS i said When i use the command:lsmod
I can see the b44,the result is:b44 32973 0
and i also did:
[root@localhost ~]# ls /lib/modules/2.6.18-1.2798.fc6xen/kernel/drivers/net
3c59x.ko de620.ko myri10ge pppox.ko sungem.ko
8139cp.ko dl2k.ko natsemi.ko ppp_synctty.ko sungem_phy.ko
8139too.ko dummy.ko ne2k-pci.ko r8169.ko sunhme.ko
8390.ko e1000 netconsole.ko s2io.ko tg3.ko
acenic.ko e100.ko ns83820.ko sb1000.ko tlan.ko
amd8111e.ko epic100.ko pcmcia sis190.ko tokenring
appletalk eql.ko pcnet32.ko sis900.ko tulip
atp.ko fealnx.ko phy skfp tun.ko
b44.ko forcedeth.ko plip.ko skge.ko typhoon.ko
bnx2.ko hamachi.ko ppp_async.ko sky2.ko via-rhine.ko
bonding ifb.ko ppp_deflate.ko slhc.ko via-velocity.ko
cassini.ko irda ppp_generic.ko slip.ko wireless
chelsio ixgb ppp_mppe.ko starfire.ko yellowfin.ko
de600.ko mii.ko pppoe.ko sundance.ko
There is the b44.ko too.But when i did:
[root@localhost net]# insmod b44.ko
insmod: error inserting 'b44.ko': -1 File exists
Then i try another command:modprobe b44 ,the result is:
[root@localhost net]# modprobe b44
[root@localhost net]#
There is nothing happen!I try to configure network protocol and address,but network didn't work
what should i do? help me,Please!
If the b44 module is loaded, your card should be available. Please post the output of ifconfig and the details of how your are trying to configure the card.
Quote:
insmod: error inserting 'b44.ko': -1 File exists
Then i try another command:modprobe b44 ,the result is:
[root@localhost net]# modprobe b44
[root@localhost net]#
By the way, those are normal results if the module is already loaded. Modprobe only returns errors if something goes wrong and stays quiet if the module loads successfully.
dear Hangdog42:
Thanks very much for your helps.
I am a a newbie.I just try to configure the card using static IP or DHCP.I don't know what should configure the card ,could you tell me,please?
As I asked in my previous post, post the output of ifconfig and all the details about how you are trying to configure and use the card. You are the only one sitting in front of your computer, so unless you post details, we can't help you.
Dear Hangdog42:
I am sorry,because i thought you had go off,i planed to reply later.There are lots of threads in this web site.I am afraid that you can't find this thread quickly ,and then you won't reply me.If you had go off and i reply later,you will find this thread conveniently when you come in again. I am sorry for that.
This is what i did:
[root@localhost ~]# dmesg | grep eth
[root@localhost ~]#
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@localhost ~]# ifconfig eth0 up
eth0: unknown interface: No such device
[root@localhost ~]# /etc/init.d/network restart
Because i am a chinese,the command(/etc/init.d/network restart)'s output includes some chinese,i translate the chinese into english.Maybe there are some wrongs,but i thought that you will understand the main informain which is useful.This is the output:
close interface ： [ok]
pop-up interface ： [ok]
pop-up interface eth0： Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth0 ; No such device.
SIOCGIFFLAGS: No such device
pop-up eth0 failed.
[failed]
pop-up eth1： Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; No such device.
Determining Ip information for eth1...failed
[failed]
When i use the gnome's network tools in order to set the eth0 active,the output is:
Error for wireless request"set Encode"(8B2A) SET failed on device eth0;NO such device
Determining IP information for eth0...failed
The eth0 is the Broadcom 4401 networking,and the eth1 is the INTEL wireless card.
Dear Hangdog42:
I am a beginner of linux,so if my previous post's information is not useful,could you tell me what should i do,then i will post the output here.Thanks a lot!
I am a beginner of linux,so if my previous post's information is not useful,could you tell me what should i do,then i will post the output here.Thanks a lot!
That post was exactly what I needed, so thanks for posting it!
There are a couple of odd things going on here. First, in your ifconfig output there is a device named xenbr0. Since there is no eth0, I think we need to run a test to see if that is your Broadcom card. So try this:
1) Check lsmod and make sure b44 is loaded
2) Run ifconfig and see if xenbr0 is there
3) Remove b44 by running modprobe -r b44
4) Check ifconfig again and see if xenbr0 is there
Also please post your output of lspci and lsmod. There is something strange going on here as your system is not creating eth0. It may have something to do with your first attempt to install the b44 module.
Quote:
[root@localhost ~]# dmesg | grep eth
Could you run dmesg | grep b44 and post the output?
Quote:
I am afraid that you can't find this thread quickly ,and then you won't reply me.
Don't worry, as you've seen, LQ emails me when a thread I'm working on has a new post. I may get busy and can't answer immediately, but I will find the thread and answer.
[root@localhost ~]# dmesg |grep b44
b44.c:v1.01 (Jun 16, 2006)
b44 0000:03:00.0: No usable DMA configuration, aborting.
b44: probe of 0000:03:00.0 failed with error -5
b44.c:v1.01 (Jun 16, 2006)
b44 0000:03:00.0: No usable DMA configuration, aborting.
b44: probe of 0000:03:00.0 failed with error -5
OK, this is why it isn't working. From the googling I've done, this is apparently a known bug in FC6, and according to this there is a kernel that fixes it. Have a read through the linked article, but it looks like you're going to need to upgrade your kernel.
Dear friend:
Thanks very much!I will try to upgrade my kernel.Could you tell me what should i do,please?
Yeah - let's start from the beginning.
0/ You'll probably get a more specific response to FC6 problems on fedoraforum.org.
1/ Nearly every driver in the kernel source tree is included in Fedora as a module - so typically modprobe is your first/best choice.
2/ You've learned to use dmesg & /var/log/messages - so I won't re-iterate the point further.
3/ The build directory not found was because you didn't have the kernel development code installed. "yum install kernel-devel" solves this.
4/ WHY are you using the xen kernel ? The Xen project gives you the ability run and manage other kernels under Linux but it is experimental (IMO). The Xen features do break a lot of other things along the way. Please don't drive the Porche till you get past the training wheels. Sincerely no offense meant but it's a lot harder you help you when you crawl way out on the thin branches.
5/ The "ifconfig" command will not tell you if the driver is bound to the hardware. Use "ifconfig -a" for this. Better yet, ifconfig is deprecated so use "ip link".
6/ "System->Administration->Network" from the top panel, or else "system-config-network" gives you a simlpe GUI interface to configure your network interfaces. If the interface appears there, the select the line, and hit the "edit" button. In the edit window select the boxes for startup at boot, autoconfig w/ DHCP and auto DNS. This is the typical config. Select "OK" and then File->save in the main window. The "activate". If that works then it should work on bootup.
==
To install the standard conventional kernel do:
yum install kernel kernel-devel
then reboot and select the standard (non Xen) kernel from the grub menu at reboot.
I'll suggest you remove the xen kernels after reboot for now with:
yum remove kernel-xen
You can always re-install Xen when you feel like tap dancing on a landmine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
