gnasch

Maybe you cannot see the whole screen on your monitor or TV. Access your Orange Pi via its IP Address on ethernet. For this try secure shell login from another computer. if Windows user use "putty ssh client" then report *exact* behaviour of patient. Our crystal ball is currently broken ;-) best, gnasch

Hello the orange pi's are not software compatible to raspi images. the docs are here: https://docs.armbian.com/User-Guide_Getting-Started/ best, gnasch

http://forum.armbian.com/index.php/topic/487-reinitiate-sd-card-resize-on-boot/ best, gnasch

If my OpiPc is any indication, for 8192CU first try depmod -a as root, or else build your module locally as per the documentation. maybe blacklist the rtl8192 module from the kernel. best, gnasch

Hm - sorry about all the problems. Maybe it would be best for the endusers to not upgrade without a way back. There is a thread in this forum about backup of sdcards. Is there a possibility to "force" or at least strongly motivate the users to not upgrade before at least a copy of the old sdcard has been made? About the money: maybe lead the downloaders to donate page first? Best wishes, and I appreciate! gnasch

http://forum.armbian.com/index.php/topic/998-xfce-in-spanish-or-any-other-language-different-than-english/?hl=language

Yes OpiPc works with armbian 5.20 on 1280x1024, I have it running, see here: http://forum.armbian.com/index.php/topic/752-tutorial-h3disp-change-display-settings-on-h3-devices/page-2#entry17461 If you like, I could try an image, but need instructions what to do or record. Thanks, gnasch

I am happy to report success when using native 1280x1024 resolution on an older Samsung 191T display using h3disp -m33 -d on an Opi Pc updated to 5.20. On the other hand the 8192cu driver delivered with 5.20 does not work, wireless only started to work after local recompiling and installation of the module as described in the documentation. Power to the device also had to be cut and reapplied. Thanks for the nice work! gnasch

According to Brother, your printer does not implement any printer languages like PCL or Postscript. It is a GDI Printer, where the rasterization is generated by a Windows driver on the PC. Source of this info: http://support.brother.com/g/b/faqend.aspx?c=at〈=de∏=hl2130_all&ftype3=2047&faqid=faq00000180_005 English: (slightly different) http://support.brother.com/g/b/faqend.aspx?c=us_ot〈=en∏=hl2130_all&faqid=faq00000180_005 On Brothers site you will find .deb files for download, which are meant to work on Debian. I found no information as to what Debian version are supported. No information on x86 / Arm support. Generally it is a bad idea to buy GDI printers, as they are only well supported in Windows. Better get one with PCL and/or Postscript support. I personally use Brother printers which have a Postscript emulation inside; they work well with all Linux computers after installing the corresponding .ppd (Postscript Printer Definition) file from Brothers site into CUPS. This does depend on neither Debian version nor CPU type.

script.bin or .fex is for 3.x legacy kernel. for vanilla 4.x kernel you have to use device tree. There is something about it at: http://forum.armbian.com/index.php/topic/385-banana-pi-usb-otg/#entry16721 hth, gnasch

Sorry to state the obvious: The file you linked is a 7-zip archive, it contains the image.raw, the PgpChecksum.raw.asc and armbian.txt with the license. You should boot from the .raw not from the archive. best, gnasch

Hi sagt3k did you read this: http://forum.armbian.com/index.php/topic/1614-running-h3-boards-with-minimal-consumption/#entry12475 best wishes, gnasch

turning off without using sync first, buffers not written to the sdcard?

There is a desktop version of armbian, but you may will have trouble with wicd, a GUI program that is supposed to help set up the network connections. When this happens, search for "tutorial wireless success" in this forums *titles*, then apt purge wicd and configure it by hand. Be sure to read the Docs: http://docs.armbian.com/ Please forget about configuring your system with the GUI. You will use the command line tools, and you will have to read, google and learn a lot, From a user perspective armbian is like debian and mostly like ubuntu. So general user instructions on these systems can often be cautiously adapted. Many of the problems you will encounter have already been solved in this forum, so use the search. best wishes, gnasch

try depmod -a

Hello Tkaiser, could you please elaborate a bit on these THS fixes? about 2 month ago i read in the forums that they had been submitted to the kernel. Are they somehow waiting for somebody to accept them or how does this work? thanks, gnasch

Nice image here: http://www.cnx-software.com/2015/09/26/status-of-orange-pi-boards-gpio-support/

I have this: http://www.ebay.com/itm/Realtek-RTL8188cus-USB-USB2-0-150Mbps-802-11b-g-n-n-Wireless-WiFi-adapter-dongle-/230973235744?hash=item35c713e220:g:fmEAAOxyFiRRz9v9 and this: http://www.ebay.de/itm/EDIMAX-EW-7811UN-Wireless-USB-Adapter-150-Mbit-s-IEEE802-11b-g-n-/380644550751?hash=item58a02ee85f:g:pJQAAOSwPcVVsogi both work fine. After updates, do not forget: depmod -a

try dpkg-reconfigure wicd (this is not tested, but should make a new config for it). apt purge wicd will remove wicd completely. apt install wicd will install it anew. Wicd does manipulate config without you knowing why and what. Best would be to configure it by hand as of here: http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/?hl=%2Bwifi+%2Bsuccess good luck!

The 0bda:8176 one seems identical to mine. Please try fresh unaltered armbian image for orangepi one. No need to compile module, as this is already included. The 0bda:8179 one I know nothing about. Why is 8188eu loaded?

Well I see a difference to my working config. I do not have 8188eu loaded, just 8192cu. But these are present too: rtlwifi 45784 0 rtl8192c_common 33420 0 mac80211 358429 2 rtlwifi,rtl8192c_common 8192cu 627893 0 they get loaded automatically when 8192cu is loaded, This is my lsusb with the dongle outwardly looking the same as yours. Please verify the USB ID and report back root@poisson:~# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@poisson:~# This is an orange pi pc. What is your board?

You do not provide a lot of information. Guessing is hard. with lsusb you can see what is your device. please show this. with lsmod you can see what modules are loaded. please show this also. what is in your /etc/modules-load.d/modules.conf ? thanks, gnasch

You may try an atx power supply from an old pc, and connect your OPI with one of these: http://www.ebay.com/itm/4pcs-30cm-1ft-DC-Power-Cable-4-0x1-7mm-DC-Tip-Male-Plug-Straight-CCTV-Cord-Cable-/321914510023?hash=item4af3999ac7:g:1H8AAOSw~bFWPew9 this way you can also connect your disks directly. if you have several power supplies please join their ground wires on the secondary side.

Yes, plus2 just has more memory. This should work. best wishes gnasch

had the same problem here, setcap cap_net_raw+ep /bin/ping executed as root, solved it, remains ok after boot.