Quantcast
Channel: Linux Device Hacking - Debian
Viewing all 26623 articles
Browse latest View live
↧

Re: Debian on Dell Kace M300

August 31, 2019, 8:23 pm
$
0
0
mikeh49 Wrote:
-------------------------------------------------------
> Good work, Neal!
>
> OK, got ssh working in stock OS per the above, but
> also had to edit the /etc/network/interfaces file
> to set the the eth0 interface to dhcp. It was
> static 192.168.2.1 or something like that. My
> network is 192.168.1.x.

Oh yes I had forgotten that I had done that earlier. I have since gone through the configuration wizard in the web UI and it sets it up for static again using the IP you give it.

I really didn’t find anything in the web UI to assist. I’m guessing somehow that tether key temporarily enables ssh access by changing the sshd_config. It otherwise seems like a normal OpenSSH install.

Neal
↧
Search

Pogoplug V4 lost power, boots but will not get IP address for SSH

August 31, 2019, 11:24 pm
$
0
0
I have a Pogoplug V4 I have been using as a NAS, and recently had a power surge. It is booting from an SD card, and displays a green light once the power cycles, but does not show up on the network, and will not accept SSH connections at the IP address I had for it. I created a new rootfs for it on a new SD card, but it will not boot that image, only the SD card I originally made when I installed Debian.

I'm tempted to trash it and move to a PI, but I like the V4's USB 3.0 ports. Any suggestions where I go from here?
↧
↧

Re: Pogoplug V4 lost power, boots but will not get IP address for SSH

September 1, 2019, 2:16 am
$
0
0
spexandwally,

> I have a Pogoplug V4 I have been using as a NAS,
> and recently had a power surge. It is booting from
> an SD card, and displays a green light once the
> power cycles, but does not show up on the network,
> and will not accept SSH connections at the IP
> address I had for it. I created a new rootfs for
> it on a new SD card, but it will not boot that
> image, only the SD card I originally made when I
> installed Debian.
>
> I'm tempted to trash it and move to a PI, but I
> like the V4's USB 3.0 ports. Any suggestions where
> I go from here?

Power outage usually causes rootfs corruption, if the SD rootfs is not journal. But it is a recoverable error. Have you tried to take the SD card to another Linux box and run e2fsck to fix the rootfs corruption?

But first you need to tell us what you have installed in this Pogo V4. Does it have a new u-boot? you were booting with SD card, then what's on it, Debian, Arch,....? how was it formatted, Ext3, Ext4...?

The above information is the minimum you need to provide before I can suggest what is the next step to fix it. If you have a boot log before it was broken then post here, too.
↧

Re: Debian on Dell Kace M300

September 1, 2019, 5:16 am
$
0
0
Neal,

> Oh yes I had forgotten that I had done that
> earlier. I have since gone through the
> configuration wizard in the web UI and it sets it
> up for static again using the IP you give it.
>

So you can change the IP to anything you want through the web page (from the original 192.168.2.100) ?

> I really didn’t find anything in the web UI to
> assist. I’m guessing somehow that tether key
> temporarily enables ssh access by changing the
> sshd_config. It otherwise seems like a normal
> OpenSSH install.

I think we close to exhaust the possibilities of how to access the box without serial console.

Albeit, I have thought and finalized (in my mind) of another procedure to install on the internal SATA module. As JT mention, there are only 2 screws to remove. And that can be put inside a SATA enclosure or using a SATA-USB cable.
↧

Re: Debian on Dell Kace M300

September 1, 2019, 6:07 am
$
0
0
bodhi Wrote:

> So you can change the IP to anything you want
> through the web page (from the original
> 192.168.2.100) ?

Yes. I guess the idea is for initial configuration you hook it up direct to an unused ethernet port that you configure to 192.168.2.x, then access the web page via 192.168.2.100. So at least you can do that to get it on your network. Not sure why they didn't just configure it to use DHCP for initial setup. Probably makes it easier having it at a known address.

> I think we close to exhaust the possibilities of
> how to access the box without serial console.

I really don't mind that, it was easy enough to access the serial console.

> Albeit, I have thought and finalized (in my mind)
> of another procedure to install on the internal
> SATA module. As JT mention, there are only 2
> screws to remove. And that can be put inside a
> SATA enclosure or using a SATA-USB cable.

There's probably enough room in the box to put a 3.5 inch SATA drive in there and attaching to the SATA port with a short SATA cable. Going SATA-USB you would lose some performance since I believe these are only USB 2.0 ports.

Neal
↧
↧

Re: Debian on Dell Kace M300

September 1, 2019, 6:44 am
$
0
0
nwestfal Wrote:
-------------------------------------------------------
> bodhi Wrote:
>
> > So you can change the IP to anything you want
> > through the web page (from the original
> > 192.168.2.100) ?
>
> Yes. I guess the idea is for initial
> configuration you hook it up direct to an unused
> ethernet port that you configure to 192.168.2.x,
> then access the web page via 192.168.2.100. So at
> least you can do that to get it on your network.
> Not sure why they didn't just configure it to use
> DHCP for initial setup. Probably makes it easier
> having it at a known address.

It is actually very common to use known address like that. Most of wireless bridges in the market use a known address. There is pros and cons between that and dynamic IP, as far as installation is concerned.

>
> > I think we close to exhaust the possibilities
> of
> > how to access the box without serial console.
>
> I really don't mind that, it was easy enough to
> access the serial console.

For more experienced users, we always connect serial console. But It would make the box more popular for beginners if serial console is not needed for installation.


> > Albeit, I have thought and finalized (in my
> mind)
> > of another procedure to install on the internal
> > SATA module. As JT mention, there are only 2
> > screws to remove. And that can be put inside a
> > SATA enclosure or using a SATA-USB cable.
>
> There's probably enough room in the box to put a
> 3.5 inch SATA drive in there and attaching to the
> SATA port with a short SATA cable. Going SATA-USB
> you would lose some performance since I believ
> these are only USB 2.0 ports.

I did not mean we want a SATA drive inside this box :) The SATA-USB connection is outside and temporary, only during the installation of the new rootfs.
↧

Re: Debian on Dell Kace M300

September 1, 2019, 8:37 am
$
0
0
My quick reaction is that pulling the SSD doesn't seem easier than setting up serial. If someone is comfortable with pulling the SSD and has an adapter, they probably have a USB serial adapter as well. Especially if they're into these little boxes. But, if the SSD approach is a better/easier technical solution, then of course that's the way to go.

Getting into the Pogo plugs with SSH from the get-go, was a good deal.
↧

Re: Debian on Dell Kace M300

September 1, 2019, 8:52 am
$
0
0
mikeh49 Wrote:

> Getting into the Pogo plugs with SSH from the
> get-go, was a good deal.

Even then it only worked because Pogoplug made it doable through their web site. Now that they're gone, the only way to hack a stock pogo is through serial.

Neal
↧
Search

Re: Debian on Dell Kace M300

September 1, 2019, 8:57 am
$
0
0
bodhi Wrote:
-------------------------------------------------------

> For more experienced users, we always connect
> serial console. But It would make the box more
> popular for beginners if serial console is not
> needed for installation.

True that.

> I did not mean we want a SATA drive inside this
> box :) The SATA-USB connection is outside and
> temporary, only during the installation of the
> new rootfs.

Ah, I see. But partly I'm thinking ahead for my own uses :)

Neal
↧
↧

Re: Debian on Dell Kace M300

September 1, 2019, 7:43 pm
$
0
0
This M300 is pretty picky on usb flash drives. I have some Kingston / Lexar / xxx brand flash drives which worked fine on Dockstar / Pogo E02 / etc, but those won't work on the M300. Only two 4GB sandisk flash drives worked.
↧

Re: Linux Kernel 5.2.9 Kirkwood package and Debian rootfs

September 2, 2019, 6:27 am
$
0
0
Hello bodhi,

Could you please look at this issue?
https://forum.doozan.com/read.php?2,18152,51209#msg-51209

It still produce exact same error on building the kernel module, even with the latest rootfs and latest kernel&header files. I'm not sure if that's the module's issue or headers issue.

The module that pre-build by TheFeaR is for 5.1 which is not the latest kernel now...

Thanks!
↧

Re: Linux Kernel 5.2.9 Kirkwood package and Debian rootfs

September 2, 2019, 7:54 am
↧

Re: Debian on Dell Kace M300

September 2, 2019, 9:25 am
$
0
0
Looks like M300 has a pretty "strong" CPU...

https://www.softprayog.in/troubleshooting/how-to-get-the-value-of-pi-in-bc-calculations

apt-get install bc

time echo "scale=4000; 4*a(1)" | bc -l 


=================================

1.2GHz

goflexhome		1m7.236s

Dockstar		1m7.026s

dreamplug		1m3.545s

=================================

2.0GHz

Kace M300		0m38.069s

=================================

1.2GHz

Mirabox		        1m8.176s

=================================

1.0 GHz

Rpi 0 w			1m23.440s

=================================

1.2GHz

Rpi 3B			0m43.348s

=================================

3.1GHz

i3-2100			0m11.850s
↧
↧

Re: Debian on Dell Kace M300

September 2, 2019, 2:27 pm
$
0
0
> Looks like M300 has a pretty "strong" CPU...

Yes indeed :)
↧

Re: Debian on wrt1200ac

September 2, 2019, 4:30 pm
$
0
0
Hi Bodhi.

Sorry for the delay (busy week) and for the confusion regarding stock vs mainline kernel.

My box is WRT1200AC v1. Testing the new dtb: 

Hit any key to stop autoboot:  0
Marvell>> setenv mtdparts  mtdparts=pxa3xx_nand-0:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg); setenv bootargs console=ttyS0,115200 init=/sbin/init root=LABEL=WRT rootdelay=10 $mtdparts earlyprintk=serial ipv6.disable=1; dhcp; tftpboot 0x02000000 wrt/test/zImage; tftpboot 0x2900000 wrt/test/uInitrd; tftpboot 0x1000000 wrt/test/armada-385-linksys-caiman-bodhi.dtb; setenv fdt_skip_update yes; bootz 0x02000000 0x2900000 0x1000000
BOOTP broadcast 1
DHCP client bound to address 192.168.1.112
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.112
Filename 'wrt/test/zImage'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################################################
         6.5 MiB/s
done
Bytes transferred = 4661552 (472130 hex)
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.112
Filename 'wrt/test/uInitrd'.
Load address: 0x2900000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################
         6.3 MiB/s
done
Bytes transferred = 7991206 (79efa6 hex)
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.112
Filename 'wrt/test/armada-385-linksys-caiman-bodhi.dtb'.
Load address: 0x1000000
Loading: ##
         4.4 MiB/s
done
Bytes transferred = 18580 (4894 hex)
## Loading init Ramdisk from Legacy Image at 02900000 ...
   Image Name:   initramfs-5.1.7-mvebu-tld-1
   Created:      2019-07-31   4:34:29 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7991142 Bytes = 7.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x01000000
   Loading Ramdisk to 1f208000, end 1f9a6f66 ... OK
   Loading Device Tree to 00ff8000, end 00fff893 ... OK

   Skipping Device Tree update ('fdt_skip_update' = yes)

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.1.7-mvebu-tld-1 (root@tldDebianVM) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-27ubuntu1~18.04)) #1 SMP PREEMPT Sat Jun 8 20:04:26 PDT 2019
[    0.000000][    T0] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Linksys WRT1200AC
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writealloc
[    0.000000][    T0] random: get_random_bytes called from start_kernel+0x78/0x4dc with crng_init=0
[    0.000000][    T0] percpu: Embedded 18 pages/cpu s41932 r8192 d23604 u73728
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 init=/sbin/init root=LABEL=WRT rootdelay=10 mtdparts=pxa3xx_nand-0:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) earlyprintk=serial ipv6.disable=1
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000][    T0] Memory: 497256K/524288K available (9216K kernel code, 826K rwdata, 2388K rodata, 1024K init, 332K bss, 27032K reserved, 0K cma-reserved, 0K highmem)
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000][    T0]  Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000][    T0] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000][    T0] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000][    T0] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000][    T0] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000][    T0] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000007][    T0] sched_clock: 64 bits at 666MHz, resolution 1ns, wraps every 4398046511103ns
[    0.008678][    T0] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x999999d70a, max_idle_ns: 440795225152 ns
[    0.020379][    T0] Switching to timer-based delay loop, resolution 1ns
[    0.027202][    T0] Ignoring duplicate/late registration of read_current_timer delay
[    0.034919][    T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.046991][    T0] Console: colour dummy device 80x30
[    0.052130][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 1332.00 BogoMIPS (lpj=6660000)
[    0.063397][    T0] pid_max: default: 32768 minimum: 301
[    0.068802][    T0] LSM: Security Framework initializing
[    0.074145][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.081433][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.089544][    T0] *** VALIDATE proc ***
[    0.093639][    T0] *** VALIDATE cgroup1 ***
[    0.097901][    T0] *** VALIDATE cgroup2 ***
[    0.102187][    T0] CPU: Testing write buffer coherency: ok
[    0.107753][    T0] CPU0: Spectre v2: using BPIALL workaround
[    0.113607][    T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.177054][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.183997][    T1] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.189942][    T1] mvebu-pmsu: Initializing Power Management Service Unit
[    0.207028][    T1] rcu: Hierarchical SRCU implementation.
[    0.247027][    T1] smp: Bringing up secondary CPUs ...
[    0.307099][    T1] Booting CPU 1
[    0.310572][    T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.310576][    T0] CPU1: Spectre v2: using BPIALL workaround
[    0.322710][    T1] smp: Brought up 1 node, 2 CPUs
[    0.327506][    T1] SMP: Total of 2 processors activated (2664.00 BogoMIPS).
[    0.334526][    T1] CPU: All CPU(s) started in SVC mode.
[    0.340425][    T1] devtmpfs: initialized
[    0.346930][    T1] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.355574][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.366076][    T1] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.372969][    T1] prandom: seed boundary self test passed
[    0.380095][    T1] prandom: 100 self tests passed
[    0.384867][    T1] pinctrl core: initialized pinctrl subsystem
[    0.391636][    T1] NET: Registered protocol family 16
[    0.397468][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.405442][    T1] audit: initializing netlink subsys (disabled)
[    0.412257][   T33] audit: type=2000 audit(0.380:1): state=initialized audit_enabled=0 res=1
[    0.420723][    T1] cpuidle: using governor ladder
[    0.425508][    T1] cpuidle: using governor menu
[    0.430341][    T1] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.439019][    T1] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.445673][    T1] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.454435][    T1] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.487678][    T1] vgaarb: loaded
[    0.491356][    T1] SCSI subsystem initialized
[    0.496306][    T1] usbcore: registered new interface driver usbfs
[    0.502548][    T1] usbcore: registered new interface driver hub
[    0.508626][    T1] usbcore: registered new device driver usb
[    0.514841][    T1] media: Linux media interface: v0.10
[    0.520765][    T1] videodev: Linux video capture interface: v2.00
[    0.527154][    T1] pps_core: LinuxPPS API ver. 1 registered
[    0.532790][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.542640][    T1] PTP clock support registered
[    0.548279][    T1] clocksource: Switched to clocksource arm_global_timer
[    1.041619][    T1] VFS: Disk quotas dquot_6.6.0
[    1.046274][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.062038][    T1] NET: Registered protocol family 2
[    1.067489][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    1.075840][    T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    1.083585][    T1] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    1.090734][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    1.097802][    T1] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    1.104328][    T1] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    1.111405][    T1] NET: Registered protocol family 1
[    1.116751][    T1] RPC: Registered named UNIX socket transport module.
[    1.123361][    T1] RPC: Registered udp transport module.
[    1.128748][    T1] RPC: Registered tcp transport module.
[    1.134124][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.141374][    T1] Unpacking initramfs...
[    1.452271][    T1] Freeing initrd memory: 7804K
[    1.457059][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    1.464532][    T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    1.475012][    T1] Initialise system trusted keyrings
[    1.480204][    T1] Key type blacklist registered
[    1.484969][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    1.492167][    T1] zbud: loaded
[    1.495958][    T1] NFS: Registering the id_resolver key type
[    1.501711][    T1] Key type id_resolver registered
[    1.506568][    T1] Key type id_legacy registered
[    1.511272][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.518646][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.525807][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.533886][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    1.541098][    T1] orangefs_init: module version upstream loaded
[    1.605771][    T1] Key type asymmetric registered
[    1.610566][    T1] Asymmetric key parser 'x509' registered
[    1.616199][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    1.626040][    T1] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    1.636057][    T1] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.642704][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.648872][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.656412][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.664887][    T1] PCI: bus0: Fast back to back transfers disabled
[    1.671158][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.679847][    T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.688974][    T1] pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring
[    1.729375][    T1] PCI: bus1: Fast back to back transfers disabled
[    1.735977][    T1] pci 0000:02:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0000:00:02.0 (capable of 4.000 Gb/s with 5 GT/s x1 link)
[    1.750617][    T1] pci 0000:00:02.0: ASPM: current common clock configuration is broken, reconfiguring
[    1.789373][    T1] PCI: bus2: Fast back to back transfers disabled
[    1.795657][    T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe01fffff]
[    1.803214][    T1] pci 0000:00:02.0: BAR 14: assigned [mem 0xe0200000-0xe03fffff]
[    1.810765][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0400000-0xe04007ff pref]
[    1.818659][    T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0500000-0xe05007ff pref]
[    1.826549][    T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe00fffff 64bit pref]
[    1.834968][    T1] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0100000-0xe01fffff 64bit pref]
[    1.843385][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.849031][    T1] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe01fffff]
[    1.856490][    T1] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0200000-0xe02fffff 64bit pref]
[    1.864908][    T1] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0300000-0xe03fffff 64bit pref]
[    1.873324][    T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[    1.878969][    T1] pci 0000:00:02.0:   bridge window [mem 0xe0200000-0xe03fffff]
[    1.886476][    T1] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[    1.893308][    T1] pcieport 0000:00:02.0: enabling device (0140 -> 0142)
[    1.900607][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.958770][    T1] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    1.967063][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    2.028751][    T1] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    2.086191][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.094767][    T1] printk: console [ttyS0] disabled
[    2.119866][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A
[    2.129527][    T1] printk: console [ttyS0] enabled
[    2.129527][    T1] printk: console [ttyS0] enabled
[    2.139352][    T1] printk: bootconsole [earlycon0] disabled
[    2.139352][    T1] printk: bootconsole [earlycon0] disabled
[    2.151993][    T1] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    2.161809][    T1] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[    2.172104][    T1] scsi host0: ahci-mvebu
[    2.176581][    T1] scsi host1: ahci-mvebu
[    2.180958][    T1] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 43
[    2.189632][    T1] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 43
[    2.199215][    T1] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[    2.206303][    T1] nand: AMD/Spansion S34ML01G2
[    2.210965][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    2.219638][    T1] Bad block table found at page 65472, version 0x01
[    2.226765][    T1] Bad block table found at page 65408, version 0x01
[    2.233617][    T1] 10 cmdlinepart partitions found on MTD device pxa3xx_nand-0
[    2.240972][    T1] Creating 10 MTD partitions on "pxa3xx_nand-0":
[    2.247186][    T1] 0x000000000000-0x000000200000 : "uboot"
[    2.253541][    T1] 0x000000200000-0x000000240000 : "u_env"
[    2.259840][    T1] 0x000000240000-0x000000280000 : "s_env"
[    2.266129][    T1] 0x000000900000-0x000000a00000 : "devinfo"
[    2.272593][    T1] 0x000000a00000-0x000003200000 : "kernel"
[    2.279033][    T1] 0x000001000000-0x000003200000 : "rootfs"
[    2.285458][    T1] 0x000003200000-0x000005a00000 : "alt_kernel"
[    2.292252][    T1] 0x000003800000-0x000005a00000 : "alt_rootfs"
[    2.299058][    T1] 0x000000a00000-0x000005a00000 : "ubifs"
[    2.305512][    T1] 0x000005a00000-0x000008000000 : "syscfg"
[    2.312924][    T1] libphy: Fixed MDIO Bus: probed
[    2.318203][    T1] libphy: orion_mdio_bus: probed
[    2.323564][    T1] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    2.333471][    T1] mvneta f1070000.ethernet eth0: Using hardware mac address c0:56:27:6d:20:a7
[    2.343893][    T1] mvneta f1034000.ethernet eth1: Using random mac address 0a:f4:b7:1c:d2:fc
[    2.352733][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.360025][    T1] ehci-pci: EHCI PCI platform driver
[    2.365231][    T1] ehci-orion: EHCI orion driver
[    2.370100][    T1] orion-ehci f1058000.usb: EHCI Host Controller
[    2.376239][    T1] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
[    2.384625][    T1] orion-ehci f1058000.usb: irq 39, io mem 0xf1058000
[    2.428317][    T1] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[    2.435101][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    2.444124][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.452090][    T1] usb usb1: Product: EHCI Host Controller
[    2.457693][    T1] usb usb1: Manufacturer: Linux 5.1.7-mvebu-tld-1 ehci_hcd
[    2.464784][    T1] usb usb1: SerialNumber: f1058000.usb
[    2.470452][    T1] hub 1-0:1.0: USB hub found
[    2.474940][    T1] hub 1-0:1.0: 1 port detected
[    2.480333][    T1] usbcore: registered new interface driver usblp
[    2.486589][    T1] usbcore: registered new interface driver usb-storage
[    2.493545][    T1] mousedev: PS/2 mouse device common for all mice
[    2.500552][    T1] armada38x-rtc f10a3800.rtc: registered as rtc0
[    2.506947][    T1] i2c /dev entries driver
[    2.513782][    T1] orion_wdt: Initial timeout 171 sec
[    2.529830][ T1185] ata1: SATA link down (SStatus 0 SControl 300)
[    2.547301][    T1] marvell-cesa f1090000.crypto: CESA device successfully registered
[    2.555442][    T1] hidraw: raw HID events driver (C) Jiri Kosina
[    2.561919][    T1] usbcore: registered new interface driver usbhid
[    2.568221][    T1] usbhid: USB HID core driver
[    2.573143][    T1] drop_monitor: Initializing network drop monitor service
[    2.580369][    T1] IPv6: Loaded, but administratively disabled, reboot required to enable
[    2.589707][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.596758][    T1] NET: Registered protocol family 17
[    2.602040][    T1] 8021q: 802.1Q VLAN Support v1.8
[    2.606975][    T1] Key type dns_resolver registered
[    2.612163][    T1] ThumbEE CPU extension supported.
[    2.617158][    T1] Registering SWP/SWPB emulation handler
[    2.623183][    T1] registered taskstats version 1
[    2.628000][    T1] Loading compiled-in X.509 certificates
[    2.633576][    T1] zswap: loaded using pool lzo/zbud
[    2.649482][    T1] Key type big_key registered
[    2.659125][    T1] Key type encrypted registered
[    2.665626][    T5] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.671704][    T5] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2
[    2.680012][    T5] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    2.690022][    T5] xhci-hcd f10f8000.usb3: irq 45, io mem 0xf10f8000
[    2.696702][    T5] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    2.705725][    T5] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.713717][    T5] usb usb2: Product: xHCI Host Controller
[    2.719328][    T5] usb usb2: Manufacturer: Linux 5.1.7-mvebu-tld-1 xhci-hcd
[    2.726413][    T5] usb usb2: SerialNumber: f10f8000.usb3
[    2.732204][    T5] hub 2-0:1.0: USB hub found
[    2.736693][    T5] hub 2-0:1.0: 1 port detected
[    2.741557][    T5] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.747604][    T5] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[    2.755865][    T5] xhci-hcd f10f8000.usb3: Host supports USB 3.0  SuperSpeed
[    2.763087][    T5] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.772002][    T5] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    2.781022][    T5] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.788993][    T5] usb usb3: Product: xHCI Host Controller
[    2.794594][    T5] usb usb3: Manufacturer: Linux 5.1.7-mvebu-tld-1 xhci-hcd
[    2.801686][    T5] usb usb3: SerialNumber: f10f8000.usb3
[    2.807401][    T5] hub 3-0:1.0: USB hub found
[    2.811903][    T5] hub 3-0:1.0: 1 port detected
[    2.817336][    T1] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    2.825045][    T1] armada38x-rtc f10a3800.rtc: setting system clock to 2019-09-02T23:19:15 UTC (1567466355)
[   12.218295][ T1189] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   12.225518][ T1189] ata2.15: Port Multiplier 1.1, 0x197b:0x2352 r0, 2 ports, feat 0x0/0x0
[   12.233755][ T1189] ata2.15: Asynchronous notification not supported, hotplug won't work on fan-out ports. Use warm-plug instead.
[   12.248468][ T1189] ahci-mvebu f10a8000.sata: FBS is enabled
[   12.254299][ T1189] ata2.00: hard resetting link
[   12.590730][ T1189] ata2.00: SATA link down (SStatus 113 SControl 113)
[   12.597332][ T1189] ata2.01: hard resetting link
[   12.930713][ T1189] ata2.01: SATA link down (SStatus 123 SControl 123)
[   12.938026][ T1189] ata2.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133
[   12.945300][ T1189] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32)
[   12.953363][ T1189] ata2.00: configured for UDMA/133
[   12.959120][ T1189] ata2.01: ATA-8: Hitachi HDT721010SLA360, ST6OA31B, max UDMA/133
[   12.966818][ T1189] ata2.01: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32)
[   12.975022][ T1189] ata2.01: configured for UDMA/133
[   12.980067][ T1189] ata2: EH complete
[   12.984016][    T7] scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA DT01ACA1 A750 PQ: 0 ANSI: 5
[   12.993575][  T233] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[   12.993599][    T7] scsi 1:1:0:0: Direct-Access     ATA      Hitachi HDT72101 A31B PQ: 0 ANSI: 5
[   13.002035][  T233] sd 1:0:0:0: [sda] 4096-byte physical blocks
[   13.017094][   T35] sd 1:1:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[   13.025567][   T35] sd 1:1:0:0: [sdb] Write Protect is off
[   13.028354][  T233] sd 1:0:0:0: [sda] Write Protect is off
[   13.036644][   T35] sd 1:1:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   13.036650][  T233] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   13.077104][   T35]  sdb: sdb1 sdb2 sdb3
[   13.082075][   T35] sd 1:1:0:0: [sdb] Attached SCSI removable disk
[   13.097007][  T233]  sda: sda1 sda2 sda3
[   13.101910][  T233] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   13.109743][    T1] Freeing unused kernel memory: 1024K
[   13.158687][    T1] Checked W+X mappings: passed, no W+X pages found
[   13.165076][    T1] Run /init as init process
Loading, please wait...
starting version 232
[   13.214705][ T1543] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[   13.218687][ T1544] random: udevadm: uninitialized urandom read (16 bytes read)
[   13.222944][ T1543] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[   13.509104][ T1547] mv88e6085 f1072004.mdio-mii:00: switch 0x1760 detected: Marvell 88E6176, revision 1
[   13.706890][ T1547] libphy: mv88e6xxx SMI: probed
[   13.954219][ T1547] mv88e6085 f1072004.mdio-mii:00 lan4 (uninitialized): PHY [mv88e6xxx-0:00] driver [Marvell 88E1540]
[   13.965752][ T1547] mv88e6085 f1072004.mdio-mii:00 lan3 (uninitialized): PHY [mv88e6xxx-0:01] driver [Marvell 88E1540]
[   13.979257][ T1547] mv88e6085 f1072004.mdio-mii:00 lan2 (uninitialized): PHY [mv88e6xxx-0:02] driver [Marvell 88E1540]
[   13.990684][ T1547] mv88e6085 f1072004.mdio-mii:00 lan1 (uninitialized): PHY [mv88e6xxx-0:03] driver [Marvell 88E1540]
[   14.004172][ T1547] mv88e6085 f1072004.mdio-mii:00 wan (uninitialized): PHY [mv88e6xxx-0:04] driver [Marvell 88E1540]
[   14.019817][ T1547] DSA: tree 0 setup
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[   24.136108][    C0] random: fast init done
[/sbin/fsck.ext4 (1) -- /dev/sdb1] fsck.ext4 -a -C0 /dev/sdb1
WRT: clean, 51924/393216 files, 788803/1572864 blocks
done.
[   24.210904][ T1595] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[ ok ] Setting hostname to 'trunks'...done.
[....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[....] Waiting for /dev to be fully populated...[   25.881532][ T1806] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   25.931603][ T1806] sd 1:1:0:0: Attached scsi generic sg1 type 0
[   25.994014][ T1808] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   26.038963][ T1808] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   26.265621][ T1808] mwlwifi: no symbol version for module_layout
[   26.274222][ T1801] mwlwifi: loading out-of-tree module taints kernel.
[   26.283078][ T1808] mwlwifi: loading out-of-tree module taints kernel.
[   26.301325][ T1801] <<Marvell Mac80211 Wireless PCIE Network Driver version 10.3.8.0-20181210>>
[   26.637238][ T1958] md0: detected capacity change from 0 to 1986179104768
[   27.358493][ T1801] ieee80211 phy0: device node: pcie@1,0
[   27.382758][ T1801] ieee80211 phy0: firmware version: 0x702091a
[   27.406790][ T1801] ieee80211 phy0: firmware region code: 0
[   27.485271][ T1801] ieee80211 phy0: 2G enabled, 5G enabled
[   27.490843][ T1801] ieee80211 phy0: 4 TX antennas, 4 RX antennas
[   28.482362][ T1801] ieee80211 phy1: device node: pcie@2,0
[   28.506656][ T1801] ieee80211 phy1: firmware version: 0x702091a
[   28.530684][ T1801] ieee80211 phy1: firmware region code: 0
[   28.569670][ T1801] ieee80211 phy1: 2G enabled, 5G enabled
[   28.575189][ T1801] ieee80211 phy1: 4 TX antennas, 4 RX antennas
[   28.609702][ T1802] mwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[   28.658456][ T1807] mwlwifi 0000:02:00.0 wlp2s0: renamed from wlan1
done.
[....] Activating swap:swapon: [   28.991922][ T2149] Adding 524284k swap on /dev/sdb2.  Priority:-2 extents:1 across:524284k FS
/dev/sdb2: found signature [page[   29.002651][ T2149] Adding 524284k swap on /dev/sda2.  Priority:-3 extents:1 across:524284k FS
size=4096, signature=swap]
swapon: /dev/sdb2: pagesize=4096, swapsize=536870912, devsize=536870912
swapon /dev/sdb2
swapon: /dev/sda2: found signature [pagesize=4096, signature=swap]
swapon: /dev/sda2: pagesize=4096, swapsize=536870912, devsize=536870912
swapon /dev/sda2
. ok
[   29.090349][ T2173] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[....] Will now activate lvm and md swap:swapon: /dev/sdb2: already active -- ignored
swapon: /dev/sda2: already active -- ignored
done.
[info] Will now check all file systems.
[   29.433084][    C0] random: crng init done
[   29.437209][    C0] random: 7 urandom warning(s) missed due to ratelimiting
fsck from util-linux 2.29.2
Checking all file systems.
LABEL=WRT is mounted
UUID="61d3400b-2508-4e9c-8591-c67cefbdc418" is not mounted
[/sbin/fsck.jfs (1) -- /exports] fsck.jfs -y /dev/md0
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 9/2/2019 19:19:25
Using default parameter: -p
The current device is:  /dev/md0
Block size in bytes:  4096
Filesystem size in blocks:  484907008
**Phase 0 - Replay Journal Log
Filesystem is clean.
[....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs[ ok hat location is writable..
[info] Loading kernel module mv88e6xxx.
[info] Loading kernel module tmp421.
[ ok ] Cleaning up temporary files...[....] Cleaning /tmp...done.
[ ok .
[   30.059444][ T2487] JFS: nTxBlock = 3953, nTxLock = 31630
[ ok ] Will now mount local filesystems:.
[....] Will now activate swapfile swap:swapon: /dev/sdb2: already active -- ignored
swapon: /dev/sda2: already active -- ignored
done.
[ ok ] Checking minimum space in /tmp...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables...done.
[ ok ] Initializing random number generator...done.
[   30.773001][ T2736] mvneta f1070000.ethernet eth0: configuring for fixed/rgmii-id link mode
[   30.781628][   T16] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   30.855232][ T2776] mvneta f1034000.ethernet eth1: configuring for fixed/sgmii link mode
[   30.863535][    T5] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[   31.065648][ T2821] device eth1 entered promiscuous mode
[   31.071144][ T2821] mv88e6085 f1072004.mdio-mii:00 lan1: configuring for phy/gmii link mode
[   31.086637][ T2821] 8021q: adding VLAN 0 to HW filter on device lan1
[....] 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/

Listening on LPF/lan1/c0:56:27:6d:20:a7
Sending on   LPF/lan1/c0:56:27:6d:20:a7
Sending on   Socket/fallback
DHCPDISCOVER on lan1 to 255.255.255.255 port 67 interval 5
[   34.340362][    T5] mv88e6085 f1072004.mdio-mii:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   35.813842][ T2879] mv88e6085 f1072004.mdio-mii:00 lan2: configuring for phy/gmii link mode
[   35.828564][ T2879] 8021q: adding VLAN 0 to HW filter on device lan2
[   35.899840][ T2917] mv88e6085 f1072004.mdio-mii:00 lan3: configuring for phy/gmii link mode
[   35.915346][ T2917] 8021q: adding VLAN 0 to HW filter on device lan3
[   35.987604][ T2955] mv88e6085 f1072004.mdio-mii:00 lan4: configuring for phy/gmii link mode
[   36.001084][ T2955] 8021q: adding VLAN 0 to HW filter on device lan4
[   36.072828][ T2993] mv88e6085 f1072004.mdio-mii:00 wan: configuring for phy/gmii link mode
[   36.088257][ T2993] 8021q: adding VLAN 0 to HW filter on device wan
DHCPDISCOVER on lan1 to 255.255.255.255 port 67 interval 8
DHCPREQUEST of 192.168.1.112 on lan1 to 255.255.255.255 port 67
DHCPOFFER of 192.168.1.112 from 192.168.1.2
DHCPACK of 192.168.1.112 from 192.168.1.2
bound to 192.168.1.112 -- renewal in 8739 seconds.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
[ ok ] Setting up ALSA...done (none loaded).
[ ok ] Setting sensors limits...done.
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Starting Squeezebox client: squeezelite.
[....] Starting enhanced syslogd: rsyslogd[   37.223252][ T3306] NFSD: starting 90-second grace period (net f0000039)
. ok
[ ok ] Exporting directories for NFS kernel daemon....
[....] Starting NFS kernel daemon: nfsd mountdrpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
. ok
[ ok ] Starting MD monitoring service: mdadm --monitor.
[ ok ] Starting automount....
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting S.M.A.R.T. daemon: smartd.
[ ok ] Starting NTP server: ntpd.
[ ok ] Running local boot scripts (/etc/rc.local).

Debian GNU/Linux 9 trunks ttyS0

trunks login:

$ free
              total        used        free      shared  buff/cache   available
Mem:           506M        102M        294M        245K        109M        353M
Swap:          1.0G          0B        1.0G


$ dmesg |grep rtc
[Mon Sep  2 19:22:28 2019] armada38x-rtc f10a3800.rtc: registered as rtc0
[Mon Sep  2 19:22:28 2019] armada38x-rtc f10a3800.rtc: setting system clock to 2019-09-02T23:19:15 UTC (1567466355)


$ cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00020000 "uboot"
mtd1: 00040000 00020000 "u_env"
mtd2: 00040000 00020000 "s_env"
mtd3: 00100000 00020000 "devinfo"
mtd4: 02800000 00020000 "kernel"
mtd5: 02200000 00020000 "rootfs"
mtd6: 02800000 00020000 "alt_kernel"
mtd7: 02200000 00020000 "alt_rootfs"
mtd8: 05000000 00020000 "ubifs"
mtd9: 02600000 00020000 "syscfg"

$ cat /proc/cmdline
console=ttyS0,115200 init=/sbin/init root=LABEL=WRT rootdelay=10 mtdparts=pxa3xx_nand-0:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) earlyprintk=serial ipv6.disable=1

