Re: New console output at boot?

On 9/25/24 12:46, Tomek CEDRO wrote: Also question is if serial console port can be used to catch the full bootloader process ? This is a laptop without a hardware serial port. My serial dongle needs USB to operate and those drivers don't get loaded before the boot process begins. Tom -- P

Re: New console output at boot?

On 9/25/24 09:37, Thomas Laus wrote: On 9/25/24 08:03, Ronald Klop wrote: Hi, Nice work. I did the video trick also in the past with boot issues. Can you tell us what the errors are? Like what filenames are mentioned. Maybe post the screenshot of the video somewhere. My /boot/fonts on

Re: New console output at boot?

On 9/25/24 08:03, Ronald Klop wrote: Hi, Nice work. I did the video trick also in the past with boot issues. Can you tell us what the errors are? Like what filenames are mentioned. Maybe post the screenshot of the video somewhere. My /boot/fonts on raspberry pi 4 15.0-CURRENT contains. $ ls

Re: New console output at boot?

On 9/24/24 15:26, Warner Losh wrote: Thinking about it, I found a hole. If gptzfsboot picked the wrong BE this could happen. And updating it might fix a bug that's causing it. Knowing when your system last updated the gptzfsboot would be useful... After getting a hint to use my cellphone cam

Re: New console output at boot?

On 9/24/24 15:26, Warner Losh wrote: Thinking about it, I found a hole. If gptzfsboot picked the wrong BE this could happen. And updating it might fix a bug that's causing it. Knowing when your system last updated the gptzfsboot would be useful... The last time that my gptzfsboot was updated

Re: New console output at boot?

On 9/24/24 14:42, Thomas Laus wrote: On 9/24/24 13:55, Warner Losh wrote:     FreeBSD 15.0-CURRENT #13 1c6bb4c57 Impossible. Gptzfsboot is an earlier phase than the new message. It can't produce a mismatch. Only loader/loader.efi vs /boot/lua/* can cause this. And usually in this setup

Re: New console output at boot?

On 9/24/24 13:55, Warner Losh wrote: FreeBSD 15.0-CURRENT #13 1c6bb4c57 Impossible. Gptzfsboot is an earlier phase than the new message. It can't produce a mismatch. Only loader/loader.efi vs /boot/lua/* can cause this. And usually in this setup both are updated as a pair. It might not

Re: New console output at boot?

On 9/24/24 11:04, Warner Losh wrote: On Sun, Sep 22, 2024 at 6:21 PM Kevin Oberman > wrote: Since an update to current a couple of weeks ago, I now see several lines (6 or 7) early in the boot. I'm not sure whether it is from one of the boots or the loader

Re: Freebsd 14+ -- tcsh incompatible with terminfo

n for that). (-T is appropriate here - ymmv) With -C alone, I get -rw--- 1 tom users 7315 Nov 2 21:02 .TCAP With -CrT, -rw--- 1 tom users 14390 Nov 2 21:02 .TCAP For terminfo, no options -rw--- 1 tom users 16027 Nov 2 21:03 .TCAP For terminfo with -x -rw--- 1 tom users 19533 No

Re: Freebsd 14+ -- tcsh incompatible with terminfo

$TERMCAP would be work) > Is this, therefore, a terminfo.db issue? > > Thanks again, Jamie > -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature

Re: documentation nit / TERMINFO in ncurses man pages

ory reference is set to *d here in the tic manpage: > > 18259542b2f8f contrib/ncurses/man/tic.1m 2000-10-11 07:31:01 + 37) .ds > d @TERMINFO@ > > Since this is also set in alot of other places, we probably need someone to > make some sort of decision :-) > > Dan > -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature

Installation using NFS spams console

I have been building FreeBSD CURRENT every 2 weeks for years. I build on a fest PC and then use NFS exports of /usr/src and /usr/obj to update several other PC's. I received many 'Permission denied' messages as the kernel and world installs progressed. make[4]: warning: /usr/obj/usr/src/amd

