unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 白熊 <guix-devel_gnu.org@sumou.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Gluglug X60 Guix howto
Date: Wed, 03 Dec 2014 00:00:48 -0500	[thread overview]
Message-ID: <87vblt72f3.fsf@yeeloong.lan> (raw)
In-Reply-To: <16DEF189-FB08-4A35-9BA1-13EF4BB26700@sumou.com> ("白熊"'s message of "Tue, 25 Nov 2014 12:56:07 +0300")

白熊 <guix-devel_gnu.org@sumou.com> writes:

> On 2014年11月23日 20:22:24 GMT+03:00, Alex Sassmannshausen <alex.sassmannshausen@gmail.com> wrote:
>>Hello,
>>
>>I received a request for instructions on how to get Guix running as
>>standalone on the Gluglug X60 — my work is ongoing (I haven't
>>reconfigured the Grub BIOS, nor have I got wireless working yet), but
>>a first draft may help other owners.
>
> I hope you can get the wireless working! Especially during Guix install...

I run standalone Guix on my Gluglug X60 with wireless.  All you have to
do is create a wpa_supplicant.conf file containing stanzas like this:

--8<---------------cut here---------------start------------->8---
network={
        ssid="my network name"
        key_mgmt=WPA-PSK
        psk="my network password"
}
--8<---------------cut here---------------end--------------->8---

and then run:

  wpa_supplicant -i wlp2s0 -c /path/to/wpa_supplicant.conf -B
  dhclient wlp2s0

If you have problems connecting to wireless, you can replace the "-B"
with "-d" in the wpa_supplicant command, which will run it in the
foreground with debugging output enabled.

     Regards,
       Mark

  reply	other threads:[~2014-12-03  5:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 17:22 Gluglug X60 Guix howto Alex Sassmannshausen
2014-11-23 18:36 ` David Thompson
2014-11-25  3:58 ` Jason Self
2014-11-25  9:56 ` 白熊
2014-12-03  5:00   ` Mark H Weaver [this message]
2014-12-03 16:48     ` Ludovic Courtès
2014-11-25 12:42 ` Ludovic Courtès
2014-11-25 13:22   ` Amirouche Boubekki
2014-11-25 14:40     ` Ludovic Courtès

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=87vblt72f3.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-devel_gnu.org@sumou.com \
    /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).