Debian on Action Tech SG200 and MI424WR-rev-I

bodhi,

My uboot doesn't support usb.

8086k

8086k,

> My uboot doesn't support usb.

It has tftp boot?

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

bodhi,

Yes, it have tftpboot. I think either put the kernel in the NAND or use tftp to boot it is possible. but I don't know how to do it. I'm new to embedded debian. I think I also need to know how to compile the debian kernel.

Can you help me read F660's stock log? There are some PCI-E configurations there. I can't tell the differences of PCI-E devices between these two boxes.

8086k



Edited 1 time(s). Last edit at 05/24/2021 08:35AM by 8086k.

bodhi,

I used lspci on f660 stock firmware and get this. Is it helpful?

root@F660:/ # ./pci -vv
01:01.0 Class 0280: Device 10ec:8191 (rev 01)
        Subsystem: Device 10ec:8191
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 24
        Region 0: I/O ports at 10000000100000 [size=256]
        Region 2: Memory at f4000000f4000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
                        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
                         EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
        Capabilities: [100 v1] #10ec
        Capabilities: [818 v0] Power Budgeting <?>
        Capabilities: [f40 v3] #5001
        Kernel driver in use: RTL8192C-RTL8188C
lspci: Unable to load libkmod resources: error -12

8086k

> Yes, it have tftpboot. I think either put the
> kernel in the NAND or use tftp to boot it is
> possible. but I don't know how to do it.


See the Wiki thread

Quote
https://forum.doozan.com/read.php?2,23630
Booting Debian on Pogoplug

How to set up U-Boot for booting in multiple drives configuration
Backup and Restore NAND mtds
UART Booting HowTo for Selected Kirkwood Devices
Migrating from Arch to Debian?
How to boot new Debian rootfs using stock u-boot tftp - Pogo E02

> I'm new
> to embedded debian. I think I also need to know
> how to compile the debian kernel.
>

Just use my kernel release to test. No need to build.

> Can you help me read F660's stock log?

That lspci output above does not have anything useful regarding the problem.

The only way I can help you with PCIe activation is if you are running the same Debian kernel and rootfs as I am.

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

bodhi,

If possible, please post the lspci -vv output in mi424wr rev i's stock firmware. I want to compare them to see if there are differences. At the same time, I am trying to run debian on it.

If you use my binary, so much the better.

8086k



Edited 1 time(s). Last edit at 05/25/2021 04:48AM by 8086k.

bodhi,

The I/O port address and PCI-E memory address from lspci are different from current dtsi. So I doubt it uses a different range for PCI-E device. But I'm not sure whether new kernel and old kernel use different configuration logic. So I need to know lspci output in linux 2.6 kernel of MI424WR-REV-I. Thanks for reading.

8086k

8086k,

The MI424WR-rev-I runs OpenRG.

OpenRG system shell gets me to Linux busybox, so I can browse the rootfs and execute some Linux shell commands. Unfortunately they did not include lspci in this system. There is no other way to get PCIe information that I can find in this box.

=====

BTW, I'm taking timeout from this topic to do other things more important. Good luck with the F660!

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

bodhi,

Quote
8086k
bodhi,

If possible, please post the lspci -vv output in mi424wr rev i's stock firmware. I want to compare them to see if there are differences. At the same time, I am trying to run debian on it.

If you use my binary, so much the better.

8086k



Edited 1 time(s). Last edit at 05/25/2021 05:48PM by 8086k.
Edit Reply Quote Report
Attachments:
open | download - lspci.7z (96.3 KB)

Run lspci on MI424WR REVI is easy. F660 also doesn't contain lspci. I copies the binary and necessary libs from openwrt and packs into lspci.7z in previous post. You can just download it, copy the libs to /lib and copy lspci to anywhere you want and run it. Then it will work.

There is a tip I want to share. If you can't use chmod, you can copy any original executable (e.g. busybox) in /bin to the same directory as your new executable. Then run 'cat /lspci > /busybox'. Finally, run busybox that you copied.

8086k



