Welcome! Log In Create A New Profile

Advanced

Help: kernel build vs uBoot requirements

Posted by fcopurico 
Help: kernel build vs uBoot requirements
February 18, 2022 07:40PM
I am new here. I own a GoflexHome.
I follow your wiki and had success in general. With your latest files I can boot Debian from USB and HDD. So your multiboot environment do work nicely. Even when most of the stuff in the enviroment are strange to me.

I have a project in mind where I need to build my owm kernel and OS. The OS is not an issue. But I have trouble with the kernel. It seems to me that uBoot rejects the initrd.

Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.19.0-18-marvell
Created: 2022-02-17 20:06:22 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 15665801 Bytes = 14.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

To understand the process, I end up ignoring the fact I will build my kernel.
Instead I am using Debian provided kernel=> image-4.19.0-18-marvell.deb

Continue.
Re: Help: kernel build vs uBoot requirements
February 18, 2022 07:41PM
So I went to run in an more manual way:
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.19.0-18-marvell -d vmlinuz-4.19.0-18-marvell uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs--4.19.0-18-marvell -d initrd.img--4.19.0-18-marvell uInitrd

I stop uBoot and used
usb reset
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x1100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
run usb_bootcmd

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

ID (hex)        NAME
ffffffff        Generic DT based system
ffffffff        Marvell Kirkwood (Flattened Device Tree)
0000054e        Marvell Orion-2 Development Board
000005e4        Marvell Orion-NAS Reference Design
00000631        Buffalo Linkstation Pro/Live
000005e5        Buffalo/Revogear Kurobox Pro
00000630        Buffalo Terastation Pro II/Live
000007d5        Buffalo Linkstation LS-HGL
0000061d        QNAP TS-109/TS-209
00000641        QNAP TS-409
00000661        Linksys WRT350N v2
00000674        Technologic Systems TS-78xx SBC
0000069d        HP Media Vault mv2120
00000926        LaCie 2Big Network
00000709        Netgear WNR854T
00000714        Marvell Orion-VoIP GE Reference Design
0000071a        Marvell Orion-VoIP FXO Reference Design
00000766        Marvell Orion-1-90 AP GE Reference Design
ffffffff        Marvell Orion5x (Flattened Device Tree)

Please check your kernel config and/or bootloader.

continue
Re: Help: kernel build vs uBoot requirements
February 18, 2022 07:45PM
So this time I used the alternate method
cd /boot
cp -a vmlinuz-4.19.0-18-marvell zImage.fdt
cat dts/kirkwood-goflexhome.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.19.0-18-marvell -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs--4.19.0-18-marvell -d initrd.img--4.19.0-18-marvell uInitrd

And this time I can boot from USB Debian using
I stop uBoot and used
usb reset
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x1100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
run usb_bootcmd

Conclusion: There is nothing wrong with Debian's provided stock marvell kernel. It can boot.

But I can not seems to make it boot with your original enviroment. I will get the

Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid

continue
Re: Help: kernel build vs uBoot requirements
February 18, 2022 08:00PM
here is the original env
root@OpenWrt:~# fw_printenv
arcNumber=2097
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_lede=run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3
bootdelay=10
bootdev=usb
device=0:1
device_type=mmc
devices=usb ide mmc
disk_number=3
disks=0 1 2 3
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.106
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
partition=nand0,0
preboot=run if_netconsole start_netconsole
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.104
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_lede=setenv bootargs console=ttyS0,115200 $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_loaded=0
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
usb_ready_retry=15
root@OpenWrt:~#

Sorry for the length of the posts. I wanted to provide all info in hand.
What I want is to keep your nice boot sequence if any of then is not available or fail: USB to HDD to NAND. But running my own kernel/OS.

Where should a I read more on uBoot that can explain this past long enviroment you use?
What is the importace of
arcNumber=2097
machid=0x831

when I thnink Goflex use:
arcNumber=3338
machid=0x831
** Taken from https://forum.doozan.com/read.php?3,129944,129944#msg-129944

witch kind of match info from https://forum.doozan.com/read.php?3,12381

for GoFlex Home: 

fw_setenv arcNumber 3338
fw_setenv machid

I know there is comnets like
"Note that setting arcNumber and machid are not necessary if you are booting with FDT kernel 3.17+ in the latest kernel and rootfs thread. But it's required for non-FDT kernel. "

"In the special case when you are booting with a non-FDT kernel, or if you have appended the DTB to uImage. Remove the DTB file env. If not sure please post question before continuing.

fw_setenv dtb_file"

I wonder is failure has something to do with those. Thanks in advance.

Note: I edited the original enviroment. This is mine, Previous was from a friend. Not of important only IP changes and bootarg. But changed to set the record clear.



Edited 1 time(s). Last edit at 02/20/2022 12:53AM by fcopurico.
Re: Help: kernel build vs uBoot requirements
February 18, 2022 10:04PM
fcopurico,


> What I want is to keep your nice boot sequence if
> any of then is not available or fail: USB to HDD
> to NAND. But running my own kernel/OS.

That's how you should approach it. The mainline kernel does not have the DTB appended to it. So it is correct that you appended it to uImage in your rootfs.


> What is the importace of
> arcNumber=2097
> machid=0x831

These are no longer relevant. I've updated the u-boot installation instruction to inidicate that they are deprecated.

> I know there is comnets like
> "Note that setting arcNumber and machid are not
> necessary if you are booting with FDT kernel 3.17+
> in the latest kernel and rootfs thread. But it's
> required for non-FDT kernel. "

Yes. The mainline Debian kernel is FDT. It's been FDT for a long time. So ignore that statement.

This is the inportant info:
fw_setenv dtb_file

In the u-boot evns script, dtb_file points to where the DTB file is located in the rootfs. If this env is not defined, then the DTB is embeded inside uImage.

So reboot, interrupt serial console, and use the default sequence. But also adjust the envs:

setenv dtb_file
setenv load_initrd_addr 0x2100000
printenv
and then

boot

Please post the entire serial console log here. Even if it is successfully booted into Debian, it's good to have a point of reference for others to see when they look for how to boot mainline kernel.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Help: kernel build vs uBoot requirements
February 19, 2022 02:59PM
Can you explain or correct me.

fw_setenv dtb_file
I guess this in fact clear or delete "dtb_file" variable?
Why it is important? Is the same file any way.
Well one I did attached at the end of new uImage.
The original option I guess points to \boot\dts\kirkwood-goflexhome.dtb
But both are the same file kirkwood-goflexhome.dtb?

setenv load_initrd_addr 0x2100000
Interesting. I should learn here.
After original installation the environments shows
load_initrd_addr=0x1100000

The thread I follow show manual instruction
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'

So I updated my manual to
setenv load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'

To be honest both seems to work. But can you explain what is the correct value. I am under the assumption that this are RAM address we some how pick to be use to temporary load. I guess any number should work if we do not overwrite previous important loads. But I got no knowledge of what address has been used. So what I did was to used what I thought was working ( 0x1100000 ) Can you help understand or correct me?

So reboot, interrupt serial console, and use the default sequence. But also adjust the envs:
I guess by "use the default sequence" you mean using your original full environment.

From what I saw, I will expect: If I stop serial console and manually boot then it will boot.
Problem/question will be if mainland kernel will auto boot with original environment.

I will try your suggestion and post all I can.

I was referred to this forum after seem a friend works his. By the way this forum have interesting posts.
Thank for your time and effort.
Re: Help: kernel build vs uBoot requirements
February 19, 2022 05:02PM
fcopurico,

>
fw_setenv dtb_file
> I guess this in fact clear or delete "dtb_file"
> variable?
> Why it is important? Is the same file any way.
> Well one I did attached at the end of new uImage.

> The original option I guess points to
> \boot\dts\kirkwood-goflexhome.dtb
> But both are the same file
> kirkwood-goflexhome.dtb?
>

The normal way to boot a FDT kernel is loading the DTB separately (if u-boot has FDT capability). Otherwise, if u-boot is old,and does not have FDT capability, then we must append the DTB to uImage (My released u-boot is new, and supports FDT).

So if you append the DTB to uImage, then the DTB must not be also loaded. Hence, clearing the env dtb_file makes u-boot fail to load DTB, and the logic will go to the path where it will boot without separate DTB.

So etither booting method is fine, will work. You just need to use the original uImage (after you install mainline kernel), if you want to keep loading separate DTB.

The bottom line is that that DTB cannot be both loaded separately and also embedded inside uImage. This will cause a conflict.


>
setenv load_initrd_addr 0x2100000
> Interesting. I should learn here.

