Debian on Dell Kace M300
Posted by JDS420
|
Re: Debian on Dell Kace M300 October 11, 2019 05:11PM |
Admin Registered: 13 years ago Posts: 18,549 |
Neal,
When you list the GPIO in Linux, they are exactly what the DTS defines.
No, I did not find Poweroff. However, shutdown is working fine in Debian, so looks like there is no GPIO for Poweroff.
There are other GPIOs that this u-boot defines, but they don't seem to have any effect when I poke them.
Without GPL source code, it will take too much time to complete a new u-boot for this box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
When you list the GPIO in Linux, they are exactly what the DTS defines.
No, I did not find Poweroff. However, shutdown is working fine in Debian, so looks like there is no GPIO for Poweroff.
There are other GPIOs that this u-boot defines, but they don't seem to have any effect when I poke them.
Without GPL source code, it will take too much time to complete a new u-boot for this box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 October 11, 2019 09:05PM |
Registered: 9 years ago Posts: 39 |
bodhi Wrote:
-------------------------------------------------------
> Without GPL source code, it will take too much
> time to complete a new u-boot for this box.
That's a shame, but you've done quite a lot! Thanks for all the work you've put into making this into a quite capable little server!
Neal
-------------------------------------------------------
> Without GPL source code, it will take too much
> time to complete a new u-boot for this box.
That's a shame, but you've done quite a lot! Thanks for all the work you've put into making this into a quite capable little server!
Neal
|
Re: Debian on Dell Kace M300 October 12, 2019 04:28PM |
Registered: 10 years ago Posts: 155 |
The M300 went into production today with the 120GB SSD and the cover installed. It's had a week or two of burn-in and several successful boots. No haveged, I just wait. The SSD is secured with zip ties through a couple of fittings installed in the tapped holes in the enclosure on each side of the SSD. Working great. Thanks Bodhi!
|
Re: Debian on Dell Kace M300 October 12, 2019 05:56PM |
Admin Registered: 13 years ago Posts: 18,549 |
mikeh49,
> The M300 went into production today with the 120GB
> SSD and the cover installed. It's had a week or
> two of burn-in and several successful boots. No
> haveged, I just wait.
FYI, there are mainline works going on for kernel 5.4.x which will solve the entropy delay issue.
> The SSD is secured with zip
> ties through a couple of fittings installed in the
> tapped holes in the enclosure on each side of the
> SSD.
Nice!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> The M300 went into production today with the 120GB
> SSD and the cover installed. It's had a week or
> two of burn-in and several successful boots. No
> haveged, I just wait.
FYI, there are mainline works going on for kernel 5.4.x which will solve the entropy delay issue.
> The SSD is secured with zip
> ties through a couple of fittings installed in the
> tapped holes in the enclosure on each side of the
> SSD.
Nice!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 October 17, 2019 03:04AM |
Admin Registered: 13 years ago Posts: 18,549 |
Thanks everybody :) you guys were doing a lot of works and made this project successful too! I've really enjoyed the collaboration.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 January 06, 2020 07:28PM |
Registered: 9 years ago Posts: 429 |
Just wanted to let those interested know that the M300 does indeed support port multiplication as I had earlier hoped. I bought a 22 pin male to male adapter and a SATA to ESATA cable and hooked these up (via ESATA cable) to a Sans Digital 4 bay ESATA external disk enclosure.
The 22 pin male to male adapter is here: https://www.amazon.com/gp/product/B00S6HTVGI/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
The SATA to external ESATA port cable is here: https://www.amazon.com/gp/product/B000GX4C7I/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
I have attached pics of the setup linked below.
dmesg shows the following
One of the external bay disk mounted to media shows a speed test as follows:
Hdparm test for both drives:
Have to admit not the performance I was hoping for therefor I am debating whether it's worth it to go through the hassle of putting a hole in the beautiful enclosure for the ESATA port.
Your thoughts / impressions bodhi?
Edited 4 time(s). Last edit at 01/06/2020 09:47PM by LeggoMyEggo.
The 22 pin male to male adapter is here: https://www.amazon.com/gp/product/B00S6HTVGI/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
The SATA to external ESATA port cable is here: https://www.amazon.com/gp/product/B000GX4C7I/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
I have attached pics of the setup linked below.
dmesg shows the following
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.3.2-kirkwood-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6)) #1.0 PREEMPT Wed Oct 2 00:06:56 PDT 2019 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt: Machine model: Dell KACE M300 [ 0.000000] printk: bootconsole [earlycon0] enabled [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Ignoring RAM at 0x70000000-0x80000000 [ 0.000000] Consider using a HIGHMEM enabled kernel. [ 0.000000] On node 0 totalpages: 458752 [ 0.000000] Normal zone: 3584 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 458752 pages, LIFO batch:63 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 455168 [ 0.000000] 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] Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 1795396K/1835008K available (10240K kernel code, 892K rwdata, 3468K rodata, 1024K init, 294K bss, 39612K reserved, 0K cma-reserved) [ 0.000000] random: get_random_u32 called from cache_alloc_refill+0x500/0x8fc with crng_init=0 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns [ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.008511] Switching to timer-based delay loop, resolution 5ns [ 0.015591] Console: colour dummy device 80x30 [ 0.020766] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000) [ 0.031970] pid_max: default: 32768 minimum: 301 [ 0.037505] LSM: Security Framework initializing [ 0.042957] Mount-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 0.051061] Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 0.060261] *** VALIDATE proc *** [ 0.064438] *** VALIDATE cgroup1 *** [ 0.068735] *** VALIDATE cgroup2 *** [ 0.073062] CPU: Testing write buffer coherency: ok [ 0.080020] Setting up static identity map for 0x100000 - 0x100058 [ 0.087041] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1 [ 0.093111] rcu: Hierarchical SRCU implementation. [ 0.100482] devtmpfs: initialized [ 0.108249] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.118794] futex hash table entries: 256 (order: -1, 3072 bytes, linear) [ 0.126469] xor: measuring software checksum speed [ 0.228530] arm4regs : 1816.800 MB/sec [ 0.328531] 8regs : 1090.400 MB/sec [ 0.428531] 32regs : 1583.600 MB/sec [ 0.433390] xor: using function: arm4regs (1816.800 MB/sec) [ 0.439659] prandom: seed boundary self test passed [ 0.447707] prandom: 100 self tests passed [ 0.452504] pinctrl core: initialized pinctrl subsystem [ 0.459547] NET: Registered protocol family 16 [ 0.465186] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.473402] audit: initializing netlink subsys (disabled) [ 0.480542] audit: type=2000 audit(0.460:1): state=initialized audit_enabled=0 res=1 [ 0.489053] cpuidle: using governor ladder [ 0.493881] cpuidle: using governor menu [ 0.498872] Feroceon L2: Enabling L2 [ 0.503151] Feroceon L2: Cache support initialised. [ 0.512457] No ATAGs? [ 2.578514] random: fast init done [ 3.426029] alg: No test for lzo-rle (lzo-rle-generic) [ 3.432198] alg: No test for lzo-rle (lzo-rle-scomp) [ 3.618935] raid6: int32x8 gen() 208 MB/s [ 3.788738] raid6: int32x8 xor() 142 MB/s [ 3.958781] raid6: int32x4 gen() 215 MB/s [ 4.128612] raid6: int32x4 xor() 138 MB/s [ 4.298521] raid6: int32x2 gen() 208 MB/s [ 4.468522] raid6: int32x2 xor() 151 MB/s [ 4.638698] raid6: int32x1 gen() 157 MB/s [ 4.808522] raid6: int32x1 xor() 109 MB/s [ 4.813461] raid6: using algorithm int32x4 gen() 215 MB/s [ 4.819527] raid6: .... xor() 138 MB/s, rmw enabled [ 4.825064] raid6: using intx1 recovery algorithm [ 4.830634] vgaarb: loaded [ 4.834409] SCSI subsystem initialized [ 4.839028] libata version 3.00 loaded. [ 4.839214] usbcore: registered new interface driver usbfs [ 4.845395] usbcore: registered new interface driver hub [ 4.851449] usbcore: registered new device driver usb [ 4.857291] pps_core: LinuxPPS API ver. 1 registered [ 4.862933] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 4.872730] PTP clock support registered [ 4.878292] clocksource: Switched to clocksource orion_clocksource [ 5.570931] VFS: Disk quotas dquot_6.6.0 [ 5.575590] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 5.590119] thermal_sys: Registered thermal governor 'step_wise' [ 5.590317] NET: Registered protocol family 2 [ 5.602654] tcp_listen_portaddr_hash hash table entries: 1024 (order: 1, 8192 bytes, linear) [ 5.611859] TCP established hash table entries: 16384 (order: 4, 65536 bytes, linear) [ 5.620602] TCP bind hash table entries: 16384 (order: 4, 65536 bytes, linear) [ 5.628690] TCP: Hash tables configured (established 16384 bind 16384) [ 5.636019] UDP hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 5.643454] UDP-Lite hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 5.651445] NET: Registered protocol family 1 [ 5.656960] RPC: Registered named UNIX socket transport module. [ 5.663601] RPC: Registered udp transport module. [ 5.668984] RPC: Registered tcp transport module. [ 5.674350] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 5.681461] PCI: CLS 0 bytes, default 32 [ 5.686265] Trying to unpack rootfs image as initramfs... [ 6.122075] Freeing initrd memory: 7076K [ 6.126791] NetWinder Floating Point Emulator V0.97 (double precision) [ 6.134887] Initialise system trusted keyrings [ 6.140073] Key type blacklist registered [ 6.144909] workingset: timestamp_bits=30 max_order=19 bucket_order=0 [ 6.152141] zbud: loaded [ 6.156190] NFS: Registering the id_resolver key type [ 6.161980] Key type id_resolver registered [ 6.166830] Key type id_legacy registered [ 6.171550] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 6.178930] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 6.186272] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. [ 6.194327] fuse: init (API version 7.31) [ 6.199287] orangefs_debugfs_init: called with debug mask: :none: :0: [ 6.206522] orangefs_init: module version upstream loaded [ 6.212603] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled [ 6.247160] async_tx: api initialized (async) [ 6.252262] Key type asymmetric registered [ 6.257024] Asymmetric key parser 'x509' registered [ 6.262654] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 6.271770] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver [ 6.281128] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00 [ 6.289419] pci_bus 0000:00: root bus resource [bus 00-ff] [ 6.295571] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff] [ 6.303123] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff] [ 6.310064] pci_bus 0000:00: scanning bus [ 6.310127] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400 [ 6.316815] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref] [ 6.324875] pci_bus 0000:00: fixups for bus [ 6.324884] PCI: bus0: Fast back to back transfers disabled [ 6.331148] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0 [ 6.331155] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 6.339825] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1 [ 6.339915] pci_bus 0000:01: scanning bus [ 6.340437] pci_bus 0000:01: fixups for bus [ 6.340441] PCI: bus1: Fast back to back transfers enabled [ 6.346588] pci_bus 0000:01: bus scan returning with max=01 [ 6.346597] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 6.353895] pci_bus 0000:00: bus scan returning with max=01 [ 6.354012] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref] [ 6.361911] pci 0000:00:01.0: PCI bridge to [bus 01] [ 6.367599] pcieport 0000:00:01.0: assign IRQ: got 0 [ 6.367617] pcieport 0000:00:01.0: enabling bus mastering [ 6.367932] mv_xor f1060800.xor: Marvell shared XOR driver [ 6.428874] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 6.438185] mv_xor f1060900.xor: Marvell shared XOR driver [ 6.498845] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 6.508399] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 6.516306] printk: console [ttyS0] disabled [ 6.521352] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A [ 6.531026] printk: console [ttyS0] enabled [ 6.540853] printk: bootconsole [earlycon0] disabled [ 6.557733] loop: module loaded [ 6.561859] sata_mv f1080000.sata: version 1.28 [ 6.562080] sata_mv f1080000.sata: slots 32 ports 2 [ 6.570384] scsi host0: sata_mv [ 6.574635] scsi host1: sata_mv [ 6.578702] ata1: SATA max UDMA/133 irq 33 [ 6.583512] ata2: SATA max UDMA/133 irq 33 [ 6.589612] m25p80 spi0.0: mx25l4005a (512 Kbytes) [ 6.595129] 2 cmdlinepart partitions found on MTD device spi0.0 [ 6.601814] Creating 2 MTD partitions on "spi0.0": [ 6.607329] 0x000000000000-0x00000007f000 : "uboot" [ 6.613897] 0x00000007f000-0x000000080000 : "u-boot-env" [ 6.621633] libphy: Fixed MDIO Bus: probed [ 6.626989] libphy: orion_mdio_bus: probed [ 6.635372] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 6.643285] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set [ 6.651232] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 18:03:73:41:db:ba [ 6.660849] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 6.668122] ehci-pci: EHCI PCI platform driver [ 6.673367] ehci-orion: EHCI orion driver [ 6.678219] orion-ehci f1050000.ehci: EHCI Host Controller [ 6.684495] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 6.693067] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000 [ 6.728314] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00 [ 6.735222] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 [ 6.744246] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.752206] usb usb1: Product: EHCI Host Controller [ 6.757799] usb usb1: Manufacturer: Linux 5.3.2-kirkwood-tld-1 ehci_hcd [ 6.765155] usb usb1: SerialNumber: f1050000.ehci [ 6.771026] hub 1-0:1.0: USB hub found [ 6.775528] hub 1-0:1.0: 1 port detected [ 6.780682] usbcore: registered new interface driver usb-storage [ 6.787678] mousedev: PS/2 mouse device common for all mice [ 6.794416] rtc-mv f1010300.rtc: registered as rtc0 [ 6.800150] i2c /dev entries driver [ 6.804793] device-mapper: uevent: version 1.0.3 [ 6.810391] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com [ 6.819900] device-mapper: multipath round-robin: version 1.2.0 loaded [ 6.827188] device-mapper: multipath queue-length: version 0.2.0 loaded [ 6.834569] device-mapper: multipath service-time: version 0.3.0 loaded [ 6.842001] device-mapper: dm-log-userspace: version 1.3.0 loaded [ 6.848876] device-mapper: raid: Loading target version 1.14.0 [ 6.856377] hidraw: raw HID events driver (C) Jiri Kosina [ 6.862815] drop_monitor: Initializing network drop monitor service [ 6.870034] NET: Registered protocol family 17 [ 6.875396] Key type dns_resolver registered [ 6.881023] registered taskstats version 1 [ 6.885859] Loading compiled-in X.509 certificates [ 6.891564] zswap: loaded using pool lzo/zbud [ 6.923756] Key type big_key registered [ 6.938486] Key type encrypted registered [ 6.944697] rtc-mv f1010300.rtc: setting system clock to 2020-01-07T01:05:13 UTC (1578359113) [ 7.148386] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 7.158343] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 7.166194] ata1.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 [ 7.177801] ata1.00: hard resetting link [ 7.348832] usb 1-1: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00 [ 7.357760] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 7.366182] hub 1-1:1.0: USB hub found [ 7.370823] hub 1-1:1.0: 4 ports detected [ 7.618402] ata1.00: link resume succeeded after 1 retries [ 7.688312] usb 1-1.3: new high-speed USB device number 3 using orion-ehci [ 7.732692] ata1.01: hard resetting link [ 7.839572] usb 1-1.3: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00 [ 7.848675] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.856727] usb 1-1.3: Product: Ultra Fit [ 7.861460] usb 1-1.3: Manufacturer: SanDisk [ 7.866442] usb 1-1.3: SerialNumber: XXXXXXXXXXXXXXXXXXX [ 7.873201] usb-storage 1-1.3:1.0: USB Mass Storage device detected [ 7.880558] scsi host2: usb-storage 1-1.3:1.0 [ 8.072558] ata1.02: hard resetting link [ 8.412142] ata1.03: hard resetting link [ 8.752137] ata1.04: hard resetting link [ 8.909524] scsi 2:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6 [ 8.919854] sd 2:0:0:0: [sda] 30031250 512-byte logical blocks: (15.4 GB/14.3 GiB) [ 8.929720] sd 2:0:0:0: [sda] Write Protect is off [ 8.935239] sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 8.935843] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 8.952927] sda: sda1 [ 8.958722] sd 2:0:0:0: [sda] Attached SCSI removable disk [ 9.092389] ata1.05: hard resetting link [ 12.488357] ata1.02: ATA-7: ST380815AS, 3.ADA, max UDMA/133 [ 12.494654] ata1.02: 156250000 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 12.588351] ata1.02: configured for UDMA/133 [ 12.618381] ata1.03: ATA-7: ST3808110AS, 3.AHL, max UDMA/100 [ 12.624763] ata1.03: 156301488 sectors, multi 0: LBA48 [ 12.635184] ata1.03: configured for UDMA/100 [ 12.640364] ata1: EH complete [ 12.654391] scsi 0:2:0:0: Direct-Access ATA ST380815AS A PQ: 0 ANSI: 5 [ 12.663951] sd 0:2:0:0: [sdb] 156250000 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 12.672799] scsi 0:3:0:0: Direct-Access ATA ST3808110AS L PQ: 0 ANSI: 5 [ 12.681711] sd 0:2:0:0: [sdb] Write Protect is off [ 12.687227] sd 0:2:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 12.687950] sd 0:3:0:0: [sdc] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 12.696706] sd 0:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 12.706578] sd 0:3:0:0: [sdc] Write Protect is off [ 12.712106] sd 0:3:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 12.712194] sd 0:3:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 13.029666] ata2: SATA link down (SStatus 0 SControl F300) [ 16.009982] sdc: sdc1 [ 16.014729] sd 0:3:0:0: [sdc] Attached SCSI disk [ 16.041370] sdb: sdb1 [ 16.045537] sd 0:2:0:0: [sdb] Attached SCSI disk [ 16.054051] Freeing unused kernel memory: 1024K [ 16.068826] Checked W+X mappings: passed, no W+X pages found [ 16.075214] Run /init as init process [ 16.151424] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 16.166730] random: udevadm: uninitialized urandom read (16 bytes read) [ 16.174777] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 28.230367] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 28.293956] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 28.912593] random: crng init done [ 28.916714] random: 7 urandom warning(s) missed due to ratelimiting [ 30.562066] watchdog: f1020300.watchdog-timer: driver supplied timeout (4294967295) out of range [ 30.658926] watchdog: f1020300.watchdog-timer: falling back to default timeout (21) [ 30.718778] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 30.770888] orion_wdt: Initial timeout 21 sec [ 30.787407] sd 0:2:0:0: Attached scsi generic sg1 type 0 [ 30.810574] marvell-cesa f1030000.crypto: CESA device successfully registered [ 30.832922] usbcore: registered new interface driver uas [ 30.847530] sd 0:3:0:0: Attached scsi generic sg2 type 0 [ 33.261928] EXT4-fs (sda1): re-mounted. Opts: (null) [ 33.466620] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 34.268325] Adding 262140k swap on /swapfile. Priority:-2 extents:10 across:5786024k FS [ 38.458936] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled [ 48.673772] NET: Registered protocol family 10 [ 48.680264] Segment Routing with IPv6
One of the external bay disk mounted to media shows a speed test as follows:
root@debian:~# dd if=/dev/zero of=/media/output bs=8k count=100k; rm -f /media/output 102400+0 records in 102400+0 records out 838860800 bytes (839 MB, 800 MiB) copied, 16.4479 s, 51.0 MB/s
Hdparm test for both drives:
root@debian:~# hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 818 MB in 2.00 seconds = 408.26 MB/sec Timing buffered disk reads: 218 MB in 3.02 seconds = 72.24 MB/sec root@debian:~# hdparm -Tt /dev/sdc /dev/sdc: Timing cached reads: 816 MB in 2.00 seconds = 407.27 MB/sec Timing buffered disk reads: 194 MB in 3.01 seconds = 64.38 MB/sec
Have to admit not the performance I was hoping for therefor I am debating whether it's worth it to go through the hassle of putting a hole in the beautiful enclosure for the ESATA port.
Your thoughts / impressions bodhi?
Edited 4 time(s). Last edit at 01/06/2020 09:47PM by LeggoMyEggo.
|
Re: Debian on Dell Kace M300 January 06, 2020 11:35PM |
Admin Registered: 13 years ago Posts: 18,549 |
LeggoMyEggo,
Cool! Port multiplier works so that would make this box substantially more powerful than the NSA325 :)
This might need adjustment
I hope it was the case that you've overlooked this: If your rootfs is USB then /media/output is on /dev/sda1. So the dd test should be tried on sdb1 or sdc1, after you've mounted them.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Cool! Port multiplier works so that would make this box substantially more powerful than the NSA325 :)
This might need adjustment
root@debian:~# dd if=/dev/zero of=/media/output bs=8k count=100k; rm -f /media/output
I hope it was the case that you've overlooked this: If your rootfs is USB then /media/output is on /dev/sda1. So the dd test should be tried on sdb1 or sdc1, after you've mounted them.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 January 07, 2020 11:12PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> LeggoMyEggo,
> I hope it was the case that you've overlooked
> this: If your rootfs is USB then /media/output is
> on /dev/sda1. So the dd test should be tried on
> sdb1 or sdc1, after you've mounted them.
I had mounted /dev/sdb1 to /media before performing the test.
-------------------------------------------------------
> LeggoMyEggo,
> I hope it was the case that you've overlooked
> this: If your rootfs is USB then /media/output is
> on /dev/sda1. So the dd test should be tried on
> sdb1 or sdc1, after you've mounted them.
I had mounted /dev/sdb1 to /media before performing the test.
|
Re: Debian on Dell Kace M300 January 07, 2020 11:55PM |
Admin Registered: 13 years ago Posts: 18,549 |
LeggoMyEggo Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > LeggoMyEggo,
> > I hope it was the case that you've overlooked
> > this: If your rootfs is USB then /media/output
> is
> > on /dev/sda1. So the dd test should be tried on
> > sdb1 or sdc1, after you've mounted them.
>
> I had mounted /dev/sdb1 to /media before
> performing the test.
Then I would suggest plugging in a SATA cable directly for the single HHD test (to remove the possible slow down impact by external HDD enclosure controller).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/08/2020 01:44AM by bodhi.
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > LeggoMyEggo,
> > I hope it was the case that you've overlooked
> > this: If your rootfs is USB then /media/output
> is
> > on /dev/sda1. So the dd test should be tried on
> > sdb1 or sdc1, after you've mounted them.
>
> I had mounted /dev/sdb1 to /media before
> performing the test.
Then I would suggest plugging in a SATA cable directly for the single HHD test (to remove the possible slow down impact by external HDD enclosure controller).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/08/2020 01:44AM by bodhi.
|
Re: Debian on Dell Kace M300 January 08, 2020 04:33PM |
Registered: 9 years ago Posts: 429 |
For comparisons sake, I mounted the stock SSD module to media and tested.
Have to dig out a single external ESATA enclosure I have somewhere to test your hypothesis about the controller of the Sans Digital ESATA unit. It is an older model I picked up used and it is SATA II but that should not mean much as the controller in the M300 is SATA 2 as well.
root@debian:~# mount /dev/sda2 /media root@debian:~# cd /media root@debian:/media# dd if=/dev/zero of=/media/output bs=8k count=100k; rm -f /media/output 102400+0 records in 102400+0 records out 838860800 bytes (839 MB, 800 MiB) copied, 31.1632 s, 26.9 MB/s root@debian:/media# hdparm -Tt /dev/sda /dev/sda: Timing cached reads: 766 MB in 2.00 seconds = 383.06 MB/sec Timing buffered disk reads: 210 MB in 3.00 seconds = 69.99 MB/sec
Have to dig out a single external ESATA enclosure I have somewhere to test your hypothesis about the controller of the Sans Digital ESATA unit. It is an older model I picked up used and it is SATA II but that should not mean much as the controller in the M300 is SATA 2 as well.
|
Re: Debian on Dell Kace M300 January 08, 2020 11:33PM |
Admin Registered: 13 years ago Posts: 18,549 |
Leggo,
> Have to dig out a single external ESATA enclosure
I think the enclosure of any type would effect the speed. I don't recall right now if this M300 SATA is a 22 pin connector type, I'm thinking about a direct cable connection.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Have to dig out a single external ESATA enclosure
I think the enclosure of any type would effect the speed. I don't recall right now if this M300 SATA is a 22 pin connector type, I'm thinking about a direct cable connection.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 January 09, 2020 12:17AM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> Leggo,
I don't recall right now if this M300 SATA
> is a 22 pin connector type,
It is. See first picture in my upper post for the way I adapted 22 pin to 7 pin SATA.
Just curious, what performance read / write would you have expected given the M300's specs?
Edited 1 time(s). Last edit at 01/09/2020 12:18AM by LeggoMyEggo.
-------------------------------------------------------
> Leggo,
I don't recall right now if this M300 SATA
> is a 22 pin connector type,
It is. See first picture in my upper post for the way I adapted 22 pin to 7 pin SATA.
Just curious, what performance read / write would you have expected given the M300's specs?
Edited 1 time(s). Last edit at 01/09/2020 12:18AM by LeggoMyEggo.
|
Re: Debian on Dell Kace M300 January 09, 2020 03:34AM |
Admin Registered: 13 years ago Posts: 18,549 |
The NSA325 (1.6 GHz CPU) benchmarks tested with older kernel.
dmesg
root@tldDebian:/localdisk# hdparm -tT /dev/sda
I did not save dd test. But usually it is about 70MB/s write speed cp a large file (> 1GB) on NSA325.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/09/2020 03:40AM by bodhi.
dmesg
[Thu Dec 3 22:50:50 2015] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [Thu Dec 3 22:50:51 2015] ata1.00: ATA-8: ST9750420AS, 0002DEM1, max UDMA/133 [Thu Dec 3 22:50:51 2015] ata1.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 31/32) [Thu Dec 3 22:50:51 2015] ata1.00: configured for UDMA/133 [Thu Dec 3 22:50:51 2015] scsi 0:0:0:0: Direct-Access ATA ST9750420AS DEM1 PQ: 0 ANSI: 5
root@tldDebian:/localdisk# hdparm -tT /dev/sda
/dev/sda: Timing cached reads: 626 MB in 2.00 seconds = 312.28 MB/sec Timing buffered disk reads: 316 MB in 3.00 seconds = 105.32 MB/sec
I did not save dd test. But usually it is about 70MB/s write speed cp a large file (> 1GB) on NSA325.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/09/2020 03:40AM by bodhi.
|
Re: Debian on Dell Kace M300 January 28, 2020 04:04PM |
Registered: 10 years ago Posts: 155 |
I'm trying to get my second M300 going. I have installed the Debian filesystem (5.9.2 with M300 DTB) on a 4GB partition of the 16GB SSD card that comes in the M300. The remaining space on the card is formatted EXT 3 to be used for data. I had this card running on my frist M300 back in September with no significant problems that I can recall. After installing it in the new M300, making the environment settings, testing with a USB drive (OK) and then booting from the SSD card, I've run into several boot failures with kernel panic. The environments are set to boot USB first, if that is not found, then to boot SATA. Here is the serial log of the latest:
Any help would be appreciated. Is this hardware or software? I've also had one "segmentation fault" while working on SSH. Is that hardware or software?
Thanks.
▒
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ 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: 0
Booting USB...
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number
Booting SATA...
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: TS16GSSD25H-M Firm: 20100712 Ser#: 20110423421602036222
Type: Hard Disk
Supports 48-bit addressing
Capacity: 15272.0 MB = 14.9 GB (31277056 x 512)
4981772 bytes read
9784769 bytes read
## Booting image at 00800000 ...
Image Name: Linux-5.2.9-kirkwood-tld-2
Created: 2019-09-12 16:29:16 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4981708 Bytes = 4.8 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
Image Name: initramfs-5.2.9-kirkwood-tld-2
Created: 2019-09-07 16:57:30 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9784705 Bytes = 9.3 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.2.9-kirkwood-tld-2 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Wed Aug 28 03:55:21 PDT 2019
[ 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] Built 1 zonelists, mobility grouping on. Total pages: 455168
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=sata_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)
[ 0.000000][ T0] Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000][ T0] Memory: 1793952K/1835008K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 300K bss, 41056K reserved, 0K cma-reserved)
[ 0.000000][ T0] random: get_random_u32 called from cache_alloc_refill+0x52c/0x924 with crng_init=0
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] 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] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000006][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.008508][ T0] Switching to timer-based delay loop, resolution 5ns
[ 0.015620][ T0] Console: colour dummy device 80x30
[ 0.020801][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.032005][ T0] pid_max: default: 32768 minimum: 301
[ 0.037567][ T0] LSM: Security Framework initializing
[ 0.043034][ T0] Mount-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.050445][ T0] Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.058890][ T0] *** VALIDATE proc ***
[ 0.063086][ T0] *** VALIDATE cgroup1 ***
[ 0.067343][ T0] *** VALIDATE cgroup2 ***
[ 0.071690][ T0] CPU: Testing write buffer coherency: ok
[ 0.078557][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.085584][ T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[ 0.091639][ T1] rcu: Hierarchical SRCU implementation.
[ 0.099351][ T1] devtmpfs: initialized
[ 0.107046][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.117588][ T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.124598][ T1] xor: measuring software checksum speed
[ 0.228530][ T1] arm4regs : 1816.800 MB/sec
[ 0.328529][ T1] 8regs : 1090.400 MB/sec
[ 0.428530][ T1] 32regs : 1585.600 MB/sec
[ 0.433391][ T1] xor: using function: arm4regs (1816.800 MB/sec)
[ 0.439661][ T1] prandom: seed boundary self test passed
[ 0.447707][ T1] prandom: 100 self tests passed
[ 0.452504][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.459525][ T1] NET: Registered protocol family 16
[ 0.465030][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.473231][ T1] audit: initializing netlink subsys (disabled)
[ 0.480294][ T14] audit: type=2000 audit(0.470:1): state=initialized audit_enabled=0 res=1
[ 0.488803][ T1] cpuidle: using governor ladder
[ 0.493628][ T1] cpuidle: using governor menu
[ 0.498637][ T1] Feroceon L2: Enabling L2
[ 0.502909][ T1] Feroceon L2: Cache support initialised.
[ 0.512288][ T1] No ATAGs?
[ 2.568513][ C0] random: fast init done
[ 3.736906][ T71] alg: No test for lzo-rle (lzo-rle-generic)
[ 3.743057][ T73] alg: No test for lzo-rle (lzo-rle-scomp)
[ 3.918829][ T1] raid6: int32x8 gen() 208 MB/s
[ 4.088873][ T1] raid6: int32x8 xor() 142 MB/s
[ 4.258670][ T1] raid6: int32x4 gen() 208 MB/s
[ 4.428664][ T1] raid6: int32x4 xor() 138 MB/s
[ 4.598723][ T1] raid6: int32x2 gen() 210 MB/s
[ 4.768668][ T1] raid6: int32x2 xor() 152 MB/s
[ 4.938707][ T1] raid6: int32x1 gen() 157 MB/s
[ 5.108551][ T1] raid6: int32x1 xor() 109 MB/s
[ 5.113485][ T1] raid6: using algorithm int32x2 gen() 210 MB/s
[ 5.119552][ T1] raid6: .... xor() 152 MB/s, rmw enabled
[ 5.125088][ T1] raid6: using intx1 recovery algorithm
[ 5.130649][ T1] vgaarb: loaded
[ 5.134376][ T1] SCSI subsystem initialized
[ 5.139176][ T1] usbcore: registered new interface driver usbfs
[ 5.145358][ T1] usbcore: registered new interface driver hub
[ 5.151415][ T1] usbcore: registered new device driver usb
[ 5.157249][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 5.162896][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.172694][ T1] PTP clock support registered
[ 5.178228][ T1] clocksource: Switched to clocksource orion_clocksource
[ 5.790931][ T1] VFS: Disk quotas dquot_6.6.0
[ 5.795591][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 5.809924][ T1] NET: Registered protocol family 2
[ 5.815528][ T1] tcp_listen_portaddr_hash hash table entries: 1024 (order: 1, 8192 bytes)
[ 5.824021][ T1] TCP established hash table entries: 16384 (order: 4, 65536 bytes)
[ 5.832034][ T1] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 5.839436][ T1] TCP: Hash tables configured (established 16384 bind 16384)
[ 5.846709][ T1] UDP hash table entries: 1024 (order: 2, 16384 bytes)
[ 5.853441][ T1] UDP-Lite hash table entries: 1024 (order: 2, 16384 bytes)
[ 5.860753][ T1] NET: Registered protocol family 1
[ 5.866248][ T1] RPC: Registered named UNIX socket transport module.
[ 5.872891][ T1] RPC: Registered udp transport module.
[ 5.878279][ T1] RPC: Registered tcp transport module.
[ 5.883646][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 5.890757][ T1] PCI: CLS 0 bytes, default 32
[ 5.895511][ T1] Trying to unpack rootfs image as initramfs...
[ 6.437827][ T1] Freeing initrd memory: 9556K
[ 6.442617][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 6.450720][ T1] Initialise system trusted keyrings
[ 6.455860][ T1] Key type blacklist registered
[ 6.460756][ T1] workingset: timestamp_bits=30 max_order=19 bucket_order=0
[ 6.467912][ T1] zbud: loaded
[ 6.471954][ T1] NFS: Registering the id_resolver key type
[ 6.477688][ T1] Key type id_resolver registered
[ 6.482596][ T1] Key type id_legacy registered
[ 6.487282][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 6.494664][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 6.501920][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 6.509794][ T1] fuse: init (API version 7.31)
[ 6.514736][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 6.521981][ T1] orangefs_init: module version upstream loaded
[ 6.528043][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[ 6.548210][ T1] async_tx: api initialized (async)
[ 6.553315][ T1] Key type asymmetric registered
[ 6.558077][ T1] Asymmetric key parser 'x509' registered
[ 6.563698][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 6.572797][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 6.582148][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 6.590436][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 6.596588][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 6.604141][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 6.611147][ T1] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[ 6.617832][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 6.625969][ T1] PCI: bus0: Fast back to back transfers disabled
[ 6.632233][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 6.641579][ T1] PCI: bus1: Fast back to back transfers enabled
[ 6.647735][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 6.655140][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[ 6.663040][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 6.669080][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 6.728777][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 6.738020][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 6.798736][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 6.808164][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 6.816089][ T1] printk: console [ttyS0] disabled
[ 6.821122][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 6.830795][ T1] printk: console [ttyS0] enabled
[ 6.830795][ T1] printk: console [ttyS0] enabled
[ 6.840617][ T1] printk: bootconsole [earlycon0] disabled
[ 6.840617][ T1] printk: bootconsole [earlycon0] disabled
[ 6.857258][ T1] loop: module loaded
[ 6.861575][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 6.869107][ T1] scsi host0: sata_mv
[ 6.873385][ T1] scsi host1: sata_mv
[ 6.877433][ T1] ata1: SATA max UDMA/133 irq 33
[ 6.882297][ T1] ata2: SATA max UDMA/133 irq 33
[ 6.888355][ T1] m25p80 spi0.0: mx25l4005a (512 Kbytes)
[ 6.893875][ T1] 2 cmdlinepart partitions found on MTD device spi0.0
[ 6.900552][ T1] Creating 2 MTD partitions on "spi0.0":
[ 6.906067][ T1] 0x000000000000-0x00000007f000 : "uboot"
[ 6.912597][ T1] 0x00000007f000-0x000000080000 : "u-boot-env"
[ 6.920278][ T1] libphy: Fixed MDIO Bus: probed
[ 6.925630][ T1] libphy: orion_mdio_bus: probed
[ 6.940249][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 6.948094][ T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[ 6.956023][ T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 18:03:73:41:dc:68
[ 6.965614][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.972959][ T1] ehci-pci: EHCI PCI platform driver
[ 6.978161][ T1] ehci-orion: EHCI orion driver
[ 6.983056][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 6.989327][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 6.997841][ T1] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 7.028253][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 7.035164][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
[ 7.044182][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.052146][ T1] usb usb1: Product: EHCI Host Controller
[ 7.057739][ T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-2 ehci_hcd
[ 7.065095][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 7.070946][ T1] hub 1-0:1.0: USB hub found
[ 7.075432][ T1] hub 1-0:1.0: 1 port detected
[ 7.080592][ T1] usbcore: registered new interface driver usb-storage
[ 7.087586][ T1] mousedev: PS/2 mouse device common for all mice
[ 7.094325][ T1] rtc-mv f1010300.rtc: registered as rtc0
[ 7.100062][ T1] i2c /dev entries driver
[ 7.104705][ T1] device-mapper: uevent: version 1.0.3
[ 7.110302][ T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
[ 7.119810][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 7.127093][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 7.134474][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 7.141906][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 7.148782][ T1] device-mapper: raid: Loading target version 1.14.0
[ 7.156124][ T1] hidraw: raw HID events driver (C) Jiri Kosina
[ 7.162523][ T1] drop_monitor: Initializing network drop monitor service
[ 7.169755][ T1] NET: Registered protocol family 17
[ 7.175122][ T1] Key type dns_resolver registered
[ 7.180725][ T1] registered taskstats version 1
[ 7.185565][ T1] Loading compiled-in X.509 certificates
[ 7.191254][ T1] zswap: loaded using pool lzo/zbud
[ 7.259391][ T1] Key type big_key registered
[ 7.292500][ T1] Key type encrypted registered
[ 7.298953][ T1] rtc-mv f1010300.rtc: setting system clock to 2020-01-28T21:48:40 UTC (1580248120)
[ 7.388265][ T112] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 7.399752][ T112] ata1.00: ATA-7: TS16GSSD25H-M, 20100712, max UDMA/133
[ 7.406574][ T112] ata1.00: 31277056 sectors, multi 0: LBA48
[ 7.419123][ T112] ata1.00: configured for UDMA/133
[ 7.434494][ T7] scsi 0:0:0:0: Direct-Access ATA TS16GSSD25H-M 0712 PQ: 0 ANSI: 5
[ 7.444117][ T116] sd 0:0:0:0: [sda] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 7.452456][ T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 7.460342][ T116] sd 0:0:0:0: [sda] Write Protect is off
[ 7.466032][ T116] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 7.477294][ T116] sda: sda1 sda2
[ 7.482078][ T116] sd 0:0:0:0: [sda] Attached SCSI disk
[ 7.658724][ T15] usb 1-1: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00
[ 7.667644][ T15] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7.675967][ T15] hub 1-1:1.0: USB hub found
[ 7.680593][ T15] hub 1-1:1.0: 4 ports detected
[ 7.791835][ T114] ata2: SATA link down (SStatus 0 SControl F300)
[ 7.811295][ T1] Freeing unused kernel memory: 1024K
[ 7.816928][ T1] Checked W+X mappings: passed, no W+X pages found
[ 7.823441][ T1] Run /init as init process
Loading, please wait...
Starting version 241
[ 8.366396][ T164] input: gpio_keys as /devices/platform/gpio_keys/input/input0
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.
[ 18.811818][ T184] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 18.820768][ T184] pgd = (ptrval)
[ 18.824182][ T184] [00000000] *pgd=00000000
[ 18.828487][ T184] Internal error: Oops: 80000005 [#1] PREEMPT ARM
[ 18.834777][ T184] Modules linked in: gpio_keys
[ 18.839420][ T184] CPU: 0 PID: 184 Comm: blkid Not tainted 5.2.9-kirkwood-tld-2 #1
[ 18.847107][ T184] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 18.854095][ T184] PC is at 0x0
[ 18.857341][ T184] LR is at lookup_fast+0xd4/0x2c0
[ 18.862237][ T184] pc : [<00000000>] lr : [<80277c8c>] psr: 20000013
[ 18.869221][ T184] sp : 8270fd78 ip : 00000073 fp : 8270fdb8
[ 18.875160][ T184] r10: 825e72b0 r9 : 8270fdb4 r8 : 80f04028
[ 18.881098][ T184] r7 : 8270fdbc r6 : ee581550 r5 : ee581dd0 r4 : 8270fe18
[ 18.888344][ T184] r3 : 00600008 r2 : 00000000 r1 : 00000041 r0 : ee581dd0
[ 18.895592][ T184] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
[ 18.903448][ T184] Control: 0005397f Table: 026d4000 DAC: 00000051
[ 18.909909][ T184] Process blkid (pid: 184, stack limit = 0x(ptrval))
[ 18.916457][ T184] Stack: (0x8270fd78 to 0x82710000)
[ 18.921524][ T184] fd60: 00000081 00600008
[ 18.930430][ T184] fd80: 00000002 5bdf822c 00000000 8270fe18 00000000 80f04028 00000000 00000000
[ 18.939342][ T184] fda0: 00000000 8270ff08 00000000 802780fc 0000000a 821493d0 00000002 5bdf822c
[ 18.948254][ T184] fdc0: 8270fe18 5bdf822c 8270fe18 00000000 80f04028 8270fecc 00000000 7efa1704
[ 18.957166][ T184] fde0: 8270ff08 802792e8 00080040 0000027d ee40651c 00080060 ee803e58 5bdf822c
[ 18.966078][ T184] fe00: 00000001 00000001 80f04028 82707000 8270fecc 8027b568 825e72b0 ee581550
[ 18.974990][ T184] fe20: a7940d14 0000000b 82707023 00000ff0 eec2b730 ee803e58 8214caf0 00000041
[ 18.983902][ T184] fe40: 00000002 0000003e 00000000 00000000 00000000 8270fe58 0005e8fc 80636208
[ 18.992813][ T184] fe60: 82707010 00000ff0 00000ff0 82707000 ffffff9c 80f0460c 80f04028 7efa1704
[ 19.001725][ T184] fe80: 00000000 00000001 82707000 00000000 00000001 00000002 ffffff9c 80f04028
[ 19.010637][ T184] fea0: ffffff9c 5bdf822c 00000001 00000800 76f0a968 80f04028 ffffff9c 80271a78
[ 19.019549][ T184] fec0: 00000000 ee4d9880 e82f7cec 0000000a 82707015 5bdf822c 00000000 80f04028
[ 19.028461][ T184] fee0: 7efa1698 76f0a968 000000c3 80101208 8270e000 00000000 76ed91e0 8027224c
[ 19.037372][ T184] ff00: 000007ff 8270e000 00000000 80f13b38 826fa020 8016fb90 00000000 5bdf822c
[ 19.046284][ T184] ff20: 00000000 80101208 00000000 8270ffb0 ffffe000 80f04028 5ac3c35a 00000000
[ 19.055196][ T184] ff40: 76ed91e0 8010b5f0 8270e000 00000000 76ed91e0 80260ab8 fffffffe ffffff9c
[ 19.064108][ T184] ff60: 80f04028 8026a528 80f08c80 76d8d410 00020000 00050000 00000004 00000100
[ 19.073020][ T184] ff80: 00000001 5bdf822c 023871c0 023871c0 76f0a968 5bdf822c 00000142 7efa1704
[ 19.081932][ T184] ffa0: 76ed8be8 80101000 7efa1704 76ed8be8 7efa1704 7efa1698 7efa1698 00000002
[ 19.090844][ T184] ffc0: 7efa1704 76ed8be8 76f0a968 000000c3 02387198 7efa1708 76ed8be8 76ed91e0
[ 19.099756][ T184] ffe0: 76ed8f80 7efa1688 76e8b3d8 76df47b4 60000010 7efa1704 00000000 00000000
[ 19.108678][ C0] [<80277c8c>] (lookup_fast) from [<802780fc>] (walk_component+0xdc/0x288)
[ 19.117155][ C0] [<802780fc>] (walk_component) from [<802792e8>] (path_lookupat+0x124/0x204)
[ 19.125892][ C0] [<802792e8>] (path_lookupat) from [<8027b568>] (filename_lookup+0x6c/0xd8)
[ 19.134546][ C0] [<8027b568>] (filename_lookup) from [<80271a78>] (vfs_statx+0x6c/0xcc)
[ 19.142853][ C0] [<80271a78>] (vfs_statx) from [<8027224c>] (sys_stat64+0x34/0x6c)
[ 19.150717][ C0] [<8027224c>] (sys_stat64) from [<80101000>] (ret_fast_syscall+0x0/0x50)
[ 19.159100][ C0] Exception stack(0x8270ffa8 to 0x8270fff0)
[ 19.164867][ C0] ffa0: 7efa1704 76ed8be8 7efa1704 7efa1698 7efa1698 00000002
[ 19.173779][ C0] ffc0: 7efa1704 76ed8be8 76f0a968 000000c3 02387198 7efa1708 76ed8be8 76ed91e0
[ 19.182689][ C0] ffe0: 76ed8f80 7efa1688 76e8b3d8 76df47b4
[ 19.188455][ C0] Code: bad PC value
[ 19.192243][ C0] ---[ end trace 9a8f9bd17ead60cc ]---
[ 19.197574][ C0] Kernel panic - not syncing: Fatal exception in interrupt
[ 19.204650][ C0] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
Any help would be appreciated. Is this hardware or software? I've also had one "segmentation fault" while working on SSH. Is that hardware or software?
Thanks.
|
Re: Debian on Dell Kace M300 January 28, 2020 05:42PM |
Admin Registered: 13 years ago Posts: 18,549 |
Mike,
It's software. Try mounting this SD card on another Linux box and running chkdisk. If it does not help, create a new rootfs and boot with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It's software. Try mounting this SD card on another Linux box and running chkdisk. If it does not help, create a new rootfs and boot with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 January 28, 2020 06:20PM |
Registered: 10 years ago Posts: 155 |
|
Re: Debian on Dell Kace M300 February 08, 2020 01:33PM |
Registered: 4 years ago Posts: 22 |
Hi all, I saw mikeh49's post over on the slimdevices forum which had a link back here and just wanted to say thanks for the info and work you've done on the m300. I bought 1 off ebay for $13.95 shipped (new in the box) and once I got it I felt like it was such a good deal I bought 3 more!
I've been spending a lot of time with Alpine Linux and have been working on getting all the components of squeezebox ecosystem working with it (Logitech Media Server, squeezelite, jivelite), mostly on RPi's, but now have a cross-compiled base load of Alpine running on the m300, using the info from this thread and the kernel config and dts file that bodhi made available.
This could change, but right now I've got a StarTech dual m.2 to sata adapter configured as a jbod, 2x 500GB HP m.2 ssd's with 2 md raid partitions being autodetected by the kernel using the 0.90 metadata version. I've got a 100M partition mounted on /boot and then the second partition is the rest of the space ~465GB.
For whatever reason I thought it would be nice to not change the uboot environment variables from the stock, so right now I've got the uImage file of the 5.4.18 kernel with appended .dtb that I changed the dts file bootparams to include root=/dev/md1 and I'm not using an initramfs but created an empty uInitrd file to keep uboot happy.
It's a bit early yet but things seem to be mostly working.
I've been spending a lot of time with Alpine Linux and have been working on getting all the components of squeezebox ecosystem working with it (Logitech Media Server, squeezelite, jivelite), mostly on RPi's, but now have a cross-compiled base load of Alpine running on the m300, using the info from this thread and the kernel config and dts file that bodhi made available.
This could change, but right now I've got a StarTech dual m.2 to sata adapter configured as a jbod, 2x 500GB HP m.2 ssd's with 2 md raid partitions being autodetected by the kernel using the 0.90 metadata version. I've got a 100M partition mounted on /boot and then the second partition is the rest of the space ~465GB.
For whatever reason I thought it would be nice to not change the uboot environment variables from the stock, so right now I've got the uImage file of the 5.4.18 kernel with appended .dtb that I changed the dts file bootparams to include root=/dev/md1 and I'm not using an initramfs but created an empty uInitrd file to keep uboot happy.
It's a bit early yet but things seem to be mostly working.
|
Re: Debian on Dell Kace M300 February 08, 2020 03:31PM |
Admin Registered: 13 years ago Posts: 18,549 |
sodface,
Thanks for the feedback!
> I've been spending a lot of time with Alpine Linux
> and have been working on getting all the
> components of squeezebox ecosystem working with it
> (Logitech Media Server, squeezelite, jivelite),
> mostly on RPi's, but now have a cross-compiled
> base load of Alpine running on the m300, using the
> info from this thread and the kernel config and
> dts file that bodhi made available.
>
> This could change, but right now I've got a
> StarTech dual m.2 to sata adapter configured as a
> jbod, 2x 500GB HP m.2 ssd's with 2 md raid
> partitions being autodetected by the kernel using
> the 0.90 metadata version. I've got a 100M
> partition mounted on /boot and then the second
> partition is the rest of the space ~465GB.
Nice use of the internal SATA port!
> For whatever reason I thought it would be nice to
> not change the uboot environment variables from
> the stock, so right now I've got the uImage file
> of the 5.4.18 kernel with appended .dtb that I
> changed the dts file bootparams to include
> root=/dev/md1 and I'm not using an initramfs but
> created an empty uInitrd file to keep uboot
> happy.
That's a good alternative if you stay with this system configuration and not booting other. You can also make another DTS to boot USB rootfs (root=/dev/sdxx) to be a rescue system. It is not flexible as using root device label in u-boot env, but since you already know how the DTS should be coded, so not bad at all!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks for the feedback!
> I've been spending a lot of time with Alpine Linux
> and have been working on getting all the
> components of squeezebox ecosystem working with it
> (Logitech Media Server, squeezelite, jivelite),
> mostly on RPi's, but now have a cross-compiled
> base load of Alpine running on the m300, using the
> info from this thread and the kernel config and
> dts file that bodhi made available.
>
> This could change, but right now I've got a
> StarTech dual m.2 to sata adapter configured as a
> jbod, 2x 500GB HP m.2 ssd's with 2 md raid
> partitions being autodetected by the kernel using
> the 0.90 metadata version. I've got a 100M
> partition mounted on /boot and then the second
> partition is the rest of the space ~465GB.
Nice use of the internal SATA port!
> For whatever reason I thought it would be nice to
> not change the uboot environment variables from
> the stock, so right now I've got the uImage file
> of the 5.4.18 kernel with appended .dtb that I
> changed the dts file bootparams to include
> root=/dev/md1 and I'm not using an initramfs but
> created an empty uInitrd file to keep uboot
> happy.
That's a good alternative if you stay with this system configuration and not booting other. You can also make another DTS to boot USB rootfs (root=/dev/sdxx) to be a rescue system. It is not flexible as using root device label in u-boot env, but since you already know how the DTS should be coded, so not bad at all!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 February 08, 2020 08:25PM |
Registered: 9 years ago Posts: 429 |
sodface Wrote:
-------------------------------------------------------
> I've been spending a lot of time with Alpine Linux
> and have been working on getting all the
> components of squeezebox ecosystem working with it
> (Logitech Media Server, squeezelite, jivelite),
> mostly on RPi's, but now have a cross-compiled
> base load of Alpine running on the m300, using the
> info from this thread and the kernel config and
> dts file that bodhi made available.
Funny you mention it, I've spent a number of hours (and spent some brain cells) trying to get bluetooth audio working with squeezelite and pulseaudio on the M300. Have the logitechmediaserver working as well after recompiling CPAN for Debian 10. It works for the most part but I am having issues getting things to auto load after boot.
The problem for us not using RasPi's is that everything is written for Raspi! I have Raspi 3 and 4 but from a hacking point of view they are not as much a challenge. Throw in it being headless without display and it increases the challenge. Quite the bargain this M300 is, if only it had USB3.0 or mPCIe but you won't find another Kirkwood device running at 2GHZ and with 2 Gigs of Ram. They are so cheap, I have three of them. Plus you get network cables and if the unit shits the bed, you can recycle the SATA drive for other projects. This is now my favorite 'play plug' with the Cisco ON100 (Onplus) a close second.
Edited 1 time(s). Last edit at 02/08/2020 08:40PM by LeggoMyEggo.
-------------------------------------------------------
> I've been spending a lot of time with Alpine Linux
> and have been working on getting all the
> components of squeezebox ecosystem working with it
> (Logitech Media Server, squeezelite, jivelite),
> mostly on RPi's, but now have a cross-compiled
> base load of Alpine running on the m300, using the
> info from this thread and the kernel config and
> dts file that bodhi made available.
Funny you mention it, I've spent a number of hours (and spent some brain cells) trying to get bluetooth audio working with squeezelite and pulseaudio on the M300. Have the logitechmediaserver working as well after recompiling CPAN for Debian 10. It works for the most part but I am having issues getting things to auto load after boot.
The problem for us not using RasPi's is that everything is written for Raspi! I have Raspi 3 and 4 but from a hacking point of view they are not as much a challenge. Throw in it being headless without display and it increases the challenge. Quite the bargain this M300 is, if only it had USB3.0 or mPCIe but you won't find another Kirkwood device running at 2GHZ and with 2 Gigs of Ram. They are so cheap, I have three of them. Plus you get network cables and if the unit shits the bed, you can recycle the SATA drive for other projects. This is now my favorite 'play plug' with the Cisco ON100 (Onplus) a close second.
Edited 1 time(s). Last edit at 02/08/2020 08:40PM by LeggoMyEggo.
|
Re: Debian on Dell Kace M300 February 08, 2020 10:03PM |
Registered: 4 years ago Posts: 22 |
bodhi Wrote:
-------------------------------------------------------
> Nice use of the internal SATA port!
Thanks. Next job is to get the bottom plate drilled out so I can mount the drive brackets and get it closed back up. Hopefully it doesn't get too hot in there!
> That's a good alternative if you stay with this
> system configuration and not booting other. You
> can also make another DTS to boot USB rootfs
> (root=/dev/sdxx) to be a rescue system. It is not
> flexible as using root device label in u-boot env,
> but since you already know how the DTS should be
> coded, so not bad at all!
I did boot from USB to set up the raid partitions. I originally tried to do it on my laptop by connecting the dual sata adapter via a USB adapter but it was only able to see one of the two drives - I guess it doesn't provide the port multiplier support that the m300 controller does. I tried to setup the md partitions with just one drive using the "missing" keyword for the second drive, thinking I could add it later on the m300 but I couldn't get it working. Which is to say, yes, a rescue usb is probably a great idea!!
LeggoMyEggo Wrote:
-------------------------------------------------------
> Funny you mention it, I've spent a number of
> hours (and spent some brain cells) trying to get
> bluetooth audio working with squeezelite and
> pulseaudio on the M300. Have the
> logitechmediaserver working as well after
> recompiling CPAN for Debian 10. It works for the
> most part but I am having issues getting things to
> auto load after boot.
You are using a USB DAC? Any recommendations? I thought this Topping D50S in silver would go nicely with the m300 but I'm too much of a tight wad to spend $250 on a DAC.
http://amzn.com/B07VJMJVC6
I don't have any squeezebox stuff working with Alpine on the M300 yet - just got the base OS to the point today that I think it looks good to press on. LMS will be the hardest to get going but is really the main thing I want to use this box for. Squeezelite with a DAC is a possibility but I'm not running any audio out of my current LMS server since I have numerous other players in service already.
> The problem for us not using RasPi's is that
> everything is written for Raspi! I have Raspi 3
> and 4 but from a hacking point of view they are
> not as much a challenge. Throw in it being
> headless without display and it increases the
> challenge. Quite the bargain this M300 is, if
> only it had USB3.0 or mPCIe but you won't find
> another Kirkwood device running at 2GHZ and with 2
> Gigs of Ram. They are so cheap, I have three of
> them. Plus you get network cables and if the unit
> shits the bed, you can recycle the SATA drive for
> other projects. This is now my favorite 'play
> plug' with the Cisco ON100 (Onplus) a close
> second.
Completely agree on all points! I've spent way more time on the m300 than on the RPi4 I got for Christmas. Not sure what that says about me?? That and the fact I'm planning on replacing my 10 year old Atom based LMS / file server with a 9 year old M300!?
-------------------------------------------------------
> Nice use of the internal SATA port!
Thanks. Next job is to get the bottom plate drilled out so I can mount the drive brackets and get it closed back up. Hopefully it doesn't get too hot in there!
> That's a good alternative if you stay with this
> system configuration and not booting other. You
> can also make another DTS to boot USB rootfs
> (root=/dev/sdxx) to be a rescue system. It is not
> flexible as using root device label in u-boot env,
> but since you already know how the DTS should be
> coded, so not bad at all!
I did boot from USB to set up the raid partitions. I originally tried to do it on my laptop by connecting the dual sata adapter via a USB adapter but it was only able to see one of the two drives - I guess it doesn't provide the port multiplier support that the m300 controller does. I tried to setup the md partitions with just one drive using the "missing" keyword for the second drive, thinking I could add it later on the m300 but I couldn't get it working. Which is to say, yes, a rescue usb is probably a great idea!!
LeggoMyEggo Wrote:
-------------------------------------------------------
> Funny you mention it, I've spent a number of
> hours (and spent some brain cells) trying to get
> bluetooth audio working with squeezelite and
> pulseaudio on the M300. Have the
> logitechmediaserver working as well after
> recompiling CPAN for Debian 10. It works for the
> most part but I am having issues getting things to
> auto load after boot.
You are using a USB DAC? Any recommendations? I thought this Topping D50S in silver would go nicely with the m300 but I'm too much of a tight wad to spend $250 on a DAC.
http://amzn.com/B07VJMJVC6
I don't have any squeezebox stuff working with Alpine on the M300 yet - just got the base OS to the point today that I think it looks good to press on. LMS will be the hardest to get going but is really the main thing I want to use this box for. Squeezelite with a DAC is a possibility but I'm not running any audio out of my current LMS server since I have numerous other players in service already.
> The problem for us not using RasPi's is that
> everything is written for Raspi! I have Raspi 3
> and 4 but from a hacking point of view they are
> not as much a challenge. Throw in it being
> headless without display and it increases the
> challenge. Quite the bargain this M300 is, if
> only it had USB3.0 or mPCIe but you won't find
> another Kirkwood device running at 2GHZ and with 2
> Gigs of Ram. They are so cheap, I have three of
> them. Plus you get network cables and if the unit
> shits the bed, you can recycle the SATA drive for
> other projects. This is now my favorite 'play
> plug' with the Cisco ON100 (Onplus) a close
> second.
Completely agree on all points! I've spent way more time on the m300 than on the RPi4 I got for Christmas. Not sure what that says about me?? That and the fact I'm planning on replacing my 10 year old Atom based LMS / file server with a 9 year old M300!?
|
Re: Debian on Dell Kace M300 February 08, 2020 10:32PM |
Registered: 9 years ago Posts: 429 |
sodface Wrote:
-------------------------------------------------------
>
> You are using a USB DAC? Any recommendations? I
> thought this Topping D50S in silver would go
> nicely with the m300 but I'm too much of a tight
> wad to spend $250 on a DAC.
> http://amzn.com/B07VJMJVC6
I've thought about USB DAC for the M300, even noticed the one you like (nice match to the finish of the M300), this one is about the most I would spend: Cheap USB DAC Hope it performs better than my cheap Sarbent USB audio adapter. There are dozens upon dozens of these things, some that cost north of $2,000 and I don't necessarily trust the reviews.
> I don't have any squeezebox stuff working with
> Alpine on the M300 yet - just got the base OS to
> the point today that I think it looks good to
> press on. LMS will be the hardest to get going
> but is really the main thing I want to use this
> box for.
Only problem with getting LMS to work on the M300 is that the pre-compiled CPAN version is meant for armhf (aka RasPi). For Debian 10, after you dpkg the latest nightly deb (which will fail to start because of the missing proper CPAN), you need to clone the slimserver git at https://github.com/Logitech/slimserver-vendor.git, switch to the CPAN subdirectory and run the buildme.sh script. This will create 5.28 version of CPAN that you will need to manually copy per the instructions on this page: https://github.com/Logitech/slimserver-vendor/tree/public/7.9/CPAN. Note the required packages you will need before compiling. Restart logitechmediaserver after the new CPAN directory has been copied.
Edited 2 time(s). Last edit at 02/08/2020 10:46PM by LeggoMyEggo.
-------------------------------------------------------
>
> You are using a USB DAC? Any recommendations? I
> thought this Topping D50S in silver would go
> nicely with the m300 but I'm too much of a tight
> wad to spend $250 on a DAC.
> http://amzn.com/B07VJMJVC6
I've thought about USB DAC for the M300, even noticed the one you like (nice match to the finish of the M300), this one is about the most I would spend: Cheap USB DAC Hope it performs better than my cheap Sarbent USB audio adapter. There are dozens upon dozens of these things, some that cost north of $2,000 and I don't necessarily trust the reviews.
> I don't have any squeezebox stuff working with
> Alpine on the M300 yet - just got the base OS to
> the point today that I think it looks good to
> press on. LMS will be the hardest to get going
> but is really the main thing I want to use this
> box for.
Only problem with getting LMS to work on the M300 is that the pre-compiled CPAN version is meant for armhf (aka RasPi). For Debian 10, after you dpkg the latest nightly deb (which will fail to start because of the missing proper CPAN), you need to clone the slimserver git at https://github.com/Logitech/slimserver-vendor.git, switch to the CPAN subdirectory and run the buildme.sh script. This will create 5.28 version of CPAN that you will need to manually copy per the instructions on this page: https://github.com/Logitech/slimserver-vendor/tree/public/7.9/CPAN. Note the required packages you will need before compiling. Restart logitechmediaserver after the new CPAN directory has been copied.
Edited 2 time(s). Last edit at 02/08/2020 10:46PM by LeggoMyEggo.
|
Re: Debian on Dell Kace M300 February 13, 2020 02:39PM |
Registered: 10 years ago Posts: 155 |
A user on the LMS forum has compiled Perl 5.28 for LMS and posted it here:
I could not get the buildme script to work, this kind soul stepped up on the forum and saved me. LMS has been running great on the M300 for about 5 months with a internal 120GB drive plugged into the SATA port.
I have been happy with the Muse DAC, typically available on ebay, but only see one there now. Maybe the virus.
Also, hifimediy has a well regarded DAC:
Both of these are in the non-audiophile price range, but are not junk either. I have one of the junk ones and one that looks like junk but sounds pretty good.
Edited 1 time(s). Last edit at 02/13/2020 02:41PM by mikeh49.
https://github.com/mw9/slimserver/commit/46c22a3c7e69187a2ead9392c53f1c90790a03fa
I could not get the buildme script to work, this kind soul stepped up on the forum and saved me. LMS has been running great on the M300 for about 5 months with a internal 120GB drive plugged into the SATA port.
I have been happy with the Muse DAC, typically available on ebay, but only see one there now. Maybe the virus.
https://www.ebay.com/itm/MUSE-HIFI-USB-to-S-PDIF-Coaxial-Optical-Converter-Analog-out-USB-DAC-PCM2704/392620943106?hash=item5b6a082702:g:7JsAAOSwbyVdIujg
Also, hifimediy has a well regarded DAC:
https://www.amazon.com/HiFiMeDIY-Digital-Analog-Converter-Optical/dp/B00AOH5JTQ/ref=sr_1_2?keywords=hifimediy&qid=1581626227&s=hi&sr=8-2
Both of these are in the non-audiophile price range, but are not junk either. I have one of the junk ones and one that looks like junk but sounds pretty good.
Edited 1 time(s). Last edit at 02/13/2020 02:41PM by mikeh49.
|
Re: Debian on Dell Kace M300 February 18, 2020 09:27AM |
Registered: 4 years ago Posts: 22 |
Thanks for the info mikeh49. I bought an Apple USB-C dongle/DAC and a two pack of USB-C to USB-A adapters from Amazon based on this review and some other positive comments about the Apple dongle:
https://www.audiosciencereview.com/forum/index.php?threads/review-apple-vs-google-usb-c-headphone-adapters.5541/
It's the first Apple product I've ever purchased and I did it reluctantly but I figure it was just a $8 dongle so it didn't really count, of course my daughter said that full Apple conversion is now required (not likely!). I can confirm it works on my Fedora laptop and it looks like it is recognized correctly on the M300 but I don't have alsa or any of the other necessary packages built for Alpine yet so I haven't been able to test it.
I ran into an issue with Alpine's package manager that you can read about here:
https://lists.alpinelinux.org/~alpine/apk-tools/%3CCAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug%40mail.gmail.com%3E
Came down to an issue with memory alignment that I never would have figured out on my own. I did find a couple references to it here on this site (after I knew what to search for) - this must be something that the Debian port accounts for in their configuration?
Would one of you post the results of cat /proc/cpu/alignment so I can configure Alpine the same way?
Thanks!
https://www.audiosciencereview.com/forum/index.php?threads/review-apple-vs-google-usb-c-headphone-adapters.5541/
It's the first Apple product I've ever purchased and I did it reluctantly but I figure it was just a $8 dongle so it didn't really count, of course my daughter said that full Apple conversion is now required (not likely!). I can confirm it works on my Fedora laptop and it looks like it is recognized correctly on the M300 but I don't have alsa or any of the other necessary packages built for Alpine yet so I haven't been able to test it.
I ran into an issue with Alpine's package manager that you can read about here:
https://lists.alpinelinux.org/~alpine/apk-tools/%3CCAGP1gyMH+GoXnGd3YQjg4piFYpMpNiHkC7PDO7BoHTSbYsP1Ug%40mail.gmail.com%3E
Came down to an issue with memory alignment that I never would have figured out on my own. I did find a couple references to it here on this site (after I knew what to search for) - this must be something that the Debian port accounts for in their configuration?
Would one of you post the results of cat /proc/cpu/alignment so I can configure Alpine the same way?
Thanks!
|
Re: Debian on Dell Kace M300 February 18, 2020 10:34AM |
Registered: 10 years ago Posts: 155 |
Not sure this is much help:
I didn't think Apple sold anything for $8, they must have misplaced the decimal point.
root@m300-2:~# cat /proc/cpu/alignment User: 0 System: 0 (0x0) Skipped: 0 Half: 0 Word: 0 DWord: 0 Multi: 0 User faults: 0 (ignored) root@m300-2:~#I think you need Bohdi's brain for this.
I didn't think Apple sold anything for $8, they must have misplaced the decimal point.
|
Re: Debian on Dell Kace M300 February 18, 2020 01:43PM |
Registered: 4 years ago Posts: 22 |
Thanks Mike, this memory alignment thing on the M300 may be something that could also affect you guys running Debian.
See:
https://wiki.debian.org/ArmEabiFixes#word_accesses_must_be_aligned_to_a_multiple_of_their_size
and
https://www.kernel.org/doc/html/latest/arm/mem_alignment.html
It looks like by your output above that you are set to "0" which I believe is what my Alpine install defaulted to and was causing the problem I talked about in the mailing list thread I linked to.
"0" supposedly means "A user process performing an unaligned memory access will cause the kernel to print a message indicating process name, pid, pc, instruction, address, and the fault code." but if it was printing any messages I never saw them anywhere. The crappy part about it was that the apk command I was using (alpine's package manager) worked for some things, sort of worked for others, and didn't work at all for still others, but the command never actually caused a crash or seg fault or anything else that would be an _obvious_ problem. I'd rather have that then something that "sort of" works and leaves you wondering what else can't be trusted.
//edit, see also https://stackoverflow.com/questions/16548059/how-to-trap-unaligned-memory-access
I'd be curious to see if you did a:
echo 2 > /proc/cpu/alignment
let the system run for a while and cat the file periodically if you'd see fault numbers going up (and being corrected by the kernel) which I think would mean that at the current setting of 0, the faults were still there, just not being caught and what's worse, not being corrected.
I could be completely misunderstanding the situation and settings, I just know I ran into an issue and it looks like you are running with the same setting I was.
//edit 2, now that I'm home I pulled the /cat/proc/alignment info off the two m300 I have running, keep in mind that the one that says "2 (fixup)" I just changed yesterday by doing the "echo 2 > /proc/cpu/alignment" as a troubleshooting step, so It's been running at 0 like the other one for the majority of it's uptime.
Don't know what your uptime was but it looks like you've had 0 errors which seems like a good thing. I think it either means your system config is accounting for it somehow or all the software you're running is coded to only do aligned memory access (or whatever the correct way of stating that is).
Edited 5 time(s). Last edit at 02/18/2020 05:08PM by sodface.
See:
https://wiki.debian.org/ArmEabiFixes#word_accesses_must_be_aligned_to_a_multiple_of_their_size
and
https://www.kernel.org/doc/html/latest/arm/mem_alignment.html
It looks like by your output above that you are set to "0" which I believe is what my Alpine install defaulted to and was causing the problem I talked about in the mailing list thread I linked to.
"0" supposedly means "A user process performing an unaligned memory access will cause the kernel to print a message indicating process name, pid, pc, instruction, address, and the fault code." but if it was printing any messages I never saw them anywhere. The crappy part about it was that the apk command I was using (alpine's package manager) worked for some things, sort of worked for others, and didn't work at all for still others, but the command never actually caused a crash or seg fault or anything else that would be an _obvious_ problem. I'd rather have that then something that "sort of" works and leaves you wondering what else can't be trusted.
//edit, see also https://stackoverflow.com/questions/16548059/how-to-trap-unaligned-memory-access
I'd be curious to see if you did a:
echo 2 > /proc/cpu/alignment
let the system run for a while and cat the file periodically if you'd see fault numbers going up (and being corrected by the kernel) which I think would mean that at the current setting of 0, the faults were still there, just not being caught and what's worse, not being corrected.
I could be completely misunderstanding the situation and settings, I just know I ran into an issue and it looks like you are running with the same setting I was.
//edit 2, now that I'm home I pulled the /cat/proc/alignment info off the two m300 I have running, keep in mind that the one that says "2 (fixup)" I just changed yesterday by doing the "echo 2 > /proc/cpu/alignment" as a troubleshooting step, so It's been running at 0 like the other one for the majority of it's uptime.
localhost:~# uptime 09:13:32 up 2 days, 4:17, load average: 0.00, 0.00, 0.00 localhost:~# cat /proc/cpu/alignment User: 53325 System: 0 (0x0) Skipped: 0 Half: 0 Word: 13837 DWord: 0 Multi: 0 User faults: 2 (fixup)
22:46:05 up 3 days, 19:52, load average: 0.00, 0.00, 0.00 m300-01:~$ cat /proc/cpu/alignment User: 13206 System: 0 (0x0) Skipped: 0 Half: 0 Word: 0 DWord: 0 Multi: 0 User faults: 0 (ignored)
Don't know what your uptime was but it looks like you've had 0 errors which seems like a good thing. I think it either means your system config is accounting for it somehow or all the software you're running is coded to only do aligned memory access (or whatever the correct way of stating that is).
Edited 5 time(s). Last edit at 02/18/2020 05:08PM by sodface.
|
Re: Debian on Dell Kace M300 February 18, 2020 06:45PM |
Registered: 10 years ago Posts: 155 |
Here's my production M300:
Runs Logitech Media Server and nothing else.
This has been running without a swap file; I configured one this morning.
The other M300 running with swap file, uptime 9 hrs:
Edited 2 time(s). Last edit at 02/18/2020 06:56PM by mikeh49.
root@Dell-M300:~# uptime 16:43:36 up 11 days, 5:44, 1 user, load average: 0.00, 0.00, 0.00 root@Dell-M300:~# cat /proc/cpu/alignment User: 0 System: 3 (__fixup_a_pv_table+0x44/0x54) Skipped: 0 Half: 0 Word: 3 DWord: 0 Multi: 0 User faults: 0 (ignored)
Runs Logitech Media Server and nothing else.
This has been running without a swap file; I configured one this morning.
The other M300 running with swap file, uptime 9 hrs:
root@m300-2:~# cat /proc/cpu/alignment User: 0 System: 0 (0x0) Skipped: 0 Half: 0 Word: 0 DWord: 0 Multi: 0 User faults: 0 (ignored)
Edited 2 time(s). Last edit at 02/18/2020 06:56PM by mikeh49.
|
Re: Debian on Dell Kace M300 February 18, 2020 08:55PM |
Admin Registered: 13 years ago Posts: 18,549 |
sodface,
This box architecture is Armv5te, i.e Kirkwood. Same as other Kirkwood boxes that we have been supporting since kernel 3.16.x. So I dont think alignment is a problem at all.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This box architecture is Armv5te, i.e Kirkwood. Same as other Kirkwood boxes that we have been supporting since kernel 3.16.x. So I dont think alignment is a problem at all.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 February 18, 2020 11:04PM |
Registered: 4 years ago Posts: 22 |
bodhi Wrote:
-------------------------------------------------------
> sodface,
>
> This box architecture is Armv5te, i.e Kirkwood.
> Same as other Kirkwood boxes that we have been
> supporting since kernel 3.16.x. So I dont think
> alignment is a problem at all.
Hi bodhi, you guys have way more knowledge on this than I do so I don't doubt you are correct, at least for debian, which is what this forum is about so I probably shouldn't be posting about Alpine here anyway. I'm definitely seeing memory alignment problems with this one application on Alpine though, as you can see from the number of errors in my output above. Mike's output from his one box indicates 3 errors so it doesn't seem to be a complete non-issue on debian but certainly nothing like I'm seeing. I think this is largely dependent on the application and how it's coded.
-------------------------------------------------------
> sodface,
>
> This box architecture is Armv5te, i.e Kirkwood.
> Same as other Kirkwood boxes that we have been
> supporting since kernel 3.16.x. So I dont think
> alignment is a problem at all.
Hi bodhi, you guys have way more knowledge on this than I do so I don't doubt you are correct, at least for debian, which is what this forum is about so I probably shouldn't be posting about Alpine here anyway. I'm definitely seeing memory alignment problems with this one application on Alpine though, as you can see from the number of errors in my output above. Mike's output from his one box indicates 3 errors so it doesn't seem to be a complete non-issue on debian but certainly nothing like I'm seeing. I think this is largely dependent on the application and how it's coded.
|
Re: Debian on Dell Kace M300 February 19, 2020 12:31AM |
Admin Registered: 13 years ago Posts: 18,549 |
sodface,
> about so I probably shouldn't be posting about
> Alpine here anyway. I'm definitely seeing memory
> alignment problems with this one application on
> Alpine though, as you can see from the number of
> errors in my output above.
On the contrary, when you're out of idea to fix something, please post here. We welcome any Linux distro users. You should see a very long thread about booting FreeBSD here :) We will learn something from it.
> Mike's output from his
> one box indicates 3 errors so it doesn't seem to
> be a complete non-issue on debian but certainly
> nothing like I'm seeing. I think this is largely
> dependent on the application and how it's coded.
I did not recall Mike has "bus error" ? usually iirc that it is hardware problem, or running a binary that was compiled for a wrong architecture. If other binaries are running fine on Alpine on this box, and then just one binary that has bus error, then it itself is suspected.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> about so I probably shouldn't be posting about
> Alpine here anyway. I'm definitely seeing memory
> alignment problems with this one application on
> Alpine though, as you can see from the number of
> errors in my output above.
On the contrary, when you're out of idea to fix something, please post here. We welcome any Linux distro users. You should see a very long thread about booting FreeBSD here :) We will learn something from it.
> Mike's output from his
> one box indicates 3 errors so it doesn't seem to
> be a complete non-issue on debian but certainly
> nothing like I'm seeing. I think this is largely
> dependent on the application and how it's coded.
I did not recall Mike has "bus error" ? usually iirc that it is hardware problem, or running a binary that was compiled for a wrong architecture. If other binaries are running fine on Alpine on this box, and then just one binary that has bus error, then it itself is suspected.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Kace M300 February 19, 2020 05:36AM |
Registered: 10 years ago Posts: 155 |
FWIW, here's the alignment info from a Pogo E02 running latest Debian and samba:
The M300 with the errors is running Logitech Media Server with Perl modules compiled by a LMS forum member for armel. Don't know if that means anything It'd s pretty big app I think. .
root@BlackPogo:~# uptime 03:28:46 up 7 days, 18:05, 1 user, load average: 0.00, 0.00, 0.00 root@BlackPogo:~# cat /proc/cpu/alignment User: 0 System: 0 (0x0) Skipped: 0 Half: 0 Word: 0 DWord: 0 Multi: 0 User faults: 0 (ignored)
The M300 with the errors is running Logitech Media Server with Perl modules compiled by a LMS forum member for armel. Don't know if that means anything It'd s pretty big app I think. .
