LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 12-12-2019, 09:23 AM   #31
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by aaditya View Post
Hey sndwvs,

In /etc/slackpkg/mirrors, can add more mirrors or link where to find more mirrors, ie:
http://fail.pp.ua/download.html

Thanks.
these are currently all available mirrors
 
Old 12-12-2019, 09:36 AM   #32
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by aaditya View Post
Hey sndwvs,

In /etc/slackpkg/mirrors, can add more mirrors or link where to find more mirrors, ie:
http://fail.pp.ua/download.html

Thanks.
Quote:
Originally Posted by aaditya View Post
Hey sndwvs,

mpv refusing to work here:
Code:
$ mpv --profile=rkmpp VTS_01_1.VOB 
ffmpeg library versions:
   libavutil       56.35.100 (runtime 56.31.100)
   libavcodec      58.59.102 (runtime 58.54.100)
   libavformat     58.33.100 (runtime 58.29.100)
   libswscale      5.6.100 (runtime 5.5.100)
   libavfilter     7.62.100 (runtime 7.57.100)
   libswresample   3.6.100 (runtime 3.5.100)
ffmpeg version: 4.2.1

mpv was compiled against a different version of FFmpeg/Libav than the shared
library it is linked against. This is most likely a broken build and could
result in misbehavior and crashes.

mpv does not support this configuration and will not run - rebuild mpv instead.
Missing precompiled VLC from AlienBob.

I tried compiling parole from SBo. It works after installing gst-plugins-libav and tweaking some options, but full screen performance is laggy.
that's right, HWDEC support is a bunch of mpp + ffmpeg + mpv, slarm64 uses basic build keys.
for rockchip I collect these packages separately 1, 2:
ffmpeg-r95909.8c2f81a17a-aarch64-1.txz
libass-r1422.0527f02-aarch64-1mara.txz
mpp-r1763.5c1476f9-aarch64-1mara.txz
mpv-0.29.1-aarch64-3mara.txz
 
1 members found this post helpful.
Old 12-12-2019, 09:38 AM   #33
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
these are currently all available mirrors
Yes.

In that link 4 mirrors are showing currently.

While in /etc/slackpkg/mirrors, there are only 2:

Code:
#----------------------------------------------------------------
# slarm64 AArch64 current
#----------------------------------------------------------------
#http://mirrors.slackware.bg/slarm64/slarm64-current/
#
#http://dl.fail.pp.ua/slackware/slarm64-current/
It can be changed like this:

Code:
#----------------------------------------------------------------
# slarm64 AArch64 current
#----------------------------------------------------------------
#http://mirrors.slackware.bg/slarm64/slarm64-current/
#http://dl.fail.pp.ua/slackware/slarm64-current/
#
# More mirrors may be available at http://fail.pp.ua/download.html
Another small request:
To add libXfontcache

Code:
xset: error while loading shared libraries: libXfontcache.so.1: cannot open shared object file: No such file or directory
Thanks.
 
Old 12-12-2019, 09:43 AM   #34
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
that's right, HWDEC support is a bunch of mpp + ffmpeg + mpv, slarm64 uses basic build keys.
for rockchip I collect these packages separately 1, 2:
ffmpeg-r95909.8c2f81a17a-aarch64-1.txz
libass-r1422.0527f02-aarch64-1mara.txz
mpp-r1763.5c1476f9-aarch64-1mara.txz
mpv-0.29.1-aarch64-3mara.txz
Ok, got it. Will try it later. Thanks.

Can be add here: http://dl.fail.pp.ua/slackware/image...i_4/README.TXT
 
Old 12-12-2019, 09:53 AM   #35
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
try updating slackpkg reinstall slackpkg

thanks aaditya, added in build
 
1 members found this post helpful.
Old 12-12-2019, 09:57 AM   #36
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by aaditya View Post
Ok, got it. Will try it later. Thanks.

Can be add here: http://dl.fail.pp.ua/slackware/image...i_4/README.TXT
these are specific things related to a particular platform, or to describe them separately, although the build kit serves for this.
 
1 members found this post helpful.
Old 12-17-2019, 04:45 AM   #37
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by aaditya View Post
HDMI cable was connected before boot (restarted many times to check), but still got this issue.
Definitely looks like an upstream bug / regression.

When I write poweroff command screen switches on and shows the shutdown sequence before poweroff.
Tried adding the udev rule and script on my system, didnt work so far.

Script reports this:
Code:
No protocol specified
Can't open display :0.0
No protocol specified
Can't open display :0.0
Thanks!
Found a workaround for the HDMI issue:

