RN10400

Hi Tme,

Well then i will try to download the RPM files for fedora 30, 31 and 32 with my win 10 computer and do the same again and see.

But i really think i shall have a better ver of linux. So what is best to run.

Okay thanks again.

AkkJaa...

Hi,

Now i have install Debain 10.6.0 on one of my computer's, a full install with everything and updated the system. it's take me about 3 try to got it installed, but now it's done and the debain is up and going.

Then i have downloaded picocom and minicom in the download dir. but how do i install them.??
i'am not good in linux, i have only work and do programming in dos and windows computer's before. But now i'am so fedup with microsoft products that i think i go over to linux for good.

Well okay, So now i think i can start to find out what is wrong with the netgear RN10400 motherboard.

Many thank's for all help i get here.

AkkJaa...

AkkJaa,

> Then i have downloaded picocom and minicom in the
> download dir. but how do i install them.??

You don't need to download these. You can install them inside Debian.

apt-get update
apt-get install picocom
apt-get install minicom

If you run a different distribution on your laptop/PC, such as Ubuntu, Mint,... these apt-get commands also work.

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

Hi Tme.

Now i have installed Debain 10.6.0 on a new computer and i have download'ed picocom and minicom but how do i install them.? and what treminal or program do i use to install the picocom and minicom.

Thanks-

AkkJaa...

Hi AkkJaa,

What output did you get from the command bodhi suggested?

apt-get install picocom

Regards,
Trond Melen

Hi Bodhi,

I did not see you message. Oki yes but what terminal or program do i use for this commands.:-

apt-get update
apt-get install picocom
apt-get install minicom

Many thanks.

AkkJaa.

Hi Bodhi and Tme,

I just was in here now, i have not try it yet, But enyway i must know what terminal or program i use this commands in. because i'am really rusty when it comes to linux and debain.
But i'am also really fedup / bored when it come the microsoft. so it is time to change all my computers to linux i think.

Okay thanks again.

Regards

AkkJaa...

Hi AkkJaa,

You need a terminal window, for instance "GNOME terminal".

You may try holding down both the 'Ctrl' key and the 'Alt' key and then hit the 'T' key. If no terminal window pops up, search the menus on your desktop for a possibility to choose 'terminal' of 'command line'.

Regards,
Trond Melen

As a reminder:

- On Windows box, use putty for serial console.
- On Mac box, use screen for serial console.
- On any Linux box, use minicom or picocom for serial console.

On Linux, if running distro such as Debian, Mint, Ubuntu, Arch , or any other with a GUI desktop, you can install minicom/picocom using GUI.

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

Hi Bodhi,

i open the terminal by hold down Ctrl and Alt key and then press T
Then come up a terminal and i try the commands.:-
apt-get update
apt-get install picocom
apt-get install minicom

Then this come up.:-
apt-get update
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)
charles1@Debian:~$
charles1@Debian:~$ apt-get install picocom
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
charles1@Debian:~$
charles1@Debian:~$ apt-get install minicom
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
charles1@Debian:~$

Yes so then i'am stuck again.
Eny thing i can do to get this installed.?

By the way marry christmas and a happy new year to everybody here. and thank you all.

Regards

AkkJaa...

Hi AkkJaa,

you have to be the root user to install software. That is the way most linux systems work and provides an additional layer of safety. You either need to change to the root user or install the software using sudo. Have a look at the following website:

https://www.wikihow.com/Install-Software-in-Debian-Linux

Koen

Hi Bodhi.
Now i think i have find out what was wrong. If you look at photo RN102 i got from the link from forum here that is a other motherboard then i have and the serial must have be diffrent because now i have change the pin's and connected it this way.:-
GND to GND on motherboard.
RXD to TX on motherboard.
TXD to RX on motherboard.

Now the motherboard start up when the USB cable is conneced. Before it did not.
And now i see the blue light on the CP2102 pin RXD is blinking when i turn on the motherboard.

On the CP2102 module when the USB cable is connected are.:-
The RED light on, on GND pin
The BLUE light on, on RXD pin.

When i turn on the RN10400 motherboard.
The front of the motherboard is blinking as before all the time.
And on the CP2102 module.
RED light on GND no change still light.
BLUE light on RXD is blinking fast and slow for about 2-3 sec. then stop, then start blinking again for about 2-3 sec. then stop again. and go off. no more light in the BLUE RXD pin when the motherboard are on.

When i power off then the BLUE light on again together with the RED light who is on all the time the USB is connected.

So there must be different from the RN102 and the RN10400. because it look like everything now is okay with the connection between the CP2102 and the RN10400 motherboard. And the blinking in the blue light on the RXD is signal/data on the boot up from the motherboard.

So i now need to get the picocom or the minicom up and going. i have uploaded 3 photos of what i have done now. But now i can't get the picocom or the minicom installed.

Ok, what do you think.

Best Regards.
AkkJaa...

Hi Bodhi,

Here is the reading i have from the Picocom terminal. From the RN10400. come under here.:-

BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0001
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:56:14) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-104 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9f514
       BSS:		0x1ffef8a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xf12c)	128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   egiga0, egiga1 [PRIME]
Power On!

FDT loaded successfully
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Active port:	0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found

** Invalid boot device **

** Invalid boot device **

NAND read: device 0 offset 0xd4000, size 0x6000
 24576 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>

Yes then you have it, Can you find something wrong with it.????

Best Regards.

AkkJaa...

========
Moderator edit: please use code tags (formatted code button) to post log.



Edited 3 time(s). Last edit at 12/29/2020 07:00PM by AkkJaa.

AkkJaa,

Quote

root@Debian:~# picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0

Just curious (unrelated to the problem) what type box is this host "Debian" ?

Quote

scanning bus for storage devices... 0 Storage Device(s) found

Meaning there is no USB drive attached to this box. It there was, then it was not detected by u-boot.

Quote

NAND read: device 0 offset 0xd4000, size 0x6000
24576 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!

This means either:
- the kernel stored at that location on NAND is not good.
- or the envs to boot this box has some problem so it did not execute the correct commands.

So interrupt u-boot at cound down

Quote

Hit any key to stop autoboot: 0

and get the listing of the envs

printenv

Please post the serial console log up until this point.

=====

If the envs look sane, then you can proceed to use the RN012 envs set up to boot Debian rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 on USB.

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

Hello Bodhi,

Host debain,? I have build a computer i put up some photos so you can see. This is a old computer i build for a long time ago. But it is ok now, and for run debain.
It is a Asus motherboard model.: P5 VDI-X. with Intel pentium 4. on 3,4 Ghz, 775 Land. with 2 Gb. ram.

I have build and repair different computer's for customer's for about 30 years, go back to the old ms dos 3,10 - 3,30 - 4,00 - 5,00 - and 6,22 then windows driver ver. then 3,11 for workgroups and NT yes and so on. And also run a Database's like wild Cat, PC Board with USRobotic modems. and done some programming. Well.

But Never be in the Linux world before now. And and i like it so now i think i turn over to Linux world, Coz i can't say that i am so very happy with Win 10 and the win products for the moment.

Yes that was a bit of me. Now i will try what you have write up to me here and post it on to you later on.

But again many thanks for all help i get here. because i need it when it come to Linux. Ohhh.. well in the computer world you are old in the game iven not to be updated for some mounts, it's impossible to be updated on all that is going on in the computer world. Coz it come up so many new things every day that no one can follow on everything or every topic.

Okay thanks again.

Best Regards.

AkkJaa...

Hi Bodhi.

I don't understand what hi and you mean about this.:-

========
Moderator edit: please use code tags (formatted code button) to post log.

Please post the serial console log up until this point.

=====

There is no this point.: ===== ? in the log i have put up.

Thanks Again.

AkkJaa...

AkkJaa,

> Moderator edit: please use code tags (formatted
> code button) to post log.

The boot log you post you posted was not inside code tags (you can use the "Formatted Code" button on the uper right of the text box to put them in code tags). Log are hard to read without the format. Example:

This text is inside code tags

> Please post the serial console log up until this point.

Meaning: post the entire serial console log until the last output on your terminal.

> I have build and repair different computer's for customer's for about 30 years, go back to the old ms dos 3,10

The good old days :)

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



Edited 1 time(s). Last edit at 12/30/2020 02:18AM by bodhi.

Hi Bodhi,

Ok, understand. Yeah.. the good old days. But gone for a long time ago.. Well, i have look at the link you put up before and i have downloaded 2 files there. now i will try to read the envs and put it up here later on.

Thank you again and happy new year to you and the rest of the people in here.

Best Regards.

AkkJaa....

Ps.: i did that with the output from the RN10400 yesterday, i edit the the message 
and cut out the output from the RN10400 then i push the formatted code bottom and 
copy the output in there.

Like this over here.



Edited 2 time(s). Last edit at 12/30/2020 02:30PM by AkkJaa.

Hi Bodhi,

Is there anti virus program for Debain.?

Best Regards.

AkkJaa...

Hi Bodhi,

Here is what i have read from the RN10400 Motherboard.

Marvell>> printenv
AC_Power_fail_detect=open
CASset=min
HW_version=MVT
MALLOC_len=5
Manufacturer=NETGEAR
Product=ReadyNAS 104
SKUNum=RN104
SerialNum=3EPE51EM006E2
Startup=Normal
UUID=8ad06a7e-97fc-11e4-9cf7-e8fcafe534ca
Version=V1.0
autoload=no
bootargs=console=ttyS0,115200
bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=usb start;fatload usb 0:1 0x2000000 /uImage-recovery;fatload usb 0:1 0x3000000 /initrd-recovery.gz;nand read 0x1000000 0xD4000 0x6000; bootm 0x2000000 0x3000000 0x1000000
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_ubi=ubi part ubifs; ubifsmount rootfs; ubifsload 0x2000000 kernel; ubifsload 0x3000000 initrd.gz; bootm 0x2000000 0x3000000 0x1000000
bootdelay=0
cacheShare=no
console=console=ttyS0,115200
disL2Cache=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=yes
enaExtDisk=no
enaFPU=no
enaMonExt=no
enaWrAllo=no
envver=3
eth1addr=E8:FC:AF:E5:34:CB
eth1mtu=1500
ethact=egiga1
ethaddr=E8:FC:AF:E5:34:CA
ethmtu=1500
ethprime=egiga1
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-370-db.dtb
image_name=uImage
initrd_name=uInitrd
load_addr=0x02000000
loadaddr=0x02000000
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)
mvNetConfig=mv_net_config=1,(00:50:43:11:11:11,0:1:2:3:4),mtu=1500
mv_pon_addr=00:50:43:00:00:02
nandEcc=1bit
netbsd_en=no
netretry=no
pcieTune=no
pexMode=rc
pxe_files_load=:default.arm-armada370-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
rcvrip=169.254.100.100
sata_delay_reset=0
sata_dma_mode=yes
setL2CacheWT=no
standalone=fsload $load_addr $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm $load_addr;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 2349/131068 bytes
Marvell>>

Yes, Then i have write out what is there i think. can you see something here.

Many thanks.

Best Regards.

AkkJaa...

Hi Bodhi,
Here i put up everything of the read out from the RN10400 motherboard.

Terminal ready

BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0001
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:56:14) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-104 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB
Port0: phyAddr=0x0, Not Marvell PHY id1 ffff id2 ffff
PHY error - shutdown port0

Map:   Code:		0x1feef000:0x1ff9f514
       BSS:		0x1ffef8a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xf12c)	128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   egiga1 [PRIME]
Warning: egiga1 MAC addresses don't match:
Address in SROM is         e8:fc:af:e5:34:cb
Address in environment is  e8:fc:af:e5:34:ca

Power On!

FDT loaded successfully
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Active port:	0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found

** Invalid boot device **

** Invalid boot device **

NAND read: device 0 offset 0xd4000, size 0x6000
 24576 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>> printenv
AC_Power_fail_detect=open
CASset=min
HW_version=MVT
MALLOC_len=5
Manufacturer=NETGEAR
Product=ReadyNAS 104
SKUNum=RN104
SerialNum=3EPE51EM006E2
Startup=Normal
UUID=8ad06a7e-97fc-11e4-9cf7-e8fcafe534ca
Version=V1.0
autoload=no
bootargs=console=ttyS0,115200
bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=usb start;fatload usb 0:1 0x2000000 /uImage-recovery;fatload usb 0:1 0x3000000 /initrd-recovery.gz;nand read 0x1000000 0xD4000 0x6000; bootm 0x2000000 0x3000000 0x1000000
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_ubi=ubi part ubifs; ubifsmount rootfs; ubifsload 0x2000000 kernel; ubifsload 0x3000000 initrd.gz; bootm 0x2000000 0x3000000 0x1000000
bootdelay=0
cacheShare=no
console=console=ttyS0,115200
disL2Cache=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=yes
enaExtDisk=no
enaFPU=no
enaMonExt=no
enaWrAllo=no
envver=3
eth1addr=E8:FC:AF:E5:34:CB
eth1mtu=1500
ethact=egiga1
ethaddr=E8:FC:AF:E5:34:CA
ethmtu=1500
ethprime=egiga1
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-370-db.dtb
image_name=uImage
initrd_name=uInitrd
load_addr=0x02000000
loadaddr=0x02000000
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)
mvNetConfig=mv_net_config=1,(00:50:43:11:11:11,0:1:2:3:4),mtu=1500
mv_pon_addr=00:50:43:00:00:02
nandEcc=1bit
netbsd_en=no
netretry=no
pcieTune=no
pexMode=rc
pxe_files_load=:default.arm-armada370-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
rcvrip=169.254.100.100
sata_delay_reset=0
sata_dma_mode=yes
setL2CacheWT=no
standalone=fsload $load_addr $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm $load_addr;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 2349/131068 bytes
Marvell>>

