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.
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
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 cou
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
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 Li
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 s
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:
> >> > . It would obviously be helpful, but I have always heretofore
> >> > just accepted the interface name I was given! Google here I come
> >>
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
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
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.
reg
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
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
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 conne
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
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
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}=="x
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.
>
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 w
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}=="xxx", ATTR{dev_id}=="0x0", \
>
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}=="xxx", ATTR{dev_id}=="0x0", \
ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
why shouldn't
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 i
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:
> >> > . It would obviously be helpful, but I have always heretofore
> >> > just accepted the interface name I was given! Google here I come
> >> > again.
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
Lisi Reisz wrote:
> On Sunday 03 July 2016 21:36:58 deloptes wrote:
>> Lisi Reisz wrote:
>> > . 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 a
On 7/3/16, 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",
>> b
On Sunday 03 July 2016 21:36:58 deloptes wrote:
> Lisi Reisz wrote:
> > . 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
Lisi Reisz wrote:
> . 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
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
>
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
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 (onc
30 matches
Mail list logo
