Jump to content

Search the Community

Showing results for tags 'odroidm1'.

  • 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

Found 11 results

  1. Hi everyone, New to the forum, so apologies if the questions are answered elsewhere, but please redirect me if they are. I have identified a bug in the `armbian-install` script in the current Bullseye Edge image (Dec 19,2022) that prevents it showing NVMe targets in the installation prompt if they don't have a valid filesystem on them. This appears to have been fixed on the 19th of December in this commit (the grep for filesystems was removed from the lsblk command that returns valid partitions). https://github.com/armbian/build/commit/893ed2347d97af574becf69dee1166a1bf933081#diff-8752ea87e0340f217187b70f7b08735d872a14c0467d02a6285222e594db3299L635-R635 I am not sure if it's a coincidence that these are the same date, but the Bullseye image downloaded today still has the older version of the script that includes the 'grep' for filesystems. I have a workaround for my immediate issue (mkfs.ext4 on the NVMe partition so the installer detects it), but thought this may be impacting other users of Odroid M1 as they are likely installing on the NVMe. If I need to raise this elsewhere, eg. github issue etc. please let me know the process. Thanks!
  2. Trying to interface with a Raspbee II but the uarts dont seem to function, could this be correct?
  3. I try to install the package rtl8812au-dkms and it fails with: CC [M] /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.o /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c: In function ‘rtw_change_ifname’: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:2183:28: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 2183 | _rtw_memcpy(pnetdev->dev_addr, padapter->eeprompriv.mac_addr, ETH_ALEN); | ~~~~~~~^~~~~~~~~~ /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:807:24: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 807 | void _rtw_memcpy(void* dst, const void* src, u32 sz) | ~~~~~~^~~ /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c: In function ‘rtw_random32’: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:2310:16: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration] 2310 | return prandom_u32(); | ^~~~~~~~~~~ | prandom_u32_max cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.o] Error 1 make[1]: *** [Makefile:1992: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-rc5-rk3568-odroid' Same issue, if I try to compile the driver manually: CC [M] /home/astrodroid/rtl8812au/core/efuse/rtw_efuse.o CC [M] /home/astrodroid/rtl8812au/os_dep/osdep_service.o /home/astrodroid/rtl8812au/os_dep/osdep_service.c: In function ‘rtw_random32’: /home/astrodroid/rtl8812au/os_dep/osdep_service.c:2591:16: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration] 2591 | return prandom_u32(); | ^~~~~~~~~~~ | prandom_u32_max cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:250: /home/astrodroid/rtl8812au/os_dep/osdep_service.o] Error 1 make[1]: *** [Makefile:1992: /home/astrodroid/rtl8812au] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-rc5-rk3568-odroid' Which package I missed to be installed, that this function may be available. With the original Odroid M1 Ubuntu LTS 22.04 and Linux 5.19 this package could be installed. Thx
  4. Hello, Some weeks ago, I installed the kinetic version. It was rooted on the nvme drive and was working decently. After some explanations on this forum, I decided to install the LTS version. I burned a new SD card, inserted it and powered on. I was never prompt about where to install the system. After installation, the df command shows that the system is installed on the sd card. I can see nvme partitions in /dev but they aren't mounted. nvme is partitionned in two parts : one for the system, the other one is crypted and dedicated to data. How should I do? Thanks Julien
  5. Hello, Some weeks ago, I installed the "under development" version. File was named Armbian_22.11.0-trunk_Odroidm1_kinetic_edge_6.1.0-rc5.img.xz Now, I see that the "advertised" version is a rolling release armbian 22.11 Jammy. Based on this (https://wiki.ubuntu.com/Releases) page kinetic is an earlier version than jammy. If I scroll down the page ( https://www.armbian.com/odroid-m1/ ) , I see a kinetic rolling weekly release. I suspect that the kinetic is an unstabled release while Jammy 22.11 is. Please can you confirm/explain? If yes, is there a way to "downgrade" to the stable version? Thanks Julien
  6. Hello, If I unplug my M1 for the whole night. When I power up It does not start the first time. It stays stuck on the hardkernel splashScreen. If I power cycle, it starts as it should. I'm booting on the SD card and system is on nvme. System is up-to-date. Do you have any idea of what may happen? Thanks Julien
  7. I get static noise on the analog audio out when no sound is playing (I use alsa). I tried to add a configuration file in /etc/modprobe.d which disables power saving (as this appears to be the usual reason for static noise), but this does not work. Does anyone know how to resolve this?
  8. Hello, download page for odroid M1 states: I have two questions: - Does that mean that the system will be installed on SD or eMMC? or does that meant booting on SD is just for startup to launch system stored on NVMe (or any other storage)? - Is there a plan for booting from M.2 NVMe M-Key PCIe3.0 2-Lane in the future? Thanks Julien
  9. https://www.armbian.com/odroid-m1/ - kernel 6.1.y LTS
  10. Board Dimensions: 90mm x 122mm x 16mm Heatsink Dimensions: 100mm x 123mm x 19mm Weight: 253 g including heatsink Rockchip RK3568 Processor L1 instruction cache: 32 KB, 4-way set associative (128 sets), 64 byte lines, shared by 1 processor L1 data cache: 32 KB, 4-way set associative (128 sets), 64 byte lines, shared by 1 processor L3 data cache: 512KB , 16-way set associative (512 sets), 64 byte lines, shared by 4 processorsQuad-Core Cortex-A55 (1.992GHz) ARMv8-A architecture with Neon and Crypto extensions Mali-G52 MP2 GPU with 4 x Execution Engines (650Mhz) 0.8Tops@INT8, integrated high-performance AI accelerator RKNN NPU Supports one-click switching of Caffe/TensorFlow/TFLite/ONNX/PyTorch/Keras/Darknet 4 or 8GiB LPDDR4 with 32-bit bus width memory Data rate: 3120 MT/s, up to 1,560MHz 1 x eMMC slot 1 x Micro SD slot (DS/HS mode up to UHS-I SDR104) 1 x NVME M.2 SSD (PCIe 3.0 x 2) 1 x SATA3.0 1 x GbE LAN ports (RJ45, supports 10/100/1000 Mbps) Realtek RTL8211F (Ethernet transceiver) LED indicators Green LED: Flashing by data traffics at 100Mbps connection Amber LED: Flashing by data traffics at 1000Mbps connection 1 x HDMI 2.0 (up to 4K@60Hz with HDR, EDID) 1 x MIPI-DSI (works with 800 x 1280 LCD) 1 x 3.5mm phone jack 1 x mono speaker output 1 x HDMI sound 2 x USB 2.0 host port 2 x USB 3.0 host port (or 1 x USB 3.0 host + 1 x USB 2.0 OTG port) 1 x Debug serial console (UART, 1.5Mbps N81) 1 x SATA Connector 1 x MIPI-CSI Camera Interface (15 pin) 1 x MIPI-DSI LCD Interface (31 pin) 1 x 40pin GPIO header IR receiver for remote controller RTC and backup battery holder (to keep time and date for several months without main power input) System LED Indicators: Red (POWER) – Solid light when DC power is connected Blue (ALIVE) – Flashing “heartbeat” while Kernel is running. Solid On when in the u-boot stage. 1 x DC jack : outer (negative) diameter 5.5mm, inner (positive) diameter 2.1mm DC input : 7.5V ~ 15.5V DC 12V/2A power adapter is recommended IDLE : ≃ 1.25W CPU Stress : ≃ 4.44W (Performance governor) Power Off : ≃ 0W https://www.hardkernel.com/shop/odroid-m1-with-8gbyte-ram/
×
×
  • Create New...