@sudos, https://forum.doozan.com/read.php?2,35581,135216#msg-135216by bodhi - Debian
Response to sudos on the Dell Kace M300 thread. https://forum.doozan.com/read.php?2,61344,135215#msg-135215 This is where the orphan sysvinit scripts can be installed: Quoteapt-cache show orphan-sysvinit-scripts Package: orphan-sysvinit-scripts Version: 0.14 Installed-Size: 80 Maintainer: Debian sysvinit maintainers <debian-init-diversity@chiark.greenend.org.uk> Architecture:by bodhi - Debian
I've uploaded a new tarball. In this I updated the envs related files (u-boot kwb image is the same). The envs was updated slightly to correct typos. The envs image was updated to avoid misleading error message during flashing. uboot.2023.04-tld-1.pogo_v4.environment.img uboot.2023.04-tld-1.pogo_v4.environment uboot.2023.04-tld-1.pogo_v4.boot.scr This should be the final update.by bodhi - uBoot
dhargens, > I'll be glad to help when I return on the 5th or > so. OK cool! in the mean time I put this warning in the 1st post until I can figure out some weird message while flashing the default envs image. QuotePlease do not use. I'm revising this installation instruction and upload new version Things look normal in using, but nandwrite output some message that coulby bodhi - uBoot
I think we might not be done yet (my mistake in the envs image). So stay tume.by bodhi - uBoot
> They are infornation only, not errors. Wish I can > suppress them, but I can't :) I migth be able to make them less noisy. But that will be some day when I can revisit this subject.by bodhi - uBoot
Ah I see that was your question in a post before. QuoteHere's a non-truncated log of a boot with a USB 2 drive in the top port. I note that there's more error messages ("Bad device specification") when loading envs from usb & sata - but I don't know why. They are infornation only, not errors. Wish I can suppress them, but I can't :)by bodhi - uBoot
dhargens, > And here's a non-truncated boot from the rear port > using a USB 3 drive. It too has errors in the same > place as above. I don't see any error in this log. > Loading envs from usb 1... > ** Bad device specification usb 1 ** > Couldn't find partition usb 1:1 > Can't set block device > Loading envs from usb 2... > ** Badby bodhi - uBoot
That truncated log is not good! When you post the good log, please also do this in Debian. cat /proc/mtdby bodhi - uBoot
xanatos, In the past there were GPL issues with SECCOMP so I did not include it. It seems those issues have been resolved, so I will see if it can be enabled in the next kernel release (6.3.x).by bodhi - Debian
Hi dhargens, > > It boots from either USB 2 or 3, and seems like > a > > perfectly functioning system now. I have the > boot > > logs and can include them if you'd like. > > Cool! no need to post log. But keep them in safe > place in case we need to see it again. Please post the boot log. I'd like to double check a few things.by bodhi - uBoot
See the entire discussion in this thread: https://forum.doozan.com/read.php?4,54044 My suggestion: https://forum.doozan.com/read.php?4,54044,135056#msg-135056 Quotebodhi With this type of problem, the best I can suggest is to stay with 4.14.198 for now if you run Debian. Don't know when I will build Debian kernel 5.15.x, but that's my plan.The EOL date for 5.15.x is Oct 20by bodhi - Debian
snickerweb, > I tried to put the rootfs on the HDD. > Unfortunately then the HDD idle does not work when > swap and rootfs are on the disk. I think use the > USB Stick for Rootfs/Swap in the future. :( Yes. Roofts cannot go to sleep. But swap file is OK. When the system is idle there is no swapping going on. So use the USB for rootfs, but create a 2nd swap file on the HDD, anby bodhi - Debian
gennnarino, This problem occured before the kernel booting. Likely somehow u-boot determined that there are only 512M available (could be one out of 2 RAM chips is faulty). You need to connect serial console, boot and post the entire serial console log here.by bodhi - Debian
> I was happy early.)) > I think the problem is in OMV6. All this time I > haven't accessed the OMV6 web interface. > Today I tried to log into the web interface and > immediately got a system reboot. That makes sense. BTW, because you are running systemd which has binary log (journald), during a problem like this it is harder to pinpoint where it occured. With aby bodhi - Debian
Use only the 1st post for installation, and ignore the testing done in subsequent posts.by bodhi - uBoot
I've updated the first post: Overview, and uploaded new tarball to include boot.scr (therefore hash values change).by bodhi - uBoot
Glad to hear! That was a weird problem. ps -deaf > /tmp/ps.txt Can you attach the ps.txt here in a post. The pics are quite useless because the only processes on the screen were captured.by bodhi - Debian
Hi Robert, > I have one working DNS320L and 2 non-working ones > that have this blue flashing light issue Can you run kwboot with the working box?by bodhi - uBoot
> I have a 2nd V4 with 2017.07 on it, so thought I'd > update it. I did something new this time - I > followed the instructions! (It works a > lot better that way!) > I made several thumbs for booting, and on this one > (it's hard to keep track) doesn't look like the > /boot.scr is there - and it doesn't need it > either. Right! you don'tby bodhi - uBoot
To dual boot Debian and OpenWrt. setenv bootcmd_openwrt 'nboot 60500000 0 440000; bootm' setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_openwrt; reset' After testing both ways of booting, save the envs setenv bootcmd_openwrt 'nboot 60500000 0 440000; bootm' setenv bootcmd 'run bootcmd_uenv; run sby bodhi - Debian
Right, what I said above QuoteNow you already have OpenWrt on NAND, you can go one step further and set up the envs to dual boot Debian on USB and OpenWrt on flash. So now what u-boot had you install? is that OpenWrt u-boot? you current envs are for booting Debian only. So you have erased the bootcmd for OpenWrt. Please do this: with the Debian USB rootfs attached, power up, and let it bby bodhi - uBoot
Here is the updated boot script. I've had a wrong mtdparts in the script before. It was setenv mtdparts "mtdparts=orion_nand:2M(u-boot)ro,3M(uImage),3M(uImage2),8M(failsafe),112M(root)" Should be setenv mtdparts "mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)" Please try again.by bodhi - uBoot
dhargens, > I seem to remember somewhere here about having to > unlock a write-protect setting, but I'm not > finding it to reference. Did I hit that problem > here, or is it something else? No, it is not related to that. Let me look at my script again.by bodhi - uBoot
> It booted fine - found the uboot script /boot.scr > and continued onward. Cool! This is another major enhancement but I did not want to advertise it (it's not relevant to what we do here, and it'll take some detailed explanation). > Here's the console log to the boot prompt: It looks good. > > So at least now it boots fine. Do I erase the NAND >by bodhi - uBoot
QuoteSounds good. Maybe my mistake will help others when they see what screws up when you don't read, eh? Right on! also it is an opportunity to test this script. It should be an important part of your Debian rootfs. ===== The script is attached to this post. Mount the USB rootfs on another Linux box. Assuming it is mounted at /media/sdb1. cd /media/sdb1/boot cp -a uboot.202by bodhi - uBoot
6. I wrote the new environment.img to NAND: root@deb03:/tmp# /usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.environment.img Writing data to block 6 at offset 0xc0000 no error. Did you erase the NAND block first? Quote6. Flash default u-boot envs image If you are upgrading from 2017.07-tld-1 u-boot, you can skip this step. But some envs will need to be updby bodhi - uBoot
> debain however still makes problems from usb with > the new u-boot dtb_file env was not set correctly. Power up, interrupt serial console countdown, and setenv dtb_file /boot/dts/ox820-stg212.dtb bootby bodhi - Debian
QuoteOn another HDD I have successfully started archlinux. :) It worked :) U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) Cool!by bodhi - Debian
snickerweb, > I also tested archlinux but is the same: > in the log it always reports that it does not find > /dev/sdx although USB storage is detected. > i tested /dev/sdX but openWRT say my stick is > sda1 /dev/sdx meaning it could be /dev/sda1, /dev/sdb1,.... x here is a shorthand to say: whatever the drive letter is, replace x with that. > with "nano /prby bodhi - Debian