From: LamaRaz <LamaRaz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dhcpcd connection refused
Date: Wed, 22 Apr 2020 06:53:44 +0200 [thread overview]
Message-ID: <20200422045344.uYNXq5WHR5Dt_iavyhtilVQyFCsOchr00qhd6ElXcZU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21234@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
New comment by LamaRaz on void-packages repository
https://github.com/void-linux/void-packages/issues/21234#issuecomment-617546598
Comment:
no apparmor, it's a fresh system with nothing but lvm2 and crypsetup with efi
```
rd.auto=1
cryptdevice=UUID=<UUID>:lvm
ipv6.disable=1
net.ifnames=0
```
dhcpdcd also says "connected to access point 'xxx'"
with wpa_supplicant set up correctly and running
dhcpcd was also working fine when setting everything up from the live system, no surprise since it's an older version
the system in question does have one of those 32 bit EFI firmwares with a 64 bit CPU, no idea if it's related. After installing grub-x86_64-efi initially i also had to install grub-i386-efi
`grub-install --target=i386-efi --efi-directory=/boot/efi --bootloader-id=void_grub --boot-directory=/boot --recheck --debug`
next prev parent reply other threads:[~2020-04-22 4:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 4:42 [ISSUE] " LamaRaz
2020-04-22 4:44 ` Vaelatern
2020-04-22 4:45 ` LamaRaz
2020-04-22 4:46 ` LamaRaz
2020-04-22 4:46 ` LamaRaz
2020-04-22 4:48 ` LamaRaz
2020-04-22 4:49 ` LamaRaz
2020-04-22 4:52 ` LamaRaz
2020-04-22 4:52 ` LamaRaz
2020-04-22 4:53 ` LamaRaz [this message]
2020-04-22 5:02 ` LamaRaz
2020-04-22 5:11 ` LamaRaz
2020-04-22 5:11 ` LamaRaz
2020-04-22 5:46 ` Vaelatern
2020-04-22 14:18 ` Piraty
2020-04-22 14:19 ` Piraty
2020-04-22 14:20 ` xtraeme
2020-04-22 14:20 ` Piraty
2020-04-22 14:25 ` ErinVoid
2020-04-22 14:28 ` Piraty
2020-04-22 14:29 ` [ISSUE] [CLOSED] " Piraty
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200422045344.uYNXq5WHR5Dt_iavyhtilVQyFCsOchr00qhd6ElXcZU@z \
--to=lamaraz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).