LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64
Reload this Page Quartz64 RK3566 (aarch64)
User Name
Password
slarm64 This forum is for the discussion of slarm64.

Notices


Reply
Page 2 of 3 1 2 3
  Search this Thread
Old 05-16-2022, 12:25 AM   #16
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,915

Original Poster
Rep: Reputation: Disabled

installation README.TXT

kernel 5.17.7

slarm64-current-aarch64-server-quartz64-5.17.7-build-20220515.img.zst
slarm64-current-aarch64-server-quartz64-5.17.7-build-20220515.img.zst.sha256
slarm64-current-aarch64-xfce-quartz64-5.17.7-build-20220515.img.zst
slarm64-current-aarch64-xfce-quartz64-5.17.7-build-20220515.img.zst.sha256
 
1 members found this post helpful.
Old 07-16-2022, 08:19 PM   #20
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
latest xorg updates kinda break display on both legacy and next
This one has me scratching my head. I run a Quartz64-A legacy image daily. When I installed the latest batch of xorg updates (on 15.0, not current), my default screen resolution dropped from 1920x1080 down to 1200x1080. I know it was the xorg updates because everything was working like normal before those, and I updated nothing else.

I checked a freshly-built quartz64-a next image, and it boots up just fine. However, if you run the updates and let the xorg updates install, then on reboot, X does not start at all, regardless of the resolution.

I am going to try some older images to isolate if any specific kernels, u-boot versions, or ATF blobs change anything. I just wanted to give you a heads up on this one because you can probably check it yourself (just update any xfce image for the quartz-a and see if X behaves any differently afterwards).

I checked other machines, and the Pinebook seems to be affected also. X starts but then is completely blank, no output at all. None of my x86 machines are acting like this, so it seems slarm64 or aarch64 specific maybe? I can also test my Rock64.

Or maybe this is just me? I only have one monitor to test, sadly. If anyone notices anything similar with the xorg updates on any quartz64 images, I would love to hear about it. Thanks.
Last edited by shelldweller; 07-16-2022 at 10:36 PM. Reason: updated info for Pinebook and 15.0 branch
 
Old 07-17-2022, 02:10 AM   #21
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,915

Original Poster
Rep: Reputation: Disabled
let's see dmesg and Xorg.0.log
 
1 members found this post helpful.
Old 07-17-2022, 07:42 AM   #23
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,915

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by shelldweller View Post
This one has me scratching my head. I run a Quartz64-A legacy image daily. When I installed the latest batch of xorg updates (on 15.0, not current), my default screen resolution dropped from 1920x1080 down to 1200x1080. I know it was the xorg updates because everything was working like normal before those, and I updated nothing else.

I checked a freshly-built quartz64-a next image, and it boots up just fine. However, if you run the updates and let the xorg updates install, then on reboot, X does not start at all, regardless of the resolution.

I am going to try some older images to isolate if any specific kernels, u-boot versions, or ATF blobs change anything. I just wanted to give you a heads up on this one because you can probably check it yourself (just update any xfce image for the quartz-a and see if X behaves any differently afterwards).

I checked other machines, and the Pinebook seems to be affected also. X starts but then is completely blank, no output at all. None of my x86 machines are acting like this, so it seems slarm64 or aarch64 specific maybe? I can also test my Rock64.

Or maybe this is just me? I only have one monitor to test, sadly. If anyone notices anything similar with the xorg updates on any quartz64 images, I would love to hear about it. Thanks.
i built a new image kernel-5.19.0-rc6 with the latest xorg:
Code:
xorg-server-1.20.14-aarch64-4
xorg-server-xephyr-1.20.14-aarch64-4
xorg-server-xnest-1.20.14-aarch64-4
xorg-server-xvfb-1.20.14-aarch64-4
xorg works:
Attached Files
File Type: log Xorg.0.log (32.8 KB, 5 views)
File Type: txt dmesg.txt (30.6 KB, 5 views)
Last edited by sndwvs; 07-17-2022 at 07:48 AM.
 
1 members found this post helpful.
Old 07-18-2022, 09:09 PM   #24
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
i built a new image kernel-5.19.0-rc6 with the latest xorg:
Code:
xorg-server-1.20.14-aarch64-4
xorg-server-xephyr-1.20.14-aarch64-4
xorg-server-xnest-1.20.14-aarch64-4
xorg-server-xvfb-1.20.14-aarch64-4
xorg works:

I have been able to isolate this to the stable 15.0 branch. The problem is present on Rock64, Pinebook, and Quartz64 (legacy and next), only as long as I am on the stable branch. Checking the current branch, I see the problem is not there. So this has something to do with the stable xorg updates.

I will try to generate some logs. I can say for sure on the Pinebook the error message is "no display found". Stay tuned for more info. I was busy testing my other boards to try to isolate the issue.
 
Old 07-19-2022, 09:10 AM   #25
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
let's see dmesg and Xorg.0.log
I know I should always generate logs before I even report here. In any case, here are the relevant logs for a recent Quartz64-A next image on the 15.0 stable branch:

https://slarmboards.3space.xyz/quartz64/logs/

Xorg.0.log, dmesg, and also Xorg.1.log are there as text files, renamed for the board and kernel branch.

I will generate more logs as I have time.
 
Old 07-19-2022, 10:05 AM   #26
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,915

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by shelldweller View Post
I know I should always generate logs before I even report here. In any case, here are the relevant logs for a recent Quartz64-A next image on the 15.0 stable branch:

https://slarmboards.3space.xyz/quartz64/logs/

Xorg.0.log, dmesg, and also Xorg.1.log are there as text files, renamed for the board and kernel branch.

I will generate more logs as I have time.
Thanks for the logs.

it is not immediately clear why lib instead of lib64 (clearly, in 15.0 it is)
error in this: modesetting_drv.so: undefined symbol: shadowRemove
Code:
[   656.768] (II) LoadModule: "modesetting"
[   656.769] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   656.769] (EE) Failed to load /usr/lib/xorg/modules/drivers/modesetting_drv.so: /usr/lib/xorg/modules/drivers/modesetting_drv.so: undefined symbol: shadowRemove
[   656.769] (EE) Failed to load module "modesetting" (loader failed, 0)
[   656.769] (II) LoadModule: "fbdev"
Last edited by sndwvs; 07-19-2022 at 10:08 AM.
 
1 members found this post helpful.
Old 07-19-2022, 11:23 AM   #27
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Thanks for the logs.

it is not immediately clear why lib instead of lib64 (clearly, in 15.0 it is)
error in this: modesetting_drv.so: undefined symbol: shadowRemove
Code:
[   656.768] (II) LoadModule: "modesetting"
[   656.769] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   656.769] (EE) Failed to load /usr/lib/xorg/modules/drivers/modesetting_drv.so: /usr/lib/xorg/modules/drivers/modesetting_drv.so: undefined symbol: shadowRemove
[   656.769] (EE) Failed to load module "modesetting" (loader failed, 0)
[   656.769] (II) LoadModule: "fbdev"
Good catch. Yeah I saw that too, but I was not sure what to make of it. Looking around the 'net, I found this thread:

https://forums.gentoo.org/viewtopic-...8-start-0.html

They mention the same problem and a fix. I tried the fix on a Rock64 that was behaving exactly the same as the Quartz64. I added a Modules section to /etc/X11/xorg.conf.d/10-monitor.conf. I put in the same modules that were used in the other thread. Upon booting, X seems to start fine now, but I have no keyboard or mouse at all. Maybe I have to add these too? Or maybe I added the wrong modules. In any case, X starts now, which is interesting. I think if I can just figure out the right modules and the right order, this might correct the problem.

Thanks for the lead, that helped.
 
Old 07-19-2022, 12:02 PM   #28
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,359

Rep: Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333Reputation: 2333
For some mad reason I was compiling Mesa (version 18 or 19?) when it went over to some crazy build system. My first reaction was that some friend of the devs must have cobbled it up, and bought the drinks.

Alien Bob promptly did a build script for it, which tied every single detail and didn't allow it to do any thinking at all. If you guys building the OS asked him nicely, I'm sure you'd get a copy. I did, many years ago.
Last edited by business_kid; 07-19-2022 at 12:04 PM.
 
Old 07-19-2022, 12:20 PM   #29
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,915

Original Poster
Rep: Reputation: Disabled
the solution is simple, when building in patches, all flags were applied, and deleting flags CFLAGS -fno-plt, CXXFLAGS -fno-plt, LDFLAGS -z,now solves this problem.
packages updated.
 
1 members found this post helpful.
Old 07-19-2022, 06:00 PM   #30
shelldweller
Member
 
Registered: Mar 2019
Distribution: Slackware
Posts: 300

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
the solution is simple, when building in patches, all flags were applied, and deleting flags CFLAGS -fno-plt, CXXFLAGS -fno-plt, LDFLAGS -z,now solves this problem.
packages updated.
Yes, that did the trick, problem solved here. Thank you!
 
  


Reply
Page 2 of 3 1 2 3

Tags
pine64 team, rk3566, rockchip, slackware, slarm64



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Quartz64-A with legacy kernel 4.19.y - Wireguard? shelldweller slarm64 3 01-17-2022 08:10 PM
[SOLVED] Station M2(RK3566)/P2(RK3568) (slarm64, aarch64) sndwvs Slackware - ARM 4 12-07-2021 09:31 AM
[SOLVED] Quartz64 RK3566 (slarm64, aarch64) sndwvs Slackware - ARM 21 12-07-2021 09:11 AM
LXer: Quartz64 SBC starts at $60 and Pine64 unveils SOQuartz module with same RK3566 LXer Syndicated Linux News 0 06-17-2021 05:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64

All times are GMT -5. The time now is 12:03 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration