Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #169609 > unrolled thread

Laptop wireless problem

Back to article view | Back to linux.debian.user

Contents

  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 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

#169648

Lisi Reisz wrote:

> Ah!  That could be part of the problem,but on its home network it has
> worked fine for several years, and stopped working suddenly on Friday
> afternoon, on the clients' premises,  while connected.  I had been
> upgrading earlier.

If it was working, then perhaps it messed up with the upgrades. I would
check if I have some older packages not completely removed - example
dpkg -l | grep '^rc'

If this does not help I would check tcpdump or tcp6dump.

regards

[toc] | [prev] | [next] | [standalone]

#169641

Lisi Reisz wrote:

> eth1      Link encap:Ethernet  HWaddr 00:16:6f:00:3a:b3

Ah and check txpower with iwconfig

sometimes it is set to 0dB rendering wireless useless.
example
iwconfig eth1 txpower 10

regards

[toc] | [prev] | [next] | [standalone]

#169642

On Sunday 03 July 2016 10:41:31 deloptes wrote:
> Lisi Reisz wrote:
> > eth1      Link encap:Ethernet  HWaddr 00:16:6f:00:3a:b3
>
> Ah and check txpower with iwconfig
>
> sometimes it is set to 0dB rendering wireless useless.
> example
> iwconfig eth1 txpower 10

root@debian-wheezy:/home/sarah# iwconfig eth1
eth1      IEEE 802.11bg  ESSID:off/any
          Mode:Managed  Frequency:2.437 GHz  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

root@debian-wheezy:/home/sarah#

Since txpower is currently set to 20 should I leave it alone for now?  Or 
change it to 30?

Thank you.
Lisi

[toc] | [prev] | [next] | [standalone]

#169633

Did you reload the ipw2000 module after installation of the firmware?
Don't know if 'modprobe -r ..' would work. Else you'd have to reboot.

Regards,
jvp.

[toc] | [prev] | [next] | [standalone]

#169647 — Re: Laptop wireless problem - very slight tangent

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. :-/

Lisi

[toc] | [prev] | [next] | [standalone]

#169658 — Re: Laptop wireless problem - very slight tangent

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. :-/
> 
> Lisi

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.

regards

[toc] | [prev] | [next] | [standalone]

#169659 — Re: Laptop wireless problem - very slight tangent

On Sunday 03 July 2016 19:59:50 deloptes 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. :-/
> >
> > Lisi

Thanks. :-)

> I assume you have not changed passwords on the access point recently.

Yes, I have - but before the laptop had been told what it was.  When I had 
gone onto the router to add the MAC address of the laptop.  But I will try to 
retype it in the laptop.  I am a lousy typist and an almost equally lousy 
proofreader.

Meanwhile, it is now worse than it was before, and is not seeing the access 
point at all. :-(

> 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.

If I can once get it started!  I thought that I would start again in the 
morning.

> It could be also 
> that your wpa_supplicant has issue(s).

Yes, I will investigate this.

> What I also think you should do, is change the name from eth1 to wlan0 if
> using jessie.

<gulp>.  It would obviously be helpful, but I have always heretofore just 
accepted the interface name I was given!  Google here I come again. 

Thanks.  
Lisi

[toc] | [prev] | [next] | [standalone]

#169660 — Re: Laptop wireless problem - very slight tangent

Lisi Reisz wrote:

> <gulp>.  It would obviously be helpful, but I have always heretofore just
> accepted the interface name I was given!  Google here I come again.

just comment out the eth1 lines from the udev file and reboot. it should add
the proper one after AFAIR

[toc] | [prev] | [next] | [standalone]

#169661 — Re: Laptop wireless problem - very slight tangent

On Sunday 03 July 2016 21:36:58 deloptes wrote:
> Lisi Reisz wrote:
> > <gulp>.  It would obviously be helpful, but I have always heretofore just
> > accepted the interface name I was given!  Google here I come again.
>
> just comment out the eth1 lines from the udev file and reboot. it should
> add the proper one after AFAIR

Thanks!  And AFAIR it will then be a random name that I can't remember. :-(  
Say what you like about wlan0 and eth3 they are easy to remember.  But I'll 
do it the next time I turn the laptop on, the first thing I do.

Lisi

[toc] | [prev] | [next] | [standalone]

#169666 — Re: Laptop wireless problem - very slight tangent

Lisi Reisz wrote:

> On Sunday 03 July 2016 21:36:58 deloptes wrote:
>> Lisi Reisz wrote:
>> > <gulp>.  It would obviously be helpful, but I have always heretofore
>> > just accepted the interface name I was given!  Google here I come
>> > again.
>>
>> just comment out the eth1 lines from the udev file and reboot. it should
>> add the proper one after AFAIR
> 
> Thanks!  And AFAIR it will then be a random name that I can't remember.
> :-(
> Say what you like about wlan0 and eth3 they are easy to remember.  But
> I'll do it the next time I turn the laptop on, the first thing I do.
> 
> Lisi

AFAIR it defaults to wlan[n] in jessie. At least when I upgraded this is
what I observed and I vaguely remember the wlan name was conventionally
used by other programs, but no even 40% sure.

D.

[toc] | [prev] | [next] | [standalone]

#169689 — Re: Laptop wireless problem - very slight tangent

On Monday 04 July 2016 08:48:46 deloptes wrote:
> Lisi Reisz wrote:
> > On Sunday 03 July 2016 21:36:58 deloptes wrote:
> >> Lisi Reisz wrote:
> >> > <gulp>.  It would obviously be helpful, but I have always heretofore
> >> > just accepted the interface name I was given!  Google here I come
> >> > again.
> >>
> >> just comment out the eth1 lines from the udev file and reboot. it should
> >> add the proper one after AFAIR
> >
> > Thanks!  And AFAIR it will then be a random name that I can't remember.
> >
> > :-(
> >
> > Say what you like about wlan0 and eth3 they are easy to remember.  But
> > I'll do it the next time I turn the laptop on, the first thing I do.
> >
> > Lisi
>
> AFAIR it defaults to wlan[n] in jessie. At least when I upgraded this is
> what I observed and I vaguely remember the wlan name was conventionally
> used by other programs, but no even 40% sure.


It defaulted to <trumpet roll> eth1. :-(

So, for the benefit of newbies, or perennial newbies like me, who aren't in 
the mood for a treasure hunt, I again went 
into /etc/udev/rules.d/70-persistent-net.rules and, crossing my fingers, 
reread the instructions at the top of the file and manually altered eth1 to 
wlan0.  It worked!!

But here is probably part of the problem:
<quote>
# PCI device 0x8086:0x4220 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
</quote>

So  it would appear that it now knows what the card is, but can't find the 
driver.  It can certainly no longer see the router at all, since the clear 
out and tidy up. :-(

FWIW I have removed the external card.  I can easily get a new internal card, 
which I initially hadn't thought of, and the external card wasn't actually 
helping. :-/

Lisi

[toc] | [prev] | [next] | [standalone]

#169701 — Re: Laptop wireless problem - very slight tangent

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?

lsmod
iwconfig
dmesg

[toc] | [prev] | [next] | [standalone]

#169707 — Re: Laptop wireless problem - very slight tangent

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# 

[toc] | [prev] | [next] | [standalone]

#169759 — Re: Laptop wireless problem - very slight tangent

On Mon 04 Jul 2016 at 09:48:46 (+0200), deloptes wrote:
> Lisi Reisz wrote:
> > On Sunday 03 July 2016 21:36:58 deloptes wrote:
> >> Lisi Reisz wrote:
> >> > <gulp>.  It would obviously be helpful, but I have always heretofore
> >> > just accepted the interface name I was given!  Google here I come
> >> > again.
> >>
> >> just comment out the eth1 lines from the udev file and reboot. it should
> >> add the proper one after AFAIR
> > 
> > Thanks!  And AFAIR it will then be a random name that I can't remember.
> > :-(
> > Say what you like about wlan0 and eth3 they are easy to remember.  But
> > I'll do it the next time I turn the laptop on, the first thing I do.
> 
> AFAIR it defaults to wlan[n] in jessie. At least when I upgraded this is
> what I observed and I vaguely remember the wlan name was conventionally
> used by other programs, but no even 40% sure.

It would be nice to know what the "it" is that chooses that default.
I have a laptop with the same IPW2200 wireless, and it has always
defaulted to eth1 in the same way as Lisi's did.

If it's a "default", that would imply that there's some way to choose
an alternative like wlan0 (which is indeed what, say, wicd will think
the interface ought to be named). How would I go about making this choice?
The installer displays something like:

Primary network interface:
eth0: Broadcom NetXtreme BCM5705 Gigabit Ethernet
eth1: Intel PRO/Wireless 2200BG [Calexico2] Network Connection

and you have the choice of selecting one or the other.

This laptop works perfectly well with eth1. It justs needs you
to change wlan0 to eth1 in wicd when you install it (Shift-P and
type eth1 in the appropriate box).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#169760 — Re: Laptop wireless problem - very slight tangent

On Tuesday 05 July 2016 16:02:52 David Wright wrote:
> It would be nice to know what the "it" is that chooses that default.
> I have a laptop with the same IPW2200 wireless, and it has always
> defaulted to eth1 in the same way as Lisi's did.
>
> If it's a "default", that would imply that there's some way to choose
> an alternative like wlan0 (which is indeed what, say, wicd will think
> the interface ought to be named). How would I go about making this choice?

After these agonising hours I can answer that:

Edit /etc/udev/rules.d/70-persistent-net.rules. 

Just cross your fingers, hold your breath, and follow the instructions at the 
top of the file.  In case of disaster, it seems it regenerate quite happily.  
(No, I didn't have a disaster - but deloptes' first suggestion was to comment 
out the eth1 line and reboot to give it the chance to generate wlan0.  But it 
didn't, it regenerated eth1.  So I left my commented out line just in case, 
and edited the new eth1 line.  I have now deleted the commented out line and 
just have:

sarah@debian-wheezy:~$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0/ssb0:0 
(b44)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:14:22:e7:6f:21", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x4220 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:16:6f:00:3a:b3", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
KERNEL=="eth*", NAME="wlan0"
sarah@debian-wheezy:~$ 

Lisi

[toc] | [prev] | [next] | [standalone]

#169762 — Re: Laptop wireless problem - very slight tangent

On Tue 05 Jul 2016 at 16:12:58 (+0100), Lisi Reisz wrote:
> On Tuesday 05 July 2016 16:02:52 David Wright wrote:
> > It would be nice to know what the "it" is that chooses that default.
> > I have a laptop with the same IPW2200 wireless, and it has always
> > defaulted to eth1 in the same way as Lisi's did.
> >
> > If it's a "default", that would imply that there's some way to choose
> > an alternative like wlan0 (which is indeed what, say, wicd will think
> > the interface ought to be named). How would I go about making this choice?
> 
> After these agonising hours I can answer that:
> 
> Edit /etc/udev/rules.d/70-persistent-net.rules. 
> 
> Just cross your fingers, hold your breath, and follow the instructions at the 
> top of the file.  In case of disaster, it seems it regenerate quite happily.  
> (No, I didn't have a disaster - but deloptes' first suggestion was to comment 
> out the eth1 line and reboot to give it the chance to generate wlan0.  But it 
> didn't, it regenerated eth1.

This is my point. Your *system* regenerated eth1. My *installer* generated eth1.
When I install, I have set
language
keyboard
locale
and I have provided a USB stick with the tg3 and ipw2200 firmware.
Nothing else.

I might look around and find a /etc/udev/rules.d/70-persistent-net.rules
file, but persist it will not! The only thing that persists at this
stage is /target, and that's barely begun construction at this step
in the installation. I think fiddling at that point is beyond even
an "expert" install.

So what I want to know from deloptes (or anyone else) is:

Why does this system (and yours) default to eth1, and
How can it be changed *at this point in the install*, if it
really is just a "default".

> So I left my commented out line just in case, 
> and edited the new eth1 line.  I have now deleted the commented out line and 
> just have:
> 
> sarah@debian-wheezy:~$ cat /etc/udev/rules.d/70-persistent-net.rules
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
> 
> # PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0/ssb0:0 
> (b44)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="00:14:22:e7:6f:21", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
> KERNEL=="eth*", NAME="eth0"
> 
> # PCI device 0x8086:0x4220 (ipw2200)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="00:16:6f:00:3a:b3", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
> KERNEL=="eth*", NAME="wlan0"
> sarah@debian-wheezy:~$ 

Agreed. I could do all this, but it would gain me nothing as
eth1 works perfectly ok.

I have a suspicion that, at some time in the past, not every kernel's
ipw2200 module has worked properly (even with the firmware apparently
correctly loaded). However, I have no evidence, and it's water under
the bridge. It could have been finger trouble on my part.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#169763 — Re: Laptop wireless problem - very slight tangent

On Tuesday 05 July 2016 16:32:32 David Wright wrote:
> I have a suspicion that, at some time in the past, not every kernel's
> ipw2200 module has worked properly (even with the firmware apparently
> correctly loaded).

MIne (or rather, my client's) isn't doing now.  We have proved that it can 
work.  But I still can't restart the laptop and find that wireless is 
working.  I still have to fiddle, and then fiddle some more.  And there is 
still a dns problem that I still haven't solved. (NM still isn't setting it 
properly).  Perhaps I should go back to wicd - but that wasn't working. :-(

I wonder whether it would be worth using a different kernel.  I hadn't thought 
of that.  I think that there is a kernel upgrade in the wings.  Next thing to 
investigate anyway.

Lisi

[toc] | [prev] | [next] | [standalone]

#169766 — Re: Laptop wireless problem - very slight tangent

Lisi Reisz wrote:

> MIne (or rather, my client's) isn't doing now.  We have proved that it can
> work.  But I still can't restart the laptop and find that wireless is
> working.  I still have to fiddle, and then fiddle some more.  And there is
> still a dns problem that I still haven't solved. (NM still isn't setting
> it properly).  Perhaps I should go back to wicd - but that wasn't working.
> :-(
> 
> I wonder whether it would be worth using a different kernel.  I hadn't
> thought of that.  I think that there is a kernel upgrade in the wings. 
> Next thing to investigate anyway.

I don't think it is a kernel issue.

Check 
ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 31 Jul  5
17:50 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf

some times it is created as local file. IF so remove/move it in tmp and run 

dhclient <interface>

The network manager (or wicd) should do this for you anyway.

regards

[toc] | [prev] | [next] | [standalone]

#169765 — Re: Laptop wireless problem - very slight tangent

David Wright wrote:

> This laptop works perfectly well with eth1. It justs needs you
> to change wlan0 to eth1 in wicd when you install it (Shift-P and
> type eth1 in the appropriate box).

Ah yes might have been the easier way.
The naming is set in
/etc/udev/rules.d/70-persistent-net.rules

I couldn't find out why and when it changed. Perhaps eth* is typical for
ipw2200 (However https://bbs.archlinux.org/viewtopic.php?id=78419)

Thanks for helping Lisi. I also suspected the wpa_supplicant for the
problems she had.

I found those articles pretty interesting and useful

https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_network_infrastructure
https://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_the_udev_system
https://wiki.debian.org/WiFi

regards

[toc] | [prev] | [next] | [standalone]

#169768 — Re: Laptop wireless problem - very slight tangent

On Tue 05 Jul 2016 at 18:20:15 +0200, deloptes wrote:

> David Wright wrote:
> 
> > This laptop works perfectly well with eth1. It justs needs you
> > to change wlan0 to eth1 in wicd when you install it (Shift-P and
> > type eth1 in the appropriate box).
> 
> Ah yes might have been the easier way.
> The naming is set in
> /etc/udev/rules.d/70-persistent-net.rules
> 
> I couldn't find out why and when it changed. Perhaps eth* is typical for
> ipw2200 (However https://bbs.archlinux.org/viewtopic.php?id=78419)

There is a complex interaction between the kernel and the modules it
loads. Naming of interfaces is the very least of the problems the OP
faces here and is a sideshow.

> Thanks for helping Lisi. I also suspected the wpa_supplicant for the
> problems she had.

The supplicant has been well and truly exonerated.

[toc] | [prev] | [next] | [standalone]

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | linux.debian.user

csiph-web