System hanging at boot, blinking cursor

Looking at past threads, this (inxi -Fxxxc0z) was requested:

My system was fully up to date, and I had restarted just before doing only these two commands:

sudo groupadd plugdev
sudo usermod -aG plugdev $USER

After these commands, my system now boots to a blinking cursor.

The purpose of these commands was in-order to allow my system to update the key layout on my keyboard. This was my first time doing this in Linux. I had created a file like this:

sudo touch /etc/udev/rules.d/50-zsa.rules

And put the following lines in the file:

# Rules for Oryx web flashing and live training
KERNEL=="hidraw*", ATTRS{idVendor}=="16c0", MODE="0664", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="3297", MODE="0664", GROUP="plugdev"

It’s probably worth mentioning that this hanging up (unrelated to keyboard, I think) has happened before, but a restart or two and things would boot normally. This probably happened on a off for a week, and then it stopped happening and I had never diagnosed the problem.

I would love some help on getting this sorted. Preferably I’d like to be able to update my keyboard layout, but if I can’t then some instruction in undoing what I’ve done would also be great.

One more piece of information, I am able to boot up with the fallback intramfs option, which I am using now to make this post.

Thanks so much for any and all help! I love this place!

EDIT: I’ve done some experimenting. I’ve commented out the lines the ‘/etc/udev/rules.d/50-zsa.rules’ file. I was able to successfully boot normally after that. I uncommented the lines and then was unable to boot normally. After trying a handful of times with both the lines commented and uncommented, it seems that both normally booting and fallback intramfs booting can both hang and there doesn’t seem to be a correlation with either mode and whether or not those lines are commented out. It may be possible that the keyboard has nothing to do with this and it’s the initial problem I mentioned that went away for a bit…I guess it’s back now?

EDIT 2: Did some more experimenting. It almost never boots normally, regardless of if those lines are commented. When I attempt to boot inframfs fallback, it rarely works the first attempt, but usually works the second attempt. No ideas.

EDIT 3: Changed loglevel in grub to get more information. Every time boot fails, the last message presented is:

amdgpu: SRAT table not found

More investigation to be done.

EDIT 4: from:

journalctl -b | grep amd

after a successful boot. Not sure if it is useful.

I am able to boot successfully and consistently after moving over to LTS release. I’d like to have rolling release and figure out this issue still though.

you could wait for a few releases and try again.

1 Like

I have the same problem

1 Like

I was going to say just boot the fallback. If the fallback is not stable successful, I would suggest it is a HW problem.
The last log line has only investigative value. OTOH is amdgpu early loaded? (i.e. in MODULES array in mkinitcpio.conf).

What made you think you need that udev rule and the commands? Any links?

1 Like

ZSA keyboards create keyboard firmware (if I want to change key bindings, for example) in the cloud and flash it to the keyboard through the browser. I think the issue may be unrelated to the keyboard.

It seems like this issue is related to this here:

There is a slight bit of embarrassment for me not seeing that thread earlier.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.