GhostBSD to be made current

mutterhunt

here is a link to a for me not very helpful topic:

https://forums.ghostbsd.org/viewtopic.php?f=98&t=1549

My aim is to make out of GhostBSD (currently based on freeBSD 12.2 with open RC init) a -CURRENT system.

make buildworld and make installworld ok, make kernel -j5 (sorry, machine's not faster) builds correctly and I get the freeBSD logo as a splash screen, not the GhostBSD one anymore.

Having had driver problems to kernel panic with the drm-current-kmod, will try to install/build drm-devel. But this is another thing to be resolved.

When using the new world (without the CURRENT kernel) with llvm11 programs don't start anymore like firefox, thunderbird, etc.

pkg (it's pkg-devel) wants to downgrade immidiatly, so is there an option to not downgrade back to GhostBSD 12.2?

I loose contact to X extremely often and depending on custom built (no-debug) drm-current-kmod leads to kernel panic.

Can someone tell me what is the right processing of doing this meaningful thing? is it still possible? how to prevent pkg to uninstall all of the programs, pkg tells me to be installed programs that are definitely not installed, and a pkg bootstrap -f finds no pkg anymore.

the two repos GhostBSD and freeBSD are to be able to work simultaneously.

lizbeth

Jay

mutterhunt GhostBSD uses its own build scripts. I haven't tried that

rvp

mutterhunt My aim is to make out of GhostBSD (currently based on freeBSD 12.2 with open RC init) a -CURRENT system.

If you use -CURRENT, then don't install binary packages. That's just asking for trouble. A lot of things will fail mysteriously because the kernel and userland are out of sync.
Concrete example: I currently run 12.2-RELEASE and the drm-kmod binary package (built on 12.1) from the quarterly repository does not work---as soon as the kernel module is loaded, it reboots the system. So, I now run X on top of scfb, the software framebuffer.
If you're running -CURRENT, then build all software from the ports source collection. Don't use binary packages.
Why do you want to build a new distro based on GhostBSD anyway? It's just FreeBSD-12.2 with a very easy to use installer and the MATE desktop. If you just want the MATE desktop on FreeBSD-CURRENT, you can easily build it from ports.

mutterhunt

yup and a lotta proggies like variety a better octopkg (software-station), so when freeBSD is actually your tribe you'da add the repo GhsotBSD in /etc/pkg/GhostBSD.conf

GhostBSD: {
  url: "http://pkg.us.ghostbsd.org/unstable/FreeBSD:12:amd64
  enabled: yes
  }

to add even the folding@home port at /biology/linux-foldingathome. I remember we used to call it SETI in the late 90s'.

I guess it's the best thing to leave out the 'mergemaster -Ui' command and reinstall mate; there's Plasma5 now on BSD!

So, hope to make some enthuaiasts for leading back the systems to their origins, the answer to the Captcha Question in their mailing lists.

Lizbeth

mutterhunt

@kamil well, in fact these are two people; I just read what's vanbreukelingen wrote and thought: "this would be my chance to bring things forward!"

rvp this is quite clear to build all needed packages from source as they are higher versions then in the repo. A good example is perl with 5.32 in the repo but when doing the buildworld command you'll get 5.34.

The drm-fbsd12.0-kmod driver works for me at 12.2. but I'm not sure the build of drm-kmod-current or the build of drm-devel will fail; there's the use of making it in console mode without any graphics so I won't see probably why it fails to use . To install the drm-current-kmod from repo doesn't work!

The scfb-"driver" is a good kinda thing and if not detected as intel or radeon card ('X -configure') it's the only way-out to get X running if things go wrong. Don't forget: it's a complete new environment and I'da be proud if it would works at least partely (getting back the graphic)

Machine's still compiling the userland (old Celeron processor but fully compatible to the amd64 version of GhostBSD), then I have to make right on the custom 13.CURRENT kern (with no-debug and a verbose sysinit), reboot into single mode, install the world and then I'm probably outta X.

I have to build the

ports-mgmt/pkg-devel

again as 'pkg bootstrap -f' doesn't find binary at /usr/sbin. hmmm.... the openRC is gone and the logo comes from now on as freeBSD not as ghostBSD. this is why I avoid the 'mergemaster -URi' command and merge the two's togehter; they are independent distributions but neighbours and mother and daughter.

The aim of the whole thing is to lead back and forward the ghostBSD project into the 13.0.-CURRENT environment!

Another possibility would have been to install freeBSD, make it CURRENT and add the GhostBSD repo as mentioned as I want the whole plasma5-plasma stuff!

Let's see if I'm able to write from firefox again in a couple of hours (probably rebuild it from source).

lizbeth

kamil

Just a generic question. Are there two people using the mutterhunt account: Lizbeth and Miranda?

neb

Quote from Telegrams GhostBSD support group linking here:
"They do not realize that GhostBSD was once on 13-CURRENT. 😉"

rvp

neb "They do not realize that GhostBSD was once on 13-CURRENT. 😉"

I had a vague idea that one of the BSD desktops distros was, at one time, based on -CURRENT, but, I didn't realize that it was GhostBSD. But, my point was that if you run -CURRENT, then compile from source.

mutterhunt getting again this: "Cannot determine local path"

You should not get this (In fact, I couldn't find that specific error in either the 13.0 or 12.2 source tree; where is it coming from?). That indicates a broken (parallel) build or a filesystem error. Boot into single-user mode and run fsck for the latter.

mutterhunt suggestions?

Yes:
a) Start over
b) Don't mix and match binary packages from -CURRENT and GhostBSD.
c) Since you have some old hardware: Sig11 FAQ

mutterhunt

so far, so good, so what!? now built with kern completed but pkg is totally dead! I've tried to build both pkg and pkg-devel from /ports/ports-mgmt but I get when installing pkg:

/usr/local/etc/bash-completion/_pkg.bash is the conflicting file, error 70

when rm the file, same effect on pkg installation.

I downloaded the pkg-devel.txz and untared it from root, getting again this: "Cannot determine local path", so I can't uninstall drm-freebsd.12-kmod and install the drm-devel (already built).

suggestions?

mutterhunt

@neb you really think so? a 12.2.kern is not a 13-CURRENT and the kern now after 'make installworld' slaps good outta it without any debug and the #option hyperv.

neb

mutterhunt Now it runs -STABLE — it used to run -CURRENT.

mutterhunt

rvp ah... quite the kernel is newer, GhostBSD has a middle layer, TrueOS where the open RC comes from. Why I primarly started the whole stuff, was that freeBSD didn't get X to run on this old laptop. So I tried GhostBSD, saw how X initializes (what's CUSE, a driver module or a pkg, btw?) and thought, ok I'd bring the whole thing to the current point from there on. I know that there's lot to be compiled from ports (btw, 'pkg install ports' isn't anymore and even tried to hashtag the GhostBSD-repo, but no success.)

doing an fsck -y now, and then return to netBSD here to get a freeBSD version to try it the other way 'round.

soft/hard-problems possible, never forget: it's an amd64 environment on an intel celeron (i486).

lizbeth

rvp

mutterhunt Why I primarly started the whole stuff, was that freeBSD didn't get X to run on this old laptop

This, I can possibly help you with:

a) Post the output of dmesg or /var/run/dmesg.boot
b) Post a copy of Xorg.0.log
c) The output of: sudo pciconf -lv

mutterhunt it's an amd64 environment on an intel celeron (i486).

Didn't understand this. Can you elaborate?

PS. does the scfb driver work at the native resolution when you set the max. resolution using vesa / efi in the bootloader?

bsduck

mutterhunt what's CUSE, a driver module or a pkg, btw?

In case you have not figured it out yourself yet: it's a kernel module.
$ man cuse for more information

mutterhunt

{S O L V E D }

rvp Well, now I got a fresh CURRENT install from freebsd.org/download for amd64; I bootstrapped pkg, installed all the plasma5-plasma and kf5-guiaddons and kf5-coreaddons and sddm things and look!!! it is working without any problems.

I had to install the drm-current-kmod binary and the xf86-video-intel and swupdiwup! X -configure brings a remarkable driver load. Installed plasma, need someone to configure and personize it as it is later than MidnightBSD ever was (3 in the morning).

I mean it is cpu emulation for a 64bit machine, once built during the last producing MBR and 32bit hearts. I got it, because it is a Dell and I always used to have Dells or a lotta time if not screwing my own parts together and it is red on the outside, has a 128GB SSD, so for 160$ I made my 100x again-beginning on PCs.

Off topic: Some thoughts to BSD: The reason I left Linux after 20 years of positive collaboration and developing I found out that it the same problem with leadership as on the commercials, some of them (us) tend to pray to Torvalds and here we have a lotta personalities but no main central key figure.

And it was a new thing for me, I get here support and my work is not longer been criticized as too dangerous.

I wrote a bit a confusing thing earlier with the GhostBSD repo: when trying to add in CURRENT, it tells me about architecture incompatibility, as the GhostBSD is really on 12.2., not on 13.

to your PS-question: I think it depends if there is an MBR or a GPT boot: GTP does not VESA anymore, the efi-framebuffer decides if this is possible but I am not a specialist with this. Try to activate the radeon or i915 port, you get a better quality of graphics in 3D and sfcb (or modesetting) was once out with 1024x768.

I am a bit confused now, a brand-new world from Nov., 13th and the suitable kernel; nothing left to build. buhuhuhu.... :-( g

thanx for discussion,
lizbeth

rvp

mutterhunt I had to install the drm-current-kmod binary and the xf86-video-intel and swupdiwup! X -configure brings a remarkable driver load

You don't need both. If drm-kmod is active, then X will use the "modesetting" driver. If you install xf86-video-intel (and configure it), X will use the "intel" driver. You can check which one is being used by looking at /var/log/Xorg.0.log. If there are no config. files, then X will try to load display driver modules in this order on FreeBSD: modesetting, intel, scfb, vesa.

mutterhunt I mean it is cpu emulation for a 64bit machine, once built during the last producing MBR and 32bit hearts.

You mean a 32-bit Celeron emulating a MBR-based 64-bit system?

mutterhunt GTP does not VESA anymore

64-bit doesn't do VESA.

mutterhunt sfcb (or modesetting) was once out with 1024x768

On 64-bit with UEFI, you can add a line like:

efi_max_resolution=1366x768

and set the max. available resolution. 1366x768 is correct for my laptop; you can check what resolutions you have using the gop list command in the bootloader. On 32-bit systems, I think you can load the vesa module and check and then set a better resolution afterwards.

mutterhunt

The X -configure is always a bit a prayer if it works, you can manually copy the /root/xorg.conf.new to /etc/X11/xorg.conf for taking the X-Server the config file in /etc! There you can manage to overwrite "intel" with "scfb" or "modesetting" or "xorg", aso....

There's a command: X -retro, if this works or maybe SLIM it's the half way to login! At netBSD here I use gdm and start a xfce4-session with it, quite cute 'coz xfce4 is really slim and on slower machines recommended.

yup, this machine is built 32bit but due to CPU-flags fully compatible with 64-bit-systems on BSD, with linux you'da have luck to find the right image... And not even MBR anymore, coz ZFS overwrites the partitiontable with GPT. I use the whole 128GB for freeBSD now, my main system for working.

the stuff with the efi_max_resolution was new for me, thx.

good luck,
lizbeth

rvp

mutterhunt The X -configure is always a bit a prayer if it works, you can manually copy the /root/xorg.conf.new to /etc/X11/xorg.conf

You don't need the whole file, just the relevant fragments will do. For example, to use the scfb X display driver after setting the max. resolution in /boot/loader.conf, I use this xorg.conf fragment:

$ cat /usr/local/etc/X11/xorg.conf.d/scfb.conf
Section "Device"
    Identifier "Card0"
    Driver "scfb"
EndSection
$

You can just change scfb to intel or modesetting to use a different display driver.

mutterhunt There's a command: X -retro

I've never seen this flag so far...

mutterhunt this machine is built 32bit but due to CPU-flags fully compatible with 64-bit-systems on BSD

I didn't get this at all.

mutterhunt

@rvp with the cat-command, defenitely right, but faster with nano /etc/X11/xorg.conf and changing to and through!

architecture: the system was once 32-bit, I get arch-linux just as 32bit to run, but amd64-GhostBSD and FreeBSD images, ZFS destroys the MBR and makes (gpart show ada0) a GPT partition table outta it. curious, the CPU is a bit overclocked after all theese years of slavery in windoze but it makes it's best when compiling, etc. a world build takes a 28 hours and the kern 2 hours...

all the best,
lizbeth

rvp

mutterhunt architecture: the system was once 32-bit, I get arch-linux just as 32bit to run, but amd64-GhostBSD and FreeBSD images

A 64-bit emulation running on a 32-bit CPU? A bit out of the ordinary, this.
Post /var/run/dmesg.boot from FreeBSD (emulation) and a dmesg output from Arch Linux (host?).

mutterhunt

here we go: https://pastebin.com/QJ9gkGVN

this is the CPU-part:
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT #5 r367741: Tue Nov 17 12:41:51 CET 2020 "GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0xdbae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,OSXSAVE> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> XSAVE Features=0x1<XSAVEOPT> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics

from the arch I haven't but I swear it's not able to boot from i386 nor from amd64-image. had to use the archlinux32.org download site.

lizbeth

rvp

mutterhunt
cpu_startup(0)... CPU: Intel(R) Celeron(R) CPU 867 @ 1.30GHz (1297.08-MHz K8-class CPU) Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7

If this is from the host system, then what you have is a native 64-bit CPU: Celeron 867

mutterhunt

rvp but why did arch-linux tells me after grub when loading the kernel: "wrong architecture"? btw, archlinux32.org is going offline as of 1st Dec. 2020, as nobody uses the 32bit kernel anymore. With Ubuntu Cinnamon I had a 64bit linux experience, but this is water under the bridge as I don't use linux anymore. Just BSD! What to do with an Oculus Rift upcoming for me? Virtualised under Debian with freeBSD? Or a physical install of Arch and use the AUR build system?!