GNU bug report logs -
#35630
graphical install, no network device found (HP EliteDesk 800 G1)
Previous Next
To reply to this bug, email your comments to 35630 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#35630
; Package
guix
.
(Wed, 08 May 2019 08:40:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Giovanni Biscuolo <g <at> xelera.eu>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 08 May 2019 08:40:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Guix,
executive summary: this bug is still to be triaged since I've
succesfully used the same steps some days ago, so it could be a false
positive
I'm having a strange error when installing Guix 1.0.0 from USB media
using the Newt Graphical Install
Recently I succesfully installed using the same steps (newt installer)
and the network was succesfully detected, but now I got this message
twice [1]:
--8<---------------cut here---------------start------------->8---
...requires internet access but no network device were found
--8<---------------cut here---------------end--------------->8---
Switching to a terminal console I was able to:
1. check the eno1 interface was correctly detected (via "ip a ls")
2. start the interface (ifconfig eno1 up)
3. get an IP via DHCP client (dhclient -v eno1)
4. ping gnu.org
Sorry but I don't know how to debug the installer or find a specific log
file from it to help better understand why the installer does not find
the network device
Following /var/log/debug on a console I see no error messages right
before the above mentioned message appears in installer, even selecting
"Continue" or exiting the next dialog and re-selecting
After eno1 "manual" setup I was able to complete the install
As I already mentioned, some day ago I'm *sure* the installer correctly
detected and activated the network interface (using another USB pen
drive) and I really don't understand what changed here :-O
The one and only test that comes to my mind is to double check the
content wrote to the pen drive is not somehow corrupted, I got it and
dd'ed following the Guix manual instructions [2]
I'll check and/or redo my install media to see if that's the problem
If you have any other hint or "debug trick" please comment
Thanks! Gio'
[1] I rebooted the machine and tried again
[2] https://www.gnu.org/software/guix/manual/en/html_node/USB-Stick-and-DVD-Installation.html#USB-Stick-and-DVD-Installation
--
Giovanni Biscuolo
Xelera IT Infrastructures
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35630
; Package
guix
.
(Wed, 08 May 2019 09:32:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 35630 <at> debbugs.gnu.org (full text, mbox):
On Wed, May 08, 2019 at 10:39:20AM +0200, Giovanni Biscuolo wrote:
> Hello Guix,
>
> executive summary: this bug is still to be triaged since I've
> succesfully used the same steps some days ago, so it could be a false
> positive
>
I hope this is an instance of <https://issues.guix.info/issue/35550>,
that is “herd status wpa-supplicant” shows that wpa-supplicant is
stopped instead of running? I hope there will be a new release soon
where this is fixed.
Regards,
Florian
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35630
; Package
guix
.
(Wed, 08 May 2019 10:05:02 GMT)
Full text and
rfc822 format available.
Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Guix,
actually I had a faulty USB media (details below): I've redone it but
nothing changed, I'm still getting the "Internet access" dialog with an
error message telling "no network device were found"
Giovanni Biscuolo <g <at> xelera.eu> writes:
[...]
> The one and only test that comes to my mind is to double check the
> content wrote to the pen drive is not somehow corrupted, I got it and
> dd'ed following the Guix manual instructions [2]
>
> I'll check and/or redo my install media to see if that's the problem
--8<---------------cut here---------------start------------->8---
$ sudo cmp -n `stat -c '%s' guix-system-install-1.0.0.x86_64-linux.iso` guix-system-install-1.0.0.x86_64-linux.iso /dev/sdb
guix-system-install-1.0.0.x86_64-linux.iso /dev/sdb differ: byte 4128769, line 1274
--8<---------------cut here---------------end--------------->8---
so I computed the sha1sum of the downloades ISO image:
--8<---------------cut here---------------start------------->8---
$ sha1sum guix-system-install-1.0.0.x86_64-linux.iso
724eaa8f6f80ed65d07965f2b96282023c6736c3 guix-system-install-1.0.0.x86_64-linux.iso
--8<---------------cut here---------------end--------------->8---
and the one from my pen drive:
--8<---------------cut here---------------start------------->8---
$ sudo head -c $(stat -c '%s' guix-system-install-1.0.0.x86_64-linux.iso) /dev/sdb | sha1sum
9ad81a175d49df62561bb274cc74bafb7a9cc199 -
--8<---------------cut here---------------end--------------->8---
they differ: the USB pen drive image was corrupted!
now I remember: I'm almost sure I did not _sync_ the device after dd, as
clearly stated in the documentation
I copied the ISO again (dd if=guix-system-install-1.0.0.system.iso
of=/dev/sdX && sync) and re-computed the USB pen drive sha1sum:
--8<---------------cut here---------------start------------->8---
$ time sudo head -c $(stat -c '%s' guix-system-install-1.0.0.x86_64-linux.iso) /dev/sdb | sha1sum
724eaa8f6f80ed65d07965f2b96282023c6736c3 -
--8<---------------cut here---------------end--------------->8---
it corresponds to the ISO one now
really strange...
HTH! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#35630
; Package
guix
.
(Wed, 08 May 2019 11:34:03 GMT)
Full text and
rfc822 format available.
Message #14 received at 35630 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Florian,
thank you for pointing me to the right bug report!
I checked the bug reports list via web [1] but did not link
wpa-supplicant to my issue since I did not realized that such an issue
also affects wired connections
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> writes:
> I hope this is an instance of <https://issues.guix.info/issue/35550>,
> that is “herd status wpa-supplicant” shows that wpa-supplicant is
> stopped instead of running? I hope there will be a new release soon
> where this is fixed.
yes, this is definitely an instance of #35550
I confirm I see the very same wpa_supplicant log messages in
/var/log/messages as reported by Sirgazil and pelzflorian
the following suggested workaround (in a text console activated via
CTRL-ALT-F3) works for me:
--8<---------------cut here---------------start------------->8---
pkill wpa_supplicant
herd start networking
--8<---------------cut here---------------end--------------->8---
after that I was able to restart the "Network interface" installer step
(by choosing "Exit" and selecting it again in the proposed dialog) and
was able to select the wired interface
Thanks! Gio'
[1] I'm going to subscribe bug-guix :-)
--
Giovanni Biscuolo
Xelera IT Infrastructures
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 6 years and 35 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.