(WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package
Posted by bodhi
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package March 19, 2020 04:42PM |
Registered: 4 years ago Posts: 1 |
bodhi, Yama, tommy79, markTurner.
Looking for some tips to port the work done here
https://github.com/KL-Yang/seagate_central_linux
to the latest 4.19 kernel.
Here it mentions doing "make uImage" but in this thread it always refers to mkimage. If I want to create a fresh kernel and initrd, and use mkimage, what are my options for the "-d" . Can I use the existing working 4.19 kernel from the download link on the repo README? Or can I make initrd a different way. My build env is Ubuntu 19.10.
So far trying to use even the linux.4.4.121 source code from Tommy. I do not get a fully working kernel. It boots but then does a stack trace. Same with my port to 4.19.110 and the latest 4.14. This is a two bay Seagate Business Storage LAN. I can get the bodhi kernel from the opening page to boot but do not get a network. . Ideally I would like to get the latest 4.19 but will setting for 4.14 or 4.4 if I have to. I guess 5.X is not an option or has anyone played with that yet?
Thanks for any tips you can provide in helping me gen my own kernel and initrd.
Keith
Looking for some tips to port the work done here
https://github.com/KL-Yang/seagate_central_linux
to the latest 4.19 kernel.
Here it mentions doing "make uImage" but in this thread it always refers to mkimage. If I want to create a fresh kernel and initrd, and use mkimage, what are my options for the "-d" . Can I use the existing working 4.19 kernel from the download link on the repo README? Or can I make initrd a different way. My build env is Ubuntu 19.10.
So far trying to use even the linux.4.4.121 source code from Tommy. I do not get a fully working kernel. It boots but then does a stack trace. Same with my port to 4.19.110 and the latest 4.14. This is a two bay Seagate Business Storage LAN. I can get the bodhi kernel from the opening page to boot but do not get a network. . Ideally I would like to get the latest 4.19 but will setting for 4.14 or 4.4 if I have to. I guess 5.X is not an option or has anyone played with that yet?
Thanks for any tips you can provide in helping me gen my own kernel and initrd.
Keith
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package March 19, 2020 07:45PM |
Admin Registered: 13 years ago Posts: 19,102 |
Keith,
> Here it mentions doing "make uImage" but in this
> thread it always refers to mkimage.
Use mkimage. It is a manual command to produce the uImage the way you want. make depends on the Makefile in the directory that you are running.
> So far trying to use even the linux.4.4.121 source
> code from Tommy. I do not get a fully working
> kernel. It boots but then does a stack trace.
Depending on how serious the error is. Can you post serial console log?
> Same with my port to 4.19.110 and the latest
> 4.14. This is a two bay Seagate Business Storage
> LAN. I can get the bodhi kernel from the opening
> page to boot but do not get a network.
The kernel I posted was only a work-in-progress build. So there are a lot more that need to be added. That network problem might be that the DTS definition was not correct for that part. In fact, I just took a peek at my patch, there is no network definition in it! not sure why (it was too long ago and I've archived this project build).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/19/2020 10:51PM by bodhi.
> Here it mentions doing "make uImage" but in this
> thread it always refers to mkimage.
Use mkimage. It is a manual command to produce the uImage the way you want. make depends on the Makefile in the directory that you are running.
> So far trying to use even the linux.4.4.121 source
> code from Tommy. I do not get a fully working
> kernel. It boots but then does a stack trace.
Depending on how serious the error is. Can you post serial console log?
> Same with my port to 4.19.110 and the latest
> 4.14. This is a two bay Seagate Business Storage
> LAN. I can get the bodhi kernel from the opening
> page to boot but do not get a network.
The kernel I posted was only a work-in-progress build. So there are a lot more that need to be added. That network problem might be that the DTS definition was not correct for that part. In fact, I just took a peek at my patch, there is no network definition in it! not sure why (it was too long ago and I've archived this project build).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/19/2020 10:51PM by bodhi.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package June 28, 2020 09:36PM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package June 30, 2020 05:36PM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 07, 2020 06:54PM |
Registered: 4 years ago Posts: 17 |
Managed to run the kernel on my 4bay , but the problem is this
======
moderator edit: please use code tags to post log.
Edited 1 time(s). Last edit at 10/21/2020 04:01PM by bodhi.
U-Boot 2008.10-mpcore (Nov 11 2012 - 15:04:27)
Whitney model:(ELCAPITAN) release v1.2-beta2
CPU: Cavium Networks CNS3000
ID Code: 410fb024 (Part number: 0xB02, Revision number: 4)
CPU ID: 900
Chip Version: c
DRAM: 512 MB
Parallel Flash: 0 kB
Flash Manufacturer: MX
Serial Flash: 512 kB
Serial Flash:
Bank # 1: Nb pages: 2048 Page Size: 256
Size: 524288 bytes, Logical address: 0x60000000
Area 0: 60000000 to 60FFFFFF SPI flash
In: serial
Out: serial
Err: serial
CPU works at 700 MHz (700/1/1)
DDR2 Speed is 400 MHz
Restoring RTC
Whitney # tftp 0x28000000
Initialize PHY s/w auto-polling
phy_id: 1c
Initialize RTL8211
phy_id: 1c
Initialize RTL8211
TFTP from server 192.168.1.1; our IP address is 192.168.1.2
Filename 'uImage'.
Load address: 0x28000000
Loading: T T #################################################################
#################################################################
#################################################################
###########
done
Bytes transferred = 3019912 (2e1488 hex)
Whitney # bootm 0x28000000
enter do_eth_down!!!
## Booting kernel from Legacy Image at 28000000 ...
Image Name: Linux-4.4.121-tommy
Created: 2018-03-18 23:01:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3019848 Bytes = 2.9 MB
Load Address: 22000000
Entry Point: 22000000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x900
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.4.121-tommy (root@debian9) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #26 SMP Sun Mar 18 23:57:36 CET 2018
CPU: ARMv6-compatible processor [410fb024] revision 4 (ARMv7), cr=00c5787d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Seagate CNS3420 NAS
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @dfbd9000 s17004 r8192 d23956 u49152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,38400 mem=512M@0x20000000 root=/dev/sda1
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513692K/524288K available (4211K kernel code, 159K rwdata, 1256K rodata, 212K init, 101K bss, 10596K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc055ef9c (5468 kB)
.init : 0xc055f000 - 0xc0594000 ( 212 kB)
.data : 0xc0594000 - 0xc05bbe10 ( 160 kB)
.bss : 0xc05bbe10 - 0xc05d5348 ( 102 kB)
Hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
NR_IRQS:16 nr_irqs:16 16
clocksource: freerun: mask: 0xffffffffffff max_cycles: 0x179dd7f66, max_idle_ns: 28210892933900 ns
smp_twd: clock not found -2
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating local timer... 347.99MHz.
Calibrating delay loop... 277.70 BogoMIPS (lpj=1388544)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Initializing cgroup subsys io
Initializing cgroup subsys devices
Initializing cgroup subsys net_cls
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x200082a0 - 0x200082fc
Brought up 2 CPUs
SMP: Total of 2 processors activated (555.41 BogoMIPS).
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
L2C: DT/platform modifies aux control register: 0x02040000 -> 0x02540000
L2C-310 cache controller enabled, 8 ways, 256 kB
L2C-310: CACHE_ID 0x410000c4, AUX_CTRL 0x06540000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource freerun
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x78000000 (irq = 45, base_baud = 1500000) is a 16550A
loop: module loaded
mGine mflash driver, (c) 2008 mGine Co.
zram: Added device: zram0
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi host0: ahci
scsi host1: ahci
ata1: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x100 irq 65
ata2: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x180 irq 65
physmap platform flash device: 08000000 at 10000000
physmap-flash physmap-flash.0: map_probe failed
libphy: Fixed MDIO Bus: probed
libphy: CNS3xxx MII Bus: probed
eth0: RGMII PHY 0 on cns3xxx Switch
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
CNS3XXX Real Time Clock, (c) 2009 Cavium Networks
rtc irq:23
rtc rtc0: invalid alarm value: 1900-1-7 0:0:0
cns3xxx-rtc cns3xxx-rtc: rtc core: registered cns3xxx-rtc as rtc0
i2c /dev entries driver
adt7475 0-002e: ADT7473 device, revision 0
adt7475 0-002e: Optional features: fan4 pwm2
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
PCI-E0 uses external clock source.
ata2: SATA link down (SStatus 0 SControl 300)
PCIe: Port[0] Enable PCIe LTSSM
PCIe: Port[0] Check data link layer...
Link up.
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0xac000000-0xacffffff]
pci_bus 0000:00: root bus resource [mem 0xa0000000-0xaaffffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers disabled
PCIe map irq: 0000:01:00.00 slot 0, pin 1, irq: 61
pci 0000:00:00.0: BAR 8: assigned [mem 0xa0000000-0xa00fffff]
pci 0000:01:00.0: BAR 0: assigned [mem 0xa0000000-0xa0007fff 64bit]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0: bridge window [mem 0xa0000000-0xa00fffff]
pci 0000:00:00.0: Max Payload Size set to 128/ 128 (was 128), Max Read Rq 128
pci 0000:01:00.0: Max Payload Size set to 128/ 512 (was 128), Max Read Rq 128
pci 0000:01:00.0: enabling device (0140 -> 0142)
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
xhci_hcd 0000:01:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb1: SerialNumber: 0000:01:00.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb2: SerialNumber: 0000:01:00.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: HPA detected: current 39070080, native 39179952
ata1.00: ATA-7: SAMSUNG HM020GI, YU100-06, max UDMA7
ata1.00: 39070080 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM020GI 0-06 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 39070080 512-byte logical blocks: (20.0 GB/18.6 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
List of all partitions:
0800 19535040 sda driver: sd
0801 102400 sda1 f2ea40bc-01
0802 19430400 sda2 f2ea40bc-02
No filesystem could mount root, tried: ext3 ext4 ext2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.121-tommy #26
Hardware name: Seagate CNS3420 NAS
Backtrace:
[<c00131f0>] (dump_backtrace) from [<c00133e8>] (show_stack+0x18/0x1c)
r7:c058485c r6:60000093 r5:00000000 r4:c05a36c8
[<c00133d0>] (show_stack) from [<c01f41a0>] (dump_stack+0x94/0xb0)
[<c01f410c>] (dump_stack) from [<c009fc20>] (panic+0x94/0x1fc)
r7:c058485c r6:c04e8734 r5:c04fa654 r4:c05bc1e8
[<c009fb90>] (panic) from [<c056038c>] (mount_block_root+0x288/0x2cc)
r3:df441ec0 r2:80000000 r1:df441ec0 r0:c04e86c8
r7:c058485c
[<c0560104>] (mount_block_root) from [<c0560430>] (mount_root+0x60/0x7c)
r10:c055f5fc r9:c058483c r8:00000083 r7:c055d150 r6:c0584838 r5:c0584871
r4:00000001
[<c05603d0>] (mount_root) from [<c0560588>] (prepare_namespace+0x13c/0x1a0)
r5:c0584871 r4:c05bbe44
[<c056044c>] (prepare_namespace) from [<c055fec8>] (kernel_init_freeable+0x194/0x1e4)
r6:c0584838 r5:c05bbe20 r4:00000008
[<c055fd34>] (kernel_init_freeable) from [<c041ea50>] (kernel_init+0x10/0xf0)
r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c041ea40
r4:00000000
[<c041ea40>] (kernel_init) from [<c000f870>] (ret_from_fork+0x14/0x24)
r5:c041ea40 r4:00000000
CPU0: stopping
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.121-tommy #26
Hardware name: Seagate CNS3420 NAS
Backtrace:
[<c00131f0>] (dump_backtrace) from [<c00133e8>] (show_stack+0x18/0x1c)
r7:c0595f10 r6:60000193 r5:00000000 r4:c05a36c8
[<c00133d0>] (show_stack) from [<c01f41a0>] (dump_stack+0x94/0xb0)
[<c01f410c>] (dump_stack) from [<c0016350>] (handle_IPI+0x17c/0x1bc)
r7:c0595f10 r6:00000000 r5:00000000 r4:c05bc060
[<c00161d4>] (handle_IPI) from [<c00094b8>] (gic_handle_irq+0x8c/0xa0)
r7:c0596550 r6:c0595f10 r5:000003ff r4:ff00010c
[<c000942c>] (gic_handle_irq) from [<c0013df4>] (__irq_svc+0x54/0x70)
Exception stack(0xc0595f10 to 0xc0595f58)
5f00: 00000001 00000000 00000000 00000000
5f20: c0594000 c059627c 00000000 00000000 c05962dc c058e2a0 c04246b8 c0595f6c
5f40: c0595f70 c0595f60 c00102b0 c00102b4 60000013 ffffffff
r10:c04246b8 r9:c058e2a0 r8:c05962dc r7:c0595f44 r6:ffffffff r5:60000013
r4:c00102b4
[<c0010284>] (arch_cpu_idle) from [<c005afe4>] (default_idle_call+0x28/0x34)
[<c005afbc>] (default_idle_call) from [<c005b21c>] (cpu_startup_entry+0x1d8/0x250)
[<c005b044>] (cpu_startup_entry) from [<c041ea28>] (rest_init+0x6c/0x84)
r7:c0596220
[<c041e9bc>] (rest_init) from [<c055fcc0>] (start_kernel+0x340/0x3b4)
[<c055f980>] (start_kernel) from [<20008078>] (0x20008078)
r10:20423788 r9:410fb024 r8:2000400a r7:c0599b44 r6:c0584a24 r5:c0596250
r4:c05bbfd4
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
======
moderator edit: please use code tags to post log.
Edited 1 time(s). Last edit at 10/21/2020 04:01PM by bodhi.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 07, 2020 11:18PM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
> Whitney # bootm 0x28000000
> enter do_eth_down!!!
> ## Booting kernel from Legacy Image at 28000000
> ...
> Image Name: Linux-4.4.121-tommy
> Created: 2018-03-18 23:01:24 UTC
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 3019848 Bytes = 2.9 MB
> Load Address: 22000000
> Entry Point: 22000000
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
So you are booting with the uImage only.
> Kernel command line: console=ttyS0,38400
> mem=512M@0x20000000 root=/dev/sda1
And your root device is /dev/sda1
So take this SAMSUNG HDD/SSD to another Linux box, and list the partition using fdisk. If it was assigned /dev/sdb on this Linux box
How many partitions are on this disk, and is the rootfs on the 1st partition?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Whitney # bootm 0x28000000
> enter do_eth_down!!!
> ## Booting kernel from Legacy Image at 28000000
> ...
> Image Name: Linux-4.4.121-tommy
> Created: 2018-03-18 23:01:24 UTC
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 3019848 Bytes = 2.9 MB
> Load Address: 22000000
> Entry Point: 22000000
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
So you are booting with the uImage only.
> Kernel command line: console=ttyS0,38400
> mem=512M@0x20000000 root=/dev/sda1
And your root device is /dev/sda1
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: HPA detected: current 39070080, native 39179952 ata1.00: ATA-7: SAMSUNG HM020GI, YU100-06, max UDMA7 ata1.00: 39070080 sectors, multi 0: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM020GI 0-06 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 39070080 512-byte logical blocks: (20.0 GB/18.6 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI disk List of all partitions: 0800 19535040 sda driver: sd
So take this SAMSUNG HDD/SSD to another Linux box, and list the partition using fdisk. If it was assigned /dev/sdb on this Linux box
fdisk -l /dev/sdb
How many partitions are on this disk, and is the rootfs on the 1st partition?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 08, 2020 12:15PM |
Registered: 4 years ago Posts: 17 |
bodhi, I have a little progress, but still I need a working dump of The u-Boot MX25L4006 chip from the 4-bay version of the NAS
=====
moderator edit: please use code tag (Formatted Code button) to post log.
Edited 1 time(s). Last edit at 07/09/2020 04:44AM by bodhi.
U-Boot 2008.10-mpcore (Nov 11 2012 - 15:04:27)
Whitney model:(ELCAPITAN) release v1.2-beta2
CPU: Cavium Networks CNS3000
ID Code: 410fb024 (Part number: 0xB02, Revision number: 4)
CPU ID: 900
Chip Version: c
DRAM: 512 MB
Parallel Flash: 0 kB
Flash Manufacturer: MX
Serial Flash: 512 kB
Serial Flash:
Bank # 1: Nb pages: 2048 Page Size: 256
Size: 524288 bytes, Logical address: 0x60000000
Area 0: 60000000 to 60FFFFFF SPI flash
In: serial
Out: serial
Err: serial
CPU works at 700 MHz (700/1/1)
DDR2 Speed is 400 MHz
Restoring RTC
Whitney # tftp
Initialize PHY s/w auto-polling
phy_id: 1c
Initialize RTL8211
phy_id: 1c
Initialize RTL8211
TFTP from server 192.168.1.1; our IP address is 192.168.1.33
Filename 'uImage'.
Load address: 0x800000
Loading: T T #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####
done
Bytes transferred = 3019912 (2e1488 hex)
Whitney # bootm
enter do_eth_down!!!
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.121-tommy
Created: 2018-03-18 23:01:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3019848 Bytes = 2.9 MB
Load Address: 22000000
Entry Point: 22000000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x900
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.4.121-tommy (root@debian9) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #26 SMP Sun Mar 18 23:57:36 CET 2018
CPU: ARMv6-compatible processor [410fb024] revision 4 (ARMv7), cr=00c5787d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Seagate CNS3420 NAS
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @dfbd9000 s17004 r8192 d23956 u49152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,38400 mem=512M@0x20000000 root=/dev/sda1
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513692K/524288K available (4211K kernel code, 159K rwdata, 1256K rodata, 212K init, 101K bss, 10596K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc055ef9c (5468 kB)
.init : 0xc055f000 - 0xc0594000 ( 212 kB)
.data : 0xc0594000 - 0xc05bbe10 ( 160 kB)
.bss : 0xc05bbe10 - 0xc05d5348 ( 102 kB)
Hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
NR_IRQS:16 nr_irqs:16 16
clocksource: freerun: mask: 0xffffffffffff max_cycles: 0x179dd7f66, max_idle_ns: 28210892933900 ns
smp_twd: clock not found -2
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating local timer... 347.98MHz.
Calibrating delay loop... 277.70 BogoMIPS (lpj=1388544)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Initializing cgroup subsys io
Initializing cgroup subsys devices
Initializing cgroup subsys net_cls
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x200082a0 - 0x200082fc
Brought up 2 CPUs
SMP: Total of 2 processors activated (555.41 BogoMIPS).
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
L2C: DT/platform modifies aux control register: 0x02040000 -> 0x02540000
L2C-310 cache controller enabled, 8 ways, 256 kB
L2C-310: CACHE_ID 0x410000c4, AUX_CTRL 0x06540000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource freerun
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x78000000 (irq = 45, base_baud = 1500000) is a 16550A
loop: module loaded
mGine mflash driver, (c) 2008 mGine Co.
zram: Added device: zram0
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi host0: ahci
scsi host1: ahci
ata1: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x100 irq 65
ata2: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x180 irq 65
physmap platform flash device: 08000000 at 10000000
physmap-flash physmap-flash.0: map_probe failed
libphy: Fixed MDIO Bus: probed
libphy: CNS3xxx MII Bus: probed
eth0: RGMII PHY 0 on cns3xxx Switch
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
CNS3XXX Real Time Clock, (c) 2009 Cavium Networks
rtc irq:23
rtc rtc0: invalid alarm value: 1900-1-8 0:0:0
cns3xxx-rtc cns3xxx-rtc: rtc core: registered cns3xxx-rtc as rtc0
i2c /dev entries driver
adt7475 0-002e: ADT7473 device, revision 0
adt7475 0-002e: Optional features: fan4 pwm2
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
ata2: SATA link down (SStatus 0 SControl 300)
PCI-E0 uses external clock source.
PCIe: Port[0] Enable PCIe LTSSM
PCIe: Port[0] Check data link layer...
Link up.
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0xac000000-0xacffffff]
pci_bus 0000:00: root bus resource [mem 0xa0000000-0xaaffffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers disabled
PCIe map irq: 0000:01:00.00 slot 0, pin 1, irq: 61
pci 0000:00:00.0: BAR 8: assigned [mem 0xa0000000-0xa00fffff]
pci 0000:01:00.0: BAR 0: assigned [mem 0xa0000000-0xa0007fff 64bit]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0: bridge window [mem 0xa0000000-0xa00fffff]
pci 0000:00:00.0: Max Payload Size set to 128/ 128 (was 128), Max Read Rq 128
pci 0000:01:00.0: Max Payload Size set to 128/ 512 (was 128), Max Read Rq 128
pci 0000:01:00.0: enabling device (0140 -> 0142)
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
xhci_hcd 0000:01:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb1: SerialNumber: 0000:01:00.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb2: SerialNumber: 0000:01:00.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: HPA detected: current 39070080, native 39179952
ata1.00: ATA-7: SAMSUNG HM020GI, YU100-06, max UDMA7
ata1.00: 39070080 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM020GI 0-06 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 39070080 512-byte logical blocks: (20.0 GB/18.6 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext3 filesystem) on device 8:1.
devtmpfs: mounted
Freeing unused kernel memory: 212K
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
ERROR: could not open /proc/stat: No such file or directory
findfs: unable to resolve 'LABEL=rootfs'
[warn] Files under mount point '/run' will be hidden. ... (warning).
[....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232
. ok
[....] Synthesizing the initial hotplug events...random: udevadm: uninitialized urandom read (16 bytes read, 82 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 87 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 88 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 88 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 89 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 89 bits of entropy available)
done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Setting hostname to 'debian'...done.
random: nonblocking pool is initialized
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Activating swap:.
Usage:
mountpoint [-qd] /path/to/directory
mountpoint -x /dev/device
Check whether a directory or file is a mountpoint.
Options:
-q, --quiet quiet mode - don't print anything
-d, --fs-devno print maj:min device number of the filesystem
-x, --devno print maj:min device number of the block device
-h, --help display this help and exit
-V, --version output version information and exit
For more details see mountpoint(1).
EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Will now check root file system:fsck from util-linux 2.29.2
[/sbin/fsck.ext3 (1) -- /run/rootdev] fsck.ext3 -y -C0 /run/rootdev
e2fsck 1.43.4 (31-Jan-2017)
/run/rootdev: clean, 11953/1221600 files, 224261/4883504 blocks
. ok
mount: can't find LABEL=rootfs
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Will now activate lvm and md swap:done.
[info] Will now check all file systems.
fsck from util-linux 2.29.2
LABEL=rootfs: nonexistent device ("nofail" fstab option may be used to skip this device)
Checking all file systems.
LABEL=rootfs is not mounted
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 LABEL=rootfs
fsck.ext3: Unable to resolve 'LABEL=rootfs'
fsck exited with status code 8
[....] File system check failed. A log is being saved in /var/log/fsck/checkfs i[FAILt location is writable. Please repair the file system manually. ... failed!
[....] A maintenance shell will now be started. CONTROL-D will terminate this sh[warnnd resume system boot. ... (warning).
Give root password for maintenance
(or press Control-D to continue):
rm: cannot remove '/tmp/.clean': Read-only file system
[ ok ] Cleaning up temporary files....
[ ok ] Will now mount local filesystems:.
[ ok ] Will now activate swapfile swap:done.
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Checking minimum space in /tmp...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables...done.
[FAIL] Initializing random number generator...failed.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
can't create /var/lib/dhcp/dhclient.eth0.leases: Read-only file system
RTNETLINK answers: Cannot assign requested address
Listening on LPF/eth0/00:00:00:00:00:00
Sending on LPF/eth0/00:00:00:00:00:00
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
/etc/init.d/bootlogs: 23: /etc/init.d/bootlogs: cannot create /var/log/dmesg: Read-only file system
chgrp: cannot access '/var/log/dmesg': No such file or directory
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1585 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1583 (klogd)
. ok
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Running local boot scripts (/etc/rc.local).
Z▒▒T▒▒J
=====
moderator edit: please use code tag (Formatted Code button) to post log.
Edited 1 time(s). Last edit at 07/09/2020 04:44AM by bodhi.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 08, 2020 04:15PM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
Which rootfs are you using? can you log into Debian using serial console now?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Which rootfs are you using? can you log into Debian using serial console now?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 09, 2020 03:02AM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 09, 2020 04:50AM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
Login and,
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Login and,
mount cat /etc/fstab
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 09, 2020 01:31PM |
Registered: 4 years ago Posts: 17 |
bodhi Wrote:
-------------------------------------------------------
> sanchelo81,
>
> Login and,
>
>
========
moderator edit: please use code tag to post log. When you edit the post, the "Format code" button on the far right on the top row of the tetxt box ( the far left is the B for bold text).
Edited 1 time(s). Last edit at 07/09/2020 04:30PM by bodhi.
-------------------------------------------------------
> sanchelo81,
>
> Login and,
>
>
> mount > cat /etc/fstab >
Whitney # tftp
Initialize PHY s/w auto-polling
phy_id: 1c
Initialize RTL8211
phy_id: 1c
Initialize RTL8211
TFTP from server 192.168.1.1; our IP address is 192.168.1.33
Filename 'uImage'.
Load address: 0x800000
Loading: T T T T #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####
done
Bytes transferred = 3019912 (2e1488 hex)
Whitney # bootm
enter do_eth_down!!!
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.121-tommy
Created: 2018-03-18 23:01:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3019848 Bytes = 2.9 MB
Load Address: 22000000
Entry Point: 22000000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x900
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.4.121-tommy (root@debian9) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #26 SMP Sun Mar 18 23:57:36 CET 2018
CPU: ARMv6-compatible processor [410fb024] revision 4 (ARMv7), cr=00c5787d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Seagate CNS3420 NAS
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @dfbd9000 s17004 r8192 d23956 u49152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,38400 mem=512M@0x20000000 root=/dev/sda1
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513692K/524288K available (4211K kernel code, 159K rwdata, 1256K rodata, 212K init, 101K bss, 10596K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc055ef9c (5468 kB)
.init : 0xc055f000 - 0xc0594000 ( 212 kB)
.data : 0xc0594000 - 0xc05bbe10 ( 160 kB)
.bss : 0xc05bbe10 - 0xc05d5348 ( 102 kB)
Hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
NR_IRQS:16 nr_irqs:16 16
clocksource: freerun: mask: 0xffffffffffff max_cycles: 0x179dd7f66, max_idle_ns: 28210892933900 ns
smp_twd: clock not found -2
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating local timer... 347.98MHz.
Calibrating delay loop... 277.70 BogoMIPS (lpj=1388544)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Initializing cgroup subsys io
Initializing cgroup subsys devices
Initializing cgroup subsys net_cls
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x200082a0 - 0x200082fc
Brought up 2 CPUs
SMP: Total of 2 processors activated (555.41 BogoMIPS).
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
L2C: DT/platform modifies aux control register: 0x02040000 -> 0x02540000
L2C-310 cache controller enabled, 8 ways, 256 kB
L2C-310: CACHE_ID 0x410000c4, AUX_CTRL 0x06540000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
clocksource: Switched to clocksource freerun
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x78000000 (irq = 45, base_baud = 1500000) is a 16550A
loop: module loaded
mGine mflash driver, (c) 2008 mGine Co.
zram: Added device: zram0
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi host0: ahci
scsi host1: ahci
ata1: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x100 irq 65
ata2: SATA max UDMA/133 mmio [mem 0x83000000-0x83ffffff] port 0x180 irq 65
physmap platform flash device: 08000000 at 10000000
physmap-flash physmap-flash.0: map_probe failed
libphy: Fixed MDIO Bus: probed
libphy: CNS3xxx MII Bus: probed
eth0: RGMII PHY 0 on cns3xxx Switch
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
CNS3XXX Real Time Clock, (c) 2009 Cavium Networks
rtc irq:23
rtc rtc0: invalid alarm value: 1900-1-9 0:0:0
cns3xxx-rtc cns3xxx-rtc: rtc core: registered cns3xxx-rtc as rtc0
i2c /dev entries driver
adt7475 0-002e: ADT7473 device, revision 0
adt7475 0-002e: Optional features: fan4 pwm2
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
PCI-E0 uses external clock source.
ata2: SATA link down (SStatus 0 SControl 300)
PCIe: Port[0] Enable PCIe LTSSM
PCIe: Port[0] Check data link layer...
Link up.
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0xac000000-0xacffffff]
pci_bus 0000:00: root bus resource [mem 0xa0000000-0xaaffffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers disabled
PCIe map irq: 0000:01:00.00 slot 0, pin 1, irq: 61
pci 0000:00:00.0: BAR 8: assigned [mem 0xa0000000-0xa00fffff]
pci 0000:01:00.0: BAR 0: assigned [mem 0xa0000000-0xa0007fff 64bit]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0: bridge window [mem 0xa0000000-0xa00fffff]
pci 0000:00:00.0: Max Payload Size set to 128/ 128 (was 128), Max Read Rq 128
pci 0000:01:00.0: Max Payload Size set to 128/ 512 (was 128), Max Read Rq 128
pci 0000:01:00.0: enabling device (0140 -> 0142)
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
xhci_hcd 0000:01:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb1: SerialNumber: 0000:01:00.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 4.4.121-tommy xhci-hcd
usb usb2: SerialNumber: 0000:01:00.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: HPA detected: current 39070080, native 39179952
ata1.00: ATA-7: SAMSUNG HM020GI, YU100-06, max UDMA7
ata1.00: 39070080 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM020GI 0-06 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 39070080 512-byte logical blocks: (20.0 GB/18.6 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext3 filesystem) on device 8:1.
devtmpfs: mounted
Freeing unused kernel memory: 212K
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
ERROR: could not open /proc/stat: No such file or directory
findfs: unable to resolve 'LABEL=rootfs'
[warn] Files under mount point '/run' will be hidden. ... (warning).
[....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232
. ok
[....] Synthesizing the initial hotplug events...random: systemd-udevd: uninitialized urandom read (16 bytes read, 91 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 91 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 91 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 92 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 92 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 92 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 92 bits of entropy available)
random: systemd-udevd: uninitialized urandom read (16 bytes read, 92 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 96 bits of entropy available)
random: udevadm: uninitialized urandom read (16 bytes read, 96 bits of entropy available)
done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Setting hostname to 'debian'...done.
random: nonblocking pool is initialized
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Activating swap:.
Usage:
mountpoint [-qd] /path/to/directory
mountpoint -x /dev/device
Check whether a directory or file is a mountpoint.
Options:
-q, --quiet quiet mode - don't print anything
-d, --fs-devno print maj:min device number of the filesystem
-x, --devno print maj:min device number of the block device
-h, --help display this help and exit
-V, --version output version information and exit
For more details see mountpoint(1).
EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Will now check root file system:fsck from util-linux 2.29.2
[/sbin/fsck.ext3 (1) -- /run/rootdev] fsck.ext3 -y -C0 /run/rootdev
e2fsck 1.43.4 (31-Jan-2017)
/run/rootdev: clean, 11953/1221600 files, 224261/4883504 blocks
. ok
mount: can't find LABEL=rootfs
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Will now activate lvm and md swap:done.
[info] Will now check all file systems.
fsck from util-linux 2.29.2
LABEL=rootfs: nonexistent device ("nofail" fstab option may be used to skip this device)
Checking all file systems.
LABEL=rootfs is not mounted
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 LABEL=rootfs
fsck.ext3: Unable to resolve 'LABEL=rootfs'
fsck exited with status code 8
[....] File system check failed. A log is being saved in /var/log/fsck/checkfs i[FAILt location is writable. Please repair the file system manually. ... failed!
[....] A maintenance shell will now be started. CONTROL-D will terminate this sh[warnnd resume system boot. ... (warning).
Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
root@debian:~# mount
/dev/sda1 on / type ext3 (ro,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=256844k,nr_inodes=64211,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=51392k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102780k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
root@debian:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults 0 0
root@debian:~# ls
root@debian:~# exit
exit
rm: cannot remove '/tmp/.clean': Read-only file system
[ ok ] Cleaning up temporary files....
[ ok ] Will now mount local filesystems:.
[ ok ] Will now activate swapfile swap:done.
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Checking minimum space in /tmp...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables...done.
[FAIL] Initializing random number generator...failed.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
can't create /var/lib/dhcp/dhclient.eth0.leases: Read-only file system
RTNETLINK answers: Cannot assign requested address
Listening on LPF/eth0/00:00:00:00:00:00
Sending on LPF/eth0/00:00:00:00:00:00
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over eth0 interface.
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
/etc/init.d/bootlogs: 23: /etc/init.d/bootlogs: cannot create /var/log/dmesg: Read-only file system
chgrp: cannot access '/var/log/dmesg': No such file or directory
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1581 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting system message bus: dbus.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1580 (klogd)
. ok
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[ ok ] Running local boot scripts (/etc/rc.local).
Z▒▒T▒▒J
========
moderator edit: please use code tag to post log. When you edit the post, the "Format code" button on the far right on the top row of the tetxt box ( the far left is the B for bold text).
Edited 1 time(s). Last edit at 07/09/2020 04:30PM by bodhi.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 09, 2020 02:41PM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 09, 2020 04:36PM |
Admin Registered: 13 years ago Posts: 19,102 |
Since you are booting with uImage only, the fstab should be
root@debian:~# cat /etc/fstab
Becasuse you are running a kernel that I am not familiar with, I am not sure why it freezes. Changing fstab like I suggest might fix it, or might not. But at least it will allow the rootfs to be mounted properly.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
root@debian:~# cat /etc/fstab
# /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> /dev/sda1 / ext3 noatime,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults 0 0
Quote
also freezes at the end.
Quote
Linux version 4.4.121-tommy (root@debian9) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #26 SMP Sun Mar 18 23:57:36 CET 2018
Becasuse you are running a kernel that I am not familiar with, I am not sure why it freezes. Changing fstab like I suggest might fix it, or might not. But at least it will allow the rootfs to be mounted properly.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 17, 2020 12:57PM |
Registered: 4 years ago Posts: 17 |
bodhi Wrote:
-------------------------------------------------------
> Since you are booting with uImage only, the fstab
> should be
>
> root@debian:~# cat /etc/fstab
>
>
>
> Becasuse you are running a kernel that I am not
> familiar with, I am not sure why it freezes.
> Changing fstab like I suggest might fix it, or
> might not. But at least it will allow the rootfs
> to be mounted properly.
Well, for now I need the correct dump of SPI FLASH because printenv gives out only a couple of lines from which it is clear that not everything is registered. I wrote to many people about this topic and Mark promised to help with the dump. Then it will be easier for me. With your help, I have already been able to run the kernel very well, so the problem is soft in flash memory.
-------------------------------------------------------
> Since you are booting with uImage only, the fstab
> should be
>
> root@debian:~# cat /etc/fstab
>
> # /etc/fstab: static file system information. > # > # <file system> <mount point> <type> <options> > <dump> <pass> > /dev/sda1 / ext3 > noatime,errors=remount-ro 0 1 > tmpfs /tmp tmpfs defaults > 0 0 >>
>
>Quote
also freezes at the end.
>
>Quote
Linux version 4.4.121-tommy (root@debian9)
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) )
> #26 SMP Sun Mar 18 23:57:36 CET 2018
> Becasuse you are running a kernel that I am not
> familiar with, I am not sure why it freezes.
> Changing fstab like I suggest might fix it, or
> might not. But at least it will allow the rootfs
> to be mounted properly.
Well, for now I need the correct dump of SPI FLASH because printenv gives out only a couple of lines from which it is clear that not everything is registered. I wrote to many people about this topic and Mark promised to help with the dump. Then it will be easier for me. With your help, I have already been able to run the kernel very well, so the problem is soft in flash memory.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 17, 2020 03:41PM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
> Well, for now I need the correct dump of SPI FLASH
> because printenv gives out only a couple of lines
> from which it is clear that not everything is
> registered. I wrote to many people about this
> topic and Mark promised to help with the dump.
> Then it will be easier for me. With your help, I
> have already been able to run the kernel very
> well, so the problem is soft in flash memory.
Yes. So you should wait for Mark (I don't have this box).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Well, for now I need the correct dump of SPI FLASH
> because printenv gives out only a couple of lines
> from which it is clear that not everything is
> registered. I wrote to many people about this
> topic and Mark promised to help with the dump.
> Then it will be easier for me. With your help, I
> have already been able to run the kernel very
> well, so the problem is soft in flash memory.
Yes. So you should wait for Mark (I don't have this box).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 17, 2020 04:38PM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 18, 2020 03:26PM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package July 19, 2020 04:34PM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
Congrats! and thanks for posting the stock u-boot. It will be handy for someone someday.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Congrats! and thanks for posting the stock u-boot. It will be handy for someone someday.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 09:48AM |
Registered: 4 years ago Posts: 4 |
@sanchelo81
My English is not good
I have the same problem as you. Can you use the mixed firmware of linux-4.4.121-tommy and debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi? How to solve it? In addition, can the network card get the IP assigned by DHCP normally?
I have also tried to modify / etc / fstab in accordance with Bodhi's method and modify /etc/lc.local In the first line add exit 0;The results are the same.
Please help me reply
@Bodhi I tried to use debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi to start, but it was stuck in "loading kernel image..." and could not continue,please help me.
THK
Edited 1 time(s). Last edit at 10/21/2020 09:52AM by tang.
My English is not good
I have the same problem as you. Can you use the mixed firmware of linux-4.4.121-tommy and debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi? How to solve it? In addition, can the network card get the IP assigned by DHCP normally?
I have also tried to modify / etc / fstab in accordance with Bodhi's method and modify /etc/lc.local In the first line add exit 0;The results are the same.
Please help me reply
@Bodhi I tried to use debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi to start, but it was stuck in "loading kernel image..." and could not continue,please help me.
THK
Edited 1 time(s). Last edit at 10/21/2020 09:52AM by tang.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 10:12AM |
Registered: 4 years ago Posts: 17 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 03:54PM |
Admin Registered: 13 years ago Posts: 19,102 |
sanchelo81,
> Я поросто востановил свой
> Nas родной прошивеой, вы
> хотите вернуть родную
> прошивку?
Please translate it to English before posting.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Я поросто востановил свой
> Nas родной прошивеой, вы
> хотите вернуть родную
> прошивку?
Please translate it to English before posting.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 07:40PM |
Registered: 4 years ago Posts: 4 |
sanchelo81 Wrote:
-------------------------------------------------------
> Я поросто востановил свой
> Nas родной прошивеой, вы
> хотите вернуть родную
> прошивку?
THK reply
I want to use debian-4.14.24 firmware replace linux-2.6.35.13-cavm1.whitney firmware;
Because Linux-2.6.35.13-cavm1.whitney firmware has two big bug on my 4bay-NAS:
1: CNS3420 CPU is dual core, but only single core can be used in this firmware
2: rsync is very, very slow. run "rsync -aP /shares/temp/a /shares/back/a" is only 2Mb / s. if use "cp", it can reach 60MB / s
So I want to try debian-4.14.24, but "debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi" can't started. stuck in "loading kernel image...", and then I used "cp ./linux-4.4.121-tommy/uImage ./debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi/boot/uImage", can be started, but stuck in"[ ok ] Running local boot scripts (/etc/rc.local).". So how do you solve this problem?
now,do you use debain firmware or linux-2.6.35.13 firmware?
Edited 3 time(s). Last edit at 10/22/2020 01:57AM by tang.
-------------------------------------------------------
> Я поросто востановил свой
> Nas родной прошивеой, вы
> хотите вернуть родную
> прошивку?
THK reply
I want to use debian-4.14.24 firmware replace linux-2.6.35.13-cavm1.whitney firmware;
Because Linux-2.6.35.13-cavm1.whitney firmware has two big bug on my 4bay-NAS:
1: CNS3420 CPU is dual core, but only single core can be used in this firmware
2: rsync is very, very slow. run "rsync -aP /shares/temp/a /shares/back/a" is only 2Mb / s. if use "cp", it can reach 60MB / s
So I want to try debian-4.14.24, but "debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi" can't started. stuck in "loading kernel image...", and then I used "cp ./linux-4.4.121-tommy/uImage ./debian-4.14.24-cns3xxx-tld-1-rootfs-bodhi/boot/uImage", can be started, but stuck in"[ ok ] Running local boot scripts (/etc/rc.local).". So how do you solve this problem?
now,do you use debain firmware or linux-2.6.35.13 firmware?
Edited 3 time(s). Last edit at 10/22/2020 01:57AM by tang.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 07:48PM |
Registered: 4 years ago Posts: 4 |
bodhi Wrote:
-------------------------------------------------------
> sanchelo81,
>
> > Я поросто востановил свой
> > Nas родной прошивеой, вы
> > хотите вернуть родную
> > прошивку?
>
> Please translate it to English before posting.
@bodhi
I use "Linux-4.4.121-tommy/uImage + Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start faild;
error log "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
I want use your's uImage-4.14.24 or uImage-3.8.15 start my NAS,please help me.
-------------------------------------------------------
> sanchelo81,
>
> > Я поросто востановил свой
> > Nas родной прошивеой, вы
> > хотите вернуть родную
> > прошивку?
>
> Please translate it to English before posting.
@bodhi
I use "Linux-4.4.121-tommy/uImage + Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start faild;
error log "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
I want use your's uImage-4.14.24 or uImage-3.8.15 start my NAS,please help me.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 21, 2020 09:39PM |
Admin Registered: 13 years ago Posts: 19,102 |
tang,
> @bodhi
> I use "Linux-4.4.121-tommy/uImage +
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start
> faild;
> error log
> "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
>
> I want use your's uImage-4.14.24 or uImage-3.8.15
> start my NAS,please help me.
That's a typical problem with running a kernel uImage that was not installed on a different rootfs. Since the rootfs was installed with kernel 4.14.24-cns3xxxx-tld-1, the rootfs has some init scripts that conform to that kernel, but not to kernel Linux-4.4.121-tommy (this kernel is much older than the kernel 4.14.24-cns3xxxx-tld-1).
I've looked at your log. It stuck at the point where the kernel was trying to mount the rootfs (through some init scripts).
There are 2 approaches to solve this problem.
1. So to make it consistent, you should try to use chroot to install the kernel Linux-4.4.121-tommy on the rootfs Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. When you run dpkg to install the kernel, it will create some sysvinit scripts for that kernel version, and during booting, those sysvinit scripts will mount the rootfs properly.
or
2. Instead of using Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. you can try using the older rootfs: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
https://forum.doozan.com/read.php?2,12096,12098#msg-12098
Scroll down to:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> @bodhi
> I use "Linux-4.4.121-tommy/uImage +
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start
> faild;
> error log
> "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
>
> I want use your's uImage-4.14.24 or uImage-3.8.15
> start my NAS,please help me.
That's a typical problem with running a kernel uImage that was not installed on a different rootfs. Since the rootfs was installed with kernel 4.14.24-cns3xxxx-tld-1, the rootfs has some init scripts that conform to that kernel, but not to kernel Linux-4.4.121-tommy (this kernel is much older than the kernel 4.14.24-cns3xxxx-tld-1).
I've looked at your log. It stuck at the point where the kernel was trying to mount the rootfs (through some init scripts).
[ ok ] Running local boot scripts (/etc/rc.local).
There are 2 approaches to solve this problem.
1. So to make it consistent, you should try to use chroot to install the kernel Linux-4.4.121-tommy on the rootfs Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. When you run dpkg to install the kernel, it will create some sysvinit scripts for that kernel version, and during booting, those sysvinit scripts will mount the rootfs properly.
or
2. Instead of using Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. you can try using the older rootfs: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
https://forum.doozan.com/read.php?2,12096,12098#msg-12098
Scroll down to:
Quote
Updated 20 Feb 2016:
This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.
Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:
- tarball size: 137M
- install size: 398M
- a basic jessie rootfs.
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root
Download at Dropbox:
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
md5:
9f957e1dc5a36f90a285ab4615cb02fd
sha256:
d33349118e34bd078ca635cd2d6776f3e312accfc77d29da5870b9980add5c36
And remember to check the hash of what you download, as always.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 25, 2020 05:18AM |
Registered: 4 years ago Posts: 4 |
bodhi Wrote:
-------------------------------------------------------
> tang,
>
> > @bodhi
> > I use "Linux-4.4.121-tommy/uImage +
> >
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start
> > faild;
> > error log
> >
> "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
> >
> > I want use your's uImage-4.14.24 or
> uImage-3.8.15
> > start my NAS,please help me.
>
> That's a typical problem with running a kernel
> uImage that was not installed on a different
> rootfs. Since the rootfs was installed with kernel
> 4.14.24-cns3xxxx-tld-1, the rootfs has some init
> scripts that conform to that kernel, but not to
> kernel Linux-4.4.121-tommy (this kernel is much
> older than the kernel 4.14.24-cns3xxxx-tld-1).
>
> I've looked at your log. It stuck at the point
> where the kernel was trying to mount the rootfs
> (through some init scripts).
>
>
> There are 2 approaches to solve this problem.
>
> 1. So to make it consistent, you should try to use
> chroot to install the kernel Linux-4.4.121-tommy
> on the rootfs
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. When
> you run dpkg to install the kernel, it will create
> some sysvinit scripts for that kernel version, and
> during booting, those sysvinit scripts will mount
> the rootfs properly.
>
> or
>
> 2. Instead of using
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. you
> can try using the older rootfs:
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
>
> https://forum.doozan.com/read.php?2,12096,12098#msg-12098
>
> Scroll down to:
>
>
I tried uimage.4.4.121-tommy uimage + debian-4.4.0-kirkwood-tld-1-rootfs-bodhi, but I couldn't. This time, I was stuck in "starting busybox 'klogd implementation: klogdstarting / SBIN / klogd...";
Although I would like to replace Seagate linux-2.6.35.13-cavm1.whitney firmware with Debian firmware to solve two big bug I want to solve:
1: CNS3420 CPU is dual core, but only single core can be used in seagate linux-2.6.35.13-cavm1.whitney
2: rsync is very, very slow. run "rsync -aP /shares/temp/a /shares/back/a" is only 2Mb / s. if use "cp", it can reach 60MB / s
However, I can only give up Debian temporarily, unless there is a supporting uimage + rootfs;
Thanks for your help
-------------------------------------------------------
> tang,
>
> > @bodhi
> > I use "Linux-4.4.121-tommy/uImage +
> >
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi"start
> > faild;
> > error log
> >
> "https://forum.doozan.com/file.php?2,file=4919,filename=Linux-4.4.121-tommy_uImage_Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.log";
> >
> > I want use your's uImage-4.14.24 or
> uImage-3.8.15
> > start my NAS,please help me.
>
> That's a typical problem with running a kernel
> uImage that was not installed on a different
> rootfs. Since the rootfs was installed with kernel
> 4.14.24-cns3xxxx-tld-1, the rootfs has some init
> scripts that conform to that kernel, but not to
> kernel Linux-4.4.121-tommy (this kernel is much
> older than the kernel 4.14.24-cns3xxxx-tld-1).
>
> I've looked at your log. It stuck at the point
> where the kernel was trying to mount the rootfs
> (through some init scripts).
>
>
> [ ok ] Running local boot scripts > (/etc/rc.local). >>
> There are 2 approaches to solve this problem.
>
> 1. So to make it consistent, you should try to use
> chroot to install the kernel Linux-4.4.121-tommy
> on the rootfs
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. When
> you run dpkg to install the kernel, it will create
> some sysvinit scripts for that kernel version, and
> during booting, those sysvinit scripts will mount
> the rootfs properly.
>
> or
>
> 2. Instead of using
> Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi. you
> can try using the older rootfs:
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
>
> https://forum.doozan.com/read.php?2,12096,12098#msg-12098
>
> Scroll down to:
>
>
Quote
Updated 20 Feb 2016:
>
> This
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> is to keep in sync with kernel
> Linux-4.4.0-kirkwood-tld-1.
>
> Basic minimal Debian Kirkwood rootfs for most
> Kirwood plugs:
>
> - tarball size: 137M
> - install size: 398M
> - a basic jessie rootfs.
> - The init system used in this rootfs is sysvinit
> . To boot with systemd, see note 2 below.
> - Installed packages: nano, avahi, ntp,
> busybox-syslogd (log to RAM), htop,
> isc-dhcp-client, dialog, bzip2, nfs server/client,
> iperf, ethtool, sysvinit-core, sysvinit, and
> sysvinit-utils.
> - see LED controls in /etc/rc.local, and
> /etc/init.d/halt
> - see some useful aliases in /root/.profile
> - root password: root
>
> Download at Dropbox:
>
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> md5:
> 9f957e1dc5a36f90a285ab4615cb02fd
> sha256:
> d33349118e34bd078ca635cd2d6776f3e312accfc77d29da5870b9980add5c36
>
>
> And remember to check the hash of what you
> download, as always.
I tried uimage.4.4.121-tommy uimage + debian-4.4.0-kirkwood-tld-1-rootfs-bodhi, but I couldn't. This time, I was stuck in "starting busybox 'klogd implementation: klogdstarting / SBIN / klogd...";
Although I would like to replace Seagate linux-2.6.35.13-cavm1.whitney firmware with Debian firmware to solve two big bug I want to solve:
1: CNS3420 CPU is dual core, but only single core can be used in seagate linux-2.6.35.13-cavm1.whitney
2: rsync is very, very slow. run "rsync -aP /shares/temp/a /shares/back/a" is only 2Mb / s. if use "cp", it can reach 60MB / s
However, I can only give up Debian temporarily, unless there is a supporting uimage + rootfs;
Thanks for your help
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package October 25, 2020 05:01PM |
Admin Registered: 13 years ago Posts: 19,102 |
tang,
> I tried uimage.4.4.121-tommy uimage +
> debian-4.4.0-kirkwood-tld-1-rootfs-bodhi, but I
> couldn't. This time, I was stuck in "starting
> busybox 'klogd implementation: klogdstarting /
> SBIN / klogd...";
OK so the rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi did not work either. This is most likely due to the fact that kernel 4.4.121-tommy is too different from the kernel 4.4.0-kirkwood-tld-1.
So the other alternative is to chroot into the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and then install the kernel 4.4.121-tommy. You need to learn how to do this process if you're not familiar with chroot.
1. Mount the USB that contains the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on another Linux box. If this Linux host is an ARM box, it is quite straight forward. If this Linux host is a Intel x86 box then some extra step needed (since it is a different arcitecture from the ARM rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2).
2. chroot into the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
3. Install kernel 4.4.121-tommy using dpkg command. This is so that the rootfs will be populated with init scripts and modules for kernel 4.4.121-tommy properly.
====
So yo answer the question, you can boot rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with kernel 4.4.121-tommy trying the above 3 steps.
If the above is a little bit too much to do for you at this moment, you might want to wait until I have some free time to go back to this project (no promise when can I do that).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I tried uimage.4.4.121-tommy uimage +
> debian-4.4.0-kirkwood-tld-1-rootfs-bodhi, but I
> couldn't. This time, I was stuck in "starting
> busybox 'klogd implementation: klogdstarting /
> SBIN / klogd...";
OK so the rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi did not work either. This is most likely due to the fact that kernel 4.4.121-tommy is too different from the kernel 4.4.0-kirkwood-tld-1.
So the other alternative is to chroot into the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and then install the kernel 4.4.121-tommy. You need to learn how to do this process if you're not familiar with chroot.
1. Mount the USB that contains the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on another Linux box. If this Linux host is an ARM box, it is quite straight forward. If this Linux host is a Intel x86 box then some extra step needed (since it is a different arcitecture from the ARM rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2).
2. chroot into the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2.
3. Install kernel 4.4.121-tommy using dpkg command. This is so that the rootfs will be populated with init scripts and modules for kernel 4.4.121-tommy properly.
====
So yo answer the question, you can boot rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with kernel 4.4.121-tommy trying the above 3 steps.
If the above is a little bit too much to do for you at this moment, you might want to wait until I have some free time to go back to this project (no promise when can I do that).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package January 28, 2021 04:32AM |
Registered: 3 years ago Posts: 5 |
Hello. I have been watching this thread for a few years, and finally gotten around to playing with this.
The "freeze" after running rc.local is simply that in inittab of Bodhi's rootfs, a getty command is issued, at a baud rate of 115200. So, to fix this, set you serial speed to 115.200 at this point, in order to log in. Then, you can modify inittab (the last line), so you can stick with 38400, which is the default baud rate of this board.
The "freeze" after running rc.local is simply that in inittab of Bodhi's rootfs, a getty command is issued, at a baud rate of 115200. So, to fix this, set you serial speed to 115.200 at this point, in order to log in. Then, you can modify inittab (the last line), so you can stick with 38400, which is the default baud rate of this board.
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package January 28, 2021 04:16PM |
Admin Registered: 13 years ago Posts: 19,102 |
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package February 16, 2021 09:36AM |
Registered: 3 years ago Posts: 5 |
I have started playing a bit with this now. I have combined Tommy's excellent work with the GPL'ed sources for Seagate NAS (kernel version 2.6.35) over to a 4.19.99 kernel. Basically, I have the same functionality as Tommy at the moment.
I also dissected the uBoot image that ships stock with the device. In addition to the kernel, it seems to contain 7 .crt files (which openssl cannot open, so they are likely not certificates), and the initrd being used. -So, quite obviously, the uImage containes BOTH the zImage and the initrd, but these have been concatenated before running the mkimage command. mkimage only sees the uImage containig a single file.
Would you know how to "piggyback" initrds ontp the zImage like that?
I have been able to make the second NIC port visible, but unfortunately, I am still struggling to make it actually pass any data through...
I also dissected the uBoot image that ships stock with the device. In addition to the kernel, it seems to contain 7 .crt files (which openssl cannot open, so they are likely not certificates), and the initrd being used. -So, quite obviously, the uImage containes BOTH the zImage and the initrd, but these have been concatenated before running the mkimage command. mkimage only sees the uImage containig a single file.
Would you know how to "piggyback" initrds ontp the zImage like that?
I have been able to make the second NIC port visible, but unfortunately, I am still struggling to make it actually pass any data through...
|
Re: (WIP) Linux Kernel and rootfs 4.14.24 for Seagate Business Storage NAS (CNS3xxx) package February 16, 2021 04:38PM |
Admin Registered: 13 years ago Posts: 19,102 |
oklona,
> Would you know how to "piggyback" initrds ontp the
> zImage like that?
This is easy to do. I usually don't provide this in my kernel/rootfs instruction because it would make kernel upgrade a bit more works in maintenance. And it is less flexible then booting with separate DTB.
However, in some special cases, you need to do this. Perhaps this is the case!
UPDATE:
I posted the command below in a short How-To so it can be added to the Wiki.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/16/2021 10:12PM by bodhi.
> Would you know how to "piggyback" initrds ontp the
> zImage like that?
This is easy to do. I usually don't provide this in my kernel/rootfs instruction because it would make kernel upgrade a bit more works in maintenance. And it is less flexible then booting with separate DTB.
However, in some special cases, you need to do this. Perhaps this is the case!
UPDATE:
I posted the command below in a short How-To so it can be added to the Wiki.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/16/2021 10:12PM by bodhi.
