Piv Klit Posted November 23, 2017 Posted November 23, 2017 Quote at least I don't like to run stuff that matters with that outdated kernels) same here, like I said, thats why I wont use the pulpstone image, but if they are using Armbian, then maybe they will update in the near future.
ap17 Posted November 24, 2017 Posted November 24, 2017 I have a request to Igor. Dear Igor! The OS “19- Nov-2017 Testing image for Orange Pi R1 (4.13.14)” has the driver for 8189ETV (8189es.ko). As far as I understand, the mainlining of this driver was carried out by you personally. I ran this OS on my OPi-R1 only once, with the sole purpose of seeing how this driver identifies itself, nothing more. OK. In what my request consists: if it is possible, please, point me to or send me, maybe by e-mail, the sources of this your mainlined driver. Why do I need it? In mid-October, I completed my personal mainlining (4.14) of this driver (v4.3.18.1_15373.20151005) and now I’m using it for a month. On infrastructure and AP modes it works well (fine? – it will be seen in a month). But some aspects of this mainlining have been solved by me rather roughly, in my opinion. It’s technically interesting to me to see how you did it. Thank you in advance. By the way. Sorry for off-topic. Applying the same approaches to perform the mainlining … 1. … at the same time I have done my personal mainlining (4.14) of 8189FS driver (v4.3.24_15589.20151023) and now I’m using it on my OPi-P2E. The same words: on the above modes it works well, etc. It does not concern to mainlining, but doing it I found one nuance deep in 8189fs driver code, which causes a random assignment of the mac address, not affecting operation of the driver. The same code is present in 8723bs driver, but there it works correctly because of known features of this device. For 8189fs, this problem is still not solved, and I doubt that it can be solved at all with our knowledge of the details of the 8189fs device. 2. … a week ago I completed the mainlining of 8188EU driver (v4.3.0.6_12167.20140828) and now I’m using it on my OPi-PC. The same words again: it works well, etc. I also have mainlined (4.14) 8723bs drv. (v4.3.5.5_12290.20140916_BTCOEX20140507-4E40) for OPi-Prime and can share all my results.
zador.blood.stained Posted November 24, 2017 Posted November 24, 2017 9 minutes ago, ap17 said: if it is possible, please, point me to or send me, maybe by e-mail, the sources of this your mainlined driver. https://raw.githubusercontent.com/armbian/build/e8b0e6442a3a3b37ab73e02c06ecc0a579ba987d/patch/kernel/sunxi-next/90-02-add_rtl8189es-experimental.patch Originally copied from this repository which contains both 8189es and 8189fs: https://github.com/jwrdegoede/rtl8189ES_linux
ap17 Posted November 24, 2017 Posted November 24, 2017 On 11/24/2017 at 12:54 PM, zador.blood.stained said: Originally copied from ... repository which contains ... 8189es ... Thank you. I made a comparison of our works. They are almost identical. The same files have been fixed, not more, not less. But you did it more carefully.
Piv Klit Posted December 2, 2017 Posted December 2, 2017 On 23/11/2017 at 7:01 PM, tkaiser said: This whole stuff looks interesting. My only concern is the rather outdated kernels they use (for Raspberry Pi it's 4.4.50 and for the Oranges 3.4.113 -- at least I don't like to run stuff that matters with that outdated kernels) fulvio (The man behind Zeroshell) Are looking into migrating to Kernel 4.13.x The project looks damn cool.
tkaiser Posted December 2, 2017 Author Posted December 2, 2017 2 hours ago, DEHN.IO said: fulvio (The man behind Zeroshell) Are looking into migrating to Kernel 4.13.x If that's true then this is a clear indication to better stay away from this at all (since 4.13 is already EOL this means he doesn't take care about the kernel part at all and now only thinks about an upgrade to please concerned users). More thoughts here BTW: https://www.cnx-software.com/2017/11/30/zeroshell-firewall-router-linux-distribution-works-on-x86-hardware-raspberry-pi-23-some-orange-pi-boards/#comments 1
Michael Dehn Klit Posted February 16, 2018 Posted February 16, 2018 If anybody missed it, there is an openwrt image now. https://openwrt.org/toh/hwdata/xunlong/xunlong_orange_pi_r1 1
guidol Posted June 25, 2018 Posted June 25, 2018 On 11/23/2017 at 4:28 PM, guidol said: So this may be the first (and may be at this time the only) Orange Pi R1 with the NAS-Expansionboard "on the world" because I did not much with my OPi R1 (256MB Ram only) I moved my customized NAS-extension design from my OPi R1 to my OPi Zero Plus2 H5. Because I didnt got the right spacers I reused the ones which I used with the OPi R1 For getting all USB-ports recognized I had to enable usbhost1 in armbian-config/Hardware: usbhost 2 & 3 root@opi-zero-plus2-h5(192.168.6.25):~# lsusb Bus 006 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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub usbhost 1 & 2 & 3 root@opi-zero-plus2-h5(192.168.6.25):~# 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lrrr Posted October 26, 2018 Posted October 26, 2018 On 2/16/2018 at 3:07 AM, Michael Dehn Klit said: If anybody missed it, there is an openwrt image now. Is there an "official" way to install openwrt to spiflash? About the only thing I've found for installing to spiflash, is this: https://github.com/hyphop/miZy. 1
guidol Posted March 24, 2019 Posted March 24, 2019 On 10/26/2018 at 11:52 PM, lrrr said: Is there an "official" way to install openwrt to spiflash? About the only thing I've found for installing to spiflash, is this: https://github.com/hyphop/miZy. the following thread has instructions to flash u-boot to spi-nor-flash.... maybe you could use this to flash openwrt to the (on R1 = 16MB) spi-flash. But I dont know if you brik your R1 if you flash OpenWRT there and no u-boot. I used the instructions to flash a newer u-boot there to boot via usb: # ========================================================================================== nano /boot/armbianEnv.txt overlays=analog-codec spi-jedec-nor usbhost2 usbhost3 param_spinor_spi_bus=0 cat /proc/mtd apt install mtd-utils mtd_debug info /dev/mtd0 find / -name u-boot-sunxi-with-spl.bin ls -l /usr/lib/linux-u-boot-dev-orangepi-r1_5.77_armhf/u-boot-sunxi-with-spl.bin -rw-rw-r-- 1 root root 420961 Mar 24 11:38 /usr/lib/linux-u-boot-dev-orangepi-r1_5.77_armhf/u-boot-sunxi-with-spl.bin flash_erase /dev/mtd0 0 256 nandwrite -p /dev/mtd0 /usr/lib/linux-u-boot-dev-orangepi-r1_5.77_armhf/u-boot-sunxi-with-spl.bin dd if=/dev/mtd0 bs=1 count=420961 of=./current.bin cmp /usr/lib/linux-u-boot-dev-orangepi-r1_5.77_armhf/u-boot-sunxi-with-spl.bin ./current.bin # ==========================================================================================
Race666 Posted November 26, 2019 Posted November 26, 2019 Six days ago i installed Armbian Buster mainline based kernel 5.3.y, Armbian 19.11.3, Welcome to Armbian Buster with Linux 5.3.9-sunxi and latest update on an Orange PI R1. I have multiple kernel panics during some network operations: Starting OpenVPN or set a interface (wlan0) up down. Are there any known issues? Message from syslogd@localhost at Nov 26 09:06:13 ... kernel:[48503.690394] Internal error: Oops: 5 [#1] SMP THUMB2 kernel:[48503.799195] Process RTW_CMD_THREAD (pid: 1040, stack limit = 0x4f9a57 f2) kernel:[48503.805886] Stack: (0xc74eff28 to 0xc74f0000) kernel:[48503.810233] ff20: c85d5a00 d0a99518 d0a99518 cf184a 00 d0a98000 bfa95058 kernel:[48503.818402] ff40: d0a99518 bfa29827 d0a98000 c85d5640 d0a99518 bfa126 6b 00b7e151 cf184a00 kernel:[48503.826570] ff60: c74eff78 c8777cc0 c85d0c00 00000000 c74ee000 d0a980 00 bfa1257f ce667914 kernel:[48503.834738] ff80: c8777cdc c013339d 00000035 c85d0c00 c01332a1 000000 00 00000000 00000000 kernel:[48503.842905] ffa0: 00000000 00000000 00000000 c01010f9 00000000 000000 00 00000000 00000000 kernel:[48503.851073] ffc0: 00000000 00000000 00000000 00000000 00000000 000000 00 00000000 00000000 kernel:[48503.859240] ffe0: 00000000 00000000 00000000 00000000 00000013 000000 00 00000000 00000000 kernel:[48503.931490] Code: f43f af2d f8d4 2d3a (6e43) 429a kernel:[48503.941146] Kernel panic - not syncing: Fatal exception in interrupt
Recommended Posts