Hi there,

im trying to install debian on my nasbox but having difficulties of finding the correct u-boot
and such. Im fairly familiar and comfortable using basic linux commandline tools so that
isnt the problem. I have currently installed plugout.ne fvdw firmware 18.3 with their u-boot.
So gpt and usb capabilities should be there. Made usb rootfs stick according to directions
from https://forum.doozan.com/read.php?2,12096 01 nov 2023.

Tried booting it with instructions found :

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv usb_boot 'mw 0x800000 0 1; ext2load usb 0:1 0x800000 /boot/uImage; if ext2load usb 0:1 0x2100000 /boot/uInitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
printenv
boot




Marvell>> boot
boot
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
GPT: skipping last lba check
.
## Valid EFI partition found ##
GPT: skipping last lba check
.
## Valid EFI partition found ##
T Device NOT ready
   Request Sense returned 06 28 00
Device NOT ready
   Request Sense returned 06 28 00
** ext2fs_devread() read error **

** Unable to read "/boot/uImage" from usb 0:1 **
Device NOT ready
   Request Sense returned 06 28 00
*** ERROR: Can't read GPT header ***
get_partition_info_efi: *** ERROR: Invalid GPT ***
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number
stopping USB..
After that it boots from hdd

ahuovinen,

> So gpt and usb capabilities should be there. Made
> usb rootfs stick according to directions
> from https://forum.doozan.com/read.php?2,12096 01
> nov 2023.

When you are setting up the first time, use MBR partition and Ext3 file system. Don't use GPT, and don't use Ext4.

After booting into Debian in USB, you can try GPT if u-boot supports it (looks like it's buggy). And stock u-boots ususally do not support Ext4.

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

Thank you for the quick reply,

I can get into u-boot console using windows program fvdw-sl-console which is an installer application for that firmware and have it currently installed.

Marvell>> version
version

U-Boot 1.1.4 (Jan  7 2013 - 21:15:04) Marvell version: 3.4.16  LaCie 1.3.9 256MB fvdw gpt usbboot vs80

I found out that my usb stick actually was broken OR the nasbox is a picky mf as for the brand of sticks :D . Bought a new one and now i get this (removed loads of loading info)

5791271 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-6.5.7-kirkwood-tld-1
   Created:      2023-10-31  22:53:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6223880 Bytes =  5.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Removed the loading part. -- waited for like 30 minutes and tried to log in using ssh.. but no luck.

Also i tried of repartitioning the hdd so that debian-rootfs is on sda7 like in the fvdw firmware but that didnt work either.

I also understand that Lacie networkspace is supported on U-boot directly as i found some stuff for it on U-boot sources.
Used git to clone it locally and installed cross-compiler stuff for it.

Also couldnt compile clunc myself cause the github was missing some headerfile.

ahuovinen,

You should follow this instruction:

Boot Kirkwood rootfs with stock u-boot
https://forum.doozan.com/read.php?2,102054,105374#msg-105374

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



Edited 1 time(s). Last edit at 03/09/2024 01:21AM by bodhi.

Well, still no luck.

## Booting image at 00800000 ...
   Image Name:   Linux-6.5.7-kirkwood-tld-1
   Created:      2023-10-31  22:53:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6223880 Bytes =  5.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-6.5.7-kirkwood-tld-1
   Created:      2023-10-31  22:53:55 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5791207 Bytes =  5.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

actually yes, it gets up. and gets ip. but port 22 stays as closed according to nmap. So i cannot ssh in.



Edited 1 time(s). Last edit at 03/09/2024 02:13AM by ahuovinen.

Bought usb serial port adapter, using settings 115200 8n1 and at boot i get nothing sensible. only looks like random characters. what could be the correct settings for serial?

-a

ahuovinen,

> it gets up. and gets ip. but port 22 stays as closed according to nmap. So i cannot ssh in.

Please post the log what you did when you created the rootfs (especially Step 4). Or if you keep the log of that rootfs creation session, post the entire log.

Quote

4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time, or running kwboot with latest u-boot image).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-6.5.7-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt uImage
sync