Edited 1 time(s). Last edit at 05/28/2021 07:20PM by 8086k.

8086k,

> open | download - lspci.7z (96.3 KB)

I see, I did not notice that you've posted the binary.

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

> Run lspci on MI424WR REVI is easy. F660 also
> doesn't contain lspci. I copies the binary and
> necessary libs from openwrt and packs into
> lspci.7z in previous post. You can just download
> it, copy the libs to /lib and copy lspci to
> anywhere you want and run it. Then it will work.

Actually you don't really need to do all that. Just make sure the binary is static and from a kernel that circa the version you are running (in the old day it is Debian Squeeze).

https://forum.doozan.com/read.php?3,27280

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

bodhi,

I get it. But compiling it again costs me a lot of time. So I decide to use the one compiled with openwrt. Can you run it and post the output? Thank you.

8086k

bodhi,

I have discovered F660's uboot doesn't initialize eth devices during autoboot. Official kernel can initialize eth devices but kernel3.14 can't. So hacking uboot is impossible. I'd rather boot linux manually each time. Although I have found the way to run bootcmd during autoboot, the ethernet devices doesn't work.

8086k

8086k,

Sorry I can't help you. While in stock OS, I don't have wifi/ethernet connection. And I can't not get access to USB drive either.

@bkallus and Dave,

Perhaps you guys can help?

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

bodhi,

I think I don't need help anymore. I have read the source code of mi424wr and found the problem. I'm surprised that Claudio made so many mistakes in the dts. Mbus NAND memory range is wrong. When I finish, I will post my dts.

8086k

> I think I don't need help anymore. I have read the
> source code of mi424wr and found the problem. I'm
> surprised that Claudio made so many mistakes in
> the dts. Mbus NAND memory range is wrong. When I
> finish, I will post my dts.

No, I do not think he made any mistake regarding NAND.

What you found probably the differences between your box and the MI242WR rev I.

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



Edited 1 time(s). Last edit at 05/29/2021 09:26PM by bodhi.

bodhi,

Please read mvsyshwconfig.h and kirkwood.h in the linux kernel 3.14. NAND addr should be 0xf8000000. PEX0 addr should be 0xf3000000 and PEX1 addr should be 0xf4000000. And maybe crypto address should be 0xf2200000.

8086k

NANd is working fine in my MI424WR-rev-I box running kernel linux-5.12.6-kirkwood-tld-1.

See the DTS tarball I've uploaded most recently in this thread.

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

bodhi,

I found that crypto address is 0xF2200000. Size is 2M(0x00200000). Maybe this will fix the crypto device?

Maybe NAND driver can scan the device itself. I changed the NAND reg and it works fine as well.

PCI-E is different. Maybe Claudio didn't care about it and just make PCI-E port 1 work, port 2 doesn't work. I don't know how to convert the old config to DT values.

/* PEX */
#define PEX0_MEM_BASE		0xF3000000
#define PEX0_MEM_SIZE		_16M

#define PEX1_MEM_BASE		0xF4000000
#define PEX1_MEM_SIZE		_16M

#define CRYPT_ENG_BASE(chan) 		(0xF2200000 + (chan * 0x200000))
#define CRYPT_ENG_SIZE	_2M

/* Internal registers: size is defined in Controllerenvironment */
#define INTER_REGS_BASE	0xF1000000

#define DDR_OPERATION_BASE	(INTER_REGS_BASE | 0x1418)

#define PEX0_IO_BASE	0xF2000000
#define PEX0_IO_SIZE	_1M

#define PEX1_IO_BASE		0xF2100000
#define PEX1_IO_SIZE		_1M

#define SPI_CS_BASE		0xF0000000
#define SPI_CS_SIZE	_16M

#define PNC_BM_PHYS_BASE	0xF5000000
#define PNC_BM_SIZE		_1M

#define PMT_GIGA_PHYS_BASE      0xf5100000
#define PMT_PON_PHYS_BASE       0xf5200000
#define PMT_MEM_SIZE            _1M

