Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
as suggested in other forums on the web but that did not work for me.
This appears to be the correct module to load for the nic you have. What happens when you entered the command 'modprobe atl1c' We need to know exactly what happens, 'did not work for me' does not help at all. No response is a good sign. If a module loads correctly, no news is good news. If you got some output, post it.
In other posts I have seen users requiring a 2.6.38 kernel before they had success with this driver.
What happens if you run the command ifconfig ? Can copy and paste the results? Do you see the card? The card will be in a 'down' state most probably.
Quote:
there is no entry on /etc/udev/rules.d/70-persistent-net.rules
This gets updated by running '/lib/udev/write_net_rules' as root. You can also manually create, or modify an entry. After making sure the module is loaded, you can run the command, and see if that creates an entry. I'm not sure what normally calls /lib/udev/write_net_rules. The purpose of the rules files is to give consistent results, even with changing system conditions. Net rules are used to give consistent names to devices, based on things like mac address.
So, in summary, run /lib/udev/write_net_rules as root. Look for a new entry. There should be an entry for the wireless card, and a name.
Run 'ifconfig nameofnewcard' and see if the card activates.
You will still have to configure the card before it will work online.
i also have exactly the same problem.. The motherboard i use (asus p5g41t-m lx3) has got this chip integrated for on board Gb lan eth port, i.e. it's not a wifi
i've tried these suggestions and module atl1c loads without errors but ifconfig still shows only localhost loop interface, without eth..
well, since I don't have internet, because linux cannot recognize my network card, I'm not able to provide all the fancy info you need, sorry about that
ifconfig -a shows only localhost loop
to make this a little more simple, is there anything similar to a "generic network card driver for linux"? just like the windows has a "generic display driver" for example, which will enable me to just put my network card online, without all the fancy functionality, provided by the specific driver?
well, since I don't have internet, because linux cannot recognize my network card, I'm not able to provide all the fancy info you need, sorry about that
ifconfig -a shows only localhost loop
to make this a little more simple, is there anything similar to a "generic network card driver for linux"? just like the windows has a "generic display driver" for example, which will enable me to just put my network card online, without all the fancy functionality, provided by the specific driver?
You are posting here some how. Just direct the information to a file then transport it;
Quote:
lspci -vvv >mylspci.txt
Edit out other information and just post the relevant information. If you wish to post all then use http://pastebin.com/ . You could include the output for 'dmesg >mydmesg.txt' and post to http://pastebin.com/. Just provide the links for all the requested information. No one can help without having requested information.
FYI: I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem or query.
@camorri, you are right, I also went that way and solved my problem (with the help from the guys from #debian irc channel on freenode)
I went to the link: http://kmuto.jp/debian/d-i/
And downloaded the first iso from the list (squeeze-custom-amd64-0808.iso) and installed it from usb/cd and everything worked out of the box.
have you resolve that problem with atheros communications device module ???
i had same problem and just found a simple way to resolve that problem
if any one wants to know how i did done that please write here i will share my experience with you
Please do share your solution, because Google (and other search engines) will index your method, so other people might be able to resolve their issues in the future.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.