@spiderdijon, I've updated Steps 4-6 in the installation post above. Please try, and post serial console log here.by bodhi - Debian
That looks promising. It might take a few tries to get it to boot successfully but should be easy. I'll write the Steps in a separate post.by bodhi - Debian
Jader Marasca, > I'd love to use it as a server/docker/... but I'm > a hardware newbie so I'd need instructions about: > 1) how to get a new SO on a new disk (a new > 120/240 SSD) .. may I use DD from another linux > machine to write to it and later replace disk > inside M300. Where can I get a .img ready to > transfer to new SSD ? You can install tby bodhi - Debian
@sudos, Thanks! all good points. I'll update the release notes to include your recommendation. BTW, - Marvell CESA: agreed as your edit said. - kirkwood_thermal: this module only works with the M300, afaict. Other boxes Kirkwood 88F6282 SoC seems not working properly, perhaps because they have their own method for thermal. So it might also be a good thing not to confuse the userby bodhi - Debian
@someguys561235 Thanks!by bodhi - Debian
Booting the MVEBU (Armada 37x, 38x, and XP) boards with stock u-boot. 1. Create the Debian rootfs on a USB stick, using the tarball Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 (16 Dec 2023) from the Linux Kernel MVEBU package and Debian armhf rootfs release thread. Or use whichever the latest rootfs in the release thread. In rootfs installation Step 3, the DTB you need to use must be forby bodhi - Debian
spiderdijon, Yes, this box is supported in mainline Linux. So I'd expect it can be supported here easily (if the u-boot used in this box is a bit newish). Let me write a summary of steps to get it to boot Debian in the next post.by bodhi - Debian
dhargens, > 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 drive needed. One of my M300's is booting this way. Post your current u-boot envs and Iby bodhi - Debian
> Is there an easy way to get a working webinterface > for configuring NFS share, or would it all have to > be via SSH/Serial? We set it up manually through SSH. Quotehttps://forum.doozan.com/read.php?2,23630 (Wiki thread) NFS NFS - HowTo set up NFS shares (and boot NFS rootfs), see also Debian 12 (bookworm) settings Boot your Dockstar (and other plugs) using NFS rootfs,by bodhi - uBoot
> You are correct, I've saved the envs.. Sorry. Not at all. We all have been there done that :) > I created the boot.scr now and it seems to be > working! Cool! > Now instead of me doing more bad things, would the > next correct step be to flash? > https://forum.doozan.com/read.php?3,135222 > "B. Flashing Instruction:" Yes, I would flash 202by bodhi - uBoot
FIS, > I've not seen any step in the guides to change the > envs? During booting with kwboot we should not save the envs. But you apparently did save the envs while booting 2023.04-tld-1 version. Perhaps without knowing it would cause problem, you ran the command saveenv at u-boot prompt. Am I correct? Now the envs are no longer consistent. It is not appropriate for 2017.07-tby bodhi - uBoot
> I've tried with both uboots already. Looks like your envs are messed up! did you save the envs at all? kwboot again, interrupt the countdown and, printenvby bodhi - uBoot
FIS, Your USB rootfs creation steps looks good. And there is no problem with your USB stick. Try again with this combination: - kwboot the u-boot 2017.07-tld-1 version - attach the USB rootfs to one of the two USB 2.0 ports in the back - And boot I will explain it after you got it to boot this time.by bodhi - uBoot
FIS, > But, I cannot get it to boot of the USB. Please post the entire log of the kwboot session when you try to boot the USB Debian rootfs.by bodhi - uBoot
FIS, If you still have trouble creating the USB rootfs, copy and paste here the entire terminal session log on the Linux host when you did this. Perhaps I will be able to see some mis-step.by bodhi - uBoot
FIS Wrote: ------------------------------------------------------- > Ahh, ok so Debian would be installed onto the > nand, I thought it would be running of the USB, > having uboot on nand. Is the reason you need uboot > just to get it to run it off the USB for the first > time? I just don't see why one couldn't make a > debian image and flash directly, but againby bodhi - uBoot
> What I have not yet found is how I flash the > u-boot to the nand, because I have to reuse kwboot > every time I turn it off now. And is the > uboot.2023.04-tld-1.nsa325.bodhi.tar image better > to use as it's newer? Does it matter? Log into Debian, follow the instruction in the u-boot release post to install to NAND. And for the initial installation, it does not matby bodhi - uBoot
FIS, > No idea what binary it was. Found it here > https://forum.doozan.com/read.php?2,61344,134363#msg-134363 I see. I think it was not tested thouroughly because not many people use Windows. > What version of Linux would you recommend? I would recommend Linux Mint. But Mint is a Ubuntu derivative. So Ubuntu is fine. Basically, you need to format the drive at command linby bodhi - uBoot
> Before this I ran > kwboot from Windows 10, thus ttyS2. Not a good idea. Which kwboot binary were you using? was it compiled on Windows? > Never connected the 3,3v pin so serial is not > fried. But for some reason Windows would get > stuck/do nothing when running the kwboot command. I would avoid using Windows apps for things Linux-related. Just install a Linux VM forby bodhi - uBoot
ksuszka, > @bodhi I'm not sure if I understood correctly. > Should we test it with released kernel 6.5.7 and > only modified kernel boot params or something else > should be changed? > > If it is the first case then I attach two logs, > from two boots which differ only in kernel boot > param. In both cases the behaviour of dumping mtd > is the same - evby bodhi - Debian
Ok so it was my mistake. The DTS clearly/badly stated spi1 but I overlooked (BTW, the non-standard naming convention used by the author here). ssp1: spi@d4035000 { compatible = "marvell,mmp2-ssp"; reg = <0xd4035000 0x1000>; clocks = <&soc_clocks MMby bodhi - Debian
I've just noticed your kwboot command: kwboot -t -B 115200 /dev/ttyS2 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Why it is /dev/ttyS2? Usually it is /dev/ttyUSB0 on most Linux host, or /dev/ttyAMA0 on the rPi. See: https://forum.doozan.com/read.php?3,51739,51919#msg-51919by bodhi - uBoot
> Found a way to flash the firmware from software > after all :) Cool! > [*] Followed > this > guide to bind the spidev driver to spi1.0. So I missed that fact! spi1 is the device. QuoteCompiled this kernel from the mmp-armada-drm-5 branch Built uImage for the kernel Successfully booted into Debian Do you have a boot log for this run? that could be very helpful.by bodhi - Debian
QuoteI have serial connection (which was what I used to erase it) Even the NAND is completely erased, kwboot should work for this box. Quote> Am I supposed to connect the 3.3V pin? No. If you had connected the 3.3V pin before, then that could have fried the serial port. ================ Some ideas: - Make sure the serial connection wires are away from the power cord. Sometime iby bodhi - uBoot
QuoteOn a sidenote, I found this extremely promising repository from the creator of linux-mmp, Lubomir Rintel. It seems like he even got the DRM drivers working, and his DTS is much more complete. It looks like this repo's kernel is a work-in-progress. Even the latest DTS seems to be a working version.by bodhi - Debian
> OK. I did not think it would have made a > difference either, but worth a try! I'll take a > look at this driver to see if there is anything > strange. I've looked at the Winbond SPI driver and did not see anything peculiar.by bodhi - Debian
msh493, > When I try to connect to the board with screen > /dev/ttyUSB0 115200 I get a blinking cursor. And > that's it. I can't get to firmware prompt. What > have I done? :) And how do I get back to being > operational? I would love to learn how to try > different images to learn the process. Right now > I'm kind of confused. You need to connectby bodhi - uBoot
FIS, > > I have an older NSA325v2 I decided I wanted to get > Debian on. I found some different posts here on > the forums and decided to give it a go. To cut it > short, I wanted to update the u-boot and somehow > managed to erase the nand, and now it won't do > anything. > I have serial connection (which was what I used to > erase it) but is there a wby bodhi - uBoot
Kernel linux-5.4.268-oxnas-tld-1 package was uploaded. See 1st post for download link. And please create a new thread for questions or problem in installation.by bodhi - Debian
CyberPK, I'm hesitate to restore the driver to what it was before, given what was said in the email thread. QuoteFrom: Mikulas Patocka The driver drivers/crypto/marvell/cesa/cipher.c uses GFP_ATOMIC allocations (see mv_cesa_skcipher_dma_req_init). So, it is not really safe to use it for dm-crypt. GFP_ATOMIC allocations may fail anytime (for example, they fill fail if the macby bodhi - Debian