Welcome! Log In Create A New Profile

Advanced

Linux Kernel 4.19.0 Kirkwood package and Debian rootfs

Posted by bodhi 
Damien Wrote:
> Well, problem solved. Module driver now works on
> both 3.18-5 and 4.4.0 with Jessie rootfs. At
> least, that`s what 1 day of testing says. I had a
> bad .conf file (copied there by mistake) and it
> seems it was enough to screw up everything - weird
> thing is, I never saw any error message until I
> tried to compile the module on 4.1.0 (libkmod
> error). Sometimes I just hate Linux.

If anyone`s interested, the .conf file error I was talking about was a bad file located in /etc/modprobe.d/
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
February 20, 2016 05:40PM
I've uploaded the latest rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
February 23, 2016 04:10PM
Thanks bodhi!
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
February 24, 2016 04:17PM
I've move sebr's issue to a new thread below.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 03, 2016 11:47AM
it there a way to upgrade rootfs without reinstall everything?

I was trying to build cryptodev module, which asks for 4.4 linux-headers which I don't have. Would updating rootfs fix that or I should simply use the 3.16 linux-header (I currently have) to build that?

EDIT:
Just realized that the 4.4 linux-header is included in the 4.4 kernel package. So it solved the second question. I am still not clear about the first one. Should I update my rootfs to 4.4 and is there a way to do it without reinstall everything?
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 03, 2016 01:34PM
auzn,

You can update the kernel to 4.4. There is no need to replace rootfs. In the 1st post scroll down to previous release dates:

Quote

Updated 31 Jan 2015:

Kernel linux-4.4.0-kirkwood-tld-1 package has been uploaded. The following features were updated/added:

Beware that it will be a massive change from from kernel 3.16 on your rootfs. So back up your rootfs first!

-bodhi
===========================
Forum Wiki
bodhi's corner
I haven't used my NSA-325 v1 in a while and when I went to boot it up with 2 spare 3TB sata drives got my hands on I found that the usb thumb drive was not good anymore so i got my hands on a new one (same model 6gb sandisk cruzer fit) and loaded created a single new ext3 partition with label "rootfs" and plugged it into the same usb port as the old failed sandisk cruzer fit. It starts the boot then reboots while trying to "sd 2:0:0:0: [sdb] Attached SCSI removable disk" sdb is my sandisk cruzer fit".

I have never updated uboot ever on this device, but was thinking of attempting to update uboot but not sure I really need to give that I have serial/tty access to the device.

the old failed cruzer fit I had I believe had your 3.16 kernel on it.

There is no data on either the cruzer fit or the two 3TB sata drives that inside the NSA325.

My question I guess is why is it rebooting and how can I fix it?

below is the serial output while it boots up until it reboots.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Sep 16 2011 - 17:51:53) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFF00

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000   size 512MB
DRAM Total size 512MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled


USB 0: host mode
        [BlueDBG] reseting SoC Pex[0]  0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
        [BlueDBG] reseting SoC Pex[1]  0 ...
        [BlueDBG] reseting SoC Pex[1]  1 ...
        [BlueDBG] reseting SoC Pex[1]  2 ...
        [BlueDBG] reseting SoC Pex[1]  3 ...
        [BlueDBG] reseting SoC Pex[1]  4 ...
        [BlueDBG] reseting SoC Pex[1]  5 ...
        [BlueDBG] reseting SoC Pex[1]  6 ...
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
........................................................................................................

3169424 bytes read
....
.
......
............
.........................
...................................................
......................................................................................................
.................................................................................................................................................................................................................
..............................................................................................................................................................................................................................................................................................