Currently 0x1100000 should work, because the uInitrd is small enough to fit in the RAM region for it (11 MB). But for future u-boot release, I will change it to 0x2100000, so that we don't have to worry about the uInitrd growing larger than 11MB. These numbers were picked many years ago, when the kernel was quite small.

load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000

> I guess by "use the default sequence" you mean
> using your original full environment.

Yes.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Help: kernel build vs uBoot requirements
February 20, 2022 01:05AM
I try to read a little before I posted. But to be honest what you ask was so simple that I did not need to read.

I started by restoring my original environment. So I
1) 1rst deleted new items I added
setenv usb_boot
setenv usb_bootcmd
setenv usb_load_uimage
setenv usb_load_uinitrd
setenv usb_set_bootargs

2) Restore some I did change
setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede'
printenv
saveenv

3) At this point my printenv is just as I started. Look at my 4th post if you want to know.
This means that I can boot from NAND Openwrt or original bodhi
Latest released kernel: linux-5.16.5-kirkwood-tld-1-bodhi.tar.bz2 (07 Feb 2021)
Latest released rootfs: Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (26 Sept 2021)

But NOT image-4.19.0-18-marvell.deb kernel files.

3) Now added what you just ask me
setenv dtb_file
setenv load_initrd_addr 0x2100000
printenv
saveenv
boot

And just as you just said my new USB with a simple rootfs and debian_armel_marvell kernel did work. Also OpenWrt on Nand did launch when USB not present. Very nice.

As requested here are my logs



Edited 1 time(s). Last edit at 02/20/2022 01:37AM by fcopurico.
Re: Help: kernel build vs uBoot requirements
February 20, 2022 01:15AM
This is the log running my own Debian Buster with Kernel 4.19.0-18-marvell from USB. Yes the two simple enviroment corrections did the trick. Now it is booting with original bodhi environments. It can still multiboot USB and NAND. I have not tested HDD but It should not be a problem.
GoFlexHome> setenv dtb_file
GoFlexHome> setenv load_initrd_addr 0x2100000
GoFlexHome> saveenv
GoFlexHome> boot
Initializing devices...
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: ide_preinit failed
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
415 bytes read in 1300 ms (0 Bytes/s)
... envs loaded
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 446 ms (0 Bytes/s)
Found bootable drive on usb 0
2069161 bytes read in 517 ms (3.8 MiB/s)
loading uInitrd ...
15665865 bytes read in 916 ms (16.3 MiB/s)
loading DTB ...
** No boot file defined **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.19.0-18-marvell
   Created:      2022-02-17  23:55:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2069097 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02100000 ...
   Image Name:   initramfs-4.19.0-18-marvell
   Created:      2022-02-17  20:06:22 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    15665801 Bytes = 14.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   Loading Ramdisk to 06c1c000, end 07b0ca89 ... OK
Using machid 0x831 from environment

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.0-18-marvell (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 Debian 4.19.208-1 (2021-09-29)
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Seagate GoFlex Home
[    0.000000] Memory policy: Data cache writeback
[    0.000000] random: get_random_bytes called from start_kernel+0x78/0x4a8 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 108476K/131072K available (3987K kernel code, 342K rwdata, 1040K rodata, 316K init, 220K bss, 22596K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (3989 kB)
[    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   ( 316 kB)
[    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 343 kB)
[    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 221 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] ftrace: allocating 18981 entries in 38 pages
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000041] Switching to timer-based delay loop, resolution 5ns
[    0.000138] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.000161] pid_max: default: 32768 minimum: 301
[    0.000419] Security Framework initialized
[    0.000439] Yama: disabled by default; enable with sysctl kernel.yama.*
[    0.000560] AppArmor: AppArmor initialized
[    0.000689] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000712] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001684] CPU: Testing write buffer coherency: ok
[    0.002731] Setting up static identity map for 0x8200 - 0x823c
[    0.002971] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.004838] devtmpfs: initialized
[    0.008480] VFP support v0.3: not present
[    0.008651] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.008677] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.008961] pinctrl core: initialized pinctrl subsystem
[    0.010108] NET: Registered protocol family 16
[    0.010526] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.011158] audit: initializing netlink subsys (disabled)
[    0.011976] cpuidle: using governor ladder
[    0.011992] cpuidle: using governor menu
[    0.012387] Feroceon L2: Enabling L2
[    0.012430] Feroceon L2: Cache support initialised.
[    0.012674] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.016098] audit: type=2000 audit(0.008:1): state=initialized audit_enabled=0 res=1
[    0.016266] No ATAGs?
[    0.020685] clocksource: Switched to clocksource orion_clocksource
[    0.043471] VFS: Disk quotas dquot_6.6.0
[    0.043548] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.044045] AppArmor: AppArmor Filesystem Enabled
[    0.045226] NET: Registered protocol family 2
[    0.045364] IP idents hash table entries: 2048 (order: 2, 16384 bytes)
[    0.045922] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[    0.045950] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.045971] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.045991] TCP: Hash tables configured (established 1024 bind 1024)
[    0.046087] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.046112] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.046307] NET: Registered protocol family 1
[    0.046577] Unpacking initramfs...
[    1.020715] random: fast init done
[    1.383750] Freeing initrd memory: 15300K
[    1.384616] Initialise system trusted keyrings
[    1.384721] Key type blacklist registered
[    1.384896] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    1.389600] zbud: loaded
[    1.391336] Key type asymmetric registered
[    1.391349] Asymmetric key parser 'x509' registered
[    1.391400] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    1.391554] io scheduler noop registered
[    1.391797] io scheduler cfq registered (default)
[    1.393294] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    1.394983] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.425594] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.425777] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.453576] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.453931] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.454884] console [ttyS0] disabled
[    1.454948] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 12500000) is a 16550A
[    1.978219] console [ttyS0] enabled
[    1.982439] libphy: Fixed MDIO Bus: probed
[    1.986581] i2c /dev entries driver
[    1.990854] ledtrig-cpu: registered to indicate activity on CPUs
[    1.997829] registered taskstats version 1
[    2.001974] Loading compiled-in X.509 certificates 
[    2.034031] Loaded X.509 cert 'Debian Secure Boot CA: ########################################'
[    2.068085] Loaded X.509 cert 'Debian Secure Boot Signer 2021 - linux: ########################################'
[    2.078442] AppArmor: AppArmor sha1 policy hashing enabled
[    2.085585] hctosys: unable to open rtc device (rtc0)
[    2.093417] Freeing unused kernel memory: 316K
[    2.097898] This architecture does not have kernel memory protection.
[    2.104380] Run /init as init process
Loading, please wait...
Starting version 241
[    2.512865] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    2.571569] libphy: orion_mdio_bus: probed
[    2.577166] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.629733] usbcore: registered new interface driver usbfs
[    2.638160] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[    2.658936] SCSI subsystem initialized
[    2.685353] usbcore: registered new interface driver hub
[    2.720296] usbcore: registered new device driver usb
[    2.752452] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.764228] sata_mv f1080000.sata: slots 32 ports 1
[    2.797800] ehci-orion: EHCI orion driver
[    2.804476] scsi host0: sata_mv
[    2.812166] ata1: SATA max UDMA/133 irq 32
[    2.821246] orion-ehci f1050000.ehci: EHCI Host Controller
[    2.831801] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    2.839705] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    2.860706] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    2.866972] usb usb1: New USB device found, idVendor=1234, idProduct=0002, bcdDevice= 4.19
[    2.875300] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.882569] usb usb1: Product: EHCI Host Controller
[    2.887485] usb usb1: Manufacturer: Linux 4.19.0-18-marvell ehci_hcd
[    2.893885] usb usb1: SerialNumber: f1050000.ehci
[    2.900536] hub 1-0:1.0: USB hub found
[    2.904379] hub 1-0:1.0: 1 port detected
[    3.131040] ata1: SATA link down (SStatus 0 SControl F300)
Begin: Loading essential drivers ... done.
[    3.160720] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    3.322834] usb 1-1: New USB device found, idVendor=0123, idProduct=4567, bcdDevice= 1.10
[    3.331073] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.338270] usb 1-1: Product: Memory
[    3.342311] usb 1-1: Manufacturer: DISK
[    3.346444] usb 1-1: SerialNumber: ######################
[    3.365367] usb-storage 1-1:1.0: USB Mass Storage device detected
[    3.371900] scsi host1: usb-storage 1-1:1.0
[    3.378881] usbcore: registered new interface driver usb-storage
[    3.389222] usbcore: registered new interface driver uas
[    3.497307] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 52:3b:20:9c:11:51
[    4.385797] scsi 1:0:0:0: Direct-Access     DISK  Memory      PMAP PQ: 0 ANSI: 0 CCS
[    4.405647] sd 1:0:0:0: [sda] 62750720 512-byte logical blocks: (32.2 GB/30.0 GiB)
[    4.414988] sd 1:0:0:0: [sda] Write Protect is off
[    4.420227] sd 1:0:0:0: [sda] No Caching mode page found
[    4.425589] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    5.181476]  sda: sda1
[    5.187232] sd 1:0:0:0: [sda] Attached SCSI removable disk
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 
rootfs: clean, 14723/981120 files, 269976/3921664 blocks
done.
[   13.917832] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.93 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting hotplug events dispatcher: systemd-udevd. ok 
[....] Synthesizing the initial hotplug events (subsystems)...[   15.840821] random: crng init done
done.
[....] Synthesizing the initial hotplug events (devices)...[   16.336955] systemd-udevd[310]: Using default interface naming scheme 'v240'.
[   16.449214] systemd-udevd[310]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   16.524014] orion_wdt: Initial timeout 21 sec
[   16.595787] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
[   16.602223] nand: Toshiba NAND 256MiB 3,3V 8-bit
[   16.606880] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[   16.675774] marvell-cesa f1030000.crypto: CESA device successfully registered
[   16.765271] Scanning device for bad blocks
[   17.045944] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   17.062427] systemd-udevd[306]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
done.
[....] Waiting for /dev to be fully populated...[   17.279608] 3 fixed-partitions partitions found on MTD device orion_nand
[   17.286398] Creating 3 MTD partitions on "orion_nand":
[   17.295114] 0x000000000000-0x000000100000 : "u-boot"
[   17.302441] 0x000000100000-0x000000700000 : "uImage"
[   17.309686] 0x000000600000-0x00000de00000 : "root"
done.
[....] Setting up keyboard layout.../etc/console-setup/cached_setup_keyboard.sh: 7: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty1: No such file
/etc/console-setup/cached_setup_keyboard.sh: 8: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty2: No such file
/etc/console-setup/cached_setup_keyboard.sh: 9: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty3: No such file
/etc/console-setup/cached_setup_keyboard.sh: 10: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty4: No such file
/etc/console-setup/cached_setup_keyboard.sh: 11: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty5: No such file
/etc/console-setup/cached_setup_keyboard.sh: 12: /etc/console-setup/cached_setup_keyboard.sh: cannot open /dev/tty6: No such file
Couldn't get a file descriptor referring to the console
Couldn't get a file descriptor referring to the console
done.
[   18.444266] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[....] Cleaning up temporary files... /tmp. ok 
[....] Checking file systems...fsck from util-linux 2.33.1
done.
[....] Mounting local filesystems...done.
[....] Activating swapfile swap...[   20.334260] Adding 131068k swap on /swapfile.  Priority:-2 extents:6 across:327676k FS
done.
[....] Cleaning up temporary files.... ok 
[....] Cleaning up temporary files.... ok 
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Setting up console font and keymap...done.
[....] Starting system message bus: dbus. ok 
[....] Starting session management daemon: elogind[   21.963523] elogind-daemon[1048]: New seat seat0.
. ok 

