tested quickly - it's actually worse, now not only usb devices are not powering up, but also not detectedby gt - Debian
Hi! Here are dmesg logs. Is it enough, or serial log really important? Also, no ic2 and no usb...by gt - Debian
Here's lsusb output, if that's of any use: http://sprunge.us/Nrp9oJby gt - Debian
Yep, red flashing. I do beleive that the engineer who made this device had some quirks, is all am saying. And this is relevant for usb gpio.by gt - Debian
red none green default-on =green green none red default-on =red green none red heartbeat =red flashing green heartbeat red none =red flashing >Oh, that's not usable. MTD trigger is there because the kernel can control it for boards that have MTD LEDs (usually on >the motherboard, but not outside). It's not a third led, it is a trigger for red or greeen leds,by gt - Debian
I thought so, that the "both on" would produce orange, i.e. they would be independent, but no, it is not so. greeen default-on + red default-on = no led! green none + red none = red on Red mtd is one of triggermodes in /sys/devices/platform/gpio-leds/leds/wtplug\:green\:stat/trigger There's just one physical led, but it has two color modes. And by alike I meant, that mayby gt - Debian
No, no changes in USB But here's something interesting about leds: green and red leds are not independent. green default-on + red none = green on green hearbeat + red none = red flashing (maybe greeen then red flashing, green is way darker) green default-on + red mtd = green on, none on mtd iops Maybe usb logic is alike and non-evident?by gt - Debian
Can confirm LED works correctly! USB, though, acts weird: usb flash drives do not work [ 320.362159] usb 1-1.3: rejected 1 configuration due to insufficient available bus power usb hdd spins up, but does not detect partitions. Also, bash welcome line shows a hieroglyph instead of hashtag sometimes... That's new!by gt - Debian
Well, I transferred rootfs to ubfs on mtd, it boots and works OK. Bodhi, thank you a lot! If my bootenvs are of any use, I can post them here as well as nanddump of rootfs. But in overall it was as easy as adding mtd table to bootenvs, formatting biggest device as ubi+ubifs and transferring your rootfs archive. Then writing uImage (manually patched with experimental wtplug.dtb) to other mtd anby gt - Debian
ps looking at the names, i would guess USB INDicator and USB ReSet INDicator: the board has 1 led with red/green function, flashing red being "u-boot-mode" and green_on being "booted ok". Surprisingly, it works correct with kirkwood-silverstore-hncn2.dtb.by gt - Debian
Updated uImage, rebooted... Nope, sadly [ 17.231333][ T1] Waiting for root device /dev/sda1... I think l'll finish for today, and will try to move root to NAND flash - that suits my purposes better. Thank you a lot!by gt - Debian
U-Boot 2011.06 (Feb 22 2012 - 04:24:47) Promwad-PlugComputer SoC: Kirkwood 88F6282_?? RevID 0x01 DRAM: 1 GiB NAND: 1024 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0, devadr 1 88E1121 Initialized on egiga1, devadr 0 Hit any key to stop autoboot: 0 Marvell>> md.l 0xF1010000 8 f1010000: 01111111 00003300 33331100 33003by gt - Debian
Wow! Your help was fast and on point! eth0 worked inside debian, usb worked with hub ("[ 17.311402][ T1] Waiting for root device /dev/sda1..." when plugged directly) Output log: https://pastebin.com/wx3NbB7zby gt - Debian
I actually fiddled with u-boot, followed OpenWrt guide to replacing it to most recent working one for Kirkwood. It boots the board, but does not see usb or network. With stock u-boot I am able to read files from usb and use network upload. But it seems no support for UBI or ext4 So, maybe u-boot patch will be of some use (I think it is smaller than the kernel)by gt - Debian
>Which dtb file are you using? Have you tried each of the existing dtb files that support the 6283 SOC? Yes I tried all of those. Results vary a little, some use LED properly, some blink "faliure", but work. Some show 1 eth, some both. But no network and no boot wothout usb hub. >Which DTB you are using? Mostly openblocks a7, it shows both eth >Post the entire serialby gt - Debian
Also I found a USB-hub with external power supply. Using it, I successfully booted to Debian USB! Yay! But Ethernet ports are not working :( . They do register link, but fail to receive anything, just like OpenWRT images. Is there a way to create dtb from a patch that makes workable kernel 3.1.1, from manufacturer's archives?by gt - Debian
I added "usbcore.authorized_default=1" after reading https://www.kernel.org/doc/html/v5.19/admin-guide/kernel-parameters.html, but it did no goodby gt - Debian
I tried another usb drive, same result. Is there a kernel bootarg to ignore bus power warnings? I've found this: https://blog.famzah.net/2010/08/11/usb-rejected-1-configuration-due-to-insufficient-available-bus-power/ but unsure how to make kernel read it from u-boot bootargsby gt - Debian
>Do you have serial console connected (if this box has serial header)? Yes, I have connected terminal to UART >Try Silverstore or OBa7 dtbs Thanks for the advice! That helped to make some progress! I can see that the device boots to "Waiting for the rootfs device /dev/sda1" but then it stucks I deleted the "rootwait" part of u-boot arguments and now it outpuby gt - Debian
Hi! I am trying to upgrade an old vpn-box on 88f6283, but it only works with Squeeze it came with. I followed great guide by bodhi, but the booting of new system fails because the dtb is nowhere to be found. The u-boot is also stuck on obscure patched version from around 2010, and any attempt to replace it ends in usb+eth not showing, and only portion of 1gb ram visible. At this moment Iby gt - Debian