Jump to content

Search the Community

Showing results for tags 'odroidhc4'.

  • 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
    • Orange Pi 5
  • 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

  1. Hey, I have a very similar problem here to this and this thread. I rebooted as the HC4 was already bugging me for a while to reboot on the motd (unattended-upgrades). Since the reboot, /dev/sdb is gone. It's a new Samsung SSD 870 EVO as well as in the other thread. The other (still running) one is a new Crucial MX500. I tried several Armbian kernels but no change. I went back to 5.10.57-meson64. There are no obviously burnt components on the device. There seem quite a few people with this problem. Any ideas? Thanks a lot! P.S. TP10 and TP11 are at 12V.
  2. The zfs-dkms included in Armbian_22.11.1_Odroidhc4_jammy in version 2.1.4 is to old for 5.19.17 kernel. It should be 2.1.6 like in Armbian_22.08.7. Loading new zfs-2.1.4 DKMS files... Building for 5.19.17-meson64 Building initial module for 5.19.17-meson64 configure: error: *** None of the expected "blk_queue_discard" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 http://paste.debian.net/1267188/
  3. Hi everyone! For about a week now, I have been using armbian 22.11.1 on my new Odroid HC4, which is my Nextcloud server. As alway, armbian is rock solid πŸ˜‰ I have just a little question: Can one modify the information presented in htop? I'd like to have "CPU temperature" and "TX today" (meaning sent bytes) showing. The welcome screen already shows "CPU temperature" and "RX today". I know that the CPU temperature can be read here /etc/armbianmonitor/datasources/soctemp and but I can't find it in the htop-configuration under "available meters".
  4. I'm trying to complete the installation of Armbian onto the HC4 (HC4-P if that changes anything). With a fresh SD card I run sudo dd if=Armbian_22.11.1_Odroidhc4_bullseye_current_5.19.17.img of=/dev/sdb status=progress plug in the card to the board, plug in the ethernet cable, hold down the boot switch, and plug it into power. It all seems to run correctly: I can SSH into the board and I complete the initial steps to set-up the installation (root pass, default shell, username, real name, and locale). However it does not seem as I can access the SPI FLASH device. Running the following commands from the HC4 page do not work as there are no mtd devices. root@odroidhc4:~# ls -ltr /dev/mtd* ls: cannot access '/dev/mtd*': No such file or directory Here's a paste of the files available under /dev: https://paste.tildeverse.org/?aa94ecb514ce9e50#E5qD2kbTFiQzaHRrgnBLfMw8PMfspfVsCFrxhPATYDyi
  5. Hi there, I have new HC4 (like 6 moths old) and since beginning I am struggling with reboot. I have latest Armbian Bullseye, and every time I make reboot, I need to power cycle to get it up. Is there any solution to that problem? I tried HK images, and they are rebooting but they are old so I want to be a bit modern but that is really annoying issue. Any help please? And Merry Christmas guys, thanks for the awesome distro even with that stupid problem.
  6. Running a home NAS using Armbian/meson bullseye and openmediavault. After apt upgrade today, my SATA disks are no longer spinning up or showing up in "fdisk -l". The system is on an SD card and still boots fine. This is what I'm seeing: [ 2.270633] scsi host0: ahci [ 2.272861] scsi host1: ahci [ 2.273074] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 27 [ 2.273090] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 27 ... [ 2.584971] ata1: SATA link down (SStatus 0 SControl 300) [ 2.896948] ata2: SATA link down (SStatus 0 SControl 300) Both disks work fine in another system. I have tried to upgrade the firmware, no change. Moved to nightly and booted into linux-image-edge-meson64 (6.1.0), same issue. Next, I tried booting into kernel 5.19.17-meson64, but the problem persists. I wonder what has happened here? Could it be a userspace problem (since I didn't downgrade userspace here, only the kernel)? Any hints very much welcome!
  7. As the original thread, which was closed by moderator for obvious reason, did attract attention of few peoples having the same problem as me, it would be a waste not to follow up on this, I think. Let me sum up: I have two HC4, one bought in 8.2021 and other one 11.2022, both have two SSDs each. The older one after a kernel upgrade didn't see a second disk any more. I've just tried few kernels I could find with the following results: OK: Linux odroidhc4 5.12.10-meson64 #21.05.4 SMP PREEMPT Wed Jun 16 08:19:35 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux OK: Linux odroidhc4 5.13.12-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:35:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Not OK:Linux odroidhc4 5.15.4-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:46:10 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Couldn't find any kernel between 5.13.12 and 5.15.4, so it's not clear which is exact the version where the problem started. Here is what I found in /var/log/syslog: Nov 22 14:40:46 odroidhc4 kernel: [ 2.355049] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.355060] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.358363] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.564017] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.830521] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830799] ata1.00: FORCE: horkage modified (noncq) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830854] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.830860] ata1.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.830865] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (not used) Nov 22 14:40:46 odroidhc4 kernel: [ 2.832778] ata1.00: Features: Trust Dev-Sleep Nov 22 14:40:46 odroidhc4 kernel: [ 2.833128] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.835140] ata1.00: configured for UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835408] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 2B6Q PQ: 0 ANSI: 5 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835890] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.836066] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Nov 22 14:40:46 odroidhc4 kernel: [ 2.836102] sd 0:0:0:0: [sda] Write Protect is off Nov 22 14:40:46 odroidhc4 kernel: [ 2.836108] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 22 14:40:46 odroidhc4 kernel: [ 2.836159] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 22 14:40:46 odroidhc4 kernel: [ 2.850916] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.872432] sda: sda1 sda9 Nov 22 14:40:46 odroidhc4 kernel: [ 2.872842] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.886688] sd 0:0:0:0: [sda] Attached SCSI disk Nov 22 14:40:46 odroidhc4 kernel: [ 3.148738] ata2: SATA link down (SStatus 0 SControl 300) The newer HC4 doesn't show this problem which leads me to the conclusion: their hardware (firmware?) must differ. Asked about it on the HardKernel Forum, didn't get a clear answer (yet?). I don't know how to proceed i.e. where to look for further help. Any idea anyone? I'm to old for an advanced GIT class πŸ˜‰ Thanks for your time. Chris
  8. Some time ago a I was desperate to have ZFS on an Odroid HC4 and after some trying found Armbian 21.05.8 Buster with Linux 5.10.57-meson64 on which I could compile ZFS module. Then I moved everything from the SD card to filesystems in a ZFS pool. It boots from SD card, though. And has been working fine for several months. Recently I bought another HC4 and took the current Armbian image for it: Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 Everything works fine. Tried this image on the older HC4 and it doesn't see the second SSD. In the syslog I found this message: ata1: SATA link down (SStatus 0 SControl 300) Is it a firmware problem? Googling hasn't help. Any idea anyone? Thanks for your time. Chris BTW Does anybody know how to disable the "Clear Screen" after the "Starting kernel" message? I would like to see what u-boot has to tell me, especially if I have some problems.
  9. Hi, i have armbian bullseye (headless) installed on my odroid-hc4. petitboot is disabled. The boot-partition lies on a sd-card while the root-partion is on a ssd. this configuration worked fine. After upgrading to armbian bullseye 22.11 the boot process stucks in initramfs cause the root file-system is not found anymore (ALERT! UUID=xxx does not exist. Dropping to a shell. The sd-card with the boot partition as well as the ssd with the root-partition can be mounted on another PC and seem to be flawless. the UUID shown in fstab and initramfs are identical. In initramfs ls /dev/sd* shows no devices while ls /dev/mm* shows the sdcard (mmcblk01...). I don't really know how the boot process works on an arm-system. What steps can I do to narrow down the problem. Thanks in advance. Hardware: odroid-hc4, samsung 870 EVO 1TB (sda), WD60EFZX (sdb), BS: armbian-bullseye with OMV 6.0.46-5 fs: ext4 no raid
  10. Hello, Bluetooth stopped working in kernel 5.19.17-meson64 #22.11.1 root@nextcloudpi:~# hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:14 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:3 errors:2 root@nextcloudpi:~# hcitool dev Devices: root@nextcloudpi:~# dmesg | grep Bluetooth [ 10.005353] Bluetooth: Core ver 2.22 [ 10.010561] Bluetooth: HCI device and connection manager initialized [ 10.010582] Bluetooth: HCI socket layer initialized [ 10.010589] Bluetooth: L2CAP socket layer initialized [ 10.010621] Bluetooth: SCO socket layer initialized [ 10.273422] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [ 11.647454] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.647474] Bluetooth: BNEP filters: protocol multicast [ 11.647489] Bluetooth: BNEP socket layer initialized [ 15.326913] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [ 15.327136] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [ 15.327149] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [ 15.327153] Bluetooth: hci0: HCI Set Event Filter command not supported. [ 17.341929] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42900.593231] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42900.922097] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42900.923021] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42900.923040] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42900.923044] Bluetooth: hci0: HCI Set Event Filter command not supported. [42902.934227] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42905.073243] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42905.661928] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42905.662099] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42905.662108] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42905.662112] Bluetooth: hci0: HCI Set Event Filter command not supported.
  11. Hi, I'm trying to use ZFS but the kernel I'd like to use doesn't support loadable modules. The version is 22.08.4 at the moment (5.10.147) Can I use zfs-dkms on linux-image-current-meson64? And I'm curious why loadable modules are not supported by default for linux-image-current-meson64, is it same with every model? or probably Odroid-HC4 is one of the models in which loadable modules are not build by default? System diagnosis information: https://paste.armbian.com/ezisijedob Thank you, Gunwoo Gim
  12. Long story short: I used for about one year an odroid HC4 as NFS server and worked fine. Now I would add a player service for it. It mounts an HDMI port, so I tried to plug in the cable and it worked. I were able to see the video output but with no sound. I found there is no detected hdmi card: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ODROIDHC4 [ODROID-HC4], device 0: fe.dai-link-0 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 1: fe.dai-link-1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 2: fe.dai-link-2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 tried again after # alsactl init alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "axg-sound-card" "" "" "" "" Hardware is initialized using a generic method (alsactl -U init provides no error) The modules side looks fine to me (it was the same on 5.10.144, I tried moving to 5.19.10 with no result): # lsmod | grep snd snd_soc_hdmi_codec 24576 1 snd_soc_meson_axg_sound_card 16384 0 snd_soc_meson_card_utils 16384 1 snd_soc_meson_axg_sound_card snd_soc_meson_g12a_tohdmitx 20480 1 snd_soc_meson_codec_glue 16384 1 snd_soc_meson_g12a_tohdmitx snd_soc_meson_axg_tdmout 24576 1 snd_soc_meson_axg_frddr 36864 3 snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout snd_soc_core 245760 10 snd_soc_meson_axg_tdm_formatter,snd_soc_meson_axg_sound_card,snd_soc_hdmi_codec,snd_soc_meson_g12a_tohdmitx,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_fifo,snd_soc_meson_axg_tdmout,snd_soc_meson_axg_frddr,snd_soc_meson_card_utils,snd_soc_meson_codec_glue snd_compress 24576 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 20480 1 snd_soc_core snd_pcm 131072 7 snd_soc_hdmi_codec,snd_compress,snd_soc_meson_axg_tdm_interface,snd_soc_core,snd_soc_meson_axg_fifo,snd_soc_meson_codec_glue,snd_pcm_dmaengine snd_timer 40960 1 snd_pcm snd 90112 5 snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm soundcore 16384 1 snd I tried digging in dmesg and the only related issue that came out is:p panfrost ffe40000.gpu: error -ENODEV: dev_pm_opp_set_regulators: no regulator (mali) found but I wouldn't say that to be the source of the sound problem. There are errors but I don't feel the solution behind any of them. Do you? Kernel, modules, drive, dtb... where else could the lack of sound come from? Any suggestion?
  13. ChrisO

    ZFS again

    Hi I was using: Title: Armbian 21.08.5 Odroidhc4 Debian buster legacy Then something bad pushed me to run apt update/upgrade No ZFS anymore. Installed 22.08.2, but, when tried to install kernel headers using armbian-config, result: "grep: invalid max count" message. What is the current correct way to install Armbian with ZFS? Thanks ChrisO
  14. Hello, After a firmware update today I got a problem with Wireguard on my Odroid-hc4. I got that when checking ufw status, sudo ufw status verbose ERROR: problem running iptables: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.10.123-meson64 iptables v1.8.7 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. How to fix that? Laurent
  15. Dear All, I am using Jammy with kernel 5.18 on hold, but yesterday I noticed very important updates that were kept back because the kernel is locked, such s: armbian-bsp-cli-odroidhca armbian-firmware linux-dtb-edge-meson64 linux-headers-edge-meson64 linux-image-edge-meson64 linux-u-boot-odroidhc4-edge I wonder if is worth to update or if I had better to stick with my current setup, where my main feature β€” ZFS β€” is working. What's your recommendations? Thanks in advance! F.
  16. Is there any way to enable Wake on Lan? As far as I know the Odroid-HC4 Supports WoL but I can't get it to work
  17. I do not have petitboot installed. I ran the Armbian buster with OMV5 for over a year. I decided to make a clean install and booted Armbian bullseye 11. I changed hostname and rebooted (curiously reboot doesn't reboot the hc4, why?). I used armbian-config to install OMV. Installation completed, brought me back to armbian-config and prompted to reboot. I hit reboot (then was forced to power cycle as hc4 won't come back to life after a soft-boot?). Note that I was able to power cycle and get a good boot BEFORE omv installed but not after. At that point Odroid hc4 never comes back online. I've been through this 3 times today. I gave it as long as 30 minutes but doesn't respond even to pings. It does get the blue led blinking denoting successful kernel load. How do I get past this?! (I've tried with and without armbian-config's update upgrade with firmware, the full firmware option etc) Nothing is working. Any and all help is greatly appreciated.
  18. I don't understand why I can't update to 5.19. I just updated to various user-space Debian 11.5 packages, but I can't see any newer kernels. root@odo:/boot# apt policy linux-image-edge-meson64 linux-image-edge-meson64: Installed: 22.05.1 Candidate: 22.05.1 Version table: *** 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0046 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0045 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0040 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0035 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0034 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0031 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0029 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0027 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0025 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0023 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0021 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.115 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.108 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.101 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages root@odo:/boot# apt policy linux-u-boot-odroidhc4-edge linux-u-boot-odroidhc4-edge: Installed: 22.05.3 Candidate: 22.05.3 Version table: *** 22.05.3 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.05.2 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.8 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.6 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages I'm looking at https://mirrors.xtom.de/armbian/pool/main/l/ for example and I can see items such as https://mirrors.xtom.de/armbian/pool/main/l/linux-5.19.5-meson64/. How do I get my apt to see them?
  19. Is there a command to load this splash screen that shows when I open a new session? Also is there a way I can show the storage availability/temperature for the second hard drive? I think the current setting only shows information for the drive on /sda but i need info for drive on /sdb
  20. Hi ! I recently got an Odroid HC4. I am following the guide (https://www.armbian.com/odroid-hc4/) to install Armbian 22.05 Bullseye on it. But I have some problems and I dont know how to do.. So my problems is actually this part : "Create a file in /etc/fancontrol with the following content: INTERVAL=10 DEVPATH=hwmon0=devices/virtual/thermal/thermal_zone0 hwmon2=devices/platform/pwm-fan DEVNAME=hwmon0=cpu_thermal hwmon2=pwmfan FCTEMPS=hwmon2/pwm1=hwmon0/temp1_input FCFANS= hwmon2/pwm1=hwmon2/fan1_input MINTEMP=hwmon2/pwm1=50 MAXTEMP=hwmon2/pwm1=60 MINSTART=hwmon2/pwm1=20 MINSTOP=hwmon2/pwm1=28 MINPWM=hwmon2/pwm1=0 MAXPWM=hwmon2/pwm1=255 followed by: sudo systemctl restart fancontrol" I made this file (see screenshot). Then I run the command, and I got an error : And this I was is shown when I type the command "systemctl status fancontrol;service" :
  21. I see a lot of tutorials online and they all have seems to have different ways of going about making a share and it seems most of them are logged into a user as opposed to root. I'm logged in to root through ssh so that might the the cause of many of my issues I believe. I did a simple apt install samba and it seems to be running fine. I see other tutorials recommending you install "smbclient" and "cifs-utils", is that necessary? Some of the tutorials also say to add user groups and to add settings to the firewall. I'm just using 1 user and don't have any firewalls installed, unless armbian comes with one by default. I think my my service is running fine though. When I run 'sudo systemctl status smbd' it says "active (running)" in green. I can open the sbc on the network and view the shared folders, I cannot access them however. Also the sbc does not show up when I click network on windows explorer, it will however open if i type in the ip/name manually on run or the open bar, not sure if that matters. I did create a new user and gave it a samba password (mouse) I did chown the folder to the user and chmod 777. Here's the what comes up when i ls -al in the root directory where the folder i'm trying to share is located: drwxrwxrwx 3 mouse root 4096 Jun 5 09:25 testfolder Here's my smb.conf [testfolder] comment = Test Folder path = /root/testfolder browseable = yes read only = no writable = yes guest ok = no force user = mouse create mask = 0777 directory mark = 0777 On path I did /root/testfolder instead of /testfolder because I also mounted a hard drive inside that folder. When I tried mapping a drive to fstab using the directory /testfolder , it kept giving me an error about folder not existing or something, but when I typed /root/testfolder , it correctly mounted the drive. I also tried using the /testfolder on the smb config and it doesn't work either. These folders structures are REALLY confusing. When I ls -al in root don't see any folders like mnt var etc I only see the "testfolder" i created and a few folders starting with a period like .bashrc .... Where are the other folders located? in /root/etc ? Here's the error I get when trying to access my folder.
  22. Hi all, we have developed a script to create an SD image for Odroid HC4. With this method you can use Armbian without erase Petitboot partition. https://github.com/TheLillo/generate-image-hc4-armbian
  23. I noticed that TOP an HTOP are in disagreement about many things while my LCD Info panel and TOP are on the same page... TOP OUTPUT top - 23:50:26 up 5:18, 2 users, load average: 1.69, 1.77, 1.72 Tasks: 226 total, 1 running, 225 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.6 us, 0.7 sy, 0.0 ni, 84.5 id, 13.4 wa, 0.1 hi, 0.7 si, 0.0 st MiB Mem : 3785.8 total, 135.1 free, 2551.9 used, 1098.8 buff/cache MiB Swap: 1892.9 total, 1891.4 free, 1.5 used. 1139.1 avail Mem HTOP OUTPUT 1[||||||| 7.9%] Hostname: odroidhc4 2[|||| 4.0%] Tasks: 45, 13 thr; 1 running 3[||| 2.6%] Load average: 1.60 1.65 1.69 4[||| 2.0%] Disk IO: 23.7% read: 0K write: 32K Mem[|||||||||||||||||||673M/3.70G] Network: rx: 5.50MiB/s tx: 115KiB/s (5821/2708 packets) zrm[| 1.16M(5.52M)/1.90G] Uptime: 05:23:36 Swp[| 1.50M/1.85G] Systemd: running (0/353 failed) (0/220 jobs) Who is right?
  24. Ok folks... This very setup was fixed and made working at my job. I tested from the new M$ Terminal while connected to the LAN of my office, extremely satisfied I returned to home and when I connected the HC4 to my router, the "systemd smbd.service" didn't work again (event though at my workplace I rebooted for testing purpose the board several time and Samba had been woking all the time). The Office LAN is most likely managed by a Win Server and is on 192.160.0.X, at home I am connected to a Comcast Cable Router on 10.0.0.X... This the error I get from systemd: Γ— smbd.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2022-06-08 20:48:33 EDT; 19min ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 3650 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Process: 3655 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 3655 (code=exited, status=1/FAILURE) Status: "daemon failed to start: reinit_after_fork() failed" Error: 2 (No such file or directory) CPU: 306ms systemd[1]: Starting Samba SMB Daemon... smbd[3655]: [2022/06/08 20:48:33.962189, 0] ../../source3/lib/util.c:482(reinit_after_fork) smbd[3655]: messaging_reinit() failed: NT_STATUS_OBJECT_NAME_NOT_FOUND smbd[3655]: [2022/06/08 20:48:33.962547, 0] ../../lib/util/become_daemon.c:119(exit_daemon) smbd[3655]: exit_daemon: daemon failed to start: reinit_after_fork() failed, error code 2 systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: smbd.service: Failed with result 'exit-code'. odroidhc4 systemd[1]: Failed to start Samba SMB Daemon My setup doesn't change the default "smbd.conf' but it recalls another configuration with: config file = /etc/samba/smb-local.conf I added that line to the very first section of the default "smbd.conf": [global] config file = /etc/samba/smb-local.conf ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = %h server (Samba, Ubuntu) All my main configurations go under the "smb-local.conf", this is the setup has been taken from my current "OMSC/RPI2" Samba configuration: [global] # If you require a fully custom smb.conf create smb-local.conf instead of editing smb.conf so your # configuration will not be overwritten by samba upgrades. You can use smb.conf as a template by # copying it to smb-local.conf then removing the config file line below in the new file. If you only # need to add some additional shares see smb-shares.conf below for a simpler way to do this. workgroup = YOUR-HOME-CLOUD security=user follow symlinks = yes wide links = no unix extensions = no lock directory = /var/cache/samba load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes log level = 1 map to guest = bad user usershare template share = automount template ############## read raw = Yes write raw = Yes strict locking = no min receivefile size = 16384 use sendfile = true aio read size = 2048 aio write size = 2048 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072 ## FreeBSD Changes ntlm auth = yes server max protocol = SMB3_11 server min protocol = NT1 client max protocol = SMB3_11 client min protocol = NT1 [droid] browsable = no read only = yes valid users = droid path = /home/YOUR-HC4-USER comment = Droid Home Directory [automount template] browseable = yes -valid = no valid users = YOUR-HC4-USER path = %P hide files = /$RECYCLE.BIN/System Volume Information/desktop.ini/thumbs.db/ # Add custom shares in smb-shares.conf instead of editing smb.conf so they will not be # overwritten by samba updates. You can only add new shares to smb-shares.conf, not change # the default shares or global options. If you need full control see smb-local.conf above. include = /etc/samba/smb-shares.conf Users are handled by: include = /etc/samba/smb-shares.conf This is an example how my "/etc/samba/smb-shares.conf" is composed and is taken by my documentation, but matches my current setup: [public] comment =Public Storage path = /srv/samba/public valid users = @users force group = users create mask = 0660 directory mask = 0771 read only = no [MyUSER] browsable = yes read only = no valid users = YOUR-HC4-USER, MyUSER path = /srv/samba/MyUSER comment = MyUSER Folder force group = users locking = no create mask = 0765 directory mask = 0765 Of course if I remove from "smbd.conf" this line: config file = /etc/samba/smb-local.conf The systemd service doesn't fail... But with my configuration "testparm -s" doesn't fail either... $ testparm -s Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed Server role: ROLE_STANDALONE # Global parameters [global] config file = /etc/samba/smb-local.conf log file = /var/log/samba/log.%m logging = file map to guest = Bad User max log size = 1000 obey pam restrictions = Yes pam password change = Yes panic action = /usr/share/samba/panic-action %d passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . passwd program = /usr/bin/passwd %u server role = standalone server server string = %h server (Samba, Ubuntu) unix password sync = Yes usershare allow guests = Yes idmap config * : backend = tdb [printers] browseable = No comment = All Printers create mask = 0700 path = /var/spool/samba printable = Yes [print$] comment = Printer Drivers path = /var/lib/samba/printers Thanks! πŸ™πŸ™πŸ™
  25. Dear Friends, I have been testing Armbian 22.04 Current CLI version and 22.01 Edge Jammy CLI and both does not reboot. When I reboot Armbian the LEDs stop to blinking but I can clearly listen the rust-drives spinning, also the LCD is still active. Initially I though it was because the software that handles the LCD but I made a test without it and it was the same. I also thought that was because the spin drives, but when I did the test I made it without the disks as well, therefore I excluded both cases. Since I didn't read anything about it, I think this issue is affecting just me, any idea where I may look to find out what is preventing the board to reboot properly? Thanks in advance! Freezr
Γ—
Γ—
  • Create New...