Debian GNU/Linux 10 mumble ttyS0

mumble login:  root
Password: 
Last login: Sun Feb 20 06:06:12 UTC 2022 on ttyS0
Linux mumble 4.19.0-18-marvell #1 Debian 4.19.208-1 (2021-09-29) 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.
[  128.882138] elogind-daemon[1048]: New session 1 of user root.
(debian-armel)root@mumble:~# uname -a
Linux mumble 4.19.0-18-marvell #1 Debian 4.19.208-1 (2021-09-29) armv5tel GNU/Linux
(debian-armel)root@mumble:~# 
(debian-armel)root@mumble:~# uname -r
4.19.0-18-marvell



Edited 1 time(s). Last edit at 02/20/2022 01:26AM by fcopurico.
Re: Help: kernel build vs uBoot requirements
February 20, 2022 01:19AM
If I remove USB I can still boot from OpenWrt in NAND.
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Using egiga0 device
host 192.168.0.104 is alive
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.95 (buildbot@79ba7960e4b2) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7676-cddd7b4c77)) #0 Wed Jan 30 12:21:02 2019
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Seagate GoFlex Home
[    0.000000] Memory policy: Data cache writeback
[    0.000000] random: get_random_bytes called from 0xc0700994 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 122264K/131072K available (4692K kernel code, 166K rwdata, 724K rodata, 1024K init, 208K bss, 8808K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc05952a0   (5685 kB)
[    0.000000]       .init : 0xc0700000 - 0xc0800000   (1024 kB)
[    0.000000]       .data : 0xc0800000 - 0xc0829840   ( 167 kB)
[    0.000000]        .bss : 0xc0829840 - 0xc085d88c   ( 209 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000039] Switching to timer-based delay loop, resolution 5ns
[    0.000114] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000136] pid_max: default: 32768 minimum: 301
[    0.000288] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000309] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000871] CPU: Testing write buffer coherency: ok
[    0.001642] Setting up static identity map for 0x100000 - 0x10003c
[    0.001893] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.004862] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.004891] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.004981] pinctrl core: initialized pinctrl subsystem
[    0.006028] NET: Registered protocol family 16
[    0.006404] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.007322] cpuidle: using governor ladder
[    0.007678] Feroceon L2: Enabling L2
[    0.007722] Feroceon L2: Cache support initialised.
[    0.007974] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.011459] No ATAGs?
[    0.027530] SCSI subsystem initialized
[    0.028219] usbcore: registered new interface driver usbfs
[    0.028276] usbcore: registered new interface driver hub
[    0.028330] usbcore: registered new device driver usb
[    0.030256] clocksource: Switched to clocksource orion_clocksource
[    0.031034] NET: Registered protocol family 2
[    0.031633] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.031657] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.031675] TCP: Hash tables configured (established 1024 bind 1024)
[    0.031754] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.031776] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.031913] NET: Registered protocol family 1
[    0.033038] Crashlog allocated RAM at address 0x3f00000
[    0.034619] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.038971] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.038984] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.046746] io scheduler noop registered
[    0.046760] io scheduler deadline registered (default)
[    0.047926] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.071394] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.073445] console [ttyS0] disabled
[    0.073521] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 12500000) is a 16550A
[    0.539646] console [ttyS0] enabled
[    0.544263] sata_mv f1080000.sata: slots 32 ports 2
[    0.552631] scsi host0: sata_mv
[    0.556280] scsi host1: sata_mv
[    0.559563] ata1: SATA max UDMA/133 irq 32
[    0.563715] ata2: SATA max UDMA/133 irq 32
[    0.568288] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
[    0.574701] nand: Toshiba NAND 256MiB 3,3V 8-bit
[    0.579340] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.586972] Scanning device for bad blocks
[    0.808021] 2 cmdlinepart partitions found on MTD device orion_nand
[    0.814331] Creating 2 MTD partitions on "orion_nand":
[    0.819493] 0x000000000000-0x000000100000 : "u-boot"
[    0.825018] 0x000000100000-0x000010000000 : "ubi"
[    0.831706] libphy: Fixed MDIO Bus: probed
[    0.836053] libphy: orion_mdio_bus: probed
[    0.842706] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    0.851294] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 52:3b:20:9c:11:51
[    0.860099] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.866681] ehci-pci: EHCI PCI platform driver
[    0.871205] ehci-orion: EHCI orion driver
[    0.875405] orion-ehci f1050000.ehci: EHCI Host Controller
[    0.880959] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    0.888777] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    0.920269] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    0.926829] hub 1-0:1.0: USB hub found
[    0.930818] hub 1-0:1.0: 1 port detected
[    0.935195] usbcore: registered new interface driver usb-storage
[    0.941606] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    0.948580] i2c /dev entries driver
[    0.952691] orion_wdt: Initial timeout 21 sec
[    0.961969] marvell-cesa f1030000.crypto: CESA device successfully registered
[    0.969995] NET: Registered protocol family 10
[    0.976110] Segment Routing with IPv6
[    0.979860] NET: Registered protocol family 17
[    0.984390] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    0.997420] 8021q: 802.1Q VLAN Support v1.8
[    1.004357] UBI: auto-attach mtd1
[    1.007698] ubi0: attaching mtd1
[    1.173022] ata1: SATA link down (SStatus 0 SControl F300)
[    1.389244] ubi0: scanning is finished
[    1.405964] ubi0: attached mtd1 (name "ubi", size 255 MiB)
[    1.411525] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    1.418430] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    1.425178] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    1.432013] ubi0: good PEBs: 2040, bad PEBs: 0, corrupted PEBs: 0
[    1.438129] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[    1.445399] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1313013592
[    1.454580] ubi0: available PEBs: 0, total reserved PEBs: 2040, PEBs reserved for bad PEB handling: 40
[    1.464625] block ubiblock0_1: created from ubi0:1(rootfs)
[    1.470140] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[    1.477353] rtc-mv f1010300.rtc: setting system clock to 2022-02-20 06:07:27 UTC (1645337247)
[    1.486434] ubi0: background thread "ubi_bgt0d" started, PID 950
[    1.502650] ata2: SATA link down (SStatus 0 SControl F300)
[    1.512375] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    1.522441] Freeing unused kernel memory: 1024K
[    1.843270] init: Console is alive
[    1.846840] init: - watchdog -
[    1.947800] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    1.955094] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    1.964988] init: - preinit -
[    2.200285] random: fast init done
[    2.460981] random: jshn: uninitialized urandom read (4 bytes read)
[    2.533523] random: jshn: uninitialized urandom read (4 bytes read)
[    2.565241] random: jshn: uninitialized urandom read (4 bytes read)
[    2.644212] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[    2.654048] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[    2.661187] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    4.705899] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[    4.715776] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    5.858365] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 1020
[    5.892099] UBIFS (ubi0:2): recovery needed
[    6.053988] UBIFS (ubi0:2): recovery completed
[    6.058535] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[    6.066426] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    6.076404] UBIFS (ubi0:2): FS size: 252112896 bytes (240 MiB, 1954 LEBs), journal size 12644352 bytes (12 MiB, 98 LEBs)
[    6.087333] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB) 
[    6.093990] UBIFS (ubi0:2): media format: w4/r0 (latest is w5/r0), UUID ########-####-####-####-############, small LPT model
[    6.110881] mount_root: switching to ubifs overlay
[    6.128200] urandom-seed: Seeding with /etc/urandom.seed
[    6.212292] procd: - early -
[    6.215257] procd: - watchdog -
[    7.028628] procd: - watchdog -
[    7.032025] procd: - ubus -
[    7.067198] urandom_read: 3 callbacks suppressed
[    7.067204] random: ubusd: uninitialized urandom read (4 bytes read)
[    7.085745] random: ubusd: uninitialized urandom read (4 bytes read)
[    7.092455] random: ubusd: uninitialized urandom read (4 bytes read)
[    7.099720] procd: - init -
Please press Enter to activate this console.
[    7.283181] kmodloader: loading kernel modules from /etc/modules.d/*
[    7.292434] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    7.305574] ip_tables: (C) 2000-2006 Netfilter Core Team
[    7.315610] nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
[    7.350611] xt_time: kernel timezone is -0000
[    7.360840] PPP generic driver version 2.4.2
[    7.366739] NET: Registered protocol family 24
[    7.373482] kmodloader: done loading kernel modules from /etc/modules.d/*
[   12.025956] br-lan: port 1(eth0) entered blocking state
[   12.031258] br-lan: port 1(eth0) entered disabled state
[   12.036740] device eth0 entered promiscuous mode
[   12.080467] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   13.709798] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   13.719681] br-lan: port 1(eth0) entered blocking state
[   13.724959] br-lan: port 1(eth0) entered forwarding state
[   13.736743] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready



BusyBox v1.28.4 () built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 18.06.2, r7676-cddd7b4c77
 -----------------------------------------------------
root@OpenWrt:/#

Very very good and very Happy. Thanks.



Edited 1 time(s). Last edit at 02/20/2022 01:35AM by fcopurico.
Re: Help: kernel build vs uBoot requirements
February 20, 2022 03:27PM
Cool, very nice!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Help: kernel build vs uBoot requirements
February 21, 2022 12:07AM
fcopurico Wrote:
-------------------------------------------------------
> _______ ________ __
> | |.-----.-----.-----.| | | |.----.|
> |_
> | - || _ | -__| || | | || _||
> _|
> |_______|| __|_____|__|__||________||__|
> |____|
> |__| W I R E L E S S F R E E D O M
> -----------------------------------------------------
> OpenWrt 18.06.2, r7676-cddd7b4c77
> -----------------------------------------------------
> root@OpenWrt:/# [/code]
>
Just curious why you are using a no longer supported version of OpenWrt when the device you are using is supported by the latest release OpenWrt 21.02.1 for GoFlex Home.

Ray
Re: Help: kernel build vs uBoot requirements
February 22, 2022 04:33PM
The why in general?
I am new to doozan.com and Debian on Arm device. My installation went relative easy, because a friend help. And that I follow Wiki and a few other links here.

Openwrt version Why?
I do not intent to use Openwrt. Nor to run from NAND. So any version is good enough to be used as a Rescue System.

Why exactly 18.06.2 ?
Because it was posted here: https://forum.doozan.com/read.php?2,130784
I guess if it did work for him why not used it? There is no real good reason. Just I went with the flow and help from a friend.

Why this post?
Because I will be building my own kernel, I like to turn off one or more forced features like wiregard. I do not intent to convince anyone, but I personally consider this a security threat. And I like to add at least a driver. Now the most important is that I intend to make use of Debia's Live Boot & persistence feature. Where the OS will be save as a whole in a Read ONLY file "firmware.squashfs". All (volatile) changing personal data and OS changes will be store ins a Read/Write ext4 file system image called "persistence". As a reference. lets just say a 2GB size file. The advantage is that my daily backup, becomes just to copy this 2 GB file to HDD. I try to get is to make repair as simple as it can be. In the event that OS become unstable, I only need to delete my "persistence" file and restore from my daily backup. And I am up in a minute.

Yes OS will boot just as your Debian Live CD or USB. Just that is not a CD/USB, instead a "firmware.squashfs" store in HDD.

rayknight I hope I did not confuse you any further. But now you know my project intention. I have not tested yet Debian's persistence/Live boot method. I was hold by personal issues last two days. I hope to test it tonight. It should be no trouble as it is a build in Debian thing.



Edited 1 time(s). Last edit at 02/22/2022 04:37PM by fcopurico.
Re: Help: kernel build vs uBoot requirements
February 22, 2022 07:46PM
So your intent is just to use OpenWrt for rescue only. I suppose in that case the version you are using doesn't matter. I just wanted to ensure that you were aware that the version you were using is currently unsupported. A more current version would have less potential security issues and updates would be available if any new vulnerabilities were reported.

Ray
Re: Help: kernel build vs uBoot requirements
February 23, 2022 05:58AM
rayknight

Thanks for your concern.

Regards security issues, updates, new vulnerabilities etc. I am one of those guys that do not believe the way all that updated STUFF is been handle. It is ironic how Doors are left open on purpose. Just to tell others they have the latest in updates. A never ending updates that may be the real cause of all.

It is easy if you are concern on security, then Browsers should have turn off ALL their scripts. But java, java-script and many others are free to use by web sites. Now even HTML5 are left running on the free. Clearly the ones that claim to secure your data are the same that wants to collect it in the 1rst place. Even our Linux PC should have some sort of collar to keep projects like python under control. Python is just one, there are so many scripts like translators that I will not have space here if I start mentioning. They should normally be off until we have a need for them. That is my opinion.

And at the end all this Hi profile companies running the best updates, and what they do? They tell you, we did all what we could do to safegard your personal data. But it is the fault of all this MF%^&* (filled in the blank) hackers. And your data is gone, no repercussion.

Now see my approach, This unit will be on without human intervention. Will be build with only what It needs. And in any case its OS will be Read Only. Any vulnerability will not survive a daily reboot.

Listen I do not pretend to convince you. We all have to decide our-self. Go with the flow and be Updated. Or try something else.

========

I've edited this post (see italic). This is a tech forum and I understood it was sarcastic, but other with English as second language might not.



Edited 1 time(s). Last edit at 02/23/2022 04:06PM by bodhi.
Re: Help: kernel build vs uBoot requirements
February 23, 2022 04:08PM
I'd think that this discussion has gone off topic. Please keep on topic or create a new thread in Off-Topics sub-forum.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Help: kernel build vs uBoot requirements
February 24, 2022 01:01AM
Sorry. It was not my intention to go against any rule in the forum. For house keeping. You can delete that post and even this one.

I only have thanks from what I have learn from you guys. And from what I am hopping to learn new.
Re: Help: kernel build vs uBoot requirements
February 24, 2022 02:07AM
fcopurico,

Not at all. Vent all you'd like :) The only rule we have is common sense (avoiding race, gender, religion, ethnic, etc...etc... discussion/opinion/bias, i.e. subjects that could be misunderstood and causes unecessary flame wars).

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: