@Lazar-Demin Also, why is uboot even aware of usb mounts during boot? I thought that generally, /etc/fstab was cleared out? Is it possible that we could fix this by making opkg a little better at running packages off of usb, and ignoring them when usb isn't present/mounted?
Did you follow the guide at: https://wiki.openwrt.org/doc/techref/opkg to effect installations to externally mounted drives. They seem to mention, specifically, that each startup script needs to:
Libraries installed along with those packages are also installed to the external filesystem. This causes the programm [sic] not to start during bootup.
You need to manually set the LD_LIBRARY_PATH in each 'external' startup script:
@Antonio-Ramos I've built in the necessary kernel modules to support Human Interface Devices (HID) over USB.
Run oupgrade -force to grab build 216 that has all of the required updates.
If anyone is interested, the modules added were:
Some instructions on using a HID with the Omega:
Once the device is plugged in, dmesg will show something along these lines:
[ 923.700000] usb 1-1.4: new low-speed USB device number 9 using ehci-platform
[ 923.830000] input: BTC USB Multimedia Keyboard as /devices/platform/ehci-platform/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C313.0008/input/input4
[ 923.840000] hid-generic 0003:046D:C313.0008: input,hidraw1: USB HID v1.10 Keyboard [BTC USB Multimedia Keyboard] on usb-ehci-platform-1.4/input0
[ 923.920000] input: BTC USB Multimedia Keyboard as /devices/platform/ehci-platform/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C313.0009/input/input5
[ 923.930000] hid-generic 0003:046D:C313.0009: input,hiddev0,hidraw2: USB HID v1.10 Device [BTC USB Multimedia Keyboard] on usb-ehci-platform-1.4/input1
You can then run lsusb to see more info on your device:
Bus 001 Device 002: ID 0835:8500
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0835:8501
Bus 001 Device 009: ID 046d:c313
Bus 001 Device 005: ID 0835:8500
Bus 001 Device 006: ID 0835:8502
My keyboard was mapped to device 9 (I'm using a powered USB hub), so the Device 009 ID matches the identifier for Logitech keyboards.
Take a look at /proc/bus/input/devices for more info on the keyboard you've plugged in:
I have the same issue and I'm currently making a new topic for it (Lazar asked me to do this after I first posted to the ticketing system).
A friend and I managed to hack into the omega by interupting the boot sequence an replacing init with sh. Then we were able to see the crypted password, wich in turn googled to the string '5up'. This seems to be the OpenWRT standard root password.
@Theodore-Borromeo You won't need to email us manually to be assigned a secret token. Once we've released the cloud integration, you will be able to log into a page on our website where you can manage and generate new secret tokens.
@Shamsul-Tehahmad The Omega has only 1 set of UART port and it is reserved for the Linux terminal. Your best option right now is to use a 3.3V USB to Serial adapter an plug it in to the USB port on the Expansion or Mini Dock.
@Sawyer-McBride Yup, it will be released fortnightly. We are actually constantly making changes to the Console. We just want to first get into the habit of releasing Console updates regularly, and then we can adjust the frequency of the updates to suit the community
I've decided to make a new reply.
Minutes ago I've tested to connect my Omega and my T520 without limitations to the 802.11b/g/n. What shall I say? It just works fine for both devices, so there seems to be some problem with my router at home.
Therefor I'd say that this problem is solved.
Thanks to everybody who helped me!