00:00:03 yeah ddr4 price is wtf i just looked 00:00:47 yep 00:00:55 i have a ton of 32gb modules 00:01:08 could even part with 64gb for right price 00:01:10 barely any size and price is wohoow 00:01:33 r430 and r720 mem 00:01:47 so does zfs work now 00:02:20 yep ty 00:02:51 it may be going up due to failures in existing modules 00:03:43 i read it was about the industry retooling for next gen mem mfg 00:03:47 so it's like eol 00:04:17 no doubt insiders made a bundle 00:04:26 speculate -> supply shock -> profit 00:08:30 ah, uch 00:08:48 i know what I wouldn't do if I was the rationing chief 00:17:12 eat all 00:24:03 update: if I turn on AMD DASH in the BIOS it now loads the kernel module without crashing. And then times out. And does not work. 00:24:15 then _unloading_ it causes a kernel panic! cool 00:24:50 oh well, my remote management approach is to shove a USB null modem serial cable into a spare port anyway 00:27:26 Desktop and mobile Architecture for System Hardware 00:27:33 i think that naming sucks 00:40:21 now that this wee gadget is on my desk instead of in a cupboard it is very obvious how hot it gets 00:40:34 maybe I should go find another mini PC for my freebsd server needs 00:41:29 then again I'm in Scotland, there's very few parts of the year where running a mini heater in the corner of the room is a bad idea 00:59:10 zip, how «in Scotland» are you? Edinburgh, or highland and islands? is summer weather severe enough to merit air conditioning? 01:07:45 i doubt any uk is tropical place 01:08:22 but why it has to be in cupboard 01:08:36 without a vent? 01:12:07 Some things only make sense in Scotland. 01:13:41 scottish summers are pretty oppressive lately 01:18:46 ketas a lot of the UK has borderline tropical summers. yes winters are rainy and cold, but summer is a riot of excess heat. not that I'd know, I've not been there in years 01:21:41 yeah really summer does get a little toastier than I'd like 01:22:41 ketas: honestly it's off most of the time because I'm tinkering rather than using it for what I planned to use it for 01:22:52 I don't feel like 'borderline tropical' reflects the reality of UK/Irish weather. It is mostly miserable weather, and then a couple of months that are ok/warm. 01:23:55 misterable 01:24:31 this year estonia is bust again 01:24:39 bust how? 01:24:43 weather wise 01:25:02 weather is warm 01:25:08 but it's not good 01:25:24 everything sucks due moisture 01:26:54 I like tropical weather with an AC that dials into UK weather. It's the best of both worlds. 01:27:42 :p 01:28:12 tropical outside is horrible actually 01:28:43 Agreed. Too hot for me. 01:28:44 not only will mold grow but also all sorts of nasty parasites 01:28:56 True 01:29:01 which will die in winter 01:30:18 i like the old +25'c ... -20'c 01:30:30 those are cycles too of course 01:31:02 anyway i'm now proud owner of old touchscreen thinkpad 01:31:16 should be fun 01:31:35 Hard to go wrong with a thinkpad 01:31:48 yeah 01:31:59 hopefully lasts 01:32:04 but then 01:32:58 just recently someone had new laptop, suddenly didn't charge, took usb c out and replugged, got cloud of smoke and brick 01:33:19 pulled a wrong ticket eh 01:33:44 I've been blessed to avoid horror stories like that, but they do happen 01:34:55 i still have my first, was t60, was n.o.s., did serve me well, started failing and eventually froze and gone 01:35:02 have to look what it did 01:35:15 served past 10y actually 01:35:18 i mean 01:37:00 lid is perfect and carries freebsd the power to serve sticker :p 01:37:26 yeah whatever 01:39:53 i replaced it's ccfl which busted the inverter eventually 01:40:55 i mean they actually are kind of used up goods 06:16:37 any easy way to add bsdinstall scripting to the first time a fresh install boots? i wanna run the freebsd-update fetch, install, shutdown -r now sequence 06:20:30 i use scripted bsdinstall and i always forget to run that manually after first boot :( 06:24:15 ( echo freebsd-update fetch install; echo shutdown -r now; echo rm -f /etc/rc.local ) > /etc/rc.local 06:24:21 ? 06:26:54 tried reading rc.local in man page but can't figure out what it is 06:26:59 wouldn't that run on every boot or? 06:27:08 oh you rm it 06:27:10 fetch install can't be chained tho 06:27:13 yes 06:27:22 it's old thing 06:27:23 oh so that won't actually work? 06:27:39 now executes via /etc/rc.d/local 06:27:46 it does work 06:27:58 well now you can't shutdown hah 06:28:00 :p 06:28:11 no 06:28:36 the /etc/rc.shutdown.local is for shutdown 06:29:37 that hopefully executes once 06:29:42 i never tried 06:29:59 you can also write your own 06:30:10 that checks a file in install 06:31:10 what do you mean fetch install can't be chained? maybe i misunderstood 06:33:24 like can't run both at once 06:33:43 also isn't this time for pkgbase eh 06:34:08 huh? 06:34:14 oh 06:34:17 well i'm not on 15 06:34:28 what do you think about using firstboot service? 06:35:08 wait you could maybe still 06:35:16 i never used it 06:35:31 and now i never will 06:36:54 oh yeah there was that too 06:37:01 you'll never use what? 06:37:10 really hard to understand what you say 06:38:29 kerneldove: it's possible to script sysinstall, but i last did it quite a while ago 06:38:48 and with it, you could drop a rc script to do what you're after 06:39:03 kerneldove: never had reason do try freebsd-update 06:40:53 rtprio, by systinstall do you mean scripted bsdinstall? 06:41:08 yeah, man bsdinstall talks about it 06:41:29 i said like 10 lines up i use scripted bsdinstall. 06:41:42 what i want is, upon first boot, to run the freebsd-update sequence and reboot again 06:41:53 so should i use the firstboot service to do that or? 06:42:12 seems like accident waiting to happen anyway 06:42:25 how so? 06:42:38 i'd just write your own that does the update, deletes $0 and reboots 06:42:54 https://www.freshports.org/sysutils/firstboot-pkgs/ 06:42:56 hmm 06:43:24 why not use the builtin firstboot to do this? 06:44:05 i didn't use it 06:44:23 but it would probably work 06:44:29 what the cis 06:44:32 hence the rc.local && rm 06:45:01 ketas are you saying you don't trust the firstboot service to only run once? 06:45:28 the fuck is firstboot service 06:45:57 i think there is firstboot somewhere there indeed 06:47:32 kerneldove: do you not manage updates elsewhere in config management? 06:48:08 also poking around it looks like there's the package firstboot-freebsd-update for this exact reason? 06:48:17 i only found firstboot lately 06:48:57 Run 'freebsd-update fetch' when the system first boots; and if updates are 06:48:58 downloaded, install them and request a reboot. 06:49:00 indeed 06:51:07 looks good 06:51:11 that pkg i mean 06:51:39 know where i can look at the files in the pkg without installing it? 06:51:43 i'm away from freebsd system 06:52:49 it's a tar 06:52:52 look at the makefile, via freshports or git 06:53:39 ketas: no it is not, it's a single rc script 06:53:42 hmm freshports don't have it 06:53:58 i mean pkg is a tar :p 06:54:22 but if you meant without downloadinf 06:54:23 https://github.com/freebsd/freebsd-ports/tree/main/sysutils/firstboot-freebsd-update 06:54:27 hmm 06:54:28 it's right there 06:55:05 yeah in this case yes 06:55:27 otherwise i don't know if there's pkg explorer 07:04:48 but that doesn't mean it's not a tar if it's made into pkg itself :p 15:43:02 Got an intel fiber NIC, fiber switch, can't seem to get them to work together. Both SFP modules are the same intel model, and I can see each one has light coming out of one of the ports before I insert the fiber cable. I believe polarity is correct, light should go no no light, and vice-versa. 15:43:50 The light for the switch is on for the SFP port, but there is no light on the NIC. I've tried both ports, tried swapping NICs (I have two). 15:48:38 And I got it. Swapped SFP modules between NIC and switch, connection is active and NIC is lit up. 16:31:50 Connection is active, but it's slower than 1gbps ethernet, should be runnig at 10gbps... 16:33:05 Well, 2.5gbps is the limiting connection my my client, but I'm seeing transfers less than 1000kbps 16:43:12 How are you measuring this? With some bandwidth measuring utility such as "iperf"? 16:45:07 rwp: it's what scp is showing. Things seem to be moving faster with KDE, which is weird. 16:46:12 If it were me I would try testing with iperf between two systems as that is pretty raw data transfer and does not have any interactions with encryption or anything. Try with both UDP and TCP. 16:46:46 On one system run "iperf -s" and let it sit. On the other run "iperf -c othername" and let them spew between them for a minute and it will say something. 16:52:23 [ ID] Interval Transfer Bandwidth 16:52:23 [ 1] 0.00-11.68 sec 6.50 MBytes 4.67 Mbits/sec 16:53:58 server interface shows: media: Ethernet autoselect (10Gbase-SR ) 16:55:18 The only thing I might note is that the SFP modules are multimode, my cable is single mode - the vender I bought the modules from listed them incorrectly, and I only noticed when I went to buy more that the model didn't line up. 16:55:43 But if the cable was an issue, would it not fail to negotiate at 10g? 16:58:38 that's different wavelengths, it'll connect, but as you're seeing, won't be quick 16:59:33 single mode is 1310nm, multmode is 850nm 17:00:01 multimode can be 1300nm, which is close, but still barely works 17:06:43 In terms of cost, my best course of action seems to be to buy everything multimode and eat the cost of the cable. I've read that single mode is the way to go, but these runs will be between a few feet to a few dozen feet around the house. I just figured fiber would be better for power use, along with power isolation between nodes. 17:07:51 wipt, That's pretty awful numbers. :-( 17:08:56 when i get a chance to do it i need to reboot my nas and check the bios to see what SOL is set for so i can enable it 17:08:57 My GigE copper two systems say this: [ 3] 0.0-10.0 sec 1.09 GBytes 936 Mbits/sec 17:09:37 i'd love to be able to use it as a makeshift ipmi since i'm not going to be running anything graphical on it (just vanilla fbsd) but i'd also like to be able to see it boot 17:10:19 Macer, I only ever use serial IMPI sol because the serial terminal for booting and installing and controlling a server is totally sufficient to do everything. 17:10:40 singlemode fiber is higher quality than multimode, but for under 200m, it won't matter much 17:11:21 Firmware Build Time : Aug 27 2013 15:47:45 17:11:35 rwp: how exactly do you even connect to it? the web interface causes all types of problems since it's so dated for me 17:13:33 tomorrow i'm going to load it up with ram from an old 1u i'm no longer using. 17:13:48 so i'll probably check on it then since i have to be local without the web based kvm 17:15:21 Macer, "ipmitool -I lanplus -H $IPADDRESS -UADMIN -PADMIN sol activate" Replacing ADMIN and ADMIN with the account name and password that are actually used. ADMIN is the factory default for both. 17:17:18 Note that the system must be configured to use that as the serial console. So for example for me on FreeBSD on a Supermicro X9 motherboard it uses the 3rd serial interface which is not the system default and therefore I must configure comconsole_port=0x3e8 console="comconsole,vidconsole" in /boot/loader.conf so that the system will use the 3rd serial port. 17:17:47 Otherwise you might connect to a serial port that the system is not using for the serial console and that's not going to be useful. 17:20:28 Using that terminal to login will be using ttyu2 on my Supermicro FreeBSD system. 17:20:33 and will that, for instance, give you serial access to the bios if that's necessary? 17:20:43 Yes. 17:21:20 On a server type system such as a Supermicro which uses IPMI. (Dell uses iDRAC for example which is similar but different. HP uses iLO which is similar but different.) 17:21:29 wow... thank you so much. i'll have to look at that 17:21:37 this is an X8 soooo.. pretty old 17:23:32 now i want to reboot to see it work lol 17:23:39 let me try it 17:25:22 Good luck! 17:28:47 hm. so i reboot and didn't see anything. i just saw !, in ipmitool 17:29:16 so it seems like it reboot without the SOL working properly. i'll have to go downstairs and check the bios. i was hoping this was all already set 17:29:59 I don't know anything about the X8 series. Good luck! 17:30:08 yeah.. it's from the days of yesteryear 17:30:17 but knowing i have to use ipmitool is a step in the right direction 17:31:44 Over the network the serial port speed is virtualized and so shouldn't matter. But I found that it still needed to be used consistently through from power up to console login. By default 115200 is used in the BIOS and I would then not ever set it anywhere else and let it be inherited through. That gave me the best result. 17:32:49 The reason is that it isn't actually virtual on the Supermicro motherboard! It's an actual hardware serial port on the motherboard. Which is connected to the BMC and then converted to network. So if the serial port speed is mismatched then you get all of the expected serial port fail when speed is not correctly matched. 17:35:24 gm 17:35:38 how do i get rid of these errors 17:35:47 ACPI Error: Aborting method \RTMP due to previous error (AE_AML_LOOP_TIMEOUT) 17:36:41 i cant even login for minutes when it boots 17:37:10 nomia: what is the software version and hardware platform ? 17:38:01 this is 14.2 and a super old old pc 17:38:07 OK 17:38:30 you can try to book without ACPI 17:38:39 s/book/boot 17:38:44 linux's work fine but i cant ever get freebsd to disable acpi and work 17:39:48 try never FreeBSD, 15.0-BETA 17:40:01 s/never/newer 17:40:09 mzar: disable like this? https://lists.freebsd.org/archives/freebsd-current/2022-November/002838.html 17:40:54 it looks like if i edit loader.conf it will stop booting 17:41:19 can i just do this > 2. Type set hint.acpi.0.disabled="0" on the loader prompt 17:43:09 rwp: comconsole_port and console="..." are separate lines in loader.conf right? 17:43:29 Macer, Yes. I just joined them for the IRC line. 17:43:54 You can set all of those manually, if tediously, at the FreeBSD boot loader screen. 17:43:58 ok. yeah i double checked. i guess remote access was set to com2 instead of 3 (bmc) and it's the same adress you have at 3e8 17:44:14 that's ok. I have it in a position where it can be reboot at will for testing 17:44:17 But if you are not seeing the BIOS screen then things are not set up right from the start. 17:44:37 Are you seeing the BIOS screen? 17:44:41 yeah. i'm seeing it now. i also saw the fbsd boot screen but, of course, it stopped afterwards 17:44:58 yes. seems so. i'm going to adjust the loader.conf and see if i get the full boot 17:45:26 Sounds like you have things very close to fully working. :-) 17:45:55 one thing i noticed as well since i was in the bios was that aes-ni was disabled lol 17:46:17 I enable that option. 17:46:18 like... why? i also disabled hyperthreading because i guess... exploits? 17:46:22 yeah i did 17:46:51 i was wondering why it was off to begin with tbh.. .let me adjust this and reboot and see what happens. hopefully after loader.conf i can finally have some sort of remote access to this thing during boot since ipmiview / java is essentially useless :) 17:47:03 Whenever I benchmark systems I always find them faster with HT disabled. Real cores are faster than fake cores. HT does allow faster context switching but the workload mix is critical to actually being faster. 17:47:23 HyperThreading is a great marketing term for Intel since it is a trademark and therefore AMD can't sell it. 17:48:37 ok. i'm rebooting now 17:48:38 At the boot loader screen you can interactively select "Escape to loader prompt" and then type in these "set comconsole_port=0x3e8" and "set console=comconsole" and "boot" and it should work. Also must be typed in SLOWLY because if copy-pasted in it will garble things (for some reason). 17:49:38 ok yeah. i'm seeing it boot 1990s bbs style lol 17:49:38 mzar: is it suppose to restart the pc when i do OK set hint.acpi.0.disabled="1" and then do boot? 17:50:09 now i am back at geli 17:50:12 The above can be done for an install ISO booting system and then can use the serial console to install FreeBSD. at some point I want to create an install ISO that has this for the installation so that I can simply boot the ISO and then install over the IPMI serial. 17:50:39 nomia, issue command "boot: 17:50:45 "boot" 17:51:11 i think i did that 17:51:35 i choose 3 and then at OK i type set hint.acpi.0.disabled="1" 17:51:38 IIRC you can disable ACPI from the loader menu 17:51:43 and next line is boot 17:52:08 hm. it stalls out after the fbsd boot screen after it loads the kernel 17:52:23 Macer, One more thing from my notes... In order to accomodate the IPMI SOL for the BIOS the xterm size must be 100x30. But the standard terminal is of course 80x24. Set the environment variables to override. export COLUMNS=100 LINES=30 Because there is no SIGWINCH on the serial port console. 17:52:44 "stalls out"? 17:52:59 Yes. I see the fbsd logo and the countdown and the kernel loads and nothing 17:53:19 comconsole_port=0x3e8 17:53:21 console="comconsole,vidconsole" 17:53:23 It's probably booting, try pinging it, using ssh to it. 17:53:23 that's what i put in loader.conf 17:53:28 i can ssh to it just fine 17:53:57 so i mean it's booting afterwards. but it doesn't seem like the console is getting passed to ipmitool 17:54:51 My "sysctl kern.console" says "kern.console: ttyu2,ttyv0,/ttyu2,ttyv0," 17:56:24 Macer, My /boot/loader.conf file: https://termbin.com/4zw7 17:57:03 And unfortunately I must run off now. It's the top of the hour and I must run. Good luck! You are getting close. 17:58:17 yeah mine is essentially the same with regard to the serial console 17:58:28 hm.. i'll look around a bit more. but just the fact i can see it booting is better :) 17:58:38 so i'm sure it's just a config issue with fbsd to use the serial connection 18:16:10 hm. still not working. 18:18:25 https://pastebin.com/NdGcfTri hangs at kernel load... let me look at the handbook and see if i can sort it out 18:19:52 mzar: it crashes as soon as it loads the kernel 18:26:17 i think the issue is that it is using COM3 18:28:58 https://www.pc-freak.net/blog/how-to-disable-acpi-power-saving-support-in-freebsd-disable-acpi-on-bsd-kernel-boot-time/?cid=5308408 18:29:12 (: at least im not the only victim 18:31:22 wait just a second... why is there /boot/loader.conf and /etc/loader.conf? 18:32:33 * Macer facepalms 18:32:38 are they the same file? 18:32:41 OK... guess that had to be in /boot/loder.conf lol 18:32:43 no 18:32:45 they are not 18:34:48 so have i been doing things wrong all this time? i always thought adding kernel options at boot was /etc/loader.conf 18:35:07 and now my SOL console works after putting the console settings in /boot/loader.conf 18:35:31 (: yay? 18:35:42 yeah. it's awesome. but still. that's an hour i'll never get back lol 18:35:46 let me make sure that's the case 18:35:50 going to reboot one more time 18:36:36 i think if i edit /boot/loader.conf i will be finished with freebsd 18:36:39 Yeah. /etc/loader.conf isn't a thing. 18:37:06 it will take me all day to add 1 line 18:37:21 what in the world? 18:37:30 how did i even get that wrong? lol 18:37:48 maybe i edited it using muscle memory one day then it stuck in my brain that's where it was meant to go 18:38:28 i guess we learn by doing (or not doing) ... seriously with that. 18:38:58 Could be! You could always "ln -s /boot/loader.conf /etc/loader.conf" just in case it happens again. 18:39:43 Sounds like you have that all cleared up now, though. Likely won't forget in the future. 18:40:32 i sure won't lol 18:40:41 but yeah i might want to do that. you're right 18:42:03 how can i edit /boot/loader.conf in single user login? 18:42:21 it says read only filesystem 18:42:50 rwp: ok so that was my problem. we'll just try to look past that :) 18:42:53 it's working now 18:43:30 which is absolutely awesome. now i have makeshift kvm with ipmi using the serial console... no more need for crappy java based web interface! 18:44:55 nomia: perhaps you can run an older version of FreeBSD on this hardware instead newest one 18:46:46 mzar: thats why i tried 14.2 so i could learn how to upgrade 18:47:32 (: i learned how to make zfs readonly=no 18:48:06 now i wait 5 more minutes and reboot 18:48:44 incidentally, how does one load a module from the loader prompt? 18:48:58 acpi errors freeze the system so i can only type for 5 seconds every few minutes 18:49:06 I tried doing a `set ipmi_load="YES"`, then I tried unloading and reloading the kernel ... 18:51:35 oh it's load 19:16:46 actual java? 19:16:52 like java applet? 19:17:09 i have hp printserver like this 19:17:32 entire webui is made of several java applets 19:18:14 and then i have dlink ipcam where login is activex object 19:28:24 mzar: do u rly think older fbsd will work? 19:31:34 could work 19:31:42 also, newer 19:31:59 idk why this works fine as single user but not regular 19:32:21 ketas: i get this error with the 14.2 and 14.3 installers too 19:32:34 and latest 13 i think 19:33:12 some supermicro server i read 19:33:25 getting tired of spending dl's on this tbh 19:33:42 hmm multiuser doesn't work? 19:34:12 i would be curious if CURRENT works 19:34:44 because this doesn't seem hw that the support is removed 19:35:17 also, what works in single user? 19:35:52 if i am in multi user it boots but i get errors all over the screen every few minutes 19:36:03 wait 19:36:06 and between everything is frozen 19:36:08 who has which hw 19:36:23 my hw is a super old pc 19:37:04 ACPI Error: Aborting method \RTMP due to previous error (AE_AML_LOOP_TIMEOUT) 19:37:10 yeah Macer had supermicro :p 19:37:28 lots of these errors 19:37:52 i also get acpi errors 19:37:58 but does it boots? 19:38:16 ya 19:38:30 when does it stop? 19:38:31 single user is perfect 19:38:46 so no need to download anything new 19:38:51 if single user works 19:39:20 the freezes start as soon as it finishes booting and gets to login 19:39:32 that's... fun 19:39:52 so i can type root and wait 2 min for it to show up 19:40:00 then hit enter 19:40:03 wait it still works? 19:40:22 (: i dont call that working 19:40:24 nomia: have you submitted bug report about it ? 19:40:49 i was about to ask if any caps bulge in that hw 19:40:51 mzar: no 19:41:06 plase, don't hestitate to do so 19:41:10 the other bug reports i saw werent fixed either 19:41:30 so such bugs were reported ? 19:41:37 ketas: nah this pc works great with linux 19:42:08 does it always take 2min for text to appear? 19:42:18 and on physical console, right? 19:42:26 FreeBSD is different OS 19:42:30 fun, definitely 19:42:37 what's the error message? 19:42:38 nomia: perhaps BIOS update will help 19:42:45 i missed that part 19:42:52 yeah bios update too 19:42:53 ketas: no i get a few seconds to type like normal every few minutes 19:43:02 hmm 19:43:06 then it freezes again 19:43:07 that's right on boot? 19:43:14 i recall that from somewhere 19:43:15 like during the fbsd boot screen? 19:43:20 Macer: its all the time 19:43:33 yeah but i mean is it before or after it starts booting? 19:43:37 o no the boot screen w the red artwork is fine 19:43:49 able to run top -qaHSPs1 19:43:53 maybe? 19:44:04 oh so it actually gets far enough where you login then just freezes? 19:44:16 ketas: gimme a min and i will try 19:44:31 Macer: freezes start before i can login 19:44:33 but then waiting 2min is fun 19:44:59 yeah but you are able to run top 19:45:22 i think so 19:45:26 you don't get like a kernel dump or something? that sounds pretty bad 19:45:31 if it were me i'd be thinking hardware 19:45:40 it will have error messages on it but i think it will run 19:45:58 Macer: its messages like this 19:46:03 if it responds every few minutes for a few sec you can have top from there 19:46:04 but i guess if it runs in single user mode without issue then it's something getting loaded 19:46:05 ACPI Error: Aborting method \RTMP due to previous error (AE_AML_LOOP_TIMEOUT) 19:48:27 hm 19:48:51 but single user mode works is weird 19:49:58 on my old boxes i get i look for any bulging caps in psu or mobo (could do more), update all the firmwares and run memtest86+... then would be nice to run buildworld as test maybe 19:50:12 but that doesn't apply here maybe? 19:50:16 maybe does 19:50:51 oh and new battery :p 19:50:58 sometimes that's fun 19:51:01 is hint.apic.0.disabled="1" still a thing in loader.conf? 19:52:06 ya i added that 19:52:18 it doesnt do anything i dont think 19:53:02 i ran memtest for 3 days and 0 errors 19:53:30 right now i cant type at all 19:53:42 still waiting to login and run top 19:54:22 hell of a bug 19:54:49 since kernel works 19:54:54 single user works 19:55:00 wtf is it :) 19:55:41 so any hw the kernel accesses there, or anything else it runs 19:57:36 of course the system performs much more actual work in multiuser, it would be fun if it pushes power system over limit 19:57:47 no idea about this tho 19:58:09 i'd probably yank whatever i could out of it and disable zfs just to sort out where it's starting 19:58:33 disk works hopefully? 19:58:40 i can run linux on this hw no prob 19:58:42 oh 19:58:58 fancy sw error then 19:58:59 i have an ancient A10 that fbsd just won't run on :) 19:59:02 same sorts of problem 19:59:09 a10? 19:59:20 yeah. ancient AMD APU 19:59:23 now i cant even ctr alt delete 19:59:37 in linux i have to disable the on die gpu power management 19:59:44 cant fbsd run on amd? 19:59:50 i think i recall strange bugs being reported 19:59:51 sure it can :) 20:00:03 i run it on my ryzen 3700x 20:00:15 ok 20:00:25 a10 is fro, 2012 20:00:29 from 20:00:31 ketas: yeah 20:00:34 sounds about right 20:00:39 lol 20:00:50 still works great for debian 20:01:01 you can run much older hw 20:01:08 my macbook pro that i use as a daily driver with fedora on it is from 2013 20:01:31 i yanked out the ssd and replaced it with an adatper + nvme and replaced the wifi module with an intel one so it works out the box 20:01:36 yeah 20:01:42 i have to unbust the psu but i had 2006 amd64 machine 20:01:45 actual amd too 20:01:48 i think fbsd still has the old 32bit stuff around 20:01:51 what are all these methods that keep aborting 20:02:03 yeah 32bit is now going away 20:02:06 :/ 20:02:06 so you can pull the 386 out the closet and run it 20:02:16 oh really? 20:02:19 \csms \rtmp \rbyt \_tz.thrm._tmp 20:02:24 say it isn't so freebsd! i mean i get it lol 20:02:33 probably not actual 386 20:02:40 why not? 20:02:48 have to recompile kernel 20:02:56 for a 386? 20:02:58 can i disable whatev is causing this? 20:03:22 it was upped to minimum 686 cpu iirc 20:03:25 hm... i saw something like that... 20:03:53 i mean i have ran fbsd on actual 486 tho 20:04:32 the first machine i got 20:04:45 i did too back in the 1990s :P 20:04:56 back when the ports tree was so innovative lol 20:05:02 i have no idea how it evolved 20:05:07 66mhz cpu 20:05:31 too bad bsd had to deal with that whole sco unix nonsense lol 20:06:30 nomia... i saw something earlier about that .... something about adding some sort of hint 20:06:31 #include #include 20:06:37 :p 20:07:26 i only installed 4.6 as first one 20:07:53 Macer: i put set hint.acpi.0.disabled="1" in /boot/loader.conf 20:08:04 wait no 20:08:09 no set 20:08:21 only hint.acpi.0.disabled="1" 20:08:44 i think i have to kill power to reboot :( 20:09:15 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202069 20:09:22 i'm not sure if that is related tho and that's very old 20:10:24 bits /6 20:10:29 err 20:10:45 hint.apic.0.disabled="1" <- it's not that? 20:10:53 * Macer points at "apic" vs "acpi" 20:20:08 (: oh 20:21:11 well i changed it but its still freezing 20:23:12 ok i was able to run top finally 20:23:26 top -qaHSPs1 20:23:45 but it is frozen after a few seconds 20:24:33 top process is [idle] 20:25:35 oh hey 20:25:50 [acpi_thermal] is using the most time 20:26:03 can i disable that? 20:34:39 debug.acpi.disabled="thermal" 20:39:38 i tried that with the apic and it is still giving error messages but not freezing yet 20:40:02 top -qaHSPs1 is working too 20:40:32 hmm only 1 set of errors and no more? 20:40:38 you have a lot more patience than me. i'd have given up by now lol 20:46:37 o nope it did error messages again 20:47:01 but no freezing i dont think 20:50:08 not yet :D 21:19:54 oh go fuck yourself This may be because upgrading from this platform (amd64) 21:19:54 or release (14.4-RELEASE) is unsupported by freebsd-update. Only 21:19:54 platforms with Tier 1 support can be upgraded by freebsd-update. 21:19:54 See https://www.freebsd.org/platforms/ for more info. 21:20:02 last thing i want to do is hassle with this 21:26:01 Macer: (: i like winning 21:26:21 i am glad this is working now 21:26:27 mostly 21:30:15 hmm it looks like it still freezes sometimes but much less 22:22:39 nomia: that's fun 22:22:50 thermal is unsure what 22:22:54 fan control? 22:22:59 just temps? 22:23:30 freezes less eh 22:23:32 idk 22:23:36 what runs there? 22:23:44 according to top 22:23:56 ye it is still freezing sometimes but i figured out how to switch consoles 22:24:04 load is not high? 22:24:13 so now the error messages arent a big problem 22:25:06 hm load is up to 3 sometimes 22:25:16 there we go 22:25:25 what exactly runs there? 22:25:29 i cant run pkg updated cuz the xfer keeps freezing 22:25:37 wdym 22:25:47 well load is 3 22:25:47 like what apps? 22:25:51 so wtf runs 22:25:57 idk 22:26:00 3 times over the cpu time 22:26:09 i dont see anything in top 22:26:20 and load is 3? 22:26:32 just zfs things and powerd but no user apps 22:26:48 those top args also show all kernel threads 22:26:54 this system is brand new i didnt even install tmux on it yet 22:27:32 something runs if load is 3 22:27:55 why it runs long no idea 22:28:00 io or cpu 22:28:11 how old is it :p 22:28:20 well it has acpi :) 22:28:35 smth is running and taking all the cpu for a minute i guess 22:28:50 like periodically? 22:28:56 ya 22:29:32 unsure 22:29:44 service crond stop? 22:29:53 but it should not run anything 22:29:56 pkg is updating quarterly data.pkg 22:30:03 so that runs eh? 22:31:19 it is taking 10 minutes 22:31:31 downloads a lil bit and then freezes 22:31:49 freezes whole system? 22:31:52 i am running pkg -d now so i can see progress 22:31:56 yep 22:32:49 disk is bust or something 22:33:02 or it swapa? 22:33:04 swaps 22:33:09 i doubt it 22:33:31 it runs linux w no problems 22:33:56 i put these disks in a friends system to install 22:34:00 oh right 22:34:04 bc of the freezes 22:34:20 i tested them overnite 22:35:29 top says cpu is running 99.9% system 0.1% interrupt 22:35:55 that means the kernel is using all the cpu? 22:36:16 i have to yank all this ddr3 ecc out of my ancient supermicro 1u to toss into my ancient isilon lol 22:36:17 mmm yes 22:36:37 i'm considering turning the old 1u into a router 22:36:39 but below it shows where it goes 22:36:58 if pkg finishes downloading im going to try removing the acpi disable and reboot 22:37:13 no vacuum cleaner noises? 22:38:20 data.pkg 78% now 22:38:21 if it's zfs, kernel shows it in top 22:39:09 shows as [*zfs*] something 22:39:27 you used zfs right? 22:40:08 ya 22:40:20 no errors in zpool status 22:40:38 thats good but 22:40:52 unsure where cpu goes 22:41:21 maybe kernel errors 22:41:25 zfs uses all resources isn't new 22:41:43 disk is not full? 22:42:01 that also causes slow io and high frag 22:42:26 outside of pkg, it runs? 22:42:37 or wait you told it won't 22:42:53 so load is 3 after boot too? 22:42:56 and keeps there? 22:43:05 it goes up and down 22:43:22 up when it freezes and then back down when its not 22:43:40 hmm 22:44:04 and no single user issues? 22:44:29 unsure what periodically freezes the system in multiuser 22:45:09 no way to get actual top outputs? 22:46:30 i can run the command u gave me 22:48:03 here it gives me 22:48:07 PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 22:48:07 11 root 155 ki31 0B 32K RUN 1 254.7H 96.78% [idle{idle: cpu1} 22:48:10 ] 22:48:12 11 root 155 ki31 0B 32K CPU0 0 249.4H 96.78% [idle{idle: cpu0} 22:48:15 ] 22:48:19 which is like 2core and idle 22:48:39 i'm curious what's below ir 22:48:42 it 22:48:57 as load has to come from somewhere :) 22:49:54 even if that thing comes from kernel, it has to come from somewhere within kernel 22:51:18 what does dmesg say about this? 22:54:53 i just realized fbsd doesn't have a dmesg -w equivalent 22:57:17 dmesg is full of ACPI Error: Aborting method 22:57:49 and ACPI Error: AE_AML_LOOP_TIMEOUT 23:01:02 oh -w is followtail 23:01:25 but you can pipe most of kernel into syslog 23:01:29 and tail it 23:01:51 at least 23:02:38 whatever fancy acpi bug is it 23:05:03 oh there's kern.msgbuf_show_timestamp 23:05:07 i found 23:26:26 tmux freezes even worse than a regular login :( 23:41:21 crazy resource exhaustion0 23:41:22 ? 23:41:34 or just something blows 23:41:51 what, i have no idea 23:52:21 i think its just random freezes maybe 23:52:26 idk 23:52:58 i keep finding tons of pages about AE_AML_LOOP_TIMEOUT for linux