DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-allwinner
<DC-IRC> <shivansps> to be fair, its not the one i posted either, it is a chinese clone compatible with the waveshare 3.5" LCD "C"... petty slow too but i dont plan to use it for gaming, i dont think it would be possible anyway outside RPI and the super optimised driver for these slow displays. I dont even know what IC is either, i can see the touch controller that is in fact a XPT2046.
<DC-IRC> <shivansps> to be fair, its not the one i posted either, it is a chinese clone compatible with the waveshare 3.5" LCD "C"... petty slow too ( i dont think it supports the high speed SPI) but i dont plan to use it for gaming, i dont think it would be possible anyway outside RPI and the super optimised driver for these slow displays. I dont even know what IC is either, i can see the touch cont <clipped message>
<DC-IRC> <shivansps> roller that is in fact a XPT2046.
<DC-IRC> <shivansps> to be fair, its not the one i posted either, it is a chinese clone compatible with the waveshare 3.5" LCD "C"... petty slow too ( i dont think it supports the high speed SPI) but i dont plan to use it for gaming, i dont think it would be possible anyway outside RPI and the super optimised driver for these slow displays. I dont even know what IC is either, i can see the touch cont <clipped message>
<DC-IRC> <shivansps> roller that is in fact a XPT2046. But im guessing that, since it works with the waveshare script it is in fact a ILI9486
<DC-IRC> <zwillx> sounds like a challenge for sure haha
<DC-IRC> <zwillx> I'm still trying for 6.6 build on zero2W and I've re-lost the mmc mount
<DC-IRC> <zwillx> [ 2.416245] sunxi-mmc 4021000.mmc: allocated mmc-pwrseq
<DC-IRC> <zwillx> [ 2.640033] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
<DC-IRC> <zwillx> and then that's it lol.
<DC-IRC> <zwillx> are there any particular drivers or kernel configs I should look for? I obv have sunxi mmc, and I copied some from the config.gz of the Opi OS, and put these in the initramfs:
<DC-IRC> <zwillx> /lib/modules/6.6.4-edge-sunxi64/kernel/drivers # ls
<DC-IRC> <zwillx> block cdrom dma mfd mmc scsi
<DC-IRC> <zwillx> but I'm still missing something. I feel a bit stupid because I got this working on 6.1 kernel config lol
<DC-IRC> <zwillx> I noticed the 6.6 kernel deprecated the sdio_spi but that can't be it.. spi is too slow for SD anyway
<DC-IRC> <viraniac> As most of the things are supposed to be common between h616 and h618, I guess it shouldn't be kernel config. Instead the original Armbian kernel config should have worked fine
<DC-IRC> <viraniac> I think the problem may be related to dts
<DC-IRC> <viraniac> Is your code available somewhere? Probably I can take a look
<DC-IRC> <zwillx> interesting! the DTS is the same, but maybe I need to recompile the UBoot or something going from 6.1 to 6.6? The stock DTB/Uboot comes from OPi OS (is 6.1), so dtb/dts and uboot was working well for 6.1
<DC-IRC> <zwillx> let me do a diff on the two config.gz for things selected "=y" between working and non-working SD card and see if I missed something. Thanks 🙂
<DC-IRC> <viraniac> use diffconfig. But do note, there are a lot of configs that have changed between 6.1 and 6.6. So some things will be listed changed even if its not changed by you
<DC-IRC> <viraniac> if you are using git, then probably git diff will give better result
<DC-IRC> <zwillx> I should use git. but it was working and I've had 3 VM crashes/data corruption (now switched to Docker 2 days ago) so it was too much to implement at the time. Nice tip on diffconfig! let me see. My strategy has been - build kernel for pizero2, take modules, add to initramfs/modloop matching necessary modules, and add them to existing SD card w uboot/dts, so I haven't integra <clipped message>
<DC-IRC> <zwillx> ted the pi zero 2w defconfig yet
<DC-IRC> <zwillx> ... and then edge released switched from 6.6.2 to 6.6.4 in the past couple days, and I had to redo the whole thing yet again XD
<DC-IRC> <zwillx> lol
<DC-IRC> <viraniac> Not really. We switched from 6.6.2 to 6.6.3 and then 6.6.3 to 6.6.4. Each shift was seperated by 1 week of time.
<DC-IRC> <viraniac> BTW heads up 6.6.5 is scheduled to be release on Friday, so we would switch to it most likely by saturday
<DC-IRC> <zwillx> got it 😄 it got away from me and I was like.. why are my modules broken lol. Honestly, that's a pretty fast pace!
<DC-IRC> <zwillx> if the VMs would stop being corrupted, and I think my docker is now finally stable, I can switch to "offline" maybe?
<DC-IRC> <viraniac> you can build off the v23.11 branch. Its not going to be modified unless we need to release a fix
<DC-IRC> <zwillx> ok the diffconfig isn't showing me anything clear. Of the equal stuff which I changed, I believe none of it should break MMC. Like I took off MHI - modem host interface.. lol
<DC-IRC> <zwillx> I tried adding a few MMCs which the OPiOS had ticked "y" (for presumably no reason), no luck
<DC-IRC> <zwillx> I did notice a bunch of new boot security settings though? Of course it successfully mounts the kernel image so I don't see how that's an issue
<DC-IRC> <zwillx> actually I see it! block dev sd somehow toggled "n" ---- that should be it 🤞
<DC-IRC> <viraniac> block dev sd is scsi disk support. Thats is when you see things that starts with /dev/sd* like sda, sdb, etc, thats what it controls
<DC-IRC> <viraniac> with that removed, you might have lost usb storage, but microsd should still work
<DC-IRC> <viraniac> This is what armbian has for anything related to sdcard or mmc in allwinner kernel https://paste.armbian.com/tomazipure.bash
<DC-IRC> <viraniac> One more thing. The 2 lines that you shared earlier, were for 4021000.mmc. Thats mmc1. SDcard is connected to mmc0. So you need to tweak something related to mmc@4020000
<DC-IRC> <zwillx> ah OK I see what you mean.. 4020000 is off. I believe that comes from UBoot... ? That might be it but I have no idea how to change it!
<DC-IRC> <zwillx> [ 2.709284] sunxi-mmc 4020000.mmc: Got CD GPIO
<DC-IRC> <zwillx> [ 2.748392] sunxi-mmc 4020000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
<DC-IRC> <zwillx> this is the working one! good eye man thanks 🙂
<DC-IRC> <zwillx> ok I see what you mean. On the working one
<DC-IRC> <zwillx> [ 2.709284] sunxi-mmc 4020000.mmc: Got CD GPIO
<DC-IRC> <zwillx> [ 2.748392] sunxi-mmc 4020000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
<DC-IRC> <zwillx> However, it does continue with :
<DC-IRC> <zwillx> [ 2.928726] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
<DC-IRC> <zwillx> so that particular initialization is also 4021000, probably because that's partition 1? Still, good eye man, thanks : )
<DC-IRC> <zwillx> basically it seems the missing thing is the CD GPIO in dmesg
<DC-IRC> <zwillx> basically it seems the missing thing in the 6.6 attempt is the CD GPIO in dmesg
<DC-IRC> <viraniac> No, 4021000 is not partition 1. Its connected to wifi card
<DC-IRC> <zwillx> you know they might share a bus or something, because wifi works great on my 6.1 build 😄
<DC-IRC> <zwillx> here is the working dmesg from 6.1
<DC-IRC> <zwillx> and the SD broken 6.6 one
<DC-IRC> <zwillx> but this makes me consider the wifi because I hadn't added that yet to the initramfs, and there is firmware also..
<DC-IRC> <zwillx> you know they might share a bus or something, because wifi works great on my 6.1 build 😄
<DC-IRC> <zwillx> here is the working dmesg from 6.1
<DC-IRC> <zwillx> and the SD broken 6.6 one
<DC-IRC> <zwillx> but this makes me consider the wifi because I hadn't added that yet to the initramfs, and there is firmware also..
<DC-IRC> <viraniac> Can you share your 6.6 dts?
<DC-IRC> <zwillx> I'm just using the same .dtb from 6.1 (OpiOs), and that may indeed be the problem. Like, I'm baisically using Armbian for "BUILD-ONLY=kernel" and didn't mess with what worked - figured Opi zero2 dts wouldn't overlap
<DC-IRC> <zwillx> but I can share it 🙂
<DC-IRC> <zwillx> I'm just using the same .dtb from 6.1 (OpiOs), and that may indeed be the problem. Like, I'm baisically using Armbian for "BUILD-ONLY=kernel" and didn't mess with what worked - figured Opi zero2 dts wasn't guaranteed to work with zero2W
<DC-IRC> <zwillx> but I can share it 🙂
<DC-IRC> <tenkawa42> @zwillx yeah the 6.1 dts will 80-90% likely not work without modifications... they are dramaticly diff between 6.1 6.5/6.6/6.7-rc here for the Radxa mainline RK3588 and even on the RISC-V platform I work on.
<DC-IRC> <tenkawa42> That is just too far diff kernel revisions
<DC-IRC> <zwillx> got it, thanks! I was out of other options. I am thinking to use mainline UBoot to build fresh. Like, the Armbian system is so complex, that's basically easier for me still. Lame, I know 😄
<DC-IRC> <tenkawa42> Unfortunately I have no Orange PI devices at all or I'd try stuff out
<DC-IRC> <tenkawa42> I have a lot of other stuff but nothing OPi
<DC-IRC> <zwillx> are you in an AliExpress friendly country? send me a DM we can see ; )
<DC-IRC> <terrorpup> let me check later, I am at work right now
<DC-IRC> <viraniac> zwillx try using the dts that I shared before. You can take the patch file for the commit that added it from - https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/patch/arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts?id=c505ee1eae18fb7b32d792e4470d5ef1934376bd
<DC-IRC> <viraniac> just drop it in patch/kernel/archive/sunxi-6.6 directory
<DC-IRC> <viraniac> then modify your board config to use that dts file