Is it possible at this time upgrading step by step from 12.2-RELEASE to 14.2-RELEASE?

Nope. Not the base system at least. Try with something like:

pkg query -e '%a = 0' %o > ~/installedpkgslist

from the console as root will make a list of your installed packages. Then remove all installed packages with

pkg delete -aFy

then reinstall everything with

pkg install `cat ~/installedpkglist`
 
larshenrikoern said:
Nope. Not the base system at least. Try with something like:

pkg query -e '%a = 0' %o > ~/installedpkgslist

from the console as root will make a list of your installed packages. Then remove all installed packages with

pkg delete -aFy

then reinstall everything with

pkg install `cat ~/installedpkglist`
Click to expand...
Thanks, I would try it
 
larshenrikoern said:
Nope. Not the base system at least. Try with something like:

pkg query -e '%a = 0' %o > ~/installedpkgslist

from the console as root will make a list of your installed packages. Then remove all installed packages with

pkg delete -aFy

then reinstall everything with

pkg install `cat ~/installedpkglist`
Click to expand...
The command "pkg query -e '%a = 0' %o > ~/installedpkgslist" gives an error, I have replaced with "pkg query -a '%a=0' %o > ~/installedpkgslist".
Then installedpkglist shows a large list like 1=1, 1=1, 0=1,... and so on.

Actually my idea is to get mouse working in pure mode text like old releases, 12.0 to 12.4 in example. No problem there when running the O.S., immediately appears mouse pointer after login in, pure mode text, no GUI.

But since 13.0 mouse does not appears in console's pure mode text. I have installed minimal 13.0-RELEASE without GUI and mouse does not appear in console after login. Always I have moused-enable=YES in rc.conf, but such a sentence is not the actual problem.

The image below shows mouse working in 12.1-12.2-RELEASE, but in 14.0-14-2 mouse just does not work in pure mode text. That's the reason I have tried to upgrade from 12.4 to 14.0. Inspecting dmesg after pkg-static upgrade -f appears some errors like I post below

12.1 working mouse.JPG
 

Attachments

  • dmesg.errors.JPG
    dmesg.errors.JPG
    34.5 KB · Views: 197
raul_comodoro said:
The command "pkg query -e '%a = 0' %o > ~/installedpkgslist" gives an error, I have replaced with "pkg query -a '%a=0' %o > ~/installedpkgslist".
Then installedpkglist shows a large list like 1=1, 1=1, 0=1,... and so on.

Actually my idea is to get mouse working in pure mode text like old releases, 12.0 to 12.4 in example. No problem there when running the O.S., immediately appears mouse pointer after login in, pure mode text, no GUI.

But since 13.0 mouse does not appears in console's pure mode text. I have installed minimal 13.0-RELEASE without GUI and mouse does not appear in console after login. Always I have moused-enable=YES in rc.conf, but such a sentence is not the actual problem.

The image below shows mouse working in 12.1-12.2-RELEASE, but in 14.0-14-2 mouse just does not work in pure mode text. That's the reason I have tried to upgrade from 12.4 to 14.0. Inspecting dmesg after pkg-static upgrade -f appears some errors like I post below
Click to expand...
That is why i suggest using -e instead of -a so the list contains only the packages installed by the user, and not all libs and dependencies and so on.

Are you running in a VM or on real hardware. If on real hardware the errors does not mean anything as they are about memory management in a VM.

Does startx work now ??
 
larshenrikoern said:
That is why i suggest using -e instead of -a so the list contains only the packages installed by the user, and not all libs and dependencies and so on.

Are you running in a VM or on real hardware. If on real hardware the errors does not mean anything as they are about memory management in a VM.

Does startx work now ??
Click to expand...
Running a "VMWared" machine. I do not know what images I have put were.
 
raul_comodoro said:
The command "pkg query -e '%a = 0' %o > ~/installedpkgslist" gives an error, I have replaced with "pkg query -a '%a=0' %o > ~/installedpkgslist".
Then installedpkglist shows a large list like 1=1, 1=1, 0=1,... and so on.

Actually my idea is to get mouse working in pure mode text like old releases, 12.0 to 12.4 in example. No problem there when running the O.S., immediately appears mouse pointer after login in, pure mode text, no GUI.

But since 13.0 mouse does not appears in console's pure mode text. I have installed minimal 13.0-RELEASE without GUI and mouse does not appear in console after login. Always I have moused-enable=YES in rc.conf, but such a sentence is not the actual problem.

The image below shows mouse working in 12.1-12.2-RELEASE, but in 14.0-14-2 mouse just does not work in pure mode text. That's the reason I have tried to upgrade from 12.4 to 14.0. Inspecting dmesg after pkg-static upgrade -f appears some errors like I post below

View attachment 22278
Click to expand...
Here the images, console is inside a virtual machine, 12.1-12.2 Release, mouse works perfectly, buy something is wrong when updating/upgrading from 12.2 or 12.4 to 14.0, look the image below, seldom kernel errors appear.
 
larshenrikoern said:
Does your loader.conf contain ums_load=“YES””
Found this link https://www.reddit.com/r/freebsd/comments/18xe5ax/help_needed_running_freebsd_14_on_vmware_fusion/ Might be your issue

Know VM-Ware quite well. But only for windoze
Click to expand...
Well, I have a 14.0-RELEASE working, it was upgrades step-by-step from 12.2-RELEASE, some problems in the middle but nothing very important.
When now I'm trying to upgrade from 14.0 to 14.2 appears that I have to merge the file auto_master or so, If I rembember, by using vi or visudo, excusme, but I hate "visudo", it is a stone's age program, it is horrible, the man page it seems to be written in "Chinese". I prefer "ee", but I don't know where and how set a environment variable, i.e: "% export EDITOR=/usr/local/bin/ee" using as default "ee" editor. Y have deleted all configuration instructions from the matching files related to auto_master, auto_fs or whatever whith but appears again like automatic usb´s mounting is enabled.
Well, I am just on step to the goal. I hope just a little work more.
 
sudo $SHELL
export EDITOR=ee # (if you use sh / bash / zsh?)
setenv EDITOR ee # (if you use tcsh / csh)
freebsd-update args
 
WEll, at this moment upgrading since 12.0 to 12.4 is not a problem, everything's OK. But working 13.0-RELEASE gets something very wrong with, it is not possible update and upgrade from 12.4 to 13.0-RELEASE, it gives a lot of errors and system ends broken.
As an optional work I have installed 14.2-RELEASE, OK, but errors appeared again, and something rare, sound is detected if speakers are connected to the front usb connectors, and there is no way to enable them connected to rear usb connectors, I can´t find any mixer to controll audio speakers working at the rear connector.
 
As days before, I have installed 14.2-RELEASE, it works fine, the question is "How to enable mouse working in pure mode text as of 12.1-12.2-RELEASE"?
Without using graphic environment. Fotget service moused start or something like that, it does not work, it is enabled by default in /etc/rc.conf.
In other word booting the system, login as normal user o root in pure text mode and mouse appearing immediately working without calling "startx"
 
raul_comodoro said:
Fotget service moused start or something like that, it does not work, it is enabled by default in /etc/rc.conf.
Click to expand...
Is your machines firmware BIOS (to check: sysctl machdep.bootmethod)? I've noticed (in a VirtualBox VM) moused has no effect when the machine is BIOS configured.

With EFI firmware setting, moused works nicely (copy, paste). Same on bare metal machine (laptop), UEFI.
 
T-Daemon said:
Is your machines firmware BIOS (to check: sysctl machdep.bootmethod)? I've noticed (in a VirtualBox VM) moused has no effect when the machine is BIOS configured.

With EFI firmware setting, moused works nicely (copy, paste). Same on bare metal machine (laptop), UEFI.
Click to expand...
Running that command gives: machdep.bootmethod=BIOS

Then I see there is no solution at all
 
raul_comodoro said:
Then I see there is no solution at all
Click to expand...
Not necessarily.

raul_comodoro said:
But in older releases mouse works perfectly, like 12.0-12.1-12.2...
Click to expand...
Well, there are considerable major and minor version gaps between those and the current 14.2. There happened a lot of changes in the source code since then.


I suggest you open a moused(8) PR, to make sure the developers are aware of this issue.


After some testing, there seems still some mouse activity, even when no mouse pointer is visible. Try enable debug messages on your system and move mouse on screen.
Code: 
# service moused onestop

# moused -d -f -p /dev/psm0

moused(8) has no issues with the sc(4) driver instead of the default vt(4) driver (check on current running system: sysctl kern.vty). To try, "Escape to loader prompt" at the boot menu, set kern.vty=sc (permanent set in /boot/loader.conf). See image [2].

But sc(4) has disadvantages compared to vt(4), no UTF-8 support for example, and, to quote the manual:
Code: 
DEPRECATION NOTICE
     The syscons console is deprecated, and will be removed in a future
     version of FreeBSD.  Users are advised to migrate to the vt(4) console
     instead.


As for why there is a problem with moused in BIOS on 14.2 in vt(4) console, I suspected that the following commit could be the cause:

loader: Change this BIOS tradeoff: Add back zip and use text only

and indeed, reverting the changes (in the source code and building from souce [1]) brings back moused visible mouse pointer in BIOS vt(4) console. Reverting the changes is less than ideal, the user must maintain any eventual changes of the loader by system upgrade on his own.



[1] Fetch source code, apply patch, build, install loader:
Diff: 
diff --git a/share/mk/src.opts.mk b/share/mk/src.opts.mk
index 22373f8c7af1..774b6fffd3df 100644
--- a/share/mk/src.opts.mk
+++ b/share/mk/src.opts.mk
@@ -129,7 +129,6 @@ __DEFAULT_YES_OPTIONS = \
     LLD_IS_LD \
     LLVM_COV \
     LLVM_CXXFILT \
-    LOADER_BIOS_TEXTONLY \
     LOADER_GELI \
     LOADER_KBOOT \
     LOADER_LUA \
@@ -207,6 +206,7 @@ __DEFAULT_NO_OPTIONS = \
     DTRACE_TESTS \
     EXPERIMENTAL \
     HESIOD \
+    LOADER_BIOS_TEXTONLY \
     LOADER_VERBOSE \
     LOADER_VERIEXEC_PASS_MANIFEST \
     LLVM_ASSERTIONS \
diff --git a/stand/i386/loader/Makefile b/stand/i386/loader/Makefile
index c2037772fc76..a4aa3a3c4d45 100644
--- a/stand/i386/loader/Makefile
+++ b/stand/i386/loader/Makefile
@@ -7,8 +7,8 @@ LOADER_CD9660_SUPPORT?=    yes
 LOADER_EXT2FS_SUPPORT?=    no
 LOADER_MSDOS_SUPPORT?=    no
 LOADER_UFS_SUPPORT?=    yes
-LOADER_GZIP_SUPPORT?=    yes
-LOADER_BZIP2_SUPPORT?=    yes
+LOADER_GZIP_SUPPORT?=    no
+LOADER_BZIP2_SUPPORT?=    no

 .include <bsd.init.mk>

Code: 
# cd /usr/src/stand

# make && make install

If the file system is ZFS, a boot environment (bectl(8) should be created before applying the changes, just in case.

After reverting the commit, installed loader in a VirtualBox VM. The mouse pointer is tiny, I suppose due screen resolution.

moused.png



[2]

moused-sc.png
 
This code:


Code:


# service moused onestop<
# moused -d -f -p /dev/psm0

Does not work at all, is a endless loop, pressing ctrl-Z stopped but the system is freesed.
 
raul_comodoro said:
# moused -d -f -p /dev/psm0

Does not work at all, is a endless loop, pressing ctrl-Z stopped but the system is freesed.
Click to expand...
The moused -d enables debugging messages. It is not supposed to terminate until terminated by the user.

moused(8)
Code: 
     -d      Enable debugging messages.

There must be special circumstances on your system triggering the freeze. In any case, I can't reproduce a system freeze (in a VM at least).

moused-01.png

After moving the mouse and terminating the process:

moused-02.png
 
You must log in or register to reply here.
Back
Top