7179935 bytes read
## Booting image at 02000000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-03-04   5:53:56 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3169360 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes =  6.8 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: ZyXEL NSA325
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c08a06b4, node_mem_map dfbf9000
[    0.000000]   Normal zone: 1024 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200=mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/sdb1 rw rootwait loglevel=8
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 503456K/524288K available (6007K kernel code, 573K rwdata, 1992K rodata, 296K init, 312K bss, 20832K 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 : 0xe0800000 - 0xff800000   ( 496 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07d7ef4   (8000 kB)
[    0.000000]       .init : 0xc07d8000 - 0xc0822000   ( 296 kB)
[    0.000000]       .data : 0xc0822000 - 0xc08b169c   ( 574 kB)
[    0.000000]        .bss : 0xc08b169c - 0xc08ff9d0   ( 313 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000006] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000262] Console: colour dummy device 80x30
[    0.000286] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[    0.090063] pid_max: default: 32768 minimum: 301
[    0.090150] Security Framework initialized
[    0.090208] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090224] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090837] Initializing cgroup subsys io
[    0.090864] Initializing cgroup subsys devices
[    0.090882] Initializing cgroup subsys freezer
[    0.090908] Initializing cgroup subsys net_cls
[    0.090974] CPU: Testing write buffer coherency: ok
[    0.091327] Setting up static identity map for 0x8200 - 0x8258
[    0.091572] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[    0.094363] devtmpfs: initialized
[    0.099081] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.099438] prandom: seed boundary self test passed
[    0.102279] prandom: 100 self tests passed
[    0.102307] pinctrl core: initialized pinctrl subsystem
[    0.103378] NET: Registered protocol family 16
[    0.103705] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.130080] cpuidle: using governor ladder
[    0.160078] cpuidle: using governor menu
[    0.160412] Feroceon L2: Enabling L2
[    0.160446] Feroceon L2: Cache support initialised.
[    0.160750] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.165161] No ATAGs?
[    0.191251] vgaarb: loaded
[    0.191542] usbcore: registered new interface driver usbfs
[    0.191605] usbcore: registered new interface driver hub
[    0.191653] usbcore: registered new device driver usb
[    0.192520] clocksource: Switched to clocksource orion_clocksource
[    0.235239] NET: Registered protocol family 2
[    0.235883] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.235939] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.235990] TCP: Hash tables configured (established 4096 bind 4096)
[    0.236040] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.236061] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.236221] NET: Registered protocol family 1
[    0.236542] RPC: Registered named UNIX socket transport module.
[    0.236551] RPC: Registered udp transport module.
[    0.236556] RPC: Registered tcp transport module.
[    0.236562] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.236578] PCI: CLS 0 bytes, default 32
[    0.236785] Unpacking initramfs...
[    0.715028] Freeing initrd memory: 7012K (c1100000 - c17d9000)
[    0.715143] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.716031] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.716090] audit: initializing netlink subsys (disabled)
[    0.716138] audit: type=2000 audit(0.710:1): initialized
[    0.716417] Initialise system trusted keyring
[    0.716741] zbud: loaded
[    0.716973] VFS: Disk quotas dquot_6.6.0
[    0.717022] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.717454] NFS: Registering the id_resolver key type
[    0.717484] Key type id_resolver registered
[    0.717491] Key type id_legacy registered
[    0.717511] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.717522] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.717703] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.718117] Key type big_key registered
[    0.733433] Key type asymmetric registered
[    0.733450] Asymmetric key parser 'x509' registered
[    0.733524] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.733540] io scheduler noop registered
[    0.733552] io scheduler deadline registered
[    0.733599] io scheduler cfq registered (default)
[    0.734662] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.735195] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    0.735515] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    0.736124] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.736139] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.736149] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.736159] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.736169] pci_bus 0000:00: scanning bus
[    0.736195] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[    0.736234] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x40
[    0.736432] pci_bus 0000:00: fixups for bus
[    0.736444] PCI: bus0: Fast back to back transfers disabled
[    0.736455] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[    0.736464] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.736476] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[    0.736587] pci_bus 0000:01: scanning bus
[    0.736626] pci 0000:01:00.0: [1033:0194] type 00 class 0x0c0330
[    0.736681] pci 0000:01:00.0: reg 0x10: [mem 0x90000000-0x90001fff 64bit]
[    0.736753] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x40
[    0.736816] pci 0000:01:00.0: PME# supported from D0 D3hot
[    0.736829] pci 0000:01:00.0: PME# disabled
[    0.752579] pci_bus 0000:01: fixups for bus
[    0.752595] PCI: bus1: Fast back to back transfers disabled
[    0.752604] pci_bus 0000:01: bus scan returning with max=01
[    0.752616] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.752627] pci_bus 0000:00: bus scan returning with max=01
[    0.752640] pci 0000:00:01.0: fixup irq: got 0
[    0.752648] pci 0000:00:01.0: assigning IRQ 00
[    0.752696] pci 0000:01:00.0: fixup irq: got 83
[    0.752706] pci 0000:01:00.0: assigning IRQ 83
[    0.752734] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    0.752749] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit]
[    0.752769] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.752781] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.752848] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[    0.752867] pcieport 0000:00:01.0: enabling bus mastering
[    0.752903] pci 0000:01:00.0: calling quirk_usb_early_handoff+0x0/0x630
[    0.752916] pci 0000:00:01.0: enabling bus mastering
[    0.753158] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.793048] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.793237] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.833038] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.833422] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.834523] console [ttyS0] disabled
[    0.834573] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    1.682922] console [ttyS0] enabled
[    1.687469] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[    1.693881] nand: Samsung NAND 128MiB 3,3V 8-bit
[    1.698520] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.706143] Scanning device for bad blocks
[    1.792307] Bad eraseblock 796 at 0x000006380000
[    1.801430] Bad eraseblock 840 at 0x000006900000
[    1.829865] libphy: Fixed MDIO Bus: probed
[    1.834330] libphy: orion_mdio_bus: probed
[    1.842056] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.849363] mv643xx_eth: Set the PHY to fix link down
[    1.854939] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:50:43:00:02:02
[    1.864018] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.870594] ehci-pci: EHCI PCI platform driver
[    1.875156] ehci-orion: EHCI orion driver
[    1.879322] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.884875] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.892700] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    1.912548] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.918762] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.925601] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.932867] usb usb1: Product: EHCI Host Controller
[    1.937761] usb usb1: Manufacturer: Linux 4.4.0-kirkwood-tld-1 ehci_hcd
[    1.944421] usb usb1: SerialNumber: f1050000.ehci
[    1.949722] hub 1-0:1.0: USB hub found
[    1.953556] hub 1-0:1.0: 1 port detected
[    1.957990] xhci_hcd 0000:01:00.0: enabling bus mastering
[    1.963464] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.968727] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.976483] xhci_hcd 0000:01:00.0: hcc params 0x014042c3 hci version 0x96 quirks 0x00000004
[    1.984893] xhci_hcd 0000:01:00.0: enabling Mem-Wr-Inval
[    1.990399] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    1.997234] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.004503] usb usb2: Product: xHCI Host Controller
[    2.009397] usb usb2: Manufacturer: Linux 4.4.0-kirkwood-tld-1 xhci-hcd
[    2.016055] usb usb2: SerialNumber: 0000:01:00.0
[    2.021258] hub 2-0:1.0: USB hub found
[    2.025088] hub 2-0:1.0: 2 ports detected
[    2.029539] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    2.034842] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    2.042350] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.050647] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[    2.057551] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.064821] usb usb3: Product: xHCI Host Controller
[    2.069721] usb usb3: Manufacturer: Linux 4.4.0-kirkwood-tld-1 xhci-hcd
[    2.076381] usb usb3: SerialNumber: 0000:01:00.0
[    2.081570] hub 3-0:1.0: USB hub found
[    2.085404] hub 3-0:1.0: 2 ports detected
[    2.090183] mousedev: PS/2 mouse device common for all mice
[    2.096116] i2c /dev entries driver
[    2.100224] rtc-pcf8563 0-0051: chip found, driver version 0.4.4
[    2.112082] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[    2.121419] hidraw: raw HID events driver (C) Jiri Kosina
[    2.127318] drop_monitor: Initializing network drop monitor service
[    2.133831] NET: Registered protocol family 17
[    2.138505] Key type dns_resolver registered
[    2.143482] registered taskstats version 1
[    2.147632] Loading compiled-in X.509 certificates
[    2.152480] zswap: loaded using pool lzo/zbud
[    2.163698] Key type encrypted registered
[    2.169451] rtc-pcf8563 0-0051: setting system clock to 2016-03-05 04:52:08 UTC (1457153528)
[    2.178921] PM: Hibernation image not present or could not be loaded.
[    2.187084] Freeing unused kernel memory: 296K (c07d8000 - c0822000)
Loading, please wait...
[    2.253205] systemd-udevd[81]: starting version 215
[    2.259689] random: systemd-udevd urandom read with 5 bits of entropy available
[    2.272611] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.400674] SCSI subsystem initialized
[    2.444347] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.451099] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.466040] libata version 3.00 loaded.
[    2.471428] sata_mv f1080000.sata: version 1.28
[    2.476104] usb 1-1: Product: USB2.0 Hub
[    2.480919] hub 1-1:1.0: USB hub found
[    2.487741] hub 1-1:1.0: 4 ports detected
[    2.522277] sata_mv f1080000.sata: slots 32 ports 2
[    2.558278] scsi host0: sata_mv
[    2.572638] scsi host1: sata_mv
[    2.576051] ata1: SATA max UDMA/133 irq 32
[    2.580164] ata2: SATA max UDMA/133 irq 32
[    2.772543] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[    2.883455] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5571
[    2.890373] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.897742] usb 1-1.2: Product: Cruzer Fit
[    2.901854] usb 1-1.2: Manufacturer: SanDisk
[    2.906171] usb 1-1.2: SerialNumber: 4C530010550725103025
[    2.919148] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[    2.925810] scsi host2: usb-storage 1-1.2:1.0
[    2.931533] usbcore: registered new interface driver usb-storage
[    2.939962] usbcore: registered new interface driver uas
[    3.102561] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    3.142583] ata1.00: ATA-9: WDC WD30EFRX-68AX9N0, 80.00A80, max UDMA/133
[    3.149311] ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    3.192585] ata1.00: configured for UDMA/133
[    3.212903] scsi 0:0:0:0: Direct-Access     ATA      WDC WD30EFRX-68A 0A80 PQ: 0 ANSI: 5
[    3.924396] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.27 PQ: 0 ANSI: 6
[    3.938841] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    3.948262] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    3.953644] sd 2:0:0:0: [sdb] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
[    3.961556] sd 0:0:0:0: [sda] Write Protect is off
[    3.966502] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.971752] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.980943] sd 2:0:0:0: [sdb] Write Protect is off
[    3.987510] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[    3.993363] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    4.005471] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.017058]  sdb: sdb1
[    4.022617] sd 2:0:0:0: [sdb] Attached SCSI removable disk
ü

uboot config

Marvell>> printenv
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=AA03
PRODUCT_NAME=NSA-325
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethaddr=00:50:43:00:02:02
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
arcNumber=4495
to_linux="setenv mainlineLinux yes
bootcmd='run bootcmd_linux'
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /boot/uImage; ext2load usb 0:1 0x01100000 /boot/uInitrd; bootm $(loadaddr) 0x01100000
bootargs=console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set=bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
bootargs_usb=setenv=bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
bootargs_linux=console=ttyS0,115200=mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/sdb1 rw rootwait loglevel=8
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
kernel_addr=0x4640000
pcieTune=no
pcieTune1=no



Edited 3 time(s). Last edit at 03/05/2016 01:22AM by SomeoneOnLine.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 05, 2016 01:30AM
SomeoneOnLine,

This is the NSA325 watchdog that killed your kernel and caused the reboot. To boot with stock u-boot, you have to use kernel 3.16 .0-kirkwood-tld-2 or earlier. Since the new u-boot killed the watchdog, there is no need for the kernel to kill it anymore. Hence the logic that does that in the kernel was removed since 3.16 .0-kirkwood-tld-3. This was to avoid the watchdog "toggling" problem that some uses seem to have experienced.

It was stated in the 1st post.

Quote

Updated 28 Sept 2014:

Kernel 3.16.0-kirkwood-tld-3 package was uploaded. The only change in this version from 3.16.0-kirkwood-tld-2 is to incorporate the fix for the NSA325 watchdog.

NOTE: for NSA325, don't install this kernel if you still have the stock u-boot. This kernel will not kill the watchdog by itself, it is assumed that the new u-boot was already installed and already turned off the watchdog during boot.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 05, 2016 03:31PM
I've splitted Pld posts to their own topics.

Please make a new thread for separate general problem or contributing tips. This thread is mainly for problem specific to this kernel/rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner
pld
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 10, 2016 09:31AM
Hi there

There is a bug in the kernel. After setting MTD_NAND_ORION=m I get:
[    5.649977] ------------[ cut here ]------------
[    5.654625] kernel BUG at drivers/mtd/nand/nand_base.c:4416!
[    5.660309] Internal error: Oops - BUG: 0 [#1] PREEMPT ARM
[    5.665821] Modules linked in: orion_nand(+) gpio_keys ledtrig_heartbeat leds_gpio led_class ext2 mbcache sd_mod sata_mv libata fixed scsi_mod uio_pdrv_genirq uio
[    5.680527] CPU: 0 PID: 329 Comm: udevd Not tainted 4.4.3-tld-1 #2
[    5.686730] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    5.693020] task: ceca64c0 ti: cec78000 task.ti: cec78000
[    5.698449] PC is at nand_scan+0x34/0x68
[    5.702385] LR is at nand_scan+0x34/0x68
[    5.706328] pc : [<c0294a7c>]    lr : [<c0294a7c>]    psr: 40000013
[    5.706328] sp : cec79d38  ip : 00000000  fp : cf3bbe88
[    5.717852] r10: 00000000  r9 : ceef6b50  r8 : cf894800
[    5.723094] r7 : d0b0c000  r6 : cf9d83c0  r5 : 00000001  r4 : ceef6b50
[    5.729651] r3 : 60000013  r2 : 00000002  r1 : ffffffe0  r0 : 0000002c
[    5.736209] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[    5.743377] Control: 0005397f  Table: 0fbac000  DAC: 00000051
[    5.749149] Process udevd (pid: 329, stack limit = 0xcec78190)
[    5.755000] Stack: (0xcec79d38 to 0xcec7a000)
[    5.759380] 9d20:                                                       00000000 cf9d83f0
[    5.767598] 9d40: ceef6810 bf0d31fc c0484f91 cf8c8808 cec71808 00000023 00000000 00000000
[    5.775812] 9d60: cf894810 bf0d1378 c05b4810 00000000 c056ffc0 00000005 cf3bbea4 c02788e8
[    5.784028] 9d80: c02788b0 cf894810 bf0d1378 c0277174 bf0d1378 cf894810 00000001 cf894810
[    5.792242] 9da0: cf894844 bf0d1378 c055cca0 c056fee8 00000001 c0277440 00000000 bf0d1378
[    5.800456] 9dc0: c02773d8 c0275694 cf8248ac cf8c9eb0 bf0d1378 00000000 ced95ee0 c02767e8
[    5.808670] 9de0: bf0d1356 bf0d1357 bf0d1378 bf0d32a0 00000001 c0526d80 c0526d80 c0277a50
[    5.816884] 9e00: c027841c bf0d1364 bf0d32a0 c0278ab0 cf3bb740 bf0d32a0 00000000 c00097a0
[    5.825097] 9e20: 00000001 00000001 00000000 00000000 00000001 00000000 cf8c7800 bf0d1408
[    5.833313] 9e40: cef2a000 c05525ac cfff0d40 00000000 0000005a cfdf9000 cfff0d40 00000000
[    5.841526] 9e60: 00000000 00000000 cf8000a0 024000c0 bf0d13c0 bf0d13c0 00000001 ced925c0
[    5.849741] 9e80: bf0d1408 cf3bbe80 00000001 c00bae40 bf0d13c0 c056d1f8 cec79f58 00000001
[    5.857955] 9ea0: bf0d13c0 c00786a4 bf0d13cc 00007fff bf0d13c0 c0075f20 c007594c 0000004e
[    5.866169] 9ec0: c0386300 d0b0ae00 cec79ee4 b6d03cfc cec79eec c0075a8c d0b09000 00001e50
[    5.874382] 9ee0: 0002c7e1 00000000 00800001 00000000 00000000 00000000 00000000 00000000
[    5.882596] 9f00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    5.890811] 9f20: 00000000 00000000 00000010 00000000 b6d03cfc 00000006 0000017b c000f1a8
[    5.899026] 9f40: cec78000 00000000 00000000 c0078d54 00000002 00000000 d0b09000 00001e50
[    5.907240] 9f60: d0b0a950 d0b09e7b d0b0a4a8 000005c0 00000650 00000000 00000000 00000000
[    5.915453] 9f80: 0000001e 0000001f 00000017 00000014 00000012 00000000 7f60504c 00000000
[    5.923669] 9fa0: 00020000 c000efe0 7f60504c 00000000 00000006 b6d03cfc 00000000 8011a2c8
[    5.931882] 9fc0: 7f60504c 00000000 00020000 0000017b b6d03cfc 00020000 8011a2c8 00000000
[    5.940097] 9fe0: be8701b0 be8701a0 b6cfb5e8 b6e62610 60000010 00000006 00000000 00000000
[    5.948330] [<c0294a7c>] (nand_scan) from [<bf0d31fc>] (orion_nand_probe+0x1fc/0x2a0 [orion_nand])
[    5.957354] [<bf0d31fc>] (orion_nand_probe [orion_nand]) from [<c02788e8>] (platform_drv_probe+0x38/0x6c)
[    5.966976] [<c02788e8>] (platform_drv_probe) from [<c0277174>] (driver_probe_device+0x170/0x3d4)
[    5.975895] [<c0277174>] (driver_probe_device) from [<c0277440>] (__driver_attach+0x68/0x8c)
[    5.984379] [<c0277440>] (__driver_attach) from [<c0275694>] (bus_for_each_dev+0x6c/0x90)
[    5.992601] [<c0275694>] (bus_for_each_dev) from [<c02767e8>] (bus_add_driver+0x114/0x240)
[    6.000903] [<c02767e8>] (bus_add_driver) from [<c0277a50>] (driver_register+0x9c/0xe0)
[    6.008952] [<c0277a50>] (driver_register) from [<c0278ab0>] (__platform_driver_probe+0x4c/0xe8)
[    6.017786] [<c0278ab0>] (__platform_driver_probe) from [<c00097a0>] (do_one_initcall+0x114/0x1d8)
[    6.026795] [<c00097a0>] (do_one_initcall) from [<c00bae40>] (do_init_module+0x58/0x370)
[    6.034934] [<c00bae40>] (do_init_module) from [<c00786a4>] (load_module+0x19ac/0x1e64)
[    6.042979] [<c00786a4>] (load_module) from [<c0078d54>] (SyS_finit_module+0x88/0x9c)
[    6.050854] [<c0078d54>] (SyS_finit_module) from [<c000efe0>] (ret_fast_syscall+0x0/0x38)
[    6.059072] Code: 0a000003 e59f1030 e59f0030 ebf89867 (e7f001f2) 
[    6.065191] ---[ end trace 6691f475691d5e7d ]---
I use 4.4.3 patched with the bodhi patch against 4.4.0. You may check if the some holds for 4.4.0

--

Regards
PLD = Polish(ed) Linux Distribution, www.pld-linux.org
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 10, 2016 01:06PM
pld,

It should be set to

CONFIG_MTD_NAND_ORION=y

-bodhi
===========================
Forum Wiki
bodhi's corner
bohi, any way you can provide another download for 4.4.0 rootfs with Wheezy instead of Jessie? Didn't realize till too late that the 4.4 rootfs d/l was already upgraded to Jessie.

TIA

LeggoMyEggo's Google Plus Profile
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 12, 2016 02:16PM
LeggoMyEggo,

Sure I can. However, you could also use

Quote

Updated 31 Oct 2014:

Rootfs Debian-3.17.0-kirkwood-tld-1 was uploaded. This rootfs is to keep in sync with kernel Linux-3.17.0-kirkwood-tld-1.

and then upgrade the kernel to 4.4. It's pretty easy. If you don't change apt sources then it will stay wheezy.

Let me know if you still need it.

-bodhi
===========================
Forum Wiki
bodhi's corner
I'm trying to remember the first rootfs with dtb. Was that 3.17 or 3.18?

LeggoMyEggo's Google Plus Profile
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 12, 2016 02:54PM
It's 3.17.

-bodhi
===========================
Forum Wiki
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> It's 3.17.


