narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
sputnik_ has joined #linux-amlogic
vdehors has quit [Ping timeout: 245 seconds]
vdehors has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 248 seconds]
<lvrp16> alienpirate5: LibreELEC is 32-bit because of some libraries used for Netflix
<alienpirate5> How do I compile a 64 bit kernel that has support for the Amlogic Video Engine?
<lvrp16> the Linux display stack is not mature enough to support hardware video acceleration generically throughout userspace
<lvrp16> there's a lot of ongoing work at the kernel level for generic video support but making it usable generically is still far off because of x11/wayland
<lvrp16> most of the plumbing is still being built from kernel space to userspace
sputnik_ has joined #linux-amlogic
Barada has joined #linux-amlogic
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #linux-amlogic
nashpa has quit [Ping timeout: 246 seconds]
nashpa has joined #linux-amlogic
nashpa has quit [Ping timeout: 244 seconds]
nashpa has joined #linux-amlogic
nashpa has quit [Client Quit]
nashpa has joined #linux-amlogic
ldevulder has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
yann has quit [Ping timeout: 272 seconds]
ldevulder has quit [Ping timeout: 258 seconds]
warpme_ has joined #linux-amlogic
warpme_ has quit [Client Quit]
ldevulder has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 245 seconds]
yann has joined #linux-amlogic
warpme_ has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
yann has quit [Ping timeout: 246 seconds]
warpme_ has joined #linux-amlogic
yann has joined #linux-amlogic
yann has quit [Ping timeout: 244 seconds]
warpme_ has quit [Quit: warpme_]
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
<Xogium> hmm, is it a known issue that if I unplug the network cable ipv6 address becomes unusable on odroid c2 ?
<Xogium> that is, I have a fe80::/10 address lesft, but trying to use it results in network unreachable
<Xogium> when I plug the cable back that is :p
<Xogium> restarting my network manager doesn't help, either
<Xogium> only solution si reboot
<Xogium> *is
nsaenz has quit [Quit: Leaving]
nsaenz has joined #linux-amlogic
<Xogium> that's with 4.19.56 btw
<Xogium> that is with the defconfig for arm64
<Xogium> also, what does this mean ?
<Xogium> rc rc0: two consecutive events of type space
sputnik_ has quit [Ping timeout: 272 seconds]
Darkmatter66 has quit [Ping timeout: 252 seconds]
warpme_ has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
Darkmatter66 has quit [Ping timeout: 246 seconds]
Darkmatter66 has joined #linux-amlogic
afaerber has joined #linux-amlogic
yann has joined #linux-amlogic
<ukleinek> Xogium: fe80::/10 is special
<Xogium> ukleinek: nod, I know that
<Xogium> what I meant is, once I disconnect the cable, then replug it, I can't ping anything that is on a fe80::/10 adress anymore. My router for example
<Xogium> if I don't unplug the cable it's all fine
<Xogium> I mean, if I can't use the fe80:/10 address to ask for a slaac and dhcpv6 address, it's no wonder my ipv6 does not come back
<ukleinek> Xogium: if there are >1 devices with a lladdr you need to qualify the device in the address to ping
<ukleinek> Xogium: (which doesn't mean you don't have a different problem of course)
<Xogium> yeah
<Xogium> weirdly enough only my c2 has that issue
<Xogium> none of my other sbc have that :O
<Xogium> I wonder how I can debug this
<Xogium> all I really know for sure is that my fe80::/10 address stays there but it seems broken, because no matter the way I try to get a slaac address back it doesn't work
<Xogium> dhcpcd times out even
<phh> ipv4 works at that time?
<phh> or it's just that ethernet is plain dead?
<phh> if you do a tshark/tcpdump, do you see any packet incoming?
<Xogium> phh: ipv4 is perfectly alright
<Xogium> I see nothing for v6 at least
<Xogium> not even solicitations
<Xogium> hmm
<Xogium> I lose the route
<Xogium> weird
<Xogium> I'm not supposed to lose that route :p
<Xogium> and readding it doesn't help
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
Barada has quit [Quit: Barada]
warpme_ has joined #linux-amlogic
nsaenz has quit [Read error: Connection reset by peer]
nsaenz has joined #linux-amlogic
Xogium has quit [Quit: Leaving.]
Xogium has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
warpme_ has joined #linux-amlogic
vagrantc has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
Darkmatter66 has quit [Ping timeout: 245 seconds]
Darkmatter66 has joined #linux-amlogic
<xdarklight> saintdev: are you able to compile a kernel for your Odroid-C1 yourself to test something for me?
<xdarklight> saintdev: it seems that https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/commit/?h=v5.3/dt&id=a2c6e82e5341a283b06b04029f952598e445b159 "fixes" the problem you're seeing for me
<xdarklight> (I put "fixes" in suspicious air quotes on purpose because I'm not sure why that is)
<saintdev> xdarklight: I'm on vacation right now, so I won't be able to until next week
<xdarklight> saintdev: enjoy your vacation then - think of my question once you're back and you're getting bored ;)
sputnik_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 248 seconds]
memeka has joined #linux-amlogic
afaerber has quit [Quit: Leaving]
jakogut_ has joined #linux-amlogic
jakogut_ has quit [Read error: Connection reset by peer]
TheAssassin has quit [Ping timeout: 252 seconds]
vdehors has quit [Disconnected by services]
vdehors_ has joined #linux-amlogic
TheAssassin has joined #linux-amlogic