computer will not boot after upgrade to fedora29

asked 2019-04-09 21:36:08 -0600

The computer is a 64-bit acer that has been single booting fedora-xfce since fedora20. I've never had a problem upgrading before, but this time it won't complete booting up. The last thing shown is: "Started Network Manager Script Dispatcher Service". Same problem if I choose the fedora28 kernel. It does boot under the rescue kernel. uname -r gives 3.11.10-301.fc20.x86_64

I see from "journalctl -xb" that there is an error: "Cannot initialize the agpgart module". But I don't think that is the real problem. What seems critical is that vfat is not recognized and /boot/efi cannot be mounted.

I wanted to put the complete output on a flash drive, move to this computer and then include here but when I insert into the usb I get: "...device not accepting address 6, error -71". There is no directory /lib/modules/3.11.10-301.fc20.x86_64.

Also, reading on the web about similar problems, I see suggestions to dnf install this or that. I tried to get on the web, but "ifconfig wlan0 up" gives "wlan0: ERROR while getting interface flags: No such device".

I don't know what to try next.

edit retag flag offensive close merge delete

Comments

can you try to boot into single mode to see if the issue has to do with a device on you pc. Some time ago I had a sony machine that used to have switch for the wifi when it was not on my Fedora hangs o boot, check if your bios has disable de card o if there is some how a way to switch it on and off.

aeperezt ( 2019-04-10 10:30:43 -0600 )edit

I'd suggest to try using ethernet cable -- if you can, of course -- so you won't have to mess with wireless in cli.

Also to see the actual interface names use ip a command (your wireless card can now be something like wlp3s0).

You also can try to use nmcli -- command line interface to Network Manager to connect to your WiFi, here's some examples.

Night Romantic ( 2019-04-11 03:20:23 -0600 )edit

As far as I know, you won't be able to connect to WiFi just using ifconfig. Old way to do it was using wpa_supplicant, newer one is using Network Manager (even in cli), which uses wpa_supplicant on the backend (or used in the past). I don't know if new way is easier, never done it in cli myself.

Night Romantic ( 2019-04-11 03:22:42 -0600 )edit

@pueblofish, when it doesn't finish booting up, can you by any chance switch to text console with Ctrl-Alt-F3 (F4, F5)??

Night Romantic ( 2019-04-11 03:25:53 -0600 )edit

Here's one more example on using nmcli to connect to WiFi. This one seems quite simple and straightforward.

Still ethernet cable would be better, even temporary while you troubleshoot/recover.

Night Romantic ( 2019-04-11 03:28:36 -0600 )edit

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2019-04-12 23:29:31 -0600

pueblofish
21 ●4

updated 2019-04-19 22:19:51 -0600

Turns out my problem was with nomodeset.

After boot stalls: Ctrl-Alt-F3 to get a command prompt (thank you Night Romantic)

edit grub file with nano:

[ray@localhost ~]$ sudo nano /etc/default/grub

delete "nomodeset" save with Ctrl-X, y and Enter

run the following or the change will not be registered

[ray@localhost ~]$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

[ray@localhost ~]$ reboot

worked fine

My laptop graphics is as follows:

[ray@localhost ~]$ lspci | grep -iE 'vga|video'

00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)

edit flag offensive delete link

Comments

When your computer (almost) successfully boots to black screen -- and you can switch to text console, login, etc, the problem is quite often is with graphics (with driver modules, in your case with nomodeset).

Glad you were able to resolve it.

What graphics do your notebook use? Is it NVidia's by any chance? It would be useful to add this info to original question for anyone who may have similar problems. Nomodeset needs to be removed only for specific gpus, it's not a good general solution)

Night Romantic ( 2019-04-15 05:19:04 -0600 )edit

I hope this tells you what my graphics card is:

[ray@localhost ~]$ lspci | grep Graphic 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)

pueblofish ( 2019-04-17 02:28:22 -0600 )edit

That's Intel built-in one.

But there's a thing: not all chipsets report itself with the word "Graphic", my Nvidia's card is listed as: "VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)". So it's possible for other gpus to be in your computer. I don't know how to check which one is actually used.

Try lspci | grep -iE 'vga|video'. If it doesn't show anything new, then this Intel gpu should be it.

Night Romantic ( 2019-04-17 08:12:00 -0600 )edit

I got the same result:

[ray@localhost ~]$ lspci | grep -iE 'vga|video'

00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)

Thanks for your help. I would like to email you a round calendar--that is what pueblofish is all about.

pueblofish ( 2019-04-18 22:26:05 -0600 )edit

@pueblofish, I suggest to add output of lspci to you answer (you can edit it), so that any person who'll find your question/answer in the future can easily see to which gpu it applies (without reading through all the comments).

I'm glad to help, though you did all the work/research yourself)

Night Romantic ( 2019-04-19 02:28:32 -0600 )edit

add a comment

answered 2019-04-12 21:59:35 -0600

pueblofish
21 ●4

Response to aeperezt: I looked through my bios and found nothing about de card

Response to Night Romantic: Ctrl-Alt-F3 got me to a command prompt and from there the nmcli worked to get me on the internet. I still don't know where to go from there, but I downloaded the fedora29 live image and was able to use that to get the outputs of the various logs.

[root@localhost ~]# journalctl -xb -- Logs begin at Sat 2015-01-03 01:38:00 MST, end at Thu 2019-04-11 21:07:58 MST. -- Apr 11 14:07:34 localhost systemd-journal[60]: Runtime journal is using 8.0M (max 191.9M, leaving 287.8M of free 1.8G, current limit 191.9M). -- Subject: Disk space used by the journal -- Defined-By: systemd

-- Support: https://lists.freedesktop.org/mailman...

-- JOURNAL_NAME (JOURNAL_PATH) is currently using CURRENT_USE_PRETTY. -- Maximum allowed usage is set to MAX_USE_PRETTY. -- Leaving at least DISK_KEEP_FREE_PRETTY free (of currently available DISK_AVAILABLE_PRETTY of disk space).

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

-- Support: https://lists.freedesktop.org/mailman...

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

-- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Apr 11 14:07:34 localhost kernel: Initializing cgroup subsys cpuset Apr 11 14:07:34 localhost kernel: Initializing cgroup subsys cpu Apr 11 14:07:34 localhost kernel: Initializing cgroup subsys cpuacct Apr 11 14:07:34 localhost kernel: Linux version 3.11.10-301.fc20.x86_64 (mockbuild@bkernel01.phx2.fedoraprojec...) (gcc version 4.8.2 20131017 (Red Hat 4.8.2-1) (GCC) ) #1 SMP Thu Dec 5 14:01:17 UTC 2013 Apr 11 14:07:34 localhost kernel: Command line: BOOT_IMAGE=/vmlinuz-0-rescue-5cf38270a33d454e9c72757a5c473f11 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap nomodeset rd.lvm.lv=fedora/root vconsole.font=latarcyrheb-sun16 rhgb quiet Apr 11 14:07:34 localhost kernel: e820: BIOS-provided physical RAM map: Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x0000000000070000-0x000000000009dfff] usable Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable Apr 11 14:07:34 localhost kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff ... (more)

edit flag offensive delete link

add a comment

computer will not boot after upgrade to fedora29

Comments

2 Answers

Comments

-- Support: https://lists.freedesktop.org/mailman...

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

-- Support: https://lists.freedesktop.org/mailman...

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

Question Tools

Stats

Related questions

computer will not boot after upgrade to fedora29 edit

Comments

2 Answers

Comments

-- Support: https://lists.freedesktop.org/mailman...

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

-- Support: https://lists.freedesktop.org/mailman...

-- Enforced usage limit is thus LIMIT_PRETTY, of which AVAILABLE_PRETTY are still available.

Question Tools

Stats

Related questions

computer will not boot after upgrade to fedora29