Ok yes then i think i have got all now.

Thanks again.

Best Regards.

AkkJaa...

Hi AkkJaa,

Quote

Is there anti virus program for Debain?

If you are worried about viruses, Debian is your savior! It's an anti virus program by itself.

This article targets Debian and other Linux distributions on desktops, but most of it applies to you NAS box as well.

Regards,
Trond Melen

AkkJaa,

> Hit any key to stop autoboot: 0
> (Re)start USB...
> USB: Active port: 0
> Register 10011 NbrPorts 1
> USB EHCI 1.00
> scanning bus for devices... 1 USB Device(s) found
> scanning bus for storage devices... 0
> Storage Device(s) found

Looks like you have no USB drive attached to the box. Did you prepare the rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 from the release thread?

https://forum.doozan.com/read.php?2,32146

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

Hi Bodhi,

Yes true no USB in the motherboard.
Now i have downloaded the rootfs. debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 so now i will try to have it in a 16Gb USB menory stick. I have downloaded it to my win10. computer now. but move it to the debian 10 computer and try to install it on the usb. then the netgear box.
But do i need to have the HD's installed in the box.? Because now i only run the motherboard alone to get it up and going before i put it together again.

Ok, Thanks.

Regards.

AkkJaa...



Edited 1 time(s). Last edit at 01/24/2021 04:30PM by AkkJaa.

AkkJaa,

Actually, to keep things simple, don't put the HDD in the box yet, until you have booted into Debian on USB. After satisfied that it runs normally, put the case back on and insert the HDD.

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

Hi Bodhi,
Ok, i understand, i only work with the motherboard alone no HDD. I have done this now for make the USB but i can't change label name on it.

mkfs.ext3 /dev/sdc1
mke2fs 1.44.5 (15-Dec-2018)
/dev/sdc1 contains a vfat file system labelled 'rootfs'
Proceed anyway? (y,N) y
Creating filesystem with 3783968 4k blocks and 946560 inodes
Filesystem UUID: ba6705dc-a194-4877-b1e1-675ad7b7951d
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

I only come so far.
Then i see this on the net. GParted tool. And i try'ed to install it see under here.

apt-get install gparted
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-4.19.0-11-686-pae
Use 'apt autoremove' to remove it.
Suggested packages:
  xfsprogs reiserfsprogs reiser4progs jfsutils mtools kpartx dmraid gpart
  udftools
The following NEW packages will be installed:
  gparted
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,029 kB of archives.
After this operation, 7,644 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main i386 gparted i386 0.32.0-2 [2,029 kB]
Fetched 2,029 kB in 0s (4,399 kB/s)
Selecting previously unselected package gparted.
(Reading database ... 457080 files and directories currently installed.)
Preparing to unpack .../gparted_0.32.0-2_i386.deb ...
Unpacking gparted (0.32.0-2) ...
Setting up gparted (0.32.0-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.31.4-3) ...
Processing triggers for man-db (2.8.5-2) ...

Or maybe i make it now this time. You can see. Can i use this program to make the Ext3 with the label name rootfs

Yes so then you have it so far.

Many thanks

Best Regards.

AkkJaa...

AkkJaa,


Use fdisk to wipe the USB drive, and then create the new partition. Don't use gparted. The GUI sometime has its default properties applied, not what you thought it should be.

fdisk /dev/sdc

and wipe with o, create new partition with n, and take defaults for the rest.

o
n

and then format it. The command should be:

mkfs.ext3 -L rootfs /dev/sdc1

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

Bodhi,

Ok then i use fdisk, and not GParted, Yes i understand. it's best it is so clean as posible without other data only what need'ed and what is usefull. Very important.

Thanks again.

Regards.

AkkJaa...

Hi Bodhi,

After wipe the USB drive on 16 Gb, i have done this.:-

