Ask Your Question

Laptop with Fedora 27 gets stuck at boot (Just after the "balloon" is filled and the "f" appears) but only if the charger is not plugged in.

asked 2017-11-16 11:59:43 -0500

tomtava gravatar image

updated 2017-11-17 13:07:05 -0500

florian gravatar image

Hello! I just installed Fedora 27 workstation and it's great, except it doesn't boot. As the title says, it gets stuck when the "balloon" is filled and turns into a "f" (right before the gdm login screen). No matter how long I leave it, nothing happens.

If I press escape during the boot up, the last thing the terminal outputs is

Started User Manager for UID 42

and then nothing happens. The blinking cursor even stops and nothing responds at all, so I have to hold down the power button.

The curious thing is that it works if I have the charger plugged in. Then it boots, lets me login through gdm and continues to the Gnome3 desktop. I noticed this by accident and to ensure that it really worked I tried rebooting 10 times and it succeeded every time. I then tried twice to shut it completely off, let it be turned off for 5 min. and turn it on again 2 times (while plugged in) and that worked as well.

I then tried without the charger 5 times, and again it got stuck at the "f" every time.

I'm so confused, I didn't think something like this could make a difference. And it wouldn't really matter if it weren't a laptop.

Some additional information

  • I have just updated the system today (the 16. November 2017)
  • I'm using the 4.13.12-300.fc27.x86_64 kernel.
  • The computer uses a AMD® A6-4455m apu with radeon(tm) hd graphics × 2 (AMD® Aruba [Trinity [Radeon HD 7500G]]) with the preinstalled drivers.

Any help would be much appreciated and I can paste any logs or whatever, I just don't really know where to look!

Thanks a bunch

(I also made a reddit thread )

Edit: I also wanted to say I have seen other posts where people had the same problem (I guess?), but some of the posts have died without being solved, and someone had a problem where Nvidia drivers/bumblebee helped, but that obviously isn't the problem for me. Somebody also said it was a problem with SELinux and it should be disabled, but I heard you shouldn't do that.


Okay so I went ahead and added selinux=0 in grub after the "quiet" bit and it actually worked, the first time at least.

I tried again with the same setting in grub, and it failed.

I then tried without changing anything in grub and during boot selinux had to relabel the filesystem? I'm not quite sure what it did, but it looked like this:

(sorry for the dustry screen lol) and then it worked again.

Tried again without changing grub, and it failed.

Tried with selinux=0 and it restarted this process. (First time with selinux=0 worked, second time failed. First time without succeded after relabelling, second ... (more)

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2018-03-15 15:32:59 -0500

kbrwn gravatar image

boot into single user mode ( after quiet in the grub config) and then check for anything bad in the boot log journalctl -xb

i had bad /etc/udev/rules.d/ causing this issue.

edit flag offensive delete link more

Question Tools



Asked: 2017-11-16 11:59:43 -0500

Seen: 4,093 times

Last updated: Nov 17 '17