Jump to content

Search the Community

Showing results for tags 'pine64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • 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
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Skype


Github


Location


Interests

  1. I've been having a recent issue over the last couple months where my ArmbianEvn.txt file is being overwritten thus causing Helios to hang in the boot process. Using some samples i've found on these forums, I was able to re-create my file and get the Helios back up and running and have since stored a copy so that when it happens, I can just copy and paste and back up running in no time. To date, i've had this happen to me 4 times. I'm not worried about having go through this at this point in time, but I was curious if anyone else has seen this issue or not? I've saved a couple samples of what was written into the ArmbianEnv.txt file: /var/log/armbian-hardware-monitor.log { rotate 12 weekly compress missi /var/log/alternatives.log { monthly rotate 12 compress delaycompress missingok notifempty create 644 root root } I'm running Buster 5.10.21. I have 5-14TB EXOS drives in Raid 6 and have OMV as the only thing installed.
  2. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.
  3. Hello, I have a Pine64 board and recently added an audio POT with the pcm5102a chipset. It is rather difficult to get the board working/recognized. I found info on the forum saying one has to do stuff with the overlay system but only for other boards than the Pine64 and I can't get it right. aplay -l: root@pine64:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sun50ia64hdmi [sun50i-a64-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 I have edited the dtc tree and activated i2s@1c22000: i2s@1c22000 { #sound-dai-cells = <0x00>; compatible = "allwinner,sun50i-a64-i2s\0allwinner,sun8i-h3-i2s"; reg = <0x1c22000 0x400>; interrupts = <0x00 0x0d 0x04>; clocks = <0x02 0x3c 0x02 0x52>; clock-names = "apb\0mod"; resets = <0x02 0x27>; dma-names = "rx\0tx"; dmas = <0x2f 0x03 0x2f 0x03>; status = "okay"; phandle = <0x7c>; }; And the module shows up with lsmod: snd_soc_simple_card 24576 0 snd_soc_simple_card_utils 24576 1 snd_soc_simple_card cpufreq_dt 20480 0 sch_fq_codel 24576 2 snd_soc_pcm5102a 16384 0 But now I am stuck. What do I have to do to get this board working? Thanks in advance for any help. Cheers, Joost
  4. Hello, I am using Allwinner A64 processor for my use case. In that, I want to flash my custom os into emmc memory which is alredy worked in SD card. Currenlty we go thorugh below link: https://wiki.pine64.org/index.php/NOOB#Instructions_to_Flashing_eMMC_Modules we follow "xzcat imagename.img.xz | sudo dd of=/dev/mmcblk1 bs=1M status=progress conv=fsync" this command but we got input/out error while reading memory. Please check below screenshot.
  5. Yesterday, I upgraded my Pine A64 LTS to the 5.10.21 kernel: The system rebooted just fine, though took longer then before. I didn't realize why until today, when I tried to access /media/mmcboot and discovered that it wasn't there. In fact, there is no /dev/mmcblk0p1 device at all. It's bizarre: it boots from the MicroSD, switches to my SSD, but then the MicroSD card device is simply gone when the system is up. I do not see this on two other Pine A64 (not LTS) systems. I was able to mount the microSD card on one of the other systems, and fsck reported everything was fine. I could also see all of the files just fine. The files in /boot had been updated for 5.10.21. But booting up the LTS again resulted in the same thing: it boots, but /dev/mmcblk0p1 does not exist. Any ideas? Thanks!
  6. Dear friends! I have a project, where I needed to use 4 infrared receivers and 2 transmitters connected to GPIO. After a lot of research I realized how to cook all stuffs together: So I have Pine64 A64 512MB cards (not the plus model), running Armbian 20.05.0-trunk.038 nightly, (uname -r: 5.4.18-sunxi64). I needed to freeze upgrades for two reasons: Boot hangs up: The armbian thinks that I have the plus model: on every upgrade I need to replace the "sun50i-a64-pine64-plus.dtb" file with "sun50i-a64-pine64.dtb" at /boot/dtb/allwinner because the non-plus model (512MB) has different ethernet hardware. Missing gpio-ir-recv kernel module from stock Armbian: For transmitting IR signals via GPIO we are using gpio-ir-tx kernel module already located in stock armbian, but for receiving IR signals via GPIO we need the gpio-ir-recv kernel module. So I have downloaded this file from the official armbian source at github and recompiled all kernel modules to get only this gpio-ir-recv.ko kernel module file.... (it took a while) So to activate those kernel modules I needed to create a Custom Device Tree Overlay (here is how to activate it). Here is the content of my custom dt overlay, but if you want to modify GPIO pin numbers, you need to experiment which pin is interrupt enabled and not used for other stuff... +1 good advice ---> If you want to send and receive custom IR protocol, it's better to use the ir-ctl program than lirc. /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-a64"; fragment@0 { target = <&pio>; __overlay__ { ir_rx1_pins: ir-rx1-pins { pins = "PH6"; function = "gpio_in"; }; ir_rx2_pins: ir-rx2-pins { pins = "PH7"; function = "gpio_in"; }; ir_rx3_pins: ir-rx3-pins { pins = "PH8"; function = "gpio_in"; }; ir_rx4_pins: ir-rx4-pins { pins = "PH9"; function = "gpio_in"; }; ir_tx1_pins: ir-tx1-pins { pins = "PH5"; function = "gpio_out"; }; ir_tx2_pins: ir-tx2-pins { pins = "PD0"; function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio_ir_rx1: gpio-ir-receiver-1 { compatible = "gpio-ir-receiver"; pinctrl-names = "default"; pinctrl-0 = <&ir_rx1_pins>; gpios = <&pio 7 6 1>; /* PH6 */ status = "okay"; }; gpio_ir_rx2: gpio-ir-receiver-2 { compatible = "gpio-ir-receiver"; pinctrl-names = "default"; pinctrl-0 = <&ir_rx2_pins>; gpios = <&pio 7 7 1>; /* PH7 */ status = "okay"; }; gpio_ir_rx3: gpio-ir-receiver-3 { compatible = "gpio-ir-receiver"; pinctrl-names = "default"; pinctrl-0 = <&ir_rx3_pins>; gpios = <&pio 7 8 1>; /* PH8 */ status = "okay"; }; gpio_ir_rx4: gpio-ir-receiver-4 { compatible = "gpio-ir-receiver"; pinctrl-names = "default"; pinctrl-0 = <&ir_rx4_pins>; gpios = <&pio 7 9 1>; /* PH9 */ status = "okay"; }; gpio_ir_tx1: gpio-ir-transmitter-1 { compatible = "gpio-ir-tx"; pinctrl-names = "default"; pinctrl-0 = <&ir_tx1_pins>; gpios = <&pio 7 5 0>; /* PH5 */ status = "okay"; }; gpio_ir_tx2: gpio-ir-transmitter-2 { compatible = "gpio-ir-tx"; pinctrl-names = "default"; pinctrl-0 = <&ir_tx2_pins>; gpios = <&pio 3 0 0>; /* PD0 */ status = "okay"; }; }; }; };
  7. Hi, I brought new pine64 board and installing OS in SD card. This OS considering kernel 5.10.34 and now I want to modify some of the kernel features. For that, please guide me how to download kernel source and rebuild it for pine64.
  8. I have looked up relevant information on Google. Since 5.6, pine a64 already supports dsi in the kernel mainline.And the Feiyang FY07024DI26A30-D 7inch MIPI-DSI LCD Panel driver and dts already released. But the 7inch lcd above is a video mode panel.I can not found any information about the command mode panel. Is pine a64 mipi-dsi supports command mode from the kernel mainline? Any help is appreciated!!
  9. Hi, Just want to check what the recommended approach is with today's dist-upgrade. I noticed that armbian-bsp-cli-pine64 was held back, so tried a manual install to see what the problem was. Seems like apt wants to remove linux-focal-root-current-pine64 to upgrade armbian-bsp-cli-pine64. Is this a temporary dependency issue? Obviously not performing the upgrade unless informed of the correct approach. BR.
  10. Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at http://linux-sunxi.org/Linux_mainlining_effort still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if a working mainline kernel with DSI for the Pine 64 is starting to look like a possibility and if it might be possible to include in an armbian build. I might be able to do some testing of anyone can guide me in making a build with the necessary patches.
  11. Hi all, I hope someone can help me with an annoying but not pressing eMMC boot problem. Recently I bought myself a Pin64 H64 3GB SBC and an 32GB eMMC module (actually ordered a 16GB but got a 32GB :-) ) I have a Waveshare 7" TFT touchscreen attached. SBC and Screen are powered either a 5V/3A PSU or a batterypack. Now the board boots fine and fast! from a Samsung EVO sd card .. no problems there, but I cannot get the board to boot from the eMMC module. What I have done so far: 1) Flash an Armbian Buster image to the eMMC (using a USB_eMMC converter) with Etcher on Linux Mint... Boot the board from eMMC WITHOUT sd card installed. The system hangs when the kernel is started.. see attached picture and u-boot output. 2) Wipe the whole eMMC clean, format as ext4. Install it on the board, insert sd card .. boot the board.. OK.. try 'nand-sata-install' from cli or armbian-config->system->install ... both methods just hang instantly. Apart from these boot attempts I tried to access the (ext4 formatted) eMMC module after bootup from sd. But I do not see the device in the 'mount' output or /dev/disk/by-uuid listing. Is there anything else I can verify/try ? The eMMC module 'seems' to be functioning fine in the USB_eMMC converter ? Best regards and a big thank you to the dev team for Armbian.. it's running very swiftly ! Well worth my (first) donation :-) Dirk, Netherlands Armbian_boot_eMMC.txt
  12. For PINE A64 with Ubuntu Focal (stable and nightly) with a 5 MP camera, the documentation states to add camera_type=s5k4ec to /boot/armbianEnv.txt and reboot. After rebooting, the kernel module is not available. modinfo s5k4ec returns: modinfo: ERROR: Module s5k4ec not found. The file /boot/config-5.9.8-sunxi64 shows that only camera sensors OV2640 and MT9V011 are available and CONFIG_VIDEO_S5K4ECGX is not set. Is this an issue with the build?
  13. I am using Armbian Buster on Pine64-LTS units. I recently upgraded version 19.11.3 to 20.02.1 and since having problems with high kworker load and strange warning in dmesg output: [ 7.734729] ------------[ cut here ]------------ [ 7.737084] WARNING: CPU: 1 PID: 30 at drivers/clocksource/arm_arch_timer.c:360 sun50i_a64_read_cntpct_el0+0x24/0x30 [ 7.738928] Modules linked in: cpufreq_dt realtek axp20x_usb_power industrialio pinctrl_axp209 dw_hdmi_cec lima dw_hdmi_i2s_audio gpu_sched dwmac_sun8i mdio_mux [ 7.741485] CPU: 1 PID: 30 Comm: kworker/1:1 Not tainted 5.4.20-sunxi64 #20.02.1 [ 7.743435] Hardware name: Pine64 LTS (DT) [ 7.745514] Workqueue: events dbs_work_handler [ 7.747504] pstate: 80000005 (Nzcv daif -PAN -UAO) [ 7.749508] pc : sun50i_a64_read_cntpct_el0+0x24/0x30 [ 7.751489] lr : arch_counter_get_cntpct_stable+0x38/0x78 [ 7.753420] sp : ffff8000110739c0 [ 7.755295] x29: ffff8000110739c0 x28: ffff0000721e6200 [ 7.757379] x27: ffff00007246a200 x26: ffff000077b77098 [ 7.759351] x25: 0000000000000000 x24: 00000000ffffffff [ 7.761348] x23: 0000000000000001 x22: ffff800011073b10 [ 7.763352] hrtimer: interrupt took 26239875 ns [ 7.765224] x21: 0000000000000000 x20: 0000000000000018 [ 7.767278] x19: ffff800010f4f000 x18: 0000000000000001 [ 7.769323] x17: 0000000000000018 x16: 0000000000000002 [ 7.771285] x15: 0000000000000001 x14: 0000000000000001 [ 7.773271] x13: 0000000000000005 x12: 0000000000000021 [ 7.775229] x11: 0000000000000005 x10: 00000000bcd3d800 [ 7.777217] x9 : 0000000000000004 x8 : 0000000000000004 [ 7.779167] x7 : ffff800010f1b5a0 x6 : 00000000112a8800 [ 7.781121] x5 : 0000000000000010 x4 : 000000000000ffff [ 7.783220] x3 : 0000000000000050 x2 : 000000001ad70336 [ 7.785255] x1 : 0000000000000000 x0 : 000000001ad7033c [ 7.787272] Call trace: [ 7.789327] sun50i_a64_read_cntpct_el0+0x24/0x30 [ 7.791318] __delay+0x20/0xa0 [ 7.793261] __udelay+0x28/0x30 [ 7.795273] ccu_mux_notifier_cb+0x5c/0x90 [ 7.797319] notifier_call_chain+0x54/0x90 [ 7.799359] __srcu_notifier_call_chain+0x54/0x90 [ 7.801372] srcu_notifier_call_chain+0x14/0x20 [ 7.803396] __clk_notify+0x88/0xc8 [ 7.805373] clk_propagate_rate_change+0xb8/0xd0 [ 7.807431] clk_core_set_rate_nolock+0x114/0x1b8 [ 7.809441] clk_set_rate+0x34/0xa0 [ 7.811426] dev_pm_opp_set_rate+0x260/0x498 [ 7.813493] set_target+0x3c/0x80 [cpufreq_dt] [ 7.815441] __cpufreq_driver_target+0x18c/0x580 [ 7.817405] od_dbs_update+0x138/0x190 [ 7.819404] dbs_work_handler+0x3c/0x70 [ 7.821455] process_one_work+0x1ec/0x370 [ 7.823545] worker_thread+0x4c/0x4f8 [ 7.825518] kthread+0x120/0x128 [ 7.827490] ret_from_fork+0x10/0x18 [ 7.829444] ---[ end trace 869ed0a5cc6097b4 ]--- I have traced the high kworker load back to the cpufreq-dt module. When unloading this module the high kworker load stops and system is usable again. As a workaround turning off ondemand governor and selecting performance governor looked like it did the job. But on other units with an X graphics desktop i get a much higher kworker load and the system becomes unusable (slow). The only thing that works all the time is unloading the cpufreq-dt module.
  14. 5.10.4-sunxi64 pine64 board with goodix 7" mipi-dsi LCD touchscreen. The LCD output is working fine across reboots after enabling the dt overlay using armbian-config. For the touchscreen, I have added "goodix" to /etc/modules and the digitizer works fine from all cold boots: ~$ dmesg | grep -i goodix [ 5.836601] Goodix-TS 1-005d: supply VDDIO not found, using dummy regulator [ 5.843605] Goodix-TS 1-005d: ID k}\xfa, version: 7b6f [ 5.866815] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input5 but a reboot leads to either: [ 5.856172] Goodix-TS 1-005d: supply VDDIO not found, using dummy regulator [ 5.856668] Goodix-TS 1-005d: i2c test failed attempt 1: -6 [ 5.886780] Goodix-TS 1-005d: ID k}\xfa, version: 7b6f [ 5.909817] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input5 and the screen works or: $ dmesg | grep -i goodix [ 5.862909] Goodix-TS 1-005d: supply VDDIO not found, using dummy regulator [ 5.864033] Goodix-TS 1-005d: i2c test failed attempt 1: -6 [ 5.889397] Goodix-TS 1-005d: i2c test failed attempt 2: -6 [ 5.925072] Goodix-TS 1-005d: I2C communication failure: -6 a double reboot works. It looks like the i2c bus is not being completely reset in time, but that multiple connection attempts sometimes succeed. Can anyone suggest a workaround, to force a reset, add more i2c test iterations or provide more time to load from reboot? BR.
  15. Hi, Thanks to the hard work of your team, the Pine64-plus touchscreen now works great with the mainline kernel and legacy images are no longer listed in the download options, but it looks like some of the instructions at https://www.armbian.com/pine64/ are still referring to the "old way" of doing things: ie: Pine64’s own LCD with touchscreen support can simply be activated in /boot/armbianEnv.txt by setting pine64_lcd=on and adding gt9xxf_ts to /etc/modules followed by a reboot. The LCD screen is now activated by manipulating the DT overlays, which can even be done from armbian-config - hardware, and the touchscreen module is now called "goodix". Please can someone find the time to update the instructions on the page? BR.
  16. Hi, I just installed the Armbian on a Pine A64+ (Armbian Focal, mainline based kernel 5.9.y). I'm having trouble getting audio from the 3.5mm stereo output. I've tried several things, including a speaker test: speaker-test -c 2 -Dsysdefault:sun50ia64audio I tried editing /etc/asound.conf but it doesn't seem to affect anything. Do changes to that file apply instantly? What can I do to test/diagnose the issue?
  17. I have been running Armbian on a headless Pine64 (the kickstarter one) for quite sometime without any issues. Last week I woke up in the morning and noticed that there had been a power cut. The Pine64 was on again but I couldn't SSH into it. I plugged a monitor and found the system hangs while booting with the following error: Error while loading shared libraries: lib system-shares-241.so: cannot open shared object file: No such file or directory Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 CPU: 1 PID: 1 Comm: init Not tainted 5.4.43-sunxi64 #20.05.2 Hardware name: Pine64+ (DT) Call trace: dump_backtrace+0x0/0x180 show_stack+0x14/0x20 dump_stack+0xb0/0xd8 panic+0x144/0x310 do_exit+0x974/0x9a8 do_group_exit+0x40/0xa8 _arm64_sys_exit_group+0x14/0x18 el0_svc_common.constprop.2+0x88/0x150 el0_svc_handler+0x20/0x80 el0_svc+0x8/0xc SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x0002,24002004 Memory Limit: none I took the card over to my laptop and ran fsck which found no problems. I would rather fix the issue if is possible, but I have no idea how to do it. Is is possible? Or should I just create a new card? Best,
  18. Hi, Armbian gurus. I tried latest Armbian image for PineH64-b. (Armbian_20.11_Pineh64-b_focal_current_5.8.16_desktop) And I surprisingly found there is no audio device when I looked around.( by #aplay -l ) Is this expected for now? My older 5.6 kernel has HDMI device at least. I tried search audio problem around but had no discover so far. Please allow me to confirm with you. I'm looking for a good 5.8 multimedia-capable kernel to merge with my gentoo rootfs. Thank you.
  19. Hi, Thank you all for so much work to fully implement the mainline kernel for the Pine64! So much is now working out-of-the-box with armbian, that there is no need to use the legacy version based on kernel 3.10. The pine64 does have CIR capabilities and the sunxi-cir kernel module is available, but we are still missing DT bindings for the device, although I see that an overlay file is present for the h5: /dts-v1/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <0xffffffff>; status = "okay"; }; }; __fixups__ { ir = "/fragment@0:target:0"; r_ir_rx_pin = "/fragment@0/__overlay__:pinctrl-0:0"; }; }; /tmp/sun50i-h5-cir.dtbs (END) I would be very happy to try to implement and test this, if anyone can suggest changes to the overlay code, to shoehorn it into the pine64-plus DT. Update: I did try the obvious, simple approach of changing the compatible line to compatible = "allwinner,sun50i-a64" , recompiling and changing the filename to /boot/overlay-user/sun50i-a64-pine64-cir.dtbo but this looks like it messes up the official 7 inch lcd overlay (blank screen) that otherwise loads fine. So looks like it needs more changes. Many thanks in advance for any suggestions! BR.
  20. LCD support does not appear to be working in the latest builds (stable kernel 5.8.6, development kernel 5.9.7) My understanding is that this has been an issue for a while with A64 boards, specifically the Pine64, but that it was working at one time. Here's what I've tried so far: -Followed instructions at https://docs.armbian.com/Hardware_Allwinner/ and added "setenv video-mode sunxi:480x272-24@60,monitor=lcd,hpd=1,edid=1" to boot.cmd and put "saveenv" at the end, re-compiled boot.scr -Did a modprobe of panel-olimex-lcd-olinuxino -Rebooted several times -Ensured that LCD jumper was closed and verified LCD was working with Olimex builds. Screen flickers at startup then stays white. Any thoughts?
  21. Hi! I'm using the Sopine A64 Armbian Buster image version 5.91 in combination with my PineA64-LTS SBC. First off I'd like to say that it runs great, thank you guys very much for providing this fully featured image and thereby keeping this SBC up to date! For the last few weeks I've been trying to get the Pine 64 7" LCD screen to work with it, but so far unfortunately I haven't been able to. What I've tried: Follow instructions to get LCD working as stated on the older brother's PineA64 page: add 'pine64_lcd=on' to /boot/armbianEnv.txt, and add 'gt9xxf_ts' to /etc/modules, then reboot. No luck. Read about the Allwinner Overlays and try to understand how they work. Decompile both 'sun50i-a64-pine64.dtb' and 'sun50i-a64-pine64-lts.dtb' (found in /boot/dtb/allwinner/), search for 'lcd' in both .dts files and compare. I noticed some differences in addresses but wouldn't know which of those are correct or incorrect. Add the decompiled 'sun50i-a64-pine64.dts' as user-overlay through 'sudo armbian-add-overlay sun50i-a64-pine64.dts', then reboot. System still booted, but no working LCD screen. and that's about how far my knowledge goes, without really just going into the realm of trying random things Is there anyone that managed to got the aforementioned combination of hardware to work? Or anyone that could give me any pointers on what to try next? I'm very much willing to put time and effort into this, I just don't know where to start/what to try next. Thanks a lot in advance for any assistance.
  22. Hi, I try to enable sound on headphone jack with pine64+ but i could not Alsa says "no sound found" at dmesg Could anyone help me? Thank you root@pine64:~# dmesg|grep -i sound [ 2.686397] No soundcards found. [ 6.323086] input: sun50i-a64-audio Headset Jack as /devices/platform/sound/sound/card0/input5 root@pine64:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sun50ia64hdmi [sun50i-a64-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Alsamixer Settings;
  23. Ethernet does not appear to be working on the latest versions of Armbian with pine64 512mb model (has only 10/100MBps Eth) Current Version: ARMBIAN 5.83 stable Debian GNU/Linux 9 (stretch) 4.19.38-sunxi64 - I have tried 2 boards in case its a hardware issue, no go. - Ethernet works with Armbian Xenial (3.10 legacy kernel) - The network port shows activity when initially powering up, but when it begins boot lights go out. - I have tried many older and newer kernels, including the new 5.1.0 dev kernel, with no luck. - Eth0 show up with command "ip address" but not with "ifconfig" - When I try running "sudo ethtool eth0" I get errors with "Device or resource busy"
  24. Hi. I am getting a kernel Oops in the Pine64+ . . . .see below. Kernel is 5.8.13-sunxi64. It was installed after a recent update. I would like to drop back to the previous kernel if possible. Does this seem like a reasonable search term for a suitable kernel? Any ideas on searching and installing a previous kernel appreciated. sudo apt-cache search kernel 5.8* | grep sunxi64 linux-dtb-current-sunxi64 - Linux DTB, version 5.8.13-sunxi64 linux-dtb-dev-sunxi64 - Linux DTB, version 5.9.0-rc7-sunxi64 linux-dtb-legacy-sunxi64 - Linux DTB, version 5.4.62-sunxi64 linux-headers-current-sunxi64 - Linux kernel headers for 5.8.13-sunxi64 on arm64 linux-headers-dev-sunxi64 - Linux kernel headers for 5.9.0-rc7-sunxi64 on arm64 linux-headers-legacy-sunxi64 - Linux kernel headers for 5.4.62-sunxi64 on arm64 linux-image-current-sunxi64 - Linux kernel, version 5.8.13-sunxi64 linux-image-dev-sunxi64 - Linux kernel, version 5.9.0-rc7-sunxi64 linux-image-legacy-sunxi64 - Linux kernel, version 5.4.62-sunxi64 linux-source-5.4.58-legacy-sunxi64 - This package provides the source code for the Linux kernel 5.4.58 linux-source-5.4.61-legacy-sunxi64 - This package provides the source code for the Linux kernel 5.4.61 [ 23.475944] ------------[ cut here ]------------ [ 23.478571] WARNING: CPU: 3 PID: 171 at drivers/clocksource/arm_arch_timer.c:364 sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.480502] Modules linked in: cpufreq_dt realtek dwmac_sun8i pinctrl_axp209 mdio_mux i2c_mv64xxx [ 23.483003] CPU: 3 PID: 171 Comm: kworker/3:3 Not tainted 5.8.13-sunxi64 #20.08.7 [ 23.484968] Hardware name: Pine64+ (DT) [ 23.487226] Workqueue: events dbs_work_handler [ 23.489416] pstate: 80000005 (Nzcv daif -PAN -UAO BTYPE=--) [ 23.491571] pc : sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.493700] lr : arch_counter_get_cntpct_stable+0x3c/0x80 [ 23.495784] sp : ffff800011afb9c0 [ 23.497758] x29: ffff800011afb9c0 x28: ffff0000743a9a00 [ 23.499861] x27: ffff0000713ed600 x26: ffff0000743a9c68 [ 23.501992] x25: ffff000072e38228 x24: 0000000000000000 [ 23.504054] x23: 0000000000000001 x22: ffff800011afbb10 [ 23.506137] x21: 0000000000000000 x20: 0000000000000018 [ 23.508260] x19: ffff8000113dd000 [ 23.510328] hrtimer: interrupt took 27046125 ns [ 23.512242] x18: ffff800011afb9b8 [ 23.514290] x17: 0000000000000004 x16: 0000000000000001 [ 23.516399] x15: 0000000000000018 x14: 0000000000000002 [ 23.518455] x13: 0000000000000001 x12: 0000000000000001 [ 23.520483] x11: 0000000000000005 x10: 0000000000000021 [ 23.522575] x9 : 0000000044aa2000 x8 : ffff8000113aaf98 [ 23.524628] x7 : 0000000000000000 x6 : 00000000112a8800 [ 23.526731] x5 : 0000000000000010 x4 : 0000000000000012 [ 23.528810] x3 : 0000000000000050 x2 : 000000002ec5d477 [ 23.530879] x1 : 0000000000000000 x0 : 000000002ec5d47d [ 23.532925] Call trace: [ 23.535068] sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.537130] __delay+0x24/0xa8 [ 23.539201] __udelay+0x2c/0x38 [ 23.541332] ccu_mux_notifier_cb+0x64/0xa0 [ 23.543415] notifier_call_chain+0x54/0x98 [ 23.545482] __srcu_notifier_call_chain+0x58/0x98 [ 23.547538] srcu_notifier_call_chain+0x18/0x28 [ 23.549615] __clk_notify+0x88/0xd0 [ 23.551707] clk_propagate_rate_change+0xc4/0xd8 [ 23.553808] clk_core_set_rate_nolock+0x114/0x1f8 [ 23.555895] clk_set_rate+0x38/0xa8 [ 23.558113] dev_pm_opp_set_rate+0x264/0x618 [ 23.560250] set_target+0x40/0x88 [cpufreq_dt] [ 23.562349] __cpufreq_driver_target+0x2c4/0x668 [ 23.564464] od_dbs_update+0x140/0x1a0 [ 23.566542] dbs_work_handler+0x40/0x80 [ 23.568628] process_one_work+0x1c8/0x378 [ 23.570711] worker_thread+0x14c/0x4c8 [ 23.572806] kthread+0xf8/0x128 [ 23.574887] ret_from_fork+0x10/0x30 [ 23.576963] ---[ end trace 32a37354cad394e6 ]--- [ 23.735669] sun8i-ce 1c15000.crypto: Set mod clock to 300000000 (300 Mhz) from 24000000 (24 Mhz) [ 23.735961] sun8i-ce 1c15000.crypto: will run requests pump with realtime priority
  25. Hello. I'm a bit confused, i have a PINE64 board ("PINE A64+", 2GB mem.) (this one : https://www.pine64.org/?product=sopine-a64-baseboard-combo) I installed some years ago ARMBIAN on it - everything is running fine. But i'm still on kernel 3.X something : ``` uname -a Linux pine64 3.10.107-pine64 #2 SMP PREEMPT Fri Feb 8 10:23:10 CET 2019 aarch64 GNU/Linux cat /etc/armbian.txt ------------------------------------------------------------------------------- Title: Armbian 5.73 Pine64 Debian jessie default Kernel: Linux 3.10.107 Build date: 28.01.2019 ... ``` Of course my whole system is up-to-date and has been switched from `jessie` to `stretch` and recently to `buster` (= apt-get update, upgrade, dist-upgrade done). What am i supposed to do to have a newer kernel (i would need 4.x in order to be able to use `overlay2` docker storage engine) ? Thanks in advance for any help.
×
×
  • Create New...