Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. Pi-factor cases

    @tkaiser my Nanopi Neo boards use 2mm thermal pad. It just works.
  3. You mean image from the download section? Which one exactly? Ideally, we should pack those things in the build process. Thank you. I'll try to cope with those problems ASAP.
  4. Android on H6 Boards

    Replacing the .dtb file contents with the one for PineH64 works somewhat (at least the kernel uses the updated .dtb -- see the gmac-power0, gmac-power1 and gmac-power2 entries in serial console output). But then with the Xunlong image PineH64 panics: Same modified image boots on an OPi Lite2 but... this Allwinner BSP crap is that horrible that it's really not worth a look (at least for the stuff I'm interested in). UAS is not supported, quick USB3 storage 'performance' test results in 40/45 MB/s read/write with an EVO840 SSD, no drivers included for any of the popular USB Ethernet dongles. I had the idea to do some tests with the BSP to get some baseline numbers but in this state this is all just a waste of time...
  5. FEX script machine
  6. It should work good enough with the legacy kernel and preinstalled mpv, check its limitation. There is no video acceleration within a web browser - you need to use some 3rd party application. Video playing and mainline kernel. It has to be developed first. Implementation on Allwinner boards is expected to happen this summer/autumn.
  7. Today
  8. Gogo android tv stick linux

    not sure this is the right place to post this got one of these really cheap last year $10nzd in a mall on clearance was wanting to know if there was any linux os out there i could install on this ?
  9. Reboot needed to update IP address

    Since I have done nothing to configure the network, /etc/network/interfaces is probable. It has: # Wired adapter #1 allow-hotplug eth0 no-auto-down eth0 iface eth0 inet dhcp
  10. Overscan issue - screen out of bounds

    I had this issue with my Cubieboard 2 in Armbian on a Viewsonic monitor, but not a (much newer) Dell monitor. The issue never appeared in Cubian or in the stock Android ROM.
  11. Yesterday
  12. ARMBIAN for Amlogic S905 and S905X

  13. Hello, I've flashed my SD card with Armbian_5.41_Orangepiwin_Ubuntu_xenial_default_3.10.107_desktop and after booting the system everything works like a charm except my sound which I've tried to get through the 3.5mm jack. I've done upgrade && update but that doesn't seem to help. I've tried several headphones and speakers and none of them worked. On top of that I've tried flashing this image file on one other microSD card and I've tried running it on another Opi Win Plus board since I have several of them lying around my house. Regarding my power supply, it's 5V 3A which I've read is the appropriate one. I'm fairly new to Linux with really limited knowledge of how everything works here, so I would really appreciate some help in solving this issue. Also, if it gives you any clues what could be the cause of problem, when playing videos on YT on Chromium all of them seem to lag a lot. They just don't have that fluidness you need to watch any video. On Firefox is a different story - videos play ok there but there is still no sound there either. When I type aplay -l I get this **** List of PLAYBACK Hardware Devices **** card 0: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 and aplay -L gives me this output null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server default Playback/recording through the PulseAudio sound server sysdefault:CARD=sndhdmi sndhdmi, Default Audio Device dmix:CARD=sndhdmi,DEV=0 sndhdmi, Direct sample mixing device dsnoop:CARD=sndhdmi,DEV=0 sndhdmi, Direct sample snooping device hw:CARD=sndhdmi,DEV=0 sndhdmi, Direct hardware device without any conversions plughw:CARD=sndhdmi,DEV=0 sndhdmi, Hardware device with all software conversions Help, please!
  14. have the same issue, is there a solution?
  15. Real time clock DS3231

    Today I connected a I2C RTC to my NanoPi Neo Core2, worked without a problem....but if anyone is getting the same RTC (ZS-042) and using a CR2032 battery - please remove the smd resistor in the upper right corner, because this board does charge the battery, because there should normally be a LIR2032 rechargeable battery. see at 02:00 and I2C instructions at
  16. EspressoBin - mPci-e

    I see, the access point broadcasts at 2.4 GHz only.
  17. Orange PI zero operate RF 433

    Yes ! That's what I mean ...
  18. Hello, i've experienced eMMC Problems with the latest stable Jessie Armbian-Image for Odroid C2. Thats why i installed Debian_jessie_next_desktop_nightly.7z from the nightly builds. After my first experiences it seems that image is working good since i did all of my configurations over serial console and ssh. Now when connecting my display it's not working. Which is 1440x900p60hz and connected over a hdmi<->dvi Adapter to the board. The device is starting with a black screen and not not detecting any display when i try to start the X-Server manually and there are also no /dev/fbdev* devices. Since the boot files between stable and nightly images differ, there might be something that needs to be configured in order to get the framebuffer device alive ??? Any help is appreciated. Best regards, Thomas
  19. Hi, I have a question regarding standard DNS server entry in resolv.conf: The Google DNS is at the top followed by the one supplied by my DHCP service. That way the Google server will be queried first, which I think is wrong, considering privacy implications. Why is it hardcoded anyway? As I understand it, it comes from /etc/resolvconf/resolv.conf.d/head? this should not include anything. Would be nice If somebody could clarify why it is implemented that way. Thanx
  20. Freedombox can and does work well on armbian. I have succeffuly installed it using the following
  21. Switched kernels. Total made 4 tests, here are my results so far: H - Hardkernel's A - Armbian's +---+--------+----------+--------+-----+ | 0 | Kernel | boot.ini | RootFS | 433 | +---+--------+----------+--------+-----+ | 1 | H | H | H | OK | | 2 | A | H | H | OK | | 3 | H | A | A | NO | | 4 | A | A | A | NO | +---+--------+----------+--------+-----+ So, the issue is caused by either boot.ini or root fs. Not easy to swap and test: both are very different boot.ini diff: --- hardkernel\boot.ini Thu Sep 14 14:35:20 2017 +++ armbian\boot.ini Sat Jan 27 18:04:08 2018 @@ -1,10 +1,12 @@ ODROIDC-UBOOT-CONFIG +setenv rootdev "UUID=753f661a-b187-4823-abce-66db73b680af" +setenv rootfstype "ext4" + # Possible screen resolutions # Uncomment only a single Line! The line with setenv written. # At least one mode must be selected. -# setenv m "480x800p60hz" # 480x800 # setenv m "vga" # 640x480 # setenv m "480p" # 720x480 # setenv m "576p" # 720x576 @@ -31,14 +33,10 @@ # setenv vout_mode "vga" # HDMI BPP Mode -setenv m_bpp "32" -# setenv m_bpp "24" +# setenv m_bpp "32" +setenv m_bpp "24" # setenv m_bpp "16" -# Monitor output -# Controls if HDMI PHY should output anything to the monitor -setenv monitor_onoff "false" # true or false - # HDMI Hotplug Force (HPD) # 1 = Enables HOTPlug Detection # 0 = Disables HOTPlug Detection and force the connected status @@ -57,7 +55,7 @@ # UHS Card Configuration # Uncomment the line below to __DISABLE__ UHS-1 MicroSD support # This might break boot for some brand models of cards. -setenv disableuhs "disableuhs" +# setenv disableuhs "disableuhs" # Disable VPU (Video decoding engine, Saves RAM!!!) @@ -75,34 +73,24 @@ # setenv condev "console=tty0" # on display (HDMI) setenv condev "console=tty0 console=ttyS0,115200n8" # on both -# Enable/Disable ODROID-VU7 Touchscreen -setenv disable_vu7 "false" # false -# CPU Max Frequency -# Possible Values: 96 192 312 408 504 600 720 816 -# 1008 1200 1320 1488 1536 1632 1728 and 1824 -setenv max_freq "1536" -# setenv max_freq "1632" -# setenv max_freq "1728" -# setenv max_freq "1824" ########################################### if test "${hpd}" = "0"; then setenv hdmi_hpd "disablehpd=true"; fi if test "${cec}" = "1"; then setenv hdmi_cec "hdmitx=cecf"; fi -if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi # Boot Arguments -setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro ${condev} no_console_suspend vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs} ${hdmi_hpd} ${hdmi_cec} ${enabledac} monitor_onoff=${monitor_onoff} max_freq=${max_freq} ${hid_quirks}" +setenv bootargs "root=${rootdev} rootwait rw ${condev} rootfstype=${rootfstype} loglevel=1 no_console_suspend consoleblank=0 vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs} ${hdmi_hpd} ${hdmi_cec} ${enabledac} ${extraargs}" # Booting -fatload mmc 0:1 0x21000000 uImage -fatload mmc 0:1 0x22000000 uInitrd -fatload mmc 0:1 0x21800000 meson8b_odroidc.dtb +ext4load mmc 0:1 0x21000000 /boot/uImage || fatload mmc 0:1 0x21000000 uImage || ext4load mmc 0:1 0x21000000 uImage +ext4load mmc 0:1 0x22000000 /boot/uInitrd || fatload mmc 0:1 0x22000000 uInitrd || ext4load mmc 0:1 0x22000000 uInitrd +ext4load mmc 0:1 0x21800000 /boot/dtb/meson8b_odroidc.dtb || fatload mmc 0:1 0x21800000 dtb/meson8b_odroidc.dtb || ext4load mmc 0:1 0x21800000 dtb/meson8b_odroidc.dtb fdt addr 21800000 if test "${vpu}" = "0"; then fdt rm /mesonstream; fdt rm /vdec; fdt rm /ppmgr; fi if test "${hdmioutput}" = "0"; then fdt rm /mesonfb; fi -bootm 0x21000000 0x22000000 0x21800000" +bootm 0x21000000 0x22000000 0x21800000
  22. I try Arch several years ago ... and is hard to learn all the different CLI commands!
  23. Please describe your setup as best as possible so we know what your operating environment is like. Name of your board with all details, version number, take a picture if you are not sure what you have Name of the image you installed or logs, when you can boot the board: armbianmonitor -u (paste URL to your forum post) If your board does not boot, provide a log from serial console (UART) or at least make and attach a picture, where it stops. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. If anything is attached to the board, supply all details
  24. Ili9341 works only with MPlayer / python?

    Ok, Just in case anyone else is having the same problem: check your nodm config. You will get very strange behavior if nodm is not properly configured.
  25. tutorial Motioneye (OPI)

    Yes, for CSI camera you must stay on legacy (Jessie dafault). CSI on mainline is on WIP stage. Main difference is Motion 3.2.12 (instead of 4.01). Next kernel 4.14.18 is more stable than 3.x (uptime: weeks vs few days). On Jessie may need "deb multimedia" packages for a recent ffmpeg version. I recommend you a good USB camera H264/MJPEG capable.
  26. WiFi AP on BPiM2+

    Since you don't know how to setup thing it is better to use armbian-config way. It does everything ... except switching this mode. In case you want to do it manually, use google. There are tons of manuals around. You need to setup DHCP server or put network into bridge mode which will make use of your current DHCP server ...
  27. Le Potato: xfs module missing

    Well, if you go through the menu and create dev packages, that will be 4.16 rc kernel. That should be the "next" environment in coming weeks.
  28. Last week
  29. Installation SD not work

    Hi Igor Thank you for your reply! I'm newbie in linux debian CLI... I've just install debian jessie from ignition, but i ddin't find fdt_file
  1. Load more activity