Jump to content

Search the Community

Showing results for tags 'rockpi-s'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 19 results

  1. Hi, everyone I have 2 rockpi s based boards, and I tried to apply an overlay to one. It actually compiled, I rebooted and the nothing more. I connected serial, e it was on U-boot, spitting this: U-boot seems unable to load the device tree, but to my knowledge, a broken overlay shouldn't break anything Any help is welcome Thx
  2. Good morning, I cannot seem to get the the newest image (22.08 Bullseye) to boot. I've noticed the disk arrangement is significantly different than the known working image I am using. Here is what I see on the known working image... #fdisk -l Disk /dev/mmcblk0: 28.9 GiB, 30985420800 bytes, 60518400 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2A33F1A5-75EA-4125-AC19-16C0435D774A Device Start End Sectors Size Type /dev/mmcblk0p1 64 8063 8000 3.9M Linux filesystem /dev/mmcblk0p2 16384 24575 8192 4M Linux filesystem /dev/mmcblk0p3 24576 32767 8192 4M Linux filesystem /dev/mmcblk0p4 32768 262143 229376 112M EFI System /dev/mmcblk0p5 262144 60518366 60256223 28.7G Linux filesystem #cat /etc/debian_version 9.9 The newest image is in has a DOS partition table and only one partition. Disk /dev/sdc: 28.91 GiB, 31016878080 bytes, 60579840 sectors Disk model: STORAGE DEVICE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1640add5 Device Boot Start End Sectors Size Id Type /dev/sdc1 32768 3833855 3801088 1.8G 83 Linux Also may be important to note my rock pi S has no onboard flash, only SD slot. Am I missing something? Thank you for your time.
  3. I just tried the official Jammy image on the Rock Pi S, which does not boot. Looking at serial, it halts after "Starting kernel ...". I've tried redownloading the image, burning it again and on a different SD card. I also tried the bullseye image, which *does* boot (which makes me believe this is not a hardware issue). Anyone with a Rock Pi S that could confirm my observation? This image failed to boot: Armbian_22.08.7_Rockpi-s_jammy_edge_5.19.16.img Serial output: rock-pi-s-fail.txt This image booted ok: Armbian_22.08.7_Rockpi-s_bullseye_edge_5.19.16.img Serial output: rock-pi-s-ok.txt Diff of serial output (up to Staring kernel... line): --- rock-pi-s-fail.txt 2022-11-09 12:40:03.199949846 +0100 +++ rock-pi-s-ok.txt 2022-11-09 12:58:16.937136391 +0100 @@ -52,7 +52,7 @@ BootCapSize=0 UserCapSize=29554MB FwPartOffset=2000 , 0 -StorageInit ok = 27839 +StorageInit ok = 27858 SecureMode = 0 Secure read PBA: 0x4 Secure read PBA: 0x404 @@ -70,7 +70,7 @@ No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x9dad0 -RunBL31 0x40000 @ 106200 us +RunBL31 0x40000 @ 106201 us ^AINFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 @@ -108,8 +108,8 @@ 3045 bytes read in 5 ms (594.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 -176 bytes read in 5 ms (34.2 KiB/s) -23219213 bytes read in 986 ms (22.5 MiB/s) +176 bytes read in 4 ms (43 KiB/s) +19531454 bytes read in 831 ms (22.4 MiB/s) 31263232 bytes read in 1328 ms (22.5 MiB/s) 54638 bytes read in 9 ms (5.8 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr' @@ -117,15 +117,33 @@ ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) - Data Size: 23219149 Bytes = 22.1 MiB + Data Size: 19531390 Bytes = 18.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 - Loading Ramdisk to 0c8fd000, end 0df21bcd ... OK + Loading Ramdisk to 0cc81000, end 0df2167e ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) - Loading Device Tree to 000000000c887000, end 000000000c8fcfff ... OK + Loading Device Tree to 000000000cc0b000, end 000000000cc80fff ... OK Starting kernel ...
  4. I have add user dtbo with "armbian-add-overlay rk3308-w1-gpio.dts" but it's NOT work.Some message is shown as below: pi@Pi-S:/boot/overlay-user$ dmesg | grep gpio [ 0.063257] OF: /onewire@0: could not get #gpio-cells for /usb@ff400000 [ 0.096538] rockchip-gpio ff220000.gpio: probed /pinctrl/gpio@ff220000 [ 0.097838] rockchip-gpio ff230000.gpio: probed /pinctrl/gpio@ff230000 [ 0.099097] rockchip-gpio ff240000.gpio: probed /pinctrl/gpio@ff240000 [ 0.100300] rockchip-gpio ff250000.gpio: probed /pinctrl/gpio@ff250000 [ 0.101462] rockchip-gpio ff260000.gpio: probed /pinctrl/gpio@ff260000 [ 8.818566] gpio-17 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 8.818683] OF: /onewire@0: could not get #gpio-cells for /usb@ff400000 [ 8.818731] w1-gpio onewire@0: gpio_request_one (ext_pullup_enable_pin) failed [ 8.818742] w1-gpio: probe of onewire@0 failed with error -22 [ 8.872897] rk3308-acodec ff560000.acodec: Don't need hp-ctl gpio [ 8.872955] rk3308-acodec ff560000.acodec: Don't need spk-ctl gpio [ 8.872984] rk3308-acodec ff560000.acodec: Don't need pa-drv gpio [ 8.873096] rk3308-acodec ff560000.acodec: Don't need micbias-en gpio What should I do to ?
  5. Thanks to @brentr we got new images with several fixes: https://armbian.atlassian.net/browse/AR-1269 RockPI WiFi assigned different MAC address on each boot https://armbian.atlassian.net/browse/AR-1268 RockPI-S WiFi throughput only 300K bytes/second https://armbian.atlassian.net/browse/AR-1265 Rock PI-S images will not boot from internal EMMC (SDNAND) https://www.armbian.com/rockpi-s/
  6. Hello, I have installed the Armbian image for Rock Pi S (https://www.armbian.com/rockpi-s/) released 19th of October 2022 on my Rock Pi S and it boots fine. However, if I update the linux kernel (using apt-get install linux-dtb-edge-rockchip64 linux-image-edge-rockchip64) this breaks the image and it will be stuck on starting kernel the next time I reboot. These packages are not installed automatically, but are listed as kept back. However, since they break the system they should maybe not be possible to install.
  7. Hello, I am quite new to armbian build system. I have rock pi s v13 hardware. I want to change the default UART2 serial console port in Armbian for Rock Pi s to UART0. The reason is I need hardware flow control with one of my serial port. And UART1's RTS/CTS are muxed with UART2. And no other port exposed on Rock Pi s have the hardware flow control pins. Please guide me how I can achieve this.
  8. Using the 5.xx kernal I have been changing the eth0 MAC address at /etc/NetworkManager/system-connections/ 'Wired connection 1.nmconnection'. This has changed a bit as the versions progress - but version Armbian 21.08.2 Focal / Linux 5.14.5-rockchip64 has now moved the "wired ..." file to the /run/NetworkManager/system-connections/ and suspect the file is recreated at every boot (edits do not stick). I have tried to set MAC at /boot/armbianEnv.txt and in the eth config file. None work. Any ideas as to how to set the MAC address - and is it now even possible?.
  9. I think I'm finally managing to understand this Armbian build system. It's an amazing piece of work! However, after the build, many source files end up owned by the root user. There's just a lot of activity going on "as root" that probably doesn't need to be run with that privilege. Disaster seems just one build script error away. Am I doing something wrong? Is there a simple way to avoid this (without resorting to virtualization of the build environment). Has this not bothered anyone else?
  10. Hi guys, I have checked the Buster image and stuck in following issue: On Rockpis, tty2 and (the only working) spi2 sharing the same PINs. Due to this reason, SPI is not functional . from dmesg: [ 1.598230] rockchip-pinctrl pinctrl: pin gpio1-22 already requested by ff0c0000.serial; cannot claim for ff140000.spi [ 1.598269] rockchip-pinctrl pinctrl: pin-54 (ff140000.spi) status -22 [ 1.598287] rockchip-pinctrl pinctrl: could not request pin 54 (gpio1-22) from group spi2-miso on device rockchip-pinctrl [ 1.598304] rockchip-spi ff140000.spi: Error applying setting, reverse things back I try to switch back tty2 to tty0 in dts and also in boot.cmd. It is only partial working, so that after the u-boot preloader has finished tty0 is used. But SPI is still not working. I assume that must something to do with u-boot preloader, which is still using tty2. Please move tty2 back to tty0. An other issue is, that the overlays seems not to work. Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr' There is only a rockship-fixup.scr avail. I suppose this missing fixup may harm the overlays ? If someone is looking how to enable 8 Channel I2S i like to share my dts part to enabe this: tdm_sound { compatible = "simple-audio-card"; simple-audio-card,name = "i2s_8ch_0"; simple-audio-card,format = "dsp_a"; simple-audio-card,mclk-fs = < 128 >; simple-audio-card,bitclock-master = <&tdm_snd_cpu>; simple-audio-card,frame-master = <&tdm_snd_cpu>; tdm_snd_cpu: simple-audio-card,cpu { dai-tdm-slot-num = <8>; dai-tdm-slot-width = <16>; sound-dai = <&i2s_8ch_0>; }; tdm_snd_codec: simple-audio-card,codec { sound-dai = <&tdm_codec>; }; }; tdm_codec: dummy-codec { compatible = "rockchip,dummy-codec"; #sound-dai-cells = <0>; }; &i2s_8ch_0 { assigned-clocks = <&cru SCLK_I2S0_8CH_RX>; assigned-clock-parents = <&cru SCLK_I2S0_8CH_TX_MUX>; rockchip,clk-trcm = <1>; rockchip,bclk-fs = <128>; #sound-dai-cells = <0>; status = "okay"; } For using it, it is required to port the rockship dummy-codec to have more than 2 channels. It can be compiled as kernel module. When you like to use up to 4 pcm5102a codecs, you must port the rockchip-multichannel-codec. It can access all 4 I2S-Dataline with shared sync/clock. I have check the function of the dummy-codec with an logic analysator and it is working. I'm also try out the bullseye image. It has the same issues like buster, but fails to reboot. Only power cycle works. Thanks, Peter
  11. My Rock Pi S logs a NULL pointer dereference in the ext4 module after running for 1 to 3 hours. Subsequently existing processes continue to run but it appears that new processes can't start (eg I can't ssh in). The filesystem is on a new Sandisk Ultra Plus microSD card. As a test, I remounted the root filesystem read/write and the board ran flawlessly for 10 hours. When I get time I will try rebuilding the image with the root filesystem on F2FS. Aug 31 09:31:27 rockpi-s kernel: [ 1944.993824] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Aug 31 09:31:27 rockpi-s kernel: [ 1944.994681] Mem abort info: Aug 31 09:31:27 rockpi-s kernel: [ 1944.994952] ESR = 0x96000004 Aug 31 09:31:27 rockpi-s kernel: [ 1944.995248] EC = 0x25: DABT (current EL), IL = 32 bits Aug 31 09:31:27 rockpi-s kernel: [ 1944.995732] SET = 0, FnV = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996020] EA = 0, S1PTW = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996313] Data abort info: Aug 31 09:31:27 rockpi-s kernel: [ 1944.996587] ISV = 0, ISS = 0x00000004 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996943] CM = 0, WnR = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.997230] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000003851000 Aug 31 09:31:27 rockpi-s kernel: [ 1944.997813] [00000000000000f8] pgd=0000000000000000, p4d=0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1944.998587] Internal error: Oops: 96000004 [#1] PREEMPT SMP Aug 31 09:31:27 rockpi-s kernel: [ 1944.999104] Modules linked in: rfkill snd_soc_rk3308 snd_soc_core snd_pcm_dmaengine snd_pcm cdc_acm snd_timer snd soundcore cpufreq_dt zr am ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs Aug 31 09:31:27 rockpi-s kernel: [ 1945.001035] CPU: 3 PID: 213 Comm: kworker/u8:3 Not tainted 5.10.60-rockchip64 #21.08.1 Aug 31 09:31:27 rockpi-s kernel: [ 1945.001746] Hardware name: Radxa ROCK Pi S (DT) Aug 31 09:31:27 rockpi-s kernel: [ 1945.002197] Workqueue: writeback wb_workfn (flush-179:0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.003074] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--) Aug 31 09:31:27 rockpi-s kernel: [ 1945.004117] pc : clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.005032] lr : clear_page_dirty_for_io+0x18/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.005936] sp : ffff8000123db730 Aug 31 09:31:27 rockpi-s kernel: [ 1945.006875] x29: ffff8000123db730 x28: ffff8000123db9a0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.007607] x27: 00000000000021f9 x26: 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.009006] x25: 000000000008c1f9 x24: 000000000000000c Aug 31 09:31:27 rockpi-s kernel: [ 1945.009951] x23: fffffe00003c7340 x22: ffff0000066b5400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.010761] x21: ffff8000123db870 x20: fffffe00003c7340 Aug 31 09:31:27 rockpi-s kernel: [ 1945.012020] x19: fffffe00003c7340 x18: 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.012965] x17: 0000000000000000 x16: ffff000002259110 Aug 31 09:31:27 rockpi-s kernel: [ 1945.014196] x15: 0000000000000001 x14: 0000000000000002 Aug 31 09:31:27 rockpi-s kernel: [ 1945.014706] x13: 0000000000005966 x12: 000000000000000b Aug 31 09:31:27 rockpi-s kernel: [ 1945.015216] x11: 0000000000000000 x10: ffff000006804540 Aug 31 09:31:27 rockpi-s kernel: [ 1945.015724] x9 : 0000000000000001 x8 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.016230] x7 : 00000000001f9000 x6 : fffffe00003c7300 Aug 31 09:31:27 rockpi-s kernel: [ 1945.016751] x5 : 00000000171cc000 x4 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.017258] x3 : 00000000000021f8 x2 : ffff0000004df800 Aug 31 09:31:27 rockpi-s kernel: [ 1945.017779] x1 : 0000000000000000 x0 : ffff0000036799d8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.018291] Call trace: Aug 31 09:31:27 rockpi-s kernel: [ 1945.018544] clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.018998] mpage_submit_page+0x30/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.019379] mpage_map_and_submit_buffers+0x168/0x2a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.019856] ext4_writepages+0x748/0xc38 Aug 31 09:31:27 rockpi-s kernel: [ 1945.020236] do_writepages+0x58/0x100 Aug 31 09:31:27 rockpi-s kernel: [ 1945.020598] __writeback_single_inode+0x44/0x508 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021037] writeback_sb_inodes+0x1e0/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021460] __writeback_inodes_wb+0x78/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021865] wb_writeback+0x26c/0x400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022218] wb_workfn+0x310/0x5f8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022549] process_one_work+0x1ec/0x4d0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022935] worker_thread+0x48/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023287] kthread+0x140/0x150 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023605] ret_from_fork+0x10/0x34 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023962] Code: b000b402 f9401401 f9474042 eb02003f (54000de0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.024526] ---[ end trace cdc066846165d221 ]--- Aug 31 09:31:27 rockpi-s kernel: [ 1945.025183] ------------[ cut here ]------------ Aug 31 09:31:27 rockpi-s kernel: [ 1945.025659] WARNING: CPU: 3 PID: 213 at kernel/exit.c:725 do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.026307] Modules linked in: rfkill snd_soc_rk3308 snd_soc_core snd_pcm_dmaengine snd_pcm cdc_acm snd_timer snd soundcore cpufreq_dt zram ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs Aug 31 09:31:27 rockpi-s kernel: [ 1945.028231] CPU: 3 PID: 213 Comm: kworker/u8:3 Tainted: G D 5.10.60-rockchip64 #21.08.1 Aug 31 09:31:27 rockpi-s kernel: [ 1945.029079] Hardware name: Radxa ROCK Pi S (DT) Aug 31 09:31:27 rockpi-s kernel: [ 1945.029525] Workqueue: writeback wb_workfn (flush-179:0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.030047] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--) Aug 31 09:31:27 rockpi-s kernel: [ 1945.030612] pc : do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.030956] lr : die+0x208/0x248 Aug 31 09:31:27 rockpi-s kernel: [ 1945.031260] sp : ffff8000123db380 Aug 31 09:31:27 rockpi-s kernel: [ 1945.031576] x29: ffff8000123db380 x28: ffff0000029fe580 Aug 31 09:31:27 rockpi-s kernel: [ 1945.032086] x27: 00000000000021f9 x26: 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.032594] x25: ffff80001023b328 x24: 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.033100] x23: ffff8000123db497 x22: ffff800011270260 Aug 31 09:31:27 rockpi-s kernel: [ 1945.033605] x21: 000000000000000b x20: ffff8000118b9948 Aug 31 09:31:27 rockpi-s kernel: [ 1945.034112] x19: ffff0000029fe580 x18: 0000000000000010 Aug 31 09:31:27 rockpi-s kernel: [ 1945.034617] x17: 0000000000000000 x16: ffff000002259110 Aug 31 09:31:27 rockpi-s kernel: [ 1945.035128] x15: 00000000000001b7 x14: ffff8000123db0c0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.035643] x13: 00000000ffffffea x12: ffff80001194ee98 Aug 31 09:31:27 rockpi-s kernel: [ 1945.036152] x11: 0000000000000003 x10: ffff800011936e58 Aug 31 09:31:27 rockpi-s kernel: [ 1945.036660] x9 : ffff800011936eb0 x8 : 0000000000017fe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.037167] x7 : c0000000ffffefff x6 : 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.037689] x5 : 0000000000000001 x4 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.038200] x3 : 0000000000000000 x2 : ffff8000118b9948 Aug 31 09:31:27 rockpi-s kernel: [ 1945.038707] x1 : ffff8000123dbc90 x0 : ffff00001d6b8c88 Aug 31 09:31:27 rockpi-s kernel: [ 1945.039216] Call trace: Aug 31 09:31:27 rockpi-s kernel: [ 1945.039471] do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.039783] die+0x208/0x248 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040070] die_kernel_fault+0x64/0x78 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040441] __do_kernel_fault+0x74/0x148 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040826] do_page_fault+0x1c8/0x3a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041206] do_translation_fault+0x50/0x60 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041605] do_mem_abort+0x40/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041944] el1_abort+0x48/0x70 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042263] el1_sync_handler+0x64/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042625] el1_sync+0x84/0x140 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042942] clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.043374] mpage_submit_page+0x30/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.043753] mpage_map_and_submit_buffers+0x168/0x2a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044225] ext4_writepages+0x748/0xc38 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044601] do_writepages+0x58/0x100 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044960] __writeback_single_inode+0x44/0x508 Aug 31 09:31:27 rockpi-s kernel: [ 1945.045398] writeback_sb_inodes+0x1e0/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.045804] __writeback_inodes_wb+0x78/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046209] wb_writeback+0x26c/0x400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046563] wb_workfn+0x310/0x5f8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046897] process_one_work+0x1ec/0x4d0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047296] worker_thread+0x48/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047648] kthread+0x140/0x150 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047963] ret_from_fork+0x10/0x34 Aug 31 09:31:27 rockpi-s kernel: [ 1945.048302] ---[ end trace cdc066846165d222 ]---
  12. Hi all Been playing with this rockpi s bluetooth . I noticed debian kernel 5.x and bluetoothctl, just hangs. No issues with debian kernel 4.x. Anyone else had this, and able to get it to work?
  13. Hi. I am trying to use bluetooth with my rock pis but I can't with armbian but debian. With debian I just followed this page and it works. https://wiki.radxa.com/RockpiS/Debian#Bluetooth But I want to work it in armbian. I turn bluetooth on in armbian-config. But "hciconfig" have no result and when I power on bluetooth, it say "No default controller available". So I searched and found it. Is it mean that I need to build a kernel to use bluetooth??
  14. I have a v1.2 Rockpi S with 512MB of RAM, while using the latest Armbian Focal and Buster images (20.08.1 with kernel 4.4.y), I have been experiencing WIFI issues. The device connects to the Access Point and maintains the connection but every minute or two the SSH connection hangs or freezes for several seconds and then comes back and prints everything that when on during the period it was not responsive. When I used the images with the 5.8.y kernel, I did not experience the same issue. In all cases wired ethernet (eth0) is not effected by the issue. Continuously pinging a local system shows the below result. Other WIFI devices on the same network do not experience this issue and I have tested it on two separate Rockpi S devices and 2 different Micro-SD cards. The power supply is a 15W USB-C power supply and I do not suspect it to be the issue. $ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.55 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.18 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.06 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.70 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=6.50 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.42 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=5.48 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=6.84 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.41 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.34 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=5.94 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=6005 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4998 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=3990 ms 64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2982 ms 64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1974 ms 64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=966 ms 64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=3.58 ms 64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=3.26 ms 64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=5.30 ms Steps to reproduce: 1. Install Armbian Focal with Kernel 4.4.y (Armbian_20.08.1_Rockpi-s_focal_legacy_4.4.228_minimal.img.xz) 2. Complete the standard installation/setup using wired ethernet 3. Configure and enable WIFI access using armbian-config on the wlan0 interface (note: same issue occurs when p2p0 is used) 4. Disconnect the eth0 cable 5. SSH to Rockpi S using WIFI/wlan0 6. Execute ping command to another device on the local network Not sure where else to look to see if I can identify the cause, any pointers would be appreciated.
  15. i2cdetect -l i2c-1 i2c rk3x-i2c I2C adapter The i2c-1 device works fine and there is a working sensor attached. Trying to get the i2c-0 device up and running. Added overlays=i2c0 to /boot/armbianEnv.txt but it didn't work. There doesn't appear to be a file with that name so I'm not sure if this doesn't exist or if there is a package that needs to be installed. find / -name '*.dtbo' 2> /dev/null | grep 3308 /boot/overlays/rk3308-uart2.dtbo /boot/overlays/rk3308-uart1.dtbo /boot/overlays/rk3308-uart0.dtbo armbian-config flashes this in the system->hardware menu │ Loading error: expected at least 6 tokens for --checklist, have 4. use --help to list options. submodule ... │ What is the right way to get i2c-0 up and running? armbianmonitorRockPiS.txt
  16. There seems to be some issue with the very early bootup on the rockpi-S using the dev or current target (not the 4.4 kernel) It hangs and requires a reboot, something like every 4th bootup works. I have a bunch of logs with various errors like: Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: add_uevent_var+0x12c/0x130 [ccff800010110d58] address between user and kernel address ranges Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: vsnprintf+0x724/0x728 This usually happens about 2.7 - 2.8 seconds into bootup. I have been building from source with a custom config and this (or something similar) and I believe 5.4 was the last stable kernel in my testing. Reproduction: Start with Armbian_20.08.1_Rockpi-s_buster_current_5.8.6_minimal.img Change add 'earlycon debug' to extrags in /boot/armbianEnv.txt Start (observe with serial connection). When the board doesn't boot, the blue LED never starts blinking.
  17. Hi. I was testing pwm with a motor, then my rock pis stopped. After boot, I couldn't see wlan0 in nmtui-connect. So I reinstall fresh armbian, I can see wlan0 again. I do wifi setting with nmtui-connect but after rebooting I can't connect wifi. I have to redo wifi setting with nmtui-connect, put password again and it adds another wifi. It seems like it can't connect to previous wifi. When I do "nmcli con show", I can see the previous wifi but it is deactive. I searched about it and found wifi mac address randomization issue. So I checked "10-override-random-mac-disable.conf". [connection] wifi.mac-address-randomization=1 [device] wifi.scan-rand-mac-address=no Whenever I redo nmtui-connect, it add file count in "/etc/NetworkManager/system-connections" Is there any way to solve it? Or pwm thing break wifi chips??
  18. Hi. I have been playing with relay and gpio and having a lot of fun. Now I want to use pwm to control a fan. So I edit "/boot/hw_intfc.conf". ..... intfc:pwm2=on intfc:pwm3=on .... And I reboot it. But I can't see "/sys/class/pwm/pwmchip2" and "/sys/class/pwm/pwmchip3" What else should I do??
  19. Hi. I am kind of linux newbie. I want to use serial console with my Rock Pi S thru usb otg. I googled and found this from https://gist.github.com/lukicdarkoo/a87f79b1c25cd86bdc47a8784d6eee9c. I tried it but failed. And I found that there was not "sunxi_usb_duc" directory. Any advice would be apreciated. =============================== ok, I just found that these are for orange pi. Any guide for rock pi s? =============================== After install new image, now I can use serial console with usb otg.
×
×
  • Create New...