Intel 3945BG does not works

naruponk · 02-13-2010, 07:31 AM

Hi,

I have a problem with my wireless device.
My laptop is Aspire 5580 series (5583 NWXMi)
I have tried to install puppy linux 4.2
puppy already detected 3945BG
but when scan for network it can not find any wireless signal

Does anyone has solution about to install 3945BG ?

onebuck · 02-13-2010, 09:14 AM

Hi,

You are sure the the device is detected & configured? What's the output of 'lsmod', 'ifconfig -a' & 'iwlist your_device scan'? How did you configure the device?

naruponk · 02-13-2010, 10:27 AM

Thanks for reply ^ ^

It show my device as wlan0.
I click to configure it, but no any wireless network found
can I configure using terminal ?

onebuck · 02-13-2010, 04:15 PM

Hi,

Please post the output of the 'ifconfig -a' at least?

Electro · 02-14-2010, 04:23 PM

The command ifconfig will only show wire networks and not wireless. Also if the firmware or microcode is not a compatible version with module or driver that comes with your setup, the 3945 wireless NIC will not work. If it is compatible, it takes about 10 minutes from upon boot up to get a full list of networks. The is one of problems with Intel products. They get something to work, but never make it better.

It will be nice to see the output from /var/log/messages from the time you boot into Linux and to the present. Do not truncate or cut it short. This will tell me or others if the installed microcode is compatible with your module or driver.

Yes, you can configure by console. Make sure the wifi tools are installed and assuming wlan0 is your wifi, do the following.

1) iwlist wlan0 scan
2) iwconfig wlan0 essid "network_name"
3) Run dhcpd utility or dhcpd scripts on wlan0 to get an IP address, gateway address, and DNS.

In some cases the wireless NIC could be off, so to turn it on do the following.

iwconfig wlan0 txpower on

If you are trying to connected to encrypted networks, more steps have to be done to connect to those networks.

naruponk · 02-15-2010, 02:43 AM

Thanks for all helps

And sorry, I have downloaded puppy 4.3.1, everything works fine !

onebuck · 02-15-2010, 07:27 AM

Hi,

Quote:

Originally Posted by Electro

The command ifconfig will only show wire networks and not wireless. Also if the firmware or microcode is not a compatible version with module or driver that comes with your setup, the 3945 wireless NIC will not work. If it is compatible, it takes about 10 minutes from upon boot up to get a full list of networks. The is one of problems with Intel products. They get something to work, but never make it better.

It will be nice to see the output from /var/log/messages from the time you boot into Linux and to the present. Do not truncate or cut it short. This will tell me or others if the installed microcode is compatible with your module or driver.

Yes, you can configure by console. Make sure the wifi tools are installed and assuming wlan0 is your wifi, do the following.

1) iwlist wlan0 scan
2) iwconfig wlan0 essid "network_name"
3) Run dhcpd utility or dhcpd scripts on wlan0 to get an IP address, gateway address, and DNS.

In some cases the wireless NIC could be off, so to turn it on do the following.

iwconfig wlan0 txpower on

If you are trying to connected to encrypted networks, more steps have to be done to connect to those networks.

That's funny! My output for 'ifconfig -a';

Code:

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:19:b9:51:81:1a
          BROADCAST MULTICAST  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:822 errors:0 dropped:0 overruns:0 frame:0
          TX packets:822 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:134458 (131.3 KiB)  TX bytes:134458 (131.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:19:7d:5e:e5:20
          inet addr:192.168.1.18  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::219:7dff:fe5e:e520/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1016037 errors:0 dropped:0 overruns:0 frame:0
          TX packets:402792 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:309857502 (295.5 MiB)  TX bytes:128863812 (122.8 MiB)

Quote:

excerpt from 'man ifconfig';

NAME
ifconfig - configure a network interface
SYNOPSIS
ifconfig [interface]
ifconfig interface [aftype] options | address ...
DESCRIPTION
Ifconfig is used to configure the kernel-resident network interfaces. It is used at boot time to set up interfaces as necessary. After that, it is usually only needed when debugging or when system tuning is needed.

If no arguments are given, ifconfig displays the status of the currently active interfaces. If a single interface argument is given, it displays the status of the given interface only; if a single -a argument is given, it displays the status of all interfaces, even those that are down. Otherwise, it configures an interface.

'ifconfig -a' will show all devices even the ones that are down by using the '-a' option as shown in the above definition.

Electro · 02-15-2010, 07:33 PM

Quote:

Originally Posted by onebuck

Hi,

That's funny! My output for 'ifconfig -a';

Code:

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:19:b9:51:81:1a
          BROADCAST MULTICAST  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:822 errors:0 dropped:0 overruns:0 frame:0
          TX packets:822 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:134458 (131.3 KiB)  TX bytes:134458 (131.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:19:7d:5e:e5:20
          inet addr:192.168.1.18  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::219:7dff:fe5e:e520/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1016037 errors:0 dropped:0 overruns:0 frame:0
          TX packets:402792 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:309857502 (295.5 MiB)  TX bytes:128863812 (122.8 MiB)

'ifconfig -a' will show all devices even the ones that are down by using the '-a' option as shown in the above definition.

Yes, including -a option for ifconfig will show all network devices even if any NIC is down, but wireless NIC are different because they need to connect by essid before they are actually connected to a network. Wireless network utilities have to be used for wireless network devices. The utility ifconfig is not enough to use for a wireless NIC.

onebuck · 02-15-2010, 08:10 PM

Hi,

Quote:

Originally Posted by Electro

Yes, including -a option for ifconfig will show all network devices even if any NIC is down, but wireless NIC are different because they need to connect by essid before they are actually connected to a network. Wireless network utilities have to be used for wireless network devices. The utility ifconfig is not enough to use for a wireless NIC.

So from your point then showing the devices up or down is not possible or is incorrect?

Get serious, I asked to see the devices, up or down with the 'ifconfig -a'. Your statement about 'ifconfig' is a farce when speaking of whether the device is up or down. Nothing in concrete about device status. Sure, if configuring a wireless device it would be best to utilize a tool that would suffice the job. Heck, so a 'ifconfig wlan0 down' is wrong from your definition. Or what about 'ifconfig wlan0 up' to control the device not configure.

WNIC and NIC are two different device types to access a computer network. I never stated the use of the wireless tools. Since I'm on wireless tools, some require that the device is up before you can use the tools so 'ifconfig device up' would work to allow the wireless tools to be used.

I guess you have a magic trick or two that you want to share now?