search

pop-os / beta

Pop!_OS Beta
359 stars 19 forks source link

[21.04] Iso exits from GUI after boot when Ethernet is plugged in #153

Closed Cantello closed 3 years ago

Cantello commented 3 years ago

How did you upgrade to 21.04? (Fresh install / Upgrade) Fresh install.

Related Application and/or Package Version (run apt policy $PACKAGE NAME): N/A

Issue/Bug Description: When booting from a USB drive (created with Etcher, ventoy & dd directly) the installation starts normally, the GUI appears, I can choose language (chose English & American English) and then the install goes back to text mode and 5 tasks are running, casper-md5check among others (I also remembered the CUPS daemon) which never terminate (waited for half an hour).

Steps to reproduce (if you know): Boot from the created USB drive.

Expected behavior: Installation continues normally.

Other Notes: This is on a desktop PC (Ryzen 5600X, B550 motherboard, Nvidia 3070 graphics card).

bflanagin commented 3 years ago

Thanks for the report @Cantello. Was this the nvidia iso or the intel iso?

Cantello commented 3 years ago

Thanks for the report @Cantello. Was this the nvidia iso or the intel iso?

Sorry for the omission, it was the nvidia ISO.

Cantello commented 3 years ago

Upgrading from 20.10 works, btw. No hassles or errors at all.

bflanagin commented 3 years ago

I'm not seeing this issue on my end (used ventoy and popsicle) . I'd suggest downloading the image again and seeing if a fresh download fixes the issue.

ebbit1q commented 3 years ago

I'm having the same issue, after a few seconds of showing the install screen it shuts down gnome again. gtx 1080 + ryzen 1700X, I'm using efi and have disabled secure boot, I prepared the usb stick with popsicle. here is the syslog from the writable section of the usb: https://gist.github.com/ebbit1q/576066f04a627a4051a3c4a2878c7e21 the line at :3241 and its surroundings seem related to the issue: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

AndreasSturm commented 3 years ago

Had the same issue, unplugging the network cable until the OS has fully loaded solved the problem, after OS has fully loaded I plugged the network cable in and I was able to install 21.04 withou any issues.

ebbit1q commented 3 years ago

I found something related to network in the log but thought it was a red herring

I've installed 21.04 as well now:

ebbit1q commented 3 years ago

this line specifically in the log seemed related to network issues https://gist.github.com/ebbit1q/576066f04a627a4051a3c4a2878c7e21#file-syslog-L1917 nm-dispatcher[1705]: /etc/network/if-up.d/resolved: 12: mystatedir: not found, I'll test later if I can boot from the usb stick without network.

jacobgkau commented 3 years ago

We were able to recreate this on an oryp4 last week, instructions to recreate are here: https://github.com/pop-os/iso/issues/279#issue-930443436

bflanagin commented 3 years ago

I've been able to reproduce the issue on most of our machines in the lab. (galp5, lemp9[using usb ethernet adapter], Thelio-r1, gazelle15)

The issue only occurs when using a usb flash drive in conjunction with having the ethernet cable plugged in. Not all flash drives or usb storage devices cause the issue.

These logs are from one of the machines that is failing.

dmesg.txt journalctl.txt

oldaccountdeadname commented 3 years ago

I observed this on my machine (Ryzen 3900X, RTX 2060) with the 21.04 release Nvidia ISO as well - unplugging ethernet made everything work, and the issue was only in the live environment, not in the installed system.

As it seems to be dependent on the USB drive, lsusb reports that mine is a 058f:6387 Alcor Micro Corp. Flash Drive

Hopefully this information is useful, thanks!

leviport commented 3 years ago

The latest published versions of the 21.04 isos include a fix for this issue.

jerlich commented 3 years ago

i had the same issue (and unplugging ethernet worked for me) with an ISO downloaded on Aug 17 pop-os_21.04_amd64_nvidia_7.iso