mkfs.ext3 -L rootfs /dev/sdc1
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 3783968 4k blocks and 946560 inodes
Filesystem UUID: 42bea2a0-0c84-4669-b8f4-23127aee6389
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Then i go in the terminal and write.:-

cd /media/sdb1

But there is no dir by name sdb1, So i go to the dir media and make the dir sdb1, and copy the Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 file into the dir sdb1
Then i go in the terminal and write.:-

cd /media/sdb1
tar -xjf Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2

And all extract into the /media/sdb1 dir. But that shall ofcause be on the USB drive and not on the HD dir. Then i copy the file Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 into the USB drive. and there all stop, because how i extract the file in the USB drive.???

Else, i have just take a read out from the motherboard with the USB drive in the Front USB on the motherboard and here is the read out of that.:-

Terminal ready

BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0001
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:56:14) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-104 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB
Port0: phyAddr=0x0, Not Marvell PHY id1 ffff id2 ffff
PHY error - shutdown port0

Map:   Code:		0x1feef000:0x1ff9f514
       BSS:		0x1ffef8a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xf12c)	128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   egiga1 [PRIME]
Warning: egiga1 MAC addresses don't match:
Address in SROM is         e8:fc:af:e5:34:cb
Address in environment is  e8:fc:af:e5:34:ca

Power On!

FDT loaded successfully
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Active port:	0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading /uImage-recovery

** Unable to read "/uImage-recovery" from usb 0:1 **
reading /initrd-recovery.gz

** Unable to read "/initrd-recovery.gz" from usb 0:1 **

NAND read: device 0 offset 0xd4000, size 0x6000
 24576 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>> printenv
AC_Power_fail_detect=open
CASset=min
HW_version=MVT
MALLOC_len=5
Manufacturer=NETGEAR
Product=ReadyNAS 104
SKUNum=RN104
SerialNum=3EPE51EM006E2
Startup=Normal
UUID=8ad06a7e-97fc-11e4-9cf7-e8fcafe534ca
Version=V1.0
autoload=no
bootargs=console=ttyS0,115200
bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=usb start;fatload usb 0:1 0x2000000 /uImage-recovery;fatload usb 0:1 0x3000000 /initrd-recovery.gz;nand read 0x1000000 0xD4000 0x6000; bootm 0x2000000 0x3000000 0x1000000
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_ubi=ubi part ubifs; ubifsmount rootfs; ubifsload 0x2000000 kernel; ubifsload 0x3000000 initrd.gz; bootm 0x2000000 0x3000000 0x1000000
bootdelay=0
cacheShare=no
console=console=ttyS0,115200
disL2Cache=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=yes
enaExtDisk=no
enaFPU=no
enaMonExt=no
enaWrAllo=no
envver=3
eth1addr=E8:FC:AF:E5:34:CB
eth1mtu=1500
ethact=egiga1
ethaddr=E8:FC:AF:E5:34:CA
ethmtu=1500
ethprime=egiga1
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-370-db.dtb
image_name=uImage
initrd_name=uInitrd
load_addr=0x02000000
loadaddr=0x02000000
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)
mvNetConfig=mv_net_config=1,(00:50:43:11:11:11,0:1:2:3:4),mtu=1500
mv_pon_addr=00:50:43:00:00:02
nandEcc=1bit
netbsd_en=no
netretry=no
pcieTune=no
pexMode=rc
pxe_files_load=:default.arm-armada370-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
rcvrip=169.254.100.100
sata_delay_reset=0
sata_dma_mode=yes
setL2CacheWT=no
standalone=fsload $load_addr $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm $load_addr;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 2349/131068 bytes
Marvell>>

Ok then you have it. And thanks alot for all help. By the way yesterday i delete the win 10 from a other computer because this is better and much more intresting. Remind me back long time ago when a was doing some programming, Yeah.. everybody need some brain exercises...

Regards.

AkkJaa...



Edited 1 time(s). Last edit at 01/28/2021 03:25AM by AkkJaa.

AkkJaa,

> Then i go in the terminal and write.:-
>

> cd /media/sdb1
>

> But there is no dir by name sdb1, So i go to the
> dir media and make the dir sdb1, and copy the
> Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 file
> into the dir sdb1

After you format the partition, you need to mount /dev/sdb1

mkdir /media/sdb1
mount /dev/sdb1 /media/sdb1

And then,

cd /media/sdb1
tar -xjf Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2

When it is done,

sync

and umount

cd /
umount /media/sdb1

ANd now you can remove it and bring to the RN10400.

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