Mischif, > Including those modules seems to be almost all of > what is needed, the kernel seemed to recognize my > ethernet adapter but couldn't configure it > correctly and doesn't seem to recognize the > built-in flash. Cool! great progress. > [ 0.000000][ T0] Kernel command line: > rootdelay=5 root=/dev/sda2 raid=noautodetect > console=ttyby bodhi - Debian
> If it works, great board now like Swiss army > knife. Indeed! as Ray said, on paper, looks like that Express card should work. You guy made me want to empty out my old drawer of old gadgets to see if I can find one :)by bodhi - Debian
Kernel 6.2.8-mvebu-tld-2.2 I've added CONFIG_PHY_PXA_USB in the chance that it is carried over from PXA to MMP2/3 architecture. I also add device hsic1 (mass storage). However, we still need more info to make hsic1 fully complete, so it might not work yet. Download at Dropbox linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 md5sum linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 e0a3a488f7a4by bodhi - Debian
Gravelrash, > Bodhi - to allow this to boot from > mmc card, what changes would one have to apply to > the uboot please? I have a suitable sized usd card > in the adaptor and would like to attempt > this Unfortunately, there is no mmc command supported by this OpenWrt u-boot 2020.04!!! Commands starts with m md - memory display mdio - MDIO utility commaby bodhi - Debian
Mischif, Can you find out if there is GPL source for this Wyse 3020 box? either u-boot and/or kernel would be helpful.by bodhi - Debian
Mischif, > Did you find any missing modules to include? Not yet. But on the safe side, I will include more PXA modules in the next build. > Also, > could you create a new dtb file that changes the > status of the mass-storage section from "disabled" > to "okay"? The mass storage and the otg are enabled in the DTS &usb_otg0 { staby bodhi - Debian
Gravelrash, It's in the Wiki https://forum.doozan.com/read.php?2,23630 QuoteBooting Other Linux Distros on Pogoplug How to boot recent Arch Linux ARM rootfs with bodhi's released u-boot (with separate DTB) How to boot older Arch Linux ARM rootfs with bodhi's released u-boot (with embedded DTB) How to boot Void Linux with bodhi's released u-boot How to boot Aby bodhi - Off-Topic
Billy, > I had no success to boot successfully from several > days. You should read the thread backward and find the post where it was last successfully booted. The DTB used in that boot results in 2 HDDs present. And then you could run from the HDD 100GB partition rootfs. When you find that DTB, please post the link here so we can keep track of the good version. I think eitherby bodhi - Debian
tormentor, > I think we should try without systemd IMO, even if you run sysvinit the OOM might still occur (but it will log the usual error in dmesg). I think 2GB swap file would be a good solution to track down this problem to see if in fact there was a OOM and by which process.by bodhi - Debian
That pxau2o-ehci must be very old. Currently this is the driver Quote│ CONFIG_USB_EHCI_MV: │ │by bodhi - Debian
QuoteReviewing the old kernel boot logs Could you post the link to the log?by bodhi - Debian
Mischif, mmp3-usb-phy and mmp3-hsic-phy are already in 2.1 kernel. I'll take a look at pxau2o-ehci.by bodhi - Debian
@mrc333777, > what would i look for on this pogoplug series 4 > for the https stuff? If you cannot log in stock OS, then run kwboot with the u-boot-2017.07-tld-1 image in my release thread. And then boot into the Debian rootfs Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (26 Sept 2021) on USB. Basically bypass everything about stock, and go straight to Debian that way. And tby bodhi - Off-Topic
Mischif, > Reviewing the old kernel boot logs it looks like > usb is handled by the pxau2o-ehci, mmp3-usb-phy > and mmp3-hsic-phy modules, do you know if they're > currently being compiled in your kernels? Ah. I have to check. I know mmp3* are configured in as builtin modules (no need to modprobe). But pxa* belong to previous versions of the SoC.by bodhi - Debian
JousterLi, > I just tried with a 2.5" drive and it read > successfully. Subsequently trying with the > original 3.5" drive also worked just fine. I'm not > sure what happened because I definitely remembered > one of my first troubleshooting steps being > re-seating the drive. Embarrassed but want to > confirm that nothing is wrong with the SATA > cby bodhi - Debian
Here is tld-2.1 kernel. Download at Dropbox linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 md5sum linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 ed9fd513ca5a6bfaf118992f0feec0b7 linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 sha256sum linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 7885b743bdba35dd8fb884b722407632ff55837698901e995f7da1071be8cb98 linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2 This tarball contaiby bodhi - Debian
QuoteAverage already begins to grow. And at LA around 14, a reboot occurs. I don't want to sounds like a systemd hater :) but now I see systemd as PID 1, my wild guess is it killed the system in OOM situation withtout a notification. My suggestion is if you are usually stress the system like that (btw, I like how you utilize it to the max), you might need to use a 2GB swap file on HDD.by bodhi - Debian
JousterLi, I took a look at the u-boot-2017.07 for this board. There is nothing abnormal about the SATA configuration. And I don't recall anybody has reported this issue, either. Is the HDD a 3.5" HDD or 2.5"? if it is 3.5", can you try a 2.5" HDD? ======= I might release rc 2023.04 version for this board and the Pogo V4 board (requested by another forum membby bodhi - Debian
QuoteOnce Openwrt is installed and booted, login and modify your u-boot variables to include the following, copy and paste if you wish, but i don't advocate doing it blindly - it should work, but be certain you have backed up your uboot environment variables before you start using the fw_printenv command from the Openwrt console setenv bootdev usb setenv device '0:1' setenv sby bodhi - Debian
Gravelrash, QuotePrerequisites : Openwrt installed on the Device following the instructions here Prerequisites : rootfs prepared on usb key using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 following the instructions here The 2 links were swapped above (1st link is Debian rootfs link).by bodhi - Debian
Billy, > I tried the last DTB but the box crashed again (i > think it's a crash) > I don't understand why it crashed either if i > didn't change anything before this try with new > DTB. Perhaps saving the DTB with a datetime stamp would be a good idea so we know which version. - Try booting the DTB version in the release rootfs. - Are the 2 fans runningby bodhi - Debian
tormentor, I don't recall anybody reported about OMV 6 experience here before.by bodhi - Debian
glw125, > So I did. Did you set up envs in serial console like I mentioned above? QuoteYout don't need to change u-boot. Treat OpenWrt u-boot like stock u-boot. And follow this instruction: Boot Kirkwood rootfs with stock u-boot https://forum.doozan.com/read.php?2,102054,105374#msg-105374 If you did and Debian did not boot, then post the entire serial bootlog here.by bodhi - uBoot
Mischif, Thanks! > Looking back through the 6.2 logs I never see the > kernel try to bring up USB, is it possible > something missed getting compiled in? Indeed, this kernel default to no USB enabled. Will upload the tld-2.1 version. Also, the bootargs should be: param="rootdelay=5 root=LABEL=rootfs console=ttyS2,115200 raid=noautodetect earlyprintk=serial" Theby bodhi - Debian
Grzegorz, Yout don't need to change u-boot. Treat OpenWrt u-boot like stock u-boot. And follow this instruction: Boot Kirkwood rootfs with stock u-boot https://forum.doozan.com/read.php?2,102054,105374#msg-105374 And you need to do Step 4 in the Debian rootfs installation. === Once you have booted Debian, there are more envs adjustments if you want to dual boot Debian on Uby bodhi - uBoot
Boot with the new DTB I've posted above.by bodhi - Debian
Mischi, Please describe what you did to set up the rootfs. And what is the content of the wloader.conf, where it resides. And, ls -lart /bootby bodhi - Debian
LeggoMyEggo, > Latest kernels seem to get internal wifi and bt > working again based on latest experimentation with > my pair. Thanks for the report!by bodhi - Debian
Billy, Here is the new DTB. Please try again the same test, kwboot, with 4 HDDs in the slots. =================== Are the 2 fans running right now in your box? - BTW, you can trim down the kwboot log like this. root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image.by bodhi - Debian
Mischif, Please post the serial header location, and pinouts. And post the entire serial boot log (from uboot banner until when the kernel hang).by bodhi - Debian