Topics created by William Scott

@crispyoz I was already at a point of unable to duplicate. Turns out I did some of the same actions you did, so between us I think we've figured this out to the extent it needs to be figured out. Have a great day! --Bill

@György-Farkas This problem was never figured out. Had to re-flash both devices to again make them accessible. However, you made a point about timing. I wasn't as patient as you. As such the first access to each device "post" upgrade wasn't actually post upgrade. This put both devices in some sort of munged up state. I'll attempt to force upgrade again, but this time chill out until the upgrade is over. thanks!! --Bill

@Douglas-Kryder @ccs-hello One more point. I've not yet metered the O2+ in the troubled dock configuration. Have only "known" lack of power up by lack of LED, basically not knowing all of the facts. Just got out a USB-LVTTL converter. Will connect later today to tty0 in breadboard dock to see if I can reflash. If so, the O2+ device may emerge from some hosed up state that prevents full boot, or perhaps even continuation past very early boot, to come up in a healthy state that will work in all configs. --Bill

@Zheng-Han I will indeed!

@cas Yes, you are right - the key: edit the the first post Thanks!

@Chris-Stratton You're right. I had just figured this out. thanks! Bill

Just upgraded several packages including libubus. [ 4.489247] usbcore: registered new interface driver usb-storage [ 4.499070] kmodloader: done loading kernel modules from /etc/modules-boot.d/* [ 4.516900] init: - preinit - [ 5.069174] usb 2-1: new full-speed USB device number 2 using ohci-platform [ 5.367204] rt3050-esw 10110000.esw: link changed 0x00 Press the [f] key and hit [enter] to enter failsafe mode Press the [1], [2], [3] or [4] key and hit [enter] to select the debug[ 5.569477] random: procd: uninitialized urandom read (4 bytes read, 10 bits of entropy available) level [ 7.998915] jffs2: notice: (401) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 8.023692] mount_root: switching to jffs2 overlay [ 8.062463] urandom-seed: Seeding with /etc/urandom.seed Error relocating /lib/libubus.so: uloop_cancelling: symbol not found [ 8.202992] watchdog watchdog0: watchdog did not stop! [ 8.208847] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 8.208847] [ 8.219687] Rebooting in 1 seconds..

Jeff, You did indeed nail it. My error was I was working so much in the ssh world for a few hours that it didn't occur to me until late that this was not an OS issue but an application issue. Setting up key pairs, no matter how many times I've done it, is so damn error prone that a repetitive motion disorder takes over. I would add for others making this trip that a global change may benefit them. In my case the actual command was: git config --global core.sshCommand "ssh -i /root/.ssh/id_omega255f.pem" I had expected to see a /etc/git/ directory get created with a config file for the global change. Not so....apparently done somewhere else. Maybe some day (like later today) I'll need to find it. 8^o thanks again!! Bill

@György-Farkas Thanks a bunch! I was stuck as I didn't have an oscilloscope at the time. I ordered one right away and received it the following week. Your response was already in hand. I "knew" there was the incompatibility as I knew (absolutely) the O2+ 3.3V system and many years of RS-232. However I couldn't find any specifics in the Omega docs of the actual device interface. Your answer confirmed what I knew. However your answer was much better as it provided a candidate solution to the incompatibility. thanks!! Bill

@William-Scott ... click 'Edit' and look at the blinking cursor please.