+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: Linux on RockPro64 (https://forum.pine64.org/forumdisplay.php?fid=101)
+--- Thread: 0.7.9 Linux release from ayufan (/showthread.php?tid=6308)
RE: 0.7.9 Linux release from ayufan - ameridroid - 08-07-2018
(08-07-2018, 04:45 PM)ab1jx Wrote:
If I do cat /proc/asound/cards I see:
Code:0 [HDMI ]: HDMI - HDMI
HDMI
1 [I2S ]: I2S - I2S
I2S
2 [SPDIF ]: SPDIF - SPDIF
SPDIF
I'm guessing the AV jack is on the I2S because the other two are digital output. And maybe the amp/driver chip is connected to the I2S bus. Haven't tried it.
If I type alsamixergui on a command line I see this message to its stderr: "No mixer elems found".
I can do ls /dev/snd and see stuff in there, but there's no /dev/dsp
I'm trying to get HDMI sound working, at this point about the same troubleshooting steps. This could all be missing drivers.
Here's what I see:
Code:
0 [rockchipes8316c]: rockchip_es8316 - rockchip,es8316-codec
rockchip,es8316-codec
1 [ROCKCHIPSPDIF ]: ROCKCHIP_SPDIF - ROCKCHIP,SPDIF
ROCKCHIP,SPDIF
2 [rkhdmidpsound ]: rk-hdmi-dp-soun - rk-hdmi-dp-sound
rk-hdmi-dp-soundBased on my config, I entered the following into /etc/asound.conf:
Code:
pcm.!default {
type hw
card 2
}
ctl.!default {
type hw
card 2
}At this point, alsamixer worked for me.
RE: 0.7.9 Linux release from ayufan - ab1jx - 08-07-2018
(08-07-2018, 04:44 PM)ameridroid Wrote: I'm thinking that lightdm isn't looking in this directory (or perhaps it isn't functioning properly) because the desktop background specified in the same folder in 99_xxx_rock64.conf isn't loading either.
My #1 reference is raspi-config (from a Raspberry Pi) which looks at /etc/lightdm/lightdm.conf
But snoop around in /etc/pam.d too. Pam can prevent autologin, I see a /etc/pam.d/liightdm-autologin
Pam can cause autologin to fail sliently, not sure if it gets logged anywhere. I'd like to rip all that crap out but you can't or it probably won't boot, you need to study how to dismantle it. Like defusing a bomb.
RE: 0.7.9 Linux release from ayufan - ameridroid - 08-07-2018
(08-07-2018, 06:35 PM)ab1jx Wrote: But snoop around in /etc/pam.d too. Pam can prevent autologin, I see a /etc/pam.d/liightdm-autologin
I don't have a lightdm-autologin there:
Code:
rock64@rockpro64:/etc/pam.d$ ls
chfn common-session other sshd
chpasswd common-session-noninteractive passwd su
chsh cron polkit-1 sudo
common-account login runuser systemd-user
common-auth lxdm runuser-l
common-password newusers slockI'll have a look at the login file when I have a bit more time. Any other suggestions are welcome!
RE: 0.7.9 Linux release from ayufan - ab1jx - 08-07-2018
(08-07-2018, 06:44 PM)ameridroid Wrote:(08-07-2018, 06:35 PM)ab1jx Wrote: But snoop around in /etc/pam.d too. Pam can prevent autologin, I see a /etc/pam.d/liightdm-autologin
I don't have a lightdm-autologin there:
Code:rock64@rockpro64:/etc/pam.d$ ls
chfn common-session other sshd
chpasswd common-session-noninteractive passwd su
chsh cron polkit-1 sudo
common-account login runuser systemd-user
common-auth lxdm runuser-l
common-password newusers slock
I'll have a look at the login file when I have a bit more time. Any other suggestions are welcome!
Wow, Ubuntu actually has less junk than Debian in this case? I see:
Code:
ls /etc/pam.d
chfn common-session login runuser
chpasswd common-session-noninteractive newusers runuser-l
chsh cron other sshd
common-account lightdm passwd su
common-auth lightdm-autologin polkit-1 sudo
common-password lightdm-greeter pure-ftpd systemd-userBut wait, in your post I see you're also on a rockpro64, I'm on a rock64. Different image probably, well, yeah, Ubuntu vs Debian.
RE: 0.7.9 Linux release from ayufan - ab1jx - 08-07-2018
(08-07-2018, 05:17 PM)ameridroid Wrote: At this point, alsamixer worked for me.
OK, I updated the kernel so uname -a says
Code:
proc
Linux rock64 4.4.132-1083-rockchip-ayufan-gfd3f12ca5fae #1 SMP Mon Aug 6 20:30:2
9 UTC 2018 aarch64 GNU/LinuxI'm using your asound.conf verbatim which seems to have changed my device numbers around. I didn't have one at all before, which can be normal
Now cat /proc/asound/devices shows:
Code:
0 [I2S ]: I2S - I2S
I2S
1 [SPDIF ]: SPDIF - SPDIF
SPDIF
2 [HDMI ]: HDMI - HDMI
HDMIAnd aplay -l says
Code:
**** List of PLAYBACK Hardware Devices ****
card 0: I2S [I2S], device 0: ff010000.i2s-rk3328-hifi rk3328-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: I2S [I2S], device 1: ff010000.i2s-snd-soc-dummy-dai snd-soc-dummy-dai-1
[]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: SPDIF [SPDIF], device 0: ff030000.spdif-dit-hifi dit-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0Looks more like a device name in there now (the rk3328) but not on the HDMI.
amixer info says
Code:
Card default 'HDMI'/'HDMI'
Mixer name : ''
Components : ''
Controls : 2
Simple ctrls : 0It looks like what's not working now is the mixer. This is a Rock64, not RockPro64.
lsmod now shows
Code:
Module Size Used by
mt7601u 98304 0
dw_hdmi_i2s_audio 16384 0
mali 262144 0
ip_tables 24576 0
x_tables 32768 1 ip_tables
autofs4 40960 0RE: 0.7.9 Linux release from ayufan - ameridroid - 08-08-2018
Quote:It looks like what's not working now is the mixer. This is a Rock64, not RockPro64.
Oh, OK. This discussion should probably be moved to the Rock64 Linux group then as this is the RockPro64 Linux group.
-Bo
However, I still haven't figured out how to get Ubuntu on the RockPro64 to autologin.
RE: 0.7.9 Linux release from ayufan - ab1jx - 08-08-2018
Oh, woops. But look at the source of raspi-config, the autologin parts. https://github.com/RPi-Distro/raspi-config Armbian has something similar, maybe derived from it. You might even be able to copy out the code and make it run, it's just a bash script. Or manually do what the script does.
There are 2 different autologin scenarios for console and GUI. Checking for autologin:
Code:
get_autologin() {
if [ $(get_boot_cli) -eq 0 ]; then
# booting to CLI - check the autologin in getty or initd */
if grep -q autologin /etc/systemd/system/getty.target.wants/getty@tty1.servi
ce ; then
echo 0
else
echo 1
fi
else
# booting to desktop - check the autologin for lightdm */
if grep -q "^autologin-user=" /etc/lightdm/lightdm.conf ; then
echo 0
else
echo 1
fi
fi
}Setting autologin:
Code:
B4*)
if [ -e /etc/init.d/lightdm ]; then
systemctl set-default graphical.target
ln -fs /etc/systemd/system/autologin@.service /etc/systemd/system/getty.target.wants/getty@tty1.service
sed /etc/lightdm/lightdm.conf -i -e "s/^\(#\|\)autologin-user=.*/autologin-user=$SUDO_USER/"
disable_raspi_config_at_boot
else
whiptail --msgbox "Do 'sudo apt-get install lightdm' to allow configuration of boot to desktop" 20 60 2
return 1
fi
;;
*)
whiptail --msgbox "Programmer error, unrecognised boot option" 20 60 2
return 1RE: 0.7.9 Linux release from ayufan - dukla2000 - 08-08-2018
rkmpv works great with 4.4.132-1075 kernel (standard in 0.7.9 release)
rkmpv locks PC with 4.4.132-1083 kernel
(I also note the ALSA cards move - the HDMI is no longer card 2 in -1083)
RE: 0.7.9 Linux release from ayufan - ameridroid - 08-08-2018
(08-08-2018, 03:26 PM)dukla2000 Wrote: rkmpv works great with 4.4.132-1075 kernel (standard in 0.7.9 release)
rkmpv locks PC with 4.4.132-1083 kernel
(I also note the ALSA cards move - the HDMI is no longer card 2 in -1083)
I also verify that the HDMI sound works fine.
Anyone else having problems with video playback 2-4x too fast (youtube.com, vimeo.com, YouTube Browser for SMPlayer), and the audio is also high-pitched and fast, the same as the video?
RE: 0.7.9 Linux release from ayufan - gabrielsr - 08-08-2018
(08-08-2018, 05:45 PM)ameridroid Wrote: Anyone else having problems with video playback 2-4x too fast (youtube.com, vimeo.com, YouTube Browser for SMPlayer), and the audio is also high-pitched and fast, the same as the video?
The same here.