thank you for all the help

Ray,

> I recently purchased some Lexar 128GB SSD from
> Amazon
> for $10.49 that are a perfect fit after removal
> from case to mount in replacement of the stock
> 16GB device. Pictures attached.
> I suspect the 256GB, 512GB and 1TB versions would
> fit as well.

So this SSD case has 2 pieces glued togother, and you'd just pry them open, i.e no screws?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Ray,
>
> > I recently purchased some Lexar 128GB SSD from
> >
> Amazon
> > for $10.49 that are a perfect fit after removal
> > from case to mount in replacement of the stock
> > 16GB device. Pictures attached.
> > I suspect the 256GB, 512GB and 1TB versions
> would
> > fit as well.
>
> So this SSD case has 2 pieces glued togother, and
> you'd just pry them open, i.e no screws?

No screws, just pops apart with a little pressure around the seams.

Ray

> I recently purchased some Lexar 128GB SSD from
> Amazon
> for $10.49 that are a perfect fit after removal
> from case to mount in replacement of the stock
> 16GB device. Pictures attached.
> I suspect the 256GB, 512GB and 1TB versions would
> fit as well.

I tried this Lexar SSD in the M300 SATA slot. Nice form factor, but damn it is too slow! as slow as my USB flash drive. I guess we'd get what we pay for.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> I tried this Lexar SSD in the M300 SATA slot. Nice
> form factor, but damn it is too slow! as slow as
> my USB flash drive. I guess we'd get what we pay
> for.

However, perhaps it should be tried on another box so see if something about this board that has slowed it down.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> > I tried this Lexar SSD in the M300 SATA slot.
> Nice
> > form factor, but damn it is too slow! as slow
> as
> > my USB flash drive. I guess we'd get what we
> pay
> > for.
>
> However, perhaps it should be tried on another box
> so see if something about this board that has
> slowed it down.

i bought 3 different ssd drives, and did some bench marks on them. the 256 gig is really slow as well, like usb stick snail speed. if your interested i can do the other 2 again, which were really fast and give you the results from each and models. i only paid like 10-13 dollars each.

@mrc333777,


> if your
> interested i can do the other 2 again, which were
> really fast and give you the results from each and
> models. i only paid like 10-13 dollars each.

That would be great ! please do.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> @mrc333777,
>
>
> > if your
> > interested i can do the other 2 again, which
> were
> > really fast and give you the results from each
> and
> > models. i only paid like 10-13 dollars each.
>
> That would be great ! please do.


dont know how much this will help but this is the best i could come up with.
i used ontrack easy recovery disk diagnostics to get these numbers.

first set of numbers is from a usb 3.0 port, second set up numbers is from
usb 2.0 port.

old usb 3.0 Seagate FreeAgent GoFlex controller from an external drive
240 MB/s , 40 mb/s - inland professional SSD 120GB P/N: 120GBM
240 MB/s , 40 mb/s - CORE ortial.com , OC-150-128 128GB 6Gb sata ssd tlc
128 MB/s , 40 mb/s - oem ssd 256GB sata III ssd s3105 series

super speed usb 3 controller from some generic hd enclosure got the numbers from all 3 drives
usb 3.0 port 400 mb/s , usb 2.0 port 48 mb/s

old usb 3.0 Seagate FreeAgent GoFlex controller from an external drive

240 MB/s , 40 mb/s - inland professional SSD 120GB P/N: 120GBM
240 MB/s , 40 mb/s - CORE ortial.com , OC-150-128 128GB 6Gb sata ssd tlc
128 MB/s , 40 mb/s - oem ssd 256GB sata III ssd s3105 series

What is exactly the 240 MB/s and 40 mb/s in this benchmark? Are they sequential read and random read speeds?

Quote

i used ontrack easy recovery disk diagnostics to get these numbers.

I think it would be best if you plug in the SSD drives to the SATA slot.

Assuming the SDD is mount at /media/sda1.

Test write

cd /media/sda1
dd if=/dev/zero of=test_write.img bs=1G count=1 oflag=dsync

Test read

hdparm -Tt /dev/sda

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

The Lexar 128G SSD read speed in this M300 box is slow, but not too bad.

# hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   672 MB in  2.00 seconds = 335.35 MB/sec
 Timing buffered disk reads: 486 MB in  3.01 seconds = 161.65 MB/sec

The write speed is about half as slow as my spinning rust HDD on another box.

# dd if=/dev/zero of=test_write.img bs=500M count=1 oflag=dsync

1+0 records in
1+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 11.7481 s, 44.6 MB/s

Note that the "Timing cached reads" is also half as slow as of my spinning rust HDD on another box.

All and all, it's a great improvement over USB drive. But not up to the performance we usually see with regular HDDs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

mrc333777 Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > @mrc333777,
> >
> >
> > > if your
> > > interested i can do the other 2 again, which
> > were
> > > really fast and give you the results from
> each
> > and
> > > models. i only paid like 10-13 dollars each.
> >
> > That would be great ! please do.
>
>
> dont know how much this will help but this is the
> best i could come up with.
> i used ontrack easy recovery disk diagnostics to
> get these numbers.
>
> first set of numbers is from a usb 3.0 port,
> second set up numbers is from
> usb 2.0 port.
>
> old usb 3.0 Seagate FreeAgent GoFlex controller
> from an external drive
> 240 MB/s , 40 mb/s - inland professional SSD 120GB
> P/N: 120GBM
> 240 MB/s , 40 mb/s - CORE ortial.com , OC-150-128
> 128GB 6Gb sata ssd tlc
> 128 MB/s , 40 mb/s - oem ssd 256GB sata III ssd
> s3105 series
>
> super speed usb 3 controller from some generic hd
> enclosure got the numbers from all 3 drives
> usb 3.0 port 400 mb/s , usb 2.0 port 48 mb/s


Yeah that doesn't work, that controller may be USB 3.0 but the numbers I'm seeing there shows it's maxing out aganist a SATA II bottleneck. it's limited to 3Gbit and not 6Gbit. For an external spinner this is fine, as not many can go over 100MB/s, and no 2.5s on a consumer level can even reach that yet.

From the numbers I've seen, the lexar drives are fine, but lack DRAM cache. they'll be okay so long as you're not manipulating lots of small files which will create I/O overhead.

bodhi Wrote:
-------------------------------------------------------
> The Lexar 128G SSD read speed in this M300 box is
> slow, but not too bad.
Yes the Lexar NS100 SSD is not really meant for speed, it was designed as a cheap replacement for spinning disks. The controller is an embedded DRAM-less design which means it was designed for cost not speed. The Lexar NQ100 SSD is only slightly more expensive and should provide a little better performance, but also was not designed for speed.

Wanted to give a PSA to anyone looking to try the Cockpit web management package from main or backports on your Kace, it forcibly changes your init system to systemd upon install. On the Kace this isn't an issue because there's plenty of RAM, and no extra RAM seems to be used much, but on other systems with 128MB or 256MB of RAM this may pose a small issue later on. I didn't need to change any init scripts or anything in the uboot, it just worked as normal, which is weird to me. but it works, and cockpit works.

So far I didn't even notice it did this until like last week, and the same box just had a bookworm update with no issues to report aside from the ssh key being regenerated during update. As this is the test machine and the other Kace is doing things, I'm going to wait until bookworm goes full-release to upgrade everything else, but it seems like everything went smoothly so far using the 6.2.7 kernel.

In the future as more things get incorporated into systemd, as much as I'm against its existence, it's finally mature enough I think it'd be an okay thing to start transitioning over the rootfs images to systemd init completely, and have a different rootfs variant available for anyone that wants to stick with sysvinit (i.e. 128/256M RAM devices, 512+ shouldn't have an issue with systemd). So many packages are starting to rely on it that it is becoming quite a problem for anyone using sysvinit, to such an extent that any init scripts orphaned by the package maintainers that have wholly moved over to systemd are now in a separate package that likely won't last. Specifically Intel's IWD wireless daemon, which aims to replace the likes of packages like wicd, has such an init script that has been orphaned and is now included in such a script. I learned this the hard way many months ago utilizing it on my pogo v4 when wicd wouldn't start the network connection automatically and came to find out that it was super bugged.

@sudos,

https://forum.doozan.com/read.php?2,35581,135216#msg-135216

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 completed the installation, ran all the 'setenv' & 'fw_setenv' commands to set up booting, upgraded all 106 packages, rebooted a couple of times and everything appears well.

Next I do the steps to update to kernel 6.3.8 so I can take advantage of the 2G of memory.

One point: when it says to check the uInitrd size, it's right at 11M.

After the 6.3.8 setup is complete, I reboot and it halts. Here's the finale of its output:

## Booting image at 00800000 ...
   Image Name:   Linux-6.3.8-kirkwood-tld-1
   Created:      2023-07-20   3:18:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6122240 Bytes =  5.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-6.3.8-kirkwood-tld-1
   Created:      2023-07-20   3:18:30 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    10515277 Bytes = 10 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...


Error: invalid dtb and unrecognized/unsupported machine ID
  r1=0x0000020f, r2=0x00000100
  r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
Available machine support:

ID (hex)        NAME
ffffffff        Generic DT based system
ffffffff        Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.

I created a 2nd drive to confirm my steps were correct, and it fails in the same way. Now that I have 2 setups broken alike, it may not be me - unless I've missed a step (I've done that before).

So what did I do wrong? I have all the steps I went through so I can post anything you need about the boot.

dhargens Wrote:
-------------------------------------------------------
> 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 completed the installation, ran all the
> 'setenv' & 'fw_setenv' commands to set up booting,
> upgraded all 106 packages, rebooted a couple of
> times and everything appears well.
>
> Next I do the steps to update to kernel 6.3.8 so I
> can take advantage of the 2G of memory.
>
> One point: when it says to check the uInitrd size,
> it's right at 11M.
>
> After the 6.3.8 setup is complete, I reboot and it
> halts. Here's the finale of its output:
>

## Booting image at 00800000 ...
>    Image Name:   Linux-6.3.8-kirkwood-tld-1
>    Created:      2023-07-20   3:18:22 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    6122240 Bytes =  5.8 MB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> OK
> ## Loading Ramdisk Image at 02100000 ...
>    Image Name:   initramfs-6.3.8-kirkwood-tld-1
>    Created:      2023-07-20   3:18:30 UTC
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    10515277 Bytes = 10 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> 
> Starting kernel ...
> 
> 
> Error: invalid dtb and unrecognized/unsupported
> machine ID
>   r1=0x0000020f, r2=0x00000100
>   r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00
> 00 00
> Available machine support:
> 
> ID (hex)        NAME
> ffffffff        Generic DT based system
> ffffffff        Marvell Kirkwood (Flattened Device
> Tree)
> 
> Please check your kernel config and/or
> bootloader.

>
> I created a 2nd drive to confirm my steps were
> correct, and it fails in the same way. Now that I
> have 2 setups broken alike, it may not be me -
> unless I've missed a step (I've done that
> before).
>
> So what did I do wrong? I have all the steps I
> went through so I can post anything you need about
> the boot.

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.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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!

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.13

dhargens Wrote:
-------------------------------------------------------
> 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.13

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 also use the standard debian upgrade process to update from buster to bullseye, but that would take significantly more time than just creating a new boot disk using the Debian-5.13.6 rootfs.



Edited 1 time(s). Last edit at 07/20/2023 09:31PM by rayknight.

dhargens Wrote:
-------------------------------------------------------
> 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.13

What Ray said above will work.

However, since you already have the Pogo V4 rootfs, it is better that you'd just clone it:

https://forum.doozan.com/read.php?2,12096,24034#msg-24034

And use it for this M300 box (of course with the m300 DTB emebdded in uImage).

Also check the MAC address:

https://forum.doozan.com/read.php?2,25683,30100#msg-30100

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/21/2023 12:30AM by bodhi.

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 also use the standard debian
> upgrade process to update from buster to bullseye,
> but that would take significantly more time than
> just creating a new boot disk using the
> Debian-5.13.6 rootfs.

Yes, that's true - I didn't. I was following the installation post at https://forum.doozan.com/read.php?2,61344,90019#msg-90019 which uses Debian-5.2.9 in the release thread. I wasn't familiar enough with this M300 to know that 5.13.6 should work fine too.

I'll create another rootfs with 5.13.6 and go from there. Then I might jump to 6.3.8!

A question - when the apt upgrade creates the new initramfs, do I need to regenerate the uInitrd boot file like I do with the P4? I was unclear on if it's only P4 or all Debian versions we use.

Next step: update uboot from stock.
Are there any issues, and the latest uboot is clean?
Also, since I still have a stock M300 uboot, is something needing tested before I do that?

dhargens Wrote:
-------------------------------------------------------
> 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 also use the standard
> debian
> > upgrade process to update from buster to
> bullseye,
> > but that would take significantly more time
> than
> > just creating a new boot disk using the
> > Debian-5.13.6 rootfs.
>
> Yes, that's true - I didn't. I was following the
> installation post at
> https://forum.doozan.com/read.php?2,61344,90019#msg-90019
> which uses Debian-5.2.9 in the release thread. I
> wasn't familiar enough with this M300 to know that
> 5.13.6 should work fine too.

The instruction has not been updated since Debian buster.

> I'll create another rootfs with 5.13.6 and go from
> there. Then I might jump to 6.3.8!

Best if you clone the rootfs like I've mentioned above. No need to repeat the whole procedure.

>
> A question - when the apt upgrade creates the new
> initramfs, do I need to regenerate the uInitrd
> boot file like I do with the P4? I was unclear on
> if it's only P4 or all Debian versions we use.

It is applicable to all boxes, and Debian roofts.

>
> Next step: update uboot from stock.
> Are there any issues, and the latest uboot is
> clean?

No issue.

> Also, since I still have a stock M300 uboot, is
> something needing tested before I do that?

No need to do more testing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 (Operation not supported)

It's stock uboot on the M300, which I'm trying to upgrade.

Here's the log of the process:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: DB-88F6282A-BP LE 

U-Boot 1.1.4 (Jun 20 2011 - 13:16:26) Marvell version: 3.4.27
USISH-SMB Ver: kacemini-1.5

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CDBC0

Soc: MV88F1155 Rev 1 (DDR3)
CPU running @ 2000Mhz L2 running @ 500Mhz
SysClock = 500Mhz , TClock = 200Mhz 

DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000   size 512MB 
DRAM CS[1] base 0x20000000   size 512MB 
DRAM CS[2] base 0x40000000   size 512MB 
DRAM CS[3] base 0x60000000   size 512MB 
DRAM Total size   2GB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[512kB@f8000000] Flash: 512 kB
Good CRC!

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]


Running diagnostics ...

	DDR3 data bus test                               PASSED

	DDR3 address bus test                            PASSED

	DDR3 device test                                 PASSED

Diag completed
Hit any key to stop autoboot:  3  0 
Marvell>> protect off all
Un-Protect Flash Bank # 1
................................................................................................................................ done
Marvell>> boot
Booting Debian ...
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
........................................................................................................................................................................................

6133201 bytes read
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
....................................................................................................................................................................................................................................................................................................................................................................................................................
....
.........................................................................................................................................................................................

10337386 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-6.3.8-kirkwood-tld-1
   Created:      2023-07-26   4:03:03 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6133137 Bytes =  5.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-6.3.8-kirkwood-tld-1
   Created:      2023-07-26   4:03:09 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    10337322 Bytes =  9.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.3.8-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Wed Jun 21 02:30:10 PDT 2023
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Dell KACE M300
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Ignoring RAM at 0x70000000-0x80000000
[    0.000000][    T0] Consider using a HIGHMEM enabled kernel.
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000006fffffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000006fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000006fffffff]
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 454720
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) earlyprintk=serial
[    0.000000][    T0] Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 1785668K/1835008K available (12288K kernel code, 1697K rwdata, 5236K rodata, 1024K init, 301K bss, 49340K reserved, 0K cma-reserved)
[    0.000000][    T0] trace event string verifier disabled
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] 	Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0] 	Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000001][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.008518][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.016462][    T0] Console: colour dummy device 80x30
[    0.021663][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.032884][    T0] pid_max: default: 32768 minimum: 301
[    0.038768][    T0] LSM: initializing lsm=capability,integrity
[    0.044914][    T0] Mount-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.053039][    T0] Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.063406][    T0] CPU: Testing write buffer coherency: ok
[    0.071408][    T1] cblist_init_generic: Setting adjustable number of callback queues.
[    0.079373][    T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[    0.086411][    T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[    0.093591][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.100726][    T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[    0.106836][    T1] rcu: Hierarchical SRCU implementation.
[    0.112381][    T1] rcu: 	Max phase no-delay instances is 1000.
[    0.119806][    T1] devtmpfs: initialized
[    0.130221][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.140808][    T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.148675][    T1] prandom: seed boundary self test passed
[    0.156773][    T1] prandom: 100 self tests passed
[    0.161591][    T1] pinctrl core: initialized pinctrl subsystem
[    0.169713][    T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.176960][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.185713][    T1] audit: initializing netlink subsys (disabled)
[    0.193394][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.193728][   T16] audit: type=2000 audit(0.180:1): state=initialized audit_enabled=0 res=1
[    0.208976][    T1] cpuidle: using governor ladder
[    0.213831][    T1] cpuidle: using governor menu
[    0.218920][    T1] Feroceon L2: Enabling L2
[    0.223198][    T1] Feroceon L2: Cache support initialised.76 bytes, linear)
[    2.294486][    T1] UDP hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    2.301914][    T1] UDP-Lite hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    2.324695][    T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    2.344864][    T1] RPC: Registered named UNIX socket transport module.
[    2.351456][    T1] RPC: Registered udp transport module.
[    2.364375][    T1] RPC: Registered tcp transport module.
[    2.369755][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.394385][    T1] PCI: CLS 0 bytes, default 32
[    2.399303][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    2.406868][   T19] Trying to unpack rootfs image as initramfs...
[    2.883895][    T1] Initialise system trusted keyrings
[    2.895197][    T1] Key type blacklist registered
[    2.904607][    T1] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    2.911842][    T1] zbud: loaded
[    2.935472][    T1] NFS: Registering the id_resolver key type
[    2.941234][    T1] Key type id_resolver registered
[    2.954495][    T1] Key type id_legacy registered
[    2.959295][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.974469][    T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    2.982940][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  ¬ 2001-2006 Red Hat, Inc.
[    3.014895][    T1] fuse: init (API version 7.38)
[    3.020011][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    3.034718][    T1] orangefs_init: module version upstream loaded
[    3.040851][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[    3.172044][    T1] xor: measuring software checksum speed
[    3.199837][    T1]    arm4regs        :  1865 MB/sec
[    3.223284][    T1]    8regs           :  1119 MB/sec
[    3.250700][    T1]    32regs          :  1587 MB/sec
[    3.264481][    T1] xor: using function: arm4regs (1865 MB/sec)
[    3.270417][    T1] async_tx: api initialized (async)
[    3.284462][    T1] Key type asymmetric registered
[    3.289254][    T1] Asymmetric key parser 'x509' registered
[    3.484971][   T19] Freeing initrd memory: 10096K
[    3.518853][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    3.527226][    T1] io scheduler bfq registered
[    3.645158][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    3.653944][    T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    3.664464][    T1] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    3.674724][    T1] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    3.684627][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    3.694738][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    3.704822][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    3.714897][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    3.725486][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    3.736082][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    3.746665][    T1] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    3.757752][    T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    3.766012][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.772169][    T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    3.783011][    T1] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    3.793852][    T1] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    3.804685][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    3.812221][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    3.819234][    T1] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[    3.826871][    T1] PCI: bus0: Fast back to back transfers disabled
[    3.833126][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.842024][    T1] PCI: bus1: Fast back to back transfers enabled
[    3.848213][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.855568][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    3.861904][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    3.925260][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    3.936177][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    4.005258][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    4.016440][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    4.024832][    T1] printk: console [ttyS0] disabled
[    4.029854][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 28, base_baud = 12500000) is a 16550A
[    4.039582][    T1] printk: console [ttyS0] enabled
[    4.039582][    T1] printk: console [ttyS0] enabled
[    4.049425][    T1] printk: bootconsole [earlycon0] disabled
[    4.049425][    T1] printk: bootconsole [earlycon0] disabled
[    4.072507][    T1] loop: module loaded
[    4.077043][    T1] sata_mv f1080000.sata: slots 32 ports 1
[    4.084663][    T1] scsi host0: sata_mv
[    4.088828][    T1] ata1: SATA max UDMA/133 irq 29
[    4.095491][    T1] spi-nor spi0.0: mx25l4005a (512 Kbytes)
[    4.101168][    T1] 2 cmdlinepart partitions found on MTD device spi0.0
[    4.107865][    T1] Creating 2 MTD partitions on "spi0.0":
[    4.113384][    T1] 0x000000000000-0x00000007f000 : "uboot"
[    4.119544][    T1] 0x00000007f000-0x000000080000 : "u-boot-env"
[    4.126411][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    4.135009][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    4.160766][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    4.170702][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 18:03:73:41:da:d6
[    4.180767][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
[    4.187074][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    4.195687][    T1] orion-ehci f105000[    6.496132][   T19] scsi 1:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[    6.516237][   T28] sd 1:0:0:0: [sdb] 60125184 512-byte logical blocks: (30.8 GB/28.7 GiB)
[    6.540248][   T28] sd 1:0:0:0: [sdb] Write Protect is off
[    6.557873][   T28] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    6.595963][   T28]  sdb: sdb1
[    6.606573][   T28] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[    7.210911][  T142] usbcore: registered new interface driver uas
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext3 (1) -- /dev/sdb1] fsck.ext3 -a -C0 /dev/sdb1 
rootfs: clean, 20440/1880480 files, 397250/7515392 blocks
done.
[   17.847237][  T171] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[   17.933419][  T171] EXT4-fs (sdb1): mounted filesystem 9482f273-e7da-4434-8534-25d5e08e0cbc with ordered data mode. Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
Setting hostname to 'm300-sid'...done.
Starting fake hwclock: loading system time.
Current system time: 2023-07-26 21:28:40
fake-hwclock saved clock information is in the past: 2023-07-26 21:08:32
To set system time to this saved clock anyway, use "force"
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...[   20.494582][  T369] orion_wdt: Initial timeout 21 sec
[   20.746118][  T370] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   20.817874][  T370] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   20.966507][  T372] marvell-cesa f1030000.crypto: CESA device successfully registered
done.
Activating swap:.
[   21.882365][  T513] EXT4-fs (sdb1): re-mounted 9482f273-e7da-4434-8534-25d5e08e0cbc. Quota mode: none.
Will now check all file systems.
Checking all file systems.
LABEL=rootfs is mounted
Done checking file systems.
Log is being saved in /var/log/fsck/checkfs if that location is writable.
Cleaning up temporary files...Cleaning /tmp...done.
 /tmp.
Will now mount local filesystems:.
Will now activate swapfile swap, if any:done.
Checking minimum space in /tmp...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
[   23.864395][    C0] random: crng init done
Initializing random number generator...done.
Configuring network interfaces...Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/18:03:73:41:da:d6
Sending on   LPF/eth0/18:03:73:41:da:d6
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
[   27.325873][    C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   27.336518][   T17] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.1.229 from 192.168.1.254
DHCPREQUEST for 192.168.1.229 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.229 from 192.168.1.254
bound to 192.168.1.229 -- renewal in 40006 seconds.
done.
Starting RPC port mapper daemon: rpcbind.
Starting NFS common utilities: statd idmapd.
Cleaning up temporary files....
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1065 (syslogd)
.
Starting NFS common utilities: statd idmapd.
Starting system message bus: dbus.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Not starting NFS kernel daemon: no exports. ... (warning).
Starting NTP server: ntpd.
Starting OpenBSD Secure Shell server: sshd.
Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1105 (klogd)
.
Running local boot scripts (/etc/rc.local)
.

Debian GNU/Linux 11 m300-sid ttyS0

m300-sid login: root
Password: 
Linux m300-sid 6.3.8-kirkwood-tld-1 #1 PREEMPT Wed Jun 21 02:30:10 PDT 2023 armv5tel

Last login: Wed Jul 26 16:01:19 CDT 2023 on ttyS0
m300-sid
192.168.1.229
Dell KACE M300
Linux version 6.3.8-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Wed Jun 21 02:30:10 PDT 2023
Debian 11.7
Wed Jul 26 16:29:19 CDT 2023 up 0 minutes
root@m300-sid:~# flash_unlock /dev/mtd0
flash_unlock: error!: could not unlock device: /dev/mtd0

              error 95 (Operation not supported)
root@m300-sid:~# flash_unlock -V
flash_unlock (mtd-utils) 2.1.2
root@m300-sid:~#

Thoughts?



Edited 1 time(s). Last edit at 07/26/2023 09:28PM by dhargens.

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 unprotect the SPI flash.

protect off all

Expected output

Un-Protect Flash Bank # 1 
................................................................................................................................ 
done

And then go ahead boot into 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 unprotect the SPI flash.

> protect off all

> Expected output

> Un-Protect Flash Bank # 1 
> ................................................................................................................................
> done

> And then go ahead boot into Debian

No, actually, I did follow the directions. I've highlighted the original post with those commands in red to make it easier to see.

dhargens,

> root@m300-sid:~# flash_unlock
> /dev/mtd0
> flash_unlock: error!: could not unlock device:
> /dev/mtd0
>
> error 95 (Operation not supported)

Ignore this error message. Go ahead and continue the installation

Quote

2. Flash new u-boot

Log into Debian, download the attached u-boot image tarball. Extract the files. And flash both images.

flash_unlock /dev/mtd0 # ignore error message

flashcp -v uboot.2022.04-tld-1.m300.mtd0.kwb /dev/mtd0

....

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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-sid:~# flashcp -v Kirkwood_files/uboot.2022.04-tld-1.m300.mtd0.kwb   /dev/mtd0
Erasing blocks: 96/96 (100%)
Writing data: 384k/384k (100%)
Verifying data: 384k/384k (100%)
root@m300-sid:~# flash_unlock /dev/mtd1
flash_unlock: error!: could not unlock device: /dev/mtd1

              error 95 (Operation not supported)
root@m300-sid:~# flashcp -v Kirkwood_files/uboot.2022.04-tld-1.m300.environment.4K.img  /dev/mtd1
Erasing blocks: 1/1 (100%)
Writing data: 4k/4k (100%)
Verifying data: 4k/4k (100%)
root@m300-sid:~# cd /boot
root@m300-sid:/boot# cp -a uImage uImage.m300.dtb
root@m300-sid:/boot# cp -a uImage.orig uImage
root@m300-sid:/boot# fw_printenv
Cannot read environment, using default
Cannot read default environment from file
root@m300-sid:/boot# fw_setenv ethaddr 18:03:73:41:da:d6
Cannot read environment, using default
Cannot read default environment from file
root@m300-sid:/boot# fw_setenv ipaddr 192.168.1.229
Cannot read environment, using default
Cannot read default environment from file
root@m300-sid:/boot# cat /boot/uEnv.txt
cat: /boot/uEnv.txt: No such file or directory
root@m300-sid:/boot# 

[I edited /boot/uEnv.txt file here]

root@m300-sid:/boot# cat /boot/uEnv.txt
custom_params=raid=noautodetect
bootdev=sata
devices=sata usb
ethaddr=18:03:73:41:da:d6
ipaddr=192.168.1.229
root@m300-sid:/boot#

I don't know what the 'serverip' value should be (unless it's the gateway?), and I didn't want to test it by rebooting because of the errors on the envs.

Don't reboot yet.

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

====

ipaddress and serverip are not important at this time. These IP addresses will be used when you want to boot with tftp, or to activate netconsole (netconsole does not work yet in this M300 u-boot version).

====

And do you have serial console? it will be helptful to troubleshoot using serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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: 00001000 00001000 "u-boot-env"
root@m300-sid:/boot# cat /etc/fw_env.config
# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
root@m300-sid:/boot#

> And do you have serial console? it will be
> helptful to troubleshoot using serial console.

Of course! The first thing I do is hook up the serial on these devices, and it's how I was able to post the earlier spew from booting.

fw_env.config is wrong...

Here is mine

root@m300:~# cat /etc/fw_env.config
# Dell KACE M300
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd1 0x0 00001000 0x00001000