Re: Beadm can't create snapshot

On 9/12/22 05:29, Ryan Moeller wrote: Here's the patch for the kernel and brief instructions: https://reviews.freebsd.org/P547 That worked. I was not familiar with patching a file using git. My experience has always used the 'patch' utility and a unified diff. I just made a backup of the

Re: Beadm can't create snapshot

On 8/17/22 10:35, Thomas Laus wrote: I attempted to create a ZFS snapshot after upgrading this morning and received this error After all of the discussion to compare and contrast beadm vs. bectl my read only bit is still set as of this morning 29-AUG-2022. # beadm create n257658 cannot

Non EFI boot issue

Another issue with the update today. This update went well on all of my PC's that use EFI but spews a lot of disturbing messages on my only laptop without an EFI BIOS: Attempted recovery for standard superblock: failed Attempt to find boot zone recovery data: failed It jumps to what is normal

Beadm can't create snapshot

I attempted to create a ZFS snapshot after upgrading this morning and received this error # beadm create n257443 cannot create 'zroot/ROOT/n257443': 'snapshots_changed' is readonly # My version info: 14.0-CURRENT FreeBSD 14.0-CURRENT #9 main-n257443-f7413197245: Wed Aug 17 08:15:27 EDT 2022

[FIXED] Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/11/22 11:17, Dennis Clarke wrote: Did the usual git pull origin main and buildworld/buildkernel but after installkernel the machine will not boot. The rev seems to be main-n254654-d4e8207317c. I can boot single user mode and get a command prompt but nothing past that. Is there something

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/18/22 21:43, Graham Perrin wrote: On 12/04/2022 23:35, Dennis Clarke wrote: … at least two examples in the wild. … Not the same symptom, but caught my eye: RC3 Guided ZFS on root with encryption unmountable Beyond that, I ha

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/13/22 07:17, Thomas Laus wrote: I had an idea that maybe a GELI encrypted disk may have an issue.  Both my laptop and desktop have encrypted disks.  The gpart partitions have a .efi appended to the name that 'gpart list' shows.  Not everyone uses GELI and that may be our diff

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/12/22 18:35, Dennis Clarke wrote: I will focus on the problem case I have and try to get better information. Somehow. I had an idea that maybe a GELI encrypted disk may have an issue. Both my laptop and desktop have encrypted disks. The gpart partitions have a .efi appended to the name

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/12/22 08:29, Ronald Klop wrote: Are you guys both using NVME or EFI? Just wondering if the common problem is in ZFS or some other component. I just repeated this issue on the desktop computer that is used for my weekly builds that get distributed to the other PC's in the house. In order

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/11/22 14:18, Ronald Klop wrote: On 4/11/22 17:17, Dennis Clarke wrote: Did the usual git pull origin main and buildworld/buildkernel but after installkernel the machine will not boot. The rev seems to be main-n254654-d4e8207317c. I can boot single user mode and get a command prompt but

Re: Kernel Panic main-n252492-ad15eeeaba3 - Solved

On 1/17/22 16:33, Thomas Laus wrote: I just updated today to main-n252492-ad15eeeaba3 from: main-n252313-ae13829ddce on 3 PC's. I tried bisecting the 87 changes involved between main-n252508-aac52f94ea5 to main-n252492-ad15eeeaba3 and started at the halfway point and worked forward.

Kernel Panic main-n252492-ad15eeeaba3

I just updated today to main-n252492-ad15eeeaba3 from: main-n252313-ae13829ddce on 3 PC's. Two of them had the update go well but my Dell Inspiron 1545 had a panic after booting. This laptop doesn't have a scroll buffer and the entire panic message scrolls off the screen, so can't take a scre

Re: main changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS but /usr/lib/libdialog.so.? naming was not adjusted? (crashes in releng/13 programs on main [so: 14] can result)

