I would point out that and older version of Arch might be findable and installable, but can't update it since Arch has dropped support for the hardware. I was initially running Arch on mine (btw), but since it can't be updated I've moved to Debian and been happy with it. This community supports Debian as a focus, and is very helpful. I'm happy with Debian and it works well forby dhargens - Off-Topic
I have the original feet on it too! The top USB drive is quite hot in operation, and even when a drive is on the back ports it's warm too. I'd hoped a slower speed would help it. No worries though. It works.by dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > However, I'd not worry much about the power > saving. I don't think the lower CPU frequency will > save that much electricity anyway. If any gain to > be had, I think it's the thermal, which is more > significant since it will run cooler. I'd agree - thermal reduction is what I was hby dhargens - Debian
Sorry for the delay in responding. Yes, it does stay at 200 when set to 'powersave'. I'm using linux-cpupower instead of cpufrequtils, but it works the same. # cpupower frequency-set -g powersave # cpupower frequency-info analyzing CPU 0: driver: kirkwood-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by soby dhargens - Debian
Update: installing linux-cpupower didn't seem to make a difference in CPU frequency - it constantly sits at 800MHz. It could be that this little thing is taxed already so it'll never throttle down, but I have no way of knowing that or confirming it.by dhargens - Debian
While digging around for answers, I also found the package 'linux-cpupower', which seems to have replaced cpufrequtils. According to https://wiki.debian.org/CpuFrequencyScaling: cpufreq is being replaced by cpupower. ...and https://packages.debian.org/bookworm/linux-cpupower: The cpupower command allows inspection and control of cpufreq and cpuidle tunables for hardware that supportsby dhargens - Debian
I just learned about 'cpufrequtils' from a discussion here, and having installed it on a Kace M300 and have it work as expected, I also set it up on a Pogo v4 - but it doesn't throttle down, it's always at 800MHz. Rebooting didn't affect it (didn't expect it to, but always try all things). Here's the outputs on the Pogo v4: # cpufreq-info -p 200000 800000 oby dhargens - Debian
[ Response was not needed either. ]by dhargens - Debian
[ Post was not relevant to this thread, so removed it and created a new topic. ]by dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > I would carve out 20 GB for rootfs. Some of my 10 > year old rootfs has reached 12 GB (with lots of > old kernel files). Even after cleaning up, they re > still 8-9 GB usage. Cool. Thanks for that guidance. That's up next!by dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > > So, if I take the next step and carve out a 1G (or > > so) partition on the SSD, label it as rootfs, > > install the kernel & everything needed to get it > > to boot, can it boot without needed the USB drive? > > Yes. It will boot the SDD rootfs with the new > u-boot, no USB drivby dhargens - Debian
> - kirkwood_thermal: this module only works with the M300 I missed this pointer - how do I load/enable this module on my M300?by dhargens - Debian
sudos Wrote: > as a closing note, I'm also noticing > popularity-contest still isn't installed > and enabled by default .... > > At time of writing, armel on popcon totals 227 > users. I'm sure that only counts a miniscule > fraction of the users that have installed any > rootfs archives from this forum and the number can > be much higher, at lby dhargens - Debian
Hi all! I've got this working with Bookworm, and booting off the USB thumb drive. I swapped the internal SSD on this box with a bigger, useful one. It works great, and does what I need, basically. I've also been reading the posts about how to set up booting with kernel files on USB and rootfs on HDD/SSD. (https://forum.doozan.com/read.php?3,135972,135972#msg-135972) So, if I takeby dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > BTW, even though currently u-boot cannot load > kernel files from SATA, you can run the box with > SATA rootfs: booting with kernel files on USB, but > the entire rootfs for the system is on one of > these SATA partitions. Basically, the USB can be > used for booting only, and the system is on SATA. &by dhargens - uBoot
I'm back, and have another problem with a stock uboot on a fresh P4 and trying to boot in any configuration. No matter what I throw at it, it simply will not complete the boot. Since it's a first time installation on a stock P4, I'm using instructions posted in https://forum.doozan.com/read.php?2,12096 from the section "Updated 26 Sept 2021", using Debian-5.13.6 (bulby dhargens - uBoot
It seems to work now and boots as expected. Thanks for the help!by dhargens - Debian
It seems the box is now running the new uboot: U-Boot 2022.04-tld-1 (Mar 20 2022 - 18:15:15 -0700) Dell KACE M300 However, since the thumb I have in it is set up for a Stock uboot on ext3 filesystem, it throws this error: [ 7.840186][ T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- I'll set up ext4 on another thumb with the normal roby dhargens - Debian
daviddyer Wrote: ------------------------------------------------------- > fw_env.config is wrong... Ok, I corrected it to reflect yours, and now fw_printenv works. I have no idea how it got wrong, since I didn't touch it. Here's the output: root@m300-sid:/boot# fw_printenv baudrate=115200 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; resetby dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > See if the mtds are defined properly (they should > be already defined when you boot Debian rootfs > with stock u-boot). > cat /proc/mtd > cat /etc/fw_env.config Here's the results: root@m300-sid:/boot# cat /proc/mtd dev: size erasesize name mtd0: 0007f000 00001000 "uboot" mtd1: 00by dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > Ignore this error message. Go ahead and continue > the installation Ok, I did that and things were looking promising. But then there were no envs found. root@m300-sid:~# flash_unlock /dev/mtd0 flash_unlock: error!: could not unlock device: /dev/mtd0 error 95 (Operation not supported) root@m300-sby dhargens - Debian
rayknight Wrote: ------------------------------------------------------- > It appears that you did not follow the > instructions at > Kace > M300 U-Boot post. Quoting from the post: > > 1. Unprotect the SPI flash > Note that this is needed to be done only once from > stock u-boot. > Boot with serial console, interrupt u-boot count > down and unprotecby dhargens - Debian
Now that I have a stable install from 5.13.6 --> 6.3.8, I wanted to update the uboot - but can't get past Step 1 in the update instructions. It says to interrupt and protect off all, then boot, and then in Debian run flash_unlock /dev/mtd0. Well, that fails as shown below. # flash_unlock /dev/mtd0 flash_unlock: error!: could not unlock device: /dev/mtd0 error 95 (Opby dhargens - Debian
rayknight Wrote: ------------------------------------------------------- > It appears that you may not have used the latest > rootfs image > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > to create your boot disk. Using that would give > you bullseye and you could then use the standard > Debian upgrade process to upgrade to bookworm if > desired. You could alsoby dhargens - Debian
Next question: is it stuck at buster, or can I go to bullseye on this - or did I miss a step yet again? root@debian:~# cat /etc/debian_version 10.13by dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > You are booting with stock u-boot. So you need to > install the new kernel with step 4b. > 4b. Boot with DTB file embedded in the kernel > image.Again, this step 4b is for stock U-Boot > only. Well, of course I missed a step! Sheesh. Follow the instructions correctly and it works!by dhargens - Debian
Hi all! This is my first time working with the Kace product - I usually spend my time in the Pogo V4 chain because I have a few of those. I have a serial connection set up to track my steps. This is a stock uboot at the moment - that update will come after kernel 6.3.8 is completed. Following the instructions, I set up a rootfs for 5.2.9 on a Cruzer Ultra 3.1, moved it to the Kace and complby dhargens - Debian
bodhi Wrote: ------------------------------------------------------- > Those were very good tests! I think it's all come > down to the top port (USB 2.0) in this box. Finally I got you something useful!! I don't doubt your reasoning a bit - I think it's the top (EHCI) port screwing up too, because 2 drives in the rear ports seem to work fine. If there's a USBby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > No, the above test did not work as expected > either. Note that you have only 2 USB storage > drives. Should be 3 drives. > > My test was working fine with 3 drives. So my > conclusion is most probably the Sandisk Ultra 3.0 > drive has some unknown quirks. I could see where I was unclear thereby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > Please run this test. > > - 64G Ultra or 32G Ultra rootfs attached to one of > the rear ports. > - 16G or 32G 2.0 Fit formatted completely (use > fdisk to wipe the drive first) as Ext3 data drive > attached to the other rear port. > - 16G or 32G 2.0 Fit formatted completely (use > fdisk tby dhargens - uBoot