OK then, ignore my earlier post :)

LeggoMyEggo's Google Plus Profile
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 01:52AM
kernel 4.5 is out.

It includes the NSA325 dtb so this device is booting up without further kernel modifications.
Now I'm trying to use the working parts of the kernel 4.4 patch.
I think all except the "ide-disk" stuff should be working.



Edited 1 time(s). Last edit at 03/15/2016 02:17AM by pengu.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 02:05AM
pengu Wrote:
-------------------------------------------------------
> kernel 4.5 is out.
>
> It includes the NSA325 dtb so this device is
> booting up without further kernel modifications.
> Now I'm trying to use the working parts of the
> kernel 4.4 patch.
> I think all expect the "ide-disk" stuff should be
> working.

Nope. I think using my old NSA325 DTB is better. Already built it and I'm testing it.

Also, ide-disk1/ide-disk2 will not work correctly without the patch.

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



Edited 2 time(s). Last edit at 03/15/2016 02:10AM by bodhi.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 02:21AM
thanks for the reply bodhi,


>Nope. I think using my old NSA325 DTB is better. Already built it and I'm testing it.

I haven't compared it I'll see later with the other patches around.



>Also, ide-disk1/ide-disk2 will not work correctly without the patch.

Shure but I can't apply the whole stuff because something has changed in the code to be patched
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 02:31AM
pengu,

