Connecting of a monitor in OpenWrt Displaylink in OpenWrt We will connect the monitor using of USB video adaptor displaylink. The current version of OpenWrt doesn’t include a complete support for displaylink, therefore there could be some difficulties on different stages which we try to get over. Before starting I would like to provide you with a link which helped me. Perhaps in the next versions of OpenWrt it won’t be so actual, but at this moment after cloning the repository from here, we can get a lot of additional applications for OpenWrt. For adding of a new application to the OpenWrt let’s copy it to the directory OpenWrt/package and by next starting of make menuconfig it will be already included to the contents of package. Ok, let’s start.
I don’t know how I can state the information in an easily accessible form for all of you. I try to tell you the mile stones)). Manipulations with video images in Linux are realized using the frame buffer. What that is, is well described in the documentation for the option CONFIG_FB in the kernel of Linux. In order that the device displaylink can work with frame buffer we have to include the support of this option in the kernel (FB_UDL). In order that we can see anything on the display we have to include the support of the virtual console in the kernel.
What that is you can also read in HELP for the option CONFIG_VT. There also should be the console support on the virtual terminal and optionally the support of the capability of binding and unbinding console drivers. War Thunder Hack Golden Eagles No Human Verification Free more.
ALIX system boards; Summary: The PC Engines ALIX series of system boards. Not included), 1 serial port (console). Required for prepared images).
We should also to specify that the console has to be connected to the frame buffer. And the console of the frame buffer has to be selected automatically by the main output device of the image. Now let’s resume all this by using of the concrete kernel options.
Hi Brett, thanks for your feedback! I do not have a 750GL at my disposal, so I can only speculate. However, based on the specs of the RB 750GL and the commits in the OpenWRT repositories, I think that there is a pretty good chance. I assume that the bootloader works much the same way, so the procedure for the RB 750 should apply to the RB 750GL. However, as said, this is pure speculation and has not been tested by me. If however you are successful in flashing your RB 750GL, please tell me!
Always happy to help! Hi, thank you for the information on how to connect to the RB750, that was new and useful infroamtion to me. On actually loading a new firmware onto the router you can make yourself your life A LOT easier by using the wget2nand utility.
All of steps 3 – 6 for the rb750 and 4-7 for the rb411 (and other mikrotik routers) are handled by that tool. All you have to do is host the two files, openwrt-ar71xx-nand-rootfs.tar.gz and openwrt-ar71xx-nand-vmlinux.elf in one directory on a webserver, and type wget2nand and the tool will do ALL of the above tasks. Once finished, all you have to do is reboot the router (and switch to nand boot on device with serial access like the rb411 or rb450x devices like in step 8 above). I applied this guide to a routerboard omnitik U-5HnD, I got the following lines. I can ping 192.168.1.1 but telnet 192.168.1.1 command advertise me: “Unable to connect to remote host: Connection timed out”. “Jul 4 09:20:08 loris-desktop dhcpd: BOOTREQUEST from 00:0c:42:cd:5b:72 via eth0 Jul 4 09:20:08 loris-desktop dhcpd: BOOTREPLY for 192.168.1.1 to routerboard (00:0c:42:cd:5b:72) via eth0 Jul 4 09:20:08 loris-desktop atftpd: Serving openwrt-ar71xx-nand-vmlinux-initramfs.elf to 192.168.1.1:50817 ” Thanks for your help.