Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Chris
On 2025-04-21 11:46, Chris wrote: On 2025-04-21 10:47, Dag-Erling Smørgrav wrote: Chris writes: Can I safely move my new kernel to say, kernel.new while running my current kernel as kernel and rebuild the new kernel with the kernconf corrections? If you're booted into kernel.old you can jus

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Chris
On 2025-04-21 10:47, Dag-Erling Smørgrav wrote: Chris writes: Can I safely move my new kernel to say, kernel.new while running my current kernel as kernel and rebuild the new kernel with the kernconf corrections? If you're booted into kernel.old you can just build a new kernel and run `make r

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Dag-Erling Smørgrav
Chris writes: > Can I safely move my new kernel to say, kernel.new while running my current > kernel as kernel and rebuild the new kernel with the kernconf corrections? If you're booted into kernel.old you can just build a new kernel and run `make reinstallkernel` to replace the new (non-working)

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Chris
On 2025-04-21 09:29, Warner Losh wrote: On Mon, Apr 21, 2025 at 10:03 AM Chris wrote: On 2025-04-21 00:23, Gary Jennejohn wrote: > On Sun, 20 Apr 2025 12:19:45 -0700 > Chris wrote: > >> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote: >> > Chris writes: >> >> Warner Losh writes: >> >> > Mayb

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Chris
On 2025-04-21 06:42, Warner Losh wrote: Put 'da' back in. I'm pretty sure it's not optional. Well, maybe it is optional, but you'll need nda if you do that and the kernel config doesn't have that. While you have nvd, the default is to prefer nda to nvd, even when nda isn't in the kernel (so more

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Warner Losh
On Mon, Apr 21, 2025 at 10:03 AM Chris wrote: > > On 2025-04-21 00:23, Gary Jennejohn wrote: > > On Sun, 20 Apr 2025 12:19:45 -0700 > > Chris wrote: > > > >> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote: > >> > Chris writes: > >> >> Warner Losh writes: > >> >> > Maybe this is a custom kernel

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Chris
On 2025-04-21 00:23, Gary Jennejohn wrote: On Sun, 20 Apr 2025 12:19:45 -0700 Chris wrote: On 2025-04-20 01:15, Dag-Erling Smørgrav wrote: > Chris writes: >> Warner Losh writes: >> > Maybe this is a custom kernel without the label code. >> It's an upgrade. It's 15 from ~11 mos ago. Yes a cus

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Warner Losh
Put 'da' back in. I'm pretty sure it's not optional. Well, maybe it is optional, but you'll need nda if you do that and the kernel config doesn't have that. While you have nvd, the default is to prefer nda to nvd, even when nda isn't in the kernel (so more like an either or choice than a bidding ch

Re: New kernel doesn?t recognize ufs gpt root filesystem

2025-04-21 Thread Gary Jennejohn
On Sun, 20 Apr 2025 12:19:45 -0700 Chris wrote: > On 2025-04-20 01:15, Dag-Erling Smørgrav wrote: > > Chris writes: > >> Warner Losh writes: > >> > Maybe this is a custom kernel without the label code. > >> It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But > >> I'm using

Re: New kernel doesn’t recognize ufs gpt root filesystem

2025-04-20 Thread Chris
On 2025-04-20 01:15, Dag-Erling Smørgrav wrote: Chris writes: Warner Losh writes: > Maybe this is a custom kernel without the label code. It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But I'm using the same kernconf as before. Was label removed from generic in the last 11 mos

Re: New kernel doesn’t recognize ufs gpt root filesystem

2025-04-20 Thread Dag-Erling Smørgrav
Chris writes: > Warner Losh writes: > > Maybe this is a custom kernel without the label code. > It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But > I'm using the same kernconf as before. Was label removed from generic > in the last 11 mos.? Please share: - The output of the `w

Re: New kernel doesn’t recognize ufs gpt root filesystem