pstream does do symbol versioning, but I don't know that can help, (it doesn't appear to have some way of saying "version >= whatever", but only "version == whatever"). The soname should be updated (which is what you're talking about "bumped") -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature

Re: EFI boot partition overwritten: mount -t msdosfs (or mount_msdosfs(8))

On 7/18/21 2:21 PM, Graham Perrin wrote: > On 16/07/2021 18:35, Warner Losh wrote: >> # newfs_msdos -F 32 /dev/ada0p4 >> # mount -t msdos /dev/ada0p4 /boot/efi > > > Typo: msdosfs, not msdos. > > Alternatively, mount_msdosfs(8). > > Alternatively (I agree, even better), incorporate things such

Re: EFI boot partition overwritten

On 7/16/21 1:35 PM, Warner Losh wrote: > > There should be. Yes. Last time I went hunting for a place to shoe-horn it > in, I got distracted by something else. > > The instructions are relatively straight forward. I'm writing them here for > your benefit, and also in case someone wants to send me

EFI boot partition overwritten

Group: This is an issue for more than just CURRENT. The 'usr/src/UPDATING' file has the instructions for updating the ZFS bootblocks but not the EFI partition. I recently upgraded a RELEASE-12.2 to RELEASE-13.0. The freebsd-update procedure did not upgrade the ZFS bootblocks. I forgot that thi

Re: drm-kmod kernel crash fatal trap 12

On 6/19/21 2:21 PM, Bakul Shah wrote: > > You may wish to see if Andriy Gapon's method (LOCAL_MODULES_DIR, > LOCAL_MODULES) > works better for you. > > I trust Makefile* to do the right thing with META_MODE and CCACHE (and if they > don't, it is a bug that would need to be fixed) so I personally

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 11:13 AM, Bakul Shah wrote: > This is what I did: > > git clone https://github.com/freebsd/drm-kmod > ln -s $PWD/drm-kmod /usr/local/sys/modules > > Now it gets compiled every time you do make buildkernel. > If things break you can do a git pull in the drm-kmod dir > and rebuild. > Tha

Re: drm-kmod kernel crash fatal trap 12

Bakul Shah [ba...@iitbombay.org] wrote: > > This is what I did: > > git clone https://github.com/freebsd/drm-kmod > ln -s $PWD/drm-kmod /usr/local/sys/modules > > Now it gets compiled every time you do make buildkernel. > If things break you can do a git pull in the drm-kmod dir > and rebuild. >

Re: drm-kmod kernel crash fatal trap 12

Hans Petter Selasky [h...@selasky.org] wrote: > > When you use -current, you need to compile this pkg from the latest ports. > I'm not sure if that happens automatically when you install the binary > package. > I just built drm-current-kmod as a port and things work. Building a kernel in the past

Re: drm-kmod kernel crash fatal trap 12

Hans Petter Selasky [h...@selasky.org] wrote: > > Make sure you also re-build the drm-kmod module. > The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. Things are good at n247230. I cleaned my source today and checked out fres

drm-kmod kernel crash fatal trap 12

I updated my system this morning to main-n247260-dc318a4ffab June 9 2012 and the first boot after the kernel was loaded I received: 'fatal trap 12' fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0x82fc3d1b stack pointer = 0x28:0x

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is > missing sw > IOW the line MUST read as: > /dev/gpt/Sea1-18noneswapsw 0 0 > or > /dev/gpt/Sea1-18noneswapsw,trimonce 0 0 > as appropriate for the media referenced.

Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be successful with "dhclient re0". UPDATING file says to boot single-user after buildkernel and installkernel, but then mount -u / or mount -u

Updating to FreeBSD-current, can't mount -uw /

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be successful with "dhclient re0". UPDATING file says to boot single-user after buildkernel and installkernel, but then mount -u / or mount -u

Re: Spam mail being sent via the FreeBSD mailing lists