$ ls -l /sys/class/leds/
total 0
lrwxrwxrwx 1 root root 0 Sep  2 19:24 caiman:white:power -> ../../devices/platform/gpio-leds/leds/caiman:white:power
lrwxrwxrwx 1 root root 0 Sep  2 19:24 caiman:white:sata -> ../../devices/platform/gpio-leds/leds/caiman:white:sata



I also tried your new 5.2.9 kernel, but I got this (with the new DTB): 

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: invalid dtb and unrecognized/unsupported machine ID
  r1=0x00000210, r2=0x00ff8000
  r2[]=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Available machine support:

ID (hex)        NAME
ffffffff        Generic DT based system
ffffffff        Marvell Berlin
ffffffff        Marvell Armada 39x (Device Tree)
ffffffff        Marvell Armada 380/385 (Device Tree)
ffffffff        Marvell Armada 375 (Device Tree)
ffffffff        Marvell Armada 370/XP (Device Tree)
ffffffff        Marvell Dove

Please check your kernel config and/or bootloader.

Thank you
fsonnlei
↧
Search

Re: Debian on wrt1200ac

September 2, 2019, 5:40 pm
$
0
0
fsonnlei,

> Sorry for the delay (busy week) and for the
> confusion regarding stock vs mainline kernel.

Not at all!

