2024-03-27.log

- vagrantc (QUIT: Ping timeout: 255 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50)00:13
- ndufresne (QUIT: Quit: Ping timeout (120 seconds)) (~ndufresne@apple.collaboradmins.com)01:03
- mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:03
+ ndufresne (~ndufresne@apple.collaboradmins.com)01:03
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@64.189.201.150)01:14
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)01:23
digitalraynejosch, cool trick :) so i guess with that you are skipping over the FAT etc as the firmware is always at a fixed offset? I'll have to give that a try 02:49
digitalraynein *BSD that would be dd if=bin/firmware.bin of=/dev/rsd2c bs=512 seek=4 count=64 (replacing sd2 with the disk ID from dmesg), that would also obviate the need for conv=nocreat,notrunc which is nice (only conv=notrunc exists on BSD dd)02:51
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:09
- skipwich (QUIT: Quit: DISCONNECT) (~skipwich@user/skipwich)04:01
+ skipwich (~skipwich@user/skipwich)04:02
joschdigitalrayne: yes, according to lukas, the filesystem is created by a firmware located in rom, so it will always look the same -- let me know if it works! :)04:37
joschif your dd tried to re-create the file in the fat (which is not allowed) then that might just explain why it didn't work for you04:38
joschdigitalrayne: you could try tracing the syscalls your dd does to find out with what arguments it tries to open the file on the fat04:55
+ jacobk (~quassel@129.110.242.173)05:40
+ chomwitt (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)07:41
- chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)08:30
+ chomwitt (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)09:22
- klardotsh (QUIT: Ping timeout: 264 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)09:50
+ mjw (~mjw@gnu.wildebeest.org)09:53
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)10:04
* Guest3473 -> mjw10:08
- jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@129.110.242.173)10:26
- chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)10:28
minutefunky https://github.com/ToNi3141/Rasterix10:29
joschthe thing can render Warcraft 3??? wow this kind of stuff is so impressive really11:12
joschdigitalrayne: and i found another way to flash the lpc firmware without mounting anything: using mtools11:39
joschsudo mcopy -D o -i /dev/sda bin/firmware.bin ::firmware.bin11:39
joschin completely unrelated news, the "Cadence MHDP8501(HDMI/DP) for i.MX8MQ" patch is now at v15 and it looks like more fixes were requested: https://lore.kernel.org/linux-arm-kernel/PAXPR04MB94488A50C2BDD6B859B110DAF42A2@PAXPR04MB9448.eurprd04.prod.outlook.com/T/11:43
- Aard (QUIT: Remote host closed the connection) (~bwachter@edna-edison.lart.info)12:23
+ Aard (~bwachter@edna-edison.lart.info)12:23
- murmr____ (QUIT: Ping timeout: 256 seconds) (sid433686@id-433686.helmsley.irccloud.com)12:41
+ wakest_ (m-a7d6fe@45.77.48.108)12:43
- wakest (QUIT: Remote host closed the connection) (m-a7d6fe@45.77.48.108)12:43
+ murmr____ (sid433686@id-433686.helmsley.irccloud.com)12:44
* wakest_ -> wakest12:48
minutejosch: it's the neverending patch! it's like a perpetual stew12:57
AbortRetryFailWhat is a DRM bridge driver for?12:58
+ mark_ (~mjw@gnu.wildebeest.org)13:00
- mtm (QUIT: Ping timeout: 272 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:04
joschminute: is the qcacld2 out-of-tree driver something you think would make sense to ship in Debian? Or are there efforts to integrate it into mainly before long?13:10
minutejosch: it could be shipped as nonfree perhaps, because it has to include bizarre firmware blobs13:10
minutejosch: mainline ath10k doesn't work and the maintainer doesn't know why13:11
minutebut maybe someone can debug that some day, i am not holding my breath atm though13:11
joschthe firmware blobs are those found in firmware-deploy?13:12
minutejosch: i need to put all of these in /usr/firmware like that, or patch the driver to fix up the paths somehow https://source.mnt.re/reform/qcacld2/-/tree/boundary-CNSS.LEA.NRT_3.1/firmware-deploy?ref_type=heads13:12
joschwhat is their license?13:12
minutejosch: yes13:12
minutejosch: i don't know :3 i need to check where i found them13:12
minuteohh probably this https://github.com/boundarydevices/qca-firmware13:13
joschthe rest of the driver seems to be bsd 2, 3 and 4-clause and isc licensed13:13
minutejosch: i think the driver is dual licensed13:13
minutenot sure what this means exactly https://source.mnt.re/reform/qcacld2/-/blob/boundary-CNSS.LEA.NRT_3.1/Makefile?ref_type=heads#L1013:13
minutejosch: ah yeah you're right13:14
joschthen that would be two packages, one for main and one for non-free-firmware13:15
minuteok!13:15
minutein any case i managed to build the driver on the target like it is in the repo now, yesterday, and it works13:15
joschthe repo on source.mntre.com is the one from https://github.com/TechNexion/qcacld-2.0 with your own modifications?13:15
minutehmm no not from technexion13:15
joschwhat was your source?13:16
minutehttps://github.com/boundarydevices/qcacld-2.0/tree/boundary-CNSS.LEA.NRT_3.113:16
joschnice, the master branch only has a README in it :D13:16
minuteyeah because you can choose your branch :D13:16
minuteit is like choose your own adventure13:17
minutebtw we only need the driver for wifi. the bluetooth portion works with mainline (it's connected via an internal UART)13:17
joschthanks, now i can upload some more stuff to NEW while we wait for tuigreet and reform-setup-wizard to get accepted :)13:17
minutejosch: great, thanks a ton!13:18
joschthank you for the great hardware :)13:18
- mark_ (QUIT: Remote host closed the connection) (~mjw@gnu.wildebeest.org)13:20
+ mark_ (~mjw@gnu.wildebeest.org)13:21
joschhuh and qcom_cfg.ini and cfg.dat also are somehow needed and need to go into /usr/lib/firmware?13:26
- mark_ (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)13:41
joschminute: there are 1.4k lines of diff between https://github.com/boundarydevices/qcacld-2.0/tree/boundary-CNSS.LEA.NRT_3.1 and https://source.mnt.re/reform/qcacld2/-/tree/boundary-CNSS.LEA.NRT_3.1?ref_type=heads are those your copyright? https://mister-muffin.de/p/cQjl.diff13:52
minutejosch: qcom_cfg.ini and cfg.dat need to go to /usr/lib/firmware/wlan13:54
minutejosch: yeah, those changes are just fixes to make it work with current kernels14:04
joschcool, just making sure that this is from you (as i have to document that) and to make sure that i am not accidentally packaging a slightly incorrect branch :)14:07
+ mark_ (~mjw@gnu.wildebeest.org)14:39
joschminute: i chose the ISC license for your debian packaging so that your additions remain trivially compatible with the upstream source, okay?14:40
minutejosch: great14:54
joschminute: if you would like to review the finished product, here it is: https://salsa.debian.org/debian/ezurio-qcacld-2.0-dkms14:57
minutejosch: amazing, thank you!15:08
joschminute: would you like to review and comment? If yes, I wait with my upload until then, if not I upload some time tonight (afk now)15:09
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:09
- cobra (QUIT: Ping timeout: 245 seconds) (~cobra@user/Cobra)16:05
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)16:45
+ chomwitt (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)17:18
- mark_ (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)17:27
+ klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)17:58
minutejosch: testing your REFORM_DEBIAN_PACKAGES_BRANCH feature in CI now for the first time18:00
minutejosch: i won't need to review just yet, to be able to really do that i need to fiddle that dkms package into the system image somehow18:01
minuteaw > refusing to build image using packages from reform-debian-packages branch18:02
minutethen i can try it locally maybe18:02
joschminute: to set variables you must do it on a branch other than "main"18:08
joschminute: the reason for that is to avoid poisoning what https://mnt.re/system-image points to18:11
joschsame with reform-debian-packages18:12
joschi wanted to avoid that pipeline runs with custom variable values would result in https://mnt.re/system-image as well as https://mntre.com/reform-debian-repo containing custom build results18:12
joschunfortunately, as we learned recently, this attempt of mine was futile18:13
joschas gitlab will happily link to build jobs from any branch with the same top commit as the requested branch18:13
joschminute: i listed possible solutions here: https://mntre.com/reform-irc-logs/2024-03-25.log.html#t17:37:0018:15
joschminute: i also added information to variables.sh so that the script that updates https://mntre.com/reform-debian-repo can make sure that it's not populating the repo with stuff that does not come from the main branch18:16
joschbut see the irc log for details18:17
minutejosch: ahh my mistake. i didn't want it to do on main18:37
joschminute: you might want to run it in your fork so that you do not accidentally change the contents behind https://mnt.re/system-image18:38
joschafter having slept over this problem for two nights, my personally preferred solution is to just forbid running the pipelines with custom variables set if $CI_PROJECT_NAMESPACE is equal to "reform"18:41
joschminute: do you have any uncommitted changes to the qcacld-2.0 packaging?18:47
minutejosch: ok, sounds good, and we can just use a fork for CI, makes sense18:47
joschwhen installing the package it doesn't build the module18:47
joschand it looks like it never calls make in the first place which sounds like an issue you had yesterday18:47
minutejosch: oh hm. let me check18:47
minuteok what i did yesterday is that i went into the dkms build dir after installing the package and ran make, which succeeded18:48
minuteand then i added the MAKE[0] line to qcacld2-dkms.dkms18:48
minutebut didn't run that again on the target18:48
joschah okay18:48
joschthen i'll investigate this later tonight18:49
minuteoh thank you18:49
minutei'm currently fighting with the imx8mp/pocket kernel config18:49
minutei found out that we need IMX2_WDT baked into the kernel. if the module is on disk and is not loaded for some reason or there's too much of a delay, the system just resets, which makes debugging more than uncomfortable18:49
- chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a17:f700:1ac0:4dff:fedb:a3f1)18:50
joschseems to become a pattern that using features as modules appears to be something that driver developers don't test much19:08
+ mark_ (~mjw@gnu.wildebeest.org)20:04
- mjw (QUIT: Killed (mercury.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:15
* mark_ -> mjw20:15
+ Guest5307 (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:15
- hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu)20:24
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)20:42
+ hairu (m-uotkmd@user/hairu)20:57
hramrachit means something already enabled the watchdog before loading the kernel, it's not the faualt of the driver 20:57
hramrachof course, if you want to paper over lockup during kernel boot that's the thing to do so it makes sens in some setups20:58
- violet (QUIT: Remote host closed the connection) (~vi@user/violet)21:07
+ violet (~vi@user/violet)21:07
minutejosch: yeah21:08
minutehramrach: possibly something in uboot21:08
+ reform1926 (~root@102.44.63.188.dynamic.wline.res.cust.swisscom.ch)21:16
reform1926hello21:17
vkoskivHello!21:17
reform1926this is great!21:17
reform1926sorry im new here 21:18
vkoskivWelcome21:18
vkoskivDid you just set up a reform?21:18
reform1926yes21:18
vkoskivVery cool! What kind of setup did you get?21:19
reform1926im trying to get familiar with it21:19
reform1926mnt reform21:19
reform1926at the sametime trying to learn system21:19
reform1926i have few questions...21:20
vkoskivYep, lots to read. Do ask if you run into any issues/confusion, many people here can help21:20
reform1926would you be able to help?21:20
vkoskivSure21:20
reform1926ok21:20
vkoskivI've had mine for a while now21:20
reform1926first question..---i have installed a DE keyboard but the system dont recogniyed and type with the EN-settings21:22
vkoskivAre you using sway or some other graphical environment? With sway, I configure it in ~/.config/sway/config21:23
vkoskivThe system image assumes US layout, it doesn't detect it automatically I think.21:23
joschor, even better, in ~/.config/sway/config.d/input21:23
vkoskivYeah, that is the recommended way. I just prefer to keep my configs to single file per thing :D21:24
vkoskivWouldn't it be possible to do some kind of automatic detection for that, since we do control the firmware?21:24
vkoskivNot sure if there is any standard way of doing that.21:24
joschvkoskiv: the firmware is only neo2, US and "normal"21:24
reform1926how can i change the setting for DE instead of EN, to tzpe the right keys... for example, where the kez z is the y and where the y is the z... is sometime overwhelming 21:24
vkoskivjosch: I meant the layout of the keeb21:25
joschreform1926: put this into your sway config: https://paste.debian.net/1312218/21:26
joschvkoskiv: the firmware does not know what is printed on the keys21:26
vkoskivGood point. Extra complexity would be needed to tell it that info when flashing21:27
reform1926@vkoskiv- im using root and sway (both)21:28
reform1926the 2nd question.. my screen is constently flickering, with time it get enozing21:32
reform1926sorry /// enoying21:32
joschreform1926: do you have an ls1028a reform?21:33
reform1926dont the reason why is constently doing this21:33
reform1926@josch- yes21:34
joschreform1926: there is a hardware fix for this issue. You should get into contact with support@mntre.com21:35
reform1926ok thanks21:35
joschreform1926: details here: https://community.mnt.re/t/research-into-ls1028a-wifi-to-edp-interference/176221:35
joschon my ls1028a i solved the problem by wrapping tape around the flex cable21:36
joschbut there is a more professional solution :)21:36
reform1926im sure... :)21:37
reform1926thank you all for the time and answers..21:39
reform1926will leave now and try to cahnge the settings 21:40
reform1926until the next time21:40
reform1926exit21:40
joschit should be /quit21:41
reform1926hahahaha21:41
joschirc commands are prefixed with a slash21:41
reform1926thanks21:41
- reform1926 (QUIT: Quit: Leaving) (~root@102.44.63.188.dynamic.wline.res.cust.swisscom.ch)21:42
joschminute: the magic runes were, that one has to set WLAN_ROOT, MODNAME and CONFIG_* options for the make invocation to build the module. There is a Kconfig which expects these to be set. The Android.mk also hints that the final module name is not wlan.ko but qcacld_wlan.ko. Unfortunately, when installing and building it, I'm getting build failures like:21:45
joschCORE/HDD/src/wlan_hdd_assoc.c:2161:13: error: ‘struct cfg80211_roam_info’ has no member named ‘bss’21:45
joschCORE/HDD/src/wlan_hdd_hostapd.c:1576:9: error: too few arguments to function ‘cfg80211_ch_switch_notify’21:45
joschsounds like i'm on the wrong kernel version?21:45
joschthis is 6.7.921:46
digitalraynethat reminds me i have to work out how to adjust my v2 keyboard for qwerty-jp now that i have the keycaps21:55
joschminute: seems there was a kernel version check around the code which errors out now: https://salsa.debian.org/debian/ezurio-qcacld-2.0-dkms/-/blob/master/debian/patches/fixup.patch?ref_type=heads#L9121:56
joschfull failure log here: https://salsa.debian.org/debian/ezurio-qcacld-2.0-dkms/-/jobs/550637121:57
joschthe bss member for cfg80211_roam_info seems to have been introduced in git efbabc1165004 which first appeared in v6.0 which is exactly what the patched out version check suggests... hrm...21:58
joschsame with cfg80211_ch_switch_notify21:59
- robin (QUIT: Remote host closed the connection) (~robin@user/terpri)22:23
+ robin (~robin@user/terpri)22:23
+ jacobk (~quassel@64.189.201.150)23:13

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!