Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #169609 > unrolled thread
| Started by | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| First post | 2016-07-02 02:20 +0200 |
| Last post | 2016-07-10 13:20 +0200 |
| Articles | 20 on this page of 72 — 8 participants |
Back to article view | Back to linux.debian.user
Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 02:20 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 03:50 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 15:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:00 +0200
Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 16:20 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:40 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-02 16:40 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-02 18:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 20:30 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 00:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 11:30 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 12:50 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 14:00 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 14:50 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:10 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 18:00 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-03 19:20 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-03 11:50 +0200
Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 12:50 +0200
Re: Laptop wireless problem Jörg-Volker Peetz <jvpeetz@web.de> - 2016-07-02 21:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 16:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-03 21:10 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 22:30 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-03 22:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-03 23:50 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 09:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 14:10 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 15:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 16:10 +0200
Re: Laptop wireless problem - very slight tangent David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:10 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 17:20 +0200
Re: Laptop wireless problem - very slight tangent David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:40 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 18:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-05 18:30 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-05 18:30 +0200
Re: Laptop wireless problem - very slight tangent Brian <ad44@cityscape.co.uk> - 2016-07-05 20:50 +0200
Re: Laptop wireless problem - very slight tangent Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-07-04 02:30 +0200
Re: Laptop wireless problem - very slight tangent Dan Purgert <dan@djph.net> - 2016-07-04 13:30 +0200
Re: Laptop wireless problem - very slight tangent Nicolas George <george@nsup.org> - 2016-07-04 14:30 +0200
Re: Laptop wireless problem - very slight tangent Dan Purgert <dan@djph.net> - 2016-07-04 16:20 +0200
Re: Laptop wireless problem - very slight tangent Nicolas George <george@nsup.org> - 2016-07-04 16:30 +0200
Re: Laptop wireless problem deloptes <deloptes@gmail.com> - 2016-07-02 22:20 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 18:30 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:00 +0200
Re: Laptop wireless problem - very slight tangent Brian <ad44@cityscape.co.uk> - 2016-07-04 19:50 +0200
POSSIBLY SOLVED Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 20:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:40 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 21:00 +0200
Re: Laptop wireless problem - very slight tangent deloptes <deloptes@gmail.com> - 2016-07-04 22:20 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 23:50 +0200
Re: Laptop wireless problem - very slight tangent Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:10 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 18:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 19:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 20:10 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 20:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-04 21:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 21:00 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-05 01:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:40 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 01:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Brian <ad44@cityscape.co.uk> - 2016-07-05 10:30 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:00 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:10 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 16:20 +0200
Re: Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem David Wright <deblis@lionunicorn.co.uk> - 2016-07-05 17:20 +0200
Success after all!!! - was: Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 00:40 +0200
Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-05 01:40 +0200
FIXED - I hope!! Laptop wireless problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-10 13:20 +0200
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
| From | Cindy-Sue Causey <butterflybytes@gmail.com> |
|---|---|
| Date | 2016-07-04 02:30 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rQZVT-75x-1@gated-at.bofh.it> |
| In reply to | #169658 |
On 7/3/16, deloptes <deloptes@gmail.com> wrote: > Lisi Reisz wrote: > >> I have discovered something I find interesting in this, which does not >> seem to be directly in reply to anything that has gone before - so it was >> difficult >> to place it in the thread. I have deliberately broken the >> "conversation", >> but not the thread. >> >> From the router's log: Every time I try (once) to connect to the router >> from the laptop with wicd, using the Intel card, it makes two attempts to >> connect >> and the router ALLOWS both. So why, when it is allowed to connect, does >> it >> not do so??? I have checked this out specifically. :-/ > > I assume you have not changed passwords on the access point recently. > What could be an issue is that wicd can not access the password stored > locally or have some other issue. I would look into this direction. perhaps > you can run it with debug enabled and see where it fails. It could be also > that your wpa_supplicant has issue(s). > What I also think you should do, is change the name from eth1 to wlan0 if > using jessie. I've still been battling trying to get my wifi up and running, too. This post triggered the memory that neither of those applies to my setup anymore. Somewhere thankfully early on, I discovered mine is "wlp2s0" on Sid Unstable. Command line's "iwconfig" as root is how I determined that. There is a reasonable rationale out there as to why it became that, but that escapes me just this second. It was about it being wireless and the tailend of it represented its... [residency] somehow. The "p" and the "s" stood for something recognizable to me, and the two numerical digits were its location at those... somethings. I just tried a quick search and didn't find it. Figured someone might recognize it if I go ahead and post anyway. :) Throwing it out there in case someone stumbles upon this thread, and the others don't apply. PS enp1s0 is now my other one, as well. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape *
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2016-07-04 13:30 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRaeC-4Z4-15@gated-at.bofh.it> |
| In reply to | #169662 |
Cindy-Sue Causey wrote:
> [snip]
> [...] "wlp2s0" on Sid Unstable.
>
> [...]
>
> PS enp1s0 is now my other one, as well.
>
As I recall it ...
- prefix ("en" | "wl") indicates whether it's [e]ther[n]et or [wl]an.
- p# indicates the PCI Bus it's on
- s# indicates the slot on that PCI Bus
it's all part of the "new" udev/systemd naming, because it's "better"
(IMO, "better" would've been locking the devices as they do, but keeping
eth0 / wlan0 / etc naming conventions). Thankfully, you can tell udev
to shove off, and keep the names as "eth#" and "wlan#" if you so choose.
--
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O|
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2016-07-04 14:30 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRbaG-5yi-17@gated-at.bofh.it> |
| In reply to | #169687 |
[Multipart message — attachments visible in raw view] — view raw
Le septidi 17 messidor, an CCXXIV, Dan Purgert a écrit :
> As I recall it ...
>
> - prefix ("en" | "wl") indicates whether it's [e]ther[n]et or [wl]an.
> - p# indicates the PCI Bus it's on
> - s# indicates the slot on that PCI Bus
>
> it's all part of the "new" udev/systemd naming, because it's "better"
> (IMO, "better" would've been locking the devices as they do, but keeping
> eth0 / wlan0 / etc naming conventions). Thankfully, you can tell udev
> to shove off, and keep the names as "eth#" and "wlan#" if you so choose.
I think the point of the new naming scheme is not to have people use them
but to give admins a well needed kick in the arse so that they will actually
CHOOSE a name instead of relying on the automatically-generated kernel name.
This is the same logic for filesystems: the trend since several years is to
push for logical volume names or filesystem labels instead of relying on
drive letter and partition name.
This is a better policy because the chosen name actually means something
while the letters and numbers not only mean nothing but also could change if
the wind blew too hard, usually at the worst possible time.
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2016-07-04 16:20 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRcT7-6F8-25@gated-at.bofh.it> |
| In reply to | #169690 |
Nicolas George wrote:
>
> --RnlQjJ0d97Da+TV1
> Content-Type: text/plain; charset=iso-8859-1
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Le septidi 17 messidor, an CCXXIV, Dan Purgert a =E9crit=A0:
>> As I recall it ...
>>=20
>> - prefix ("en" | "wl") indicates whether it's [e]ther[n]et or [wl]an. =
>=20
>> - p# indicates the PCI Bus it's on
>> - s# indicates the slot on that PCI Bus
>>=20
>> it's all part of the "new" udev/systemd naming, because it's "better"
>> (IMO, "better" would've been locking the devices as they do, but keeping
>> eth0 / wlan0 / etc naming conventions). Thankfully, you can tell udev
>> to shove off, and keep the names as "eth#" and "wlan#" if you so choose.
>
> I think the point of the new naming scheme is not to have people use them
> but to give admins a well needed kick in the arse so that they will
> actually CHOOSE a name instead of relying on the
> automatically-generated kernel name.
No, the whole udev thing is to keep the kernel from doing weird things
with device naming on boot (such as swapping eth0 for eth1). I've never
seen it happen with network cards myself, unless I had physically messed
with things (e.g. swap cards around because I needed to move everything
down a slot, but took the opportunity to clean out the motherboard, and
forgot the card order).
--
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O|
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2016-07-04 16:30 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRd2N-6Kd-5@gated-at.bofh.it> |
| In reply to | #169709 |
[Multipart message — attachments visible in raw view] — view raw
Le septidi 17 messidor, an CCXXIV, Dan Purgert a écrit : > No, No, not "no". > the whole udev thing is to keep the kernel from doing weird things > with device naming on boot (such as swapping eth0 for eth1). You are talking about implementation, I was talking about policy. > I've never > seen it happen with network cards myself I have, but this is unrelated to the question at hand.
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2016-07-02 22:20 +0200 |
| Message-ID | <rQzyp-83P-9@gated-at.bofh.it> |
| In reply to | #169628 |
Lisi Reisz wrote: > On Saturday 02 July 2016 17:02:03 Lisi Reisz wrote: >> > In case it's really Intel, is the package firmware-iwlwifi installed? >> >> It wasn't. Is now in the process of installing. Odd. It has been >> working for several years and stopped suddenly late on Friday afternoon. >> But I had been upgrading and various things, so.... > > That package hasn't made any noticeable difference. > > Lisi Last but not least. I think in wheezy the official debian kernel was 3.2 and not 3.16. It might be this changed, but check dmesg after module loading to see what it reports regarding the firmware. Could be that firmware required by kernel is not provided in the package you installed. regards
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2016-07-04 18:30 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rReUW-7St-35@gated-at.bofh.it> |
| In reply to | #169609 |
Lisi Reisz wrote:
> On Monday 04 July 2016 14:20:23 deloptes wrote:
>> Lisi Reisz wrote:
>> > /etc/udev/rules.d/70-persistent-net.rules
>>
>> on my one it looks like this
>>
>> # PCI device 0x8086:0x08b1 (iwlwifi)
>> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
>> ATTR{address}=="xxxxxxxxxxxxxxx", ATTR{dev_id}=="0x0", \
>> ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
>>
>> why shouldn't it find the driver?
>
> So I am misinterpreting it. That is good news. But there is something
> badly wrong, it isn't working!!!!
>>
>> lsmod
>> iwconfig
>> dmesg
>
> sarah@debian-wheezy:~$ dmesg | grep 2200
> [ 11.175897] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
> 1.2.2kmprq
> [ 11.175902] ipw2200: Copyright(c) 2003-2006 Intel Corporation
> [ 11.176356] ipw2200: Detected Intel PRO/Wireless 2200BG Network
> [ Connection 11.328328] ipw2200 0000:03:03.0: firmware: direct-loading
> [ firmware
> ipw2200-bss.fw
> [ 11.461720] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
> 802.11a channels)
> sarah@debian-wheezy:~$ iwconfig
> bash: iwconfig: command not found
> sarah@debian-wheezy:~$ su
> Password:
> root@debian-wheezy:/home/sarah# iwconfig
> wlan0 IEEE 802.11bg ESSID:off/any
> Mode:Managed Channel:0 Access Point: Not-Associated
> Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
> Retry limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> root@debian-wheezy:/home/sarah# lsmod | grep wifi
> root@debian-wheezy:/home/sarah# lsmod | grep wlan
> root@debian-wheezy:/home/sarah# lsmod | grep 2200
> ipw2200 130216 0
> libipw 29891 1 ipw2200
> cfg80211 350041 2 libipw,ipw2200
> lib80211 12829 2 libipw,ipw2200
> root@debian-wheezy:/home/sarah#
This all looks good.
I forgot however to ask you to check rfkill again.
I still think the problem might be in the wicd and wpa_supplicant
http://linux.die.net/man/8/wicd
http://linux.die.net/man/8/wpa_supplicant
According docs there is/are log file(s) in /var/log/wicd
Some cards (via bios setting) would disable the card when you have the cable
plugged to your network card, but I think in your case it is not true.
I would backup all wicd and purge - check config etc files are not present,
install again.
Also you shouldn't have any /etc/wpa_supplicant.conf file or entry
in /etc/network/interfaces.
Some Gentoo people had similar issues after upgrade but the wicd is 1.7.1
there https://forums.gentoo.org/viewtopic-t-914678-start-0.html
Lets doublecheck if all requried is install
# dpkg -l | grep wireless | grep -v trinit
ii crda 3.13-1
amd64 wireless Central Regulatory Domain Agent
ii iw 3.17-1
amd64 tool for configuring Linux wireless devices
ii rfkill 0.5-1
amd64 tool for enabling and disabling wireless devices
ii wireless-regdb 2014.11.18-1
all wireless regulatory database
ii wireless-tools 30~pre9-8
amd64 Tools for manipulating Linux Wireless Extensions
I've been using the ipw2200 for few years on one siemens-fujitsu notebook
with out issues. There was first debian and then ubuntu on it. Strange that
you can not suddenly connect.
Perhaps you can try with a live ubuntu just to see if it works
regards
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 19:00 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRfnX-82c-15@gated-at.bofh.it> |
| In reply to | #169678 |
On Monday 04 July 2016 17:21:29 deloptes wrote:
> Lisi Reisz wrote:
> > On Monday 04 July 2016 14:20:23 deloptes wrote:
> >> Lisi Reisz wrote:
> >> > /etc/udev/rules.d/70-persistent-net.rules
> >>
> >> on my one it looks like this
> >>
> >> # PCI device 0x8086:0x08b1 (iwlwifi)
> >> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> >> ATTR{address}=="xxxxxxxxxxxxxxx", ATTR{dev_id}=="0x0", \
> >> ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
> >>
> >> why shouldn't it find the driver?
> >
> > So I am misinterpreting it. That is good news. But there is something
> > badly wrong, it isn't working!!!!
> >
> >> lsmod
> >> iwconfig
> >> dmesg
> >
> > sarah@debian-wheezy:~$ dmesg | grep 2200
> > [ 11.175897] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
> > 1.2.2kmprq
> > [ 11.175902] ipw2200: Copyright(c) 2003-2006 Intel Corporation
> > [ 11.176356] ipw2200: Detected Intel PRO/Wireless 2200BG Network
> > [ Connection 11.328328] ipw2200 0000:03:03.0: firmware: direct-loading
> > [ firmware
> > ipw2200-bss.fw
> > [ 11.461720] ipw2200: Detected geography ZZD (13 802.11bg channels, 0
> > 802.11a channels)
> > sarah@debian-wheezy:~$ iwconfig
> > bash: iwconfig: command not found
> > sarah@debian-wheezy:~$ su
> > Password:
> > root@debian-wheezy:/home/sarah# iwconfig
> > wlan0 IEEE 802.11bg ESSID:off/any
> > Mode:Managed Channel:0 Access Point: Not-Associated
> > Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
> > Retry limit:7 RTS thr:off Fragment thr:off
> > Encryption key:off
> > Power Management:off
> > Link Quality:0 Signal level:0 Noise level:0
> > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> >
> > lo no wireless extensions.
> >
> > eth0 no wireless extensions.
> >
> > root@debian-wheezy:/home/sarah# lsmod | grep wifi
> > root@debian-wheezy:/home/sarah# lsmod | grep wlan
> > root@debian-wheezy:/home/sarah# lsmod | grep 2200
> > ipw2200 130216 0
> > libipw 29891 1 ipw2200
> > cfg80211 350041 2 libipw,ipw2200
> > lib80211 12829 2 libipw,ipw2200
> > root@debian-wheezy:/home/sarah#
>
> This all looks good.
> I forgot however to ask you to check rfkill again.
root@debian-wheezy:/home/sarah# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
root@debian-wheezy:/home/sarah#
> I still think the problem might be in the wicd and wpa_supplicant
>
> http://linux.die.net/man/8/wicd
> http://linux.die.net/man/8/wpa_supplicant
>
> According docs there is/are log file(s) in /var/log/wicd
root@debian-wheezy:/home/sarah# cd /var/log/wicd
bash: cd: /var/log/wicd: No such file or directory
root@debian-wheezy:/home/sarah#
Jessie uses systemd.
> Some cards (via bios setting) would disable the card when you have the
> cable plugged to your network card, but I think in your case it is not
> true.
>
> I would backup all wicd and purge - check config etc files are not present,
> install again.
I have got rid of wicd
>
> Also you shouldn't have any /etc/wpa_supplicant.conf file or entry
> in /etc/network/interfaces.
root@debian-wheezy:/home/sarah# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
root@debian-wheezy:/home/sarah# cd /var/log/wicd
bash: cd: /var/log/wicd: No such file or directory
root@debian-wheezy:/home/sarah# cat /etc/wpa_supplicant.conf
cat: /etc/wpa_supplicant.conf: No such file or directory
root@debian-wheezy:/home/sarah#
root@debian-wheezy:/home/sarah# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# Bring up wireless
# auto wlan0
# iface eth1 inet dhcp
# wpa-ssid NETGEAR08
# wpa-psk dao45eeWcartwheel
root@debian-wheezy:/home/sarah# aptitude purge wicd
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
root@debian-wheezy:/home/sarah#
>
> Some Gentoo people had similar issues after upgrade but the wicd is 1.7.1
> there https://forums.gentoo.org/viewtopic-t-914678-start-0.html
>
> Lets doublecheck if all requried is install
>
> # dpkg -l | grep wireless | grep -v trinit
> ii crda 3.13-1
> amd64 wireless Central Regulatory Domain Agent
> ii iw 3.17-1
> amd64 tool for configuring Linux wireless devices
> ii rfkill 0.5-1
> amd64 tool for enabling and disabling wireless devices
> ii wireless-regdb 2014.11.18-1
> all wireless regulatory database
> ii wireless-tools 30~pre9-8
> amd64 Tools for manipulating Linux Wireless Extensions
>
> I've been using the ipw2200 for few years on one siemens-fujitsu notebook
> with out issues. There was first debian and then ubuntu on it. Strange that
> you can not suddenly connect.
If the card has died it would explain it!! n It has been running fine for
years, but things do, sadly, die.
> Perhaps you can try with a live ubuntu just to see if it works
Trying now - will send this now and report back again in a while after I have
loaded something as heavy as Ubuntu-anything onto such an old laptop!!!
Thanks, Lisi
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-04 19:50 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRgal-6q-3@gated-at.bofh.it> |
| In reply to | #169685 |
On Mon 04 Jul 2016 at 17:58:58 +0100, Lisi Reisz wrote: > On Monday 04 July 2016 17:21:29 deloptes wrote: > > > > I've been using the ipw2200 for few years on one siemens-fujitsu notebook > > with out issues. There was first debian and then ubuntu on it. Strange that > > you can not suddenly connect. > > If the card has died it would explain it!! n It has been running fine for > years, but things do, sadly, die. True. > > Perhaps you can try with a live ubuntu just to see if it works > > Trying now - will send this now and report back again in a while after I have > loaded something as heavy as Ubuntu-anything onto such an old laptop!!! A featherweight five minute test could be run with a netinst image. No need to go beyond configuring the network stage. Unlike a full install netcfg is used. If the wireless card is not detected you have a very big problem. But why shouldn't it be? iwconfig managed it after all! If it doesn't get configured and connected the problem becomes tractable.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 20:20 +0200 |
| Subject | POSSIBLY SOLVED Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRgDo-vJ-15@gated-at.bofh.it> |
| In reply to | #169692 |
On Monday 04 July 2016 18:43:08 Brian wrote: > On Mon 04 Jul 2016 at 17:58:58 +0100, Lisi Reisz wrote: > > On Monday 04 July 2016 17:21:29 deloptes wrote: > > > I've been using the ipw2200 for few years on one siemens-fujitsu > > > notebook with out issues. There was first debian and then ubuntu on it. > > > Strange that you can not suddenly connect. > > > > If the card has died it would explain it!! n It has been running fine for > > years, but things do, sadly, die. > > True. > > > > Perhaps you can try with a live ubuntu just to see if it works > > > > Trying now - will send this now and report back again in a while after I > > have loaded something as heavy as Ubuntu-anything onto such an old > > laptop!!! > > A featherweight five minute test could be run with a netinst image. No > need to go beyond configuring the network stage. Unlike a full install > netcfg is used. If the wireless card is not detected you have a very > big problem. But why shouldn't it be? iwconfig managed it after all! > > If it doesn't get configured and connected the problem becomes tractable. Thank you. Brian. I'm glad that your brain is turned on, even if mine is not. It detected the card - as you say, why shouldn't it? It detected my SSID. It asked about encryption, asked for the passphrase, got given it - and went back to the beginning: which network do you want, which method of encryption, what is the passphrase - and again, back to the beginning. I tried three or four times. I have a new card on order from Amazon in case. They have a new definition of next day delivery. Ordered 3rd delivered 5th. I was in all day today (which is why I ordered it expecting delivery today). I am not in all day tomorrow. It may come while I am in. If not, we get into the Post Office's idea of redelivery. The parcel has to sit in the delivery office for two days before they can attempt redelivery. Oh, well. :-( Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 19:40 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRg0G-8uN-21@gated-at.bofh.it> |
| In reply to | #169685 |
On Monday 04 July 2016 17:58:58 Lisi Reisz wrote: > # Bring up wireless > # auto wlan0 > # iface eth1 inet dhcp > # wpa-ssid NETGEAR08 > # wpa-psk dao45eeWcartwheel Bother. Sent in error. I'd better change that fast. :-( I'm going for a cup of tea. :-( Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 21:00 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRhg6-IL-17@gated-at.bofh.it> |
| In reply to | #169678 |
On Monday 04 July 2016 17:21:29 deloptes wrote: > Perhaps you can try with a live ubuntu just to see if it works I tried. A screen full of coloured squiggly lines. I tried ctrl-alt F2. Got a blank screen with a small horizontal flashing cursor and nothing else. Tried ctrl-alt F7, ctrl-alt F8. Still that small flashing horizontal cursor. I think Brian's test was pretty conclusive. Lisi
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2016-07-04 22:20 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRivv-1HR-21@gated-at.bofh.it> |
| In reply to | #169710 |
Lisi Reisz wrote: > I think Brian's test was pretty conclusive. yes. I followed it. Perhaps indeed the card is dead. You may try replacing it. It is indeed a separate module mounted on the board. You need a screwdriver, some skills and good howto. Let us know if it helped solve the problem. regards
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 23:50 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRjUC-2t5-11@gated-at.bofh.it> |
| In reply to | #169722 |
On Monday 04 July 2016 21:13:13 deloptes wrote: > Let us know if it helped solve the problem. :-) I am at Royal Mail's mercy!! Thanks for all the patient help. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-05 00:10 +0200 |
| Subject | Re: Laptop wireless problem - very slight tangent |
| Message-ID | <rRkdX-2Ox-3@gated-at.bofh.it> |
| In reply to | #169710 |
On Monday 04 July 2016 19:58:15 Lisi Reisz wrote: > On Monday 04 July 2016 17:21:29 deloptes wrote: > > Perhaps you can try with a live ubuntu just to see if it works > > I tried. A screen full of coloured squiggly lines. I tried ctrl-alt F2. > Got a blank screen with a small horizontal flashing cursor and nothing > else. Tried ctrl-alt F7, ctrl-alt F8. Still that small flashing horizontal > cursor. > > I think Brian's test was pretty conclusive. > > Lisi Wow!!! It just hadn't finished loading. I went away for three HOURS and have come back to find that Ubuntu-Mate has just about finished loading - not quite. But "not quite" might take several hours more. I don't intend to hang around to see if it ever finishes. I shall just turn it off and run Brian's CLI test again, just for the sake of my learning how to do the test. Ubuntu nowadays just isn't useful as a live medium. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-04 18:40 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRf4B-7Vx-3@gated-at.bofh.it> |
| In reply to | #169609 |
On Mon 04 Jul 2016 at 15:37:42 +0100, Lisi Reisz wrote:
> On Monday 04 July 2016 15:16:23 Brian wrote:
>
> It isn't. It is just a short quotation to show the ipw 2200 and the
> DRIVERS=="?*", because it bothered me that the drivers bit just had a
> question mark, but apparently my worry about that was misplaced. Whole file
> beneath my signature.
Full quotes are always preferable. If I were in your position I'd
regenerate the file. You've possibly got at least one device there
which is not on the machine. Let the system take care of things.
Be that as it may, you appear to have all necessary firmware and
drivers. So, how do you fancy a bit of low level stuff?
Reboot and first check firmware loading from 'journalctl'. Then
issue the command 'wpa_cli'.
1. wpa-cli
You get a prompt ">". This is interactive mode. A selected
interface should be shown. TAB completion of commands works.
Command history is with the UP and DOWN keys. The following
commands are typed at the prompt.
2. add_network
You'll probably get 0 for the network number.
3. set_network 0 ssid "Your_SSID"
The response should be "OK".
4. set_network psk "Your_passphrase"
The response should be "OK".
5. enable_network 0
The response should be "OK". Authentication and association
should take place.
6. status 0
Has it?
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 19:40 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRg0G-8uN-39@gated-at.bofh.it> |
| In reply to | #169679 |
On Monday 04 July 2016 17:37:00 Brian wrote: > On Mon 04 Jul 2016 at 15:37:42 +0100, Lisi Reisz wrote: > > On Monday 04 July 2016 15:16:23 Brian wrote: > > > > It isn't. It is just a short quotation to show the ipw 2200 and the > > DRIVERS=="?*", because it bothered me that the drivers bit just had a > > question mark, but apparently my worry about that was misplaced. Whole > > file beneath my signature. > > Full quotes are always preferable. If I were in your position I'd > regenerate the file. You've possibly got at least one device there > which is not on the machine. No. I left the commented out line in case I needed to revert to it. It regenerated eth1, so I manually edited it to wlan0, but left the other line tehr ein case. > Let the system take care of things. > > Be that as it may, you appear to have all necessary firmware and > drivers. So, how do you fancy a bit of low level stuff? > > Reboot and first check firmware loading from 'journalctl'. root@debian-wheezy:/home/sarah# journalctl -b | grep 2200 Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Jul 04 18:01:31 debian-wheezy kernel: ipw2200 0000:03:03.0: firmware: direct-loading firmware ipw2200-bss.fw Jul 04 18:01:31 debian-wheezy kernel: ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) Jul 04 18:01:48 debian-wheezy NetworkManager[1240]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1e.0/0000:03:03.0/ieee80211/phy0/rfkill0) (driver ipw2200) Jul 04 18:01:48 debian-wheezy NetworkManager[1240]: <info> (wlan0): new 802.11 WiFi device (driver: 'ipw2200' ifindex: 3) root@debian-wheezy:/home/sarah# > Then > issue the command 'wpa_cli'. > > 1. wpa-cli > You get a prompt ">". This is interactive mode. A selected > interface should be shown. TAB completion of commands works. > Command history is with the UP and DOWN keys. The following > commands are typed at the prompt. root@debian-wheezy:/home/sarah# wpa-cli bash: wpa-cli: command not found root@debian-wheezy:/home/sarah# aptitude search wpa-supplicant root@debian-wheezy:/home/sarah# aptitude search wpa_supplicant root@debian-wheezy:/home/sarah# aptitude search net-tools i net-tools - NET-3 networking toolkit root@debian-wheezy:/home/sarah# aptitude search wireless-tools i A wireless-tools - Tools for manipulating Linux Wireless Extensions root@debian-wheezy:/home/sarah# plus a good deal of Googling. I am stuck. Of what package is wpa-cli a part? Where will I find it?? Ah!! We have wpa-cli AND wpa_cli. Let's try wpa_cli root@debian-wheezy:/home/sarah# wpa_cli wpa_cli v2.3 Copyright (c) 2004-2014, Jouni Malinen <j@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'wlan0' Interactive mode <3>CTRL-EVENT-SCAN-RESULTS > add_network 0 <3>CTRL-EVENT-SCAN-RESULTS > set_network 0 ssid NETGEAR08 FAIL > set_network 0 ssid netgear08 FAIL <3>CTRL-EVENT-SCAN-RESULTS > add_network 1 <3>CTRL-EVENT-SCAN-RESULTS artwh > set_network psk xxxxxxx Invalid SET_NETWORK command: needs three arguments (network id, variable name, and value) > I'm stuck. Or out of my depth. Or drowning. Or all three. :-( But there seesm ot be a problem with my SSID Not set by me - perhaps I should change it. :-( Help!!! Lisi > 2. add_network > You'll probably get 0 for the network number. > > 3. set_network 0 ssid "Your_SSID" > The response should be "OK". > > 4. set_network psk "Your_passphrase" > The response should be "OK". > > 5. enable_network 0 > The response should be "OK". Authentication and association > should take place. > > 6. status 0 > Has it?
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-04 20:10 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRgtI-sg-15@gated-at.bofh.it> |
| In reply to | #169696 |
On Mon 04 Jul 2016 at 18:30:47 +0100, Lisi Reisz wrote: > root@debian-wheezy:/home/sarah# wpa-cli > bash: wpa-cli: command not found Do you think I would deliberately give a command which does not exist? Try using a bit of common or garden. It's a typo. [...Snip...] > Selected interface 'wlan0' Fine. > Interactive mode > > <3>CTRL-EVENT-SCAN-RESULTS > > add_network > 0 Ok. > <3>CTRL-EVENT-SCAN-RESULTS > > set_network 0 ssid NETGEAR08 > FAIL Look at what I typed. I was particularly careful at this point and nearly warned about leaving things out. > I'm stuck. Or out of my depth. Or drowning. Or all three. :-( But there > seesm ot be a problem with my SSID Not set by me - perhaps I should change There is no problem with your SSID.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-07-04 20:40 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRgWJ-BZ-13@gated-at.bofh.it> |
| In reply to | #169698 |
On Monday 04 July 2016 19:00:02 Brian wrote: > On Mon 04 Jul 2016 at 18:30:47 +0100, Lisi Reisz wrote: > > root@debian-wheezy:/home/sarah# wpa-cli > > bash: wpa-cli: command not found > > Do you think I would deliberately give a command which does not exist? > Try using a bit of common or garden. It's a typo. No, of course not. That didn't even cross my mind. I thought that there must be a package that I needed and didn't have installed and spent ages trying to find it. I did eventually spot the typo because the twice you had typed it were different. But detail is genuinely difficult for me to see - I only spotted it when I thought that I must have done a typo because the package was so unfindable. > [...Snip...] > > > Selected interface 'wlan0' > > Fine. > > > Interactive mode > > > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > add_network > > > > 0 > > Ok. > > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > set_network 0 ssid NETGEAR08 > > > > FAIL > > Look at what I typed. I was particularly careful at this point and > nearly warned about leaving things out. <quote> set_network 0 ssid "Your_SSID" </quote> What did I leave out that I should not have left out/not leave out that I should have left out? The quotation marks, I suppose. :-( Otherwise it would probably have been <your_SSID>? > > > I'm stuck. Or out of my depth. Or drowning. Or all three. :-( But > > there seesm ot be a problem with my SSID Not set by me - perhaps I > > should change > > There is no problem with your SSID. OK.. PEBCAK. But enlighten me so that I perhaps succeed in learning. I could do with knowing this in general, not just for this specific case. Thanks for the help. I either try and make a fool of myself, or learn nothing. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-07-04 21:00 +0200 |
| Subject | Re: Totally non-functioning wifi card- starting again completely was: Re: Laptop wireless problem |
| Message-ID | <rRhg6-IL-9@gated-at.bofh.it> |
| In reply to | #169704 |
On Mon 04 Jul 2016 at 19:32:47 +0100, Lisi Reisz wrote: > On Monday 04 July 2016 19:00:02 Brian wrote: > > On Mon 04 Jul 2016 at 18:30:47 +0100, Lisi Reisz wrote: > > > root@debian-wheezy:/home/sarah# wpa-cli > > > bash: wpa-cli: command not found > > > > Do you think I would deliberately give a command which does not exist? > > Try using a bit of common or garden. It's a typo. > > No, of course not. That didn't even cross my mind. I thought that there must > be a package that I needed and didn't have installed and spent ages trying to > find it. I did eventually spot the typo because the twice you had typed it > were different. But detail is genuinely difficult for me to see - I only > spotted it when I thought that I must have done a typo because the package > was so unfindable. Sorry. I was being contentious and grumpy. I prefer my contentious side :) > > [...Snip...] > > > > > Selected interface 'wlan0' > > > > Fine. > > > > > Interactive mode > > > > > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > > > add_network > > > > > > 0 > > > > Ok. > > > > > <3>CTRL-EVENT-SCAN-RESULTS > > > > > > > set_network 0 ssid NETGEAR08 > > > > > > FAIL > > > > Look at what I typed. I was particularly careful at this point and > > nearly warned about leaving things out. > > <quote> > set_network 0 ssid "Your_SSID" > </quote> > > What did I leave out that I should not have left out/not leave out that I > should have left out? The quotation marks, I suppose. :-( Otherwise it > would probably have been <your_SSID>? The quotation marks. They are required. <your_SSID> being correct could be checked with "scan" and "scan_results". > > > I'm stuck. Or out of my depth. Or drowning. Or all three. :-( But > > > there seesm ot be a problem with my SSID Not set by me - perhaps I > > > should change > > > > There is no problem with your SSID. > > OK.. PEBCAK. But enlighten me so that I perhaps succeed in learning. > > I could do with knowing this in general, not just for this specific case. > > Thanks for the help. I either try and make a fool of myself, or learn > nothing. You are not making a fool of yourself. I think the question is whether the network card is functioning. If the technique I have advocated does not produce association it becomes a possibility. Either that or the access point is malfunctioning. You cannot get any lower investigatory method than this without killing yourself with 0s and 1s. Personally, I am interested in the outcome that wpa_cli produces. (Notice I remembered the "_". :)
[toc] | [prev] | [next] | [standalone]
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web