bodhi Wrote: ------------------------------------------------------- > > > Is this SSD formatted Ext3 or Ext4? > > > > Both are formatted Ext4. Next time it comes up > and > > fails, i'll try to get a console running to > > capture the issue for clarity's sake. > > I hope you did a "finalize" ( (no lazy_init) when > youby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > Is this SSD formatted Ext3 or Ext4? Both are formatted Ext4. Next time it comes up and fails, i'll try to get a console running to capture the issue for clarity's sake.by sudos - Debian
Something to report... Even with adjusted envs to take care of the larger-than-11MB initramfs with 5.18.6, whenever I'm doing an update that requires the rewrite of uInitrd as outlined in the kernel thread, the M300 always wants to just not-boot afterwards. This also happened previously on older kernels as well, but only past 5.15. I'm not sure what the deal is, I don't have eitby sudos - Debian
Huh, was almost sure something somewhere said 2GHz.by sudos - Debian
bodhi Wrote: ------------------------------------------------------- > This USI Topkick has been done and should be on > the support list. > > There it is: > > QuoteLinux Kernel 5.17.x Kirkwood package and > rootfs for GoFlex Home/Net, Pogoplug > E02/Mobile/V4, iConnect, Dockstar, Sheevaplug, > NSA320, NSA320S, NSA325, NSA310S, NSA310, > Topkick, Netgearby sudos - Debian
daviddyer Wrote: ------------------------------------------------------- > Looks like kirkwood @ 2Ghz with DDR2 memory DDR3. 2x H5TQ2G83DFR-H9C chips. definitely DDR3. Hynix datasheet suggests in the naming matrix that this is a normal power consumption 256Mbitx8 with "commercial temperature range" and -H9* denotes DDR3-1333 9-9-9. Probably running that RAM at 1066 for what itby sudos - Debian
Searching around on eBay I came across a $12 very peculiar item mis-categorized in the industrial PLC section... and doing some digging in the forum search, doesn't seem like anyone has talked about this device before, so here we go: It seems to be made by Universal Scientific Industrial Co., as in the same USI that is the OEM of the Kace M300 that Dell contracted from them with no expensby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > There are a couple diferent ways. If flashing is > not possible in Debian, you can kwboot the stock > u-boot image, and that stock u-boot will be able > to unlock the SPI flash. I'm pretty certain that > is possible. Note that once you unprotect the > flash using stock u-boot, it stays unprotectedby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > you could have just flashed stock > u-boot back, start fresh, and solve this problem > in an easier way. I think I've mentioned this > before in my previous post. > > Most of the time, the KISS principle is the best > method. Hardware protection mode means the flash as a whole, all 100% oby sudos - Debian
We ended up fixing the problem... but it's a lot more in-depth than I was expecting to go. the SPI flash chip was so write-protected even the section that holds the normally read/write area with the write protect bits was write protected. I'm posting the write-up here so to be able to reference in case someone else has this problem down the line. Even with the installation guide rewritby sudos - Debian
...except on both of my kace boxes, I never sent the saveenv command, and yet I can't edit either of them. I know for a true absolute fact I didn't run saveenv at all as both of my envs on both local boxes were set from Linux only as per the instructions. I never did anything at the uboot prompt aside from "protect off all" and "boot" at the stock prompt. every otherby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > Yes. I know what's going on there. It's all > because the SPI flash was protected initially > (Dell engineers are too clever by half). > > Will get back to this thread and explain in more > details. > > In a nutshell, to start fresh we can always flash > stock u-boot back and frby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > After log in, flash the default envs image > following the instruction in new u-boot > installation. > > > flash_unlock /dev/mtd1 > flashcp -v > uboot.2022.04-tld-1.m300.environment.4K.img > /dev/mtd1 > > Expected output > > Erasing blocks: 1/1 (100%) > Writing datby sudos - Debian
yeah I get that, the problem is that he has the new uboot, but old envs. his envs from serial are as follows: M300> printenv baudrate=115200 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $(mtdparts) earlyprintk=serial bootargs_console=console=ttyS0,115200 mtdparts=spi_flash:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) root=LABEL=root rw bootcmd=run kernel_config; run seby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > I've started to write a new installation procedure > for this box. The simplest way is to install from > inside stock OS. I've had issues with partition alignment and weird issues of making the rootfs from within the stock debian install... but updating uboot, yes, 100% stable and proper way to go, tby sudos - Debian
Bodhi, I'm about to drop a blog post regarding the M300 up onto wordpress, and I'm noticing the install guide linked in the OP post is outdated. Would you be willing to update the guide post so it's up to date for mentioning the current rootfs and current 2022-04 u-boot build further up this page? it also seems I sold a few of my friends on buying one to mess around with, so havby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > The Kirkwood plug-form factor boxes (Dockstar, > Sheevaplug.... ) don't have thermal sensor. Yep, that's correct, and another justification to make sure those SoCs stay cool enough to keep happy. I know in the E02 the kirkwood is bare, as it is in the Pogo v4 as well. in the E02 just add a heatsink that fby sudos - Debian
After sending the last post I found a copper shim in my parts bin, I don't recall exactly where I got it from... but it was the right thickness to place between the SoC and the steel chassis being used as a heatsink. I believe it came from ebay nearly a decade ago to replace a thermal pad in a laptop that died before it could get the shim installed. for future reference, I believe the shiby sudos - Debian
Just chiming in to say 5.17.4 works properly on the Kace. and to reply to this of course. renojim Wrote: ------------------------------------------------------- > What I finally ended up doing (if I recall correctly) > was installing openjdk-8-jre from > https://packages.debian.org/sid/armel/java/openjdk-8-jre > . It's good enough for my purposes as I'd never >by sudos - Debian
did you make sure you had swap space set up? while an old PC would do the job, something a bit more power efficient like a dell kace which has more RAM available to it might be a better option now that there's uboot for it and most of the kinks are worked out (so long as you're using 5.15.5 for the kernel at time of post.) the problem of course is the old PC costs $0 and the Kace isby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > My recommendation. > > If you use SATA as rootfs, it should be a better > SSD or external HDD. The stock internal SSD is not > of good quality. > > I see error on some sectors sometime during boot. > It does not affect the system operation (it is > just a glorified USB type of flash withby sudos - Debian
renojim Wrote: ------------------------------------------------------- > What I finally ended up doing (if I recall correctly) > was installing openjdk-8-jre from > https://packages.debian.org/sid/armel/java/openjdk-8-jre > . It's good enough for my purposes as I'd never > use Java if I didn't have to for one particular > purpose. Looking at this andby sudos - Debian
renojim Wrote: ------------------------------------------------------- > As another data point, I've been running 5.16.5 > (and Bullseye) for a while now and I'm pushing my > M300 pretty hard with .... > ...and a pretty big Java (yuck!) process that runs > everyday and I haven't seen any problems. Can I ask how you're running Java? I haven't beenby sudos - Debian
yeah I just downgraded to 5.15.5 on the kace for now, Pogo v4 and E02 will continue on with 5.16.5. looking into it a bit further and it seems like kswapd panics are usually caused by the ram not pushing to swap fast enough or too fast... which shouldn't be the case here because of the overkill SSD. I had a shower thought earlier as to if this speculatively could be a byproduct of the SoCby sudos - Debian
A couple fun things happened over the past few days after the uboot upgrade. One was a kernel panic and the other was a situation where I rebooted the Kace and it didn't activate the eth interface properly and just sat there lights-out with the system LED solid white. I dropped syslog-ng on from the start so I've got logs of the panic but not much else: Mar 24 22:01:09 yamada kby sudos - Debian
bodhi Wrote: ------------------------------------------------------- > Attched is the new u-boot. This uboot image and > its default env image can be flashed to SPI mtds. > > uboot.2022.04-tld-1.m300.bodhi.tar > > sha256sum > 0aaa790377c6433396867dd26798f52e43541f2977d46537e0ce1a0df04b2cc8 > md5sum > 7986ddeac251018219e3d65851abbbb4 > > There are 3by sudos - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the new u-boot. This image can be flashed > to SPI mtd0. > > At the moment, I still have some problem flashing > the default envs image in Debian, so that will > come later. Success! changed root login, flashed the uboot image from stock Debian, set up a spare SSD with 5.13.6 and used aby sudos - Debian
dougdeep Wrote: ------------------------------------------------------- > Success at latest kwboot! > > I bungled an attempt to upgrade the 5.2.9 kernel > so had to start over with a fresh mSATA formatted > to ext3. Not quite the same kernel as yours but > close. does it still have the same no-boot behavior unless something is plugged into USB with the latest kernel/by sudos - Debian
bodhi Wrote: ------------------------------------------------------- > Here is the latest u-boot. is this also not flashable yet?by sudos - Debian
bodhi Wrote: ------------------------------------------------------- > So I was inspired by our forum members to figure > out this u-boot (when there is a will, there will > be a way :) > > Attached is the new u-boot: > uboot.2021.10-tld-1.m300.mtd0.kwb > > Create the uEnv.txt on your rootfs /boot. Below is > an example, adjust with your real MAC address, &by sudos - Debian