/* Device Chip Selects */
#define BOOTDEV_CS_BASE	0xFF800000
#define BOOTDEV_CS_SIZE _8M

/* NAND/NOR Flash */
#define NAND_NOR_CS_BASE	0xF8000000
#define NAND_CS_SIZE		_2M
#define NOR_CS_SIZE		_128M

/* CS2 - BOOTROM */
#define DEVICE_CS2_BASE 0xFF900

from mvsyshwconfig.h

8086k



Edited 1 time(s). Last edit at 05/30/2021 03:59AM by 8086k.

8086k,

I'm not interested in kernel 3.14. I'm at 5.12.6 :)

For the record, I think Claudio's DTS patch set is quite good (no mistake). You had a wrong read of the code, and then too quick to say this "I'm surprised that Claudio made so many mistakes in the dts. Mbus NAND memory range is wrong". Advice: You should always think that your understanding might be wrong first.

The only things I changed in his DTS were newer binding and syntax to work with the latest kernel 5.11.x and later with 5.12.x.

The reason Ethernet is not working now in 5.12.x is some internal kernel changes during 3.14+ to later kernels.

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

bodhi,

DTS nodes except ethernet should be the same in these kernels.
Maybe I'm wrong, I will do more research.

8086k

bodhi,

Maybe PCI-E is not initialized in U-BOOT? This time I read the log of F660 and MI424WR-revI. Mainline linux can't initialize some of the devices in 88f6560. This is hard to solve. I don't think I am able to port the initial code to mainline linux.

8086k

8086k,

> Maybe PCI-E is not initialized in U-BOOT?

Most likely. Usually stock u-boot does not have the correct Wifi driver so you won't see PCIe activated. During boot, they don't care because Ethernet is working.

With modern u-boot, some of the Wifi driver are in mainline if it is important enough then somebody has tried to port from Linux source.

> This
> time I read the log of F660 and MI424WR-revI.
> Mainline linux can't initialize some of the
> devices in 88f6560. This is hard to solve. I don't
> think I am able to port the initial code to
> mainline linux.
>

You don't need to port. Just update OpenWrt with the latest Kirkwood kernel or compile it (probably their staging tree). And then compile your DTS to test.

Don't spend lots of time getting 3.14 working, it will be wasted. Upgrading 3.14 to 5.12.x will be a lot of works. Sooner or later, you will need to get to kernel 5.x, because most definitely 3.14 has old security bugs that nobody has backported the fixes.

Since I've proven that the Kirkwood 5.12.x kernel running OK with Wifi (PCIe), USB, LEDs, NAND, all working except Ethernet, you should be able to do the same with OpenWrt. You dont have to run Debian kernel, as long as it is 5.x kernel in OpenWrt, then you will most likely see the PCIe working. If it does not work, then we'll know that there is some real differences between the F660 and MI424WR-revI regarding PCIe.

Once you have the 5.x kernel and can run it with your DTS version (based on my DTS version), then probably the only thing remained to be figured out is Ethernet.

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

bodhi,

I have already moded the latest version of openwrt which is using linux 5.9 to support avanta. I'm using your DTS and PCI-E still don't work, only USB can work. Now ethernet is the only way to connect it to the network.

8086k

8086k,

> I have already moded the latest version of openwrt
> which is using linux 5.9 to support avanta. I'm
> using your DTS and PCI-E still don't work

OK. Sounds like a good time to troubleshoot your PCIe problem.

Boot up with serial console and post

- The entire serial boot log (or at least the entire dmesg log).
- And if you have changed the DTS files in any way, post the "diff -Naur" of the files against my version.
- Attach the kernel .config that you use to build OpenWrt 5.9 here.

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

bodhi,

Now, I'm sure that the PEX issue is caused by uboot, my f660's uboot don't initialize PEX when starting U-Boot, but you can see other avanta and kirkwood devices printing something like ''PEX 0: Root Complex Interface, Detected Link X1''.

For F660, stock linux kernel does the initialization and print
''PEX0 interface detected no Link.
PEX1 interface detected Link X4''
But none of the kernel which is not provided by marvell do the PEX initialization and print something like this. So the PEX device won't work in F660.

