• Content Count

  • Joined

  • Last visited

About arox

  • Rank
    Embedded member

Profile Information

  • Location
  • Interests

Recent Profile Visitors

3498 profile views
  1. With 32 GB emmc ?!? That is an option that generally costs the price of a RPI.
  2. Many seems to think that theirs has to be very long and powerful (if you understand what I mean). In fact, a well designed enclosure can assume this function. And in any case the quality of the thermal interface is more important than anything else.
  3. Manufacturers will always add all hardware features that does not cost a lot : i.e. crappy cheap wifi and so on, because they do not bother to provide good drivers. In the other hand, RAM is always priced a lot and thermal design bad. If I want a SBC for specific use case like computing (and not a X86 server), I want it to be passively cooled and energy efficient. Storage is also a choice : either emmc, either a good bus design for drives. I simply cannot find a SBC for a use case because they are all designed for "general purpose" like a RPI or expensive with no guaran
  4. Stupid us ! For me configuring is like programing. We need to check live parameters to debug configuration or design mistakes. I wish I would know how to debug efficiently some declarative languages ...
  5. cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power_supply/ac/voltage_now is not present om my Banana Pi. Well my kernel is outdated. You can find the correct path in armbianmonitor script.
  6. Check you have the same netmask on router, bridge and dhcp config. Check router arp tables and messages to see if it receive requests. Check if interfaces are really added to the bridge with brctl and that some nasty software has not added addresses to wlan0 and eth0 with ifconfig.
  7. Perhaps you should try another PSU or check your cables : your voltage drop low at 960 MHz and you got SATA errors and reset. Try : cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power_supply/ac/voltage_now while transferring files.
  8. I would like DT overlay could handle that sort of thing. (I may suggest here something completely stupid because I know nothing about DT). Using an overkilled dynamic system configuration system like udev to make a static configuration is somewhere strange ...
  9. The method "filtering by devpath" I have indicated before is targeted at providing a solution in that case. The match is done for a type of (identical) devices (same idVendor/idProduct) and the device name chosen according to the index of USB port.
  10. Good question ! The name depends not only on boot but also change if you plug / unplug devices ... I have the same problem when I try to work with 2 micro-controllers at the same time. This can certainly be done with an "udev rule". There is some response here : In section : filtering by "devpath" : SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ATTRS{devpath}=="1.2", SYMLINK+="ttyUSB-arduino1" SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idP
  11. What happens if you just create it ? (sudo touch /var/log/wtmp)
  12. "it should have plenty of power to run the board and hdd" This is a recurrent question on this forum. But the voltage available to the board always depends on the source voltage and also on the cable(s), contacts of connectors and internal circuits resistance, protection diodes and fuses, (and of the PSU mileage which is difficult to evaluate) ... When the board needs too much current, the total resistance can make the input voltage drop below the minimum needed for a time too short to see on a multimeter but that may cause any sort of hardware failure. If you never ch
  13. BTW A possible cause of repeated fs corruption is the power supply. (Or power cables).
  14. Hum ! A bit worrying that your second fsck complained. I do not understand why you couldn't unmount the fs or /dev/sda1 was not present and appeared the second time ? Did you run fsck with the fs mounted ro ? The fs is probably repaired now but you should check your logs and have an up-to-date backup during some times. There are commands to check disk errors recorded by firmware (but not controller or cables errors). Anyway I experienced your problems a lot of times and still use the board and cards without problem. Yes, BPI M1 with armbian was and always is