Try restarting X server / xdm by pressing Ctrl + Alt + Backspace. Afterwards the monitor lights up and is accessible.
 
Old 12-17-2019, 05:36 AM   #38
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by aaditya View Post
Found a workaround for the HDMI issue:

Try restarting X server / xdm by pressing Ctrl + Alt + Backspace. Afterwards the monitor lights up and is accessible.
can just CTRL+ALT+F1 and back CTRL+ALT+F7
 
Old 12-17-2019, 08:42 AM   #39
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
can just CTRL+ALT+F1 and back CTRL+ALT+F7
Hey mara,

I tried, but it did not make any difference, screen remained blank. Ctrl + Alt + Backspace worked.

Maybe it depends on monitor or some other factors.
 
Old 12-19-2019, 10:58 AM   #40
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Hi sndwvs,

Slarm64 is installed on eMMC.
Would it possible to boot a Radxa Debian Stretch from a SD card? Currently it gives an error and bootloops:

Code:
U-Boot SPL 2017.09-rk3399+ (Oct 18 2019 - 23:15:34)
Trying to boot from MMC2
"Synchronous Abort" handler, esr 0x02000000
ELR:     200000
LR:      18cc
x 0: 0000000000400000 x 1: 0000000000000000
x 2: 0000000000000000 x 3: 0000000000400180
x 4: 0000000000000000 x 5: 0000000000000000
x 6: 0000000000000000 x 7: 0000000080020000
x 8: 0000000000000e08 x 9: 0000000000020000
x10: 00000000005ffcbc x11: 000000000000f720
x12: 0000000000000958 x13: 0000000000000000
x14: 000000000000f720 x15: 000000000000f720
x16: 0000000000200000 x17: 0000000000050700
x18: 00000000005ffea0 x19: 000000000000efa0
x20: 000000000000ef40 x21: 000000000000ef28
x22: 00000000005ffe58 x23: 0000000000000000
x24: 000000000000d2a3 x25: 000000000000d28b
x26: 00000000deadbeef x27: 00000000000004e4
x28: 00000000000004e4 x29: 00000000005ffdf0

Resetting CPU ...
As a comparison, Radxa Debian Stretch installed on eMMC is able to boot the card:
Code:
U-Boot SPL board init

U-Boot SPL 2017.09-rk3399+ (Oct 18 2019 - 23:15:34)
Trying to boot from MMC2
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-rk3399+ (Oct 18 2019 - 23:17:11 +0300)

Model: RockPi-4B
DRAM:  3.9 GiB
DCDC_REG1@vdd_center: ; enabling
DCDC_REG2@vdd_cpu_l: ; enabling
DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
LDO_REG4@vcc_sd: set 3300000 uV; enabling
LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
LDO_REG6@vcc_1v5: set 1500000 uV; enabling
LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
LDO_REG8@vcc_3v0: set 3000000 uV; enabling
SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
vdd-log@vdd_log: ; enabling (ret: -38)
MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
SF: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: RockPi-4B
normal boot
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1393 bytes read in 15 ms (89.8 KiB/s)
## Executing script at 00500000
U-boot loaded from SD
49 bytes read in 20 ms (2 KiB/s)
93484 bytes read in 75 ms (1.2 MiB/s)
20318216 bytes read in 2169 ms (8.9 MiB/s)
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   reserving fdt memory region: addr=1f00000 size=7d000
   Loading Device Tree to 00000000f5e84000, end 00000000f5f03fff ... OK

Starting kernel ...
Thanks.

Will provide more info as needed.
 
Old 12-19-2019, 11:10 AM   #41
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
Hi aaditya,

try rewriting u-boot from Radxa Debian Stretch to eMMC.
how does the system behave if it is on a SDcard and on slarm64 eMMC?
 
Old 12-19-2019, 11:48 AM   #42
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Hi aaditya,

try rewriting u-boot from Radxa Debian Stretch to eMMC.
Hi Mara,

Could give some tips/method on how to rewrite u-boot from Radxa stretch to eMMC?

Quote:
Originally Posted by sndwvs View Post
how does the system behave if it is on a SDcard and on slarm64 eMMC?
If eMMC with Slarm64 is present:

* Able to boot Slarm64 on SD.
* Also able to boot Armbian on SD.
* However not able to boot Radxa Debian Stretch or Manjaro ARM on SD.

If eMMC slot is empty, Slarm64, Armbian, Radxa Debian, Manjaro ARM all are able to boot from SD.

Thanks.
 
