danitool_ has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
rmilecki has joined #openwrt-devel
nitroshift has joined #openwrt-devel
glbp has joined #openwrt-devel
ZeroChaos has joined #openwrt-devel
Zero_Chaos has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
Tusker has quit [Ping timeout: 480 seconds]
robin_ has joined #openwrt-devel
Tusker has joined #openwrt-devel
abiliomarques has joined #openwrt-devel
<robin_>
hi, i'm trying to run openwrt on the phyboard mira (imx6). i can boot the kernel from barebox, but i have trouble mounting the (attached) ubi0:root partition: VFS: Cannot open root device "ubi0:root" or unknown-block(0,0): error -2. Please append a correct "root=" boot option; here are the available partitions: *mtdblock{0,2}*. Does this indicate the root partition is not found/detected or "malformed"?
<robin_>
PaulFertser, I reuse the existing mtd schema and replace the ubi partition via barebox
<PaulFertser>
robin_: is there anything special with your OpenWrt (including kernel) config?
<PaulFertser>
robin_: I see one potential source of confusion: you have a NAND partition named "root" and you have the ubi volume named "root". By default OpenWrt is using name "rootfs" for the root filesystem ubi partition.
<PaulFertser>
robin_: so when reading the log it's hard to tell what's happening because of that.
<robin_>
PaulFertser, no special kernel config. the target is derived from the ventana family.
<robin_>
PaulFertser, thanks, i'll look into it
<PaulFertser>
robin_: another thing I would do: booting the very same kernel but with initramfs so that I would have all the userspace ubi tools to inspect the ubi state.
<PaulFertser>
robin_: OpenWrt can automatically pack everything you need in initramfs.
<PaulFertser>
robin_: https://termbin.com/x9tmr from my device. See the next to the last line, somehow it creates ubiblock for me but not for you.
<mrkiko>
PaulFertser: and how do I deduce this from a running system?
<mrkiko>
PaulFertser: I am in the process of porting ar71xx device to ath79
<PaulFertser>
robin_: are you sure you have "CONFIG_MTD_UBI_BLOCK=y" in your kernel config?
<PaulFertser>
mrkiko: it's probably mentioned in dmesg and somewhere in /sys/kernel/debug
<PaulFertser>
And probably also in bootloader output
<robin_>
PaulFertser, CONFIG_MTD_UBI_BLOCK=y is set
<robin_>
PaulFertser, I'll rename the partition and check
<mrkiko>
PaulFertser: I've seen this [ 0.000000] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000MHz
<mrkiko>
which made me think the default was ok
<PaulFertser>
mrkiko: so that's your ref, same 40 MHz as default.
<PaulFertser>
robin_: yes, better to not break that OpenWrt assumption, it has some special handling for "rootfs" by default.
<mrkiko>
PaulFertser: I seen it yesterday, but wasn't sure. And I didn't want to convince myself without a valid reason it was right.
<mrkiko>
PaulFertser: in my DTS I have ethernet and NAND somehow configured. Maybe it's enough to try to bootstrap the new system and go ahead from there?
<PaulFertser>
mrkiko: I always prefer going with initramfs first if at all possible.
<mrkiko>
PaulFertser: yes, agree
<PaulFertser>
robin_: with normal OpenWrt build you do not need to specify root= at all, the partition should be found by name matching.
<mrkiko>
PaulFertser: so, the bootloader doesn't allow me to boot entirely from RAM. and it's a netgear board, so it accepts a specific image format.
<PaulFertser>
mrkiko: if it's easy and fast to reflash you can try flashing normal squashfs image and proceed from that.
<PaulFertser>
mrkiko: but take care to back up calibration data first
<mrkiko>
PaulFertser: yes, it's kinda easy. that said, when you can boot entirely from ram it's much easier. :)
<mrkiko>
PaulFertser: I did backup the entire system while it was running ar71xx port
<aiyion>
mrkiko: I have a matching number using 'cat /sys/kernel/debug/clk/ref/clk_rate'
<PaulFertser>
mrkiko: and keep full dmesg from it handy
<mrkiko>
aiyion: thanks! 'cat'ing it right now
<mrkiko>
PaulFertser: for now I have dmesg, ifconfig, MACs (I built a small table with MAC addresses and notes about the base address, +1, -1, and so on)
<PaulFertser>
robin_: also name your mtd partition "ubi", not "root", then target/linux/generic/pending-5.10/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch will work
<mrkiko>
aiyion: 40000000
<PaulFertser>
robin_: and then target/linux/generic/pending-5.10/491-ubi-auto-create-ubiblock-device-for-rootfs.patch
<mrkiko>
aiyion: thanks a lot, very nice
<PaulFertser>
robin_: so it's all clear now why it doesn't work for you as you want it :)
<aiyion>
mrkiko: remeber to look at that number on the stockimage not what you have currently built; but you likely thought of that.
<PaulFertser>
robin_: the last one is needed if you have squashfs on a ubi volume
<robin_>
PaulFertser, thank you. that makes a lot of sense
<mrkiko>
aiyion: thanks for the suggestion instead; these are the kinds of things that can make it difficult to find problems later on. But yes, that number comes from the ar71xx port of openwrt
<mrkiko>
aiyion: so I am assuming it's correct for now
<aiyion>
nice
<mrkiko>
and then guys, I'll have to think about the LEDs :D
<mrkiko>
at some point. Before we have networking, GPIOs... no UART so ...
james-su has joined #openwrt-devel
<PaulFertser>
mrkiko: without UART you'll be wasting time
goliath has joined #openwrt-devel
<PaulFertser>
Highly likely
james-su has left #openwrt-devel [#openwrt-devel]
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador2 is now known as jlsalvador
rejoicetreat has joined #openwrt-devel
embargo has quit [Ping timeout: 480 seconds]
hitech95 has joined #openwrt-devel
<hitech95>
Hi guys I have a question related to netifd and custom protocols. MAP protocol does not actually assign an IP address to the interface so loopback nat roules are not created to its public IP.
<james-su>
A question about the driver for IPQ6018. Is there any plan to sink driver from Linux mainstream to OpenWRT?
<james-su>
furthermore, do we have any roadmap to support this in coming future? thanks
rejoicetreat has quit [Ping timeout: 480 seconds]
Acinonyx_ has quit [Ping timeout: 480 seconds]
Acinonyx has joined #openwrt-devel
<russell-->
well, this is annoying. my powerbeam fw seems to have a broken network on pbe-m2-400 (runs fine on pbe-m5-400)
<russell-->
i just ordered one to sacrafice the case to, so i can connect to the serial console and see what's happening
aiyion has quit [Remote host closed the connection]
aiyion has joined #openwrt-devel
_lore_ has quit [Ping timeout: 480 seconds]
_lore_ has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
<russell-->
aha!
<slh>
james-su: there are no roadmaps, at all - it happens, once it's ready (or it won't). in practice, getting ipq807x working is pretty much a pre-condition before looking at ipq807x (as it needs a lot of the same hardware), then there's still a lot of driver support missing for ipq60xx in general (and kernel v5.10 in particular), so needing a lot of work - and lastly, ath11k is RAM hungry, which is
<slh>
already a problem on 512 MB RAM ipq807x, but probably even worse on ipq60xx
<russell-->
[ 0.916713] mdio_bus mdio.0: MDIO device at address 4 is missing.
Tapper has joined #openwrt-devel
<russell-->
looks like pbe-m2-400 and pbe-m5-400 are wired differently
dedeckeh has joined #openwrt-devel
hitech95 has quit [Remote host closed the connection]
Tusker has quit [Quit: Time wasted on IRC: 11 hours 12 minutes 41 seconds]
rejoicetreat has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
embargo has joined #openwrt-devel
Rentong has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
Rentong has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 480 seconds]
minimal has joined #openwrt-devel
champtar has joined #openwrt-devel
<champtar>
Hi All, since the switch from ifname to device in the uci network config many packages are broken, is it ok to use 'uci_get_state network "$1" ifname "$1"' or should I use 'network_get_device ifname "$1"'
<champtar>
ie do we want to keep uci_get_state around forever ?
<champtar>
I feel network_get_device is cleaner but it's one more include
goliath has quit [Quit: SIGSEGV]
hitech95 has joined #openwrt-devel
jbowen has joined #openwrt-devel
ephemer0l has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
glbp has quit [Quit: leaving]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
abiliomarques has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
abiliomarques has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
hitech95 has quit [Remote host closed the connection]
danitool has joined #openwrt-devel
Borromini has joined #openwrt-devel
ephemer0l has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
shibboleth has joined #openwrt-devel
shibboleth has quit [Quit: shibboleth]
<ldir>
Could someone look at https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commit;h=bf912bfbb4547497a03c3afdee8a6c7fcbced270 and tell me whether that's a reasonable fix please?
<ldir>
'cos I've been having recursive dep warnings ever since https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commit;h=d8583664415179488dd7b5db5d5813a19b219a55
abiliomarques has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
<slh>
ldir: I think (admittedly without having checked deeper) the conflicts needs to remain