2025-04-19 Thread Chris
On 2025-04-19 22:23, Chris wrote: On 2025-04-19 20:36, Warner Losh wrote: On Sat, Apr 19, 2025, 8:51 PM Chris wrote: Finally got a build world/kernel to complete. Following a installkernel with a boot -s resulted in the inability to mount root (/dev/gpt/FBSD15) It’s a ufs2 filesystem. I boote

Re: New kernel doesn’t recognize ufs gpt root filesystem

2025-04-19 Thread Chris
On 2025-04-19 20:36, Warner Losh wrote: On Sat, Apr 19, 2025, 8:51 PM Chris wrote: Finally got a build world/kernel to complete. Following a installkernel with a boot -s resulted in the inability to mount root (/dev/gpt/FBSD15) It’s a ufs2 filesystem. I booted the 15-CURRENT usb stick. It reco

Re: New kernel doesn’t recognize ufs gpt root filesystem

2025-04-19 Thread Warner Losh
On Sat, Apr 19, 2025, 8:51 PM Chris wrote: > Finally got a build world/kernel to complete. Following a > installkernel with a boot -s resulted in the inability > to mount root (/dev/gpt/FBSD15) > It’s a ufs2 filesystem. I booted the 15-CURRENT > usb stick. It recognized it. I performed fsck on >

Re: New kernel-toolchain buildkernel problem for amd64 -> aarch64 cross build ( after -r336348 ) : ld used for addf_data only can target: elf_x86_64_fbsd elf_i386_fbsd