> Shure but I can't apply the whole stuff because
> something has changed in the code to be patched

I usually have to make a new patch for a new kernel. Always something changes, mostly because new devices were added, or sometime because they change the design in certain areas in the kernel.

Most of the time, the changes were minor. There was only one major change that occurred when we transitioned from 3.16 (non-FDT) to 3.17 (FDT) kernel.

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



Edited 1 time(s). Last edit at 03/15/2016 02:35AM by bodhi.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 02:38AM
yes, atm it's only the "ide-disk" stuff which should be modified.

As you (perhaps) guess, the "new" NSA325 DTB is missing some parts (buttuns, MTD layout)
The rest seems generic so it could be patched.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 02:49AM
The NSA325 DTS that I'm using is from Philipp Kirchhofer. It is too bad that somebody else submitted the patch, iirc. I think Phillip deserved the credit, and it is obvious that his DTS came out first and more completed. So I'm keeping it in my release.

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



Edited 1 time(s). Last edit at 03/15/2016 02:49AM by bodhi.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 15, 2016 03:52AM
yeah this DTB is more "complete"
All except "ide-disk" is patched and no "sensors" with the new one.
So I'm using "your one" again.
pld
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 16, 2016 02:05PM
Hi there,

I disassembled my NSA310 and definitely it is equipped with ADT7476, but

When I use unmodified kirkwood-nsa310.dts I get
adt7476-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0:          +0.00 V  (min =  +0.00 V, max =  +3.31 V)
in1:          +0.00 V  (min =  +0.00 V, max =  +2.99 V)
in2:          +0.00 V  (min =  +0.00 V, max =  +4.39 V)
in3:          +0.00 V  (min =  +0.00 V, max =  +6.68 V)
in4:          +0.00 V  (min =  +0.00 V, max = +15.69 V)
fan1:           0 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
temp1:       -128.0 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
temp2:       -128.0 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
temp3:       -128.0 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
cpu0_vid:    +0.000 V
So I modified dts to use LM85 and obtained:
lm85-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0:          +1.81 V  (min =  +0.00 V, max =  +3.32 V)
Vcore:        +1.09 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:        +3.21 V  (min =  +2.97 V, max =  +3.63 V)
+5V:          +5.10 V  (min =  +4.50 V, max =  +5.50 V)
+12V:        +12.19 V  (min =  +0.00 V, max = +15.94 V)
fan1:        4115 RPM  (min =    0 RPM)
MB tmp:       +31.0 C  (low  = -127.0 C, high = +127.0 C)
CPU tmp:      +33.0 C  (low  = -127.0 C, high = +127.0 C)
But, today after kernel compilation I used unmodified dts and obtained:
adt7476-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0:          +1.81 V  (min =  +0.00 V, max =  +3.31 V)
in1:          +1.10 V  (min =  +0.00 V, max =  +2.99 V)
in2:          +3.22 V  (min =  +2.98 V, max =  +3.63 V)
in3:          +5.12 V  (min =  +4.53 V, max =  +5.52 V)
in4:         +12.01 V  (min =  +0.00 V, max = +15.69 V)
fan1:        4131 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
temp1:        +29.5 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
temp2:        +30.8 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
temp3:        +32.8 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
cpu0_vid:    +0.000 V
The effect persists until the cold start. So it looks like the adt7475 kernel module is unable to initiate the chp.

--

Regards
PLD = Polish(ed) Linux Distribution, www.pld-linux.org



