So you have serial console connected? Putty with serial? Putty works fine for me, but you need to be careful that the line wraps are "clean". Maybe go full screen with the window. I usually copy and paste from the forum; you have to drag to the right to get all of the long lines. If you go off to the right, the quote box will scroll right. I do it one line at a time; thereby mikeh49 - Debian
QuoteIf you want both USB and SATA drive to have the real rootfs on each, then the partition label must be different. They should not be the same (i.e. rootfs). So if the SDD partition label is sata_rootfs Good to know. If they are different, then a rootfs USB can be plugged in while running on the SATA drive. Right? Also, if you do this you have to update fstab as well. BTW, I now haveby mikeh49 - Debian
It looks to me like your next to last line should be bootcmd 'run kernel_config etc and then remove the last line. Mine never sets bootcmd as a variable, It is only a direct command, if that makes sense.by mikeh49 - Debian
With a random Fat32 USB with a bunch of files on it, here is the relevant part of the boot: Quote[....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon[ 38.745960][ T1469] random: avahi-daemon:) . ok [....] Starting NFS common utilities: statd idmapd. okby mikeh49 - Debian
Thanks, good info. Does haveged get itself linked in so that it runs during boot such that the random number is available when ssl starts? I suppose so, otherwise what would be the point.by mikeh49 - Debian
Who knew all this random stuff was going on! I can see why it stalls at the ssl start as it needs a random number for seeding, I guess. From the Arch wiki: QuoteIf you are not sure, whether you need haveged, run: # cat /proc/sys/kernel/random/entropy_avail This command shows you how much entropy your server has collected. If it is rather low (<1000), you should probably install havby mikeh49 - Debian
Here's the relevant part of the log, 35 to 145 seconds: QuoteStarting Avahi mDNS/DNS-SD Daemon: avahi-daemon[ 35.342548][ T1466] random: avahi-daemon: uninitialized urandom read (4 bytes read) [ ok . [....] Starting NFS common utilities: statd idmapd[ ok . [....] Not starting NFS kernel daemon: no exports. ... Starting NTP server: ntpd[ ok . [....] Starting OpenBSD Secure Shell servby mikeh49 - Debian
An "interesting" development after I copied my 5.2.9 buster filesystem from USB to the internal flash card (partitioned 4GB rootfs, remainder data). Booting now stalls for about 2 minutes, usually after the starting the sshd service. The serial log got lost today, but contains "urandom warnings". A little research came up with this: https://unix.stackexchange.com/questionby mikeh49 - Debian
A bit off topic, but I need some advice from the community. I plan to use the M300 as a music server with an internal SSD. There will be a 8GB root file system partition with the remainder of the 120GB drive a second partition for the music files. Should this second partition be ext3 or ext4? Does it even make a difference? I use a Windows box for preparing the music files, tagging, etcby mikeh49 - Debian
Nice. I have another M300 on the way and this will be a concise way to get it set up. Thanks for the instructions.by mikeh49 - Debian
I just got LMS running on the Dell Kace M300 using Bohdi's Jessie file system and his 5.2.9-tld-2 kernel for the M300, following (more or less) the process from @notoneofmyseeds. I created the /usr/share/squeezeboxserver/... directory structure and extracted the "compiled armel version" into the 5.20 directory. Turns out this compiled version is only the perl 5.20 modules for armby mikeh49 - Debian
Now that we have the M300 running well, I'd like to install the Logitech Media Server. But, there seems to be no meaningfull instructions for Debian Buster; the best I can find is the wiki here for Jessie. So, can we run this new M300 kernel with a Jessie or Stretch filesystem? I'll search the Kirwood filesystem thread for Jessie, but perhaps someone knows which version it is. Also,by mikeh49 - Debian
Take a couple of days and nights off, bohdi. I have the M300 booting from the internal flash drive with a solid white light and no serial intervention. i think we're ready to put this thing to work. Thanks also to Neal and David.by mikeh49 - Debian
It would be nice if we could have this on when successfully booted. Now it blinks very rapidly. Tape is a solution, of course, but would be nice to know at a glance that it is indeed running. I have a 120G SSD on the way for use as a music server, replacing a Pogo E02 and a USB hard drive.by mikeh49 - Debian
Here's an SSD in the M300. I think you would definitely need a pad on the bottom cover to hold the drive in position; when the enclosure is right side up, the drive hangs down from the connector. There might be another way to secure it; duct tape? It sits pretty level on the 2 screw posts. Or, if you could get adapter/extender cables the drive could be located and secured differently.by mikeh49 - Debian
@Neal - that's a much better place, makes good sense. I'll wait until the community coalesces on a location before tackling the pleasure of long u-boot command lines on Putty with a serial connection. @Bohdi - so the protect off is "forever"? Or does it revert to on at the next boot? Hence the need to immediately set them permanently in Debian.by mikeh49 - Debian
It boots into stock by adding this to the set_bootargs_stock environment: Quotesetenv mainlineLinux no The whole thing is: Quoteset_bootargs_stock 'console=ttyS0,115200; setenv mainlineLinux no; mtdparts=spi_flash:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) root=/dev/sda1 rw I don't know if this is the best place to do this, but it works. I think it's a good idea toby mikeh49 - Debian
kernel_config sets mainlineLinux to yes, the stock OS has it set no. Also the stock boot commands load the kernel and ramdisk to different addresses than set in kernel_config. Debian uses the addresses in kernel_config. I tried the to use these addresses for stock, but no-go. From what I can tell, bootcmd runs before anything else and runs kernel_config first. Thus, mainlineLinux is yes whenby mikeh49 - Debian
I thought you had it, but it still won't boot into stock: Quoteâ–’ __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |by mikeh49 - Debian
Set up booting Debian from USB without serial and it went well and reliably boots into Debian from the usb. After upgrading, I had to rebuild the uInitrd, and that was really snappy. Shorter that I remember from building it the first time. Then I tried booting into stock with the Debian usb removed, and this doesn't work: QuoteDiag completed Hit any key to stop autoboot: 0 Bootingby mikeh49 - Debian
Thanks, Bohdi. Looks great. I'll try it on Saturday.by mikeh49 - Debian
My quick reaction is that pulling the SSD doesn't seem easier than setting up serial. If someone is comfortable with pulling the SSD and has an adapter, they probably have a USB serial adapter as well. Especially if they're into these little boxes. But, if the SSD approach is a better/easier technical solution, then of course that's the way to go. Getting into the Pogo plugby mikeh49 - Debian
U-boot tools seem to be in stock OS as fw_printenv works. Summarizing where we are: -Prepare a USB with bohdi's latest 5.2.9-tld-2 kernel and file system -Connect serial to M300 -Boot into bohdi's file system setting u-boot commands through serial -Change root password in stock OS by mounting internal SSD and using CHROOT -Edit /etc/ssh/sshd_config to enable listening in othby mikeh49 - Debian
Good work, Neal! OK, got ssh working in stock OS per the above, but also had to edit the /etc/network/interfaces file to set the the eth0 interface to dhcp. It was static 192.168.2.1 or something like that. My network is 192.168.1.x.by mikeh49 - Debian
Post last year on ssh from the web interface: QuoteJDS420 In order to enable ssh the way Dell intended, you have to enter a "tether key" which allows customer support to ssh into the box and undo/fix anything someone may have broken. Without a legitimate key, you have you purge all openssh packages and reinstall them. You might have to remove the kace-tether app too, but it's beby mikeh49 - Debian
Bohdi posted this in June 2018: QuoteI did it the easy way. After I've booted with the Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs, I mounted the internal SATA drive root partition and chroot into it, and reset root password. So now I can login to the box stock OS as root, if needed. With this clue, I did the same and can log in as root with my password, via serial, of courby mikeh49 - Debian
All good now, running 5.2.9 -tld-2 kernel and 5.2.9 filesystem. Took less time than my screwing around yesterday trying to save time. Story of my Linux experience. I'm also ready to get rid of the serial connection if we can. I have root access to the stock OS.by mikeh49 - Debian
OK, that's what I figured. Thanks and sorry for the bother. I wasn't sure that it was OK to replace the kernel on a running system and thought it was safer to do it off-line.. Got it now, I hope.by mikeh49 - Debian
Foolishly did an apt-get update and apt-get update and got the initiramfs issue that you address in the update thread: Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.12.1-kirkwood-tld-1 Looks to me that it updated the 4.12.1 image file, but I'm running 5.2.9. How should we/you/me handle this? -rw-r--r-- 1 root root 7713498by mikeh49 - Debian