BootROM 1.34
Booting from NAND flash
BootROM: Image checksum verification PASSED


U-Boot 2009.08 (Sep 20 2011 - 17:28:41)

CPU:   Feroceon (Rev 1) @ 1200Mhz - LE, L2 @ 400Mhz
       DDR3 @ 400Mhz, TClock @ 200Mhz, P/V ID=7/15
DRAM:  128 MB
       CS 0: base 0x00000000 size 128 MB
       Addresses 26M - 0M are saved for the U-Boot usage.
NAND:  1bit HM ECC, Size: 32 MiB
Modules Detected:
       GPON module detected.
       TDM module.
       Ethernet Switch on MAC0.
       3xFE PHY Module.
       GE-PHY on Switch port #0.
Net:   egiga0 [PRIME], egiga1

I found the function for initializing PCI-E. It is located at mvPex.c. The function name is mvPexInit. How can I call it when linux is booting?

I didn't have much time recently, but I will post the log you want as soon as possible.

8086k



Edited 1 time(s). Last edit at 06/01/2021 09:01AM by 8086k.

bodhi,

I only changed the ethernet node in the DTS, you know it.
As you can see, serial interrupt problem is always here. Serial console is still laggy.

BootROM 1.34
Booting from NAND flash
BootROM: Image checksum verification PASSED
l

U-Boot 2009.08 ( 3月 28 2013 - 16:11:59)