Edited 1 time(s). Last edit at 03/16/2016 02:45PM by pld.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 16, 2016 11:33PM
pld Wrote:
-------------------------------------------------------
> Hi there,
>
> I disassembled my NSA310 and definitely it is
> equipped with ADT7476, but
>
> When I use unmodified kirkwood-nsa310.dts I get
>
> adt7476-i2c-0-2e
> Adapter: mv64xxx_i2c adapter
> in0:          +0.00 V  (min =  +0.00 V, max = 
> +3.31 V)
> in1:          +0.00 V  (min =  +0.00 V, max = 
> +2.99 V)
> in2:          +0.00 V  (min =  +0.00 V, max = 
> +4.39 V)
> in3:          +0.00 V  (min =  +0.00 V, max = 
> +6.68 V)
> in4:          +0.00 V  (min =  +0.00 V, max =
> +15.69 V)
> fan1:           0 RPM  (min =    0 RPM)
> fan2:           0 RPM  (min =    0 RPM)
> fan3:           0 RPM  (min =    0 RPM)
> fan4:           0 RPM  (min =    0 RPM)
> temp1:       -128.0 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> temp2:       -128.0 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> temp3:       -128.0 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> cpu0_vid:    +0.000 V
>
> So I modified dts to use LM85 and obtained:
>
> lm85-i2c-0-2e
> Adapter: mv64xxx_i2c adapter
> in0:          +1.81 V  (min =  +0.00 V, max = 
> +3.32 V)
> Vcore:        +1.09 V  (min =  +0.00 V, max = 
> +2.99 V)
> +3.3V:        +3.21 V  (min =  +2.97 V, max = 
> +3.63 V)
> +5V:          +5.10 V  (min =  +4.50 V, max = 
> +5.50 V)
> +12V:        +12.19 V  (min =  +0.00 V, max =
> +15.94 V)
> fan1:        4115 RPM  (min =    0 RPM)
> MB tmp:       +31.0 C  (low  = -127.0 C, high =
> +127.0 C)
> CPU tmp:      +33.0 C  (low  = -127.0 C, high =
> +127.0 C)
>
> But, today after kernel compilation I used
> unmodified dts and obtained:
>
> adt7476-i2c-0-2e
> Adapter: mv64xxx_i2c adapter
> in0:          +1.81 V  (min =  +0.00 V, max = 
> +3.31 V)
> in1:          +1.10 V  (min =  +0.00 V, max = 
> +2.99 V)
> in2:          +3.22 V  (min =  +2.98 V, max = 
> +3.63 V)
> in3:          +5.12 V  (min =  +4.53 V, max = 
> +5.52 V)
> in4:         +12.01 V  (min =  +0.00 V, max =
> +15.69 V)
> fan1:        4131 RPM  (min =    0 RPM)
> fan2:           0 RPM  (min =    0 RPM)
> fan3:           0 RPM  (min =    0 RPM)
> fan4:           0 RPM  (min =    0 RPM)
> temp1:        +29.5 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> temp2:        +30.8 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> temp3:        +32.8 C  (low  = -127.0 C, high =
> +127.0 C)
>                        (crit = +100.0 C, hyst =
> +96.0 C)
> cpu0_vid:    +0.000 V
>
> The effect persists until the cold start. So it
> looks like the adt7475 kernel module is unable to
> initiate the chp.

Let's wait and see if anybody can confirm this for the NSA310. You should repost this in the NSA310 fan speed thread.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 17, 2016 04:48PM
Not so good news about kernel 4.5! I'm having a kernel panic related to mv643xx_eth_probe running it on Zyxel NSA310S.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 17, 2016 09:47PM
pengu Wrote:
-------------------------------------------------------
> yeah this DTB is more "complete"
> All except "ide-disk" is patched and no "sensors"
> with the new one.
> So I'm using "your one" again.

Hi pengu,

Are you building 4.5? have you tried and seen ethernet is broken in your NSA325 like I'm seeing in the NSA310S?

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



Edited 1 time(s). Last edit at 03/17/2016 09:47PM by bodhi.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 18, 2016 04:43AM
Damn guys, i was waiting for a 4.5 release on 310s, i guess i'll have to wait until you wizards will manage to fix it :)
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 18, 2016 08:15AM
bodhi Wrote:

> Hi pengu,
>
> Are you building 4.5? have you tried and seen
> ethernet is broken in your NSA325 like I'm seeing
> in the NSA310S?



yes, 4,5 is running on NSA325v2 for days and now on NSA325, no problems with ethernet.
I still have a NSA310s, let's see whats going on there


Edit

booting with 4.5 on NSA310s doesn't bring up the LAN.
The only thing I see is:

[    1.572211] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4

and nothing more


on NSA325/NSA325v2 ... all good

[    1.519357] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.591171] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address ...



Edited 2 time(s). Last edit at 03/18/2016 09:02AM by pengu.
Re: Linux Kernel 4.4 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
March 18, 2016 02:02PM
Thanks pengu,

That's what I'm seeing, too. There is some code change in the kernel that effect the NSA310S/320S, and I am not sure yet why. It's the same network chip as the NSA325.

-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: