Sorry for the delay. I tried this right away but didn’t get around to pressing results. I formatted a USB drive as ext3 and copied the whole rootfs with the broken idle dtb embedded in uImage. Tried both ext2load and ext4load, they both read the files fine and both resulted in the same crash with the same address. What’s bugging me is that usually it will only boot the uImage and then try aby megal0maniac - Debian
Nope, same thing. Eth link up and DHCP server handing out leases Process: - Boot without intervention ("press any key to stop autoboot" doesn't work anyway), wait for prompt - Set bootargs and attempt to boot (line 107) - Files are loaded and kernel is booted but not uinitrd (119 - 138) - Returned to prompt. Attempt to boot again (179) - Same failure, returned to prompt -by megal0maniac - Debian
bodhi Wrote: ------------------------------------------------------- > In that case, try connect Ethernet cable before > booting! Now there’s a novel idea! :) If it doesn’t panic then I will be truly confused, but I’m willing to try anything at this point. Will try and report back in the morningby megal0maniac - Debian
bodhi Wrote: ------------------------------------------------------- > So use either USB or HDD, but not both. See if the > random behavior will be gone that way. I’m only using the hdd. No usb plugged in > Regarding the kernel panic, try booting only with > serial console (unplug the ethernet cable) and see > far you will get it booting. This is just serial. Not boby megal0maniac - Debian
Sorry I took so long to get to this, haven't had a chance to look until now. Unfortunately it does exactly the same thing as before (log attached) so I don't think this is the issue. I confirmed that the only difference between that dtb and the one packaged with the kernel is the "broken-idle" line under coherency-fabric@21010 I'm not convinced about those addresses,by megal0maniac - Debian
Very strange... it fails in exactly the same way. I didn't provide a rootfs because it doesn't get far enough to switch, but I replaced the files on the USB stick and I get the same kernel paging request panic. I used the exact commands that osa used to generate uImage and uInitrd, with the latest dtb. I'm using the stock load addresses as well and the kernel is <5MB (it says uby megal0maniac - Debian
Okay, I went over this thread properly and see that I should be able to change bootargs once I'm booted into Debian and can use fw_setenv tool with osa's params. That will write the variable and fix the checksum. So it will only be a tethered boot the first time. Also, the difference between this time and last time is that last time I also had "junk in compressed archive" iby megal0maniac - Debian
Hi bodhi Unfortunately that doesn't seem to be the issue, the uImage/uInitrd load successfully and it hasn't gotten to the switch-root point by the time it panics. In any case, I re-formatted the drive with mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sda1 -L rootfs Once it was done, I ran sync and unmounted cleanly. I copied the images to the root again just in caseby megal0maniac - Debian
Hello Figured I'd post here rather than revive my dead thread (https://forum.doozan.com/read.php?2,36023,36023) I followed the instructions (kind of, my device never came with a disk so I used another Linux box) and prepped an hdd with the rootfs, latest kernel, and correct dtb baked into the uImage. Unfortunately, it's failing in a similar way to how it did in my previous thread (by megal0maniac - Debian
davygravy Wrote: ------------------------------------------------------- > I upgraded PiHole-FTL and the rest of the package > set... no hiccups. It looks like our Kirkwood > devices are finally supported in mainline PiHole. Really good to hear! I was considering running Pihole on a Dockstar, and thought to check here if anyone else had got it right first. What is the performanceby megal0maniac - Debian
And like magic it works! Thank you :) I see DSA is default now, which is nice.by megal0maniac - Debian
Huh, curious. It's the same failure that I see here: https://forum.doozan.com/read.php?2,36023,36037#msg-36037 Except with a non-null address: Unable to handle kernel paging request at virtual address 88000004 Not that it helps, as I shelved the MyCloud before resolving that :/by megal0maniac - Debian
I've also tried kirkwood-linksys-viper.dtb (since it's the same thing) and the one uploaded here: https://forum.doozan.com/read.php?2,26854,36051#msg-36051 Unfortunately all with the same result.by megal0maniac - Debian
When attempting to boot Debian, it kernel panics and I have no idea why. As has always been the case with the EA4500, I used step 4b to generate the uImage and uInitrd images as the old version of uBoot doesn't handle dtb files as a boot arg. I've tried the 5.2.9 which comes with the rootfs with both the dsa and the non-dsa dtb, as well as 5.5.1 (seems dsa has been dropped). Usingby megal0maniac - Debian
Interestingly, the dtb from your previous post (https://forum.doozan.com/read.php?2,26854,36051#msg-36051) works. Not sure of the difference between that one and the one in the latest kernel, but I have all 5 interfaces and can do fancy thinks like ip link set ethernet1 downby megal0maniac - Debian
I'm back! I thought I'd dust off the router and try and get DSA working again, but to no avail. Even with the latest kernel and the DSA .dtb, it fails with mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: could not detect attached switch mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: couldn't create dsa switch instance (error -22) Full boot log is here: https://paste.ubuntu.coby megal0maniac - Debian
No luck :( It couldn't read the kernel or the ramdisk: Marvell>> setenv load_dtb_addr 0x1000000 Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv usb_set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"' Marvell>> setenvby megal0maniac - Debian
Those addresses don't work :( Tried shifting it around a bit but I can't get it to boot. I had the most success with 0xa00000 0xf00000 where it at least started booting. Everything else seemed unable to read uInitrd.by megal0maniac - Debian
So I got this far. Embedded dtb in uImage (it loads, but still complains about unrecognized/unsupported device ID) It almost works... Marvell>> setenv bootargs $console root=LABEL=rootfs rootdelay=5 rootfstype=ext2 earlyprintk=serial Marvell>> usb reset; ext2load usb 0:1 0xa00000 /boot/uImage; ext2load usb 0:1 0xf00000 /boot/uInitrd; bootm 0xa00000 0xf00000 (Re)start USB...by megal0maniac - Debian
bodhi Wrote: ------------------------------------------------------- > So you just connected the ethernet cable to port 3 > ? or is it port 2? The interface names correlate to what's on the back of the router (internet & ethernet{1..4}) I just did ifconfig ethernet3 10.0.0.1/16 ifconfig ethernet3 up and it worked. When I plugged the cable in and the link lights came on,by megal0maniac - Debian
How sneaky, I didn't even notice that "viper" was there - I just tried "ea4500" and "ea4500-dsa" This looks promising (and new): [ 6.550319] Generic PHY mv88e6xxx-1:00: attached PHY driver (mii_bus:phy_addr=mv88e6xxx-1:00, irq=-1) [ 6.567104] Generic PHY mv88e6xxx-1:01: attached PHY driver (mii_bus:phy_addr=mv88e6xxx-1:01, irq=-1) [ 6.586107] Geby megal0maniac - Debian
Recently, I came into the possession of a WD My Cloud storage device (without a hard drive) I had a look inside: MV88F6720 (Armada 375) CPU, possibly dual-core 512MiB RAM Gigabit ethernet USB3 SATA 1MiB flash (for u-boot) Naturally, I now want to put Debian on it. The stock firmware (stored on the hard drive, which I don't have) was based on Debian Wheezy and had an ancient kernel.by megal0maniac - Debian
Turns out that the kernel is too big with embedded dtb. Loading uinitrd to 0x1200000 worked fine :) Too bad I'm stuck with this dumb stock u-boot. Thanks for the help!by megal0maniac - Debian
I'm 99% sure that I'm using the dtb packaged with the 4.11.3 kernel package (assuming that tar -cvf file.tgz overwrites by default) I'll check again but I don't think that is the problem...by megal0maniac - Debian
OpenWRT has always (since I've used it on this board, which was before the beginning of this thread) been capable of configuring VLANs through the web interface (or swconfig) I have no idea how it works, I tried running swconfig on Debian as well (non-DSA dtb, same one OpenWRT uses) and it doesn't detect the switch at all. I don't know enough about how it works to determine why.by megal0maniac - Debian
Thanks for that, handy trick! Here's the output. The only thing I've changed is updated the kernel, which I've done 100 times on the EA4500 and the Dockstar without problems. Might it be an issue with 4.11.3? I can try an earlier version if you'd like? Using the non-DSA dtb. ## Booting image at 00800000 ... Image Name: Linux-4.11.3-kirkwood-tld-2 Created:by megal0maniac - Debian
gets router out Give me what you've got :) OpenWRT seems to handle the switch quite well. I have yet to get DSA working on any of bodhi's builds, although I'm aware it's a work-in-progress. Pity that the wireless radios seem to perform so poorly (even with stock firmware) but that's an issue for another thread.by megal0maniac - Debian
Hey bodhi! Thanks as always for the updates. I'm playing with the EA4500 again, wanted to see if DSA is perhaps working in a newer kernel, but boot gets stuck here (with both .dtb files, with DSA and without): ## Booting image at 00800000 ... Image Name: Linux-4.11.3-kirkwood-tld-2 Created: 2017-06-21 18:47:17 UTC Image Type: ARM Linux Kernel Image (uncompressed)by megal0maniac - Debian
Me still! VLANs work on OpenWRT, just to reiterate. I don't know what black magic they're using, but running swconfig on Debian doesn't even see the switch chip.by megal0maniac - Debian
Cool, that makes sense. I am not able to make a .dtb out of the file you provided but comparing it to the one I'm currently booting with, I don't see any reason why this one would work if the other doesn't. My gut feeling is that it's an issue of not addressing external ports correctly. There seems to be incredibly limited documentation DSA, or utilities to debug it though,by megal0maniac - Debian