| *** mavrick61 has quit IRC | 02:48 | |
| *** mavrick61 has joined #crux-devel | 02:49 | |
| *** Necrosporus has quit IRC | 04:12 | |
| *** jue has quit IRC | 08:48 | |
| *** Necrosporus has joined #crux-devel | 08:58 | |
| *** sepen has joined #crux-devel | 09:39 | |
| teK_ | I am verrry busy and the upgrade reequires physical interaction with (USB) media | 09:39 |
|---|---|---|
| *** sepen has quit IRC | 09:43 | |
| Necrosporus | teK_, you could try upgrading via ssh | 09:47 |
| teK_ | I wanted to allude to the fact that real-worl interaction is exhausting ;) | 09:56 |
| teK_ | the two machines are *in* my appartment | 09:56 |
| frinnst | I have even upgraded my backup server! lazy bastard :) | 10:08 |
| teK_ | TAH | 10:10 |
| teK_ | boot: fb1280 | 11:42 |
| teK_ | (...) | 11:42 |
| teK_ | Undefined video mode number: 307 | 11:42 |
| teK_ | our 3.1 ISO | 11:42 |
| teK_ | I think this machine uses 1280 as a default resolution, will check that later, once X is up again | 11:43 |
| teK_ | pitillo | 13:11 |
| teK_ | oh boy. xfce-terminal (my terminal) seems to be incompatible with libpng-1.6 | 13:19 |
| teK_ | /o\ | 13:19 |
| teK_ | or revdep is not yet done ;) | 13:26 |
| frinnst | probably vte that is still linked against 1.4 or something | 13:46 |
| teK_ | still looking for it | 13:46 |
| teK_ | I hate xterm ;) | 13:46 |
| frinnst | urxvt ftw | 13:46 |
| teK_ | our vte port is outdated like shit | 13:49 |
| teK_ | .. | 13:49 |
| frinnst | 0.3x probably depends on gnome3 and a lot of other crap | 13:51 |
| frinnst | 0.29.0 | 13:51 |
| frinnst | ====== | 13:51 |
| frinnst | - Drop GTK 2 support | 13:51 |
| teK_ | oh boy | 13:57 |
| teK_ | I can see my statically linked xfce-terminal already | 13:57 |
| teK_ | 200MB binary size | 13:58 |
| teK_ | -.- | 13:58 |
| teK_ | 0.37.90 tries to link against png15 | 13:58 |
| teK_ | .... | 13:58 |
| teK_ | and just because I updated to 3.1 :PP | 13:58 |
| teK_ | hm, updateing gtk3 first | 13:59 |
| *** jue has joined #crux-devel | 16:22 | |
| teK_ | Romster | 17:07 |
| teK_ | + rm /home/tmp/vte3-work/pkg/usr/lib/vte/gnome-pty-helper | 17:07 |
| teK_ | rm: cannot remove '/home/tmp/vte3-work/pkg/usr/lib/vte/gnome-pty-helper': No such file or directory | 17:07 |
| teK_ | :) | 17:07 |
| teK_ | oh and there's version=0.37.90 | 17:08 |
| teK_ | of it | 17:09 |
| *** deus_ex has joined #crux-devel | 19:06 | |
| *** Necrosporus has quit IRC | 20:34 | |
| teK_ | frinnst: 5 hours of compilation and xfce-fuckup-age later I am finally on 3.1 on 1 of 2 machines | 20:58 |
| teK_ | hope you're happier now! | 20:58 |
| frinnst | :D | 21:53 |
| teK_ | on the other hand, firmware loading for my wifi is seriously broken | 21:57 |
| jaeger | curse you, wifi! | 21:57 |
| teK_ | it takes ages to load after claiming it cannot (directly) load my firmware file | 21:57 |
| teK_ | which is present in /lib/firmware | 21:57 |
| nrxtx | tek intel chip? | 22:01 |
| teK_ | yes | 22:01 |
| nrxtx | build the firmware file into kernel | 22:01 |
| teK_ | will try that. Still: this sucks | 22:02 |
| nrxtx | the kernel tries to load it before rootfs is mounted, which fails and he does not try it again | 22:03 |
| teK_ | this lazy fuck | 22:03 |
| jaeger | It would only do that if it's builtin, right? | 22:03 |
| jaeger | As module it should be fine and load after boot | 22:03 |
| nrxtx | jaeger: it should but it does not | 22:05 |
| jaeger | which driver is that? I don't have that behavior with iwlwifi | 22:05 |
| teK_ | it's iwlwifi | 22:05 |
| teK_ | 3.16.1 | 22:05 |
| jaeger | both my laptop and a desktop with a centrino 6205, both built as modules | 22:05 |
| teK_ | 02:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35) | 22:06 |
| jaeger | funky | 22:06 |
| frinnst | It may simply be a race condition somehow | 22:07 |
| teK_ | it worked until I switched to eudev | 22:08 |
| teK_ | do NOT let poettering read that!11 | 22:08 |
| jaeger | My laptop has 3.12.25 on it, desktop has 3.14.something | 22:08 |
| jaeger | both on 3.1 and using eudev | 22:08 |
| teK_ | I had 3.16.1 on it for 3.0 too | 22:08 |
| teK_ | so you have some /lib/firmware/iwlwifi-6000-4.ucode file, too? | 22:08 |
| teK_ | it specifically prints the file name during boot and the file *is* there | 22:09 |
| jaeger | yes, 6000g2a-5 in this case | 22:09 |
| teK_ | I have zero inclination to include that file in each kernel image I am going to build | 22:10 |
| teK_ | oh this should work via oldconfig, I guess. | 22:11 |
| teK_ | oh and jaeger IWLWIFI is set to yes, not module | 22:13 |
| jaeger | that's probably why it doesn't work | 22:13 |
| frinnst | .. | 22:13 |
| frinnst | :D | 22:13 |
| teK_ | https://www.youtube.com/watch?v=xkzwRkKFsjQ | 22:14 |
| jaeger | whither the money, lebowski?! | 22:17 |
| jaeger | http://www.amazon.com/Two-Gentlemen-Lebowski-Excellent-Tragical/dp/1451605811 | 22:18 |
| teK_ | how can this be any more fucked up? | 22:22 |
| teK_ | it still whines about not being able to load that crap | 22:22 |
| teK_ | hello mcfly? somebody home? | 22:22 |
| jaeger | did you switch it to module instead? what are the firmware permissions? does the md5sum match the original? | 22:23 |
| teK_ | exactly 120 seconds after boot (timeout for loading things is 60) wifi starts working | 22:23 |
| teK_ | doing that switch right now | 22:23 |
| teK_ | it worked for ages so I bet the md5sum is ok. Permissions were 600, are 644 now | 22:23 |
| jaeger | Maybe I'm wrong here but it seems to me that if you build it as builtin and don't include the firmware in the kernel, it SHOULD be expected to fail | 22:23 |
| jaeger | the first time, at least | 22:24 |
| teK_ | ok wtf :D | 22:24 |
| teK_ | what's the logic behind that | 22:24 |
| teK_ | rebooting, (brb in 120s ...) | 22:24 |
| jaeger | ok, look at it this way: if it's builtin, the wifi driver gets loaded before the filesystem containing its firmware is mounted | 22:25 |
| jaeger | therefore, failure | 22:25 |
| jaeger | If it's a module instead, the module gets loaded later by eudev instead and the firmware is available | 22:25 |
| teK_ | oooh it's getting better every time I do a reboot | 22:30 |
| teK_ | yes I get that | 22:30 |
| teK_ | I get that it *could* fix things. Yet it doesn't | 22:30 |
| teK_ | I made my kernel ooops | 22:30 |
| jaeger | how odd | 22:30 |
| jaeger | I'd suggest trying an older kernel, too, I guess | 22:30 |
| teK_ | and th 120 seconds = 60 seconds default + $TIMEOUT value in /sys/class/firmware | 22:31 |
| teK_ | I tried 3.15.7, same shit | 22:31 |
| teK_ | I have to try to connec tto my wifi abort that and retry to make it work, btw | 22:31 |
| jaeger | that's bizarre | 22:32 |
| teK_ | but that's been the case for quite some kernel versions (a year at least?) | 22:32 |
| jaeger | weird. sorry, I'll butt out, then, clearly not helping :P | 22:34 |
| teK_ | I bet frinnst has some useful ideas left | 22:36 |
| teK_ | but thanks ;) | 22:36 |
| jaeger | http://sprunge.us/iGRW <-- the kernel config from my laptop if you're interested | 22:39 |
| nrxtx | teK_: did it work as module? | 22:39 |
| teK_ | thx jaeger. nrxtx: no | 22:39 |
| teK_ | http://dpaste.com/33H13DA | 22:41 |
| teK_ | fyi | 22:41 |
| jaeger | does it do the same thing if you rmmod the module and then load it manually? | 22:44 |
| teK_ | yes | 22:46 |
| teK_ | http://dpaste.com/0MMMBFA | 22:46 |
| teK_ | I changed the timeout to 10 seconds | 22:47 |
| teK_ | I enabled debugging and experimental ucdoez | 22:47 |
| teK_ | brb.. | 22:47 |
| nrxtx | looks the same like i had before including it in the kernel | 22:47 |
| nrxtx | have the same card as 6325 | 22:47 |
| jaeger | the firmware loaded properly in that paste | 22:47 |
| jaeger | [ 1069.554910] iwlwifi 0000:02:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm | 22:48 |
| jaeger | oh, never mind, I see the errors above that | 22:48 |
| jaeger | weird | 22:48 |
| nrxtx | the failed with "-2" is ENOENT | 22:49 |
| jaeger | I don't have the fallback user helper enabled even | 22:49 |
| teK_ | it doesnt work at all if I disable the help | 22:50 |
| teK_ | er | 22:50 |
| jaeger | what does the "Device Drivers -> Generic Driver Options" section of your kernel config look like? | 22:51 |
| nrxtx | teK_: have the *.ucode in /lib/firmware/... ? | 22:51 |
| teK_ | http://dpaste.com/34YYWYH | 22:52 |
| teK_ | [tek@pita][~]% ll /lib/firmware/*ucode | 22:52 |
| teK_ | -rw-r--r-- 1 tek users 454608 [2010/06/02] /lib/firmware/iwlwifi-6000-4.ucode | 22:52 |
| nrxtx | according to the config you built that into the kernel and it still has error -2? | 22:53 |
| teK_ | yes | 22:53 |
| teK_ | 3 times | 22:54 |
| jaeger | loading the wrong kernel? | 22:54 |
| teK_ | than (timeout set to 1 sec): | 22:54 |
| teK_ | [ 64.846646] iwlwifi 0000:02:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm | 22:54 |
| teK_ | Linux pita 3.16.1 #7 SMP PREEMPT Mon Aug 25 00:38:40 CEST 2014 x86_64 Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz GenuineIntel GNU/Linux | 22:54 |
| nrxtx | can you post the output of lspci? | 22:54 |
| teK_ | http://dpaste.com/0CB57NK | 22:54 |
| teK_ | md5sum is identical to the file from http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-6000-ucode-9.221.4.1.tgz | 22:56 |
| nrxtx | what is the vendor & device id of this card? | 22:58 |
| teK_ | other than the one from lspci? | 22:59 |
| nrxtx | the one shown by lscpi -n | 22:59 |
| teK_ | 02:00.0 0280: 8086:4238 (rev 35) | 23:00 |
| nrxtx | weird | 23:06 |
| teK_ | the two-times authentication problem could be seen with my son's android smart phone during vacation with the hotel's wifi, too | 23:08 |
| teK_ | which makes it even more weird but no less annoying | 23:08 |
| nrxtx | do you have tracers enabled? | 23:15 |
| teK_ | no | 23:16 |
| teK_ | but I switched to wext in wicd and no wpa-auth works on the first try | 23:16 |
| teK_ | :o | 23:16 |
| teK_ | a Gentoo user posted: | 23:18 |
| teK_ | [ 2.613858] iwlwifi 0000:02:00.0: Direct firmware load failed with error -2 | 23:18 |
| teK_ | [ 2.613899] iwlwifi 0000:02:00.0: Falling back to user helper | 23:18 |
| teK_ | [ 4.354019] iwlwifi 0000:02:00.0: loaded firmware version 23.214.9.0 op_mode iwlmvm | 23:18 |
| teK_ | please note the timestamps.. | 23:18 |
| jaeger | also a completely different version, what's up with that? | 23:18 |
| teK_ | it's different hardware | 23:19 |
| teK_ | but the same mechansims wrt firmware loading should apply | 23:19 |
| jaeger | ah, I missed that, sorry | 23:19 |
| nrxtx | -2 should be "no such file or directory" | 23:19 |
| jaeger | gentoo user | 23:19 |
| nrxtx | you might need to add some printk to the firmware loader of the kernel to debug that | 23:20 |
| jaeger | maybe try the latest firmware from https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/iwlwifi-6000-4.ucode ? | 23:20 |
| teK_ | which is funky because the code is embedded in the kernel | 23:20 |
| teK_ | jaeger: I already have that (it's four years old) | 23:21 |
| jaeger | ah. ok | 23:21 |
| nrxtx | according to the device id and iwlwifi driver source the filename is also correct | 23:23 |
| teK_ | ENOENT is default return value | 23:25 |
| nrxtx | Do you have "CONFIG_IWLWIFI_DEBUG" and/or "CONFIG_IWLWIFI_DEVICE_TRACING" enabled? | 23:26 |
| teK_ | DEBUG yes, TRACING no | 23:26 |
| teK_ | but my guess is that the actual loading is never done | 23:26 |
| teK_ | /tried | 23:26 |
| teK_ | because in that case the loader-function would emit additional information | 23:27 |
| nrxtx | if you have debug enabled you should see what he tries to load and or if the file is suitable | 23:27 |
| teK_ | nope :) | 23:28 |
| nrxtx | what is the value of /sys/module/iwlwifi/parameters/debug ? | 23:28 |
| teK_ | 0 | 23:28 |
| nrxtx | can you load the module and immediately change it to 1? | 23:30 |
| teK_ | sure, wait 60 seconds :P | 23:30 |
| nrxtx | ah you should be able to change it as modprobe parameter "debug_level" | 23:31 |
| teK_ | omg.. | 23:32 |
| nrxtx | modprobe iwlwifi debug_level=1 | 23:32 |
| nrxtx | ? | 23:32 |
| teK_ | this is funny :D | 23:32 |
| teK_ | [ 1130.275129] iwlwifi 0000:02:00.0: U iwl_request_firmware attempting to load firmware 'iwlwifi-6000-5.ucode' | 23:32 |
| nrxtx | :D | 23:32 |
| jaeger | ... | 23:33 |
| nrxtx | yeah he tries a range of files | 23:33 |
| nrxtx | seems like they set a new upper limit | 23:33 |
| teK_ | ALL pages I checked list -4 | 23:33 |
| jaeger | never trust pages, trust dmesg | 23:33 |
| teK_ | :p | 23:33 |
| jaeger | it comes straight from the kernel driver, after all | 23:33 |
| nrxtx | and debug information :D | 23:33 |
| teK_ | I was about to patch that into the firmware loader :P | 23:33 |
| nrxtx | hehe | 23:34 |
| teK_ | so the question is.. will renaming /baking in the file suffice | 23:34 |
| teK_ | brb ;) | 23:34 |
| jaeger | I never build it in, for what that's worth | 23:34 |
| jaeger | though it should work either way if you use the right file :) | 23:34 |
| nrxtx | yes :D | 23:35 |
| nrxtx | teK_: the first try will be for .*-6.ucode | 23:37 |
| nrxtx | at least what the header file of the driver says | 23:37 |
| teK_ | -5 does not get loaded either | 23:42 |
| teK_ | not builtin and not with iwlwifi as module and the firmware just being in /lib/firmware | 23:42 |
| jaeger | if you remove them and 'dmesg | grep fw' it will tell you exactly which file it wants. Though that seems to be -5 | 23:43 |
| nrxtx | have to go, you can get more information here: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/iwlwifi/iwl-debug.h?id=refs/tags/v3.12.26#n93 | 23:43 |
| jaeger | well, I didn't look at the header but anyway | 23:43 |
| nrxtx | if you need some more you can add some printks: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/iwlwifi/iwl-drv.c?id=refs/tags/v3.12.26#n217 | 23:44 |
| jaeger | you should probably do either 1) builtin AND firmware in kernel or 2) module and firmware NOT in kernel | 23:44 |
| jaeger | not a mix of both | 23:44 |
| teK_ | ta nrxtx :) | 23:44 |
| teK_ | yes jaeger, that were the two scenarios I tested | 23:44 |
| teK_ | at least NOW I found a debian bug report that seems to be related | 23:45 |
| jaeger | ok. from your comments I could not figure out which you were doing | 23:45 |
| teK_ | both, sequentialy | 23:45 |
| jaeger | "not builtin and not with iwlwifi as module" seemed contradictory | 23:45 |
| teK_ | oops | 23:46 |
| teK_ | my bad | 23:46 |
| nrxtx | hehe gn8 and have fun :D | 23:46 |
| teK_ | in 15 minutes, my AP will disable WiFi anyway | 23:47 |
| teK_ | problem solved | 23:47 |
| teK_ | =) | 23:47 |
| nrxtx | XD | 23:47 |
| jaeger | huh? | 23:47 |
| teK_ | it's a safety measure | 23:48 |
| teK_ | it's almost 2 a.m. here | 23:48 |
| jaeger | At this point I'm completely confused. :P | 23:48 |
| teK_ | dont worry :> | 23:53 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!