old kernels disappearing?
While dealing with the fallout from my MS heartburn, I've noticed something new. I can no longer keep old kernels in /boot/kernel/, at least not with the name kernel.* Is this new behavior or have I made a mistake in my loader.conf? -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
Don Wilde wrote: On 7/16/20 11:53 PM, Polytropon wrote: On Thu, 16 Jul 2020 13:19:51 -0700, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. They do this all the time. The consensus here is to install "Windows" first, always, restricted to the designated disk space, and _then_ install Linux, FreeBSD, GRUB, or anything else non-"Windows", in order to avoid the exact problem you are describing. Even older versions of "Windows" were known to destroy things like the FreeBSD boot manager when they are installed as a 2nd choice. MICROS~1 always wants you to treat it first class, with golden feet and glockenspiel. However, is my interpretation correct? Did this happen when you _installed_ "Windows" on that machine for the first time, or did it happen after you _booted_ an already installed instance of "Windows", which then did attack "foreign data" on the disk? This machine still maintains the original Windows installation, first with W7, and then (finally, bad mistake) upgraded to W10. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. Something like that should never happen. It's absolutely normal that "Windows" installs software without user consent, and then presents it prominently in user-configured areas such as the desktop, the "Start" menu, or the bottom bar (pun absolutely intended), but it should never exceed its authority beyong the border of the "Windows" partition, which clearly means: "Hands off of Grub partition!" Yes. The bastards also screwed up my 128GB backup drive -- again without asking -- when I left it plugged in during a Doze boot. Y'all must have the special edition of Win10 handed as a punishment to those who likes to hijack questions@ (and now stable@) with "the grass was greener" threads :-) I have never seen it do anything with removable media I have attached, be it FreeBSD, illumos installation usb sticks or hard drives, or simply some data disks. Especially with "Windows 10", the PC is no longer a PC, not a _personal_ computer belonging to the user; it's rather a system remotely controlled by MICROS~1, and having installed "Windows" and therefore agreed to the terms of usage (EULA), there is probably nothing "wrong" with it, because you have agreed that they can do whatever they want, and if something goes wrong, it's your fault. Legal business as usual. Yes, agreed. They far outstrip the robber barons of the 1800s in their greed. Even Carnegie finally discovered a heart beating inside of himself, and gave us libraries and Napoleon Hill! Many years (or let's say, decades) I had a similar problem with an OS/2 installation: It messed up the system's partition table, a system where DOS (not that DOS, the other one) was installed, and there was a data loss: Partition D: became C:, E: became D:, F: became E:, and C: along with its content seemed to be gone. But in the overall "disk space calculation" it must still have been on disk, so I used the Norton Disk Editor (DISKEDIT.EXE from Norton Utilities, a great product at that time!), a handheld calculator and pen & paper to re-calculate the correct values for the partition table, entered them, rebooted, prayed unto the holy bringer of peace, Alpha-Omega, and tadaa, C: was there again, with the correct content. I never had that wonderful luxury of being saddled with a "real" IBM machine or OS/2. One would note that they, too (along with MS, eventually), are being relegated to the dustbin of history where they belong. [snip] That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. They don't mind. They already have your money. And maybe they even have your name, address, phone number, credit card number or other banking information... I have a few last resort technologies they *don't* know about, though they are not worth any more of my time or psychic energy. :D ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
drm i915kms on 12.1-STABLE (r363237)
Hi all together, yesterday I installed 12.1-STABLE [1] with kernel version `uname -K` 1201519 on my ThinkPad E490 with 'Intel UHD Graphics 620' [2]. But if I install the 'drm-fbsd12.0-kmod' and load the driver `kldload /boot/modules/i915kms.ko` it will only show a black screen until I manually poweroff the notebook. See the `/var/log/messages` [3] below. The 'drm-fbsd12.0-kmod' from pkg [4] behaves the sames as if I build it manually from ports. On 12.1-RELEASE it worked just fine. Has anybody a hint for me, what might be wrong and how I should deal with it? Regards, Nils [1] FreeBSD-12.1-STABLE-amd64-20200702-r362880-memstick.img [2] pciconf -lv ``` vgapci0@pci0:0:2:0: class=0x03 card=0x507217aa chip=0x3ea08086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'UHD Graphics 620 (Whiskey Lake)' class = display subclass = VGA ``` [3] /var/log/messages ``` Jul 17 09:13:23 NilsJ-TP kernel: drmn0: on vgapci0 Jul 17 09:13:23 NilsJ-TP kernel: vgapci0: child drmn0 requested pci_enable_io Jul 17 09:13:23 NilsJ-TP syslogd: last message repeated 1 times Jul 17 09:13:23 NilsJ-TP kernel: [drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19). Jul 17 09:13:23 NilsJ-TP kernel: Successfully added WC MTRR for [0x9000-0x9fff]: 0; Jul 17 09:13:23 NilsJ-TP kernel: [drm] Got stolen memory base 0x8a80, size 0x200 Jul 17 09:13:23 NilsJ-TP kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Jul 17 09:13:23 NilsJ-TP kernel: [drm] Driver supports precise vblank timestamp query. Jul 17 09:13:23 NilsJ-TP kernel: [drm] Connector eDP-1: get mode from tunables: Jul 17 09:13:23 NilsJ-TP kernel: [drm] - kern.vt.fb.modes.eDP-1 Jul 17 09:13:23 NilsJ-TP kernel: [drm] - kern.vt.fb.default_mode Jul 17 09:14:24 NilsJ-TP syslogd: kernel boot file is /boot/kernel/kernel Jul 17 09:14:24 NilsJ-TP kernel: ---<>--- Jul 17 09:14:24 NilsJ-TP kernel: Copyright (c) 1992-2020 The FreeBSD Project. Jul 17 09:14:24 NilsJ-TP kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jul 17 09:14:24 NilsJ-TP kernel:The Regents of the University of California. All rights reserved. Jul 17 09:14:24 NilsJ-TP kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jul 17 09:14:24 NilsJ-TP kernel: FreeBSD 12.1-STABLE r363237 GENERIC amd64 ``` [4] pkg info drm-fbsd12.0-kmod ``` drm-fbsd12.0-kmod-4.16.g20200221 Name : drm-fbsd12.0-kmod Version: 4.16.g20200221 Installed on : Fri Jul 17 09:10:42 2020 UTC Origin : graphics/drm-fbsd12.0-kmod Architecture : FreeBSD:12:amd64 Prefix : /usr/local Categories : graphics kld Licenses : BSD2CLAUSE, MIT, GPLv2 Maintainer : x...@freebsd.org WWW: https://github.com/FreeBSDDesktop/kms-drm Comment: DRM modules for the linuxkpi-based KMS components Options: DEBUG : off Annotations: FreeBSD_version: 1201000 repo_type : binary repository : FreeBSD ``` ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/17/20 1:34 AM, Manish Jain wrote: On 2020-07-17 13:57, Don Wilde wrote: On 7/16/20 7:40 PM, Manish Jain wrote: On 2020-07-17 01:49, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. It's taken me much of the morning to get underneath this, since on this unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu. That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. If I understand correctly, it's just that your Grub boot-loader is gone. Yes, exactly. That should not be much of a problem if your system is MBR+BIOS. Unfortunately, it's GPT under EFI. I can access all my files through the F12 key on this Dell tower, be it Windows, Linux or FreeBSD, but if I allow it to boot with the Doze HDD in the system, it boots to that one. If your system is MBR+BIOS, the following should work. Boot with your FreeBSD CD/DVD/memstick, and write out boot0 to all your disks: boot0cfg -B /dev/ boot0cfg -B /dev/ boot0cfg -B /dev/ Next, boot with your Ubuntu CD/DVD/memstick, and write out Grub to your Ubuntu / partition. If Ubuntu / is /dev/sdb2 : sudo mount /dev/sdb2 /mnt sudo grub-install --force --root-directory=/mnt /dev/sdb2 Reboot. When booting Ubuntu the first time, first press 'e' at the Grub loader menu to edit the configuration, delete the complete if..fi block, check that your line beginning with 'linux' is accurate and then press F10. Once the system has booted, run 'sudo update-grub'. I appreciate the good data, Manish. I'm going to make sure I've gotten all my files off the Doze partition and then wipe it completely. FreeBSD is going to be my primary host OS and I'll keep my other drive for whatever flavors of Linux I need to work with for work. Based on what I've hseen on these threads, MS is still saddled with a number of bad legacy architectural choices as well as poor management choices, and both of those contribute to the challenges the use of their OS brings. I simply won't accept any contract that requires me to work with Windows. I've survived well enough without that skill set and I see no problem going forward. Hi Done, It is further my sincere suggestion to use MBR+BIOS. GPT+UEFI is problem-prone, with one of the problems being that you won't be able to boot FreeBSD. I've already seen that one on my 'mule' machine. This tower (a 2007 machine) will boot FreeBSD directly even in UEFI-BIOS mode; I just need to set it up so that FreeBSD also hosts the boot-loader for the other OSen. To use one of my favorite phrases, "We'll get there!" :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 11:53 PM, Polytropon wrote: On Thu, 16 Jul 2020 13:19:51 -0700, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. They do this all the time. The consensus here is to install "Windows" first, always, restricted to the designated disk space, and _then_ install Linux, FreeBSD, GRUB, or anything else non-"Windows", in order to avoid the exact problem you are describing. Even older versions of "Windows" were known to destroy things like the FreeBSD boot manager when they are installed as a 2nd choice. MICROS~1 always wants you to treat it first class, with golden feet and glockenspiel. However, is my interpretation correct? Did this happen when you _installed_ "Windows" on that machine for the first time, or did it happen after you _booted_ an already installed instance of "Windows", which then did attack "foreign data" on the disk? This machine still maintains the original Windows installation, first with W7, and then (finally, bad mistake) upgraded to W10. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. Something like that should never happen. It's absolutely normal that "Windows" installs software without user consent, and then presents it prominently in user-configured areas such as the desktop, the "Start" menu, or the bottom bar (pun absolutely intended), but it should never exceed its authority beyong the border of the "Windows" partition, which clearly means: "Hands off of Grub partition!" Yes. The bastards also screwed up my 128GB backup drive -- again without asking -- when I left it plugged in during a Doze boot. Especially with "Windows 10", the PC is no longer a PC, not a _personal_ computer belonging to the user; it's rather a system remotely controlled by MICROS~1, and having installed "Windows" and therefore agreed to the terms of usage (EULA), there is probably nothing "wrong" with it, because you have agreed that they can do whatever they want, and if something goes wrong, it's your fault. Legal business as usual. Yes, agreed. They far outstrip the robber barons of the 1800s in their greed. Even Carnegie finally discovered a heart beating inside of himself, and gave us libraries and Napoleon Hill! Many years (or let's say, decades) I had a similar problem with an OS/2 installation: It messed up the system's partition table, a system where DOS (not that DOS, the other one) was installed, and there was a data loss: Partition D: became C:, E: became D:, F: became E:, and C: along with its content seemed to be gone. But in the overall "disk space calculation" it must still have been on disk, so I used the Norton Disk Editor (DISKEDIT.EXE from Norton Utilities, a great product at that time!), a handheld calculator and pen & paper to re-calculate the correct values for the partition table, entered them, rebooted, prayed unto the holy bringer of peace, Alpha-Omega, and tadaa, C: was there again, with the correct content. I never had that wonderful luxury of being saddled with a "real" IBM machine or OS/2. One would note that they, too (along with MS, eventually), are being relegated to the dustbin of history where they belong. [snip] That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. They don't mind. They already have your money. And maybe they even have your name, address, phone number, credit card number or other banking information... I have a few last resort technologies they *don't* know about, though they are not worth any more of my time or psychic energy. :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: URGENT: Microsoft overwrites boot loader!
On 7/16/20 7:40 PM, Manish Jain wrote: On 2020-07-17 01:49, Don Wilde wrote: The [deleted] ones in Redmond have done it again. My multi-OS GRUB2 boot loader is gone, and in its place is a 500M partition called 'Windows boot loader'. The purpose is to force us to look at MS' new version of Edge. All my old boot files are gone. It's taken me much of the morning to get underneath this, since on this unit my only OS (other than Doze 10) with a WM and GUI is Ubuntu. That's the last time I will allow this, and I'm calling those [deleted]s tomorrow to give them a piece of my mind. After that I will erase every vestige of that obscene OS from my disk. If I understand correctly, it's just that your Grub boot-loader is gone. Yes, exactly. That should not be much of a problem if your system is MBR+BIOS. Unfortunately, it's GPT under EFI. I can access all my files through the F12 key on this Dell tower, be it Windows, Linux or FreeBSD, but if I allow it to boot with the Doze HDD in the system, it boots to that one. If your system is MBR+BIOS, the following should work. Boot with your FreeBSD CD/DVD/memstick, and write out boot0 to all your disks: boot0cfg -B /dev/ boot0cfg -B /dev/ boot0cfg -B /dev/ Next, boot with your Ubuntu CD/DVD/memstick, and write out Grub to your Ubuntu / partition. If Ubuntu / is /dev/sdb2 : sudo mount /dev/sdb2 /mnt sudo grub-install --force --root-directory=/mnt /dev/sdb2 Reboot. When booting Ubuntu the first time, first press 'e' at the Grub loader menu to edit the configuration, delete the complete if..fi block, check that your line beginning with 'linux' is accurate and then press F10. Once the system has booted, run 'sudo update-grub'. I appreciate the good data, Manish. I'm going to make sure I've gotten all my files off the Doze partition and then wipe it completely. FreeBSD is going to be my primary host OS and I'll keep my other drive for whatever flavors of Linux I need to work with for work. Based on what I've hseen on these threads, MS is still saddled with a number of bad legacy architectural choices as well as poor management choices, and both of those contribute to the challenges the use of their OS brings. I simply won't accept any contract that requires me to work with Windows. I've survived well enough without that skill set and I see no problem going forward. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Ethernet interface Watchdog timeout
Hi! > # uname -a > FreeBSD lash.internal 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 GENERIC amd64 See here: https://www.freebsd.org/security/advisories/FreeBSD-EN-20:09.igb.asc -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Ethernet interface Watchdog timeout
Last night I needed to reboot switches connected to a FreeBSD server. There are two igb interfaces, bound via lagg0 as an LACP pair. Each is connected to a different switch and those switches support mlag (LAG distributed across more than one switch unit). One of the interfaces came back fine when its switch rebooted, but when the second switch was rebooted several hours later the other interface didn't. Both igb0 and igb1 interfaces are on the motherboard itself. This has happened once before, and rebooting the FreeBSD server resolved it. Obviously I'd like to understand the problem better first. Is there more debugging I could collect while the server is in this state? Physically removing the ethernet cable and plugging it back in does not bring the interface up. ifconfig down and up also does not help. What is this watchdog timeout that we are seeing in the logs? Ari # ifconfig igb0 igb0: flags=8c03 metric 0 mtu 1500 options=e507bb ether ac:1f:6b:00:ea:b2 media: Ethernet autoselect status: no carrier nd6 options=29 # uname -a FreeBSD lash.internal 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 GENERIC amd64 # grep igb0 /var/log/messages Jul 8 23:00:43 lash kernel: igb0: Watchdog timeout (TX: 0 desc avail: 42 pidx: 1003) -- resetting Jul 8 23:00:43 lash kernel: igb0: link state changed to DOWN Jul 8 23:00:44 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting Jul 9 00:00:01 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting Jul 9 05:01:12 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting Jul 9 05:06:56 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting Jul 9 14:25:33 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting Jul 9 14:44:30 lash kernel: igb0: Watchdog timeout (TX: 7 desc avail: 1024 pidx: 0) -- resetting igb0@pci0:1:0:0: class=0x02 card=0x152115d9 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'I350 Gigabit Network Connection' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR NS link x4(x4) speed 5.0(5.0) ASPM disabled(L0s/L1) ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 ac1f6b00eab2 ecap 000e[150] = ARI 1 ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled 0 VFs configured out of 8 supported First VF RID Offset 0x0180, VF RID Stride 0x0004 VF Device ID 0x1520 Page Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576, 4194304 ecap 0017[1a0] = TPH Requester 1 ecap 0018[1c0] = LTR 1 ecap 000d[1d0] = ACS 1 # dmidecode -t baseboard # dmidecode 3.2 Scanning /dev/mem for entry point. SMBIOS 3.0 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Supermicro Product Name: X10DRW-i Version: 1.02 Serial Number: NM173S002991 Asset Tag: Default string Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0021, DMI type 41, 11 bytes Onboard Device Reference Designation: ASPEED Video AST2400 Type: Video Status: Enabled Type Instance: 1 Bus Address: :05:00.0 Handle 0x0022, DMI type 41, 11 bytes Onboard Device Reference Designation: Intel Ethernet i350 #1 Type: Ethernet Status: Enabled Type Instance: 1 Bus Address: :01:00.0 Handle 0x0023, DMI type 41, 11 bytes Onboard Device Reference Designation: Intel Ethernet i350 #2 Type: Ethernet Status: Enabled Type Instance: 2 Bus Address: :01:00.1 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