Old 12-19-2019, 12:22 PM   #43
sndwvs
Member
 
Registered: Aug 2014
Posts: 338

Original Poster
Rep: Reputation: Disabled
in /usr/lib/u-boot-rockpi4b
files:
rockpi4b-rk-idbloader.img
rockpi4b-rk-trust.img
rockpi4b-rk-uboot.img

flash:
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-idbloader.img of=/dev/mmcblk1 seek=64
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-uboot.img of=/dev/mmcblk1 seek=16384
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-trust.img of=/dev/mmcblk1 seek=24576
 
1 members found this post helpful.
Old 12-21-2019, 03:15 AM   #44
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
in /usr/lib/u-boot-rockpi4b
files:
rockpi4b-rk-idbloader.img
rockpi4b-rk-trust.img
rockpi4b-rk-uboot.img

flash:
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-idbloader.img of=/dev/mmcblk1 seek=64
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-uboot.img of=/dev/mmcblk1 seek=16384
dd if=/usr/lib/u-boot-rockpi4b/rockpi4b-rk-trust.img of=/dev/mmcblk1 seek=24576
Hi sndwvs,

That worked! Was able to boot the Radxa Stretch image.

However, now Slarm64 on the eMMC fails to boot:
Code:
U-Boot 2017.09-02676-g4490220395 (Jul 01 2019 - 07:49:56 +0000)

Model: Rockchip RK3399 rockpi4b Board
PreSerial: 2
DRAM:  3.9 GiB
Relocation Offset is: f5be0000
Sysmem: init
I2c speed: 400000Hz
PMIC:  RK808 
vdd-center init 950000 uV
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
Using default environment

Model: Rockchip RK3399 rockpi4b Board
Bootdev(atags): mmc 0
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
## Unknown partition table type 0
PartType: <NULL>
RKPARM: Invalid parameter part table
get part misc fail -1
boot mode: None
RKPARM: Invalid parameter part table
init_resource_list: failed to get boot part, ret=-1
RKPARM: Invalid parameter part table
init_resource_list: failed to get resource part, ret=-1
Can't find file:logo.bmp
failed to display uboot logo
CLK: (uboot. arml: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
CLK: (uboot. armb: enter 24000 KHz, init 24000 KHz, kernel 0N/A)
  aplll 816000 KHz
  apllb 24000 KHz
  dpll 800000 KHz
  cpll 24000 KHz
  gpll 800000 KHz
  npll 600000 KHz
  vpll 24000 KHz
  aclk_perihp 133333 KHz
  hclk_perihp 66666 KHz
  pclk_perihp 33333 KHz
  aclk_perilp0 266666 KHz
  hclk_perilp0 88888 KHz
  pclk_perilp0 44444 KHz
  hclk_perilp1 100000 KHz
  pclk_perilp1 50000 KHz
Net:   eth0: ethernet@fe300000
Hit key to stop autoboot('CTRL+C'):  0 

Device 0: unknown device
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc0(part 0) is current device
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
RKPARM: Invalid parameter part table
** No partition table - mmc 0 **
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   failed to get usb phy
Port not available.
USB3:   failed to get usb phy
Port not available.
USB4:   Can't get the usbphy register address
probe failed, error -6
USB5:   Can't get the usbphy register address
probe failed, error -6
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-ae-1e-19-20-55-6d
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@fe300000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
To revert, I booted up the Radxa Stretch image, mounted the Slarm64 eMMC partition, and rewrote the u-boot using following command (adapted from setup.sh):

Code:
dd if=/boot/rksd_loader.img of=/dev/mmcblk1 seek=64
Thanks for your help.
 
Old 12-21-2019, 12:58 PM   #45
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 231
Blog Entries: 2

Rep: Reputation: Disabled
Note for people looking for a graphical way to setup/change wireless connection:

wpa_gui is available. Requires qt package + xfsudo for running GUI app with root privilege.

To use, setup wireless network config as specified by sndwvs (thanks!) in #15. Then run

Code:
xfsudo wpa_gui
to bring up a GUI.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ROCKPro64 RK3399 (aarch64) sndwvs Slackware - ARM 11 01-12-2020 01:28 PM
Video : RecalBox on the Rock Pi 4 (and other RK3399 boards) NicoD SBC Linux - Embedded & Single-board computer 2 02-01-2019 09:05 AM
ROCK-esque "distro", but not ROCK? piete Linux - Distributions 5 08-21-2006 05:41 PM
Rock Linux -- does it rock ?? rolando Linux - Distributions 2 10-10-2004 02:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 08:55 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration