Debian on Dell Wyse 3020

i think i need some proper instructions.... this is what i gleaned from teh above and my attempt to boot from a 8GB usb stick

My steps
create usb partitions
BOOT=64MB-fat32 & rootfs=remainder-ext3
extract Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 to rootfs
extract linux-6.3.5-mvebu-tld-1-bodhi.tar.bz2 to BOOT
replace mmp3-dell-ariel.dtb
do mkimage shennanigans

create wloader.cfg in BOOT which also holds the unimage etc

<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot)"
<TX0D_END>

my fstab is the following

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=BOOT     /boot           vfat    rw,user,exec,umask=000  0       0
LABEL=rootfs    /              ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0

I have a keyboard and mouse installed and a monitor and I manually select the boot from usb option…
I see the screen telling me its trying to load D://Umiage etc etc and then it sits there blinking the green light at me. I have tried to connect to the console port with the standard settings in screen and I get a load of garbage – irrespective of which way round I connect the RX/TX cables

============================
Breaking stuff since 1994 :-)
============================

Gravelrash,

Look at this summary of instruction by Mischif in this thread:

https://forum.doozan.com/read.php?2,134563,135415#msg-135415

Try this first to see if the console output wil be OK. Note that it will show nothing during bootloader running, and then also not much while the kernel is booting.

sed -i 's/ttyS0 115200/ttyS2 115200/' /media/mischif/rootfs/etc/inittab

If you see nothing on serial console. Then boot with /dev/sda2 (you don't need to change fstab further, the rootfs LABEL in there should be OK).

<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=/dev/sda2 raid=noautodetect console=ttyS2,115200"
<TX0D_END>

And after log in Debian, install the new kernel 6.3.5.

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

i must have baulked something somewhere.... i had already followed the instructions from Mischif and done the remainder of the suggested changes lower down the page....

Ill trash and burn this stick and try again this evening

@Bodhi - thanks as always for help and support :)

============================
Breaking stuff since 1994 :-)
============================

YUP - had well and truly baulked it :)

I re did the following and im in and currently connecting it to my apt-cache device and doing an update before i do the kernel package update.

here are the actions i did to get it booting......... interestingly i have zero console access. current thinking is my usb/ttl adaptor has gone to siliconheaven to meet all the old calcultors

Reset to factory defaults

setup the files on the partitions

tar -C /media/gravelrash/BOOTFS/ -x -j -f /home/gravelrash/Downloads/linux-6.3.5-mvebu-tld-1-bodhi.tar.bz2
tar -C /media/gravelrash/BOOTFS/ -x -f /media/gravelrash/BOOTFS/linux-dtb-6.3.5-mvebu-tld-1.tar
cat /media/gravelrash/BOOTFS/zImage-6.3.5-mvebu-tld-1 /media/gravelrash/BOOTFS/dts/mmp3-dell-ariel.dtb > /media/gravelrash/BOOTFS/zImage.fdt

sudo tar -C /media/gravelrash/rootfs/ -x -j -f /home/gravelrash/Downloads/Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2
sudo rm /media/gravelrash/rootfs/root/set_persistent_mac_address
sudo sed -i 's/ttyS0 115200/ttyS2 115200/' /media/gravelrash/rootfs/etc/inittab
sudo sed -i '2a rename \/enx*=eth0' /media/gravelrash/rootfs/etc/network/interfaces

mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -d /media/gravelrash/BOOTFS/zImage.fdt /media/gravelrash/BOOTFS/uImage
sudo mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -d /media/gravelrash/rootfs/boot/initrd.img-5.13.8-mvebu-tld-1 /media/gravelrash/BOOTFS/uInitrd

wloader

<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=/dev/sda2 raid=noautodetect console=ttyS2,115200"
<TX0D_END>

ssh into device

gravelrash@5060:~$ ssh root@debian.lan
root@debian.lan's password: 
Linux debian 6.3.5-mvebu-tld-1 #1 SMP PREEMPT Thu Jun  1 02:35:15 PDT 2023 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Jul  1 06:19:32 2023 from 192.168.10.188
debian
192.168.10.13
Dell Ariel
Linux version 6.3.5-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Thu Jun  1 02:35:15 PDT 2023
Debian 11.7
Sat Jul 1 06:27:36 PDT 2023 up 15 minutes
root@debian:~#

fdisk -l

root@debian:/# fdisk -l
Disk /dev/sda: 7.45 GiB, 8004304896 bytes, 15633408 sectors
Disk model: Cruzer Fit      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb180b99d
Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1  *       2048  1050623  1048576  512M  b W95 FAT32
/dev/sda2       1050624 15632383 14581760    7G 83 Linux

mount points

root@debian:/etc/apt/apt.conf.d# mount | grep sd
/dev/sda2 on / type ext3 (rw,noatime,errors=remount-ro)

fstab

root@debian:/etc/apt/apt.conf.d# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=BOOTFS  /boot       vfat    umask=0077      0       1
LABEL=rootfs  /           ext3    noatime,errors=remount-ro 0 1
tmpfs         /tmp        tmpfs   defaults          0       0

unknown file system

root@debian:/boot# mount /dev/sda1 /mnt
mount: /mnt: unknown filesystem type 'vfat'.
root@debian:/boot# 

 blkid
/dev/sda1: LABEL_FATBOOT="BOOTFS" LABEL="BOOTFS" UUID="DE4A-D010" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b180b99d-01"
/dev/sda2: LABEL="rootfs" UUID="cc5d8fd8-485d-4601-bc72-6c6426d6e64b" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="b180b99d-02"

modprobe vfat
modprobe: FATAL: Module vfat not found in directory /lib/modules/6.3.5-mvebu-tld-1
root@debian:/etc/apt/apt.conf.d#

lsblk

