On Saturday 02 July 2016 01:15:27 Lisi Reisz wrote:
> The built in wireless on the Dell Inspiron 9300 suddenly stopped working.
>
> Having poked around a bit with wicd and network-manager (not
> simultaneously), I am checking whether the problem is sudden hardware
> failure. I plugged in a USB net
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 Tue 05 Jul 2016 at 15:13:28 (+0100), Lisi Reisz wrote:
> Footnote:
> Just tried to ssh in from my box and got this:
>
> lisi@Tux-II:~$ ssh sarah@debian-wheezy.local
> ssh: Could not resolve hostname debian-wheezy.local: Name or service not known
> lisi@Tux-II:~$
>
> It's connected, but not.
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 Tuesday 05 July 2016 15:05:37 Lisi Reisz wrote:
> On Tuesday 05 July 2016 14:54:34 Lisi Reisz wrote:
> > On Tuesday 05 July 2016 09:26:00 Brian wrote:
> > > On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote:
> > > > > status 0
> > > >
> > > > bssid=00:8e:f2:8f:58:58
> > > > freq=0
> > > > s
On Tuesday 05 July 2016 14:54:34 Lisi Reisz wrote:
> On Tuesday 05 July 2016 09:26:00 Brian wrote:
> > On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote:
> > > > status 0
> > >
> > > bssid=00:8e:f2:8f:58:58
> > > freq=0
> > > ssid=NETGEAR08
> > > id=0
> > > mode=station
> > > pairwise_cipher=C
On Tuesday 05 July 2016 09:26:00 Brian wrote:
> On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote:
> > > status 0
> >
> > bssid=00:8e:f2:8f:58:58
> > freq=0
> > ssid=NETGEAR08
> > id=0
> > mode=station
> > pairwise_cipher=CCMP
> > group_cipher=CCMP
> > key_mgmt=WPA2-PSK
> > wpa_state=COMPLETED
On Mon 04 Jul 2016 at 23:39:26 +0100, Lisi Reisz wrote:
> > status 0
> bssid=00:8e:f2:8f:58:58
> freq=0
> ssid=NETGEAR08
> id=0
> mode=station
> pairwise_cipher=CCMP
> group_cipher=CCMP
> key_mgmt=WPA2-PSK
> wpa_state=COMPLETED
> address=xx:xx:xx:xx:xx
> uuid=
You have a fully functional wireless
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 h
On Monday 04 July 2016 23:39:26 Lisi Reisz wrote:
> On Monday 04 July 2016 23:36:44 Lisi Reisz wrote:
> > 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
On Mon 04 Jul 2016 at 18:30:47 +0100, Lisi Reisz wrote:
> root@debian-wheezy:/home/sarah# wpa_cli
That is the correct command.
> wpa_cli v2.3
> Copyright (c) 2004-2014, Jouni Malinen and contributors
>
> This software may be distributed under the terms of the BSD license.
> See README for more
On Monday 04 July 2016 23:36:44 Lisi Reisz wrote:
> 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
> > > DRI
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 h
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 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 c
On Monday 04 July 2016 19:32:47 Lisi Reisz wrote:
> Thanks for the help. I either try and make a fool of myself, or learn
> nothing.
Sorry, again. Punctuation. Try; and make a fool of myself; or don't try, and
learn nothing.
Lisi
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. I
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 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'
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: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 h
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
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 abou
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
On Monday 04 July 2016 15:16:23 Brian wrote:
> On Mon 04 Jul 2016 at 14:53:13 +0100, Lisi Reisz wrote:
> > On Saturday 02 July 2016 14:07:45 deloptes wrote:
> > > Lisi Reisz wrote:
> > > > Where next?
> > >
> > > reload wifi kernel modules and get dmesg
> > >
> > > try iwlconfig
> > >
> > > check i
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.
>
On Mon 04 Jul 2016 at 14:53:13 +0100, Lisi Reisz wrote:
> On Saturday 02 July 2016 14:07:45 deloptes wrote:
> > Lisi Reisz wrote:
> > > Where next?
> >
> > reload wifi kernel modules and get dmesg
> >
> > try iwlconfig
> >
> > check if you have the appropriate firmware
>
>
> sarah@debian-wheezy:
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", \
>
On Saturday 02 July 2016 14:07:45 deloptes wrote:
> Lisi Reisz wrote:
> > Where next?
>
> reload wifi kernel modules and get dmesg
>
> try iwlconfig
>
> check if you have the appropriate firmware
sarah@debian-wheezy:~$ dmesg | grep 2200
[ 11.175897] ipw2200: Intel(R) PRO/Wireless 2200/2915 Netw
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
Lisi Reisz wrote on 07/03/16 17:56:
> On Sunday 03 July 2016 15:05:00 Lisi Reisz wrote:
>> On Sunday 03 July 2016 14:56:07 Lisi Reisz wrote:
>>> On Sunday 03 July 2016 14:49:44 deloptes wrote:
Lisi Reisz wrote:
> Ah! That could be part of the problem,but on its home network it has
> w
On Sunday 03 July 2016 15:05:00 Lisi Reisz wrote:
> On Sunday 03 July 2016 14:56:07 Lisi Reisz wrote:
> > On Sunday 03 July 2016 14:49:44 deloptes wrote:
> > > Lisi Reisz wrote:
> > > > Ah! That could be part of the problem,but on its home network it has
> > > > worked fine for several years, and
On Sunday 03 July 2016 14:56:07 Lisi Reisz wrote:
> On Sunday 03 July 2016 14:49:44 deloptes wrote:
> > 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 c
On Sunday 03 July 2016 14:49:44 deloptes wrote:
> 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
> > upgradin
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
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
On Sunday 03 July 2016 12:53:22 deloptes wrote:
> Lisi Reisz wrote:
> > 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
Lisi Reisz wrote:
> 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 a
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# iwc
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
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
Lisi Reisz wrote:
> root@debian-wheezy:~# dmesg | grep wifi
> [ 13.615263] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
> [ 13.615316] usb 1-1: firmware: failed to load
> [ rtlwifi/rtl8192cufw_TMSC.bin
> (-2)
> [ 13.634110] usb 1-1: firmware: failed to load rtlwifi/rtl8192cufw.bin
> [
On Saturday 02 July 2016 19:28:00 deloptes wrote:
> 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 s
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.
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.
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.
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 upgradin
On Saturday 02 July 2016 15:33:40 Jörg-Volker Peetz wrote:
> Lisi Reisz wrote on 07/02/16 02:15:
> > The built in wireless on teh Dell Inspiron 9300 suddenly stopped working.
> > Having poked around a bit with wicd and network-manager (not
> > simultaneously),
>
>
>
> > sarah@debian-wheezy:~$ grep
On Saturday 02 July 2016 14:07:45 deloptes wrote:
> Lisi Reisz wrote:
> > Where next?
>
> reload wifi kernel modules and get dmesg
>
> try iwlconfig
iwlconfig doesn't seem to exist, anyhow in Debina so:
root@debian-wheezy:/home/sarah# iwconfig
lono wireless extensions.
eth0 no wirel
Lisi Reisz wrote on 07/02/16 02:15:
> The built in wireless on teh Dell Inspiron 9300 suddenly stopped working.
> Having poked around a bit with wicd and network-manager (not simultaneously),
>
> sarah@debian-wheezy:~$ grep wifi /proc/modules
> rtlwifi 45511 2 rtl8192cu,rtl_usb, Live 0xf829b00
Lisi Reisz wrote:
> Where next?
reload wifi kernel modules and get dmesg
try iwlconfig
check if you have the appropriate firmware
regards
On Saturday 02 July 2016 06:23:34 Francesco Ariis wrote:
> On Sat, Jul 02, 2016 at 01:46:37AM +0100, Lisi Reisz wrote:
> > [...]
>
> Please you are already a prolific poster, try at least to reply
> to your own threads with the proper `In-Reply-To` header or we'll
> get one new thread for every mes
On Sat, Jul 02, 2016 at 01:46:37AM +0100, Lisi Reisz wrote:
> [...]
Please you are already a prolific poster, try at least to reply
to your own threads with the proper `In-Reply-To` header or we'll
get one new thread for every message you post.
Further to the two from me which haven't got through yet (threading is going
to be really mucked up) having appeared to connect through /e/n/i/, and got
only an IPv6 address so that I appeared to be unable to make any actual
connections anywhere, I obviously did get through because, from my rout
The following lines in /e/n/i worked and wireless is now running (I am
connected over it with ssh), so the hardware is fine - though it is the
onboard card that is working, and the USB card is still not!!
sarah@debian-wheezy:~$ cat /etc/network/interfaces
# This file describes the network interf
When booting up the messages reported failure to load something to do with the
wireless cards. It went by too fast and too small for me to read it
properly. And I have tried one modification of the /e/n/i file, but if the
drivers haven't loaded, it won't do any good.
Original message.
The bui
The built in wireless on teh Dell Inspiron 9300 suddenly stopped working.
Having poked around a bit with wicd and network-manager (not simultaneously),
I am checkinh whether the problem is sudden hardware failure. I plugged in a
USB network card.
Here is what I get:
sarah@debian-wheezy:~$ ls
76 matches
Mail list logo