Hit enter to stop autoboot:  0
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=> tftp op23
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.1
Filename 'op23'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################
done
Bytes transferred = 5481001 (53a229 hex)
=> wdtdbg watchdog 0
disable watchdog
=> bootm
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   ARM OpenWrt Linux-5.4.119
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5480937 Bytes =  5.2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
----------------------
|-->setup start tag...
----------------------
|-->setup memory tag...
----------------------
|-->setup cmdline tag...
----------------------
|-->setup marvell tag...
----------------------
|-->setup versioninfo tag...
----------------------
|-->setup end tag...
----------------------

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.119 (user@ubuntu) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16090-bbbc01ede5)) #0 Mon May 24 08:36:28 2021
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: ZTE F660
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32480
[    0.000000] Kernel command line: console=ttyS0,115200n8 earlyprintk
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 111924K/131072K available (4985K kernel code, 172K rwdata, 1376K rodata, 10240K init, 206K bss, 19148K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x2d4/0x4fc with crng_init=0
[    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.000030] Switching to timer-based delay loop, resolution 5ns
[    0.000101] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000116] pid_max: default: 32768 minimum: 301
[    0.000287] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000302] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001031] CPU: Testing write buffer coherency: ok
[    0.001619] Setting up static identity map for 0x100000 - 0x10003c
[    0.001806] mvebu-soc-id: MVEBU SoC ID=0x6560, Rev=0x2
[    0.004728] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.004751] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.004846] pinctrl core: initialized pinctrl subsystem
[    0.005568] NET: Registered protocol family 16
[    0.005908] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.006687] cpuidle: using governor ladder
[    0.006967] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[    0.006976] Feroceon L2: Cache support initialised.
[    0.009645] No ATAGs?
[    0.028981] SCSI subsystem initialized
[    0.029933] usbcore: registered new interface driver usbfs
[    0.029991] usbcore: registered new interface driver hub
[    0.030086] usbcore: registered new device driver usb
[    0.030255] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[    0.033179] clocksource: Switched to clocksource orion_clocksource
[    0.033916] thermal_sys: Registered thermal governor 'step_wise'
[    0.034160] NET: Registered protocol family 2
[    0.034291] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.034732] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.034767] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.034790] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.034811] TCP: Hash tables configured (established 1024 bind 1024)
[    0.034896] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.034923] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.035117] NET: Registered protocol family 1
[    0.035152] PCI: CLS 0 bytes, default 32
[    0.174110] workingset: timestamp_bits=14 max_order=15 bucket_order=1
[    0.180093] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.180105] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.185628] kirkwood-pinctrl f1018000.pinctrl: registered pinctrl driver
[    0.186571] mvebu-pcie mbus:pcie@82000000: PCI host bridge to bus 0000:00
[    0.186591] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.186604] pci_bus 0000:00: root bus resource [mem 0xf3000000-0xf3ffffff]
[    0.186615] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.186750] pci 0000:00:02.0: [11ab:6500] type 01 class 0x060400
[    0.186785] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    0.187989] PCI: bus0: Fast back to back transfers disabled
[    0.188005] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.189178] PCI: bus1: Fast back to back transfers enabled
[    0.189196] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.189404] pci 0000:00:02.0: BAR 6: assigned [mem 0xf3000000-0xf30007ff pref]
[    0.189419] pci 0000:00:02.0: PCI bridge to [bus 01]
[    0.189810] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.190392] printk: console [ttyS0] disabled
[    0.190479] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A
[    0.656715] printk: console [ttyS0] enabled
[    0.661925] nand: device found, Manufacturer ID: 0xad, Chip ID: 0x75
[    0.668345] nand: Hynix NAND 32MiB 3,3V 8-bit
[    0.672727] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16
[    0.680097] Scanning device for bad blocks
[    0.898817] 2 fixed-partitions partitions found on MTD device orion_nand
[    0.905564] Creating 2 MTD partitions on "orion_nand":
[    0.910733] 0x000000000000-0x000000080000 : "u-boot"
[    0.916429] 0x000000080000-0x000002000000 : "firmware"
[    0.923555] libphy: Fixed MDIO Bus: probed
[    0.928419] libphy: orion_mdio_bus: probed
[    0.938421] mvneta f1070000.ethernet eth0: Using hardware mac address 00:50:43:00:00:01
[    0.946750] i2c /dev entries driver
[    0.950628] thermal thermal_zone0: Temperature sensor reading not valid
[    0.957312] thermal thermal_zone0: failed to read out thermal zone (-5)
[    0.965811] NET: Registered protocol family 10
[    0.975514] Segment Routing with IPv6
[    0.979287] NET: Registered protocol family 17
[    0.984032] 8021q: 802.1Q VLAN Support v1.8
[    0.991010] hctosys: unable to open rtc device (rtc0)
[    0.996800] random: fast init done
[    1.022404] random: crng init done
[    1.170961] irq 22: nobody cared (try booting with the "irqpoll" option)
[    1.177699] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.119 #0
[    1.183558] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    1.189881] [<c0107ef0>] (unwind_backtrace) from [<c0105824>] (show_stack+0x10/0x14)
[    1.197677] [<c0105824>] (show_stack) from [<c014a1e8>] (__report_bad_irq+0x30/0xb4)
[    1.205462] [<c014a1e8>] (__report_bad_irq) from [<c014a3e8>] (note_interrupt+0x108/0x2a0)
[    1.213770] [<c014a3e8>] (note_interrupt) from [<c01479fc>] (handle_irq_event_percpu+0x54/0x64)
[    1.222512] [<c01479fc>] (handle_irq_event_percpu) from [<c0147a34>] (handle_irq_event+0x28/0x3c)
[    1.231431] [<c0147a34>] (handle_irq_event) from [<c014af3c>] (handle_level_irq+0xac/0x11c)
[    1.239825] [<c014af3c>] (handle_level_irq) from [<c0146d04>] (generic_handle_irq+0x20/0x34)
[    1.248306] [<c0146d04>] (generic_handle_irq) from [<c0147294>] (__handle_domain_irq+0x48/0xa8)
[    1.257056] [<c0147294>] (__handle_domain_irq) from [<c03402c8>] (orion_handle_irq+0x68/0x8c)
[    1.265625] [<c03402c8>] (orion_handle_irq) from [<c0101a68>] (__irq_svc+0x68/0x84)
[    1.273316] Exception stack(0xc7831f50 to 0xc7831f98)
[    1.278394] 1f40:                                     e7fddef0 c1200000 c0816d58 009e92a4
[    1.286613] 1f60: 60000053 c05d997c 00000000 00000000 00000000 00000000 00000000 00000000
[    1.294831] 1f80: 000006f9 c7831fa0 c0108a08 c0108cac 20000053 ffffffff
[    1.301485] [<c0101a68>] (__irq_svc) from [<c0108cac>] (free_initmem+0x38/0x74)
[    1.308838] [<c0108cac>] (free_initmem) from [<c05d998c>] (kernel_init+0x10/0x110)
[    1.316448] [<c05d998c>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
[    1.324051] Exception stack(0xc7831fb0 to 0xc7831ff8)
[    1.329127] 1fa0:                                     00000000 00000000 00000000 00000000
[    1.337346] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    1.345562] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    1.352204] handlers:
[    1.354495] [<(ptrval)>] serial8250_interrupt
[    1.358871] Disabling IRQ #22
[    1.397311] Freeing unused kernel memory: 10240K
[    1.402057] Run /init as init process
[    1.760574] init: Console is alive
[    1.774584] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    1.808429] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.817642] ehci-fsl: Freescale EHCI Host controller driver
[    1.825641] ehci-orion: EHCI orion driver
[    1.829853] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.835428] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.843289] orion-ehci f1050000.ehci: irq 24, io mem 0xf1050000
[    1.873210] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.879896] hub 1-0:1.0: USB hub found
[    1.883917] hub 1-0:1.0: 1 port detected
[    1.890654] ehci-platform: EHCI generic platform driver
[    1.900533] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    1.910652] init: - preinit -
[    2.323957] mvneta f1070000.ethernet eth0: cannot request irq 25
ip: SIOCSIFFLAGS: Invalid argument
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
sendto(): Network unreachable
sendto(): Network unreachable
[    6.445527] procd: - early -
[    6.973590] procd: - ubus -
[    7.030854] procd: - init -
Please press Enter to activate this console.
[    7.432048] kmodloader: loading kernel modules from /etc/modules.d/*
[    7.474222] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[    7.536373] Loading modules backported from Linux version v5.10.34-0-g0aa66717f684
[    7.544013] Backport generated by backports.git v5.10.34-1-0-g7b5533e1
[    7.617228] xt_time: kernel timezone is -0000
[    7.718620] urngd: v1.0.2 started.
[    7.731134] PPP generic driver version 2.4.2
[    7.744170] NET: Registered protocol family 24
[    7.813512] kmodloader: done loading kernel modules from /etc/modules.d/*
[   23.110491] mvneta f1070000.ethernet eth0: cannot request irq 25
[   23.219715] br-lan: port 1(eth0) entered blocking state
[   23.225017] br-lan: port 1(eth0) entered disabled state
[   23.230542] device eth0 entered promiscuous mode



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

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 21.02-SNAPSHOT, r16099-d9603bbd3e
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# cat /proc/interrupts
           CPU0
 17:       9551  bridge-interrupt-ctrl   2 Edge      orion_event
 22:     100000  interrupt-controller@20200  33 Edge      ttyS0
 24:          0  interrupt-controller@20200  23 Edge      ehci_hcd:usb1
 26:          1  interrupt-controller@20200   4 Edge      f1072004.mdio-bus
 27:          1  f1018100.gpio  27 Edge      gpio_keys
 28:          1  f1018100.gpio  13 Edge      gpio_keys
Err:          0

8086k

8086k,

The PCIe is fine:

[    0.186571] mvebu-pcie mbus:pcie@82000000: PCI host bridge to bus 0000:00
[    0.186591] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.186604] pci_bus 0000:00: root bus resource [mem 0xf3000000-0xf3ffffff]
[    0.186615] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.186750] pci 0000:00:02.0: [11ab:6500] type 01 class 0x060400
[    0.186785] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    0.187989] PCI: bus0: Fast back to back transfers disabled
[    0.188005] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.189178] PCI: bus1: Fast back to back transfers enabled
[    0.189196] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.189404] pci 0000:00:02.0: BAR 6: assigned [mem 0xf3000000-0xf30007ff pref]
[    0.189419] pci 0000:00:02.0: PCI bridge to [bus 01]

But you don't have the driver module in the kernel configuration. You need to add CONFIG_RTL8192CE to be in kernel or loadable.

CONFIG_RTL8192CE=y

or loadable

CONFIG_RTL8192CE=m

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

bodhi,

I have added the kmod in openwrt config. And I can see it is loaded using lsmod. It doesn't find the device so there is no log. I think it's worth adding the initialization function to the kernel.

Quote
8086k
Now, I'm sure that the PEX issue is caused by uboot, my f660's uboot don't initialize PEX when starting U-Boot, but you can see other avanta and kirkwood devices printing something like ''PEX 0: Root Complex Interface, Detected Link X1''.

8086k

8086k,

THe Openwrt log seems to abbreviate a lot of info. Here is my MI424WR log

Try setting your kernel log level to 7.

root@mi424:~# dmesg | grep -i pci

[    6.919895] PCI: CLS 0 bytes, default 32
[    9.652883] mvebu-pcie mbus:pcie@82000000: host bridge /mbus/pcie@82000000 ranges:
[    9.661193] mvebu-pcie mbus:pcie@82000000: Parsing ranges property...
[    9.661232] mvebu-pcie mbus:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    9.670556] mvebu-pcie mbus:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    9.679857] mvebu-pcie mbus:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    9.689179] mvebu-pcie mbus:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    9.699015] mvebu-pcie mbus:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    9.708851] mvebu-pcie mbus:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    9.718678] mvebu-pcie mbus:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    9.728764] mvebu-pcie mbus:pcie@82000000: PCI host bridge to bus 0000:00
[    9.736257] pci_bus 0000:00: root bus resource [bus 00-ff]
[    9.742449] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    9.753304] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    9.764159] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    9.775011] pci_bus 0000:00: root bus resource [mem 0xf3000000-0xf3ffffff]
[    9.782578] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    9.789524] pci_bus 0000:00: scanning bus
[    9.789636] pci 0000:00:01.0: [11ab:6560] type 01 class 0x060400
[    9.796363] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    9.804952] pci_bus 0000:00: fixups for bus
[    9.804972] PCI: bus0: Fast back to back transfers disabled
[    9.811253] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[    9.811271] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    9.819965] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[    9.820135] pci_bus 0000:01: scanning bus
[    9.820189] pci 0000:01:00.0: [168c:002e] type 00 class 0x028000
[    9.826893] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x4000ffff 64bit]
[    9.834507] pci 0000:01:00.0: supports D1
[    9.839203] pci 0000:01:00.0: PME# supported from D0 D1 D3hot
[    9.845651] pci 0000:01:00.0: PME# disabled
[    9.870881] pci_bus 0000:01: fixups for bus
[    9.870900] PCI: bus1: Fast back to back transfers disabled
[    9.877150] pci_bus 0000:01: bus scan returning with max=01
[    9.877165] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    9.884486] pci_bus 0000:00: bus scan returning with max=01
[    9.884673] pci 0000:00:01.0: BAR 14: assigned [mem 0xf3000000-0xf30fffff]
[    9.892254] pci 0000:00:01.0: BAR 6: assigned [mem 0xf3100000-0xf31007ff pref]
[    9.900177] pci 0000:01:00.0: BAR 0: assigned [mem 0xf3000000-0xf300ffff 64bit]
[    9.908169] pci 0000:00:01.0: PCI bridge to [bus 01]
[    9.913838] pci 0000:00:01.0:   bridge window [mem 0xf3000000-0xf30fffff]
[    9.921400] pcieport 0000:00:01.0: assign IRQ: got 0
[    9.921423] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[    9.928206] pcieport 0000:00:01.0: enabling bus mastering
[   10.206804] ehci-pci: EHCI PCI platform driver
[   30.518941] pci 0000:00:01.0: enabling bus mastering

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



Edited 1 time(s). Last edit at 06/01/2021 07:52PM by bodhi.