00:00:52 well 00:01:05 i tried enabling 8n2 mode with one usb to serial adapter and it refused to 00:01:47 so i tried with another serial adapter (the one that has been connected to the UPS for the last 10 years) and it crashes as soon as getty shows the login prompt 00:02:33 and now im trying with a usb adapter that literally costed me $2 and was giving me problems with an external modem, and it seems with 8n2 mode the terminal is very happy 00:02:46 tldr it was the fucking usb adapter 00:04:11 i hope the pcie-serial adapter will be less trouble 00:04:19 (famous last words) 00:04:44 so here i am now at 19.2kbaud no flow control yolo 00:06:38 Yay! 00:07:44 i'm gonna have to do a writeup about this on my blog 00:13:42 rwp: should i go back and rescue the other two that were left at the warehouse? 00:13:53 there is that and an extremely heavy C.Itoh printer 00:16:07 That is a question only you can answer. 00:16:44 I might say that it takes at least two terminals to play a terminal game between two people. :-) 00:16:56 i might go. could make a video about restoring them 00:17:01 this one still needs retrobright 00:17:12 im waiting for the summer to start retrobrighting things around here 00:17:27 have a commodore 128 that could use some retrobright 00:17:39 It is the end of summer for us on this side of the planet. Winter is coming. 00:19:27 i need to map colors to make better use of this terminal but im not sure how its done 00:20:23 my own nick is underlined here but that's about it 00:20:36 i see that *text* like this appears also underlined 00:40:05 any hints on updating an extracted base.txz distribution with freebsd-update? neither -b nor -d seem to do the trick... 03:20:08 so i have a weird issue with the serial terminal. i can't run sudo 03:20:20 it does nothing, util i ctrl-C 03:20:36 then it prints the usage instructions 03:20:46 it works fine over ssh 03:29:04 Do you have the same problem if you try to change your password? 03:29:35 I am guessing it is asking you for a password and changing the tty to noecho for the entering of it. 03:29:53 i have it nopasswd 03:30:11 Hmm... That is weird then. 03:30:22 even truss sudo shows nothing either 03:32:04 Are you in the wheel group? Also try "su - $USER" just for additional data points. 03:32:35 "su - $USER" will stack a shell. Exit from there to return to the previous shell. 03:55:36 haro.. I found my way here from 20 yrs ago. 03:55:53 nice 03:56:20 we been waiting for you... now we can move on finally 03:56:25 I only remember asmodai from the user list. 03:57:54 Does saffron and blackend come by anymore? 03:59:42 Welcome PawTeeGal! I do not recognize those nicks but who knows? 04:01:25 People from probably the late 90's used to be efnet freebsd group. I know blackend is still on the official FreeBSD project. saffron used to be regular too, I think she used to work for Xi Systems. 04:04:05 Though there has been the big migration to Libera.Chat the others still also exist. Except for that one which was taken from us and we were forced to walk away from which I do not speak of now. Perhaps they are still using EFnet? (Shrug.) You might find them there. 04:04:12 Until then you have many new friends here to meet. 04:08:29 Sure I'll hang around. I looked around on efnet looks like it got turned into the internet ghettos.. shame.. 04:09:10 And hi Rep, Good meeting you. I figure going down memory lanes a bit and found me way here. 04:11:32 We have been enjoying hjf's adventure down museum serial terminal lane. From hjf: https://i.imgur.com/eZqPwuw.jpeg 04:13:15 now thats vintage.. alas I got rid of all my vintage stuff. back from the fbsd 2.2.8 days and my sparc 20. (good riddance honestly) 04:15:43 It's an obscure TERM=viewpoint3a+ type and how shall I say, there has been some termcap issues with it. 04:24:02 dont think I've ever seen one.. 04:24:12 I did started out on a Hearthkit H19 tho 05:06:15 https://blog.hjf.com.ar/en/2024/10/05/notes-on-the-adds-1010-text-terminal/ 05:06:27 before i forget all my learnings 07:54:16 how does the package repository work. Why am I missing almost every py39- package that py311 has? 07:55:01 im running with latest right now, the same thing applies for quarterly but for other packages. 07:56:39 is it just a temporary glitch or am I doing something wrong. 07:57:23 drobban: ports only supports a single python version, which is currently 3.11 by default, so that's what the packager builders use. it's possible to configure a package to build for multiple versions, but the vast majority of python packages don't do that 07:57:50 to get a different python version you would have to build your own packages from ports with python set to 3.9 (or whatever) 08:01:46 ivy: thanks for the clarification! 08:04:41 i phrased that a little poorly, ports supports multiple python versions, but you have to choose one version as the default version, which is what the py*-* packages will build against 08:05:02 and the default default version is 3.11 08:06:35 ivy: =) think that was how I understood you the first time as well. 08:22:24 ports named tcl9.0 and tcl9 why two? 08:23:50 dandyn: without checking, i guess tcl9 is 9.latest and tcl9.0 is fixed at 9.0. check the makefiles to be sure 08:25:00 okok, thnx 08:43:50 dandyn maybe you can ask in #tcl, they are pretty helpful and as per they conversations they are now fully engaged with tcl9, I think most people use 8.6 11:48:28 Hi, where can I find a howto or tutorial to report a bug in the base system and potentially submit a correction? https://forums.freebsd.org/threads/rcp-issue-using-legacy-bsdrcmds-r-commands-package.95211/#post-674568 11:50:25 uskerine: if you found a bug, you can report it at https://bugs.freebsd.org. however if you have a code fix, you should not file a bug but instead send a pull request to the FreeBSD github repository, https://github.com/freebsd/freebsd-src 11:50:45 uskerine: this uses the normal git workflow, if you're familiar with that 12:24:28 can someone explain how wireless works on freebsd 12:24:49 i have this network card: iwm0: mem 0xf0400000-0xf0401fff at device 0.0 on pci2 12:25:04 but i get this: ssid LF channel 6 (2437 MHz 11g) bssid 74:4d:28:8e:7a:8e 12:25:14 surely this card should do better than .11g? 12:26:11 according to the Intel spec sheet, it should do .11ac 13:06:12 According to https://docs.freebsd.org/en/books/handbook/network/#network-wireless “802.11ac support on FreeBSD is currently under development.”—that might mean, it does not work yet? My hardware is far too old to run into such a problem :-) 13:06:25 But it says there: “FreeBSD supports networks that operate using 802.11a, 802.11b, 802.11g and 802.11n.” 13:06:35 even so, surely it should work as .11n 13:11:24 Which version of FreeBSD are you on? `uname -v` 13:12:16 i'm not at that device right now but it's 14.1 from about a week ago 13:12:43 (had some weird issues with 15.0 on it, so i had to downgrade to 14.1) 13:13:52 iwm(4) says 802.11ac hmmmm... https://docs.freebsd.org/en/books/handbook/network/#network-wireless 13:14:07 wrong link: https://man.freebsd.org/cgi/man.cgi?query=iwm&manpath=FreeBSD+14.1-RELEASE+and+Ports 13:17:34 You have tried to put `iwm7260fw_load="YES"` into your `/boot/loader.conf`? 13:18:15 Sometimes loading it after that stage results in some strange problems. 13:19:11 i will try that next, thanks 13:20:45 I hope, it will solve your problem. 13:28:41 Kalten: unfortunately it did not 13:28:48 i tried loading all the iwl-related modules in loader.conf 13:28:58 iwm7260fw_load=YES 13:28:58 if_iwm_load=YES 13:28:58 if_iwlwifi_load=YES 13:29:13 but i'm still stuck on .11g: ssid LF channel 6 (2437 MHz 11g) bssid 74:4d:28:8e:7a:8e 13:29:50 i really hope i don't have to install wifibox to make this work, this ancient laptop only has 4GB RAM 13:39:01 ivy well I ahve not tested, the fix is described there, but there might be more things to do 13:39:10 so shall I just submit the bug? 13:39:42 uskerine: if you don't have a direct code fix then yes you can just submit the bug. i didn't read your link though so not sure what the specific issue is 13:41:01 brb 13:41:03 when they removed the r commands from base, there is a header that points rsh to /usr/bin but it is no longer there, it is now at /usr/local/bin, as a result of that, rcp fails 13:43:05 apparently the issue shall be fixed just by changing a header which has hardcoded /usr/bin/rsh 13:43:12 and that file is in base 13:43:44 trying to rule out a power issue with a usb-serial adapter by feeding it 5V directly instead of bus power 13:44:01 ok, so wifibox sort of worked but it's put me behind some weird kind of NAT and IPv6 doesn't work 13:44:13 i assume this isn't how it's meant to work 13:44:26 maybe i configured something wrong 13:50:09 the suggestion is the networking depends on what the guest exposes 13:51:30 I have horrendous trouble with Linux wireless, let alone Linux wireless in a VM on my laptop! 14:02:48 ok seems like wifibox does work with ipv6, had to rtfm a bit 14:02:54 traceroute6 to hemlock.eden.le-fay.org (fd12:8247:3:1::5) from fd00::1, 64 hops max, 28 byte packets 14:02:54 1 fd00::ffff 0.623 ms 1.204 ms 0.921 ms 14:02:54 2 2001:8b0:aab5:c103::1 2.471 ms 2.967 ms 2.177 ms 14:02:54 3 hemlock.eden.le-fay.org 2.060 ms 2.036 ms 2.134 ms 14:03:02 i guess fd00::ffff is the NAT router 14:03:33 let's see if it's any faster 14:04:27 [ ID] Interval Transfer Bitrate Retr 14:04:27 [ 5] 0.00-10.00 sec 108 MBytes 91.0 Mbits/sec 422 sender 14:04:50 well that's pretty bad for a 2x2 .11ac connection, but i was only getting 20Mbps with FreeBSD iwlwifi, so i suppose it's an improvement 14:05:52 bit sad that i get 550Mbps on my iphone with zero effort 14:05:55 from the same AP 14:06:21 ivy: my solution to wireless issues was an M.2 ath9k card. I get 120Mbps on 5Ghz on 15.0-CURRENT (this is A b/g/n card). Is AC really significant? 14:08:45 duncan: if you only get 120Mbps i'd say ac is significant, yes 14:09:17 i don't really care enough to investigate what's going on here (at least i'm getting more than the 20Mbps i had before) but... 14:09:43 maybe this laptop only does 20MHz or something 14:14:12 I guess what I was getting at is, 108Mb might be the best the card can do 14:14:38 yeah i just rebooted with the wifibox console enabled so i can see what the card is actually negotiating 14:15:32 how on earth do you do this in linux 14:15:56 It's an Alpine Linux VM right? I'd boot that up (it's pretty well thought out) and do a speed test, preferably one run by your ISP 14:16:27 The nominal bitrate negotiated is rarely the speed you get in practice 14:17:08 i already did a speedtest, i'm trying to work out what specifically it negotiated with the AP. e.g. if it's actually using the full 80MHz channel 14:17:21 apparently iw(1) is the right command but usage is a bit cryptic 14:17:36 The interesting question would be whether the VM differs from bare metal with the same PCI device? 14:17:55 channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz 14:18:06 why on earth is it using 2.4GHz 14:18:41 welcome to the world of Linux/UNIX wireless 14:20:51 my response to these crazy scenes was ath9k but there mut be something in between 'workhorse decade and a half old original OSS driver' and '2020s broken WiFi 7 chipsets' 14:21:29 must* 14:22:44 do linux users just not use wifi? 14:23:22 surely there must be a way to make it prefer 5GHz 14:24:25 most users use NetworkManager - it provides a GUI (this is quite good), sugar over low level config options like power saving, preferred channels 14:24:43 you can do similar with iwconfig but it's horrible 14:26:28 but the general malaise is in terms of what drivers expose and how stable they are when interacting with e.g. IOMMU, power management 14:26:56 ivy: maybe more luck (just for testing) to start (as root) bsdconfig, select “Networking Management” and than “Wireless Networks”. It should write to /etc/rc.conf in the end 14:27:43 Maybe your 2.4 and 5.0 can be chosen there? 14:28:05 Kalten: i doubt it since ifconfig wouldn't even accept 'mode 11n' on freebsd 14:28:43 i'm not too bothered, 100Mbps is fine for what i use this laptop for, i just wish i could run iperf here instead of running it on my phone 14:39:30 ivy: promotion of 5GHz band is usualy done on AP side (if supported by AP) 14:39:44 I have nothing to trie it out, but ifconfig(8) talks about something: chanlist (could be `chanlist n`) and channel (could be `channel n` or `channel nt/40` or `channel ht/40`???) 14:39:48 mzar: what do you mean by "promotion"? band steering? 14:39:56 yes 14:40:17 mzar: but shouldn't the client naturally choose 5GHz if the signal is good? that's what all our other clients do 14:40:57 I have not heard of relevant standardisation with this regard 14:41:01 Well: 2.4G has wider range (good for moving around with your laptop) 14:41:38 but 2.4GHz is much more congested, bad if you're anywhere with your laptop 14:41:48 also much slower... 14:42:05 (at least in our case as the 5GHz SSID is 80MHz wide) 14:42:10 so your AP has to support band steering 14:42:31 and it must be turned on 14:42:39 as freebsd is the only client so far that doesn't do this properly i will probably not bother with this, tbh 14:42:50 but i will bear it in mind if it comes up in future, thanks 14:44:08 ah, our vendor doesn't support it anyway 14:44:29 interesting story, so Linux clients prefer 5 over 2.4 without band steering enabled on the AP ? 14:44:33 but it does do .11k and .11r so i would think the client could find a better frequency 14:45:02 mzar: is that a statement or a question? my client (wifibox, which is linux) seems to strongly prefer 2.4GHz 14:45:11 OK 14:45:56 maybe i'll install linux on this laptop and see if it works any better natively 14:46:28 Linux has better WiFi support, that's unquestionable 14:46:52 i agree, but i thought wifibox would make this work as well as it does under native linux 14:47:04 probably yes 14:47:19 maybe signal on 2.4 is stronger 14:47:22 but in fact no, it sticks to 2.4GHz 14:47:49 if i get 600MBps in iperf3 on my iphone and 120Mbps in iperf3 on my laptop... something is wrong somewhere, i think 14:47:57 s/MBps/Mbps 14:48:12 (600MBps on wifi would be nice, heh) 14:48:27 what OS is on that laptop ? 14:48:34 FreeBSD 14.1 amd64 14:49:43 i have a user with Steam Deck (a wifi device that runs Linux) and that does manage about 500Mbps over wifi 14:50:34 hmm... i wonder if the 5GHz SSID is configured for 80MHz, and the laptop's wifi card doesn't support that for some reason, maybe it would fall back to 2.4GHz rather than using a narrower channel? 14:50:40 ha... AFAIR FreeBSD supports only 802.11n, perhaps your phone supports 802.11ac or ax ? 14:50:52 right, i'm not using freebsd wifi stack, i'm using wifibox 14:51:10 no ax here, the AP, phone, and laptop are all .11ac 14:51:35 (well i think the phone does support .11ax, but the AP doesn't) 14:51:58 I would try and produce a minimum working example: Alpine or Debian, try and get 5G. 14:52:00 cool, but AFAIK with FreeBSD you can't use ac yet 14:52:25 no, freebsd doesn't support .11ac, but wifibox does? isn't that the whole point of using it? 14:52:28 does ifconfig show ac for this WLAN NIC ? 14:52:39 ifconfig just shows the wifibox tap interface 14:52:50 i'd have to go turn on the laptop again to see what the wifibox VM says 14:53:00 interesting 14:53:11 mzar: this is unhelpful - this is wifibox, Linux handles wireless, FreeBSD just talks to it 14:53:19 you have put a lot of work to make it working ivy, congrats 14:53:41 i really didn't, i just installed wifibox and set up /etc/rc.conf like the manpage says 14:53:42 s/work/effort 14:54:30 tap interface could be also a bottleneck 14:54:33 and it does work and tbh it works well enough that i don't really mind if i only get 100Mbps... the only reason i care about this is i was having an issue with our APs (not related to FreeBSD) where with ~500Mbps wireless traffic they would sometimes crash 14:54:57 and it felt silly that i had to use my iphone to generate such traffic with iperf instead of a laptop 14:55:20 that's sad story 14:55:28 although honestly, this laptop is old enough that my iphone probably has a faster CPU 14:56:48 You need an MWE. MWEs are good both for articulating the bug report and for (not infrequently) nailing down the problem in the process of composing it 14:56:55 try to trigger this AP failure with multiple UDP streams from your FreeBSD-driven laptop, it could work 14:57:20 i think i fixed the AP issue with a stronger PSU, but we shall see 14:57:22 If Linux proper can't do faster than 100Mbit, you'll know it's probably hardware 14:57:30 duncan: what's an MWE? 14:57:42 minimum working example 14:57:51 oh, right 14:58:09 i mean like i said i don't care enough to actually file a bug 14:58:21 at least i've improved it from 20Mbps under iwlwifi(4) :-d 14:58:31 that's not a bug, only missing feature 14:58:46 omg stop being so pedantic 14:59:29 well, you don't have to report it, but it could be helpful to you later 15:00:00 later e.g. it becomes clear how to got 5Ghz 15:00:42 not worries, let's hope WiFi performance will get improved a bit https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/ 15:01:54 if wifi under freebsd is really this bad i do hope the foundation spends some $$$ on improving it 15:01:56 duncan: what do you mean by "becomes clear how to got 5Ghz" ? 15:01:56 Wifi will improve over time. Thunderbolt/USB4 is a bigger issue 15:02:07 but tbh if i bought another laptop it's going to be a macbook and not run freebsd 15:03:14 (i love freebsd on servers/vms though, and it's also pretty good on desktop) 15:03:37 ivy: it is easier to work out why a simpler Alpine/Debian Linux isn't getting 5Ghz than that in a VM. Fewer variables, easier for others to reproduce. that's why its an MWE. 15:03:49 ivy: cool, same here, it works fine in all scenarios 15:04:29 mzar: well... 15:04:56 i did have to submit a patch to alc(4) to make it work on my desktop by default 15:05:07 (some motherboard have broken MSI-X for this card) 15:05:08 IMHO it's just a waste of time to try to improve this setup working thanks to ivy's effort and tap-driven duct tape 15:05:17 not offending ivy 15:05:18 but let's say "most scenarios" :-) 15:05:41 mzar: why is it a waste of time? 15:06:04 because ivy's time is important 15:06:05 i don't know what you mean by "ivy's efforts", wifibox is nothing to do with me, i did not contribute anything to that project 15:06:47 wifibox did improve my wireless performance from 20Mbps to 100MBps, so i'm certainly not complaining about that 15:06:59 cool 15:07:00 s/MBps/Mbps 15:07:04 (ffs) 15:07:13 no, I don't get it. wireless should perform similarly in a VM to bare metal given same PCIe device access. the interesting question is why not 15:08:18 wifibox is neat but belies real disinterest from manufacturers compared to Linux/embedded 15:08:37 duncan: because there are plenty of bottlenecks, and the most relevant in this case is probably tap(4) 15:09:00 very unlikely, i get 10Gbps from tap(4) in my bhyve VMs 15:09:15 so it's fast laptop 15:10:04 I agree, but I don't know enough about how these things interact to say. Narrowing it down is time-consuming, but it's still worthwhile to do so. 15:10:05 never mind 15:16:31 am I right that the freebsd iscsi initiator does not *verify* the header and/or data digest? I saw in the man-page that they are generated, but are they als verified for incoming PDUs? 15:16:57 I'm asking as my toy-iscsi-target generated invalid digest-values and yet freebsd (and linux) seem to ignore that 15:42:49 f0lkert: you have to read that code and tell us how it works 16:49:44 f0lkert: i think someone is more likely to know on the mailing list, though mzar's playful comment about reading the code might ultimately be true 16:50:33 jmnbtsls1E: I'm considering doing so :) 17:08:54 ok so i found yet another issue. the CH340 driver for FreeBSD is incomplete unfortunately 17:09:13 this is why it was causing issues. It doesn't support any modes other than 8N1 19:26:02 trying to compile an application with FreeBSD 14.1-RELEASE after an upgrade from 14.0, but getting 'undefined reference' on a whole heap of symbols that I know are in SOs in /usr/lib & /usr/local/lib, both with GCC and CLang. File permissions are correct too 19:26:51 GCC's /usr/local/bin/ld cannot find symbols in libPoco*.so files, which are in /usr/local/lib, installed with pkg 19:28:10 same code compiles fine under Linux (GCC), MSYS2, etc. 19:35:13 hackkitten: I'm not familiar with libPoco, but chances are you're just missing some linker flags (LDFLAGS) 19:35:50 probably -L/usr/local/lib 19:37:08 what does the compiler say ? can you post the output somewhere (pastebin, whatever) 19:37:59 compiler AND linker, just post the whole thing 19:40:31 I did add that library path, yes, but it doesn't make a difference. It does find the libs at least (no errors), but cannot seem to use them. Ran a pkg upgrade earlier, seeing whether that helped 19:43:22 oprs: here's the pastebin link command: https://pastebin.com/Md3YJ18R 19:44:56 pkg upgrade didn't change matters, sadly 19:51:05 well there's the obious undefined reference to Poco::SystemException::SystemException 19:51:18 but I also see references to FreeBSD 14.0 in the object paths (obj/x86_64-portbld-freebsd14.0/chronotrigger.o, etc…) 19:52:17 did you properly clean your build tree before compiling on 14.1 ? (i.e. make clean) 19:52:50 yes, I did clean it beforehand, this is also the first time that I'm building this application on this FreeBSD system 19:52:57 cloned it off GitHub earlier 19:53:21 hm 19:53:34 though the 14.0 reference is interesting, yes 19:54:11 that's the output from g++ -dumpmachine 19:54:34 I use those strings to separate different build outputs 19:55:14 with uname -a I get: FreeBSD freebsd-nya 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64 19:56:27 I can try to reinstall the system, do a clean install of 14.1, maybe 20:00:21 I just realized there's a multimedia/nymphcast port, you could just install that 20:00:55 that doesn't explain why it doesn't compile though 20:02:15 didn't know there was a pkg online 20:02:38 I'm the NymphCast developer, so that's why I want to compile it myself :) 20:03:42 lol, I guess that makes sense ) 20:05:45 will be setting up a quick new VM with 14.1, and also GhostBSD alongside it, see whether that works better 20:05:50 thanks for the assistance :) 20:05:51 well, there seems to be a few FreeBSD specific patches: https://cgit.freebsd.org/ports/tree/multimedia/nymphcast/files 20:06:00 ah, was wondering about that 20:06:01 you may want to have a look 20:06:16 indeed, I'd want to integrate those into the main tree 20:06:21 much obliged :) 20:06:26 yw :) 22:16:12 just learn that, in the very same way that I can install python packages from the binary pkg system, I can install R packages. Who creates them? 22:16:20 s/learn/learnt/ 23:00:41 Do you mean who are all the port maintainers? Or who are the upstream devs?