> My box is WRT1200AC v1. Testing the new
> dtb:

> 
> $ dmesg |grep rtc
> [Mon Sep  2 19:22:28 2019] armada38x-rtc
> f10a3800.rtc: registered as rtc0
> [Mon Sep  2 19:22:28 2019] armada38x-rtc
> f10a3800.rtc: setting system clock to
> 2019-09-02T23:19:15 UTC (1567466355)
>

Cool! so to activate RTC, I will release a new version of the DTS in the next kernel and call it WRT1200AC v1.


Quote

> I also tried your new 5.2.9 kernel, but I got this
> (with the new DTB):

> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> Error: invalid dtb and unrecognized/unsupported
> machine ID
> r1=0x00000210, r2=0x00ff8000
> r2[]=00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00
> Available machine support:
>
> ID (hex) NAME
> ffffffff Generic DT based system
> ffffffff Marvell Berlin
> ffffffff Marvell Armada 39x (Device Tree)
> ffffffff Marvell Armada 380/385 (Device
> Tree)
> ffffffff Marvell Armada 375 (Device Tree)
> ffffffff Marvell Armada 370/XP (Device
> Tree)
> ffffffff Marvell Dove
>
> Please check your kernel config and/or
> bootloader.
> [/code]


The error is because of the kernel image size was increased. See my release note:

