Fedora Core 6 doesn't detect the wireless conection as a wireless conection...?
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
Fedora Core 6 doesn't detect the wireless conection as a wireless conection...?
Hey all...
I'm using the fedora core 6 with the with the iwp2200 and all that.
the network setup says my eth0 is a wireless connection using the driver, i've put the firmware in /lib/firmare/ , everything is in order, on paper.
but when I go to add a wireless connection, it won't let me.
the devices arn't there.
but when I choose 'ethernet-connection' , it'll give me the option of "wireless driver"... but ofcourse it wont actually be a wireless connection.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
So, it is an Ethernet device which happens to be wireless. What label it is known as eth0, wlan0 or any other name does not really matter as far as Linux is concerned. Does the driver load???? Can you connect with the device???
Try something as root like;
/sbin/iwlist eth0 scan
Do you see any wireless networks?? If yes then try;
sorry,
yes I use the eth0.
I can connect as in I'm using the internet with it right now.
In the network setup window it says it's wireless. even has the icon. but once I unplugg the cable, it dies.
and when I tried your command , I got:
eth0 Interface doesn't support scanning
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Do not worry the iwlist command, since you have a cable then this is not a wireless device.
You may have both a wired connection (currently eth0) and a wireless connection. Check the output from the typed command to see if this is true; /sbin/lspci -v
If yes then post back the information about the wireless device, just the part about the device please. For example;
00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: AMBIT Microsystem Corp. TravelMate 2410
Flags: bus master, fast devsel, latency 64, IRQ 17
Memory at e2000000 (32-bit, non-prefetchable) [size=8K]
when I was using Mandriva 2006, I could use it as a wireless. very unstable, but still worked using the instructions on the different web pages.
-------------------------------------------------------
06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
Subsystem: Hewlett-Packard Company Unknown device 12f5
Flags: medium devsel, IRQ 18
Memory at b0106000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Hewlett-Packard Company Unknown device 309d
Flags: bus master, medium devsel, latency 128, IRQ 18
I/O ports at 3000 [size=256]
Memory at b0109400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
===================================
hope this helps.
also, in the network configuration window, it says that eth1 is using the wireless driver.
it says eth0 IS a wireless connection, but uses "Real Tech Semiconductor..." something.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
This is a little strange, the Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ Ethernet interface should be a wired connection. Since you can use eth0 maybe something unexplained has happened. Take a look at both files, ifcfg-eth0 and ifcg-eth1 in the directory /etc/sysconfig/network-scripts and have a look at the etc/modprobe.conf file also.
The wireless device should be using the ipw2200 kernel module, check the /proc/modules and see if the driver is loaded; cat /proc/modules | grep ipw200
If not the as root try loading it; modprobe ipw2200
Also make sure the /etc/modprobe.conf files use the ipw2200 for eth1; alias eth1 ipw200
Also disable the kudzu service; chkconfig --level 345 kudzu off
This will stop the service from renaming/reconfiguring eth0 and eth1
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
All you really need to do is edit the current ifcfg-eth0 file and change the DEVICE= line to be eth1 and save it as ifcfg-eth1. Create a new ifcg-eth0 file like the example I provided earlier and save in the /etc/sysconfig/network-scripts directory. When done restart the network services; service network restart
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Please review this thread, you have everything you need within it. Take your time read, think and reflect.
It is not that I am not willing to help, I have.
You have the information but for whatever reason 'we' are not communicating very well. You have two Ethernet devices, one wired (8139too) and one wireless (ipw2200). It does not matter by what name they are called (eth0, eth1, wlan0 or any other name) as long as the system and you know which is which.
If the wireless device is eth0 then it is eth0, make sure that the /etc/modprobe.conf file knows which driver to alias to eth0. Do the same with the wired Ethernet device, if it is known as eth1 and has the correct alias in /etc/modprobe.conf then it will work.
The ifcfg-eth0 file must have the line DEVICE=eth0 in it and the ifcfg-eth1 must have the line DEVICE=eth1 in it. You have examples of what the wireless ifcfg-ethX file should look like and what the wired ifcfg-ethX file should look like, apply the knowledge. X is any number from 0 to whatever.
Thank you for all your help, and sorry for any inconvenience.
I've done all the steps to the T.
The only other things I could think of :
a.) One line in one of the files are wrong.
b.) There's some system service that keeps changing something in the setup.
c.) In my network command center, I now get the error message :
ipw2200 device eth0 does not seem to be present, delaying initialization.
when I try to activate the eth0
could this mean that the module for ipw2200 isn't installed atal?
the files that you told me to edit have been done so exactly as you told me.
It seems like I'm getting closer and closer to the answere, but I know it's going to come down to something stupid that , either I forgot, or something that was misstyped...
have a good one.
/santiago
Last edited by santiagosilva; 02-01-2007 at 01:19 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.