unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD is missing /dev/disk/by-uuid
Date: Sun, 14 Feb 2016 14:42:38 -0800	[thread overview]
Message-ID: <87povy52xt.fsf@gmail.com> (raw)
In-Reply-To: <87egclpnea.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 09 Feb 2016 22:46:53 +0100")

Hi,

I ran those commands, and it fixed the problem: /dev/disk/by-uuid now
exists and contains the links I expected to see.

However, it introduced a new problem. Now, my network interface eth0
does not show up like it did before. For example, when I run ifconfig,
"lo" shows up but "eth0" is missing. Nothing that relies on the network
works.

I've compared /var/log/messages before and after. Before the
reconfigure, it contained the following messages from "b44" (I think
this is my ethernet driver). This seems to show eth0 being successfully
set up:

--8<---------------cut here---------------start------------->8---
Feb 14 12:52:44 localhost vmunix: [    8.172311] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
Feb 14 12:52:44 localhost vmunix: [    8.192588] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:19:b9:7e:b4:cd
Feb 14 12:52:48 localhost vmunix: [   45.812218] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
Feb 14 12:52:48 localhost vmunix: [   45.812226] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
Feb 14 12:52:48 localhost vmunix: [   55.223285] b44 ssb0:0 eth0: powering down PHY
Feb 14 12:52:48 localhost vmunix: [   55.252555] b44 ssb0:0 eth0: powering down PHY
Feb 14 12:52:52 localhost vmunix: [   61.812216] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
Feb 14 12:52:52 localhost vmunix: [   61.814593] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
--8<---------------cut here---------------end--------------->8---

However, after the upgrade, I only see the following messages:

--8<---------------cut here---------------start------------->8---
Feb 14 12:12:16 localhost vmunix: [   10.820248] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
Feb 14 12:12:16 localhost vmunix: [   10.848595] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:19:b9:7e:b4:cd
--8<---------------cut here---------------end--------------->8---

I've checked messages, dmd.log, and shepherd.log in /var/log/, but I
can't figure out why networking isn't working. I found a similar problem
on the Guix bug tracker:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18483

However, I don't see messages like those in my logs, so I'm not sure
it's the same problem.

How can I proceed? My goal is to make networking work, like it did
before the reconfigure. I don't think I can use the new version of guix
until I get this networking problem fixed. Any advice would be
appreciated.

Thank you,
Chris

  reply	other threads:[~2016-02-14 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 10:40 GuixSD is missing /dev/disk/by-uuid Chris Marusich
2016-02-09 21:46 ` Ludovic Courtès
2016-02-14 22:42   ` Chris Marusich [this message]
2016-02-16  7:19     ` Chris Marusich

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=87povy52xt.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@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.
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).