> Bought usb serial port adapter, using settings
> 115200 8n1 and at boot i get nothing sensible.
> only looks like random characters. what could be
> the correct settings for serial?

Try swaping RX-TX. Most of the serial converters need RX-TX and TX-RX connections, but some old converter already swapped.

And this is the correct command with picocom:

picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0

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

That sets baudrate at 115200 - flowcontrol to none, parity to none and databits to 8 and device to ttyUSB0 as i had.

so no difference. still loads of unreadable stuff.. the differnce is that when that fvdw firmware boots it shows up the boot messages and when i try to boot from the stick.. nothing.. pm me if i can use skype to call you or smthing? .

-a

bodhi Wrote:
-------------------------------------------------------
> ahuovinen,
>
> > it gets up. and gets ip. but port 22 stays as
> closed according to nmap. So i cannot ssh in.
>
> Please post the log what you did when you created
> the rootfs (especially Step 4). Or if you keep the
> log of that rootfs creation session, post the
> entire log.
>
>

Quote

4. (Stock u-boot only) Create uImage with
> embedded DTB for booting with older u-boots (2012
> or earlier). Skip this step if you have installed
> the latest U-Boot for Kirkwood (or are installing
> this u-boot at the same time, or running kwboot
> with latest u-boot image).
>
> Please replace kirkwood-goflexnet.dtb below with
> the correct DTB name for your box (see the folder
> /media/sdb1/boot/dts for the exact spelling of
> your Kirkwood box name).
>
> Generate the uImage with DTB embedded inside:
> cd /media/sdb1/boot
> cp -a zImage-6.5.7-kirkwood-tld-1 zImage.fdt
> cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
> mv uImage uImage.orig
> mkimage -A arm -O linux -T kernel -C none -a
> 0x00008000 -e 0x00008000 -n
> Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt uImage
> sync

>
>
> > Bought usb serial port adapter, using settings
> > 115200 8n1 and at boot i get nothing sensible.
> > only looks like random characters. what could
> be
> > the correct settings for serial?
>
> Try swaping RX-TX. Most of the serial converters
> need RX-TX and TX-RX connections, but some old
> converter already swapped.
>
> And this is the correct command with picocom:
>

> picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0
>

and yes, RX needs to go to TX and TX needs to go to RX. TX means transmit and RX means receive.

> so no difference. still loads of unreadable
> stuff.. the differnce is that when that fvdw
> firmware boots it shows up the boot messages

May be that u-boot messed up the normal serial console. But not likely, can you interrupt serial console when it boots? If yes,

ver
help
printenv

> when i try to boot from the stick.. nothing..

See what I asked above.

> me if i can use skype to call you or smthing? .

Sorry, troubleshooting should be done in this forum only.

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



Edited 1 time(s). Last edit at 03/09/2024 05:07PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> ahuovinen Wrote:
> -------------------------------------------------------
> > That sets baudrate at 115200 - flowcontrol to
> > none, parity to none and databits to 8 and
> device
> > to ttyUSB0 as i had.
> >
> > so no difference. still loads of unreadable
> > stuff.. the differnce is that when that fvdw
> > firmware boots it shows up the boot messages
>
> May be that u-boot messed up the normal serial
> console.

>
> > when i try to boot from the stick.. nothing..
>
> See what I asked above.

Well, i could compile mainline nwsp2 u-boot from https://source.denx.de/u-boot/u-boot.git
but no way to test it before flashing because no working serial....

>
> > me if i can use skype to call you or smthing? .
>
> Sorry, troubleshooting should be done in this
> forum only.


well would be more than happy to share everything i find out in here if i get the developement running. most likely would create gentoo support for lacie nas because openRC is bettter than sysVinit and systemd

Since this box is very old, check the bootROM version at u-boot console

md ff00003c

If it is older than 1.21, kwboot won't work.

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