2018-07-16 Thread Mark Millard
[ toolchain-metadata.mk is missing when kernel-toolchain is used. I've no clue if this is intentional or not. ] On 2018-Jul-16, at 6:13 PM, Mark Millard wrote: > On 2018-Jul-16, at 4:47 PM, Bryan Drewery wrote: > >> On 7/16/2018 3:49 PM, Mark Millard wrote: >>> >>> >>> On 2018-Jul-16, at 3:3

Re: New kernel-toolchain buildkernel problem for amd64 -> aarch64 cross build ( after -r336348 ) : ld used for addf_data only can target: elf_x86_64_fbsd elf_i386_fbsd

2018-07-16 Thread Mark Millard
On 2018-Jul-16, at 4:47 PM, Bryan Drewery wrote: > On 7/16/2018 3:49 PM, Mark Millard wrote: >> >> >> On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote: >> >>> On 7/16/18 1:21 PM, Mark Millard wrote: I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain buildker

Re: New kernel-toolchain buildkernel problem for amd64 -> aarch64 cross build ( after -r336348 ) : ld used for addf_data only can target: elf_x86_64_fbsd elf_i386_fbsd

2018-07-16 Thread Bryan Drewery
On 7/16/2018 3:49 PM, Mark Millard wrote: > > > On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote: > >> On 7/16/18 1:21 PM, Mark Millard wrote: >>> I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain >>> buildkernel >>> targeting aarch64 from amd64 based on head -r336349 . I

Re: New kernel-toolchain buildkernel problem for amd64 -> aarch64 cross build ( after -r336348 ) : ld used for addf_data only can target: elf_x86_64_fbsd elf_i386_fbsd

2018-07-16 Thread Mark Millard
On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote: > On 7/16/18 1:21 PM, Mark Millard wrote: >> I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain >> buildkernel >> targeting aarch64 from amd64 based on head -r336349 . It failed by ending up >> using an ld that can only ta

Re: New kernel-toolchain buildkernel problem for amd64 -> aarch64 cross build ( after -r336348 ) : ld used for addf_data only can target: elf_x86_64_fbsd elf_i386_fbsd

2018-07-16 Thread Bryan Drewery
On 7/16/18 1:21 PM, Mark Millard wrote: > I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain > buildkernel > targeting aarch64 from amd64 based on head -r336349 . It failed by ending up > using an ld that can only target elf_x86_64_fbsd elf_i386_fbsd : I probably extended th

Re: new kernel and old programs - bad system call

2003-11-13 Thread John Hay
On Fri, Nov 14, 2003 at 06:38:28AM +1100, Bruce Evans wrote: > On Thu, 13 Nov 2003, John Hay wrote: > > > Is it ok to run a new kernel (after the statfs changes) and older > > programs? I thought so from what i gathered out of the commit > > messages, but my test box doesn't like it at all... Well

Re: new kernel and old programs - bad system call

2003-11-13 Thread Bruce Evans
On Thu, 13 Nov 2003, John Hay wrote: > Is it ok to run a new kernel (after the statfs changes) and older > programs? I thought so from what i gathered out of the commit > messages, but my test box doesn't like it at all... Well except > if something else broke stuff: I have no problems with a cur

Re: New Kernel Breaks IPFW

2003-06-10 Thread Terry Lambert
Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > Ian, > > > > The new ipfw binary will work with an up-to-date kernel. What you need to > > do is boot this new kernel and only then try out the new ipfw binary. > > That doesn't really explain why the new ipfw binary core dumped > with the n

Re: New Kernel Breaks IPFW

2003-06-10 Thread Terry Lambert
Ian Freislich wrote: > Terry Lambert wrote: > > > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought > > > > to fix it. > > > > > > I tried that as well, but the new binary also dumps core, but works > > > well with previous versions of the firewall. Even back as far as > >

Re: New Kernel Breaks IPFW

2003-06-10 Thread John Stockdale
Yep got it all figured out now. I didn't realize that the interface had changed, so I built a new kernel and rebooted before an installworld and ipfw bitched at me. Lesson learnt ;) Thanks for the feedback -John Alas make buildworld fails for the past few days: ===> usr.sbin/config [snip

Re: New Kernel Breaks IPFW

2003-06-10 Thread Fred Souza
> Alas make buildworld fails for the past few days: > ===> usr.sbin/config > [snip] > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought > > to fix it. > > I tried that as well, but the new binary also dumps core, but works > well with previous versions of the firewal

Re: New Kernel Breaks IPFW

2003-06-10 Thread Kenneth Culver
Try rebuilding ipfw. Ken On Mon, 9 Jun 2003, John Stockdale wrote: > Hey everyone, > > I just cvsup'd my src today and was going to buildworld later tonight > but when I installed the newly built kernel with IPFIREWALL etc. and > rebooted, ipfw fell over, specifically, even after ipfw firewall e

Re: New Kernel Breaks IPFW

2003-06-10 Thread Andre Guibert de Bruet
On Tue, 10 Jun 2003, Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > > > The new ipfw binary will work with an up-to-date kernel. What you need to > > do is boot this new kernel and only then try out the new ipfw binary. > > That doesn't really explain why the new ipfw binary core dumped

Re: New Kernel Breaks IPFW

2003-06-10 Thread Ian Freislich
Andre Guibert de Bruet wrote: > Ian, > > The new ipfw binary will work with an up-to-date kernel. What you need to > do is boot this new kernel and only then try out the new ipfw binary. That doesn't really explain why the new ipfw binary core dumped with the new kernel, but worked fine with old

Re: New Kernel Breaks IPFW

2003-06-10 Thread Andre Guibert de Bruet
Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Tue, 10 Jun 20

Re: New Kernel Breaks IPFW

2003-06-10 Thread Ian Freislich
Terry Lambert wrote: > Apparently, someone hosed the compiler flags. Looking at your > cribbed link: > > > Someone posted a link to the failure that I get, so I'll crib: > > http://www.0xfce3.net/error.txt > > We see: > > cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/inclu

Re: New Kernel Breaks IPFW

2003-06-10 Thread Terry Lambert
Ian Freislich wrote: > Alas make buildworld fails for the past few days: > ===> usr.sbin/config > > In file included from config.c:1: > /usr/include/stdlib.h:102: conflicting types for `restrict' > /usr/include/stdlib.h:102: previous declaration of `restrict' > /usr/include/stdlib.h:102: warning:

Re: New Kernel Breaks IPFW

2003-06-10 Thread Ian Freislich
"Daniel C. Sobral" wrote: > John Stockdale wrote: > > Hey everyone, > > > > I just cvsup'd my src today and was going to buildworld later tonight > > but when I installed the newly built kernel with IPFIREWALL etc. and > > rebooted, ipfw fell over, specifically, even after ipfw firewall enable,

Re: New Kernel Breaks IPFW

2003-06-09 Thread Daniel C. Sobral
John Stockdale wrote: Hey everyone, I just cvsup'd my src today and was going to buildworld later tonight but when I installed the newly built kernel with IPFIREWALL etc. and rebooted, ipfw fell over, specifically, even after ipfw firewall enable, an ipfw show resulted in a core dump. If its us

Re: New kernel option GDBSPEED (as in CONSPEED)?

2002-05-27 Thread Bruce Evans
On Mon, 27 May 2002, Nick Hibma wrote: > CONSPEED is used for both console and gdb. This is a bit awkward because > it means that I have to run my kernel console on 9600 baud on my > diskless box. The attached patch fixes this by introducing another > variable GDBSPEED. > > The patch makes the de

Re: New kernel, old boot... problems.

2000-02-06 Thread Daniel C. Sobral
David Gilbert wrote: > > Well... I copied the new(er) versions of the loader from my > workstation to /boot on the laptop and then "disklabel -B wd0" on the > laptop. Is there some other (non-obvious) step required? No, there isn't. The version you want is 0.7. That's the version on FreeBSD 3.

Re: New kernel, old boot... problems.

2000-02-06 Thread David Gilbert
> "Daniel" == Daniel C Sobral <[EMAIL PROTECTED]> writes: Daniel> David Gilbert wrote: >> This is what it says: >> >> /kernel.G4 text=0x1f5482 elf_loadexec: archsw.readin failed can't >> load module '/kernel.G4': input/output error >> >> ... both errors were much the same. Now... I though

Re: New kernel, old boot... problems.

2000-02-06 Thread Daniel C. Sobral
David Gilbert wrote: > > This is what it says: > > /kernel.G4 text=0x1f5482 > elf_loadexec: archsw.readin failed > can't load module '/kernel.G4': input/output error > > ... both errors were much the same. Now... I thought that this might > be that the boot loaders needed to be updated (the on

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-09 Thread Greg Childers
Yes! That is exactly the problem I have been having since the 1999/10/09 12:57:15 PDT ATA commit. Here is the link to the email I sent earlier: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1326170+1331912+/usr/local/www/db/text/1999/freebsd-current/19991212.freebsd-current Basically, on my Pen

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-09 Thread Hans Ottevangerne_anchors
Hi, Before people start wondering about my name being mangled in the From: field of my previous message: Sorry, it happens regularly when cutting and pasting into the mailer of the Netscape Communicator 4.7. Maybe I have to switch to another mailtool... Cheers, Hans To Unsubscribe: send mail

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-09 Thread Hans Ottevangerne_anchors
Matthew Dillon wrote: > > Well guys, I tried upgrading one of my older machines today to the > latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). > [ Detailed description deleted ] > HELP! Whats happening!!! :-( :-( :-( > > At the moment I am stymied. I s

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-07 Thread Hans Ottevanger
Matthew Dillon wrote: > > Well guys, I tried upgrading one of my older machines today to the > latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). > .. > HELP! Whats happening!!! :-( :-( :-( > > At the moment I am stymied. I switched to a GENERIC kernel

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-07 Thread Warner Losh
In message <[EMAIL PROTECTED]> Doug Ambrisko writes: : Tonight I will try to define : ATA_16BIT_ONLY : in my kernel and try to boot with ata. This may have to be set in GENERIC : for installs to work ... or the ata driver learn how to figure this out : automatically on the fly. Look at m

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-07 Thread Matthew Dillon
:Anyways more work and lots of testing needs to be done. Even though I like :the new ata stuff and use it on all machines (except for one) this is scary :since a bunch of 4.0 users could get screwed with older good hardware. : :Tonight I will try to define : ATA_16BIT_ONLY :in my kernel

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-07 Thread Doug Ambrisko
Matthew Dillon writes: | Well guys, I tried upgrading one of my older machines today to the | latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). I ran into a similar problem when upgrading my server at home. It is an old 486 with an Intel Saturn chipset. I found the IDE dri

Re: Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other proble

2000-01-06 Thread Soren Schmidt
It seems Matthew Dillon wrote: > > :From what I can tell so far, something during the kernel boot is > :disabling the timer interrupt. The ATA probe does a tsleep() which > :never times out. Output is queued to the console during the boot > :sequence which is never printed (unti

Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other problems)

2000-01-06 Thread Matthew Dillon
:From what I can tell so far, something during the kernel boot is :disabling the timer interrupt. The ATA probe does a tsleep() which :never times out. Output is queued to the console during the boot :sequence which is never printed (until I CTL-ALT-ESC)... : :has someone m

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-06 Thread Matthew Dillon
: :: * First, it locks up with process 0 stuck in 'atawait' while : : : I meant 'atacmd' here. : : -Matt From what I can tell so far, something

Re: New kernel no longer boots on one of my machines... ata, other problems

2000-01-06 Thread Matthew Dillon
: * First, it locks up with process 0 stuck in 'atawait' while I meant 'atacmd' here. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: new kernel.

1999-11-12 Thread Byung Yang
Ok..in addition to my earlier post, I am NOT using Linux netscape and I built the whole system from the source code. dist/module/kernel they are all from the same source tree. The thing is I never had this kind of problem before. It was working fine then. I built the world/kernel at Tue Nov

Re: new kernel.

1999-11-11 Thread Alfred Perlstein
On Thu, 11 Nov 1999, Byung Yang wrote: > > I supped two days ago and compiled everything. Now, if I try to launch > netscape, the computer just freezes right up there. First, I thought it > was the netscape, but when I was searching for a file on my computer, but > took longer than I thought a

Re: new kernel.

1999-11-11 Thread Wes Morgan
On Thu, 11 Nov 1999, Stephan van Beerschoten wrote: > On Thu, Nov 11, 1999 at 08:36:11AM +, Byung Yang wrote: > > I supped two days ago and compiled everything. Now, if I try to launch > > netscape, the computer just freezes right up there. First, I thought it > > was the netscape, but when

Re: new kernel.

1999-11-11 Thread Stephan van Beerschoten
On Thu, Nov 11, 1999 at 08:36:11AM +, Byung Yang wrote: > I supped two days ago and compiled everything. Now, if I try to launch > netscape, the computer just freezes right up there. First, I thought it > was the netscape, but when I was searching for a file on my computer, but > took longer

Re: new kernel and IPDIVERT

1999-04-19 Thread Peter Wemm
Brian Feldman wrote: > On Mon, 19 Apr 1999, Ilya Naumov wrote: > > > > > i have compiled the latest kernel and encountered a problem with IPDIVERT. even > > with "options IPDIVERT" string in kernel config, kernel says the following: > > > > IP packet filtering initialized, divert disabled,

Re: new kernel and IPDIVERT

1999-04-19 Thread Brian Feldman
On Mon, 19 Apr 1999, Ilya Naumov wrote: > > i have compiled the latest kernel and encountered a problem with IPDIVERT. > even > with "options IPDIVERT" string in kernel config, kernel says the following: > > IP packet filtering initialized, divert disabled, rule-based forwarding > disabled, lo