Quote

Updated 20 Aug 2019:

Kernel linux-5.2.9-mvebu-tld-1 package has been uploaded.

New in this release:

- Keep MTD and NAND drivers as builtin kernel drivers (to overcome a mainline kernel regression for MTD and NAND).
- Pickup security patches from mainline.

Important Note for all boxes: The new kernel zImage has increased in size significantly that it will no longer work to be used in booting with the Marvell u-boot typically installed in these Armada boxes. To make it more resilient (avoid messing with u-boot envs again when the kernel image size increases), from this kernel version, we need to boot with uImage. Please see this post for an example how to adjust u-boot envs using the Thecus N2350

So you need to create the /boot/uImage and then adjust your u-boot envs: 

Marvell>> setenv bootargs console=ttyS0,115200 init=/sbin/init root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial ipv6.disable=1
Marvell>> dhcp
Marvell>> tftpboot 0x02000000 wrt/test/iImage
Marvell>> tftpboot 0x2900000 wrt/test/uInitrd
Marvell>> setenv fdt_skip_update yes
Marvell>> bootm 0x02000000 0x2900000
↧

Re: Debian on wrt1200ac

September 2, 2019, 5:54 pm
$
0
0
Perfect! 

$ uname -a
Linux trunks 5.2.9-mvebu-tld-1 #1 SMP PREEMPT Mon Aug 19 12:47:39 PDT 2019 armv7l GNU/Linux

