caplam

  • Content Count

    7
  • Joined

  • Last visited

  1. here are the results: root@opizero1:~# stress -c 2 -m 2 stress: info: [1113] dispatching hogs: 2 cpu, 0 io, 2 vm, 0 hdd stress: FAIL: [1113] (416) <-- worker 1117 got signal 9 stress: WARN: [1113] (418) now reaping child worker processes stress: FAIL: [1113] (452) failed run completed in 86s Before test under normal opération (10% cpu load) i have 5V at 5.25V (on the 13 or 26 pins header) and 3.3V at 3.35V During test i have the same voltages. edit : here is the the result of sudo armbianmonitor -u: http://sprunge.us/VKiF edit 2 : I have another test which is running since 5 min a
  2. Thank you for your answer. I understand the need to do a stress test and I'll do it. It isn't a real issue for me as i don't have "high " network needs. In normal conditions my pi's have very light load (max 10% cpu) and a even lighter network load so it can run in half duplex mode. My point was only to report that but if the driver is to be replaced there's no need for further investigations. Anyway i ordered a console cable which could be useful in the future. I'll post here the result of stress test.
  3. For now i didn't do stress test but here are the tests i did. I change the port switch configuration and then run ethtool eth0 to see what the pi understood. switch config Connection advertised link auto No / / auto-10 No / / auto-100 No / / auto-10-100 Yes 10H-10F-100H-100F 100H 10H Yes 10H 10H 10F Yes 10H 10H 100H Yes 100H 100H 100F Ye
  4. I use an amazon adpater. It's a 22awg cable. I measured 5.35V with the pi zero running (but without the expansion board plugged). For now i don't use a poe adapter. I've no serial console attached so it's not a real diagnose. I've noticed that both of my pis didn't get network connection when plug in any port of my switch (trough my home cables or directly on a switch port with a patch cable). I ssh in the switch and saw that the link is down. When i configured the switch with a 100FD link in place of autoneg the link came up. As soon as i go back to autoneg the link is down. Notice that
  5. I needed a small device with wired and wireless connectivity, with poe support, with a case available, able to run a linux distro, cheap. I think the opi zero meet these requirements. Someone on the board (not here but on the jeedom board) mentionned the pi zero. I gave it a try. For the bluetooth i only needed to plug a cheap bt4.0 dongle. It's dedicated to ble scan. I probably will try also to plug another bt dongle to manage voice advertisement with a BT speaker and pulse audio. Ok i read too fast the specs and the poe implementation is really crapy as i don't plan to solder anything on
  6. Searching in the forum i found some posts about ethernet subject in development section. I didn't know about ethtool. It seems that both my opizero are stuck at 100HD. Doesn't seem to be unusual as i run nightly build. However the negotiation problem appeared also when using armbian 5.24 with debian jessie legacy 3.4.113
  7. Hello every one, My first post here i'll try to be clear but english is not my mother langage. I bought a couple of opi zero with usb expansion board and a case. I needed small devices able to run a linux daemon and control a bluetooth LE device. They are used as antennas in a bluetooth mesh network. The orange pi zero seemed to be a good choice. I first installed the opizero with armbian 5.24 debian version. Unfortunately I was unable to use bluepy lib. It was the same with the xenial version. Another user of the bluetooth advertisement plugin told me to use last firmware (5.25) and u