Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display is broken on OLIMEX Teres-I #6630

Open
1 of 2 tasks
Kreyren opened this issue May 18, 2024 · 5 comments
Open
1 of 2 tasks

Display is broken on OLIMEX Teres-I #6630

Kreyren opened this issue May 18, 2024 · 5 comments

Comments

@Kreyren
Copy link
Contributor

Kreyren commented May 18, 2024

What happened?

On kernels past 6.1 there have been few reworks of the relevant components that cause the display to not get initialized correctly

I fixed that by adding:

usbhid
sun4i-drm
sun4i-tcon
sun8i-mixer
sun8i_tcon_top
drm
drm_shmem_helper
drm_kms_helper
drm_dma_helper
drm_display_helper
analogix_anx6345
analogix_dp

to /etc/initramfs-tools/modules and then ran update-initramfs -u

Self-Assigning.. Currently very busy will fix it when i find a time frame for it.

How to reproduce?

Run the pre-built image on the device

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Debian 13 Trixie

Are you building on Windows WSL2?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

Jira ticket: AR-2318

@igorpecovnik
Copy link
Member

Its not a problem if you are busy, but non working display is pretty critical problem for laptop ... as there is no time, I can only disable "supported" tag on download until this is not resolved as providing known broken images for supported hardware is bad for reputation.

@Kreyren
Copy link
Contributor Author

Kreyren commented May 23, 2024

Its not a problem if you are busy, but non working display is pretty critical problem for laptop ... as there is no time, I can only disable "supported" tag on download until this is not resolved as providing known broken images for supported hardware is bad for reputation. -- @igorpecovnik (#6630 (comment))

Teres users are different userbase from the generic consumer base and generally know how to manage this problem + are in talks with me on them (all known problems explained in detail on https://linux-sunxi.org/Olimex_Teres-A64#Known_issues),

So keep the supported tag and instead i will add notes about these issues to the armbian page with links until i track down the cause of this issue in armbian (not known to happen on other distros, the display was broken in non-lts kernels until 6.8 so i assume that someone's applying obsolete patches to the armbian kernel atm)

@igorpecovnik
Copy link
Member

So keep the supported tag

Its better that its community supported until problems are not resolved as those images are auto-created once per week, one desktop, one CLI image. If someone else fixes this upstream it will just start working ... Once you confirm they work, status is changed back and new stable kernel is pushed to repo + stable images are recreated. This is exception that can be made.

i will add notes about these issue

You are free to add comments what users need to do to get going, but it might be less work just fixing it. I understand you are busy, everyone is, this is not a critical problem => when you find time.

i assume that someone's applying obsolete patches to the armbian kernel atm

Nobody is deliberately doing anything. I don't know what is the status, nobody knows "at Armbian", which is the reason why we have maintainers. They know. You know. I only know for few boards that I am dealing with and things we have on automated testings.

@Kreyren
Copy link
Contributor Author

Kreyren commented May 23, 2024

Nobody is deliberately doing anything. I don't know what is the status, nobody knows "at Armbian", which is the reason why we have maintainers. They know. You know. I only know for few boards that I am dealing with and things we have on automated testings. -- @igorpecovnik (#6630 (comment))

I am not saying that someone's doing that deliberately rather that there were a lot of relevant changes in the kernel that required downstream patches for other boards that might be interfiering with the device at the current very rushed hypothesis of mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants