On Mon, May 24, 2021 at 09:50:04PM -0400, Polyna-Maude Racicot-Summerside wrote:
>
>
> On 2021-05-24 1:16 p.m., Henning Follmann wrote:
> > On Mon, May 24, 2021 at 12:24:30PM -0400, Polyna-Maude Racicot-Summerside
> > wrote:
[...]
> >>
> >> What a crazy thing here...
> >> Now desktop
Polyna-Maude Racicot-Summerside wrote:
> You are exactly pointing to a real solution here.
> It's jumping pretty fast to conclusion about Gnome itself being the
> cause of any type of network problem.
Sorry for the sarcasm and it might be inappropriate on the list, but I can
not hold it :D
Gnome
On 2021-05-24 1:16 p.m., Henning Follmann wrote:
> On Mon, May 24, 2021 at 12:24:30PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>>
>>
>> On 2021-05-24 11:47 a.m., Juan R. de Silva wrote:
>>> On Sun, 23 May 2021 21:53:45 -0700, David Christensen wrote:
>>>
> [...]
>>>
>>> I finally
On 2021-05-24 1:31 p.m., Charles Curley wrote:
> On Mon, 24 May 2021 15:47:26 - (UTC)
> "Juan R. de Silva" wrote:
>
>> Right now I'm inclined to resolve this odd problem by reinstalling
>> Debian. It looks to be an easier path comparing to finding a weird
>> GNOME bug without even having
On Mon, 24 May 2021 15:47:26 - (UTC)
"Juan R. de Silva" wrote:
> Right now I'm inclined to resolve this odd problem by reinstalling
> Debian. It looks to be an easier path comparing to finding a weird
> GNOME bug without even having a minimal clue of what part might be
> responsible for it.
On Mon, May 24, 2021 at 12:24:30PM -0400, Polyna-Maude Racicot-Summerside wrote:
>
>
> On 2021-05-24 11:47 a.m., Juan R. de Silva wrote:
> > On Sun, 23 May 2021 21:53:45 -0700, David Christensen wrote:
> >
[...]
> >
> > I finally narrowed the problem to one specific source by installing
> >
On 2021-05-24 11:47 a.m., Juan R. de Silva wrote:
> On Sun, 23 May 2021 21:53:45 -0700, David Christensen wrote:
>
>> On 5/23/21 4:55 PM, Juan R. de Silva wrote:
>>> Help needed from somebody with the better networking knowledge than
>>> mine.
>>>
>>> Debian Buster on Dell M4800 Mobile
On Sun, 23 May 2021 21:53:45 -0700, David Christensen wrote:
> On 5/23/21 4:55 PM, Juan R. de Silva wrote:
>> Help needed from somebody with the better networking knowledge than
>> mine.
>>
>> Debian Buster on Dell M4800 Mobile Workstation, Intel Corporation
>> Wireless 7260 (rev bb) WiFi
On 5/23/21 4:55 PM, Juan R. de Silva wrote:
Help needed from somebody with the better networking knowledge than mine.
Debian Buster on Dell M4800 Mobile Workstation, Intel Corporation
Wireless 7260 (rev bb) WiFi adapter. The ISP modem offers 2 WiFi bands:
2.4G & 5G. The system connects
Help needed from somebody with the better networking knowledge than mine.
Debian Buster on Dell M4800 Mobile Workstation, Intel Corporation
Wireless 7260 (rev bb) WiFi adapter. The ISP modem offers 2 WiFi bands:
2.4G & 5G. The system connects automatically to 5G. 2.4G is reserved for
my
David (12021-02-19):
> This link reports setting "D3 cold" or similar in BIOS worked for that
> Intel 3165, does that help you?
> https://askubuntu.com/questions/1204683/intel-3165-not-working-on-ubuntu-19-10
Thank you both. I had not found that link.
I tried looking in the setup as suggested,
On Fri, Feb 19, 2021 at 11:31:28AM +0100, Nicolas George wrote:
[...]
> I have searched on the web for this "D3hot to D0" error but found only
> stuff related to NVidia hardware.
>
> Does anybody have an idea about what to try?
Not very much directly, but at least a proposed enhancement to
On Fri, 19 Feb 2021 at 21:31, Nicolas George wrote:
> [ 19.292289] iwlwifi :01:00.0: can't change power state from D3hot to
> D0 (config space inaccessible)
This link reports setting "D3 cold" or similar in BIOS worked for that
Intel 3165, does that help you?
[ Re-sending this mail, because it didn't arrive the first time. ]
Hi.
I have one of the laptops given to the students and teachers of
Île-de-France, i.e. cheap hardware (overcharged to taxpayers), booted
with Debian Live (KDE+firmware edition), and the wifi does not work.
The wifi controller
On 2020-08-05 18:01 +0100, Hilary Snaden wrote:
> Following the recent discussion about Atheros AR9271 wifi no longer working.
>
> After the most recent kernel update to 5.7.10-1 (2020-07-26), my
> AR9271 wifi dongle is recognised again, but there is now a worse
> problem: if I use the dongle,
Following the recent discussion about Atheros AR9271 wifi no longer working.
After the most recent kernel update to 5.7.10-1 (2020-07-26), my AR9271
wifi dongle is recognised again, but there is now a worse problem: if I
use the dongle, the box gradually freezes over the course of around 5 to
Okay i will try these links..thank you very much Bruce and Osamu [?]
On Sat, Mar 14, 2015 at 6:10 PM, Osamu Aoki os...@debian.org wrote:
Hi,
On Thu, Mar 12, 2015 at 09:35:13PM +0400, Gajadur Dwijesh wrote:
Hello..i have Debian wheezy 7.8 KDE installed on my laptop..i am not able
to get
Hi,
On Thu, Mar 12, 2015 at 09:35:13PM +0400, Gajadur Dwijesh wrote:
Hello..i have Debian wheezy 7.8 KDE installed on my laptop..i am not able
to get wifi connection..can someone help please?
Thank you
Debian does not install non-free things in its default installation.
Unfortunately, many
Hello..i have Debian wheezy 7.8 KDE installed on my laptop..i am not able
to get wifi connection..can someone help please?
Thank you
On 14/06/13 00:02, Doug Button wrote:
Thanks for the help, but it doesn't sound quite like my problem. I
haven't changed any network settings and these problems are only
occurring on this one device.
I should probably also mention that according to lspci my WiFi model
is Intel Corporation
Sorry, sent to private mail. I re-send to the list:
What model is your wireless card?
We need know your hardware to help you.
Regards
El Jueves, 13 de Junio de 2013 19.27 CLT, Doug Button yne...@gmail.com
Ha escrito:
I have been having a WiFi problem for a few months now, and I think I
On Thu, 2013-06-13 at 23:02 -0400, Doug Button wrote:
Thanks for the help, but it doesn't sound quite like my problem. I
haven't changed any network settings and these problems are only
occurring on this one device.
I should probably also mention that according to lspci my WiFi model is
I'm not saying this is your issue but a few months back I had a
similar problem and it turned out to be my wireless card wasn't
exactly compatible with the latest IEEE 802.11N standard. Changing my
router to B/G solved the issue for me.
If nothing else, you could at least give it a try.
--
I
I have been having a WiFi problem for a few months now, and I think I
should finally fix it. I am using a Lenovo Ideapad Z370 with Gnome 3's
network manager. Whenever I connect to a WiFi network, I have one or more
of these three problems.
1. The speed of the network drops drastically. Usually
On Thu, 2013-06-13 at 19:27 -0400, Doug Button wrote:
I have been having a WiFi problem for a few months now, and I think I
should finally fix it. I am using a Lenovo Ideapad Z370 with Gnome 3's
network manager. Whenever I connect to a WiFi network, I have one or
more of these three problems
Thanks for the help, but it doesn't sound quite like my problem. I
haven't changed any network settings and these problems are only
occurring on this one device.
I should probably also mention that according to lspci my WiFi model is
Intel Corporation Centrino Wireless-N 1000 [Condor Peak].
Just tried installing 7 firmware-b43-installer again and noticed it says
this:
Unsupported device(s) found: PCI id 14e4:472
On 14/11/12 10:39, Andrew Wood wrote:
Im trying to setup Wheezy with Gnome 3 on a Lenovo E535 which has an
AMD Radeon video chip and a Broadcom WiFi chip.
Despite
Im trying to setup Wheezy with Gnome 3 on a Lenovo E535 which has an AMD
Radeon video chip and a Broadcom WiFi chip.
Despite installing the b43 firmware packages dmesg | grep 'firmware#
still shows:
3400.531552] ieee80211 phy1: brcmsmac: fail to load firmware
brcm/bcm43xx-0.fw
[
Ok so Ive now discovered that I need to install firmware-brcm80211 which
has cleared the error about missing firmware but it still cant see any
networks despite modprobing brcmsmac and rebooting
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe.
There's a bit of acronym-soup here, for context check out the
list archives from May 2011.
I had this weird WPA-EAP TTLS problem at that time, and have
now finally gotten it resolved.
The key was to finally run a packet sniffer on the wireless port and
watch the authentication as it
On Fri, 20 May 2011 20:47:21 -0400
Andrew Reid rei...@bellatlantic.net wrote:
So, apologies for the long-windedness, but what can cause EAP to
fail? Do I need to add some libraries with more authentication
schemes in them somehow? Obviously I have all the dependencies of
wpa_supplicant,
On Fri, 20 May 2011 20:47:21 -0400
Andrew Reid rei...@bellatlantic.net wrote:
So, apologies for the long-windedness, but what can cause EAP to
fail? Do I need to add some libraries with more authentication
schemes in them somehow? Obviously I have all the dependencies of
Hi all --
I'm having a strange problem with my wireless connection, and I'm running
out of ideas.
I have a ThinkPad T510 laptop, running stock Debian squeeze. I use
the KDE desktop, but I think that's not an issue, because I've reproduced
the problem without any network managers or
L.V.Gandhi wrote:
snip
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# auto eth0
iface eth0 inet dhcp
pre-up ifconfig eth0 up
pre-up grep -q ndiswrapper /proc/modules || modprobe ndiswrapper
wireless_essid mohan
On 1/28/07, Jan Schledermann [EMAIL PROTECTED] wrote:
L.V.Gandhi wrote:
snip
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# auto eth0
iface eth0 inet dhcp
pre-up ifconfig eth0 up
pre-up grep -q ndiswrapper
L.V.Gandhi wrote:
On 1/28/07, *Jan Schledermann* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
L.V.Gandhi wrote:
snip
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# auto
I used to work with this wifi comfortably in sarge with ndiswrapper. In etch
i have problems.
first bcm43xx driver didn't work with the firmware extracted automatically
while installation and also from the working driver in windows. I copied the
files as read in /lib/hotplug/firmware. I have read
37 matches
Mail list logo
