guidol

Members
  • Content count

    173
  • Joined

  • Last visited

About guidol

  • Rank
    Elite member

Profile Information

  • Gender
    Male
  • Location
    Mudanya
  1. Did you power the drive from the Orange Pi Prime via USB or has it an external power supply? If from USB then the power supply hasnt enough power for booth - because on heavy load the Prime need more power.
  2. There is only this version of armbian for the Sunvell R69 and I - personally - wouldnt it recommend for using with Kodi. I dont know it the armbian-Desktop Version is hardware accelerated for Video. If you would use Kodi its better to use Android. For the original Android of the Sunvell R69 (Android 4.4 which is named 6.x) you could use a patches KODI 17.1 which can be found at: https://www.entertainmentbox.com/kodi-17-1-4-4-android-powered-devices/ H3Droid wouldnt run because the Sunvell R69 has a H2 CPU? https://h3droid.com/ https://h3droid.com/howitlooks
  3. I didnt know that the Orange Pi One can boot from USB But at the Boot-log I did read "scanning bus 0 for devices - 4 USB device(s) found Could you try to boot from MicroSD-Card when only connect a Keyboard/Mouse (NOT a USB-Hub or any other storage device)? (Did you "eject" the MicroSD-Cards via File-Explorer or did you only disconnect the card?) If you are using Windows you could try to write the image with USB-IT (does work fine for me - like etcher 1.2.1): http://www.alexpage.de/usb-image-tool/download/ Did you format your MicroSD-Card using SD-Formater v5 (page url says v4 but its V5) before writing the image?: https://www.sdcard.org/downloads/formatter_4/eula_windows/index.html Click accept at the bottom of the page for downloadinf the v5
  4. @Igor Thanks for the information! I did: Rollback: mkdir /home/guido/rollback cd /home/guido/rollback wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-dtb-next-sunxi64_5.34.171121_arm64.deb wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-headers-next-sunxi64_5.34.171121_arm64.deb wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-image-next-sunxi64_5.34.171121_arm64.deb dpkg --force-all -i ./linux-dtb-next-sunxi64_5.34.171121_arm64.deb dpkg --force-all -i ./linux-headers-next-sunxi64_5.34.171121_arm64.deb dpkg --force-all -i ./linux-image-next-sunxi64_5.34.171121_arm64.deb reboot armbian-config ==> system ==> freeze after that removed the usb-ethernet (because it was configured as the same IP) and rebootet again. (If I didnt need the headers - which I installed via dpkg.... could I use the armbian-config funtion to deinstall the headers?) Now my Neo2 NAS is accessable via SSH again - but I wonder after downgrading I do get the newer welcome Message out of /etc/armbian-release - which hasnt been downgraded?: Welcome to ARMBIAN 5.37.171208 nightly Debian GNU/Linux 9 (stretch) 4.13.14-sunxi64 I also did see that with the working 5.34 the u-boot doenst show the network: U-Boot 2017.11-armbian (Dec 07 2017 - 12:01:53 +0100) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. As attachment you could see that the u-boot of my Orange Pi R1 could see the network card [EDIT because of the Linux-Headers] I did try to use armbian-config for removing/uninstallting the headers - and armbian-config offered it also to uninstall/remove it - but after I selected it it does try to INSTALL something. Then goes one screen back and did now again to remove/uninstall it But with dpkg I also could complete install the headers: root@nanopineo23:/home/guido/rollback# dpkg --purge --force-all linux-headers-next-sunxi64 (Reading database ... 65039 files and directories currently installed.) Removing linux-headers-next-sunxi64 (5.34.171121) ... dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/selinux/mdp' not empty so not removed dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/selinux/genheaders' not empty so not removed dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/mod' not empty so not removed dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/kconfig' not empty so not removed dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/dtc' not empty so not removed dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/basic' not empty so not removed
  5. How to roll back? Re-Install? The kernel can be freezed in armbian-config - right?
  6. Properly powering the Tinkerboard

    The Original RPi power supply has also +5.1V 2.5A output (provides all the power your Pi will need) https://thepihut.com/products/official-raspberry-pi-universal-power-supply "It seems that the Raspberry Pi requires at least 5.1 volts of power to allow ethernet, keyboard and mice, USB, HDMI, and the SD card to even function correctly, without crashing everything due to low voltage" https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=17492
  7. I did a apt update & upgrade on my NanoPi Neo2 NAS and it updated to nightly 5.37 but at the beginning of the boot-log it tells me: Net: No ethernet found. I didnt get an eth0 interface from the mainboard ethernet-port (only lo) [ 1.633544] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.798411] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.798556] dwmac-sun8i 1c30000.ethernet: Will use external PHY [ 1.904820] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 1.904832] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 1.904842] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 1.904853] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 1.904863] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 1.904873] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 1.905433] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus [ 1.905452] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed Now I can access the Neo2 only via TTL-serial-debug console Lucky me - I have a USB-Ethernet Adapter which I can use: [ 787.473350] MOSCHIP usb-ethernet driver 3-1:1.0 eth0: register 'MOSCHIP usb-ethernet driver' at usb-1c1b000.usb-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:12:34:55:56:2b [ 787.473508] usbcore: registered new interface driver MOSCHIP usb-ethernet driver [ 787.503850] MOSCHIP usb-ethernet driver 3-1:1.0 enx00123455562b: renamed from eth0 so here the armbianmontor -u : root@nanopineo23:~# armbianmonitor -u System diagnosis information will now be uploaded to http://sprunge.us/JQdE PS: The NanoPi NAS with only a "normal" Neo has found his Network after update to 5.37 root@nanopi-neo:~# dmesg|grep -i 1c30000 [ 4.313641] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.313714] dwmac-sun8i 1c30000.ethernet: No regulator found [ 4.313819] dwmac-sun8i 1c30000.ethernet: Will use internal PHY [ 4.313937] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000) [ 4.314111] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 4.314123] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.314134] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 4.314145] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 4.314156] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 4.314167] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 19.124960] dwmac-sun8i 1c30000.ethernet eth0: device MAC address 16:1c:0c:e4:e5:76 [ 19.128797] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 19.128816] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 22.249109] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx ARMBIAN 5.37.171208 nightly Debian GNU/Linux 9 (stretch) Linux nanopineo23 4.14.4-sunxi64 #11 SMP Thu Dec 7 11:55:12 CET 2017 aarch64 GNU/Linux Neo2_Bootlog_537.txt
  8. NanoPi Neo 1.31

    normally armbian-config is already installed with armbian.... If not then you could it install in armbian with apt install armbian-config
  9. Nanopi M3 / S5P6818 boards

    Yes the M3 is gone and in future the M2a: http://www.friendlyarm.com/Forum/viewtopic.php?f=42&t=902
  10. At the page http://kaiser-edv.de/tmp/NumpU8/ there are 2 compressed boot-images. One for Desktop and one for headless server. You could download, extract the image and use Etcher as software for writing the image to MicroSD card. then insert the card in the Sunvell R69 and boot your armbian :-)
  11. NanoPi Neo 1.31

    Some time ago I also ordered a NanoPi Neo, because the Neo2 in my 2nd silver FriendlyArm-NAS case has to be in the black little Aluminium-cube with OLED-Display Now the NanoPi Neo V1.31 reside in my 2nd NAS-Case. He is running ARMBIAN 5.34.171121 nightly Ubuntu 16.04.3 LTS 4.13.14-sunxi with the SAMBA-Server installed via the armbian-config Softys. In the Case he shows: CPU temp: 46°C The 100MBit Ethernet isnt fast for a NAS - but I do get around 8-11MB/sec - thats OK for 100MBit
  12. https://www.cnx-software.com/2017/12/07/rockchip-rk3288-to-be-phased-out-soon-gpd-xd-android-console-to-get-mediatek-mt8176-soc-4gb-ram-upgrade/ Rockchip RK3288 32-bit Arm processor was first spotted in a company presentation in the summer of 2013, before being announced – with some confusion (Cortex A12 vs A17) – at CES 2014 in January. The quad core Cortex A17 processor had then its moments of glory with inclusion in products such as Chromebooks (2015) and ASUS Tinker board SBC earlier this year. “Rockchip are phasing out sales of the RK3288”, meaning most products based on the chip will soon be phased out or upgraded to another solution. How long each product will keep selling will depend on the stocks held by the manufacturer.
  13. I would try to apt remove firmware-ralink then rerun the update
  14. couldnt test with my OPi-R1 because I didnt got a SATA-device on my OPi-R1: root@orangepi-r1:/home/guido/jms/JMS578FwUpdater# ./JMS578FwUpdate -v JMicron Firmware Update Tool v0.0.0.1 Copyright (C) 2017 JMicron Corp. root@orangepi-r1:/home/guido/jms/JMS578FwUpdater# ./JMS578FwUpdate -d /dev/sda -v ERR : open device fail Get Bridge version FAIL!
  15. ODROID HC1 / HC2

    [deleted]