02:13:19 markmcb: quick question on the lightbulb by the search button.. maybe a way to know that if you click it.. it goes from "dark" to "light" mode and visa versa? tooltip? 02:15:40 and surprsingly i like the light mode as a default over the dark mode.. but i could be picky 02:45:01 voy4g3r2: there should already be one that says "Switch to light/dark mode". i see it on mine. 02:45:52 sorry i may misunderstand, i should see a tooltip? 02:47:39 yes, if i hover my mouse over it, i see the "switch" text. if you don't, let me know your browser and i'll investigate. you may have to hover for a second or two for it to appear depending on your browser. 02:49:00 ohh.. there it is 02:49:10 took about 2 seconds.. never mind.. do not mind my nonsense 02:49:19 i as like.. oohh a cool button.. must press :) 02:50:42 as for light/dark default, it should default to whatever your browser reports as a preference, which may be set in the browser, or by your OS informing your browser 02:57:10 yeah, i default to dark mode.. i just checked.. i use brave on mac os 10.15.7 as a reference point 02:59:18 i think that is all i can find.. if you are looking for any more suggestions.. let me know, that was a fun activity.. sure as hell beats learning about an assay and degrandant method using gas chromotography machines 02:59:30 it makes my head hurt.. lab people are an "odd" group.. of nerds 03:00:30 sounds complicated :) thanks for all the feedback! 03:00:55 https://chem.libretexts.org/Bookshelves/Analytical_Chemistry/Supplemental_Modules_(Analytical_Chemistry)/Instrumentation_and_Analysis/Chromatography/Gas_Chromatography 03:00:58 not too bad 03:01:46 trying to develop an interface between equipment and software.. is not easy when you are "lost" hearing.. well this peak has this indication but if you use this solvent in the pressurized gas chamber.. using a glass needle.. at this diameter the peaks may look the same.. but are not 10:00:44 The interesting people clearly hang out on #freebsd :) 10:02:24 >:)-|--/-< 12:43:30 markmcb: I dislike sticky headers, especially if they are that big and think the text in the header isn't really readable and the opacity thing makes it worse, no idea what foreground color would be good for that red background, also on the current main page, when you hover "Documentation" in the header you get a menu with more links (and for other topics there too) 13:02:22 nimaje: thanks. if you're referring to the overall site header, please ignore, along with the footer. i used a mkdocs-material template for a rapid prototype. i'll work on integrating with the header/footer you see on the the existing freebsd documentation page. (referring to https://freebsd.markmcb.com for anyone wondering) 15:33:49 Has anybody present ever installed FreeBSD on an RPi? 15:36:04 yeah 15:36:23 Any special problems/difficulties? 15:36:43 nope. dd the image, boot the pi, let it resize the partition, good to go 15:37:12 No installation -- just running from an image? 15:37:44 I ran it on a Pi awhile back. Can't recall any major issues 15:42:45 yep, just run from the image 15:47:54 I think not all of the hardware is supported quite as well as Linux, but that's to be expected and I can't remember specific examples 15:58:26 sd cards are so cheap, you've got nothing to lose trying it 15:58:34 just slap your old one in of you don't like it 16:48:53 I wonder if it will support RPi DAC+ . 16:56:28 * hodapp tries to remember why he quit using FreeBSD on his Pi... 17:12:08 hodapp, Indeed. 17:12:40 How do you guys set up media automounting on your desktop/laptop FreeBSDs? It seems not very easy to me... 17:14:38 ant-x: with autofs? 17:19:00 I have found and installed -- a non-trivial shell script for devd. I think I installed after reading the criticism of autofs here: . 17:19:55 Can autofs mount media with rw permissions for unprivileged users? 17:32:09 ant-x: I suppose it depends on definition of unprivileged users. But, I don't think anything can mount anything for unprivileged users? 17:32:27 Well, aside from root or something. And, even then, only root would have those privs. 17:39:58 I didn't ask whether an unprivileged user could mount media, but whether automounting could be set up to make the media fully accessible for non-privileged users. In the context of the desktop FreeBSD, I mean my normal user account on PC. 17:41:14 No 17:58:40 Why not? I don't want to sudo, doas, or change to root to write an a USB flash drive... 18:02:53 The abovementioned `automount' mechanism by vermaden does mount removable media with rw permissions for normal users. 18:41:10 well then use that 18:57:06 OK, but I was wondering about what's available in FreeBSD natively, without resort to third-party solutions. 18:59:00 he mentioned autofs is native 19:00:14 Yes, it is. He also says it mounts on first access, rathe than when the media is inserted. And he does not say anything about the permissions on FSes mounted by autofs. 19:00:20 ant-x: allowing unprivileged system users to mount given devices can be set with devd(8) and devd.conf. Some stuff there is pre-set and you only need to add given user existing in /etc/group (group(5)) 19:01:30 used autofs quite a bit. It only mounts when you actually do an operation on the mounted device 19:01:53 regis, Thanks. I have found that accounts can be configured to have mount permissions: . 19:02:08 ant-x: Apologies, scratch it! 19:02:09 works quite well on networked devices like nfs and smb too 19:02:19 ant-x: it's devfs.rules(5) 19:02:32 BarnabasDK, I suspect it is not very convenient for USB sticks... 19:03:03 no, then it is the oter way around 19:03:24 ant-x: Yup - this stuff you've found by yourself. Again: apologies for my comment about devd. 19:04:25 but assuming the drive is inserted and not mounted 19:05:30 no systemd on freebsd fortunately 19:06:19 I am not calling for systemd. 19:07:48 no :-) did not think you where 19:08:58 Hmmmm. I downloaded , extracted the image, dd'ed to a MicroSD card and tried to boot my RPi 4 from it. It starts booting, but goes into reboot again after some 20 seconds into the boot process... 19:09:52 turn off secure boot? - just a guess 19:09:59 I don't think I needed to prepare the SD card in any way, because dd writes raw, didn't I? 19:10:09 then enroll the key and turn it on again 19:10:21 provided your bios cooperates 19:10:29 Let me check. 19:11:38 raspberry pi's have a secure boot? 19:11:43 what? 19:12:42 I think pi4+ do 19:13:10 never used it o 19:13:25 .. on a pi though 19:14:20 At least, I got me to use both two computers simultaneosly. 19:14:48 ant-x: I haven't played with RPi 4 (initial RPi 1 from 2011 works great 24/7 for 13 years now and suits my needs) but if you got it to boot - you likely dd'd the image properly. No idea about the Secure Boot stuff on RPi 4 though. 19:15:27 Well, it it fails after detecting my mouse, so I guess I am getting /past/ whatever BIOS barriers may be there... 19:15:38 ant-x, you definately do 19:15:58 Try to unplug USB devices, just to test if it boots without mouse and other such devices 19:16:01 so does it panic? 19:16:13 regis +1 19:16:26 I do not see any panic messages, will try without devices. 19:19:33 regis, it has booted without mouse and keyboard, and recognised the keyboard when I plugged it back in. Thank you. 19:19:40 There are tons of errors, however. 19:19:59 lets have it 19:20:50 Now, the prompt is mountroot> , and typing ls gives: Invalid filesystem specification. 19:21:55 It is rebooting again. I will check dmesg. 19:22:08 then the system really did not boot - not finding the root system 19:22:34 I think this is more a problem with the image you try to boot than the hardware you try to do it on 19:22:44 Yes. It prints that error in answer to /any/ command. 19:22:45 but it is just a gut feeling 19:23:10 ant-x: Doesn't seem right - it got up to the boot loader but there's nowhere to read kernel and userland from. Far from normal. Are you sure that dd image was written in full to the SD card? What's the size of the card? 19:23:13 Hmmm. Did I download the wrong image? There was only one for RPI, perhaps I misclicked.. 19:23:41 dd took a long time to write it, and reported no errors, and about 5 GB of written data (IIRC). 19:23:59 ant-x: The image you mentioned (arm64-aarch64-RPI.img.xz) seems right. You did unpacked it to img before flashing the card, right? 19:24:46 regis, I do not think he would get to the mountroot> prompt then 19:24:47 Of course, I unxy'ed it. 19:24:58 The card is 64 Gb. 19:25:15 I have to recheck whether I downloaded the RPI image. 19:26:25 BarnabasDK: I've seen weird "compatibility layers" trying to make sense of stuff and failing. Just wanted to make sure. 19:26:35 regis, sure 19:26:55 but the system did pick up on some of the boot sector here 19:27:26 Yes, I downloaded the right one. 19:28:45 and I really don't think ARM does much in the way of compability - they mostly do their own thing 19:28:47 Check the controls sum, probably? 19:28:54 ant-x, good idea 19:29:23 or more specifically compability with amd64 19:30:32 Yikes, the control sums of the website are for .xz, rather than for .img. 19:30:45 ha ha 19:30:48 as one would expect 19:31:53 OK, re-downloading... 19:31:56 well, the latter would take into consideration faulty hw when unpacking 19:32:28 By the way, extracting takes time on RPi (with Raspbian). 19:32:43 ant-x, they where never made for speed 19:33:02 Were you extracting xz on RPi itself and flashing it on its own card...? 19:33:36 regis, extracting it on RPi, and flashing to another SD card, connected via a USB adapter. 19:34:04 ant-x: Any chance you could do this part on another hardware? 19:34:14 Yes, but not now. 19:34:24 All I can do now is repeat the process on RPi. 19:34:51 Or use RPi USB flasher program (could it work for third-party images?) 19:36:59 it has quite a list of images already 19:37:17 did you check to see, if FreeBSD was under the "headless" part? 19:41:24 https://forums.freebsd.org/threads/is-it-possible-to-boot-freebsd-from-usb-using-raspberry-pi-4.91925/ 19:41:36 wb7odyfred post 19:41:39 ant-x: I'm just guessing as you're quoting the proper procedure, but I never found using filesystems mounted under RPi's USB ports reliable. And while iirc the SD socket works under the USB stack, I've had issues with HHD and SSD drives connected to USB even when they had external powering. In your case under-powered SD card connected via an USD adapter is not an issue. But my point is: I've never 19:41:41 had issues like this when I was flashing SD cards on MacOS or PC Linux. 19:42:14 The native RPi Imager asks me for a root password, but there is none! 19:42:25 so blank? 19:42:28 I'll have to reconfigure my Raspbian for that imager to work. 19:42:46 RPi does not use root authentification by password by default. 19:42:56 the dude in the freebsd forum above seems to have made it work 19:43:33 eg using the rpi tool to install freebsd 19:43:34 Perhaps I can start the imager via sudo, for a simple solution. 19:45:39 sudo rpi-imager has helped with the permissions. 19:47:06 if you are to write directly to devices, you almost always need root 19:47:25 sudo isn't native to FreeBSD, but maybe available on RPi images as it's released under ISC and not GPL-like license. But if you haven't got an error after `su` and running `dd` it shouldn't be an issue calling for sudo. 19:47:42 Yes, and the Imager programs aks me for a root password, even thought password auth is disabled for root on Rpi. 19:47:58 ok .. then just be a rebel and do sudo bash .. 19:48:07 My RPi has Raspbian on it, where there is of course a sudo. 19:48:39 you should be at bash# 19:48:48 BarnabasDK: bash is definitely not available natively. See my license-related comment above. 19:49:00 Although, if it was done on Raspbian or such... 19:49:03 any shell then 19:49:14 BarnabasDK, I have found only one RPi image: . 19:50:02 I am glad FreeBSD uses a more standard Bourne shell by default, and a more standard vi (nvi), rathen than vim. 19:51:21 regis, the image is flashing, and my cable shows a power of 4.4W. 19:51:26 ant-x: I'm not but it's just license discrepancies. I personally use a lot of GNU stuff on FreeBSD. It just can't be bundled with the default installation due to the licensing stuff. 19:52:13 Does FreeBSD has something like GNU screen, only non-GNU? 19:52:22 s/GNU/GPL/, duh. 19:52:31 Yes, I read it that way. 19:52:38 No, I didn't :-) 19:53:36 ant-x: screen and tmux are available via ports and pkg. These are mechanisms providing an easy way to install GPL software. It just can't be bundled within the default installation. 19:53:59 `pkg install screen`. That's it. 19:54:04 Yes, I know. 19:54:08 (about pkg) 19:54:26 It has bash and vim too, likely. 19:55:25 The native RPi Imager is doing more than dd: a) zeroing-out start and end of the medum, b) veryfing after burning. 19:56:14 I will be disappointed if it does not boot still. 19:56:22 * ant-x crosses fingers on all the four limbs. 19:57:23 ant-x: Back to your problem. My only idea is that you should test if the issue appears if you flash the image on another machine. It's only based on the fact that doing it this way always worked for me. I believe I never tried to flash images onto devices connected to RPi and somehow poor experience with RPi USB ports, both under booted FreeBSD and "native" Raspbian. 19:58:28 OK. If that fails, I'll try it. Perhaps, then, you got an broken RPi, a poor power-supply, or a poor power USB cable. 19:59:31 ant-x: Also, I don't know "RPi Imager" but you also have mentioned that "dd took a long time to write it" so I guess that you tried using plain dd, too? 20:00:09 regis, my first attempt was with the plain dd. Now trying with RPi Imager. 20:00:43 The news Raspbian uses a different GUI -- slow like cold honey. The verification is complete, I will not boot my RPi. 20:03:12 regis, rpi imager is a tool for writing flash images to your sdcard. Not ported to freebsd. But it is definately in debian related linuxes 20:03:30 It has booted with a similar wall of errors. It failed to mount rootfs with error 19. 20:03:47 BarnabasDK, I am using RPi imager from under Raspbian OS. 20:04:57 in all honesty maybe you are better of asking this question in #rasberrypi 20:05:01 I can try some other OS now -- just to make sure the problem is /not/ in the FreeBSD image. 20:05:16 I could try them, too 20:06:09 Well, my oldschool RPi 1 sports Raspbian as FreeBSD has no support for 1-wire sensors I slapped onto its GPIO. But I've never had issues with booting FreeBSD on RPi 1, 2 and 3. I just never bought 4 and tested it with FreeBSD, after the COVID-related chip market shitshow. I've switched with some of my basic needs to even less power-hungry ESP32. 20:07:01 BarnabasDK: I got the idea and am just mentioning that I never used it. Plain `dd` never failed me. 20:07:17 I have a Pi 4 which I use approximately never 20:07:49 it's in an awkward niche between way overpowered for a lot of tasks, and way underpowered for others 20:07:50 I have 11 pi 4s .. all running pios though .. 20:08:06 I still call it Raspbian because I always forget the name changed 20:08:30 Guys, I have gotten into the admin console somehow. If you have ideas what I can check from there, shoot! 20:09:06 "admin" console ? 20:09:57 What is it called on FreeBSD? The single-user mode, or somehing. The KVM switching makes it unresponsive, however. 20:10:54 It was some console with a limited set of functions. 20:11:21 It can be provided by the bootloader on the RPi image... 20:12:02 hodapp: very good description of the under/over-power abyss experience. I've seen folks running desktop on Pi 4 and folks wording the experience in a way I won't quote, when trying to run ML models on it even with some "hats" marketed as capable of image recognition and such. 20:16:11 it's like an overgrown microcontroller and/or anemically slow "real" processor 20:16:50 it's still neat what some people have done with it, in the same sort of way as older video game consoles where the hardware was fixed and people found a way to really exploit the fast paths it *did* provide 20:19:50 ant-x, the bootloader definatly does not provide single user mode 20:20:15 you need the kernel loaded for that 20:21:02 issue "boot -s" at command prompt 20:23:58 It's too difficult, becase KVM switching makes that console useless. I am not trying to boot another image, using the same procedure. If I succeed, it will prove something is wrong with the FreeBSD image. 20:25:54 add "-" to /boot.config 20:25:59 add "-s" to /boot.config 20:27:11 mzar, you mean locate it in the image from under another OS/machine? I can try that after this test with the Void Linux RPi .img . 20:27:16 mzar, we are not trying to boot into single user, just boot at all 20:27:34 first things first 20:27:54 Am I right that dd if=image.img of=/dev/sda is sufficient to burn an image to an SD card? 20:28:10 bs could be important 20:28:11 OK 20:28:24 aka block size 20:28:35 bs for speed-up? 20:29:02 I was using bs=1MB according to the official FreeBSD instructions. 20:29:11 should be ok then I guess 20:29:33 never used anything else than these three parameters 20:29:47 if,of and bs 20:30:16 bs most important if you write to a phys device I think 20:30:17 hodapp: remember the original raspberry pi was a ploy by broadcom to sell a really, really bad video processing microcontroller no-one would buy. they are what is available and popular (and many alternatives are much worse) so we're stuck with it 20:30:54 duncan, well this is version 4 of the pi 20:31:13 Void Linux booted perfectly, after dd with the default bs. 20:31:38 > bs for speed-up 20:31:50 flashing speedup only, it's the block size written by dd 20:31:58 Shall I try to dd without bs with the FreeBSD image, or is chance it helps near zero? 20:33:01 ant-x: please don't hesitate to do some experimentation 20:33:08 Void Linux event set the correct graphics mode for my 1600x1200 display connected via VGA. 20:33:18 bs only impacts writing/reading speed (in this case writing) and has no impact on whether the result is written properly on the destination. It can only speed-up the procedure of writing an image on the SD in this case. 20:33:29 mzar, +1 20:33:35 that's Linux, we are on #freebsd channel 20:34:32 mzar, well since it is compiled to a RPI image you might expect it to behave somewhat similar 20:34:57 I tried a Linux image to see if I should get the same error as with the FreeBSD image -- that's fair use. 20:35:19 ant-x, agree 20:36:05 mzar: read-up. He did everything properly and tried different tools. My only guess is that there's some flaw with the USB adaptor used on Pi to write an image on USB-attached disk, to only boot it later on the same Pi. I've suggested to flask this image onto the SD card using a separate Mac or Windows/Linux machine because in my case that always worked properly. 20:36:43 regis, noted. But observe that a different .img booted properly. 20:37:02 or .. maybe try an earlier image .. if you can find it - just to rule out any problems with the image you tested 20:37:23 ha.. so guys are flashing SD via usb sd-card reader from RPi ? 20:37:39 Yes, and it works in /some/ images. 20:37:58 The RPi Images has a verification stage, it passess OK. 20:38:00 ant-x: Cool! And sorry - I focused on another channel for a moment and haven't fully caught up here. 20:38:32 ant-x: Ah, so Linux booted but not any FreeBSD. Got it. 20:38:39 TBH I'd blame this USB device and it's support from FreeBSD, encountered problems wiht them in the past 20:39:47 mzar, but the image was written in linux? 20:39:48 regis, Yes, although I have tested only with one Linux image and one FreeBSD image. I can try another FreeBSD image for RPi if I find it. 20:40:05 or .. pios 20:40:09 BarnabasDK, both the images are downloaded, unpacked, and written on Raspbian on RPi. 20:40:16 yes 20:40:30 so .. freebsd drivers - not in the loop of failure 20:40:51 not until you boot that os at least 20:41:05 or am I wrong 20:41:09 Is there a way to pause the booting process to read all the errors from the screen. It has several register dumps. 20:41:38 I'd hate to record a video of the monitor to do that. 20:41:58 * ant-x has no smartphone. 20:42:24 BarnabasDK: As I undersand: FreeBSD with mouse conncted is in a reboot loop, with USB devices connected only boots until bootloader but doesn't see any filesystems too boot from, but Linux loads fully(?) 20:42:34 ant-x: ^ do I get it right? 20:42:35 use dd with bs=1M at least, issue "sync" command later and wait for command prompt - should do the job 20:43:02 sorry, with USB devices DISconnected! 20:43:05 regis, I do not think we ever achived a fully running os 20:43:13 regis, somehow or other, it stopped loop-rebooting even with the mouse, after flashing with the RPi Imager. Sorry, if I did not report that. 20:43:51 mzar, why the sync command, if dd reports when it has finished? OK, I can try that. 20:44:04 ant-x: But with FreeBSD, it never got past the boot loader. With linux you got the actual OS loaded. Correct? 20:44:13 regis, confusion about "admin" consoles, no consoles and boot prompts 20:44:28 sync && sync && poweroff - old school 20:44:39 regis, In Linux -- all is well, yes. In FreeBSD -- I don't understand exactly where it breaks, but there is a wall of errors, and no rootfs at the end. 20:45:16 OK, I will now try the FreeBSD image again, and sync & sync & poweroff. 20:45:32 Can anybody point to an older version of an image for RPi 4? 20:46:03 ha.. one "sync" will be enough nowadays 20:46:07 Later I can try to record the video of the boot process with someone else's smartphone or a digital camera. 20:47:05 hmm is there any mandatory elements that need to be in the boot.conf for RPI? 20:47:35 that may not be there 20:47:53 I will try this one: . 20:47:54 problem with the image then .. 20:48:16 BarnabasDK, I have not seen mentioned of any mandatory elements in any of the installation instructions. 20:48:33 no, and it should be a part of the image 20:48:48 BarnabasDK: The installer from public img *should* load just fine with no need to changes made to boot.conf. Where would one even do them? 20:49:04 yes 20:49:28 speculating out loud 20:49:47 afaik - it should boot 20:52:17 Now I'd really love to have a Pi 4 at hand to quickly test this case on my side and be able to say "works for me" or "yeah, seems fucked up". 20:53:33 That's mighty kind of you, regis. I am now downloading the 14.1 . 20:54:11 I do, but none I can just flash like that 20:54:20 they are all in production 20:55:18 how do they work for you? any issues with NIC ? is network performant ? 20:55:23 can you boot it emulated on hw 20:55:47 mzar, no mine are not running freebsd 20:55:56 pios 20:55:58 I see 20:56:05 The new Raspberry Pi OS is one big regression, UI-wise. (just a rant), 20:57:18 What do you suggest -- that I test both & sync, and a different FreeBSD version at once? 20:58:23 Anyway, I hardly believe the 14.2.img can be broken on the offical site, and no one noticed. 20:58:37 .. there is a UI to the PIOS freebsd thing? 20:58:42 Or are the so few RPi users? 20:59:04 expect a console I should think .. 20:59:05 BarnabasDK, I am talking about the Raspbian OS for Rpi. 20:59:19 As to FreeBSD, I can install Xorg and a window manager. 20:59:20 ah 20:59:23 That's a use-case thing. For me RPi was never a GUI thing but rather a low-power host to connects sensors to. And I mentioned that I switched some of these needs to ESP32 (even though I hate this weird Arduino C/C++ abomination). 20:59:53 regis, yes. But it used to have tolerable GUI by default, before this huge upgrade to wayland & co. 20:59:57 ant-x, obviously, but out of the box it will be a normal root> 21:00:07 BarnabasDK, that's expected. 21:00:10 yes 21:00:50 By the way, I have never managed to setup xfce of FreeBSD, only a bare window manager. But I am looking too much forward... 21:01:38 do you expect to run xfce on this rpi ? 21:02:23 Why not? It worked very well on the Raspbian. 21:03:00 With LXDE, IIRC. 21:03:04 * mzar fades out 21:03:06 ant-x, as long as X works, the rest will too 21:03:15 wayland .. maybe 21:03:22 NO wayland, please. 21:03:33 It will, after I manager to configure it. 21:04:05 well, if you look at linux, wayland does blow X out of the water 21:04:21 it is just faster 21:04:26 I remember, I installed the xfce package, but didn't know where to configure it so it really started. 21:04:43 but . I do not know the state of the implementation of FreeBSD 21:04:51 It may be faster, because of the tighter architecture. 21:05:01 and no network nonsense 21:05:05 Yes. 21:05:14 Rather, client-server nonsense. 21:05:16 ant-x: I appreciate and support your needs. I'm only mentioning that my use-case is different. And that's why I still have a 2011 Raspberry 1 A with no ethernet port still in use. It's a low power device, works perfectly to gather data from 433 MHz ESP32 devices and deliver it over 433 MHz to upstream with more interfacing options. Again - it's an use-case thing. 21:06:22 A friend of mine told me he didn't understand the use for RPi, because there are equally small devices that are more powerful and less expensive. 21:06:33 i know of very few that run X across a wire today - from a server to a dumb client 21:06:58 the client almost always is a full on host 21:07:28 It is an interesting feature, but very rarely used indeed. 21:07:30 aka death of dumb X11 xconsoles 21:08:02 I really want a vt 520 amber text console if I could find one 21:08:14 ps2 compatible 21:08:26 I hear there are still compatibliyty problems of old GUI programs with wayland. Does GTK2 stuff work well on it? 21:08:28 but the gui stuff, is just dead 21:10:00 Will, twm (the standard X11 window manager) work in Wayland? 21:10:33 wayland is supposed to implement the entire x11 protocol sans the network things 21:10:39 BarnabasDK, you have space for a CRT? 21:11:02 Not there yet, probably. But I am glad it does. 21:11:05 I want one in my kitchen - for recipies 21:11:30 there are some panel ones too, you could use for home automation etc 21:11:35 with touch .. 21:11:44 all in amber yellow 21:11:59 I'd like a CRT for old games: . 21:12:23 Ah, you mean modern devices, not the old style monochrome CRT terminals? 21:13:23 * ant-x is dd'ing 14.1.... 21:14:15 VT 520 is cool: a monochrome text temrinal from the age of color CRT displays. 21:14:25 if you do not want a crt, the final make is just the controller and a connected vga https://www.ebay.com/itm/141627229957 21:15:04 Here are some photos from a CRT display I gave away several years ago. Now I am missing it: . 21:15:10 works with your out of the box flat screen 21:15:54 but whats the difference from a ssh console then? 21:16:12 none 21:16:52 You do not typically run SSH with a physical historical display. 21:17:15 The same difference as between owning a retro PC or emulating it. 21:18:08 what I am saying is, if you want an actual console, it should be analouge to the port of the server 21:18:09 <- atypical 21:18:22 and to your display too 21:18:51 By the way, the official install instruction for RPi does not mention `sync': . 21:19:48 and I just have played too much fallout 21:21:06 The 14.1.img is dd'ed and sync'ed, and the RPi poweroff'ed. Let us see what we shall see. 21:21:28 https://www.reddit.com/r/retrobattlestations/comments/2fzceg/digital_vt420_serial_terminal_that_lives_in_my/ 21:21:40 a vt420 in the kitchen, not mine 21:22:46 pro - none of your millenial plus kids would know anything about what to do with it .. 21:23:03 which also reveals my age I think 21:24:41 I think there was a "white" and a "green" and an "amber" version 21:24:51 The 14.1.img has had some of the same errors, but it booted, at least. It has failed to set the correct resolution for my display. The textmode console at the wrong resolution is killing my eyes, but it is there! 21:25:24 if you are considering "resolution" you are not in console mode 21:25:32 During the process, it said it had resized some partition. 21:25:39 ah 21:25:42 sorry my bad 21:26:02 I don't remember anything, including the root credentials. 21:27:05 I haved logged in as freebsd:freebsd. 21:28:08 There have been no actual installation or installer. 21:29:25 ant-x, all of these antics should not be necessary. Once you flash the image to the drive, provided you have a sane bios, that should be it. 21:29:47 so, something is wrong with the flashing process 21:30:19 BarnabasDK, antics like what? Since 14.1.img boots (as well as a Linux), 14.2.img does not boot, I think the 14.2 is broken. 21:30:25 yes .. 21:30:36 but it should boot completely to a root: login 21:30:51 It did. 21:31:02 I am there, at # 21:31:19 ok, so what is the problem now 21:31:58 you are probably at the single user prompt 21:32:03 Shall I run the TUI installer? 21:32:28 the "TUI" installer? 21:32:30 I think I am at the normal prompt, not single-user. 21:32:49 Yes, the FreeBSD installer with a pseudo-graphical interface. 21:33:09 This one: . 21:33:11 you already installed freebsd 21:33:20 how would you else boot it? 21:34:27 I think that program can be run again to change the configuration. Otherwise, I'll have to configure everything with by hand. 21:34:28 if you are at the # single user promt just "exit" and the boot process will continue to full user 21:34:42 load all services 21:34:53 and give you a real user login promt 21:35:37 It is fully booted to normal user, and it didn't even show a boot menu. 21:35:56 At the prompt, I logged in as `freebsd' with password `freebsd'. 21:36:59 so the entire system must be up 21:37:09 whats the problem? 21:38:23 First of all, thanks for helping me install FreeBSD, by tryging another image. The major problem is the 14.2 image seems broken, but I guess I can upgrade to 14.2 by hand. 21:38:29 do you know the difference between a boot menu login thing and an actual login prompt to our os 21:38:36 sorry if I am direct 21:38:39 I am Danish 21:38:51 we are like that 21:39:15 I have seen the boot menu a while ago, and do not remember the difference. No. 21:39:56 ok. so in order to move on, we need to figure out where you are in the boot chain 21:40:09 reboot from cold 21:40:26 what is the last thing your computer writes to your console 21:40:28 From cold -- by turning the power off? 21:40:33 yes 21:40:47 The last thing before the promt when it boots? 21:41:07 the last thing it outputs after it restarts 21:41:38 maybe you could cutn paste the entire thing 21:42:31 Cut and paste is out of the question -- between two machines, and one not connected to the internet yet. 21:43:23 dmesg is still there 21:44:54 basically, how do we know the boot was "bad" 21:45:06 where did you end up 21:45:07 The last thing before the login prompt is: FreeBSD/arm64 (generic) (ttyv0) 21:45:23 but you got a login promt? 21:45:25 BarnabasDK, I don't think it was "bad" this time! 21:45:36 ant-x, me too.. 21:45:52