unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marek Paśnikowski" <mail@marekpasnikowski.name>
To: 54544@debbugs.gnu.org
Subject: bug#54544: Network Issue
Date: Wed, 30 Mar 2022 14:40:04 +0200	[thread overview]
Message-ID: <d8d031091c6b72c9babd6ada952084c71f0c2e68.camel@marekpasnikowski.name> (raw)
In-Reply-To: <393f69ed-8a16-0ad4-d4e3-e56b537727c9@raghavgururajan.name>

Greetings.

On Monday I installed the stable GuixSD on my newly acquired Lenovo
X200 with an Atheros Wi-Fi (ath9 driver). It worked like a charm, so I
decided to install the unstable variant.

Yesterday I lost half a day fighting to install and understand the
development release. The overall feeling of this particular issue is
that the kernel chokes on any significant Wi-Fi traffic and remains
under pressure even when I use the hardware switch to reload the
wireless card.

Today, I connect to the internet through an USB cable from my phone.
The wireless is disabled. System stability is perfect.

Could I ask for a configuration snippet which deploys an earlier
version of the kernel? This is my first serious attempt to learn Guix
and the documentation is unhelpful in this regard.

Thank You




  parent reply	other threads:[~2022-03-30 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 14:19 bug#54544: Network Issue Raghav Gururajan via Bug reports for GNU Guix
2022-03-26  3:08 ` Maxim Cournoyer
2022-03-26 13:16   ` Raghav Gururajan via Bug reports for GNU Guix
2022-03-29 11:44     ` Raghav Gururajan via Bug reports for GNU Guix
2022-03-30  4:44       ` Maxim Cournoyer
2022-03-30  8:51         ` Raghav Gururajan via Bug reports for GNU Guix
2022-03-30 12:40 ` Marek Paśnikowski [this message]
2022-03-30 21:31 ` Marek Paśnikowski
2022-04-16  4:43 ` Raghav Gururajan via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d8d031091c6b72c9babd6ada952084c71f0c2e68.camel@marekpasnikowski.name \
    --to=mail@marekpasnikowski.name \
    --cc=54544@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).