Thank you
fsonnlei
↧
↧

Basic steps in building Linux modules

September 2, 2019, 9:54 pm
$
0
0
I have this post written up so it can be linked to when users have problem building modules with my released kernel. A few users have got around a minor problem caused by apt-get and/or dpkg to build modules successfully. Below is a more detailed explanation.


In general, here is what we need to do to build modules. I'm using linux-headers-5.2.9-kirkwood-tld-2 kernel as an example. 

apt-get install build-essential
apt-get install linux-headers-5.2.9-kirkwood-tld-2_2.0_armel.deb

Now at this point, the kernel header has been installed:

ls -l /usr/src 
drwxr-xr-x 23 root root 4096 Sep  2 19:25 linux-headers-5.2.9-kirkwood-tld-2

Note that the build folder is not created by apt-get install command above. This is a quirk with apt-get/dpkg. The build folder will be created only if you install the kernel and headers at the same time.

For example, this command will install both kernel and headers, and then create a symlink to the headers folder at the same time. 
dpkg -i linux-image-5.2.9-kirkwood-tld-1_1.0_armel.deb linux-headers-5.2.9-kirkwood-tld-2_2.0_armel.deb

But when you install the kernel only, and then install the headers later, it will not create that symlink. So we have to do it manually: 
ln -s /usr/src/linux-headers-5.2.9-kirkwood-tld-2/ /lib/modules/5.2.9-kirkwood-tld-2/build

