Solved upgraded to 12.1 release now it is a blow of boot loops

got up to .. run freebsd-update install
did that then said kernel stuff installed, reboot then run that command again, so I did and now it boot loops.

booting efi via linux
Code:
menuentry "FreeBSD cload1 v12-p10" {

set root='(hd1,7)'
#chainloader /boot/boot1.efi
chainloader /boot/loader.efi
#kfreebsd /boot/loader
}
 
In FreeBSD, do you have drm-kmod installed and are using the i915kms.ko module?
 
Yeah, you'll want to disable any additional (ports/package) installed kernel modules until you've completed the upgrade. Kernel modules are built for a specific version, at the moment your system is likely to try and load a 11.x kernel module on a 12.x kernel. Disable those temporarily, you can enable them again after you completed the upgrade and reinstalled all your packages/ports.
 
Shouldn't this somehow be caught by the module itself? I.e. incompatible kernel found, module should not load itself, so it won't be screwing things up. I would expect that as a default behavior in an OS.

Answered this myself. It's in errata: https://www.freebsd.org/releases/12.1R/errata.html#open-issues

It's mind-boggling that an issue this generic has not been caught in a release. Hard to believe none of the developers run an Intel-based graphics adapter.
 
In FreeBSD, do you have drm-kmod installed and are using the i915kms.ko module?
yeah I saw that other post on this i915kms.ko after I posted mine..... figured I wait until today to see what if anything I can do about it, it was late afternoon when i posted here.
I'm burning 12.1 img to a stick right now just incase it gets to that point of just re-installing I'll go 12.1 just to see what I see. I already backed up my personal data before upgrading. figuring something "bad" might happen. it's just my laptop not any major server so yeah.. it'll be alright,
 
Can you still boot to single user mode? If you used kld_list instead of /boot/loader.conf then this should still work. In single user mode you can finish the install part of the upgrade. Don't forget to fsck(8) (if needed) and mounting your filesystems read/write when you're in single user mode.
 
Can you still boot to single user mode? If you used kld_list instead of /boot/loader.conf then this should still work. In single user mode you can finish the install part of the upgrade. Don't forget to fsck(8) (if needed) and mounting your filesystems read/write when you're in single user mode.
yeah I hit 2 boot defaults, it craped out telling me it needed acpi or something. rebooted picked 5 and I'm in .. sooo... wondering if that is going to hold. or if I need to make preps for it to not hold, like removing load my video driver...

it is still showing - Kernel 12.0-RELEASE-p10, and I am running freebsd-upgrade install again.. waiting for it to do its thing....
ok came up with this
Code:
root@FreeBSD64.net:/home/userx
# freebsd-update install
Installing updates...
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run "/usr/sbin/freebsd-update install"
again to finish installing updates.

most of my stuff is off pkg installs. like 99.9 % of it. so I'm running pkg update?
Code:
userx@FreeBSD64.net:~
$ sudo pkg update
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%    6 MiB   1.3MB/s    00:05
Processing entries: 100%
FreeBSD repository update completed. 32620 packages processed.
All repositories are up to date.

Uptime  7:34AM  up 12 mins, 0 users, load averages: 0.78, 0.83, 0.53

HP EliteBook 840 G2
CPU: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (2294.74-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
------------------------------------------------------------------

# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (7 candidates): 100%
Processing candidates (7 candidates): 100%
The following 8 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    wpebackend-fdo: 1.4.0
    libwpe: 1.4.0

Installed packages to be UPGRADED:
    webkit2-gtk3: 2.24.4 -> 2.26.1
    mesa-libs: 18.3.2_2 -> 18.3.2_3
    mesa-dri: 18.3.2_7 -> 18.3.2_8
    harfbuzz-icu: 2.6.3 -> 2.6.4
    harfbuzz: 2.6.3 -> 2.6.4
    firefox: 70.0_1,1 -> 70.0.1,1

Number of packages to be installed: 2
Number of packages to be upgraded: 6

The operation will free 26 MiB.
71 MiB to be downloaded.
--------------------------------

root@FreeBSD64.net:/home/userx
# freebsd-update install
Installing updates...
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run "/usr/sbin/freebsd-update install"
again to finish installing updates.
root@FreeBSD64.net:/home/userx
# /usr/sbin/freebsd-update install
Installing updates... done.
still showing 12
Code:
$ uname -a
FreeBSD FreeBSD64.net 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC  amd64
 
rebooted without loading the driver in rc.conf.. wouldn't let me startx .. edited the file unommented that line and it's back to boot loops. sO I am in Linux redoing my stick using a gpt partition table on it this time. then burning img to it. UEFI. booting. no csm..
 
I'm on my phone with this message on my laptop terminal amd64/quarterly/packagesight.txs forbidden

When trying to update pkg. in boot/modules all there is is a bucket load of bin.ko video drivers. So I’m trying to figure out what to do next.

ok back in Linux.... it has the /boot/modules/i915kms.ko .. but it will not let me delete it, ports told me to make deinstall did that it did not de install anything. it is not letting me fix my system.. waaaa.
thinking of reinstalling, but which version? /boot/modules/i915kms.ko is crap in v 12.1??? needs fixing first????
as it is now showing 12.1 Kernel but not giving me xorg due to video ...
 

pkg delete drm-kmod
pkg autoremove

Once your upgrade has completed install graphics/drm-kmod from ports. At the moment you cannot use the pre-packaged version. That one is specifically built for 12.0 and will crash on 12.1. The "problem" with the package repositories is that they're built for the lowest supported version which is still 12.0. When 12.0 will be EoL (three months from now) the packages will get built for 12.1. For 99% of the packages this is not a problem. Only kernel modules (and some packages that use specific kernel structures directly) from are affected by this.

If you can continue using prebuilt packages but you will need to change the package repository. Do note that the release_1 repository is based on latest, not quarterly.

Create a /usr/local/etc/pkg/repos/FreeBSD.conf:
Code:
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_1"
}
 

pkg delete drm-kmod
pkg autoremove

Once your upgrade has completed install graphics/drm-kmod from ports. At the moment you cannot use the pre-packaged version. That one is specifically built for 12.0 and will crash on 12.1. The "problem" with the package repositories is that they're built for the lowest supported version which is still 12.0. When 12.0 will be EoL (three months from now) the packages will get built for 12.1. For 99% of the packages this is not a problem. Only kernel modules (and some packages that use specific kernel structures directly) from are affected by this.

If you can continue using prebuilt packages but you will need to change the package repository. Do note that the release_1 repository is based on latest, not quarterly.

Create a /usr/local/etc/pkg/repos/FreeBSD.conf:
Code:
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/release_1"
}
I'm all good now. it was internet connection blocking me. starbucks ciso router kitty porn and whatever they think is a no no block. switched to someone elses rebuild i915 and its running good so far.
 
Back
Top