jakogut has quit [Read error: Connection reset by peer]
jakogut_ is now known as jakogut
<memeka>
brads: I had issues with your config (using Image.gz and ramdisk like the HK image) i think because the kernel was too big - roughly having Image.gz > 7MB => would not boot ...
sundersnegi has joined #linux-amlogic
<memeka>
did you encouter that?
sundersnegi has quit [Ping timeout: 250 seconds]
<brads>
memeka: nice work! Im only using an uncompressed uImage + dtb but have had 25Mb+ kernel with some heavy debug enabled.
_whitelogger has joined #linux-amlogic
<narmstrong>
memeka: which kernel is this ? 4.9 ?
<narmstrong>
memeka: if it’s 5.1 it’s really good :-)
<narmstrong>
Ok it is, I will send the patches upstream then :-)
<memeka>
narmstrong: you can see in screenshot in terminal
<memeka>
It’s 5.1
<memeka>
:)
<narmstrong>
memeka: the screenshots were too small, I managed to get them bigger, and it’s pretty cool !
<memeka>
narmstrong: any idea about the monitor issue? Tried both hdmi-dvi cable and hdmi-vga adapter, all looks good, edid is read correctly etc but no image
<memeka>
It works on c2 kernel 4.19 and others
ldevulder_ is now known as ldevulder
<narmstrong>
Update to the new branch, I fixed an issue
<narmstrong>
ok, stupid me, I should have checked before
<vagrantc>
they might get selected because of other configuration options
<vagrantc>
and so not be in debian's template
<narmstrong>
it was not the case when I opened the debian issue, thanks for pointing it then...
<vagrantc>
it's been there a while...
<vagrantc>
:)
<narmstrong>
vagrantc: I also tried to enable the other boards in u-boot on salsa, I don't know what is the best way, should I still open a debian bug ?
<vagrantc>
narmstrong: you filed merge requests on the u-boot package?
<narmstrong>
vagrantc: yes
<vagrantc>
er, in salsa
<vagrantc>
let me check ... this whole merge request workflow is a bit new in debian :)
<narmstrong>
np, it's not really urgent !
<vagrantc>
narmstrong: those work fine on 2019.01 ? we're deep in freeze, it'd be nice to add them to get support this release :)
<narmstrong>
vagrantc: yes, they work fine for 2019.01
<vagrantc>
apparently, i don't get notices for merge requests...
<narmstrong>
at least this merge request was not useless !
<vagrantc>
narmstrong: since i've seen plenty of regressions in u-boot over time that are board-specific, if you could periodically test the debian u-boot builds of those boards, it'd be appreciated
<memeka>
narmstrong: so s922 needs a completely new cpufreq driver, or can it be derived from older soc?
<narmstrong>
memeka: we need to implement it like it was done for meson8 by xdarklight, I have a very initial implementation but it’s not on my todo list right now, and only for g12a
<narmstrong>
The work is essentially in the clock driver
<memeka>
Right so it should be pretty different from the others
<memeka>
Currently is set by uboot right?
<memeka>
The freq I mean
CyberManifest has joined #linux-amlogic
<CyberManifest>
Can someone please help me get WiFi Working on a Khadas VIM2 Max with Armbian? I tryed: 'sudo modprobe wifi_dummy' and 'sudo modprobe dhd' as suggested here: https://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825 but I get a Fatal Error saying the modules can't be found
vagrantc has quit [Quit: leaving]
vagrantc_ is now known as vagrantc
vagrantc_ has joined #linux-amlogic
<CyberManifest>
anybody... ?
vagrantc_ has quit [Quit: leaving]
sputnik_ has joined #linux-amlogic
vagrantc_ has joined #linux-amlogic
afaerber has joined #linux-amlogic
<memeka>
CyberManifest: better ask in armbian forums
CyberManifest has quit [Remote host closed the connection]
sputnik_ has quit [Read error: Connection reset by peer]
<memeka>
narmstrong: i could boot 5.1-rc1 from the integ branch, but still no monitor for me :(