vlad59

Members
  • Content count

    107
  • Joined

  • Last visited

About vlad59

  • Rank
    Elite member

Recent Profile Visitors

675 profile views
  1. That's why the use case is very important and you have to be specific : if I/O (disk or network) is the most important for you, then RPi3 can be worse than an old Banana Pi. If your main problem is CPU then Rpi3 will be better. i.e. : * you run static website (hugo for example) -> disk I/O is not that important as most of your files will be cached * you run many Wordpress / MySQL databases -> Disk I/O is important * You serve very big files -> More than 1Go of RAM can be great and Gigabit ethernet is mandatory .....
  2. vlad59

    failure rate of SBC boards

    You can use a normal kitchen oven ..... if your wife agree (at your own risk) and if you don't care about the smell afterwards.
  3. vlad59

    K-worker problem on Banana pie M1

    I'm using the workaround for the last month but my Banana pi has not a lot of work to do (load average: 0,21, 0,15, 0,11) so I really don't know if there is a risk or not.
  4. vlad59

    K-worker problem on Banana pie M1

    This is due the a kernel change so the distribution shoud not change that at all. You can use the search to find a palliative.
  5. vlad59

    failure rate of SBC boards

    I got 2 banana pis running 24/7 for 4 years with SSD -> not any problem. I've got a spare one that I boot every year. I got 2 Pine64 used at work also running 24/7 for 1,5 year -> not any problem with the boards but I had to renew the SD on both Pine64. I also have Pine64 and various Nanopi that are not running 24/7 but still work fine. My 3 Rpis (only old ones : first 256Mb RpiB, another 512Mb and a RPI2) are also fine (used with Libreelec in various room at home) -> the SDcard never had a fail. So for SBC not a single fail. If I add others microcontrollers, never had a problem with my arduinos (mainly moteinos) but some Flash fails with ESP8266.
  6. vlad59

    30-sysinfo get_ip_addresses()

    Thanks I'll test it at home and report back
  7. vlad59

    Green Artefacts on Screen - Cubietruck

    if performance works then you can try conservative it should be better for Electricity cost (if that works of course)
  8. vlad59

    30-sysinfo get_ip_addresses()

    Yes .... but something configurable is often more complex to maintain so while motd is kind of important for a guy that installed Armbian for the first time, it's rarely useful for someone that only use SSH with a purpose in mind (I only give a quick look to system load to check for unusual load that's all). It depends on the goal.
  9. vlad59

    30-sysinfo get_ip_addresses()

    I agree br should be excluded (at least for my usecase which involve docker). I remember talking about Zador when he changed it a year ago : https://github.com/armbian/build/commit/2d37a1ec3e5aee5ed6d942a6eb93fdbf20a08413#diff-02317355268e7ae7265db2efbf843d7b I don't know why @Igor changed it. But as it's only a motd I don't care a lot about it.
  10. I have a Banana Pi (The very first one, before the Banana Pro / m1 came out) running Armbian 5.38 with kernel 4.14.18 and it runs 24/7. Its uptime is 56 days (and I rebooted the board) so no problem at all. I have another Banana Pi running Armbian 5.31 with kernel 4.11.6 and its uptime is 143 days. I never had a single problem with both of them.
  11. I have two Banana Pis running 24/7, one of them is running a rather old Jessie (4.14 IIRC) and the other one latest Armbian Stretch, both didn't have any hangs or reboots (the first one has almost one year uptime)
  12. Sorry for the delay here my lsusb output : Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 64 idVendor 0x0a12 Cambridge Silicon Radio, Ltd idProduct 0x0001 Bluetooth Dongle (HCI mode) bcdDevice 88.91 iManufacturer 0 iProduct 2 CSR8510 A10 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 Device Status: 0x0001 Self Powered
  13. For now I only limited access to the Banana pi with BT 4.0 USB. As soon as I get a proper SSH, I'll send you the lsusb output.
  14. Please note that removing those two modules mean that the kernel won't know if the SOC temp is too high (check dmesg afterwards) About your bluetooth dongle problem, I would guess it's a power supply problem. My two Banana Pis are powered with a 2A Power supply through the micro usb, they both have a SSD connected and one of them also has a bluetooth BLE (cheapest one on ebay) adapter and I have no problem (+100 days uptime). The BLE Usb device is used every 20s to check for specific BLE tracker to check for home presence and there was no glitch for a few months.
  15. Please check https://groups.google.com/forum/#!searchin/linux-sunxi/lucas|sort:date/linux-sunxi/bVEsjQRNVSo/nTa3rpOyAQAJ for a workaround.