Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

932 profile views
  1. Works also great, but where is it for? What enables / Disables it? Thank you
  2. on my opi pc plus sound volume is now as loud as on my samsung smartphone... perhaps there is a other schematic on the opi PC PLUS...
  3. this helped great File: /etc/asound.conf: pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } pcm.louder { type plug slave.pcm "dmix" ttable.0.0 3.0 ttable.1.1 3.0 } pcm.!default "louder"
  4. Exactly this was my intention and I followed the first guide. First I installed the system cleanly and after that I installed apt-get install mpd mpc ncmpc with its all of thousands dependencies. After that I created the playlists exactly as described and the first difference was, that i the path was not correct (/var/lib/mpd/music/radio.pls instead of /var/lib/music/radio.pls). After I created the pls at the correct place I found out that mpd must be started manually and after that a mpc load radio.pls and mpc play works perfectly. BUT sound is too quiet. I tried three different in-ear headphones and also a analog to bluetooth sender and my denon receiver. sound is very very quiet overall. I tried to set alsamixer volume to the highest and also set the volume in script.bin from 31 to 100 - but no change. Changed the renderer to software in /etc/mpd.conf but then I can change volume in mpc so, that 100% is as quiet as before and everything below is much quieter....
  5. PUSH same problem for me using Armbian 5.23 jesse server on OPI PC Plus and getting the same issue. Volume is so quiet, that the analog to bluetooth transmitter doesnt recognize the sound... any help?
  6. Now it is 99,9% clear it is a write issue with the sandisk SD-Cards. I now made the image readonly with union-fuse and copied it back to the SD-Card. It runs stable since 3,5 days in readonly mode. THX in advance
  7. So, as far as I can say, I have beaten my personally uptime record with the sammy card. now more than 4 days I had never. Interesting is that I dd the image from the "defective" sandisk card to the sammsung card. I tested the sandisk again 2 times with h2testw and it was marked as good. For me it is cleaar, there is an incompatibility between Allwinner H3 and sandisk cards (as I told with exact these cards the Raspberry had NO problem). So, for experimenting I ordered 2 cheap SD-Cards, when they pass in h2testw I will test them with this Image. And @dottgonzo -> thanx for your advice with unionfs-fuse - I tested it yesterday with my OPi PC + and it runs fine Perhaps I'll give the sandisk cards again a try in readonly mode. I will wait till weekend and with 7 days Uptime I am 100% sure the card caused the crashes.
  8. Hello sovking, thank you for your detailed post. This post makes my suspicion in somecomponents. For me there are 3 big sources for the crashes at the moment: 1) The Sd Card: i am now using a samsung instead of Sandisk. I tested 2 old but good Sandisk Cards, both qere tested with h2wtest and both are old (4gb class 4) but good in quality. I read many people are having problems with H3 and sandisk cards, even with newer hand high class cards. Somewhere I read that Sandisk Cards have a special power saving feature and the crashes ever occur when write cycles are done. So I am now on day 2.5 with a samsung 32 GB Class 10, after one week I will be sure if it is stable. 2) I am also using a self built UPS with a step down to 4.8 V, in the middle a LiIon charging circuit connected to 2 18650 in parallel constellation and because power can go down to 3.3 volts I use a step up converter to a fixed Voltage of 5.2 Volts. I use 2 of these self built UPS on 2 x Raspberrys Pi 3 and this runs absolutely stable since the appearence of the rpi3 (I ordered them directly after appearing on the market). Perhaps there is a noise created by the step up converter the H3 board doesnt like. If the board will crash again with the samsung card I will test with a standard Mobile phone Power supply 5v 2a. 3) last and not least: we 3 here are using rs485 converters (all usb?)? Perhaps a software / driver / firmware error? On the pi this dongle ran over month without a crash... .... In my fact the crashes appear in the night at 3:05 am and around 6:45 am. There CPU load rises because of some tasks (standard taks in armbian image). I closed out some stabilty issues by fixing the cpu freq to ONE fixed value and overvolt it (648 mhz) to 1.3 volt. Crashes appeared as before. But my favorite reason is at the moment the SD card (if it will not crash this night I have beaten my own uptime record of 3 days with the OPi Lite ) Thanks for any suggestions and Infos
  9. Hello again, bad news, even with this policy (fixed freq, OV, etc) I got a crash this night. I do not think ist is a Voltage, frequency, load issue. As tkaiser told, I changed now the SDCard to a complete other brand, 32 gb Samsung class 10... Testing again.... when it now crashes I have completely no idea. I'll try to get a refund or a replacement from orangepi... Greetings
  10. Hi guys, this night my freshly and clean installed pi one crashed again. This time at 3:05 am. Uptime was ca 29,5h. Attached a ss of Armbianmonitor. Now, settings were 816MHz, 2 Cores, 1.1 V, DRAM 132 MHz, The green Power LED was off again, so I think, as dottgonzo already reported, the OPi stucks at a reboot or so on. With my last test I can exclude a defective SD-Card and a defective installation. Now my ideas for further testing: Set CPU at 1.3 Volt all the time, Reduce clock speed to 480mhz completely set 1 or 4 cores change dram clock speed (increase) I think the Pi has a problem with the suddenly increasing load when scheduled tasks are started. CPU has a passive cooler and was at 22°C at this moment. The last test I can do is the same SD-Card at my Orange Pi Plus. Only changed thing must be the voltage regulator driver and dfvs table, wifi and emmc is not needed. If all these not work I'll request refund or a spare Pi from Orangepi, because so it is unusable for me. Do you have any other ideas to find a solution? EDIT: For testing I changed the whole policy. I set CPU Freq hardly coded to 648 mhz (Min AND Max same value), activated 4 cores and corekeeper, DRAM to 408 MHz and Volt to 1.3 Volt. Temperature increased to 26 / 27 degree and this evening I will measure TP1's volt (if it is really set to 1.3 Volt). EDIT2: yesterday evening I measured TP1 and it told me to be at 1.325 Volts, so this seems very good... I decided to wait one week, and if it runs stable I will go step by step to my unstable config and wait between the steps one week per step again. So I should be able to find out what option causes the instability. Weird thing, but as tkaiser told me: the Voltage even in this config is recorded wrongly in armbianmonitor. The PI runs at a fixed frequency and a fixed voltage but as you can see in "VoltPeak1.png" there are Downpeaks... THX
  11. hello together, to exclude all software and sd-hardware failures I took an other of these cards, and first I intensively tested it with a windows tool. I re-extracted the image from the downloaded zip and tested the sha-256. I wrote the image to the tested sdcard I booted the image and wait that the pi came fully up (incl reboots). I made my h3disp config, apt-get update && apt-get upgrade installed the dependencies of my scripts and copied my scripts to it, also changed the rc.local and crontab to my fits. at last I made my h3consumption settings to 816 / 132 / display off / USB on Now I will wait for device to run stable or even not and tell here if or not. If not I can surely say SD Card and random software error are excluded! THX in advance
  12. The time in the morning seems to vary... Today it was 6:41 when CPU load rised for the minutes. But the Board today didn't crash. Yesterday I changed the place of the pi but not the electronic connections. I will test, as first mentioned with 816mhz and if it crashes again, I'll copy the contents of this SD card to another (I've got around 10-15 of these 4GB Cards laying here around). What is the cooler section for? A fan connected to a GPIO?
  13. Hi, because we use on the large boards, we shouldnt run in UV issues while using 912mhz and 1.125 (measured) Volts even when the regulator increases with delay, because regulator should not switch to 1.3 volt when I set the CPU to max 912 mhz. I think there must be a completely other issue. How many people are affected you know? What is the cooler section for? THX
  14. This time I answer myself therefore it is seen here: yesterday I made some tests and found this strange thing: As you can see in the three screenshots it is really weird with freqs and voltages. What is clear the OPi one operates only with 1.1 and 1.3 Volt. But my thought was, thatt all freqs OVER 912 mhz will operate at 1.3 V and all under 912mhz will operate at 1.1 Volt. In the three Screenshots you can see the OPi operating with 814mhz and 1.3 V and sometimes 912mhz with 1.1 Volt... In Voltages1.png you can see the pi operating at 753 mhz and 1.3 Volt In Voltages2.png you can see the pi operating at 814 mhz and 1.3 Volt In Voltages3.png you can see the pi operating at 912 mhz and 1.1 Volt really weird?!? I did not modify the fex / bin file. It is the factory default in this Armbian Image!!! fex / bin contains following: [dvfs_table] pmuic_type = 1 pmu_gpio0 = port:PL06<1><1><2><1> pmu_level0 = 11300 pmu_level1 = 1100 max_freq = 1200000000 min_freq = 480000000 LV_count = 5 LV1_freq = 1200000000 LV1_volt = 1300 LV2_freq = 1008000000 LV2_volt = 1300 LV3_freq = 912000000 LV3_volt = 1100 LV4_freq = 648000000 LV4_volt = 1100 LV5_freq = 480000000 LV5_volt = 1100 -> pmu_level0 = 11300 pmu_level1 = 1100 is 11300 really 11300 or is it a typo?
  • Create New...