[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Laptop wireless problem



On Sunday 03 July 2016 10:25:55 deloptes wrote:
> now what I don't understand is can you use your intel/build in.

No. That was the original problem and why I was trying to use an external card 
in the first place.

> you also 
> did not post the intel dmesg firmware loading lines, but i assume if you
> see networks it would be fine.

Sorry.  I was beginning to have difficulty seeing what I had posted.  I 
thought that I had posted both.  I certainly grepped for both.

root@debian-wheezy:/home/sarah# dmesg | grep 2200
[   10.873432] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 
1.2.2kmprq
[   10.873438] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   10.873683] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[   10.970011] ipw2200 0000:03:03.0: firmware: direct-loading firmware 
ipw2200-bss.fw
[   11.214232] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 
802.11a channels)
root@debian-wheezy:/home/sarah#  

This is the current state:

root@debian-wheezy:/home/sarah# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:22:e7:6f:21
          inet addr:192.168.0.9  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:fee7:6f21/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:409 errors:0 dropped:0 overruns:0 frame:0
          TX packets:234 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:68628 (67.0 KiB)  TX bytes:29511 (28.8 KiB)
          Interrupt:18

eth1      Link encap:Ethernet  HWaddr 00:16:6f:00:3a:b3
          inet6 addr: fe80::216:6fff:fe00:3ab3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:9434 (9.2 KiB)

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:65536  Metric:1
          RX packets:85 errors:0 dropped:0 overruns:0 frame:0
          TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:22633 (22.1 KiB)  TX bytes:22633 (22.1 KiB)

root@debian-wheezy:/home/sarah# 

> to use networkmanager or wicd remove all the configs from your /etc/network
> whatever files. perhaps double check with the upgrade howto and the docs
> for the manager.

Yes - that is the same for Ethernet, and I am much more used to, and therefore 
much less incompetent at, Ethernet than wlan.

I have just checked.  It is not working.  I suspect that none of the GUI 
software, this being an old 32 bit laptop, can handle IPv6.  But it seems 
very odd that the card is finding the networks (and it is finding quite a 
few) and getting an IPv6 address, but not getting an IPv4 one.

Might it be a hardware problem?  Which is where trying another card came 
in. ;-)  I would rather get the original card going - and overnight thought 
of trying to buy a replacement.  I had been forgetting, until you told me to 
look at the BIOS, that that vintage has a mini-PCI card, not onboard 
wireless.  It could easily be changed if I could get a replacement.  It is 
even pretty accessible!!

Thanks,
Lisi


Reply to: