From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Wired networking problems after guix system reconfigure
Date: Fri, 04 Mar 2016 09:59:27 -0800 [thread overview]
Message-ID: <874mcm2kg0.fsf@gmail.com> (raw)
In-Reply-To: 8737s67h5e.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> Perfect. To avoid modifying files in the Guix tree itself, you could
> put this ‘linux-libre-4.3’ in a module of its own that you keep in
> $GUIX_PACKAGE_PATH, just for your own uses.
OK. I'll try that! Can you tell me why commit adddd5b updates
Makefile.am? That wasn't clear to me, and I don't want to accidentally
forget to do something necessary for installing a custom kernel.
> Now, if the regression is serious and widespread, you might want to
> start an argument on guix-devel as to whether we should provide this
> particular kernel version in Guix proper.
I don't think it's necessary. I haven't heard complaints from anyone
else yet, and I'm pretty sure the linux-libre-4.1 variable that already
exists will work for me, also. I'll consider starting a thread if that
is not the case. I mainly just want to know how to define my own custom
kernel so I can try bisecting the kernel myself to pinpoint the problem.
To help others in the future find this thread if they encounter the same
problem, here are my wired network card specs, according to lspci:
Laptop: Dell Inspiron 1520
Network card: Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
Oh, by the way: there is a wireless network card, also, but it has never
worked (dmesg shows iwl3945 complaining: "Direct firmware load for
/*(DEBLOBBED)*/ failed")), so that isn't a viable alternative for me.
Thank you for the help,
Chris
next prev parent reply other threads:[~2016-03-04 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 8:40 Wired networking problems after guix system reconfigure Chris Marusich
2016-03-04 6:33 ` Chris Marusich
2016-03-04 8:59 ` Ludovic Courtès
2016-03-04 17:59 ` Chris Marusich [this message]
2016-03-07 9:50 ` Ludovic Courtès
2016-03-07 11:05 ` Chris Marusich
2016-03-07 12:47 ` Andreas Enge
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=874mcm2kg0.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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.
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).