• Content Count

  • Joined

  • Last visited

About guidol

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2931 profile views
  1. got these times with a Core2Duo 2.4GHz, 8GB Ram but with a normal 7200rpm HDD Image for a - to the cache - new device around 60-75 minutes. for a device in cache around 15-25 minutes.
  2. how about putting a fresh armbian to another sd-card to test if the OPi has survived the power-outtage. When this is successful try to fsck the other card on another linux system. maybe the filesystem is corrupt.
  3. if you cant ping the pi ip you do see on the router, then restart the router and when this has booted completly - boot the pi then check again
  4. we will see how long it does work after a reboot
  5. when you did try different boards - did you also try all of the !three! usb-ports on every board? specially the single one on the other side of the eth0-port? Because in you first dmesg the USB-Ethernet adapter was recognized as eth1 and then renamed. And this renamed name wouldnt go in every situation automatically up for ifconfig. So check the other usb-ports and when you will see enx00e04c680046 in dmesg get him up with ifconfig enx00e04c680046 up and then he would be displayed in ifconfig when the port is down (not automatically up or no cable/link connected the interface is in down state) then it wouldnt displayed by ifconfig The part after enx is the MAC-address of your USB3.0 Ethernet-adapter. I got this model running on my devices without special power supply and from my personal view there is no driver problem with armbian and this device.
  6. at the same USB-Port? I have also a OPi PC and he has 3 USB-Ports
  7. with this version you shouldnt have a driver issue - like you could see in your first dmesg log
  8. in his first dmesg it was recognized: 388 [ 5.571663] usbcore: registered new interface driver r8152 413 [ 5.906764] r8152 4-1:1.0 eth1: v1.09.9 414 [ 6.188868] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard 415 [ 6.552250] r8152 4-1:1.0 enx00e04c680046: renamed from eth1 but not in the second one. @cam2019 did you use another USB-Port? Maybe that has to be enabled in armbian-config -> system -> hardware ?
  9. I do use the same USB3.0-ethetnet adapter on my devices under armbian and got NO driver issue. Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 5.1.0-sunxi package bsp-kernel[5.86] u-boot[5.85] dtb[5.86] firmware[5.83] config[5.88] Linux opi-zero-99 5.1.0-sunxi #5.86 SMP Mon May 13 21:11:09 CEST 2019 armv7l GNU/Linux [1399909.295651] usb 5-1: new high-speed USB device number 2 using ehci-platform [1399909.455662] usb 5-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [1399909.455734] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [1399909.455783] usb 5-1: Product: USB 10/100/1000 LAN [1399909.455830] usb 5-1: Manufacturer: Realtek [1399909.455874] usb 5-1: SerialNumber: 000001000000 [1399909.732093] usbcore: registered new interface driver r8152 [1399909.763071] usbcore: registered new interface driver cdc_ether [1399909.867457] usb 5-1: reset high-speed USB device number 2 using ehci-platform [1399910.083109] r8152 5-1:1.0 eth1: v1.09.9 [1399910.174042] r8152 5-1:1.0 enx00e04c68007b: renamed from eth1 Which version of armbian do you use? Maybe your eth1 is also renamed (see dmesg or ifconfig) = Predictable Network Interface Name Maybe you have to switch this off for eth1 as name: sudo nano /etc/default/grub from: GRUB_CMDLINE_LINUX="" to: GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" sudo grub-mkconfig -o /boot/grub/grub.cfg reboot [EDIT] your code in your dmesg: 413 [ 5.906764] r8152 4-1:1.0 eth1: v1.09.9 414 [ 6.188868] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard 415 [ 6.552250] r8152 4-1:1.0 enx00e04c680046: renamed from eth1 So now configure enx00e04c680046 or disable the predictable network names Test: ifconfig enx00e04c680046 up and then look for the device with ifconfig
  10. Aart Bik has now released also a 64bit/aarch64 version of his BikJump-Chess-Engine (v2.5) which is available at Does run well under armbian 64bit/aarch (like on my NanoPi Neo2 with H5 CPU)
  11. UCI Engine BikJump 2.1P from Aart Bik is available under Get it running (32bit) via wget and chmod 755 on a RPi3 - does run also on a 32bit armbian! ( ==> like H2/H3-CPU ) see also:
  12. define your default soundcard in /etc/asound.conf get a list of your soundcards with aplay -l
  13. In dont like OpenWRT I have started many times with different devices to use OpenWRT, but mostly after 1 day or 2 I did put it aside, because sometimes the device isnt available anymore in the network after a network-configuration or the packets I want to use do not work on this device. debian on the LicheePi is only a "pre-version" but does work for me much better than any OpenWRT I used in the past. In the last years OpenWRT is getting better, but isnt working - for me - not as good as any real linux. Thats sad, because for small devices it would be great. The other bas thing is that many OpenWRT devices does cost now - as some Allwinner or RPi devices are now very cheap - more than a linux-system. So OpenWRT is for me only a option if you net it as an router/network-device.
  14. you can use: deb jessie main contrib non-free deb-src jessie main contrib non-free deb jessie/updates main contrib non-free deb-src jessie/updates main contrib non-free