Double check it:

ls -l /lib/modules/5.2.9-kirkwood-tld-2/ 
lrwxrwxrwx  1 root root     44 Sep  2 19:28 build -> /usr/src/linux-headers-5.2.9-kirkwood-tld-2/

At this point you can proceed and build modules. The build enviroment has been set up properly.


When you build a particular module, that will also have its own build environment setup requirements. Things such as makefile or scripts, will be specific to that source code. If the build fails, you will need to investigate that particular source and it's makefile/scripts to see if the build paths were set up propoerly.
↧

Re: Compile wireless driver rtl8188eu

September 2, 2019, 9:58 pm
↧

Re: Basic steps in building Linux modules

September 2, 2019, 10:35 pm
$
0
0
Hi,

Thanks for the great tutorial. It's indeed the basic setup for building a module.



However in many cases. It's seems we missed something more than just a soft link.
https://forum.doozan.com/read.php?2,76709,87984
https://forum.doozan.com/read.php?2,18152,51209#msg-51209

Somehow these two different modules are all missed 
#include <sys/socket.h>

And as racic said
Quote
racic
The sys/socket.h however sits within /usr/include/arm-linux-gnueabi folder.
If I modify Makefile to include that, the features.h is missing, when I include the /usr/include folder I get tons of messages warning of types redefinitions.

Did you have any clue about what cause it?

Thank you!
↧
Viewing all 26623 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>