Marvell>> md ff00003c
md ff00003c
ff00003c: 00000000 00000000 00000000 00000000 ................
ff00004c: 00000000 00000000 00000000 00000000 ................
ff00005c: 00000000 00000000 00000000 00000000 ................
ff00006c: 00000000 00000000 00000000 00000000 ................
ff00007c: 00000000 00000000 00000000 00000000 ................
ff00008c: 00000000 00000000 00000000 00000000 ................
ff00009c: 00000000 00000000 00000000 00000000 ................
ff0000ac: 00000000 00000000 00000000 00000000 ................
ff0000bc: 00000000 00000000 00000000 00000000 ................
ff0000cc: 00000000 00000000 00000000 00000000 ................
ff0000dc: 00000000 00000000 00000000 00000000 ................
ff0000ec: 00000000 00000000 00000000 00000000 ................
ff0000fc: 00000000 00000000 00000000 00000000 ................
ff00010c: 00000000 00000000 00000000 00000000 ................
ff00011c: 00000000 00000000 00000000 00000000 ................
ff00012c: 00000000 00000000 00000000 00000000 ................

bodhi Wrote:
-------------------------------------------------------
> > so no difference. still loads of unreadable
> > stuff.. the differnce is that when that fvdw
> > firmware boots it shows up the boot messages
>
> May be that u-boot messed up the normal serial
> console. But not likely, can you interrupt serial
> console when it boots? If yes,
>
>

> ver
> help
> printenv
>

>
>
> > when i try to boot from the stick.. nothing..
>
> See what I asked above.
>
> > me if i can use skype to call you or smthing? .
>
> Sorry, troubleshooting should be done in this
> forum only.

Marvell>> ver
ver

U-Boot 1.1.4 (Jan  7 2013 - 21:15:04) Marvell version: 3.4.16  LaCie 1.3.9 256MB fvdw gpt usbboot vs80


Marvell>> help
help
?       - alias for 'help'
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootext2    dev:boot_part1,boot_part2 addr boot_image linux_dev_name
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bubt    - Burn an image on the Boot Flash.
chpart  - change active partition
cmp     - memory compare
cmpm    - Compare Memory
coninfo - print console devices and information
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
date    - get/set/reset date & time
dclk    - Display the MV device CLKs.
dhcp    - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
echo    - echo args to consoleext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
factory    - reset to factory command
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
iminfo  - print header information for application image
imm[.b, .s, .w, .l]     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
eeprom  - EEPROM sub-system
erase   - erase FLASH memory
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
factory    - reset to factory command
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
iminfo  - print header information for application image
imm[.b, .s, .w, .l]     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
iprobe  - probe to discover valid I2C chip addresses
ir      - reading and changing MV internal register values.
loop    - infinite loop on address range
ls      - list files in a directory (default /)
lump    - Wait for a LUMP
map     - Diasplay address decode windows
md      - memory display
me      - PCI master enable
mm      - memory modify (auto-incrementing)
mp      - map PCI BAR
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
phyRead - Read PCI-E Phy register
pciePhyWrite    - Write PCI-E Phy register
phyRead - Read Phy register
phyWrite        - Write Phy register
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
rcvr    - Satrt recovery process (Distress Beacon with TFTP server)
reset   - Perform RESET of the CPU
resetenv        - Return all environment variable to default.
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
se      - PCI Slave enable
setenv  - set environment variables
sflash  - read, write or erase the external SPI Flash.
sg      - scanning the PHYs status
sp      - Scan PCI bus.
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor version