root@debian:/boot# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    1  7.5G  0 disk 
|-sda1   8:1    1  512M  0 part 
`-sda2   8:2    1    7G  0 part /

im wondering if there are many different flavours of these 3020 devices.. i cant for the life of me get the MMC to be accessible

============================
Breaking stuff since 1994 :-)
============================



Edited 9 time(s). Last edit at 07/01/2023 09:48AM by Gravelrash.

Gravelrash,

> here are the actions i did to get it
> booting......... interestingly i have zero console
> access. current thinking is my usb/ttl adaptor has
> gone to siliconheaven to meet all the old
> calcultors

... and all the 5" floppy disks :)

> Reset to factory defaults

Good to have this Factory Reset procedure handy.

> im wondering if there are many different flavours
> of these 3020 devices.. i cant for the life of me
> get the MMC to be accessible

The next step is to install linux-6.3.5-mvebu-tld-1-bodhi.tar.bz2 or linux-6.3.8-mvebu-tld-1-bodhi.tar.bz2.

Because while you can boot with 6.3.5 uImage, you have not installed the full kernel in the rootfs.

So install linux-6.3.8-mvebu-tld-1-bodhi.tar.bz2, and then boot with the label.

wloader config

<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=LABEL=rootfs raid=noautodetect console=ttyS2,115200"
<TX0D_END>

After that, everything will fall into place. RTC and MMC should work.

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

Mine has sticker with 'REV 3.30' on PCB. Quick search on local auction site shows ones with 'REV 3.10' and "REV 3.02".

> Mine has sticker with 'REV 3.30' on PCB. Quick
> search on local auction site shows ones with 'REV
> 3.10' and "REV 3.02".

I think the Rev might be related to other fixes (most likely SW related). This box boots with eMMC rootfs, so it must be accessible regardless of revisions.

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

and as if by magic - replacing the kernel and then moving to another machine to copy it to the fat32 partition.... all works as is should...

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1  *       2048  1050623  1048576  512M  b W95 FAT32
/dev/sda2       1050624 15632383 14581760    7G 83 Linux

Disk /dev/mtdblock0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0: 3.64 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot   Start     End Sectors   Size Id Type
/dev/mmcblk0p1          256 1933311 1933056 943.9M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      1933312 3866623 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p3 *    3866624 5799935 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p4      5799936 7634943 1835008   896M  c W95 FAT32 (LBA)


Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1  *       2048  1050623  1048576  512M  b W95 FAT32
/dev/sda2       1050624 15632383 14581760    7G 83 Linux


Disk /dev/mtdblock0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 3.64 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot   Start     End Sectors   Size Id Type
/dev/mmcblk0p1          256 1933311 1933056 943.9M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      1933312 3866623 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p3 *    3866624 5799935 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p4      5799936 7634943 1835008   896M  c W95 FAT32 (LBA)

im going to see if i can get this little beauty to output to screen when it boots.... ill try the same approach as we did for this little beasty

console on the HP

unless someone already knows and save me the effort...

Question I tried to use flashrom to update/replace the dell "bios" (i know it isnt a bios - but i dont know what else to call it :) .. however it doesnt seem to recognise, or more realistically, i dont know how to translate the information from the link in previous posts that were aimed at fedora to linux - it seems to be missing some stuff and has differing locations for spi references

echo spidev >/sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver_override
echo spi1.0 >/sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver/unbind
echo spi1.0 >/sys/bus/spi/drivers/spidev/bind
echo spi1.0 >/sys/bus/spi/drivers/spidev/bind
flashrom -p linux_spi:dev=/dev/spidev1.0 -w q7c07.rom
#
#
root@debian:~#
-bash: /sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver_override: No such file or directory
-bash: /sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver/unbind: No such file or directory
-bash: /sys/bus/spi/drivers/spidev/bind: No such file or directory
-bash: /sys/bus/spi/drivers/spidev/bind: No such file or directory
root@debian:~#

============================
Breaking stuff since 1994 :-)
============================



Edited 4 time(s). Last edit at 07/02/2023 06:00PM by Gravelrash.

this may be handy to know whats going on and what modules would be need to get this thing fully functional... or not...

.
|-- bin
|   `-- ica
|-- etc
|   |-- ld.so.cache
|   |-- ld.so.conf
|   `-- ld.so.conf.d
|       |-- arm-linux-gnueabi.conf
|       `-- libc.conf
|-- files.txt
|-- lib
|   |-- arm-linux-gnueabi
|   |   |-- libBrokenLocale.so.1
|   |   |-- libanl.so.1
|   |   |-- libc.so.6
|   |   |-- libcidn.so.1
|   |   |-- libcrypt.so.1
|   |   |-- libdl.so.2
|   |   |-- libgcc_s.so.1
|   |   |-- libgcrypt.so.11
|   |   |-- libglib-2.0.so.0
|   |   |-- libgpg-error.so.0
|   |   |-- libkeyutils.so.1
|   |   |-- libm.so.6
|   |   |-- libnss_db.so.2
|   |   |-- libnss_dns.so.2
|   |   |-- libnss_files.so.2
|   |   |-- libnss_hesiod.so.2
|   |   |-- libpcre.so.3
|   |   |-- libpng12.so.0
|   |   |-- libpthread.so.0
|   |   |-- libresolv.so.2
|   |   |-- librt.so.1
|   |   |-- libselinux.so.1
|   |   |-- libthread_db.so.1
|   |   `-- libz.so.1
|   `-- ld-linux.so.3
|-- pkg
|   `-- base.arm.pkg
`-- usr
    |-- bin
    |   |-- mmsv
    |   `-- mmsv_dove
    `-- lib
        `-- arm-linux-gnueabi
            |-- gstreamer-0.10
            |   |-- libgstaudioconvert.so
            |   `-- libgstcoreelements.so
            |-- libffi.so.5
            |-- libgio-2.0.so.0
            |-- libglib-2.0.so
            |-- libgmodule-2.0.so
            |-- libgmodule-2.0.so.0
            |-- libgobject-2.0.so
            |-- libgobject-2.0.so.0
            |-- libgstapp-0.10.so.0
            |-- libgstaudio-0.10.so
            |-- libgstaudio-0.10.so.0
            |-- libgstbase-0.10.so
            |-- libgstbase-0.10.so.0
            |-- libgsth264parse.so.0
            |-- libgstinterfaces-0.10.so
            |-- libgstinterfaces-0.10.so.0
            |-- libgstjpeg.so.0
            |-- libgstnetbuffer-0.10.so.0
            |-- libgstpbutils-0.10.so
            |-- libgstpbutils-0.10.so.0
            |-- libgstreamer-0.10.so
            |-- libgstreamer-0.10.so.0
            |-- libgstrtp-0.10.so
            |-- libgstrtp-0.10.so.0
            |-- libgstrtpdemux.so.0
            |-- libgstudp.so.0
            |-- libgstvideo-0.10.so
            |-- libgstvideo-0.10.so.0
            |-- libgstwyse.so.0
            |-- libgstwysevmeta.so.0
            |-- libgthread-2.0.so
            |-- libgthread-2.0.so.0
            |-- libjpeg.so.8
            |-- liborc-0.4.so.0
            |-- libstdc++.so.6
            |-- libtfm.so
            |-- libxml2.so
            `-- libxml2.so.2

11 directories, 73 files

============================
Breaking stuff since 1994 :-)
============================

Gravelrash,


> Question I tried to use flashrom to
> update/replace the dell "bios" (i know it isnt a
> bios - but i dont know what else to call it :) ..
> however it doesnt seem to recognise, or more
> realistically, i dont know how to translate the
> information from the link in previous posts that
> were aimed at fedora to linux - it seems to be
> missing some stuff and has differing locations for
> spi references
>
>

> echo spidev
> >/sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver_override
> echo spi1.0
> >/sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver/unbind
> echo spi1.0 >/sys/bus/spi/drivers/spidev/bind
> echo spi1.0 >/sys/bus/spi/drivers/spidev/bind
> flashrom -p linux_spi:dev=/dev/spidev1.0 -w
> q7c07.rom
> #
> #
> root@debian:~#
> -bash:
> /sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver_override:
> No such file or directory
> -bash:
> /sys/devices/platform/soc/d4000000.apb/d4035000.spi/spi_master/spi1/spi1.0/driver/unbind:
> No such file or directory
> -bash: /sys/bus/spi/drivers/spidev/bind: No such
> file or directory
> -bash: /sys/bus/spi/drivers/spidev/bind: No such
> file or directory
> root@debian:~# 
> 
> 
>

It is a lot easier now in Debian, since we got SPI mtd. That's what the update wload.cfg was:

Quote

create wloader.cfg in BOOT which also holds the unimage etc
<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot)"
<TX0D_END>

So

cat /proc/mtd

If it is

dev:    size   erasesize  name
mtd0: 00400000 00001000 "boot"

Then you can flash that ROM file to mtd0.

Warning: this flashing command could brick the box is if does not work. I was going to try this whenever I get back to this subject and actually try it on the box myself (so I would risk bricking my box first before telling others to try). You've been warned :)

flashcp -v q7c07.rom /dev/mtd0

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

bodhi Wrote:
-------------------------------------------------------
> Warning: this flashing command
> could brick the box is if does not work. I was
> going to try this whenever I get back to this
> subject and actually try it on the box myself (so
> I would risk bricking my box first before telling
> others to try). You've been warned :)
>
>

> flashcp -v q7c07.rom /dev/mtd0
>

:) Ive never known fear.... this unit was to give its life in testing the steps to install a working version of your "distro" and aid in the writing up... if it becomes brick - it becomes a brick :) whats the worst that can happen... it will mean i have to learn how to use a clamp and an spi flashing tool :)))

============================
Breaking stuff since 1994 :-)
============================

:) oooooops :)

the sizes match but not the name... so i just went for it.... teeheee and lo we have a brick :)

root@debian:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00001000 "spi0.0"
root@debian:~# mc

root@debian:~# flashcp -v q7c07.rom /dev/mtd0
Erasing blocks: 512/512 (100%)
Writing data: 10k/2048k (0%)
While writing data to 0x00000000-0x00002800 on /dev/mtd0: Connection timed out

EDIT
actually scratch that - ive just power cycled the device and it boots into debian fine

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/02/2023 06:35PM by Gravelrash.

> actually scratch that - ive just power cycled the
> device and it boots into debian fine

Phew!

There is something peculiar that I guess I need to learn about the SPI flash in this box.

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

just tested to see if its possible to erase the MMC and boot from it using the label and also the usbkey...

success!

root@debian:/# blkid
/dev/sda1: LABEL_FATBOOT="BOOTFS" LABEL="BOOTFS" UUID="DE4A-D010" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b180b99d-01"
/dev/sda2: LABEL="rootfs" UUID="cc5d8fd8-485d-4601-bc72-6c6426d6e64b" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="b180b99d-02"
/dev/mmcblk0p1: LABEL="NAND" UUID="474b483d-3525-4179-b0e8-f82bd9446942" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="db391c54-01"
root@debian:/# 
root@debian:/# 
root@debian:/# 
root@debian:/# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1024064k,nr_inodes=184609,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=205904k,mode=755)
/dev/mmcblk0p1 on / type ext3 (rw,noatime,errors=remount-ro)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=411800k)
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
root@debian:/#

i did note that all the prior partitions on the EMMC were of a W95 type... so i will repeat when i get a chance with this as a full drop on a fat32 partition... ill let you know how i get on

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/03/2023 11:01AM by Gravelrash.

anything else you would like me to try ???

do we know which graphics processor/driver this unit uses??

Mali-maybe?

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/03/2023 11:34AM by Gravelrash.

p.s. you folks are amazing.......... i just test and tinker about

============================
Breaking stuff since 1994 :-)
============================

> do we know which graphics processor/driver this
> unit uses??
>
> Mali-maybe?

Not Mali. It is the Marvell SoC MMP3 GPU.

The link to PDF is old, but can be found with Wayback Machine.

https://www.kernel.org/doc/readme/Documentation-arm-Marvell-README

Quote

PXA2128, a.k.a. MMP3 (OLPC XO4, Linux support not upstream)
Product Brief : http://www.marvell.com/application-processors/armada/pxa2128/assets/Marvell-ARMADA-PXA2128-SoC-PB.pdf
Application processor only
Core: Dual-core ARMv7 compatible Sheeva PJ4C core

So the situation is much like the Marvell Dove SoC. Stock OS use frame buffer, latest Linux supposes to have DRM graphic driver. Dove has DRM in mainline. However, I'm not sure about MMP3.

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

> i did note that all the prior partitions on the
> EMMC were of a W95 type... so i will repeat when i
> get a chance with this as a full drop on a fat32
> partition... ill let you know how i get on

Hold on. Linux does not run on FAT32. If you can log into stock, list the mount points (can't recall if others already did in this thread).

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

bodhi Wrote:
-------------------------------------------------------
> > do we know which graphics processor/driver this
> > unit uses??
> >
> >
> Mali-maybe?
>
> Not Mali. It is the Marvell SoC MMP3 GPU.
>
> The link to PDF is old, but can be found with
> Wayback Machine.
>
> https://www.kernel.org/doc/readme/Documentation-arm-Marvell-README
>
>

Quote

PXA2128, a.k.a. MMP3 (OLPC XO4, Linux
> support not upstream)
> Product Brief :
> http://www.marvell.com/application-processors/armada/pxa2128/assets/Marvell-ARMADA-PXA2128-SoC-PB.pdf
> Application processor only
> Core: Dual-core ARMv7 compatible Sheeva PJ4C
> core

>
> So the situation is much like the Marvell Dove
> SoC. Stock OS use frame buffer, latest Linux
> supposes to have DRM graphic driver. Dove has DRM
> in mainline. However, I'm not sure about MMP3.

Info to be verified, of course :)

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

no stock left on this device now....

Mountpoints from post earlier up the chain

Device         Boot   Start     End Sectors   Size Id Type
/dev/mmcblk0p1          256 1933311 1933056 943.9M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      1933312 3866623 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p3 *    3866624 5799935 1933312   944M  c W95 FAT32 (LBA)
/dev/mmcblk0p4      5799936 7634943 1835008   896M  c W95 FAT32 (LBA)

it is possible to run Linux on a "dos" type partition, from memory umsdos used to do it back in the day and i distinctly remember installing a version of linux that you launched from within M$ Windows95.... admittedly it did reboot into an msdos mode and then load linux on top.. back in mid to late 90's some computer magazines allowed the installation of Linux from there cdroms and you booted it from a batch file!. I even used to run a router from a 3.5" floppy that had been sys'd with win95 and then loaded a batch file to load the linux goodness

found it :) https://archive.org/details/win-linux-2000 - im going to make the dangerous assumption here that part of the stripped down OS that acts as the "bios" has syntax to allow booting from msdos partitions a version of linux - if memeory serves me correctly, teh same way that the early boot loaded in Suse5 used to do... you chose the image you wanted to load and added it to your boot options.. was before grub became a thing though...

i cant remember if its syslinux or something like that... memory does funny things as one archives ones memories.. i remember now *LILO* or loadlin

bodhi Wrote:
-------------------------------------------------------
> > i did note that all the prior partitions on
> the
> > EMMC were of a W95 type... so i will repeat when
> i
> > get a chance with this as a full drop on a
> fat32
> > partition... ill let you know how i get on
>
> Hold on. Linux does not run on FAT32. If you can
> log into stock, list the mount points (can't
> recall if others already did in this thread).

============================
Breaking stuff since 1994 :-)
============================



Edited 5 time(s). Last edit at 07/04/2023 08:39AM by Gravelrash.

am i correct in my assumption that the "video driver" is loaded in this...

root@debian:~# lsmod
Module                  Size  Used by
vfat                   20480  1
fat                    69632  1 vfat
joydev                 20480  0
sg                     28672  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
fuse                   98304  1
drm                   360448  0
drm_panel_orientation_quirks    16384  1 drm
configfs               36864  1
ip_tables              20480  0
x_tables               24576  1 ip_tables
hid_logitech_hidpp     40960  0
mmc_block              40960  0
spi_pxa2xx_platform    24576  0
ssp                    16384  1 spi_pxa2xx_platform
i2c_pxa                20480  0
hid_logitech_dj        24576  0
uas                    20480  0

I will be working on the assumption that updating the inittab and remaking the uimage etc should be enough to get this thing outputting to a monitor - adding fbdev as well obvs

for giggle im using tasksel to install me a full xfce desktop environment on the usb drive in readiness :) taken well over an hour so far doing it via ssh

============================
Breaking stuff since 1994 :-)
============================



Edited 2 time(s). Last edit at 07/04/2023 12:58PM by Gravelrash.

struggling to get a desktop to work on this.... so having some fun launching gui apps from an ssh session

heres how if you have never done it :)

install your gui tool of choice and satisfy its dependencies!

modify this file to enable the functionality and ensure the following options are set as enabled, save and close the file

nano /etc/ssh/sshd_config

   X11Forwarding yes
   X11DisplayOffset 10

then ssh to your device and load the gui app

in my case thunar

ssh -Y -t user@debian.lan 'thunar'

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/04/2023 02:02PM by Gravelrash.

Gravelrash,

-------------------------------------------------------
> struggling to get a desktop to work on this.... so
> having some fun launching gui apps from an ssh
> session
>
> heres how if you have never done it :)
>
> install your gui tool of choice and satisfy its
> dependencies!
>
> modify this file to enable the functionality and
> ensure the following options are set as enabled,
> save and close the file
>

> nano /etc/ssh/sshd_config
> 
>    X11Forwarding yes
>    X11DisplayOffset 10 
>

>
> then ssh to your device and load the gui app
>
> in my case thunar
>
>

> ssh -Y -t user@debian.lan 'thunar'
>

So the picture is what's on your monitor? Meaning the kernel DRM driver works?

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

bodhi Wrote:
> So the picture is what's on your monitor? Meaning
> the kernel DRM driver works?


For clarity of what i wrote above, as reading it back it wasnt exactly clear what i was doing

I cannot get the TX0D to output to screen by adding the fbdev driver into the init tab and remaking the uimages etc. If i do, the system doesnt appear to boot (remember i dont have a working ttl device and rely solely on ping to see the device is on the network)

i rolled it back to the working state and associated settings as found when doing the install from the instructions already posted in the thread, then installed a full xfce desktop from tasksel. I can see that the drm modules are loaded on boot and i can connect via ssh.

using ssh and x-forwarding to the TX0D, from my local "linux Mint" installation, i can run the program shown in the screenshot.

Can anyone shed any light on the correct way or settings to get the display to output to the screen? i used the same approach as the the HPT5235 and "no cigar"

attached image to show my local workstation and also the ssh x-forwarding working from the TX0D to the local Linux unit (5060)

============================
Breaking stuff since 1994 :-)
============================



Edited 2 time(s). Last edit at 07/05/2023 04:06PM by Gravelrash.

Does anyone have a link to documentation on the wloader? particularly on what can be passed via the wloader.cfg?
.
Id be very interested in reading this and seeing what i can make it do - my inexperience with this kind of loader has not allowed me to boot from the mmc. ive tried a simple approach of having a small vfat partition on the emmc and the rootfs on an ext3 partition behind it on the emmc... but as i say, my inexperience has brought me to no success...........

yet :)

============================
Breaking stuff since 1994 :-)
============================



Edited 2 time(s). Last edit at 07/05/2023 04:41PM by Gravelrash.

Gravelrash

> attached image to show my local workstation and
> also the ssh x-forwarding working from the TX0D to
> the local Linux unit (5060)

I see. The same approach as we did for the HP T5235 works for any Linnux box (using vnc or xrdp) to connect to the desktop app of choice.

What this box MM3 SoC and the HP T5335z (Dove SoC) potential is to use DRM driver to run the display monitor in full graphic mode when one connecs a monitor.

Unfortunately, I have not tried very hard get the Dove DRM to work. And have not researched whether the MMP3 DRM has been mainlined or not.

Stock OS for these boxes use the acient frame buffer driver. That FB driver is no longer in mainline Linux.

With that said, there is a new potential shortcut: Simple FB DRM. I'll build a new test kernel to see if we can use the same settings as stock.

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

Gravelrash,

-------------------------------------------------------
> Does anyone have a link to documentation on the
> wloader? particularly on what can be passed via
> the wloader.cfg?
> .
> Id be very interested in reading this and seeing
> what i can make it do - my inexperience
> with this kind of loader has not allowed me to
> boot from the mmc. ive tried a simple approach of
> having a small vfat partition on the emmc and the
> rootfs on an ext3 partition behind it on the
> emmc... but as i say, my inexperience has brought
> me to no success...........
>
> yet :)

Currently, only USB and network booting are supported by this wloader.

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

Gravelrash Wrote:
-------------------------------------------------------
> Does anyone have a link to documentation on the
> wloader? particularly on what can be passed via
> the wloader.cfg?
> .
> Id be very interested in reading this and seeing
> what i can make it do - my inexperience
> with this kind of loader has not allowed me to
> boot from the mmc. ive tried a simple approach of
> having a small vfat partition on the emmc and the
> rootfs on an ext3 partition behind it on the
> emmc... but as i say, my inexperience has brought
> me to no success...........
>
> yet :)

Only minimal doc that I am aware of is located at https://linux-mmp.docs.kernel.org/dell-wyse-3020.html#booting-with-wloader

Thanks Ray - that's all i was aware of as well.. shame there isn't more that is widely known. ill keep tinkering and see what i can come up with. I'm going to get another unit and see if i can dump the partitions from it to a removable disk - to see if there is anything interesting or obvious on it that will lead to the booting directly from the EMMC. :) I can but hope :)

@bodhi
as for the testing of the kernel and steps to make the installation work. this unit works well and definitely allows for the booting from the flash to a full installation of debian on the nand.


@kaze & @Mischif - good work! well done


I'll wait for the other unit to land before i do anything more on this one. Are we happy that this is now suitable for a write up and a howto

============================
Breaking stuff since 1994 :-)
============================

Gravelrash,

>
> I'll wait for the other unit to land before i do
> anything more on this one. Are we happy that this
> is now suitable for a write up and a howto

Yes. Please do that. I think we are at the point for a detailed Howto.

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