from Kurt Jaeger: > Hi! > > > On May 25, 2021, at 8:53 PM, jake h wrote: > > > I have recently received several pieces of spam mail, apparently sent via > > > this mailing list. These pieces of mail are the usual spam formula; Your > > > phone has a virus, Ads, Fake blackmail, so on and s

Re: 13.0-RC3 bison causes tputs SIGSEGV

On Sat, Apr 03, 2021 at 02:36:29PM -0400, Thomas Dickey wrote: ... attaching trace :-) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net TRACING NCURSES version 6.2.20210403 (tracelevel=0x) called {setupterm("screen",2,0x7fffe2b0) your termin

Re: 13.0-RC3 bison causes tputs SIGSEGV

On Wed, Mar 31, 2021 at 07:54:09PM -0400, Thomas Dickey wrote: > On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote: > > On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote: > > > > > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: >

Re: 13.0-RC3 bison causes tputs SIGSEGV

On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote: > On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote: > > > > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > > > > > >> > > >> Knowing that would help me see w

Re: 13.0-RC3 bison causes tputs SIGSEGV

CTL_AUTO, style_file_name)); > > Does it make any difference? I don't know yet. I've been setting up a build for bison+libtextstyle so that I can study it firsthand (and use valgrind, etc., to look for problems). That chunk is just the initialization, while the problem appears l

Re: 13.0-RC3 bison causes tputs SIGSEGV

for (_nc_nulls_sent += nullcount; nullcount > 0; nullcount--) >104 my_outch(NCURSES_SP_ARGx PC); >105 if (my_outch == NCURSES_SP_NAME(_nc_outch)) >106 NCURSES_SP_NAME(_nc_flush) (NCURSES_SP_ARG); > > Application is using term_styled_ostream_create()

Re: 13.0-RC3 bison causes tputs SIGSEGV

$$bison + > 7679 > frame #12: 0x0042e9c8 bison`___lldb_unnamed_symbol459$$bison + 56 > frame #13: 0x00403743 bison`___lldb_unnamed_symbol130$$bison + 291 > frame #14: 0x00403be0 bison`___lldb_unnamed_symbol130$$bison + > 1472 > (lldb) > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature

Re: Problem with X Server when updating to 38bfc6dee33

On 2/3/21 12:12 PM, Niclas Zeising wrote: > > I think also xf86-input-synaptics was affeced by the same issue. > In any case, kern.evdev.rcpt_mask should not need any changes on FreeBSD > 12.1 or later, the defaults have been updated there.  Unless you are > using a serial mouse. > > Can you prov

Re: Problem with X Server when updating to 38bfc6dee33

On 2/3/21 8:07 AM, Michael Gmelin wrote: > > There was a problem with xorg-server which made it build without udev > on 14. > > Try reinstalling xorg-server from ports (something like: portsnap > fetch extract; cd /usr/ports/x11-servers/xorg-server && make clean > reinstall clean) > That also di

Re: Problem with X Server when updating to 38bfc6dee33

On 2/2/21 8:16 AM, David Wolfskill wrote: > You might want to see if this ports/UPDATING entry: > > 20200320: > AFFECTS: users of x11/libxkbcommon > AUTHOR: zeis...@freebsd.org > > The libxkbcommon library (x11/libxkbcommon), used to handle keyboards > in some applications, most notably k

Problem with X Server when updating to 38bfc6dee33

I updated from c3e75b6c1 to 38bfc6dee33 today and my keyboard and mouse no longer work in X. Since my system went from 13.0-CURRENT to 14.0-CURRENT, I performed a 'pkg bootstrap -f' because of the ABI change. I also performed a fresh git checkout of main after I first noticed the issue. I built

Re: svnlite behaviour changed?

Good morning! > I regularly sync my FreeBSD source tree with the central repository using svn > update. I use a one-lis script to synchonize, which sends the output of svn > to a file, and also copies to the console. This list contained - according to > the 'svn help update' - one line

Poudriere failed to build pkg in 13-stable jail under 12-stable

The build of a 13-stable source and kernel were a success under 12-stable (though with some issues on freeze-ups and hard reboots that I suspect might be related to the bufdaemon issue and my 0x15 gen AMD cpu). Created a 13-stable poudriere jail with the knowledge that there may be issues with bui

Re: Getting /usr/src to match specific git hash?

> It is in the mini primer I wrote, along with how to bisect and other useful > things. This will migrate into the handbook once the doc tree converts to > asciidoc (happening this weekend). > https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md > Warner I looked at your mini-p

RE: Which branch in git is 13.0-current?

> > Does that mean CURRENT is now 14.0? I must have missed the > > announcement. > That is correct, 13-stable has been branched from 13-current which has now > been bumped to 14-current. > Because it's a major version change going from 13 to 14, pkg is a bit > agitated regarding the ABI. > > > D

Re: DRM problem installing kernel on main-c561-gc3e75b6c1

On 1/19/21 4:18 PM, Emmanuel Vadot wrote: > > drm-current-kmod will also install its sources in /usr/local/sys/ and > this will get built with buildkernel. The problem is that if the > package is old (and it is right now) you might have sources that either > don't compile or don't work correctly.

DRM problem installing kernel on main-c561-gc3e75b6c1

I perform a CURRENT build weekly on a more powerful build machine and then export /usr/src and /usr/obj via NFS to other slower PC's. The 'installkernel' phase failed with 'linuxkpi_gplv2.ko' not found. It looks like this file is not installed before the rest of the 'drm-current-kmod' files. Thi

Re: git and the loss of revision numbers

> Disclaimer: I just started to learn git, never used it before. > If I do understand it correctly, the switch from svn to git comes with a loss > of continuously increasing revision numbers. Correct? If so I wonder how > future security advisories and errata notices will be composed. Will there

Re: src: continued use of Subversion for getting updates

> stable/11 as well as the releng branches for as long as the project has > them under support. I wrote the code to replay commits into subversion for > the convenience of our users on those branches. The 12.x releases will be > built out of Subversion to preserve $FreeBSD$ expansion and other obsc

Re: git tools for building in base?

> Yes. I was answering the first question asked about FreeBSD and git... > The clincher for me was that git is better supported by third party tools > and has gotten quite good at 'recovery from oops' which mercurial is still > lacking in both areas. I too have used both, and I had to re clone my

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

> > I hope we don't have to start signing all commits. saltstack/salt has > > that policy, and it's extremely annoying. > Have to? Not currently. As with all process changes, there will be > community discussion around the different points. > Warner I hope not! Signatures, at least in email me

Re: git tools for building in base?

from tech-lists: > As subject - what will there be in base to interact with the new git repo? > I mean, right now, for svn there is svnlite. What for git? > Shouldn't it be in base before the move to git? Good question, and I hope the developers and others in charge are reading your post. You

Re: in -current is svn still canonical?

from Warner Losh and my last message: > > Thanks for the information, but if you feel the need to send me a > > not-quite-CC, please don't send me the multipart/alternative version when > > you send the plain-text version to the list. > > I hate multipart/alternative! > I must apologize.

Re: in -current is svn still canonical?

> Subversion is the source of truth for FreeBSD today. > In the near future, likely early next month, we'll move our operations over > to git. Git will be the source of truth after the flag day. All developer > operations will be in git: committing to current, and MFCing will all be > d

Re: in -current is svn still canonical?

from tech-lists: > As subject - is svn still canonical for -current or is it git now? > If it's not git now, when roughly is the intended switch? I recently updated FreeBSD doc, ports, src (current), and src12 (12-stable) using svn (not svnup or svnlite). But I read some time before that, FreeB

Re: Livelock on recent current

> I am seeing a problem since I moved to current on my laptop this week. It's > odd as it is linked to the keyboard. As long as the keyboard is active, > everything is fine, but if the keyboard is not used, after a few minutes, > it locks up and gets very hot. The system may be busy or idle. The sy