Marvell>>Marvell>> printenv
printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x300000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bo
otargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; versio
n;
preboot=run if_netconsole start_netconsole
rootfs=/dev/sdb7
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
bootdelay=0
boot_fail=lump
kernel_addr=0x800000
productType_env=ASTON_KW
primaryPart=6
secondaryPart=A
boot_usb=usb start;usbboot 0x800000 0:1;bootm;
resetFlag_env=0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
bootcmd=run disk_disk
boot_disk4=disk ${kernel_addr} 1:${primaryPart}; setenv rootfs /dev/sdb7;
boot_disk3=if disk ${kernel_addr} 0:${primaryPart}; then setenv rootfs /dev/sda7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:${secondaryPart}; then setenv rootfs /dev/sda7; else run boot_disk2; fi
boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_disk3; fi
disk_disk0=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro reset=${resetFlag_env} productType=${pr
oductType_env} GPT fvdw vs80; bootm ${kernel_addr};
uimage=uimage-nwsp2
usbpartboot1=/dev/sdb1
usbpartboot2=/dev/sdb1
disk_disk=run disk_disk0
usb_fvdw1=if usbboot 0x800000 0:1; then setenv bootargs ip=dhcp console=ttyS0,115200 root=${usbpartboot2} ro rootwait; b
ootm; else usb stop; ide reset; run disk_disk0; fi
usb_fvdw=if iminfo 0x800000; then setenv bootargs ip=dhcp console=ttyS0,115200 root=${usbpartboot1} ro rootwait; bootm;
else run usb_fvdw1; fi
ethaddr=00:D0:4B:8B:89:DA
fvdw_boot_usb=ide reset; usb start; ext2load usb 0:1 0x800000 /${uimage}; run usb_fvdw;
ipaddr=10.90.90.252
ncip=10.90.90.254
serverip=10.90.90.254
stdin=nc
stdout=nc

Environment size: 2756/4092 bytes
Marvell>>

===========
bodhi edit: use code tags



Edited 1 time(s). Last edit at 03/12/2024 03:24PM by bodhi.

So i can get to u boot through netconsole using fvdw-sl console.. not through serial which shows lots of non ascii characters...

ff00003c: 00000000 00000000 00000000 00000000 ................

So it is inconclusive. Hopefully kwboot will work when your serial console works.

Quote

So i can get to u boot through netconsole using fvdw-sl console.. not through serial which shows lots of non ascii characters...

Yes. And the envs looks OK for the new set of setenvs to boot Debian.

So the problem must be with the rootfs creation. That's my other question:

Quote

Please post the log what you did when you created the rootfs (especially Step 4). Or if you keep the log of that rootfs creation session, post the entire log.

If you see the IP was assigned, but cannot SSH in, then either it got stuck somewhere during rootfs mounting, or because the wrong DTB was used.

So if you can, recreate the rootfs and post the log of the session, perhaps I will be able to see the mistake. Everything in the rootfs instruction must be followed verbatim (don't substitute any command that you think will be equivalent). Things like being root not sudo, single Ext3 partition,.... are most important.

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

Also there is something in the envs that's worth trying a test for serial console. I will be back and post that tetst.

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

root@debian:~/nwsp2# fdisk -l /dev/sdb
Disk /dev/sdb: 57.72 GiB, 61973987328 bytes, 121042944 sectors
Disk model: USB DISK Pro
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: gpt
Disk identifier: 730078F8-0D72-4B42-82E0-A10C55D25A63

Device     Start       End   Sectors  Size Type
/dev/sdb1   2048 121040895 121038848 57.7G Linux filesystem

root@debian:~/nwsp2# e2label /dev/sdb1
rootfs

root@debian:~/nwsp2# mount /dev/sdb1 usb/
root@debian:~/nwsp2# cd usb
root@debian:~/nwsp2/usb# rm -rf *
root@debian:~/nwsp2/usb# tar xjf /root/Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@debian:~/nwsp2/usb# cd boot
root@debian:~/nwsp2/usb/boot# cp zImage-6.5.7-kirkwood-tld-1 zImage.fdt
root@debian:~/nwsp2/usb/boot# cat dts/kirkwood-ns2.dtb >> zImage.fdt
root@debian:~/nwsp2/usb/boot# mv uImage uImage.orig
root@debian:~/nwsp2/usb/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt  uImage
Image Name:   Linux-6.5.7-kirkwood-tld-1
Created:      Sun Mar 10 21:27:49 2024
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    6234068 Bytes = 6087.96 KiB = 5.95 MiB
Load Address: 00008000
Entry Point:  00008000
root@debian:~/nwsp2/usb/boot# sync
root@debian:~/nwsp2/usb/boot# cd ..
root@debian:~/nwsp2/usb# cd ..
root@debian:~/nwsp2# umount usb
root@debian:~/nwsp2#

i have also tried using kirkwood-rd88f6281-a0.dts. thats what is spelled on the main processor on the board.

root@debian:~/nwsp2# ssh 10.90.90.48
ssh: connect to host 10.90.90.48 port 22: Connection refused

Looks like this u-boot actually causes a real problem with serial console input/output, and would stop a modern kernel from booting.

stderr=serial 
stdin=nc 
stdout=nc

Since you cannot run kwboot, I think there is some small risk in a solution that I have in mind. If it were a pure stock u-boot, then there is no risk.

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

login as: root
root@10.90.90.39's password:
Linux debian 6.5.7-kirkwood-tld-1 #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023 armv5tel

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: Sun Mar 10 23:44:51 2024 from 10.90.90.178
debian
10.90.90.39
LaCie Network Space v2
Linux version 6.5.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023
Debian 12.2
Sun Mar 10 23:45:41 PDT 2024 up 5 minutes
root@debian:~#

got it working. the problem was that current u boot had rootfs in envs. so setenv rootfs blanks it and now it boots from stick.

There is mainline U-Boot support for this device, so you should be able to easily build a modern U-Boot for it. See https://github.com/u-boot/u-boot/blob/master/configs/netspace_v2_defconfig in the U-Boot source for the default config file for building U-Boot for the device.

Ray

Noticed that too. but having some doubt if i cant test it before flashing. Should work and usually works. but... Need to wait few days to get another serial adapter. I thing that my current one is locked at 5v cause it has no selection jumper for the voltage.

-a

> got it working. the problem was that current u
> boot had rootfs in envs. so setenv rootfs blanks
> it and now it boots from stick.

That meant the rootfs label was not stored correctly. Now if you force reset it

e2label /dev/sdb1 rootfs

And put the root=LABEL=rootfs back in the bootags, it will be mounted correctly.

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

It is in bootargs propably hardcoded. , that environment variable messed the bootargs thingy.


rootfs=/dev/sdb7

setting that to nothing it then works.

Tried also with other serial cable, pl2303hxa based chip and the output is garbage again.

https://web.archive.org/web/20150730041425/http://lacie.nas-central.org/wiki/Serial_port_(Network_space_2)

used this image for pinout to connect.

-a

> Tried also with other serial cable, pl2303hxa
> based chip and the output is garbage again.
>

The serial output was set to net console

https://forum.doozan.com/read.php?2,137024,137082#msg-137082

But I don't know this u-boot so I cannot be sure why it was not set to serial at the begining. Normally, u-boot sets stdin/stdout/stderr to serial initially, and then when it sees the envs are set to nc, it will route all input/output to nc.

Here is the test that I have in mind.

Warning: you are on your own risk here when you try this. Since you cannot kwboot, and I don't know what's inside this u-boot that could mess it up permanently.

Connect 2 terminal, one with netconsole, one with serial console.

Power up, interrupt u-boot on netconsole, at the rpompt,

setenv reset_serial 'setenv stderr serial; setenv stdout serial; setenv stdin serial'
run reset_serial

And on the serial console, type <Return> see if anything coming out.

If serial console is still not usable, recycle power. It should boot back to the way it was, since we did not save the envs.

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

gUe_▒▒▒▒▒▒VQ▒▒▒595-57▒-9/-#1▒!▒c5y!#!'5▒!#▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒YO▒▒▒▒҃▒CCCCCCCCCCCCCnZYCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC


c letter comes when i press enter

Quote

rootfs=/dev/sdb7

setting that to nothing it then works.

Check your bootargs in Debian

cat /proc/cmdline

======

OK so it does look like the problem is with serial console.

Just in case, at netconsole prompt, see if serial and net console are listed:

coninfo

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

Marvell>> coninfo
coninfo
List of available devices:
serial   80000003 SIO stderr
nc       80000003 SIO stdin stdout
Marvell>>

warri@debian:~$ cat /proc/cmdline
console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial

>

> warri@debian:~$ cat /proc/cmdline
> console=ttyS0,115200 root=LABEL=rootfs
> rootdelay=10 earlyprintk=serial
> 
>

Yes. That's why it works.

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