steev | c0rnelius: can confirm that socinfo patch works correctly | 05:53 |
---|---|---|
steev | [ 2.367917] soc soc0: Amlogic Meson G12A (S905Y2) Revision 28:b (30:2) Detected | 05:53 |
c0rnelius | Nice. | 05:57 |
c0rnelius | Did it help the audio though? | 05:57 |
steev | nope :( | 06:32 |
steev | oh also | 06:32 |
steev | i don't think it *truly* matters but | 06:32 |
steev | https://github.com/RPi-Distro/firmware-nonfree/blob/dcea7a3c12490f264033e489f8c6b56032d9f249/debian/config/brcm80211/brcm/brcmfmac43456-sdio.clm_blob works with the radxa zero | 06:34 |
steev | iirc, that's the firmware from the pi400 | 06:34 |
steev | that's the clm_blob for it* | 06:34 |
steev | oh! | 06:36 |
steev | something else you may want to do in your images | 06:37 |
steev | update-alternatives --set regulatory.db /lib/firmware/regulatory.db-upstream | 06:37 |
steev | without that, you get | 06:38 |
steev | cfg80211: loaded regulatory.db is malformed or signature is missing/invalid | 06:38 |
steev | and you can't actually set the regdomain | 06:38 |
c0rnelius | I've seen that before and that's specifically Debian related. | 06:56 |
c0rnelius | I'll look into it thanks for the insight. | 06:56 |
steev | it defaults to debian, because debian kernels and the regdb are signed with the same key, but if your kernel doesn't have the debian key in it.... | 07:02 |
c0rnelius | No my kernel doesn't and I add my own regdb | 15:58 |
c0rnelius | steev: whats the current date of the firmware being used. The one I have for the 400 is a diff size? | 16:15 |
steev | c0rnelius: i specifically mean the clm_blob, not the firmware itself | 16:16 |
steev | but | 16:16 |
steev | [ 10.471563] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84 | 16:16 |
c0rnelius | well thats pretty old. I believe the 400 one is 2020 | 16:17 |
c0rnelius | I could just add the blob and update the *.bin | 16:17 |
steev | i don't know that the bin will work, i haven't tested that, just the clm_blob | 16:21 |
steev | they aren't always compatible | 16:21 |
c0rnelius | Well I can always revert it, if it doesn't work. | 16:23 |
c0rnelius | Rather not be using some 2017 firmware if the 2020 works. | 16:24 |
c0rnelius | you can test it if you want https://github.com/pyavitz/firmware/tree/radxa | 16:25 |
steev | device does come up | 16:29 |
steev | [ 8.242187] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: May 14 2020 17:26:08 version 7.84.17.1 (r871554) FWID 01-3d9e1d87 | 16:29 |
c0rnelius | looks better to me | 16:31 |
c0rnelius | I could probs update the 43430 as well. Thats up to 2021. | 16:37 |
steev | i' | 16:39 |
steev | ve had it work on some devices, and others, just not load properly | 16:39 |
steev | updating the firmware, i mean, even if it's the same number | 16:39 |
c0rnelius | the one i'm currently using on the nanopi neo plus2 is on 2020 firmware. | 16:40 |
c0rnelius | I can't recall now if thats what I used in the radxa branch? I'd have to look. | 16:41 |
steev | i'm showing 2017 on the image you built as well (so stock) | 16:47 |
c0rnelius | size wise it looks like I used the same one for both branches which was the latest I could find that worked from cypress. | 16:52 |
steev | c0rnelius: yeah those work fine; you *could* rename the .bin to brcmfmac43456-sdio.radxa,zero.bin which gets rid of a message that it tries to find that before the generic brcmfmac43456-sdio.bin but the message is harmless | 18:47 |
c0rnelius | my plan was this -> https://github.com/pyavitz/debian-image-builder/blob/feature/patches/rockchip/3399/edge/018-direct-firmware-load-failed-error-2-REVERT-broadcom-firmware-c.patch | 18:50 |
c0rnelius | which reverts firmware.c file | 18:50 |
c0rnelius | I've tested it on the pi and T4 and works just fine for the time being. | 18:51 |
c0rnelius | I need to look through the file proper and just pull out whats checking for that stupid thing. | 18:51 |
c0rnelius | I don't even understand why they changed it? I mean who is gonna do that for every damn board? Its tarded. | 18:53 |
c0rnelius | I don't know what broadcom was thinking there. | 18:55 |
c0rnelius | I believe there is a way to just suppress or ignore which can be added to file. So that if not found it at least doesn't error -2 on you in the dmesg. | 18:58 |
steev | the one other thing you do, that i really like that i need to figure out... is that header patch of your | 19:13 |
steev | i like that it fixes actually having cross compiled headers | 19:13 |
c0rnelius | also fixes GLIBC errors when compiling native. | 19:18 |
c0rnelius | So if compiled on say Ubuntu Jammy which is way ahead of Bullseye it will correct that and recompile the headers so they are useful. | 19:19 |
c0rnelius | its pretty basic, I just place the patch in the source and tell the builddeb what to do with it. | 19:20 |
c0rnelius | https://github.com/pyavitz/debian-image-builder/blob/feature/patches/packaging/general-packaging.patch#L113 | 19:21 |
c0rnelius | Armbian does the same thing, but in reverse. So its patched and compiled during the creation of the kernel. I do it during the install so that it fixes possible complications. | 19:25 |
c0rnelius | For example in this one it checks to see if its arm, and if found is more specific. https://github.com/pyavitz/rpi-img-builder/blob/master/patches/rpi2%2B3-packaging.patch#L115 | 19:27 |
c0rnelius | I tried pointing this out to them at one point but they said I"m doing it wrong or something and just dropped the subject. | 19:28 |
steev | you are doing it correctly | 19:34 |
steev | i'll probably look closer while on vacation | 20:27 |
c0rnelius | I don't know how you guys build ur kernels but it shouldn't be to complicated to add. | 20:37 |
c0rnelius | If someone with no formal training, schooling or a degree in anything computer related such as my self, can do it. I'm sure you got this :) | 20:39 |
steev | i am.... in the same boat as you :P | 21:07 |
steev | but, i just do it as part of the script build, like you do | 21:07 |
steev | in a perfect world, i'd just get the patches in to our kernel proper, but, changing them every few days would mean lots of kernel updates across the board | 21:09 |
Vall | rrq: what would be the correct /etc/apt/sources.list entry to use your pool1 iso as a local repo? | 23:03 |
rrq | I think you use "# apt-cdrom" to add it to the sources list | 23:05 |
Vall | rrq: thanks! I was trying to construct an entry manually and was getting the shaft and not the elevator ;-) | 23:08 |
rrq | this page might be useful: https://wiki.debian.org/DebianInstaller/Modify/CD#Installing_From_the_New_Image | 23:09 |
rrq | .. or a bit further down (especially it might need the "[trusted=yes]" phrase added) | 23:11 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!