Re: Please check the current beta git conversions

from Kevin Oberman: > > So I am abandoning FreeBSD 12.x . > > Hopefully I could update 13-current from within 13-current where I have no > > internet access but could use git from NetBSD, where I also have svn. > > Tom > Not really much different from subversion. .svn in /usr/sys is a

Re: Please check the current beta git conversions

from Ed Maste: > > Any guidance on amount of diskspace and how long it takes to clone the repo > > ? > I see just over 3GB in my clone, including about 2.5GB in the .git directory. > If you have only one checkout git will require a bit more disk space > than svn. However, if you have two or mor

What is the zstreamdump command in OpenZFS?

Group: Whenever I perform a major upgrade to any of my ZFS pools, I make a habit of sending the most recent snapshot to a file and then to a DLT tape or DVD. I run the zstreamdump utility on the file and record the checksum. I also run zstreamdump on the archive media and compare checksums. Wit

Re: Geli encryption issue on r362779

> On 2020-07-10 03:56, Toomas Soome wrote: >> >> ok, then next one is r363042. By nature it is an safeguard against read >> past disk end. >> >> If that does not do, we really need to insert checkpoints in code and >> see where exactly this reset will happen. Also note I >> have https://reviews.fre

Re: Geli encryption issue on r362779

On 2020-07-10 03:56, Toomas Soome wrote: > > ok, then next one is�r363042. By nature it is an safeguard against read > past disk end. > > If that does not do, we really need to insert checkpoints in code and > see where exactly this reset will happen. Also note I > have�https://reviews.freebs

Re: Geli encryption issue on r362779

On 2020-07-07 08:26, Toomas Soome wrote: > Hi! > > I believe, 362989 should fix your issue. Please do let me know. > I updated to r362989. I built world and kernel after clearing out /usr/obj and this problem still exists. It works fine on my i5 desktop, but still has a problem reading my Geli e

Re: Geli encryption issue on r362779

On 2020-06-30 11:31, Toomas Soome wrote: > > hi! > > 362431: https://svnweb.freebsd.org/base?view=revision&revision=362431 > > The majority of the code is now shared with loader (libsa/libi386), > however, we do have some bits in zfsboot.c, which is common part of > gptzfsboot and zfsboot. > Tha

Geli encryption issue on r362779

This is a repost to this list because of my submission email address did not match the one on record. == List: I just upgraded a couple of computers from r362220 to r362779 and have booting issue on my Core2 duo laptop with the passphrase unlocking the encrypted pa

Re: r358062(ncurses) breaks installed ports, howto check?

On Tue, Feb 25, 2020 at 10:27:37AM +0100, Baptiste Daroussin wrote: > On Tue, Feb 25, 2020 at 04:19:56AM -0500, Thomas Dickey wrote: > > On Mon, Feb 24, 2020 at 08:28:03PM -0500, Thomas Dickey wrote: > > > On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote: > >

Re: r358062(ncurses) breaks installed ports, howto check?

On Mon, Feb 24, 2020 at 08:28:03PM -0500, Thomas Dickey wrote: > On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote: > > On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote: > > > On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote: > >

Re: r358062(ncurses) breaks installed ports, howto check?

On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote: > On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote: > > On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote: > > > From: "O. Hartmann" > > > Subject: r358062(ncurses

Re: r358062(ncurses) breaks installed ports, howto check?

On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote: > On Tue, Feb 25, 2020 at 04:37:11AM +0900, Yasuhiro KIMURA wrote: > > From: "O. Hartmann" > > Subject: r358062(ncurses) breaks installed ports, howto check? > > Date: Mon, 24 Feb 2020 20:19:59 +0100

Re: r358062(ncurses) breaks installed ports, howto check?

*+ti tput6 n5*+ti tset n5*+ti tset6 *n+cx view6 *n+cx vieww ti vile n5* wormt n5* wormtw ti xgettext tc xterm tc xterm-330 tc xterm-339 tc xterm-340h tc xterm-350 tc xterm-dev -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature

Re: 13-Current not format efi partition

from Andrey Fesenko: > bsdinstall script, work in 2019 PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / } #!/bin/sh -x # Make diskname independante gpart modify -l freebsd-boot -i 1 ada0 gpart modify -l efi -i 2 ada0 gpart modify -l root -i 3 ada0 # Make EFI happy

Current r355939 + drm-current-kmod 4.16g20191217 compiles and runs

After about one week of problems, I was able to successfully compile and start DRM on 3 computers. My hardware Atom D510, Intel i5 Skylake and an Intel Core2-Duo laptop. I had to rm -rf /usr/obj/* on all of them however, to get a successful compile. Thanks Tom -- Public Keys: PGP KeyID = 0x5F

FreeBSD Friday

Hello all, Apologies if this is going to the wrong list, but I would like to make FreeBSD my every day operating system. After researching, I became aware I need a commit that was made only 2 days ago. It is suppose to be merged to 12-STABLE soon, but I'd like to install today. The commit I need

Brickyard 4439 Runaway Trim from 6 Nov 2019

Claude: Another video from Juan Brown about an issue with an flight from Atlanta to New York. It is another 'fly by wire' type of aircraft and Juan goes into great detail on the hardware and software issue. Not quite a 737-Max issue, but similar. https://www.youtube.com/watch?v=vV_o9kTRXUY Tom

Re: DRM-current-kmod is still a problem at r353339

from Neel Chauhan: > For me, the following code is still necessary for me (HP Spectre x360 > 2018), which is the remaining parts of the patches not committed if you > are using a recent kernel. I don't know about you all ThinkPad users, it > should still apply as it's Intel in general not just

Re: sweeping change over all NIC drivers

from Gleb Smirnoff: > I'd like to commit a sweeping change over all NIC drivers, > details can be found here: > https://reviews.freebsd.org/D21943 > The stack changes froim the review are already committed, > only a bunch of drivers are left. You can browse them as > individual commits here: >

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-10 13:44, Mateusz Guzik wrote: > Probably whitespace issues from copypasting. I used dpaste since > people.freebsd.org was down. > > It's up, so: > https://people.freebsd.org/~mjg/pmap-fict3.diff > That patch worked for me also. The patch applied clean when I used 'wget' to retrieve vs

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-10 12:21, Mateusz Guzik wrote: > Try this: > > http://dpaste.com/0P2MXF6 > > if it still fails, provide the panic info + the first debug line(the > one with "pv_table"). > This patch did not apply cleanly to my source tree checked out today. My pmap.c version is r353311. I saved the f

DRM-current-kmod is still a problem at r353339

List: I am still getting kernel panics on my laptop after the recent changes made to /sys/amd64/amd64/pmap.c. The updated pmap.c works on my Skylake build machine but panics on my laptop. I always build on the faster computer and perform a installkernel and installworld from a nfs share. The Sk

Re: Booting anything after r352057 kills console - additional info

On 2019-09-25 17:51, Thomas Laus wrote: > I was able to mount my zfs filesystem r+w and added the rc_debug="YES" > to my rc.conf. The additional debug messages were written to the beadm > boot environment /var/log/messages. Since the computer locked up, I was > unable to r

Re: Booting anything after r352057 kills console

On 2019-09-24 15:09, Ian Lepore wrote: > > On my system, a whole lotta stuff happens between ntpd and syscons (the > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > that should write more info to syslog about what's happening between > ntpd and the lockup point. > Ian: I

Re: Booting anything after r352057 kills console

> Ian Lepore [i...@freebsd.org] wrote: > > > > On my system, a whole lotta stuff happens between ntpd and syscons (the > > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > > that should write more info to syslog about what's happening between > > ntpd and the lockup point.

Re: Booting anything after r352057 kills console

Ian Lepore [i...@freebsd.org] wrote: > > On my system, a whole lotta stuff happens between ntpd and syscons (the > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > that should write more info to syslog about what's happening between > ntpd and the lockup point. > The resul

Re: Booting anything after r352057 kills console

On 2019-09-24 11:58, Pete Wright wrote: > > darn, and they didn't give you any additional information in the > messages buffer, or generate a core file? > There were no messages in the syslog and no other log that showed anything after killing the console. On my working BEADM boot environment, th

Re: Booting anything after r352057 kills console

Pete Wright [p...@nomadlogic.org] wrote: > > I remember having similar issues a while ago when we were first hacking on > drm, one thing to try is updating /boot/loader.conf with the following: > debug.debugger_on_panic=0 > dev.drm.skip_ddb="1" > dev.drm.drm_debug_persist="1" > > these are semi-do

Re: Booting anything after r352057 kills console

Poul-Henning Kamp [p...@phk.freebsd.dk] wrote: > > In message <11db909b-57ee-b452-6a17-90ec2765c...@acm.org>, Thomas Laus writes: > > >Where do I go from here? The computer is an Intel i5 Skylake with > >onboard graphics. > > Based on personal experi

Booting anything after r352057 kills console

I updated my source today and when the computer was booted, the screen turned black at the point that the drm related kernel modules would normally load. Suspecting a drm issue, I commented out the rc.conf line that loads those kernel modules. This did not fix my problem. My last good kernel was

Re: Problem with USB after r349133

Nick Wolff [darkfiber...@gmail.com] wrote: > Thomas/HPS, > > I did manage to get a boot with hw.usb.no_boot_wait=1 set in loader.conf. > So if any debugging information off a running system would be helpful let > me know. > > Thanks, > Nick: That was the same workaround

Re: Problem with USB after r349133

Nick Wolff [darkfiber...@gmail.com] wrote: > Sorry for email spam but I was wrong. Just gets stuck now during reproping > a pci device after init happens(this is actually a trueos build which is > why you see openrc). That device it's getting stuck on is "Sky Lake-E CBDMA > Registers" which shouldn

Re: Someone broke USB

On 2019-07-06 16:50, Hans Petter Selasky wrote: > > Are you able to bisect the commit introducing the bad behaviour? > I built and booted r349160. My 'boot mount waiting for USBUS7 -> USBUS0 issue went away but the startup halted at the 'mounting late filesystems' step of rc.conf. I had the USB

Re: Problem with USB after r349133

On 2019-07-06 10:17, Graham Perrin wrote: > > I had the almost same (different bus numbers), just once, after updating > -CURRENT from r349099 to r349762. > > The subsequent boot of r349762 was free from the symptom. > > HP EliteBook 8570p, docked, with a Kensington keyboard and Logitech > track

Re: Problem with USB after r349133

On 2019-07-05 18:05, Hans Petter Selasky wrote: > > There has been very few USB changes, except for ACPI USB support in: > > https://svnweb.freebsd.org/changeset/base/349161 > https://svnweb.freebsd.org/changeset/base/349251 > It looks like I will need to build a few kernels to see what changes m

Problem with USB after r349133

I upgraded to CURRENT r349575 this week and my Dell Inspiron laptop stops processing the rc.conf with this message that repeats until I perform a hard power button reset, ctl-alt-del has no effect: Root mount waiting for USBUS7 USBUS6 USBUS0. I booted my kernel.old and everything is fine at

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

from Niclas Zeising and my previous post: > > On 6/22/2019 20:16, Thomas Mueller wrote: > > > I am trying to set up UEFI to boot my FreeBSD and NetBSD installations, > > > and later, Linux. > > Easy.  Refind should do that and allow selection from a menu. >

  1   2   3   4   5   6   7   8   9   10   >