| View previous topic :: View next topic |
| Author |
Message |
IamPenguin
n00b
Joined: 27 Oct 2014
Posts: 4
|
 Posted: Mon Oct 27, 2014 1:15 pm Post subject: Can't connect wifi |
 |
|
First of all, sorry for my bad english XD
Anyway, I installed gentoo, and it boot fine and everything, but I can't connect wifi. When I run ifconfig or iwconfig I don't see wireless interface at all, like it doesn't exists. I downloaded driver and loaded the iwlwifi module, but it doesn't seems to work. Oh and I set my AP in /etc/conf.d/net(WEP security)
My Wireless card is Intel N-7260.
I'm totally at a loss about what I'm suppose to do to fix it S:
~I think this is the right place to post it, but if not move it to anywhere I'd needed to post it~ |
|
| Back to top |
|
 |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
|
| Back to top |
|
|
IamPenguin
n00b
Joined: 27 Oct 2014
Posts: 4
|
| Posted: Mon Oct 27, 2014 3:17 pm Post subject: Re: Can't connect wifi |
|
|
lspci -k:
| Quote: | Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Wireless-N 7260
|
I'd followed those guides and still nothing was changed... |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Mon Oct 27, 2014 3:52 pm Post subject: Re: Can't connect wifi |
|
|
[quote="IamPenguin"] | charles17 wrote: | lspci -k:
| Quote: | Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Wireless-N 7260
|
I'd followed those guides and still nothing was changed... |
Option -k should have shown the driver. Here I get | Code: | $ /usr/sbin/lspci -k
08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection
Kernel driver in use: iwl3945
Kernel modules: iwl3945 |
Have you checked the kernel options? Did you install the firmware? |
|
| Back to top |
|
|
IamPenguin
n00b
Joined: 27 Oct 2014
Posts: 4
|
| Posted: Mon Oct 27, 2014 3:58 pm Post subject: Re: Can't connect wifi |
|
|
[quote="charles17"] | IamPenguin wrote: | | charles17 wrote: | lspci -k:
| Quote: | Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Wireless-N 7260
|
I'd followed those guides and still nothing was changed... |
Option -k should have shown the driver. Here I get | Code: | $ /usr/sbin/lspci -k
08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection
Kernel driver in use: iwl3945
Kernel modules: iwl3945 |
Have you checked the kernel options? Did you install the firmware? |
I installed the firmware and I think the kernel set fine. Maybe there're things that need to change, but I really don't know what is going on there and what I need to looking for. I used genkernel so I didn't work with the kernel options. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Mon Oct 27, 2014 4:05 pm Post subject: Re: Can't connect wifi |
|
|
| As long the driver is not mentioned by lspci you don't have it. Guess you need CONFIG_IWLWIFI |
|
| Back to top |
|
|
IamPenguin
n00b
Joined: 27 Oct 2014
Posts: 4
|
| Posted: Mon Oct 27, 2014 4:06 pm Post subject: Re: Can't connect wifi |
|
|
| charles17 wrote: | | As long the driver is not mentioned by lspci you don't have it. Guess you need CONFIG_IWLWIFI |
OK. As a module or built-in? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54243
Location: 56N 3W
|
| Posted: Mon Oct 27, 2014 4:08 pm Post subject: |
|
|
IamPenguin,
| IamPenguin wrote: | | ... I used genkernel so I didn't work with the kernel options. |
Oops. genkernel is a dumb script all genkernel kernels are the same unless you work with the kernel options. genkernel has a -menuconfig option for that.
There are several things genkernel leaves to the user, WiFi and 3D video acceleration being two of them.
So we know from your quote that you don't have WiFi support in your kernel.
Modules are preferred - it makes fimware loading so much easier.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Mon Oct 27, 2014 4:22 pm Post subject: |
|
|
| NeddySeagoon wrote: | | Modules are preferred - it makes fimware loading so much easier. |
Could you please drop some more words why the module driver does easier firmware loading than a built-in driver? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54243
Location: 56N 3W
|
| Posted: Mon Oct 27, 2014 4:51 pm Post subject: |
|
|
charles17,
There are four possible combinations for a module that needs fimware.
The module and firmware can both be in the kernel - that works
The module can be in /lib/modules and the firmware in /lib/firmware - that works too.
The other two combinations fail.
A built in driver cannot load its firmware from /lib/firmware as root is not yet mouted.
A loadable module cannot get its firmware from inside the kernel as its no longer available.
The wart on the face of both being in the kernel is that its not always clear at kernel build time which firmware you need.
Its then a kernel rebuild to fix it, after you read dmesg to find out the firmware file name you really need.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Tue Oct 28, 2014 9:34 am Post subject: |
|
|
| NeddySeagoon wrote: | charles17,
There are four possible combinations for a module that needs fimware.
The module and firmware can both be in the kernel - that works
The module can be in /lib/modules and the firmware in /lib/firmware - that works too.
The other two combinations fail.
A built in driver cannot load its firmware from /lib/firmware as root is not yet mouted.
A loadable module cannot get its firmware from inside the kernel as its no longer available.
The wart on the face of both being in the kernel is that its not always clear at kernel build time which firmware you need.
Its then a kernel rebuild to fix it, after you read dmesg to find out the firmware file name you really need. |
Thanks for those clear words of explanation. Guess they could be very helpful for folks new to linux. |
|
| Back to top |
|
|
|
Networking & Security
