hunderteins - you don't see the file in my repo because I removed the patch due to it not working  Altho in testing it appears the trailing backslash may have actually resolved this, which is exciting  Thanks for the help!
p1x3l3d - for docker specifically I have added aufs into the kernel. Overlay2 has some issues in the 4.4 kernel, but it sounds like aufs will work well.
I don't need anything else if Spotify is working. I am therefore forced to use the Android.
I can't install Spotify. I will be very happy if you help me to do this and I will pray a lot to you
PinePhone (BH 2GB + CE 3GB) // RockPro64 4GB (rev. 2.1) - OMV NAS // PineH64 3GB (model B) - off-prem OMV NAS // Pine64-LTS 2GB (rev. 1.2 + Playbox) - Domotics server
Hi,
I really appreciate the enormous work which was put into this distribution and the philosophy 'make this nice computer work'.
Unfortunately, when installing the distribution on my RockPro64, I get to the login page, but when logging in the system freezes and it seems that the difference to the previous distributions I have tried are not all that big? I have a configuration with a SATA disk. Here is my kern.log with '|grep failed'. This is _before_ I try to log in. I have so far not found a good log providing a clue about the desktop login problems. Login with ssh (before desktop login) is not a problem (and has never been).
Any Idea what is wrong here?
Mar 23 06:27:13 localhost kernel: [ 0.582850] sdhci-arasan fe330000.sdhci: lookup for GPIO wp failed
Mar 23 06:27:13 localhost kernel: [ 0.583989] sdhci-arasan fe330000.sdhci: Looking up vmmc-supply property in node /sdhci@fe330000 failed
Mar 23 06:27:13 localhost kernel: [ 0.584031] sdhci-arasan fe330000.sdhci: Looking up vqmmc-supply property in node /sdhci@fe330000 failed
Mar 23 06:27:13 localhost kernel: [ 0.621483] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
Mar 23 06:27:13 localhost kernel: [ 0.621769] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
Mar 23 06:27:13 localhost kernel: [ 0.623402] phy phy-ff7c0000.phy.7: Looking up phy-supply property in node /phy@ff7c0000/dp-port failed
Mar 23 06:27:13 localhost kernel: [ 0.623531] phy phy-ff7c0000.phy.8: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
Mar 23 06:27:13 localhost kernel: [ 0.627588] rockchip-drm display-subsystem: failed to parse loader memory
Mar 23 06:27:13 localhost kernel: [ 0.627637] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Mar 23 06:27:13 localhost kernel: [ 1.687315] rockchip-spdif ff870000.spdif: ASoC: pcm constructor failed: -22
Mar 23 06:27:13 localhost kernel: [ 1.687328] asoc-simple-card spdif-sound: ASoC: failed to instantiate card -22
Mar 23 06:27:13 localhost kernel: [ 1.687480] asoc-simple-card: probe of spdif-sound failed with error -22
Mar 23 06:27:13 localhost kernel: [ 2.530797] cdn-dp fec00000.dp: [drm:cdn_dp_request_firmware] *ERROR* failed to request firmware: -11
Mar 23 06:27:13 localhost kernel: [ 2.556954] rockchip-saradc ff100000.saradc: Looking up vref-supply property in node /saradc@ff100000 failed
Mar 23 06:27:13 localhost kernel: [ 2.617420] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Mar 23 06:27:13 localhost kernel: [ 3.182856] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0020]
Mar 23 06:27:13 localhost kernel: [ 3.182871] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0008]
Mar 23 06:27:13 localhost kernel: [ 3.182887] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0008]
Mar 23 06:27:13 localhost kernel: [ 3.182900] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0004]
Mar 23 06:27:13 localhost kernel: [ 3.182917] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0004]
Mar 23 06:27:13 localhost kernel: [ 3.187508] dwmmc_rockchip fe310000.dwmmc: lookup for GPIO wp failed
Mar 23 06:27:13 localhost kernel: [ 3.187647] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.238999] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.288928] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.342741] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.990700] failed to power up DHD generic adapter, 1 retry left
Mar 23 06:27:15 localhost kernel: [ 4.627439] ttyS0 - failed to request DMA, use interrupt mode
Mar 23 06:27:15 localhost kernel: [ 4.790298] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790317] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790325] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790332] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790339] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790346] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 6.307739] failed to power up DHD generic adapter, 0 retry left
Mar 23 06:27:17 localhost kernel: [ 6.323836] failed to power up DHD generic adapter, max retry reached**
Mar 23 06:27:17 localhost kernel: [ 7.170420] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170438] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170446] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170453] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170460] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170467] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998049] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998067] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998075] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998082] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998088] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998095] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
(03-23-2019, 01:01 AM)siggi Wrote: Hi,
I really appreciate the enormous work which was put into this distribution and the philosophy 'make this nice computer work'.
Unfortunately, when installing the distribution on my RockPro64, I get to the login page, but when logging in the system freezes and it seems that the difference to the previous distributions I have tried are not all that big? I have a configuration with a SATA disk. Here is my kern.log with '|grep failed'. This is _before_ I try to log in. I have so far not found a good log providing a clue about the desktop login problems. Login with ssh (before desktop login) is not a problem (and has never been).
Any Idea what is wrong here?
Mar 23 06:27:13 localhost kernel: [ 0.582850] sdhci-arasan fe330000.sdhci: lookup for GPIO wp failed
Mar 23 06:27:13 localhost kernel: [ 0.583989] sdhci-arasan fe330000.sdhci: Looking up vmmc-supply property in node /sdhci@fe330000 failed
Mar 23 06:27:13 localhost kernel: [ 0.584031] sdhci-arasan fe330000.sdhci: Looking up vqmmc-supply property in node /sdhci@fe330000 failed
Mar 23 06:27:13 localhost kernel: [ 0.621483] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
Mar 23 06:27:13 localhost kernel: [ 0.621769] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
Mar 23 06:27:13 localhost kernel: [ 0.623402] phy phy-ff7c0000.phy.7: Looking up phy-supply property in node /phy@ff7c0000/dp-port failed
Mar 23 06:27:13 localhost kernel: [ 0.623531] phy phy-ff7c0000.phy.8: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
Mar 23 06:27:13 localhost kernel: [ 0.627588] rockchip-drm display-subsystem: failed to parse loader memory
Mar 23 06:27:13 localhost kernel: [ 0.627637] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Mar 23 06:27:13 localhost kernel: [ 1.687315] rockchip-spdif ff870000.spdif: ASoC: pcm constructor failed: -22
Mar 23 06:27:13 localhost kernel: [ 1.687328] asoc-simple-card spdif-sound: ASoC: failed to instantiate card -22
Mar 23 06:27:13 localhost kernel: [ 1.687480] asoc-simple-card: probe of spdif-sound failed with error -22
Mar 23 06:27:13 localhost kernel: [ 2.530797] cdn-dp fec00000.dp: [drm:cdn_dp_request_firmware] *ERROR* failed to request firmware: -11
Mar 23 06:27:13 localhost kernel: [ 2.556954] rockchip-saradc ff100000.saradc: Looking up vref-supply property in node /saradc@ff100000 failed
Mar 23 06:27:13 localhost kernel: [ 2.617420] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Mar 23 06:27:13 localhost kernel: [ 3.182856] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0020]
Mar 23 06:27:13 localhost kernel: [ 3.182871] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0008]
Mar 23 06:27:13 localhost kernel: [ 3.182887] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0008]
Mar 23 06:27:13 localhost kernel: [ 3.182900] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0004]
Mar 23 06:27:13 localhost kernel: [ 3.182917] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0004]
Mar 23 06:27:13 localhost kernel: [ 3.187508] dwmmc_rockchip fe310000.dwmmc: lookup for GPIO wp failed
Mar 23 06:27:13 localhost kernel: [ 3.187647] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.238999] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.288928] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.342741] dwmmc_rockchip fe310000.dwmmc: failed to enable vmmc regulator
Mar 23 06:27:14 localhost kernel: [ 3.990700] failed to power up DHD generic adapter, 1 retry left
Mar 23 06:27:15 localhost kernel: [ 4.627439] ttyS0 - failed to request DMA, use interrupt mode
Mar 23 06:27:15 localhost kernel: [ 4.790298] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790317] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790325] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790332] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790339] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:15 localhost kernel: [ 4.790346] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 6.307739] failed to power up DHD generic adapter, 0 retry left
Mar 23 06:27:17 localhost kernel: [ 6.323836] failed to power up DHD generic adapter, max retry reached**
Mar 23 06:27:17 localhost kernel: [ 7.170420] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170438] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170446] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170453] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170460] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:17 localhost kernel: [ 7.170467] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998049] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998067] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998075] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998082] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998088] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
Mar 23 06:27:19 localhost kernel: [ 8.998095] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
i think you should go to square one and start with sdcard image, keyboard, mouse and monitor and see if you get anything near a clean boot and if you do then start adding on to the system.
First of all: huge thanks for making this image! I was wondering what to do about the many problems I had before. I is a big upgrade from my other two desktops (2011 netbook and raspberry pi)
1) I bought pci-e sata card from pine64 with my rockpro64. If I plug it in with no sata attached and boot and run lspci, I get segmentation fault. If I plug a sata port in, the kernel completely locks up 30 seconds after boot. I am not doing this running, making all the hardware changes with power disconnected. Is this normal or do I have maybe bad hardware? The drives work fine using usb->sata adaptor. I only supplied 5v power to the drive but don't think it should need 12 volts. I tried 3 or 4 different sata drives that all work and I can feel the drive spinning.
I am still happy without pci-e support, this image nearly fixed everything else.
2) I am trying to get this setup for 3d printing. I need openscad and cura. Neither are in apt, and both of these use opengl and Qt5. The Qt5 version in apt (5.7) is also too old for either, so I compiled Qt from source which worked. Qt can compile for gles2 (or 3) or desktop gl. The version in apt is by autodetected gles.
openscad - does not compile against gles qt5 (many conflicting definitions with glew and gles2.h) does glew support gles?
- using desktop qt5, gl4es crashes:
Cannot find EGLConfig, returning null config
Unable to find an X11 visual which matches EGL config 0
Segmentation fault
cura - does not run with gles (exceptions from pyqt opengl modules..)
- desktop qt5 again crashes from gl4es the same way. In fact, every qt application crashes in this same way using desktop gl qt with gl4es.
I would love to fix gl4es to work with desktop qt and/or fix these specific programs to work with gles qt, but the simplest solution would be:
How can I just use mesa gl and software rendering without breaking anything else? I used software rendering for both of these on 2011 single core netbook and it's slow but usable. This would also give me a newer context than 2.0. I have only one libGL.so.1
Some things to try for Cura -- you may need to recompile it? But I think forcing GL 2.1 for GLES worked.
LIBGL_GL=21 cura
Cura is Qt so it supports -platform also, you can play with that:
LIBGL_GL=21 cura -platform xcb
Will be playing with this in a bit here ..
(03-17-2019, 07:49 PM)futurejones Wrote: Absolutely awesome work! This is without doubt the best performing and looking desktop available.
Thanks for all your hard work making this possible.
One problem -
I have the PCIe m.2 adapter with a 250GB WD Black nvme ssd attached.
When I log in as root everything is working beautifully. Desktop is smooth and access to PCIe ssd works as expected. But....
When I try to log in as "rock" everything freezes and I have to restart the rockpro64.
This seems to be the same issue I have had with all other distro desktop installs I have tried except they won't boot even as root.
For now I am very happy just to be able to use as root.
Hello,
I've had a rockpro64 for some time but just starting to explore this desktop image, which I hope will make this nice hardware more useful all-round. Seems I have the same issue as you - when I log into desktop as rock it crashes, but login as root is OK. I'm also using PCIe-SATA which works fine by ssh, even logged in as rock. Then I found, +/- by chance, that rock desktop login works OK *after* I uninstalled pulseaudio. Note that pulseaudio is normally disabled for root anyway. The clue was little clicks in headphones coinciding with moment the "busy" blob froze on crashing. So now have login as rock, but no sound ... Meanwhile struggling with wifi / bt (devices see each other but not connecting), will keep trying.
In general it's progress - at least I can now open the sata drive and view photos stored there (months ago using an ayufan distro - then it was either pcie or desktop, but not both together). Thanks to all who work on it, and hope all solveable soon.
(03-26-2019, 09:57 PM)benjhm Wrote: (03-17-2019, 07:49 PM)futurejones Wrote: Absolutely awesome work! This is without doubt the best performing and looking desktop available.
Thanks for all your hard work making this possible.
One problem -
I have the PCIe m.2 adapter with a 250GB WD Black nvme ssd attached.
When I log in as root everything is working beautifully. Desktop is smooth and access to PCIe ssd works as expected. But....
When I try to log in as "rock" everything freezes and I have to restart the rockpro64.
This seems to be the same issue I have had with all other distro desktop installs I have tried except they won't boot even as root.
For now I am very happy just to be able to use as root.
Hello,
I've had a rockpro64 for some time but just starting to explore this desktop image, which I hope will make this nice hardware more useful all-round. Seems I have the same issue as you - when I log into desktop as rock it crashes, but login as root is OK. I'm also using PCIe-SATA which works fine by ssh, even logged in as rock. Then I found, +/- by chance, that rock desktop login works OK *after* I uninstalled pulseaudio. Note that pulseaudio is normally disabled for root anyway. The clue was little clicks in headphones coinciding with moment the "busy" blob froze on crashing. So now have login as rock, but no sound ... Meanwhile struggling with wifi / bt (devices see each other but not connecting), will keep trying.
In general it's progress - at least I can now open the sata drive and view photos stored there (months ago using an ayufan distro - then it was either pcie or desktop, but not both together). Thanks to all who work on it, and hope all solveable soon.
This is a VERY good find! We'll need mrfixit2001 to look at this and offer some ideas as to what the hell is going on.
|
