Getting kernel log spam that makes the tty unusable

[badly-drawn-wizards]

[   73.680019] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

is spammed on the tty on boot, making it impossible to see what I am doing.

I am using a Orange Pi 5 Plus with UEFI. I followed the instructions in the UEFI.md.

I can temporarily block it with sudo dmesg -n 1, but I want to find out what's going on.

[n0rad]

Same here using UEFI with an orangepi5plus, even when using the pre-built image in releases 🤔

[cessationoftime]

I had this same problem on orange5piplus and UEFI. I used sudo dmesg -n 1 to eliminate the spam. Then I built the image locally and applied the new image to my nvme SSD and resized the root partition with parted to take up the rest of the SSD and put the device tree in /boot/dtb/base. I believe building it locally on the orangepi5plus solved the problem. So I think the problem results from using emulation for the image build.

[gnull]

I built mine on OPI5 Plus itself and I still get the errors.

[tpwrules]

Does HDMI work for you? Are you using GRUB or systemd-boot?

[n0rad]

On my side HDMI is working, even with DVI that used to not be working in the past. and I'm on systemd-boot.

I saw the comment in the other issue but it does not match what I see.
Also I'm not using the flake of this repository directly anymore but a copy instead, and I remember that not applying the kernel params here makes the kernel displaying nothing.

[Baddad23]

Sorry I'm noob and I'm also have the problem list in post 1:

"I can temporarily block it with sudo dmesg -n 1, but I want to find out what's going on."

Can some one please explain how to run this command or from where? I'm using orangepi5plus-rawEfi.img which goes straight to install and then I get a stream of [ 73.680019] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

[gnull]

When you boot from UART (or HDMI + keyboard, but I haven't tested this), you get a lot of this spam. But the login screen is still there. If you hit enter, it prints one line of login prompt (which will be drowned in spam, you can see it if you scroll up through spam — scrolling works only with UART). What you can do is blindly type root username, hit enter, then password and enter to login. Everything like usual login, but you won't see feedback. Once you do that, you'll get root bash prompt (which you will see briefly before it drowns in spam). There, you can type dmesg -n 1, hit enter (still blindly due to spam), and spam stops. Ivan

…

On Fri, Dec 6, 2024, 15:45 Baddad23 ***@***.***> wrote: Sorry I'm noob and I'm also have the problem list in post 1: "I can temporarily block it with sudo dmesg -n 1, but I want to find out what's going on." Can some one please explain how to run this command or from where? I'm using orangepi5plus-rawEfi.img which goes straight to install and then I get a stream of [ 73.680019] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWF5J3JE24OQQWX5XEHQK32EGZ7XAVCNFSM6AAAAABKNHKMMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTGQYDONZWGY> . You are receiving this because you commented.Message ID: ***@***.***>

[gnull]

Could we disable the hdmirx node in the dts for now to prevent the spam? I'm guessing from the name that it's from the hdmi plug that's for receiving image (i.e. opi5 playing the role of monitor), and it may be reasonable to mark it as unsupported (has someone tested it?) for now until we figure out what's the reason for the spam. On Fri, Dec 6, 2024, 16:00 Ivan Oleynikov ***@***.***> wrote:

…

When you boot from UART (or HDMI + keyboard, but I haven't tested this), you get a lot of this spam. But the login screen is still there. If you hit enter, it prints one line of login prompt (which will be drowned in spam, you can see it if you scroll up through spam — scrolling works only with UART). What you can do is blindly type root username, hit enter, then password and enter to login. Everything like usual login, but you won't see feedback. Once you do that, you'll get root bash prompt (which you will see briefly before it drowns in spam). There, you can type dmesg -n 1, hit enter (still blindly due to spam), and spam stops. Ivan On Fri, Dec 6, 2024, 15:45 Baddad23 ***@***.***> wrote: > Sorry I'm noob and I'm also have the problem list in post 1: > > "I can temporarily block it with sudo dmesg -n 1, but I want to find out > what's going on." > > Can some one please explain how to run this command or from where? I'm > using orangepi5plus-rawEfi.img which goes straight to install and then I > get a stream of [ 73.680019] rk_hdmirx fdee0000.hdmirx-controller: > hdmirx_phy_register_write wait cr write done failed! > > — > Reply to this email directly, view it on GitHub > <#37 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABWF5J3JE24OQQWX5XEHQK32EGZ7XAVCNFSM6AAAAABKNHKMMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTGQYDONZWGY> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[gnull]

hbiyik/linux@1a91051

Joshua-Riek/linux@1a91051

This commit seems to be disabling hdmirx upstream (defined here) due to the same issue as here. But oddly, the hdmirx node is still enabled in the dtb on my device:

$ cat /sys/firmware/devicetree/base/hdmirx-controller@fdee0000/status
okay

I may be misunderstanding the Nix build scripts here, but I can't guess why it's still enabled. I think if we manage to properly disable that, the spam may go away.

[Baddad23]

@gnull thanks for replying. Well, I tried entering "nixos" as root username and just hit enter for password because I read somewhere it was blank. But the truth is I don't even see any green test Ithink that would be the login screen) flying by. What is the root username/password?

I thinks with just hdmi monitor it might be easier to disable hdmirx. Do you know how. At this point I'm willing to try anything as I don't have a working system

[gnull]

gnull@6ef36e6

@Baddad23 Try this revision. It's a quick workaround I found: this commit disables the driver that creates the spam (it also incorporates the current version of #64). I'm currently looking for cleaner ways to fix the issue, will make a PR in time.

About password: the user and password are given here. I wrong about logging in as root, you need to use rk user, and then do dmesg command via sudo. Don't forget to type the password after sudo. And also before you try to log in, give it enough time to make sure the system reaches login prompt as the spam starts falling before login prompt.

[gnull]

@Baddad23 #66 is the PR to try, should get rid of the log spam.

[Baddad23]

@gnull Well, managed to get thru all the spam and get to cmd line. Trying to format nvme target ssd but "parted" used to create and format cannot be found. Is there another utility now being used?

[gnull]

Can't say from the top of my head. When I did it, steps from official NixOS install instructions and the docs in this repo worked (albeit after a few attempts).

…

On Sat, Dec 7, 2024, 14:51 Baddad23 ***@***.***> wrote: @gnull <https://github.com/gnull> Well, managed to get thru all the spam and get to cmd line. Trying to format nvme target ssd but "parted" used to create and format cannot be found. Is there another utility now being used? — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWF5J7EGXZN52BWYGA5X7D2EL4M3AVCNFSM6AAAAABKNHKMMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRVGE2DEMZSGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Baddad23]

After working on this for sever hours again this morning it certainly seems that no one has tried to do an nixos install on an opi5+ following these instructions in quite a while. The manual installation https://nixos.org/manual/nixos/stable/#sec-installation-manual has a number of problems and I've spent hours trying to find work arounds, eg "parted" but there are MORE.

Someone with far more experience than me would need to go thru this, not using their experience, but just following the instructions and then marking it up for corrections!

Instructions are needed that are simple to follow and WORK.

[gnull]

It may be a good idea to create a new issue with specific problems you had or improvement suggestions.

…

On Sat, Dec 7, 2024, 17:43 Baddad23 ***@***.***> wrote: After working on this for sever hours again this morning it certainly seems that no one has tried to do an nixos install on an opi5+ following these instructions in quite a while. The manual installation https://nixos.org/manual/nixos/stable/#sec-installation-manual has a number of problems and I've spent hours trying to find work arounds, eg "parted" but there are MORE. Someone with far more experience than me would need to go thru this, not using their experience, but just following the instructions and then marking it up for corrections! Instructions are needed that are simple to follow and WORK. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWF5J25LPOTAFFKC7H6TH32EMQSFAVCNFSM6AAAAABKNHKMMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRVGI2DANRVHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Baddad23]

I did want to thank you for all your help!