00:00:06 <RhodiumToad> a red box with listings of hex numbers means that it has found errors.
00:01:53 <pr-asadi> RhodiumToad: LxGHTNxNG: https://0x0.st/HPqm.jpg
00:02:02 <pr-asadi> Yes. I guess it has found some errors.
00:03:14 <pr-asadi> It seems it has found many errors.
00:03:50 <VVD> memory errors
00:03:59 <RhodiumToad> yeah. that's not good.
00:04:17 <RhodiumToad> have you adjusted any of the bios timing settings, for overclocking or whatever?
00:04:23 <crb> I am doing a zfs send and receive of a snapshot between two hosts connected by 10G ether.  The process is printing out a line once a second: 17:03:27    188K   rz2_pool/homes@2023_04_21 is this zfs telling me it's sending 1Mbit per second?  Am I interpreting that right?
00:04:25 <pr-asadi> No. Nothing.
00:04:33 <VVD> ddr3 @ 1846MHz 6-6-6-15!!!
00:04:35 <LxGHTNxNG> RhodiumToad: E-series pentium dual core. I really doubt it.
00:05:28 <VVD> oh, no - 923=461*2
00:05:49 <VVD> what voltage do u use for ram?
00:06:03 <VVD> may be set 1.6 or even 1.7
00:06:13 <pr-asadi> VVD: I do not know really. I'm a newbie.
00:06:47 <LxGHTNxNG> pr-asadi: Try removing one of the memory sticks and rerunning memtest86plus.
00:06:52 <VVD> check bios settings for ram/orverclock/etc
00:07:12 <LxGHTNxNG> pr-asadi: From whom did you get this system?
00:07:25 <VVD> it can be 1 module 4GB
00:07:31 <LxGHTNxNG> VVD: E-series pentium dual core. I really doubt overclocking was on the vendor's mind.
00:07:51 <pr-asadi> LxGHTNxNG: I do not know. My father bought it when I was 5. And now I'm 20.
00:07:53 <RhodiumToad> eh, I had a desktop of similar age and it had a load of bios settings for tweaking
00:08:05 <pr-asadi> VVD: I will check those settings, but I'm sure I have not changed them.
00:08:22 <LxGHTNxNG> pr-asadi: Can you identify the RAM configuration in the machine? It may have just one stick, or it may have two.
00:08:30 <RhodiumToad> it can't be quite that old, from the intel specs; they show the CPU as being introduced in 2010
00:08:41 <RhodiumToad> still very old though
00:08:52 <LxGHTNxNG> If it has two, remove one and retry memtest.
00:09:03 <pr-asadi> LxGHTNxNG: It is a two channel. I have two memory sticks. Each 2GB.
00:09:14 <LxGHTNxNG> RhodiumToad: That's 13. Also remember LGA775 played host to Pentium 4/D as well as Core 2.
00:09:22 <LxGHTNxNG> pr-asadi: Remove one of them and retry the memory test.
00:09:34 <pr-asadi> LxGHTNxNG: OK. Let me shut down the PC.
00:09:37 <VVD> I have older one - E6750 Conroe (65nm), E5700 - Wolfdale (45nm)
00:09:37 <LxGHTNxNG> I think it's going to be the one closer to the CPU.
00:09:49 <RhodiumToad> 2GB will leave you a bit tight on ram, you'd probably want to replace it
00:10:18 <LxGHTNxNG> RhodiumToad: Yes, but for identifying the faulty stick this is fine.
00:10:36 <RhodiumToad> yup
00:11:06 <VVD> maybe it can work fine with higher voltage, or higher timings
00:11:14 <LxGHTNxNG> VVD: shut up for one minute
00:11:24 <VVD> lol
00:11:42 <pr-asadi> RhodiumToad: It was 2GB before, I bought another 2GB RAM to have 4GB RAM.
00:12:33 <LxGHTNxNG> pr-asadi: Which stick have you removed? The one you installed at first may be faulty.
00:13:51 <pr-asadi> LxGHTNxNG: The new one. I mean the one which I bought it myself.
00:13:56 <LxGHTNxNG> RhodiumToad: Timeframe clarification: Pentium D 945 was RTM Q3'06. This machine has likely seen a CPU upgrade.
00:14:11 <LxGHTNxNG> if pr's assertion of the machine being bought 15 years ago is correct.
00:14:52 <LxGHTNxNG> pr-asadi: Right. Rerun memtest and let us know if it shows errors.
00:15:03 <pr-asadi> LxGHTNxNG: It shows errors.
00:15:07 <pr-asadi> :(
00:15:25 <LxGHTNxNG> this soon? Power the box down, yank the DIMM, and put in the one you just removed.
00:15:35 <pr-asadi> OK.
00:16:09 <LxGHTNxNG> Attach a sticky note to the faulty DIMM saying "faulty - 30,000+ errors in Memtest86+" in English and your native language.
00:17:17 <LxGHTNxNG> What I want you to do is install the new DIMM in the slot the old DIMM was in. If memtest shows errors, the fault is with the mobo, not the DIMM.
00:18:14 <pr-asadi> LxGHTNxNG: I'm sorry, what is DIMM?
00:18:25 <LxGHTNxNG> Dual Inline Memory Module.
00:18:28 <pr-asadi> LxGHTNxNG: Exchanging the slots?
00:18:30 <LxGHTNxNG> colloquially "memory stick"
00:18:52 <pr-asadi> There is no errors yet.
00:18:59 <LxGHTNxNG> Okay, wait until it wraps around
00:19:32 <pr-asadi> OK. I'm gonna wait. After it is done, I will change the places.
00:19:53 <pr-asadi> The old memory goes to new memory's place and the new one goes to old memory's place.
00:20:27 <LxGHTNxNG> Yes
00:21:17 <LxGHTNxNG> If you get errors at the same location, it may be the motherboard. If you get errors at a lower location, it's likely the old memory.
00:23:03 <LxGHTNxNG> (or you can do this without the old memory, and just put the new module where the old one was; it should still show no errors. if it shows errors then the MB might be broken.)
00:25:41 <pr-asadi> LxGHTNxNG: I have put the new memory in old memory's place.
00:25:44 <pr-asadi> Still no errors.
00:25:47 <LxGHTNxNG> okay.
00:25:59 <LxGHTNxNG> let it run to the full 2GB.
00:26:11 <pr-asadi> Sure.
00:29:49 <LxGHTNxNG> any errors?
00:30:27 <LxGHTNxNG> if not, the DIMM you just removed is the faulty one. you're going to want to stick it with the sticky note i mentioned earlier.
00:31:07 <pr-asadi> Not yet.
00:31:13 <pr-asadi> No errors still.
00:31:48 <pr-asadi> The brands are different. No sticky note is needed. The old one is Apacer, the new one is Kingston.
00:31:52 <LxGHTNxNG> If there's still none after it's done the whole 2GB in all its different patterns, then yeah, the DIMM is kaput.
00:32:04 <LxGHTNxNG> Still need to sticky it so you do not accidentally sell it.
00:32:23 <LxGHTNxNG> and anyone who happens upon it knows it's junk.
00:32:53 <pr-asadi> I do not have sticky note around, but I can mark it. And I won't sell it.
00:32:59 <pr-asadi> DIMM is the old one right?
00:33:30 <LxGHTNxNG> DIMM is a generic term for any dual inline memory module. The one you want to mark as broken is the one that is broken.
00:34:25 <pr-asadi> Well. Should I not put the old one into the place of new memory?
00:34:52 <pr-asadi> You told me to do it few minutes ago.
00:34:58 <LxGHTNxNG> If you want? But it'll just have errors. I would not try to use it.
00:35:17 <LxGHTNxNG> The one not in the machine, mark it as broken. No further testing is required
00:35:32 <pr-asadi> Hmm. So I should buy another one.
00:35:59 <LxGHTNxNG> Yes. But for now, you can get by on just the one.
00:36:03 <pr-asadi> LxGHTNxNG: What would happen if I use it? (I'm not really going to use it, just asking to know)
00:36:25 <pr-asadi> LxGHTNxNG: Of course I can. I used FreeBSD with 2GB RAM for 2 years.
00:36:32 <LxGHTNxNG> pr-asadi: It would experience the same errors that it did 30 minutes ago that caused the hash to be different every time.
00:36:59 <pr-asadi> LxGHTNxNG: Well. It won't be harmful right? Just hash stuff?
00:37:16 <pr-asadi> I did not know about these stuff. Thank you all, LxGHTNxNG VVD RhodiumToad.
00:37:18 <LxGHTNxNG> It will be harmful. Programs will behave in strange ways.
00:37:26 <LxGHTNxNG> Things Just Won't Work.
00:37:37 <LxGHTNxNG> Or they'll return garbage.
00:38:23 <pr-asadi> LxGHTNxNG: Hmm. Thank you LxGHTNxNG. I did not know about these things. Thank you.
00:38:27 <pr-asadi> You all helped me a lot.
00:38:44 <pr-asadi> LxGHTNxNG: VVD: RhodiumToad: Thank you all.
00:46:51 <LxGHTNxNG> if only I had a lot of money so I could snag a skylake (or later) system for this kind soul
00:53:43 <pr-asadi> LxGHTNxNG: One more question. I'm re-doing the checksum on the bad files. They are still saying "FAILED". This is because some things about them are produced/made by the old RAM?
00:53:52 <LxGHTNxNG> Probably, yes.
00:53:56 <LxGHTNxNG> Delete the files, and retry.
00:55:37 <pr-asadi> OK. I'm gonna download again.
01:12:46 <pr-asadi> LxGHTNxNG: It is alright. Thank you for your time.
02:42:11 <morpho> i have never installed freebsd before. Can I expect wifi out of the box on the memstick.img? will wpa_supllicant be there? thankyou
02:44:33 <mcrane> morpho: you can use wpa_supplicant wifi on my dell laptop driver works for wifi
02:44:48 <mcrane> its going to depend on the hardware you have
02:47:55 <morpho> my wireless chipset is in https://wiki.freebsd.org/WiFi/Iwlwifi/Chipsets
02:47:56 <VimDiesel> Title: WiFi/Iwlwifi/Chipsets - FreeBSD Wiki
02:48:25 <morpho> its a thinkpad x270
03:03:54 <LxGHTNxNG> Show me a person and I will show you their crime. I don't care if they're the most moral person we both know
03:07:29 <hernan> hi! im trying to startx freebsd 13 on an intel, however i get the error: vm_fault: xauth: .serverauth does not exist.. pager read error, pid XXX (Xorg).. xinit giving up.. xinit: unable to connect to X server: Connection refused.. xinit: server error
03:07:34 <hernan> any idea how to solve this ?
03:07:52 <hernan> its a new core i5
03:08:14 <hernan> i tried to add i915kms to rc.conf but didnt help
03:21:10 <hernan> trying to startx with root gives same error
03:28:19 <hernan> its a system76 laptop.. that was expected to work flawlessly
03:38:04 <RhodiumToad> hernan: where exactly did you see those errors?
03:38:53 <RhodiumToad> pager read errors aren't expected - any indication of hardware trouble?
03:42:33 <hernan> RhodiumToad:  dont know, i installed a 13.1 and trying to startx i got those errors
03:42:42 <hernan> trying to install 13.2 now
03:43:08 <hernan> but those errors appear after "startx" command
03:43:19 <hernan> and i had exec i3 in .xinitrc
03:43:23 <hernan> with i3 installed
03:43:39 <hernan> thanks for the help RhodiumToad
03:44:19 <hernan> i will need to sleep now
03:44:33 <hernan> will try again tomorrow
03:44:53 <hernan> thanks so much =)
08:16:00 <meena> <04:28 <hernan> its a system76 laptop.. that was expected to work flawlessly ⬅️ maybe by now the WiFi works
08:41:31 <_xor> Hmm, I wonder if this could be a reasonable alternative to poudriered (which seems to have stalled?)...
08:41:33 <_xor> https://github.com/Nukesor/pueue
08:41:34 <VimDiesel> Title: GitHub - Nukesor/pueue: Manage your shell commands.
09:55:14 <VVD> pr-asadi, there is a small probability that your faulty memory stick can work if you manyally increase voltage and/or timings
09:56:49 <asoija> hello. Is there no Chrom{e,ium} pkg for arm64 in 13.2-RELEASE? Firefox broke on the update from 13.1 (segfaults every 5min or so) and I'm looking for another browser. I was surprised not to find them in the pkgs and I'm now left without a serious browser in my Raspberry Pi
09:57:40 <asoija> alternatively, does anyone suggest another browser that isn't Firefox or Chromium that can do banking with relatively little hassle?
11:47:49 <ixmpp> i like qute
13:39:12 <rustyaxe> oof browsing the web on a pi sounds horrible :o
14:18:58 <gzar> it shouldnt be, but the js devs ruined it for everyone
14:19:26 <gzar> and the possible py-script devs will make it 10 times worse
14:26:54 <wormwood> greetings, how are jails worked with now-a-days? I see iocage ( and perhaps a few others ) have been abandoned. Is it recommended to use bsdinstall or the older methods using system src and compilation?
14:28:37 <Demosthenex> iocage abandoned? i use bastille, but i thought iocage and ezjail were around
16:46:54 <asoija> rustyaxe: browsing with full Firefox on the Pi4 was actually quite usable in 13.1-p7, comparable to a 2012~ mid-hi range laptop. I think it was some powerd magic, because no Linux distro ever reached that sort of performance. But 13.2 upgrade broke the browser so I'm sort of annoyed. Might just roll back and sit around until 13.2 matures a bit :P
16:47:48 <asoija> and that including the whole Javascript framework madness nowadasys, and even (gasp!) Office365
16:54:41 <rustyaxe> idk my high end 2012 vintage laptop (dell latitude) is becoming a relic :o
16:59:33 <asoija> ayy I still have my latitude from 2006 in my parents' place. It can do my banking and even online shopping so I take it's still good!
17:14:43 <debdrup> it's probably not powerd, no.
17:20:09 <Onepamopa> Does anyone know 13/stable fails compiling with " cc: error: no such file or directory: '/usr/src/sys/amd64/linux32/linux32_support.S' " -- there's the file but with a lowercase "s"
17:25:25 <mason> Onepamopa: Might be worth a bug report.
17:25:50 <Onepamopa> by the time they read it, someone would've committed a fix already
17:28:06 <mason> Onepamopa: I repeated this on EFnet in a developer-heavy channel.
17:38:26 <mason> Onepamopa: It's being looked at now.
17:40:16 <mason> Onepamopa: They said it compiles as-is, with .s, as of commit 517ccb7c8061ace6565fb27f8f0de7bb9305e853, so maybe update?
17:40:38 <Onepamopa> well, maybe they should checkout a fresh source tree and try again ?
17:40:47 <Onepamopa> or do they need a screen shot ....
17:41:15 <mason> Ah, they tried from main, and they're trying again with stable. I assumed wrong.
17:41:58 <Onepamopa> 1. git clone the src tree; 2. git checkout stable/13 and then try to compile ....
17:42:19 <Onepamopa> the "master" tree does compile, but stable/13 doesn't
17:43:17 <Onepamopa> feel free to reproduce
17:43:36 <mason> Onepamopa: I just run releases. Are you compiling from an earlier stable/13?
17:43:53 <Onepamopa> from 13-stable to 13-stable
17:44:03 <_xor> Looking for some quick suggestions: I have a directory of packages (*.pkg files). I want to delete all but the latest version of each package (e.g. Given files curl-7.1.0.pkg, curl-7.2.0.pkg, curl-7.3.0.pkg...I want to delete all EXCEPT curl-7.3.0.pkg). What different approaches can be taken to reliably accomplish this?
17:44:22 <pr-asadi> VVD: I have to increase the voltage in BIOS?
17:44:59 <mason> _xor: Programmatically identify each base name, then sort of a list of each and keep the head or tail or however you want to do it.
17:45:23 <_xor> Originally, I was going to sort the filenames, remove non-duplicates, and then just delete all but the most recent one from that list. BUT, I'm not sure which character to split the packages on, since '-' isn't reliable.
17:45:25 <mason> Onepamopa: What's the top commit?
17:45:34 <Onepamopa> mason do tell them to do git checkout stable/13 and compile
17:45:53 <_xor> Right, that's what I was going to do, but there are cases where you could delete packages that were meant to be kept.
17:45:55 <mason> Onepamopa: Might be easiest for you to hop on EFnet/#bsdmips to connect directly.
17:46:46 <_xor> Gah, I just had an easy way to do it in my head but I lost it.
17:47:22 <Onepamopa> mason does efnet have a webclient ?
17:48:53 <mason> Onepamopa: Interesting, so I learned about https://ci.freebsd.org/tinderbox/ thanks to your making a noise.
17:48:55 <VimDiesel> Title: FreeBSD Tinderbox
17:49:12 <yuripv> _xor: to make sure you parse name/version correctly, try using `pkg query --file this.pkg <pattern>`
17:49:14 <meena> Nice
17:49:31 <mason> Onepamopa: Hm, yeah, looks like these IS one. I'd have thought not: https://www.irchelp.org/networks/efnet/servers.html
17:49:32 <VimDiesel> Title: IRCHelp.org — EFNet Server List
17:50:12 <Onepamopa> uhm.. "We couldn't connect to that server :(Unknown error"
17:50:24 <yuripv> Onepamopa: git rev-parse origin/stable/13
17:50:43 <yuripv> (as stable/13 is a branch and not really a commit which was asked about)
17:50:49 <Onepamopa> 517......853
17:51:06 <yuripv> ok, so it builds for everyone except you, it seems :D
17:51:10 <Onepamopa> (cannot copy, that machine is on another monitor just terminal)
17:51:56 <Onepamopa> yuripv how come? I just clone the src.git repo in /usr/src then go into /usr/src and do git checkout stable/13
17:51:59 <Onepamopa> ***nothing else***
17:52:09 <Onepamopa> then just make -j8 buildkernel
17:52:13 <Onepamopa> and it fails after a minute or so
17:52:22 <_xor> yuripv: Yeah, looking at that very man page right now :D
17:52:46 <_xor> yuripv: Though I was kinda hoping there was a rope-equivalent to pkg-check :/
17:52:54 <_xor> *repo-equivalent
17:53:35 <_xor> Then I'd just build the repo with multiple versions of the same package, run a check on it to generate a list of duplicate dependencies listed, and then delete the old ones.
17:53:44 <_xor> ...and re-run pkg-repo (yeah yeah, inefficient).
17:55:18 <Onepamopa> yuripv if you're telling me that somehow I'm getting a completely different source from git then... I've no words.
17:55:53 <mason> Onepamopa: The suggestion from #bsdmips was that maybe you have something local or environmental that's breaking things.
17:56:02 <mason> WITHOUT_CLEAN=1 or KERNFAST=1 or something
17:56:29 <Onepamopa> yes, I have those, but I'm running a completely "clean" "src" folder (removed src and checked it out from git)
17:56:29 <mason> It build for the person and for Jenkins, so it might be worth identifying what's different.
17:56:58 <Onepamopa> so it builds everything from 0 without having anything changed or "local" or what not
17:57:51 <yuripv> Onepamopa: i'm not telling you anything other than it builds on tinderbox; you also need to clean the obj directory
17:58:01 <mason> Worth a bug then, noting the commit along stable/13 that you're running as you build.
17:58:17 <Onepamopa> yuripv where's the obj directory?
17:58:53 <yuripv> /usr/obj, by default
17:58:56 <Onepamopa> oh
17:59:02 <mason> Possible for it to be elsewhere though.
17:59:25 <Onepamopa> it's in /usr/obj
17:59:38 <Onepamopa> can I safely rm -Rf everything in it ?
17:59:47 <mason> Yes, it'll be rebuilt.
17:59:55 <mason> It's empty by default.
18:00:11 <Onepamopa> ok I'll remove the src folder and everything in the obj folder and will try to rebuild again..
18:00:58 <mason> Onepamopa: You shouldn't need to remove source.
18:01:02 <Onepamopa> just in case ...
18:03:14 <yuripv> FWIW, >>> Kernel(s)  GENERIC built in 196 seconds, ncpu: 20, make -j20
18:03:29 <_xor> That's...quite nice.
18:03:41 <yuripv> $ git rev-parse --short HEAD    517ccb7c8061
18:04:15 <yuripv> _xor: that was for Onepamopa :D
18:04:42 <Onepamopa> yeah yeah I've got a 48 core cpu too, just not on *that* machine ;)
18:06:29 <Onepamopa> for now everything looks promising, no error...
18:06:36 <Onepamopa> so the "cached" objs were the issue
18:11:48 <pr-asadi> Greetings. I have FreeBSD-13.2-RELEASE, there is no telegram-desktpo package. I'm using pkg(8).
18:12:01 <pr-asadi> telegram-desktop*
18:18:43 <meena> pr-asadi: https://www.freshports.org/net-im/telegram-desktop/
18:18:44 <VimDiesel> Title: FreshPorts -- net-im/telegram-desktop: Telegram Desktop messaging app
18:19:31 <meena> https://bugs.freebsd.org/bugzilla/buglist.cgi?component=Individual%20Port%28s%29&list_id=611569&product=Ports%20%26%20Packages&query_format=advanced&resolution=---&short_desc=net-im%2Ftelegram-desktop&short_desc_type=allwordssubstr nobody has complained yet
18:19:34 <VimDiesel> Title: Bug List
18:20:54 <meena> pr-asadi: looks like it's in quarterly, but not in latest
18:21:05 <pr-asadi> Hmm. Thank you.
18:21:14 <pr-asadi> I should switch to quarterly then.
18:25:19 <meena> pr-asadi: might be worth building yourself with MAKE_JOBS_UNSAFE=yes  and see if that fixes it
18:27:29 <pr-asadi> meena: Sure. What does MAKE_JOBS_UNSAFE do?
18:29:04 <yuripv> builds using single make job
18:29:41 <yuripv> that's going to take (a lot) longer than usual, but can fix some failing ports
18:32:30 <meena> pr-asadi: what yuripv said.
18:33:42 <meena> to elaborate on the name: it declares that `make -j` is unsafe (with any value other than 1)
18:34:19 <parv> Is 0 "normalized" to 1?
18:36:41 <yuripv> if (*p != '\0' || opts.maxJobs < 1) { (void)fprintf(stderr, "%s: illegal argument to -j -- must be positive integer!\n"
18:38:26 <meena> now we know!
18:39:04 <parv> phttbbt
18:48:45 <VVD> pr-asadi, yes. Can you show text from both memory sticks?
19:04:31 <debdrup> and we can promptly forget it
19:09:32 <yuripv> :D yeah sorry, i don't know why looking in the code seemed easier than just trying to run `make -j0`
19:10:07 <meena> I was very briefly wondering that, but then I figured, eh
20:08:51 <Emru> Hey, I have a question. I want to install nextcloud with postgres. And, I have postgresql15-{client,server} on my machine, but nextcloud built from ports uses php81-pdo_pgsql, which in turn depends on postgresql13. Can I somehow built it against 15?
20:10:08 <vkarlsen> Emru: You can set DEFAULT_VERSIONS= pgsql=15 in make.conf
20:10:25 <Emru> vkarlsen: thanks!
20:16:22 <meena> CONFIGURE_ARGS+=	--with-pdo-pgsql=${LOCALBASE}
20:16:31 <meena> that is not very helpful
20:16:36 <meena> i think
20:16:41 <meena> but what do I know
20:32:36 <martinrame> Hi, after may hours struggling with a connection to a pptp server I found the problem was my firewall (pf). Now I need help to allow connecting to the VPN without disabling pf.
20:33:50 <martinrame> The interface created by the VPN is ng0, can I add it to pf.conf and allow all traffic pass through it?
20:35:20 <parv> The rule would be: pass out on ng0 ... # Adjust for log, state, protocol, etc
20:42:01 <parv> ... should also add a rule to allow ingress traffic _carefully_ if the connection would be initiated from outside to estabish handshake
20:42:40 <parv> s/estabish/establish/
20:42:51 <martinrame> sorry I was fiddling with pf and part of the conversation was lost
21:08:58 <parv> gone again 🤷🏽‍♂️🤷🏽‍♂️
21:20:25 <Chinese_soup> ttzt
21:20:31 <Chinese_soup> oops, wrong focus
23:38:34 <yuripv> meh, parv's emoji looks decomposed, same as meena's; wonder if it's irssi built without utf8proc or something else