No mouse, No keyboard on update from FreeBSD 13.1 to 13.2, Libreoffice stopped working even after deletion and then install..

Dear friends at Freebsd Forum,

I am unable to login after the following upgrade:


Code:
freebsd-update -r 13.2-RELEASE upgrade
freebsd-update install
shutdown -r now
freebsd-update install
pkg update
pkg upgrade
shutdown -r now

I will share my bectl list as follows:


root@kaladhari-L1:/home/admin # bectl list


Code:
BE                                Active Mountpoint Space Created

13.1-RC1_2022-05-28_205232        -      -          91M   2022-05-28 20:52
13.1-RELEASE-p2_2022-12-20_230150 -      -          3.80G 2022-12-20 23:01
13.1-RELEASE-p5_2023-03-22_123152 -      -          4.34G 2023-03-22 12:31
13.1-RELEASE-p7_2023-10-04_143608 -      -          5.47G 2023-10-04 14:36
13.1-RELEASE-p7_2023-10-06_104643 -      -          10.0M 2023-10-06 10:46
13.1-RELEASE-p9_2023-10-06_122126 -      -          147M  2023-10-06 12:21
13.1-RELEASE-p9_2023-10-06_123322 -      -          135M  2023-10-06 12:33
13.1-RELEASE-p9_2023-10-06_124440 -      -          7.79G 2023-10-06 12:44
13.1-RELEASE-p9_2023-10-06_125120 -      -          137M  2023-10-06 12:51
13.1-RELEASE-p9_2023-10-06_224609 N      /          970M  2023-10-06 22:46
13.1-RELEASE_2022-05-28_210247    -      -          7.83M 2022-05-28 21:02
13.1-RELEASE_2022-09-15_124259    -      -          3.49G 2022-09-15 12:42
13.2-RELEASE-p4_2023-10-06_172759 -      -          17.2M 2023-10-06 17:28
default                           R      -          39.5G 2021-12-01 18:39


I had to resort to previous boot environment using boot sequence option no. 8.

I am using xfce.

I look forward for your advice and guidance, where and what is missing.
I believe bectl list should have max 3 instances of boot environment on my system, if not 2.

Also , Libre office stopped working during my upgrade to Freebsd 13.1-RELEASE-p9 from p7.

At present I choose boot environment 13.1-RELEASE-p9 ( as above ), still LibreOffice doesnot open up.

Need help ASAP.....
 
So the "no mouse, no keyboard" only affects XFCE and not the console framebuffer? Otherwise how would you have run these commands?
 
After starting XFCE, do you have error messages (marked with EE) in file /var/log/Xorg.0.log?
Concerning LibreOffice, do you get error messages when you start LibreOffice from the command line with /usr/local/bin/libreoffice?
 
So the "no mouse, no keyboard" only affects XFCE and not the console framebuffer? Otherwise how would you have run these commands?
I beg your pardon, the problem arise when i boot to FreeBSD 13.2, NO PROBLEM OF MOUSE AND KEYBOARD WHEN I BOOT TO 13.1

I did run these command in 13.1 to trouble shoot. but target to run 13.2 , not reached yet.
 
After starting XFCE, do you have error messages (marked with EE) in file /var/log/Xorg.0.log?
Concerning LibreOffice, do you get error messages when you start LibreOffice from the command line with /usr/local/bin/libreoffice?
After starting XFCE, do you have error messages (marked with EE) in file /var/log/Xorg.0.log?
Concerning LibreOffice, do you get error messages when you start LibreOffice from the command line with /usr/local/bin/libreoffice?
yes on running /usr/bin/libreoffice

the reply error 1:
Code:
Cannot mix incompatible Qt library (5.15.8) with this library (5.15.10)

HENCE I AM INSTALLING QT5 library

sudo pkg install qt5

But error 1 remains there....
 
Where can't you login? Do you mean the terminal or something in X?

What happens when you try to login? To the terminal? To X?

What do you see (if anything?)
just after the boot, i can see xfcestart gui , with promting for USER, there i can NOT type and no crtl+alt+f2 or f9 work ,I as believe, keyboard doesnot show up..
 
Boot into single user mode and check if your keyboard is working.
If your keyboard is working there then edit /etc/rc.conf and commend out the desktop manager then type exit to boot into multi-user and force reinstall/upgrade all installed packages.
 
In the 13.2 Boot Environment: if you use a display manager as your graphical login manager and this doesn't show up at boot, comment that out in /etc/rc.conf too (in single user mode).
 
I believe bectl list should have max 3 instances of boot environment on my system, if not 2.
Nope, everytime you run freebsd-update install it will create a new boot environment by default if it actually has anything to do. If there is nothing to do, no new BE gets created. The BE just created represents the system before doing anything.
 
The system currently is in the following scenario:

Code:
# bectl list
BE                                Active Mountpoint Space Created
13.1-RC1_2022-05-28_205232        -      -          91M   2022-05-28 20:52
13.1-RELEASE-p2_2022-12-20_230150 -      -          3.80G 2022-12-20 23:01
13.1-RELEASE-p5_2023-03-22_123152 -      -          4.34G 2023-03-22 12:31
13.1-RELEASE-p7_2023-10-04_143608 -      -          5.47G 2023-10-04 14:36
13.1-RELEASE-p7_2023-10-06_104643 -      -          10.0M 2023-10-06 10:46
13.1-RELEASE-p9_2023-10-06_122126 -      -          147M  2023-10-06 12:21
13.1-RELEASE-p9_2023-10-06_123322 -      -          135M  2023-10-06 12:33
13.1-RELEASE-p9_2023-10-06_124440 -      -          7.79G 2023-10-06 12:44
13.1-RELEASE-p9_2023-10-06_125120 -      -          1.01G 2023-10-06 12:51
13.1-RELEASE-p9_2023-10-06_224609 -      -          6.07G 2023-10-06 22:46
13.1-RELEASE_2022-05-28_210247    -      -          7.83M 2022-05-28 21:02
13.1-RELEASE_2022-09-15_124259    -      -          3.49G 2022-09-15 12:42
13.2-RELEASE-p4_2023-10-06_172759 -      -          17.2M 2023-10-06 17:28
13.2-RELEASE-p4_2023-10-11_140830 -      -          4.98G 2023-10-11 14:08
13.2-RELEASE-p4_2023-10-11_144802 -      -          41.5M 2023-10-11 14:48
13.2-RELEASE-p4_2023-10-11_155222 -      -          4.99G 2023-10-11 15:52
13.2-RELEASE-p4_2023-10-11_160957 N      /          989M  2023-10-11 16:09
default                           R      -          39.5G 2021-12-01 18:39


# bectl list -aD
13.2-RELEASE-p4_2023-10-11_160957
  zroot/ROOT/13.2-RELEASE-p4_2023-10-11_160957                         N      /          1.99G 2023-10-11 16:09
    zroot/ROOT/13.2-RELEASE-p4_2023-10-11_155222@2023-10-11-16:09:57-0 -      -          1.24M 2023-10-11 16:09

default
  zroot/ROOT/default                                                   R      -          39.5G 2021-12-01 18:39

and

Code:
# freebsd-version -kru
13.2-RELEASE-p4
13.2-RELEASE-p4
13.1-RELEASE-p9

# uname -a
FreeBSD kaladhari-L1 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC amd64

BUT WHEN I REBOOT, THIS TITLE ISSUE REMAIN. as one can see , zroot/ROOT/default DATE back to 2021.

THEN I HAVE TO CHOOSE ONE OF THE BOOT ENVIRONMENTS(BE) USING OPTION NO 8, SELECT THIS VERY BE.

HOW TO COME OUT OF THIS LOOP OF CHOOSING BE?
 
Writing in all caps is akin to SHOUTING, and is considered very rude. Stop doing that.

Code:
# freebsd-version -kru
13.2-RELEASE-p4
13.2-RELEASE-p4
13.1-RELEASE-p9

It looks like you ran freebsd-update install only once. So only your kernel has been updated. You need to run freebsd-update install twice.
 
Writing in all caps is akin to SHOUTING, and is considered very rude. Stop doing that.



It looks like you ran freebsd-update install only once. So only your kernel has been updated. You need to run freebsd-update install twice.
and probably a reboot somewhere in there too
 
and probably a reboot somewhere in there too
No, not required. It's considered the safest way but it's been a long time since it was required to boot the new kernel first before installing world. I rarely do actually. Just run freebsd-update install twice in a row (if it's a major version upgrade, three times), throw in a pkg upgrade, then reboot.

Just make sure you're booted on the 'default' BE (it should show as 'NR' in bectl list). Because that's where your 'partially' installed upgrade is. We'll clean up those old BEs when everything's done.
 
My appologies, but my heart is shouting....

I have deleted all 13.1 and 13.2 BEs, except I am running now.


# bectl list -aD
BE/Dataset/Snapshot Active Mountpoint Space Created

13.2-RELEASE-p4_2023-10-11_160957
zroot/ROOT/13.2-RELEASE-p4_2023-10-11_160957 N / 8.00G 2023-10-11 16:09
zroot/ROOT/default@2023-10-04-14:36:08-0 - - 3.82G 2023-10-04 14:36

default
zroot/ROOT/default R - 19.3G 2021-12-01 18:39



Again if I allow my system to reboot by default, then this error of no keyboard remains exist.

I am choosing this very be with 13.2-RELEASE, using option 8 during boot. Now as guided, here above:


# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 13.2-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.2-RELEASE-p4.

root@kaladhari-L1:/home/admin # freebsd-update install
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
root@kaladhari-L1:/home/admin #


What next?
 
I am choosing this very be with 13.2-RELEASE, using option 8 during boot.
Stop messing with this. You keep booting an OLD BE, one that's halfway with the upgrade. Boot the 'default' BE. So, don't touch anything on the boot menu.

Again if I allow my system to reboot by default, then this error of no keyboard remains exist.
You're starting X at boot? Using SDDM, SLiM, whatever? Boot to single user mode and turn that off in rc.conf. Fix your system first, then worry about X and everything else.
 
SOLVED!!!

Once in a single user mode, I need to switch off, slim and xdm in /etc/rc.conf . For that we need to

#mount -u /

ref: https://ben-rowan.github.io/post/so_youve_messed_up_your_rc.conf/

This way I am able to edit the rc.conf.

Next as suggested by SirDice ,

#freebsd-update upgrade -r 13.2-RELEASE
#freebsd-update install
{ no reboot } { this is what we need to keep in mind IMPORTANT}
#freebsd-update install {repeat this }


{ until one sees a message from the FreeBSD, No updates are available to install.}

{ then reboot }

this worked for me.

Now:

# bectl list
BE Active Mountpoint Space Created
13.1-RELEASE-p9_2023-10-13_061125 - - 29.5M 2023-10-13 06:11
13.2-RELEASE-p4_2023-10-11_160957 - - 13.6G 2023-10-11 16:09
13.2-RELEASE-p4_2023-10-13_061657 - - 24.8M 2023-10-13 06:16
default NR / 22.2G 2021-12-01 18:39


This is as suggested above.

Thanks SirDice and richardtoohey2
 

# freebsd-version -urk
13.2-RELEASE-p4
13.2-RELEASE-p4
13.2-RELEASE-p4


# bectl list
BE Active Mountpoint Space Created
13.1-RELEASE-p9_2023-10-13_061125 - - 29.5M 2023-10-13 06:11
13.2-RELEASE-p4_2023-10-11_160957 - - 13.6G 2023-10-11 16:09
13.2-RELEASE-p4_2023-10-13_061657 - - 45.0M 2023-10-13 06:16
default NR / 23.1G 2021-12-01 18:39



Thanks again SirDice
 
Back
Top