Cant find eth1 intarface after compiling kernel on Asus laptop
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.
Cant find eth1 intarface after compiling kernel on Asus laptop
Hi Guys ,
I bought a new Asus a6b00vc laptop a couple of weeks ago.I am runnning ubuntu 5.04 on it (could not install 5.10 because of hot plug problem - doesnt matter)
Anyways , after installing it , i figured that i could not hear sound (which really sucks by the way , right? )After a while of googling i learned that i needed to compile my kernel because the kernel with ubuntu 5.04 (2.6.10-x) did not supporrt the module for my sound card - which is intel HD audio.
I said thats ok , and downloaded the lateset kernel (2.6.14-3)and compiled it after enabling the module.I can now hear the sounds - which is a good progress.
But the problem is , i can NOT see my wireless interface (which was "eth1" on old kernel -> this is important )and i am sure i compiled it right.To be sure i gave the lspci command and saw the Intel Corp. Pro/wireless 2200BG (rev 05) which means it is loaded.
I tried the iwconfig command and saw
lo
eth
sit0 =>all of them saying no wireless extensions (which is still ok)
than tried to load the module with modprobe :
modprobe ipw2200
and i guesss it is installed because i got no errors.
But i could still not see my eth1 interface after giving the iwconfig command.
What am i doing wrong? What should i do to make it work?
After running modprobe, run lsmod to make sure that the module actually loaded. Since ipw2200 is not part of the kernel, I'm guessing that you will have to recompile that driver in order for it to work again. However, if lsmod shows the module is loaded, have a look through your logs and see if ipw2200 is complaining about anything.
Quote:
To be sure i gave the lspci command and saw the Intel Corp. Pro/wireless 2200BG (rev 05) which means it is loaded.
Actually, all that means is that the system can see the PCI card. It doesn't really say anything about whether or not it has the drivers needed to use the card.
I agree that the ipw2200 module is loaded. The logs are /var/log/messages and /var/log/syslog. The logs are likely to be long, but ipw2200 should be identifying itself and leaving a trail of what it is doing.
Dec 8 16:10:26 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed: Reason -2
Dec 8 16:10:26 localhost kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
The card is either not finding the firmware or is not able to load the firmware that is there. What you need to do is visit the ipw2200 site and download the firmware for ipw200 version 1.0.0 (which is the version you have according to your messages log). Then have a read through the INSTALL file and pay attention to section 10 which explains how to set up the firmware to download to the card.
Before you do try to install new firmware, you may have a look and see if the firmware is already installed on your machine. That error message may also suggest a permissions problem with the firmware files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.