0.7.9 Linux release from ayufan
#21
(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-sound

Based 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.
#22
(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.
#23
(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:
[email protected]:/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!
#24
(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:
[email protected]:/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-user

But 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.
#25
(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/Linux

I'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
                      HDMI

And 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 #0

Looks 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  : 0
And now amixer refuses to open, before it opened but said there was nothing to adjust.  speaker-test, smplayer and audacity don't make any sound.

It 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  0
The dw_hdmi_i2s_audio hasn't been in there very long.
#26
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.
#27
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/[email protected]
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/[email protected] /etc/systemd/system/getty.target.wants/[email protected]
         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 1
That $SUDO_USER gets populated with who runs sudo.  If you're already root and you run raspi-config without sudo the user name is an empty string, it doesn't work.  But root can run sudo just fine.  Except root autologin is blocked elsewhere.
#28
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)
* ROCKPro64 v2.1 2GB, SM961 128GB NVMe for rootfs, HDMI video & sound, Bluetooth keyboard & mouse. Started Bionic minimal - now eoan, Openbox desktop for general purpose daily PC.
* PinePhone BraveHeart on order
#29
(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?
#30
(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.
https://github.com/dibrz/ARMBand easily maintain an ARM64 media server


Possibly Related Threads...
Thread Author Replies Views Last Post
  Rockpro64 and stock arch linux TaborFife 1 233 11-29-2019, 12:18 PM
Last Post: Yoast
  Ayufan 5.4.0 rc1 release - cannot boot Mentaluproar 1 107 11-27-2019, 04:26 AM
Last Post: dukla2000
  Reboot problem on latest ayufan and 4.4 /dev/null 2 279 11-27-2019, 04:23 AM
Last Post: dukla2000
  poor HDD performance - ayufan mainline OMV Mentaluproar 0 53 11-11-2019, 10:26 PM
Last Post: Mentaluproar
  My PCIe disk controller works with Linux 5.3.6 guannais 1 127 10-30-2019, 07:11 PM
Last Post: guannais
  Linux Build Help: Stuck at "Starting kernel ..." ihamilton 2 255 10-10-2019, 12:51 PM
Last Post: ihamilton
Big Grin Feature Complete Debian Desktop Release Mrfixit2001 152 17,274 10-09-2019, 05:42 PM
Last Post: bcnaz
  Void Linux WIP losinggeneration 0 182 10-04-2019, 03:23 AM
Last Post: losinggeneration
  Arch Linux on RockPro64 mmatyas 27 8,937 09-28-2019, 04:30 AM
Last Post: TaborFife
  Linux distro that will work with Kodi? SBCraok 9 290 09-18-2019, 02:12 AM
Last Post: mtrcycllvr

Forum Jump:


Users browsing this thread: 1 Guest(s)