Jump to content

chun.de.lac

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by chun.de.lac

    SPDIF not working due to a bug in kernel 4.16.8, after Cubox-i4Pro Armbian Ubuntu upgraded from 5.38 to 5.44

    in Other families

    Posted

    Hello Igor,

    after my Cubox-i was upgraded from Armbian 5.60 to 5.70 today, SPDIF audio output stopped working.

    Report:

    http://ix.io/1yjz

     

    Armbian 5.70:

    Operating system     Ubuntu Linux 18.04.1

    Kernel and CPU     Linux 4.19.14-cubox on armv7l

     

    SPDIF audio output used to work properly with Armbian 5.60 (kernel 4.14.70)

     

    Please, let me know if I can be of any further help.

    Thank you!

    0

    SPDIF not working due to a bug in kernel 4.16.8, after Cubox-i4Pro Armbian Ubuntu upgraded from 5.38 to 5.44

    in Other families

    Posted

    12 minutes ago, Igor said:

    On which kernel? If I understand correctly ... Cubox booted to new system fine, only audio was missing?

    First reboot after packages were upgraded to 5.44, Cubox-i booted, but no audio. After second reboot, Cubox-i did not boot anymore (no SSH).

    I've just restored Armbian Ubuntu 5.38 from my backup image.

    Upgraded only the package "linux-image-next-cubox 5.44", (armhf Linux kernel, version 4.16.8-cubox),  no other packages upgraded.

    Cubox-i booted, but no audio on optical.

    Just let me know if you need me to test anything else.

    0

    SPDIF not working due to a bug in kernel 4.16.8, after Cubox-i4Pro Armbian Ubuntu upgraded from 5.38 to 5.44

    in Other families

    Posted

    Hello everyone,

     

    just wanted to let you know, upgrade from Armbian Ubuntu 5.38 to 5.44 caused problems on my Cubox-i4Pro.

    - Armbian Ubuntu 5.38 headless (no display connected to Cubox-i) worked perfectly, there were no issues with anything.

    - Upgraded Armbian Ubuntu 5.38 to 5.44 (apt-get) and rebooted

    - After reboot, no audio was sent to my audio amplifier (through Toslink optical cable) by Shairport-Sync 3.1.7 (AirPlay emulator). Airplay was visible on my iOS devices (iPad, iPhone) and audio was streamed from iOS to AirPlay, but no audio was sent by Cubox-i to the optical connection to my audio amplifier.

    - Removed the Shairport package using dpkg -r

    - Rebooted Cubox-i using command reboot, but Cubox-i not booting anymore, SSH connection not possible anymore, red LED on Cubox-i is off (I think the LED was off also on Armbian ver. 5.38)

    - Unplugged the power cable, waited a minute, restored power, Cubox-i not booting, no SSH

     

    I'll restore the system ver. 5.38 from my backup image.

    Please let me know if I can be of any help.

    Thanks!

    0

    System time always wrong after boot - after upgrade from 4.7 to 4.81

    in Other families

    Posted

    [sOLVED]

     

    Many thanks to both of you!

     

    I've done the following steps, just for your records:

     

    - Rebooted the unit

    - System time incorrect (January 1970)

    - Manually synced system time to hardware clock, in order to get the internet connection through OpenVPN working

    - Installed fake-hwclock package (current version is 0.9): apt-get install fake-hwclock

    - Rebooted the unit

    - System time incorrect (January 1970)

    - Manually synced system time to hardware clock, in order to get the internet connection through OpenVPN working

    - Synced system time and hardware clock using NTP

    - Rebooted the unit

    - System time correct after boot

    - OpenVPN works

     

    Thank you once again!

    You can close this thread.

    1

    System time always wrong after boot - after upgrade from 4.7 to 4.81

    in Other families

    Posted

    Hi Igor,

    my Cubox-i4Pro worked perfectly fine with your Armbian Debian Jessie, until I upgraded from 4.7 to 4.81.

    After the upgrade was performed today, the system time is always wrong after boot, it is always set to Jan 1 01:00:00 1970.

    Setting the system time correctly does not help, after reboot it is wrong again.

    I didn't observe this behavior before upgrade, the system time just used to work without any attention needed.

    Nothing else was changed in the system, only the upgrade of Armbian was done to ver 4.81.

    So I'm wondering what went wrong with the upgrade.

    Hardware time is always correct, syncing system time to hardware time does not survive boot.

    I tried to delete and re-create /etc/adjtime, it does not help.

    I want to avoid workarounds like cron or ntp, if it worked properly before the upgrade it should just work I assume.

     

    These packages were upgraded :

     

    Start-Date: 2015-12-28  20:05:14
    Commandline: apt-get -y install linux-dtb-cubox
    Upgrade: linux-dtb-cubox:armhf (4.70, 4.81)
    End-Date: 2015-12-28  20:05:31

    Start-Date: 2015-12-28  20:05:49
    Commandline: apt-get -y install linux-firmware-image-cubox
    Upgrade: linux-firmware-image-cubox:armhf (4.70, 4.81)
    End-Date: 2015-12-28  20:05:57

    Start-Date: 2015-12-28  20:06:24
    Commandline: apt-get -y install linux-headers-cubox
    Upgrade: linux-headers-cubox:armhf (4.70, 4.81)
    End-Date: 2015-12-28  20:20:16

    Start-Date: 2015-12-28  20:20:57
    Commandline: apt-get -y install linux-image-cubox
    Upgrade: linux-image-cubox:armhf (4.70, 4.81)
    End-Date: 2015-12-28  20:29:25

    Start-Date: 2015-12-28  20:29:42
    Commandline: apt-get -y install linux-jessie-root-cubox-i
    Upgrade: linux-jessie-root-cubox-i:armhf (4.70, 4.81)
    End-Date: 2015-12-28  20:29:48
     

     

    The unit is Cubox-i4Pro with Armbian Debian Jessie.

     

    Please let me know if you need some further information.

     

    Thanks!!

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept