Re: Kernel compilation error for 7.0 ( with IPSEC )

[Norman Maurer]

Be sure to have this stuff in kernel config file:

options IPSEC
options IPSEC_FILTERTUNNEL
device crypto


Cheers
Norman

Am Montag, den 03.03.2008, 15:15 +0300 schrieb Leonid Satanovsky:
> Hi, people!
> I've just "CvsUP"ed the "src-all" collection for "RELENG_7_0"
> [This is a 7.0-RELEASE, as I understand, am I correct? ]
> 
> trying to compile the source with IPSEC reselts in the following:
> ---   
> <...>
> 
> xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: 
> undefined reference to `M_XDATA'
> xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: 
> undefined reference to `crypto_freereq'
> xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: 
> undefined reference to `M_XDATA'
> xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: 
> undefined reference to `crypto_freereq'
> *** Error code 1
> 
> Stop in /usr/obj/usr/src/sys/TKLGW_7.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> --
> The question: what may be wrong with that?
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel compilation error for 7.0 ( with IPSEC )

[Michael Ross]

Am Mon, 03 Mar 2008 15:15:29 +0300 schrieb Leonid Satanovsky
<[EMAIL PROTECTED]>:

> Hi, people!
> I've just "CvsUP"ed the "src-all" collection for "RELENG_7_0"
> [This is a 7.0-RELEASE, as I understand, am I correct? ]

RELENG_7_0

The release branch for FreeBSD-7.0, used only for security advisories and
other critical fixes.


> trying to compile the source with IPSEC reselts in the following:
> ---   
> <...>
> 
> xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: 
> undefined reference to `M_XDATA'
> xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: 
> undefined reference to `crypto_freereq'
> xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: 
> undefined reference to `M_XDATA'
> xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: 
> undefined reference to `crypto_freereq'
> *** Error code 1
> 
> Stop in /usr/obj/usr/src/sys/TKLGW_7.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> --
> The question: what may be wrong with that?
> 

You are missing "device crypto" in your kernel config.

Michael
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kernel compilation error for 7.0 ( with IPSEC )

[Leonid Satanovsky]

Hi, people!
I've just "CvsUP"ed the "src-all" collection for "RELENG_7_0"
[This is a 7.0-RELEASE, as I understand, am I correct? ]

trying to compile the source with IPSEC reselts in the following:
---   
<...>


xform_ipcomp.o(.text+0xcac):/usr/src/sys/netipsec/xform_ipcomp.c:570: 
undefined reference to `M_XDATA'
xform_ipcomp.o(.text+0xcbc):/usr/src/sys/netipsec/xform_ipcomp.c:571: 
undefined reference to `crypto_freereq'
xform_ipcomp.o(.text+0xda6):/usr/src/sys/netipsec/xform_ipcomp.c:584: 
undefined reference to `M_XDATA'
xform_ipcomp.o(.text+0xdb6):/usr/src/sys/netipsec/xform_ipcomp.c:585: 
undefined reference to `crypto_freereq'

*** Error code 1

Stop in /usr/obj/usr/src/sys/TKLGW_7.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

--
   The question: what may be wrong with that?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compilation fails

[Gelsema, P \(Patrick\) - FreeBSD]

On Sun, July 22, 2007 13:28, Nicolas Haller wrote:
> Hi all,
>
> I have a little problem trying to compile a -CURRENT kernel.
> The compilation fails with this message:
>
> /usr/src/sys/dev/usb/usb_quirks.c:111: error: 'USB_PRODUCT_METAGEEK_WISPY'
> undeclared here (not in a function)

This is known, introduced with commit:
http://lists.freebsd.org/pipermail/cvs-src/2007-July/080810.html

Keep an eye on
http://lists.freebsd.org/pipermail/cvs-src/2007-July/thread.html to see if
it has been fixed. In the mean time you could use a previous version of
the file, you can get this from the cvsweb.

Cheers

Patrick

>
> Config and make depend run succefully but compilation fails (done with
> make buildkernel).
>
> I give you the kernel config file.
>
> cheers,
>
> --
> Nicolas Haller
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

kernel compilation fails

[Nicolas Haller]

Hi all,

I have a little problem trying to compile a -CURRENT kernel.
The compilation fails with this message:

/usr/src/sys/dev/usb/usb_quirks.c:111: error: 'USB_PRODUCT_METAGEEK_WISPY' 
undeclared here (not in a function)

Config and make depend run succefully but compilation fails (done with
make buildkernel).

I give you the kernel config file.

cheers,

-- 
Nicolas Haller
#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.473 2007/07/01 21:47:45 njl Exp $

#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident   NICOLAS

# To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" # Default places to look for devices.

#makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols

options SCHED_4BSD  # 4BSD scheduler
options PREEMPTION  # Enable kernel thread preemption
options INET# InterNETworking
options INET6   # IPv6 communications protocols
#optionsSCTP# Stream Transmission Control Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options UFS_GJOURNAL# Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT   # GUID Partition Tables.
options GEOM_LABEL  # Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time 
extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options STOP_NMI# Stop CPUS using NMI instead of IPI
options AUDIT   # Security event auditing

# Debugging for use in -current
#optionsKDB # Enable kernel debugger support.
#optionsDDB # Support DDB.
#optionsGDB # Support remote GDB.
#optionsINVARIANTS  # Enable calls of extra sanity checking
#optionsINVARIANT_SUPPORT   # Extra sanity checks of internal 
structures, required by INVARIANTS
#optionsWITNESS # Enable checks to detect deadlocks and 
cycles
#optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for 
speed

# To make an SMP kernel, the next two lines are needed
options SMP # Symmetric MultiProcessor Kernel
device  apic# I/O APIC

# CPU frequency control
device  cpufreq

# Bus support.
device  eisa
device  pci

# Floppy drives
#device fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
de

Re: Kernel Compilation...

[Crispy Beef]

Robert Huff wrote:

Nikolas Britton writes:



Still sounds like a hardware problem.



Maybe not.
A couple of years back - in the early days of 4.x - I had a
problem which I /think/ manifested in the manner originally
described.
It turned out to be the script I'd set up to automate this
process - an unnecessary "make depends" IIRC.  It was the same error
every time, but the exact location changed.  Drove me up the wall.
Unless you (generic) really really really know what you're
doing, follow the steps in the Handbook.  They're tested, and they
work.  Including reading /ysr/src/UPDATING.


I've not really done anything special with scripts, just altered make.conf the 
one time to include a few compiler options (-O2 -march=pentium2 -pipe).


The kernel has now compiled a few times with and without the above options.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Still sounds like a hardware problem. Maybe the laptop is overheating,
compiling software is always hard on a system. Also I don't think
Memtest86 will show you anything even if your ram is bad. The best way
to find out is to just change it out if you have extra somewhere or
remove part of it and/or shuffle it around.

Check for thermal issues, maybe build the kernel with the laptop in
the refrigerator or something :-). If you do something like that make
sure you don't get condensation buildup when you take it out of the
cold and into the warm... but the humidity is always low in the winter
so it shouldn't be to much of a problem.




One more thing. You said this was an older laptop (400ish MHz) right?
If so you better double check that ACPI is working and that the
thermal trip points are set correctly. I had a major problem with an
Armada 1750 ([EMAIL PROTECTED] i440BX) in that ACPI was totally broken.
FreeBSD 5.x would never trip the fans on. The system hit would 100C
(212F) and then FreeBSD would auto shutdown the system. I sold the
laptop after I found that out and bought a better one, an Omnibook
6000 ([EMAIL PROTECTED] with 440BX). I still had major problems with ACPI so
I decide to just install SuSE 9.3 Pro on it. SuSE worked perfect.


466MHz P2 Celeron with 128Mb RAM on an i440BX mobo.  The system won't boot 
unless it's with ACPI enabled, just panics during start-up.




FreeBSD's ACPI implementation and laptops with i440BX/MX or earlier
chipsets don't mix well. sysctl will help you with the thermal
settings and http://acpi.sourceforge.net/ will help if you need a new
DSDT. this will help some too:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html


Actually thinking about it now I've got this system running you could be 
right, since then I've had to get my PCMCIA network card running properly, 
whenever it gets plugged in the kernel panics, did some research and found 
that by putting debug.acpi.disabled="sysresource" into the /boot/loader.conf 
file that it works just fine, so as you say there definitely seems to be some 
issues with ACPI.


You can hear the CPU fan wind up and down while the system is running, that's 
something I don't remember from having Gentoo compiling...that always worked 
just fine, so it could well be a heat issue.  The chipset on the laptop is an 
Intel i440BX jobbie.


Will look into the thermal thing now, cheers.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Nikolas Britton]

On 1/4/06, Nikolas Britton <[EMAIL PROTECTED]> wrote:
> On 1/4/06, Crispy Beef <[EMAIL PROTECTED]> wrote:
> > Nikolas Britton wrote:
> > > To rule out hardware problems rebuild the generic kernel using the
> > > virgin GENERIC kernel config file:
> > >
> > > 0. If you've messed with /etc/make.conf change it back to the defaults!
> > > 1. su
> > > 2. cd /usr/src/sys/i386/conf
> > > 3. rm -r ../compile/GENERIC
> > > 4. config GENERIC
> > > 5. cd ../compile/GENERIC
> > > 6. make depend
> > > 7. make
> > > 8. make install
> > > 9. reboot
> > >
> > > If you can't get to step 8 you have a hardware problem (or FreeBSD
> > > wasn't installed correctly, see step 5 below):
> >
> > First time I tried this I had another seg fault (error 11) so did a complete
> > install from the CD again (kernel developer options).  It failed once during
> > that compile, then the second time it worked just fine.  I then did my own
> > config cutting out all the stuff I don't need and it's compiled just fine.
> > Strange...
> >
> > Thinking about it, this is the only time I've got the sources from the CD.  
> > I
> > always grabbed them from an ftpe server via sysinstall, maybe the newer
> > sources were causing problems like the guys mentioned earlier?
> >
> > Got a version of MemTest86 running too and that went for a couple of hours
> > without any errors showing up, will run it overnight to be sure.
> >
> > I guess the next thing is to have a go at make buildworld with options in
> > make.conf and see if it barfs then.
> >
> > Thanks for the help. :-)
> >
> > Paul
> >
>
> Still sounds like a hardware problem. Maybe the laptop is overheating,
> compiling software is always hard on a system. Also I don't think
> Memtest86 will show you anything even if your ram is bad. The best way
> to find out is to just change it out if you have extra somewhere or
> remove part of it and/or shuffle it around.
>
> Check for thermal issues, maybe build the kernel with the laptop in
> the refrigerator or something :-). If you do something like that make
> sure you don't get condensation buildup when you take it out of the
> cold and into the warm... but the humidity is always low in the winter
> so it shouldn't be to much of a problem.
>

One more thing. You said this was an older laptop (400ish MHz) right?
If so you better double check that ACPI is working and that the
thermal trip points are set correctly. I had a major problem with an
Armada 1750 ([EMAIL PROTECTED] i440BX) in that ACPI was totally broken.
FreeBSD 5.x would never trip the fans on. The system hit would 100C
(212F) and then FreeBSD would auto shutdown the system. I sold the
laptop after I found that out and bought a better one, an Omnibook
6000 ([EMAIL PROTECTED] with 440BX). I still had major problems with ACPI so
I decide to just install SuSE 9.3 Pro on it. SuSE worked perfect.

FreeBSD's ACPI implementation and laptops with i440BX/MX or earlier
chipsets don't mix well. sysctl will help you with the thermal
settings and http://acpi.sourceforge.net/ will help if you need a new
DSDT. this will help some too:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Robert Huff]

Nikolas Britton writes:

>  Still sounds like a hardware problem.

Maybe not.
A couple of years back - in the early days of 4.x - I had a
problem which I /think/ manifested in the manner originally
described.
It turned out to be the script I'd set up to automate this
process - an unnecessary "make depends" IIRC.  It was the same error
every time, but the exact location changed.  Drove me up the wall.
Unless you (generic) really really really know what you're
doing, follow the steps in the Handbook.  They're tested, and they
work.  Including reading /ysr/src/UPDATING.


Robert Huff



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Nikolas Britton]

On 1/4/06, Crispy Beef <[EMAIL PROTECTED]> wrote:
> Nikolas Britton wrote:
> > To rule out hardware problems rebuild the generic kernel using the
> > virgin GENERIC kernel config file:
> >
> > 0. If you've messed with /etc/make.conf change it back to the defaults!
> > 1. su
> > 2. cd /usr/src/sys/i386/conf
> > 3. rm -r ../compile/GENERIC
> > 4. config GENERIC
> > 5. cd ../compile/GENERIC
> > 6. make depend
> > 7. make
> > 8. make install
> > 9. reboot
> >
> > If you can't get to step 8 you have a hardware problem (or FreeBSD
> > wasn't installed correctly, see step 5 below):
>
> First time I tried this I had another seg fault (error 11) so did a complete
> install from the CD again (kernel developer options).  It failed once during
> that compile, then the second time it worked just fine.  I then did my own
> config cutting out all the stuff I don't need and it's compiled just fine.
> Strange...
>
> Thinking about it, this is the only time I've got the sources from the CD.  I
> always grabbed them from an ftpe server via sysinstall, maybe the newer
> sources were causing problems like the guys mentioned earlier?
>
> Got a version of MemTest86 running too and that went for a couple of hours
> without any errors showing up, will run it overnight to be sure.
>
> I guess the next thing is to have a go at make buildworld with options in
> make.conf and see if it barfs then.
>
> Thanks for the help. :-)
>
> Paul
>

Still sounds like a hardware problem. Maybe the laptop is overheating,
compiling software is always hard on a system. Also I don't think
Memtest86 will show you anything even if your ram is bad. The best way
to find out is to just change it out if you have extra somewhere or
remove part of it and/or shuffle it around.

Check for thermal issues, maybe build the kernel with the laptop in
the refrigerator or something :-). If you do something like that make
sure you don't get condensation buildup when you take it out of the
cold and into the warm... but the humidity is always low in the winter
so it shouldn't be to much of a problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Nikolas Britton wrote:

To rule out hardware problems rebuild the generic kernel using the
virgin GENERIC kernel config file:

0. If you've messed with /etc/make.conf change it back to the defaults!
1. su
2. cd /usr/src/sys/i386/conf
3. rm -r ../compile/GENERIC
4. config GENERIC
5. cd ../compile/GENERIC
6. make depend
7. make
8. make install
9. reboot

If you can't get to step 8 you have a hardware problem (or FreeBSD
wasn't installed correctly, see step 5 below):


First time I tried this I had another seg fault (error 11) so did a complete 
install from the CD again (kernel developer options).  It failed once during 
that compile, then the second time it worked just fine.  I then did my own 
config cutting out all the stuff I don't need and it's compiled just fine. 
Strange...


Thinking about it, this is the only time I've got the sources from the CD.  I 
always grabbed them from an ftpe server via sysinstall, maybe the newer 
sources were causing problems like the guys mentioned earlier?


Got a version of MemTest86 running too and that went for a couple of hours 
without any errors showing up, will run it overnight to be sure.


I guess the next thing is to have a go at make buildworld with options in 
make.conf and see if it barfs then.


Thanks for the help. :-)

Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Nikolas Britton wrote:

On 1/3/06, Crispy Beef <[EMAIL PROTECTED]> wrote:


Jonathan Chen wrote:


On Mon, Jan 02, 2006 at 04:15:48PM +, Crispy Beef wrote:



Hi All,

Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE,
so a while ago now.  I have just installed 6.0-RELEASE on my old laptop and
have been configuring the system, am onto the kernel at the moment, have
followed the traditional method in the FreeBSD handbook.  All works fine
(make depends) until I do 'make' then I get a compilation error as follows:


/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
internal compiler error: Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.



Internal compiler errors usually indicate faulty memory. If you rerun
your compilation and it fails in the same spot, then it could be
software. If the compilations fails in a different area, you've
probably got faulty hardward.


It's looking very much like faulty hardware at the moment...bit of a shame
really.  Have used Gentoo Linux on this machine before (compiling from source)
and that's always worked just fine, I only ditched it a couple of weeks ago to
have a play with FreeBSD again.

Also tried the memtest86 util from a floppy, that doesn't even boot properly
so looks like it might be a no go.  :-/




To rule out hardware problems rebuild the generic kernel using the
virgin GENERIC kernel config file:

0. If you've messed with /etc/make.conf change it back to the defaults!
1. su
2. cd /usr/src/sys/i386/conf
3. rm -r ../compile/GENERIC
4. config GENERIC
5. cd ../compile/GENERIC
6. make depend
7. make
8. make install
9. reboot

If you can't get to step 8 you have a hardware problem (or FreeBSD
wasn't installed correctly, see step 5 below):

(Very Basic/Limited Flow chart)

1. Go into the BIOS and reset everything to their safety defaults
etc., repeat generic kernel build and if it's successful...

2. Pull the Mem, Hard drive, etc. clean/dust/etc. Reinsert etc.,
repeat generic kernel build and if it's successful...

3. Sub Out/Replace Memory, repeat generic kernel build...

4. Wipe (zero out) Hard Drive and Reinstall a virgin copy of FreeBSD 6 from CD:
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.0/6.0-RELEASE-i386-disc1.iso
MD5 (6.0-RELEASE-i386-disc1.iso) = cfe3c1a2b4991edd6a294ca9b422b9d5
Check the MD5 hash before you burn the disc and verify the disc after
it's burned. Hit "A" then "Q" for FDISK and Disklabel and Install only
the "Kern-Developer" Distribution set, don't install the ports system.
repeat generic kernel build...  Oh... and run a defective sector scan
of the hard drive using the diag disk that came with it, you can find
the zero out and diag software on the UBCD CD link below.

5. If you've done steps 1 - 4 and still can't build the kernel your
system is broke, I'll take it off your hands if you'd like. :-)
Also... you may want to start with step 4 then do 1, 2, and 3.


Thanks for all the tips, am trying to compile the GENERIC kernel as I type 
this so will see what happens there, I had tried my own kernel config with and 
without a few settings in make.conf but it's reset back to what it was at the 
moment.


Have also located the final version of BIOS so will flash that too to see if 
it helps with anything.


Will let you know how it goes.

Cheers.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Nikolas Britton]

On 1/3/06, Crispy Beef <[EMAIL PROTECTED]> wrote:
> Jonathan Chen wrote:
> > On Mon, Jan 02, 2006 at 04:15:48PM +, Crispy Beef wrote:
> >
> >>Hi All,
> >>
> >>Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE,
> >>so a while ago now.  I have just installed 6.0-RELEASE on my old laptop and
> >>have been configuring the system, am onto the kernel at the moment, have
> >>followed the traditional method in the FreeBSD handbook.  All works fine
> >>(make depends) until I do 'make' then I get a compilation error as follows:
> >>
> >>
> >>/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> >>internal compiler error: Segmentation fault: 11
> >>Please submit a full bug report,
> >>with preprocessed source if appropriate.
> >
> >
> > Internal compiler errors usually indicate faulty memory. If you rerun
> > your compilation and it fails in the same spot, then it could be
> > software. If the compilations fails in a different area, you've
> > probably got faulty hardward.
>
> It's looking very much like faulty hardware at the moment...bit of a shame
> really.  Have used Gentoo Linux on this machine before (compiling from source)
> and that's always worked just fine, I only ditched it a couple of weeks ago to
> have a play with FreeBSD again.
>
> Also tried the memtest86 util from a floppy, that doesn't even boot properly
> so looks like it might be a no go.  :-/
>

To rule out hardware problems rebuild the generic kernel using the
virgin GENERIC kernel config file:

0. If you've messed with /etc/make.conf change it back to the defaults!
1. su
2. cd /usr/src/sys/i386/conf
3. rm -r ../compile/GENERIC
4. config GENERIC
5. cd ../compile/GENERIC
6. make depend
7. make
8. make install
9. reboot

If you can't get to step 8 you have a hardware problem (or FreeBSD
wasn't installed correctly, see step 5 below):

(Very Basic/Limited Flow chart)

1. Go into the BIOS and reset everything to their safety defaults
etc., repeat generic kernel build and if it's successful...

2. Pull the Mem, Hard drive, etc. clean/dust/etc. Reinsert etc.,
repeat generic kernel build and if it's successful...

3. Sub Out/Replace Memory, repeat generic kernel build...

4. Wipe (zero out) Hard Drive and Reinstall a virgin copy of FreeBSD 6 from CD:
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.0/6.0-RELEASE-i386-disc1.iso
MD5 (6.0-RELEASE-i386-disc1.iso) = cfe3c1a2b4991edd6a294ca9b422b9d5
Check the MD5 hash before you burn the disc and verify the disc after
it's burned. Hit "A" then "Q" for FDISK and Disklabel and Install only
the "Kern-Developer" Distribution set, don't install the ports system.
repeat generic kernel build...  Oh... and run a defective sector scan
of the hard drive using the diag disk that came with it, you can find
the zero out and diag software on the UBCD CD link below.

5. If you've done steps 1 - 4 and still can't build the kernel your
system is broke, I'll take it off your hands if you'd like. :-)
Also... you may want to start with step 4 then do 1, 2, and 3.

http://www.ultimatebootcd.com/
http://www.ultimatebootcd.com/download.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Jonathan Chen wrote:

On Mon, Jan 02, 2006 at 04:15:48PM +, Crispy Beef wrote:


Hi All,

Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, 
so a while ago now.  I have just installed 6.0-RELEASE on my old laptop and 
have been configuring the system, am onto the kernel at the moment, have 
followed the traditional method in the FreeBSD handbook.  All works fine 
(make depends) until I do 'make' then I get a compilation error as follows:



/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
internal compiler error: Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.



Internal compiler errors usually indicate faulty memory. If you rerun
your compilation and it fails in the same spot, then it could be
software. If the compilations fails in a different area, you've
probably got faulty hardward.


It's looking very much like faulty hardware at the moment...bit of a shame 
really.  Have used Gentoo Linux on this machine before (compiling from source) 
and that's always worked just fine, I only ditched it a couple of weeks ago to 
have a play with FreeBSD again.


Also tried the memtest86 util from a floppy, that doesn't even boot properly 
so looks like it might be a no go.  :-/


Cheers.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Robert Huff wrote:

Crispy Beef writes:



I wasn't aware that I needed to do a buildworld too, am limited
on the amount of disk space I have, the whole disk is 6Gb with a
1Gb /home and over 3Gb /usr.  Is that going to be enough?



1) It is _very_ important to keep the kernel and userland in
sync.
	2) 


huff@>> du -s /usr/src
442996  /usr/src

As a ball-park estimate, figure 1Gb when you need to update.
Assuming you have a high-speed connection, I would rebuild
world and kernel per the handbook.  After installing and testing the
new system I would save the kernel config file elsewhere and delete
/usr/src and /usr/obj.  THe next time you need to rebuild you'll
need to clear the disk and download the entire source tree, but
you'll have the disk available until then.


Basically I had just installed 6.0-RELEASE from the CD, got the kernel sources 
 from an ftp server (using sysinstall) and then proceded to build the kernel 
as I mentioned in another post (traditional method).  Basically you're saying 
I should grab the entire source tree and then build everything before the 
kernel?  Just checking before I go ahead...having said that as it's a clean 
install there's nothing too vital on the system so won't matter to much if I 
trash it.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Jonathan Chen]

On Mon, Jan 02, 2006 at 04:15:48PM +, Crispy Beef wrote:
> Hi All,
> 
> Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, 
> so a while ago now.  I have just installed 6.0-RELEASE on my old laptop and 
> have been configuring the system, am onto the kernel at the moment, have 
> followed the traditional method in the FreeBSD handbook.  All works fine 
> (make depends) until I do 'make' then I get a compilation error as follows:
> 
> 
> /usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.

Internal compiler errors usually indicate faulty memory. If you rerun
your compilation and it fails in the same spot, then it could be
software. If the compilations fails in a different area, you've
probably got faulty hardward.
-- 
Jonathan Chen <[EMAIL PROTECTED]>
--
  "Opportunity does not knock,
   it presents itself when you beat down the door" - W.E. Channing
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Robert Huff]

Crispy Beef writes:

>  I wasn't aware that I needed to do a buildworld too, am limited
>  on the amount of disk space I have, the whole disk is 6Gb with a
>  1Gb /home and over 3Gb /usr.  Is that going to be enough?

1) It is _very_ important to keep the kernel and userland in
sync.
2) 

huff@>> du -s /usr/src
442996  /usr/src

As a ball-park estimate, figure 1Gb when you need to update.
Assuming you have a high-speed connection, I would rebuild
world and kernel per the handbook.  After installing and testing the
new system I would save the kernel config file elsewhere and delete
/usr/src and /usr/obj.  THe next time you need to rebuild you'll
need to clear the disk and download the entire source tree, but
you'll have the disk available until then.


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Adam Nealis]

--- Crispy Beef <[EMAIL PROTECTED]> wrote:

> Adam Nealis wrote:
> 
> *snip*
> 
> >>
> >>Here's what I did:
> >>
> >>1.Install from CD (6.0-RELEASE)
> >>2.Got latest kernel src with sysinstall
> > 
> > 
> > Hmm. cvsup might be better. Having said that, when I cvsup'd 6.0-RELEASE
> > after installing from CD, there were only one or two files updated. But
> > my version went from 6.0-RELEASE to 6.0-RELEASE-p1.
> > 
> > The other thing is you don't appear to have run buildworld. This step
> > uses the 6.0-RELEASE source in /usr/src to build userland and gcc and
> > so on. I'm not sure, but I think you have to use the compilation tools
> > from buildworld to create your new kernel.
> 
> I wasn't aware that I needed to do a buildworld too, am limited on the amount 
> of disk space I have, the whole disk is 6Gb with a 1Gb /home and over 3Gb 
> /usr.  Is that going to be enough?  /tmp and /var are quite small.

All the stuff is built in /usr/obj. On my system, the 6.0-STABLE build
I did yesterday looks like this:

{frank:adam:~} df /usr/obj/
Filesystem  1K-blocks   Used Avail Capacity  Mounted on
/dev/da0s2e507630 405354 6166687%/usr/obj

However, I have trimmed some stuff from userland and the kernel. With 3GB
free in /usr you should have plenty of space.

> Will go through the Makefile and see what happens this time round.

Good luck!




__ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Adam Nealis wrote:

*snip*



Here's what I did:

1.Install from CD (6.0-RELEASE)
2.Got latest kernel src with sysinstall



Hmm. cvsup might be better. Having said that, when I cvsup'd 6.0-RELEASE
after installing from CD, there were only one or two files updated. But
my version went from 6.0-RELEASE to 6.0-RELEASE-p1.

The other thing is you don't appear to have run buildworld. This step
uses the 6.0-RELEASE source in /usr/src to build userland and gcc and
so on. I'm not sure, but I think you have to use the compilation tools
from buildworld to create your new kernel.


I wasn't aware that I needed to do a buildworld too, am limited on the amount 
of disk space I have, the whole disk is 6Gb with a 1Gb /home and over 3Gb 
/usr.  Is that going to be enough?  /tmp and /var are quite small.


Will go through the Makefile and see what happens this time round.





3.cd /usr/src/sys/i386/conf
4.Created my own config file (LAPTOP)
5.Did a /usr/sbin/config LAPTOP
6.Moved into compile directory (/usr/src/sys/i386/compile/LAPTOP)
7.Did 'make depend'



Did you do

make cleandepend; make depend ?


Yes, did that too.





8.make

At this point it failed...



I'd be inclined to start from the beginning, going through the steps
given in usr/src/Makefile


Will do, cheers.

Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Adam Nealis]

--- Crispy Beef <[EMAIL PROTECTED]> wrote:
> 
> Adam Nealis wrote:
> > --- Crispy Beef <[EMAIL PROTECTED]> wrote:
> > 
> > 
> >>Hi All,
> >>
> >>Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, 
> >>so 
> >>a while ago now.  I have just installed 6.0-RELEASE on my old laptop and 
> >>have 
> >>been configuring the system, am onto the kernel at the moment, have 
> >>followed 
> >>the traditional method in the FreeBSD handbook.  All works fine (make 
> >>depends) 
> > 
> > 
> > Yesterday I installed 6.0-RELEASE from ISO, then used cvsup to upgrade
> > to 6.0-STABLE. I followed the steps given in /usr/src/Makefile:
> > 
> > 1.  `cd /usr/src'   (or to the directory containing your source tree).
> > 2.  `make buildworld'
> > 3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
> > 4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
> > 5.  `reboot'(in single user mode: boot -s from the loader prompt).
> > 6.  `mergemaster -p'
> > 7.  `make installworld'
> > 8.  `mergemaster'
> > 9.  `reboot'
> > 
> > Is this what you did? Can youprovide the precise steps you followed?
> > 
> > 
> 
> Here's what I did:
> 
> 1.Install from CD (6.0-RELEASE)
> 2.Got latest kernel src with sysinstall

Hmm. cvsup might be better. Having said that, when I cvsup'd 6.0-RELEASE
after installing from CD, there were only one or two files updated. But
my version went from 6.0-RELEASE to 6.0-RELEASE-p1.

The other thing is you don't appear to have run buildworld. This step
uses the 6.0-RELEASE source in /usr/src to build userland and gcc and
so on. I'm not sure, but I think you have to use the compilation tools
from buildworld to create your new kernel.

> 3.cd /usr/src/sys/i386/conf
> 4.Created my own config file (LAPTOP)
> 5.Did a /usr/sbin/config LAPTOP
> 6.Moved into compile directory (/usr/src/sys/i386/compile/LAPTOP)
> 7.Did 'make depend'

Did you do

make cleandepend; make depend ?

> 8.make
> 
> At this point it failed...

I'd be inclined to start from the beginning, going through the steps
given in usr/src/Makefile

> This machine has run Linux for the past few months compiling various things.

Cheers,
Adam.




__ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Adam Nealis wrote:

--- Crispy Beef <[EMAIL PROTECTED]> wrote:



Hi All,

Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, so 
a while ago now.  I have just installed 6.0-RELEASE on my old laptop and have 
been configuring the system, am onto the kernel at the moment, have followed 
the traditional method in the FreeBSD handbook.  All works fine (make depends) 



Yesterday I installed 6.0-RELEASE from ISO, then used cvsup to upgrade
to 6.0-STABLE. I followed the steps given in /usr/src/Makefile:

1.  `cd /usr/src'   (or to the directory containing your source tree).
2.  `make buildworld'
3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
5.  `reboot'(in single user mode: boot -s from the loader prompt).
6.  `mergemaster -p'
7.  `make installworld'
8.  `mergemaster'
9.  `reboot'

Is this what you did? Can youprovide the precise steps you followed?




Here's what I did:

1.Install from CD (6.0-RELEASE)
2.Got latest kernel src with sysinstall
3.cd /usr/src/sys/i386/conf
4.Created my own config file (LAPTOP)
5.Did a /usr/sbin/config LAPTOP
6.Moved into compile directory (/usr/src/sys/i386/compile/LAPTOP)
7.Did 'make depend'
8.make

At this point it failed...

This machine has run Linux for the past few months compiling various things.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[luke]

signal 11 usually indicates hardware failure, which i suppose is what the
link pasted explained. the problem is not the way in which you're compiling
the kernel. run diagnostics on your hardware.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Crispy Beef]

Robert Slade wrote:

On Mon, 2006-01-02 at 16:15, Crispy Beef wrote:


Hi All,

Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, so 
a while ago now.  I have just installed 6.0-RELEASE on my old laptop and have 
been configuring the system, am onto the kernel at the moment, have followed 
the traditional method in the FreeBSD handbook.  All works fine (make depends) 
until I do 'make' then I get a compilation error as follows:



/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
internal compiler error: Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
*** Error code 1

Stop in /usr/src/sys/modules/ata/atapci.
*** Error code 1

Stop in /usr/src/sys/modules/ata.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/i386/compile/LAPTOP.


Last time I had an error with USB Mass Storage do I disabled it in my config 
hoping the kernel would compile, am starting to think this is something a bit 
more serious.


Any thoughts?

--
Paul



Paul,

Welcome.

If you will take some advise from a 'newbe' I suggest that you use the
new method - I have done a kernel compile quite a few times with no
problems using it.

The only time I had problems with compiling was when I got the config
file wrong. I did find that after a failed compile I needed to clear out
the old obj libraries before trying again.

Rob


Will take advice from anybody. :-)

Whenever I have a failed compile I generally do a 'make cleandepends' and make 
clean first just to make sure it's all going from scratch.  Might try the new 
method later and see if that gives me better results.


Cheers.

Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Adam Nealis]

--- Crispy Beef <[EMAIL PROTECTED]> wrote:

> Hi All,
> 
> Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, so 
> a while ago now.  I have just installed 6.0-RELEASE on my old laptop and have 
> been configuring the system, am onto the kernel at the moment, have followed 
> the traditional method in the FreeBSD handbook.  All works fine (make 
> depends) 

Yesterday I installed 6.0-RELEASE from ISO, then used cvsup to upgrade
to 6.0-STABLE. I followed the steps given in /usr/src/Makefile:

1.  `cd /usr/src'   (or to the directory containing your source tree).
2.  `make buildworld'
3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
5.  `reboot'(in single user mode: boot -s from the loader prompt).
6.  `mergemaster -p'
7.  `make installworld'
8.  `mergemaster'
9.  `reboot'

Is this what you did? Can youprovide the precise steps you followed?

> until I do 'make' then I get a compilation error as follows:
> 
> 
> /usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata/atapci.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules.
> *** Error code 1
> 
> Stop in /usr/src/sys/i386/compile/LAPTOP.
> 
> 
> Last time I had an error with USB Mass Storage do I disabled it in my config 
> hoping the kernel would compile, am starting to think this is something a bit 
> more serious.
> 
> Any thoughts?
> 
> --
> Paul
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 




__ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Robert Slade]

On Mon, 2006-01-02 at 16:15, Crispy Beef wrote:
> Hi All,
> 
> Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, so 
> a while ago now.  I have just installed 6.0-RELEASE on my old laptop and have 
> been configuring the system, am onto the kernel at the moment, have followed 
> the traditional method in the FreeBSD handbook.  All works fine (make 
> depends) 
> until I do 'make' then I get a compilation error as follows:
> 
> 
> /usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata/atapci.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules.
> *** Error code 1
> 
> Stop in /usr/src/sys/i386/compile/LAPTOP.
> 
> 
> Last time I had an error with USB Mass Storage do I disabled it in my config 
> hoping the kernel would compile, am starting to think this is something a bit 
> more serious.
> 
> Any thoughts?
> 
> --
> Paul

Paul,

Welcome.

If you will take some advise from a 'newbe' I suggest that you use the
new method - I have done a kernel compile quite a few times with no
problems using it.

The only time I had problems with compiling was when I got the config
file wrong. I did find that after a failed compile I needed to clear out
the old obj libraries before trying again.

Rob

 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation...

[Peter]

--- Crispy Beef <[EMAIL PROTECTED]> wrote:

> Hi All,
> 
> Just joined this list.  The last time I used FreeBSD was with
> 4.6-RELEASE, so 
> a while ago now.  I have just installed 6.0-RELEASE on my old laptop and
> have 
> been configuring the system, am onto the kernel at the moment, have
> followed 
> the traditional method in the FreeBSD handbook.  All works fine (make
> depends) 
> until I do 'make' then I get a compilation error as follows:
> 
> 
> /usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata/atapci.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules/ata.
> *** Error code 1
> 
> Stop in /usr/src/sys/modules.
> *** Error code 1
> 
> Stop in /usr/src/sys/i386/compile/LAPTOP.
> 
> 
> Last time I had an error with USB Mass Storage do I disabled it in my
> config 
> hoping the kernel would compile, am starting to think this is something
> a bit 
> more serious.

http://www.bitwizard.nl/sig11/






__ 
Find your next car at http://autos.yahoo.ca
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kernel Compilation...

[Crispy Beef]

Hi All,

Just joined this list.  The last time I used FreeBSD was with 4.6-RELEASE, so 
a while ago now.  I have just installed 6.0-RELEASE on my old laptop and have 
been configuring the system, am onto the kernel at the moment, have followed 
the traditional method in the FreeBSD handbook.  All works fine (make depends) 
until I do 'make' then I get a compilation error as follows:



/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
internal compiler error: Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
*** Error code 1

Stop in /usr/src/sys/modules/ata/atapci.
*** Error code 1

Stop in /usr/src/sys/modules/ata.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/i386/compile/LAPTOP.


Last time I had an error with USB Mass Storage do I disabled it in my config 
hoping the kernel would compile, am starting to think this is something a bit 
more serious.


Any thoughts?

--
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kernel compilation failed in 5.3-RELEASE

[Robert Kot]

Hi Don,

>Hi Jarek,
>
> I noticed the original post was signed Robert, are there two people 
> working on this or is Jarek another name you go by? Just curious.

Sorry for the confusion, my coworker finished and sent the message
I started :)

> First Advice: don't make changes to /usr/src/sys/i386/conf/GENERIC. 
> Copy GENERIC to some other name and make the changes there.

That's obvious. I did it this way. 

> Second Advice: read /usr/src/UPDATING - you may already know this, 
> but... - start with the "COMMON ITEMS" section, found towards the 
> end. Then work your way backwards from the beginning. 
> Also, look at /usr/src/share/examples/etc/make.conf 
> or /usr/share/examples/etc/make.conf

> Third Advice: there are too many other places to look for 
> information to list. Handbook, FAQ, Release Notes, Errata, 
> Installation Guide, Hardware Notes, Installation Notes, Migration 
> Guide, etc.

> Your first questions: Sure, it does, if you use it as is. You're 
> making changes and there are things you need to do in order for 
> those changes to work. 

> Second Question: recvsup should probably be re-cvsup, this supposes 
> that you did a cvsup of your sources to begin with and something 
> was wrong with it. So, do you have cvsup installed? Do you know how 
> to use it? Do you know about supfiles and what should be in one?

> I think you need to cvsup your sources and go through the full 
> buildworld sequence. I think you're trying to short cut and it's 
> biting you in the butt right now.

> Everyone was a beginner at some time. 

I will try to check if this file splash_bmp.c isn't corrupted.
John Murphy wrote he was able to build kernel with my
configuration, so it's probably some my local problem, perhaps 
indeed with file corruption ? If it fails, I will follow your advices.

Thanks a lot,
Robert
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Kernel compilation failed in 5.3-RELEASE

[Subhro]

-Original Message-
From: Robert Kot [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 14, 2004 16:22
To: Subhro
Cc: [EMAIL PROTECTED]
Subject: Re: Kernel compilation failed in 5.3-RELEASE

>
> Recvsup and rebuild. Did you change anything in /etc/make.conf?
>

No, absolutely not. This is my /etc/make.conf:

# -- use.perl generated deltas -- #
# Created: Wed Nov 10 22:37:45 2004
# Setting to use base perl from ports:
PERL_VER=5.8.5
PERL_VERSION=5.8.5
PERL_ARCH=mach
NOPERL=yo
NO_PERL=yo
NO_PERL_WRAPPER=yo

Isn't it supposed to work out of the box ? I had
no such problems with 5.1 and 5.2. 

Yes it DOES compile out of the box.

How can I do recvsup ? Sorry for the stupid question,
I'm still a beginner. 

Refer to the section of handbook which refers to the "Keeping tree in sync"

Regards
S.
 
Subhro Sankha Kar
Block AQ-13/1, Sector V
Salt Lake City
PIN 700091
India


smime.p7s
Description: S/MIME cryptographic signature

RE: Kernel compilation failed in 5.3-RELEASE

[Subhro]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Murphy
Sent: Sunday, November 14, 2004 20:44
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Kernel compilation failed in 5.3-RELEASE



>How can I do recvsup ? Sorry for the stupid question,
>I'm still a beginner. 

There should be no need unless you want to track STABLE.

I beg to differ. Regular cvsups are absolutely required *even* if someone
tracks RELEASE as cvsups get important security patches which are referred
to as patchlevels and indicated as x.x-RELEASE-py (ex. 5.2.1-RELEASE-p9).

Regards
S. 

Subhro Sankha Kar
Block AQ-13/1, Sector V
Salt Lake City
PIN 700091
India


smime.p7s
Description: S/MIME cryptographic signature

Re: Kernel compilation failed in 5.3-RELEASE

[John Murphy]

Robert Kot wrote (quoting Subhro):

>> Recvsup and rebuild. Did you change anything in /etc/make.conf?
>>
>
>No, absolutely not. This is my /etc/make.conf:
>
># -- use.perl generated deltas -- #
># Created: Wed Nov 10 22:37:45 2004
># Setting to use base perl from ports:
>PERL_VER=5.8.5
>PERL_VERSION=5.8.5
>PERL_ARCH=mach
>NOPERL=yo
>NO_PERL=yo
>NO_PERL_WRAPPER=yo
>
>Isn't it supposed to work out of the box ?

It does! I've just compiled a kernel based on GENERIC with these
changes and it compiles without problem:
#cpu  I486_CPU
#cpu  I586_CPU
cpu  I686_CPU

options  EXT2FS
options  IPFIREWALL
options  IPFIREWALL_VERBOSE
options  IPFIREWALL_DEFAULT_TO_ACCEPT
options  MAC
options  GEOM_BDE
device  sound

One of the error messages you saw said:
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60:
error: syntax error before "mod"

Perhaps that file got corrupted somehow.  You could delete the
/usr/src/sys directory (after backing up your config file) and
re-install the sys source from CD.  You could compare it with
its CVS Log entries if you can find them, it has moved but there
are traces at:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/splash/bmp/Attic/splash_bmp.c

Or you could simply manage without splash screens for now by
commenting out the device splash line in your kernel config.

>How can I do recvsup ? Sorry for the stupid question,
>I'm still a beginner. 

There should be no need unless you want to track STABLE.

-- 
John.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel compilation failed in 5.3-RELEASE

[Donald J. O'Neill]

On Sunday 14 November 2004 04:52 am, Robert Kot wrote:
> > Recvsup and rebuild. Did you change anything in /etc/make.conf?
>
> No, absolutely not. This is my /etc/make.conf:
>
> # -- use.perl generated deltas -- #
> # Created: Wed Nov 10 22:37:45 2004
> # Setting to use base perl from ports:
> PERL_VER=5.8.5
> PERL_VERSION=5.8.5
> PERL_ARCH=mach
> NOPERL=yo
> NO_PERL=yo
> NO_PERL_WRAPPER=yo
>
> Isn't it supposed to work out of the box ? I had
> no such problems with 5.1 and 5.2. Since 5.3 is
> a production release, I'm quite surprised by such
> problems with kernel recompilation, unless I screwed
> something up.
>
> How can I do recvsup ? Sorry for the stupid question,
> I'm still a beginner.
>
> Regards,
> Jarek
> ___
Hi Jarek,

I noticed the original post was signed Robert, are there two people 
working on this or is Jarek another name you go by? Just curious.

First Advice: don't make changes to /usr/src/sys/i386/conf/GENERIC. 
Copy GENERIC to some other name and make the changes there.

Second Advice: read /usr/src/UPDATING - you may already know this, 
but... - start with the "COMMON ITEMS" section, found towards the 
end. Then work your way backwards from the beginning. 
Also, look at /usr/src/share/examples/etc/make.conf 
or /usr/share/examples/etc/make.conf

Third Advice: there are too many other places to look for 
information to list. Handbook, FAQ, Release Notes, Errata, 
Installation Guide, Hardware Notes, Installation Notes, Migration 
Guide, etc.

Your first questions: Sure, it does, if you use it as is. You're 
making changes and there are things you need to do in order for 
those changes to work. 

Second Question: recvsup should probably be re-cvsup, this supposes 
that you did a cvsup of your sources to begin with and something 
was wrong with it. So, do you have cvsup installed? Do you know how 
to use it? Do you know about supfiles and what should be in one?

I think you need to cvsup your sources and go through the full 
buildworld sequence. I think you're trying to short cut and it's 
biting you in the butt right now.

Everyone was a beginner at some time. 

Don

-- 
Donald J. O'Neill
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel compilation failed in 5.3-RELEASE

[Robert Kot]

>
> Recvsup and rebuild. Did you change anything in /etc/make.conf?
>

No, absolutely not. This is my /etc/make.conf:

# -- use.perl generated deltas -- #
# Created: Wed Nov 10 22:37:45 2004
# Setting to use base perl from ports:
PERL_VER=5.8.5
PERL_VERSION=5.8.5
PERL_ARCH=mach
NOPERL=yo
NO_PERL=yo
NO_PERL_WRAPPER=yo

Isn't it supposed to work out of the box ? I had
no such problems with 5.1 and 5.2. Since 5.3 is
a production release, I'm quite surprised by such
problems with kernel recompilation, unless I screwed
something up.

How can I do recvsup ? Sorry for the stupid question,
I'm still a beginner. 

Regards,
Jarek
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Kernel compilation failed in 5.3-RELEASE

[Subhro]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert Kot
Sent: Sunday, November 14, 2004 6:39
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Kernel compilation failed in 5.3-RELEASE



#cpu  I486_CPU
#cpu  I586_CPU
cpu  I686_CPU

Unfortunately, it failed the same way:

===> splash
===> splash/bmp
cc -O -pipe  -D_KERNEL -DKLD_MODULE -nostdinc -I-   
-include /usr/src/sys/i386/compile/ROBERT_20041113_0/opt_global.h -I. -I@ 
-I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common  
-I/usr/src/sys/i386/compile/ROBERT_20041113_0 -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -fformat-extensions -std=c99 
-c /usr/src/sys/modules/splash/bmp/splash_bmp.c
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"mod"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: warning: function
declaration 
isn't a prototype
/usr/src/sys/modules/splash/bmp/splash_bmp.c: In function 
`splash_bmp_modevent':
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `modeventtype_t' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: (Each undeclared 
identifier is reported only once
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: for each function it

appears in.)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"type"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `MOD_UNLOAD' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: case label not
within 
a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `default' label not 
within a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: break statement not 
within loop or switch
/usr/src/sys/modules/splash/bmp/splash_bmp.c: At top level:
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"return"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:47: warning: 'splash_mode' 
defined but not used
/usr/src/sys/modules/splash/bmp/splash_bmp.c:48: warning: 'splash_on'
defined 
but not used
/usr/src/sys/modules/splash/bmp/splash_bmp.c:50: warning: 'bmp_start' used
but 
never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:51: warning: 'bmp_end' used but

never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:52: warning: 'bmp_splash' used 
but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:53: warning: 'bmp_Init'
declared 
`static' but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:54: warning: 'bmp_Draw'
declared 
`static' but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: warning: 
'splash_bmp_modevent' defined but not used
*** Error code 1

Stop in /usr/src/sys/modules/splash/bmp.
*** Error code 1

Stop in /usr/src/sys/modules/splash.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/i386/compile/ROBERT_20041113_0.


Recvsup and rebuild. Did you change anything in /etc/make.conf?

Regards
S.
Subhro Sankha Kar
Block AQ-13/1, Sector V
Salt Lake City
PIN 700091
India


smime.p7s
Description: S/MIME cryptographic signature

Kernel compilation failed in 5.3-RELEASE

[Robert Kot]

5.3-RELEASE

Hi,

 I'm just trying to build kernel in 5.3-RELEASE and it fails.
I added the following to GENERIC config:

#cpu  I486_CPU
#cpu  I586_CPU
cpu  I686_CPU

options  EXT2FS
options  IPFIREWALL
options  IPFIREWALL_VERBOSE
options  IPFIREWALL_DEFAULT_TO_ACCEPT
options  MAC
options  GEOM_BDE
device  sound

Compilation failed:

===> splash
===> splash/bmp
cc -O -pipe  -D_KERNEL -DKLD_MODULE -nostdinc -I-   
-include /usr/src/sys/i386/compile/ROBERT_20041113/opt_global.h -I. -I@ 
-I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common  
-I/usr/src/sys/i386/compile/ROBERT_20041113 -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -fformat-extensions -std=c99 
-c /usr/src/sys/modules/splash/bmp/splash_bmp.c
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"mod"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: warning: function declaration 
isn't a prototype
/usr/src/sys/modules/splash/bmp/splash_bmp.c: In function 
`splash_bmp_modevent':
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `modeventtype_t' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: (Each undeclared 
identifier is reported only once
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: for each function it 
appears in.)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"type"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `MOD_UNLOAD' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: case label not within 
a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `default' label not 
within a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: break statement not 
within loop or switch
/usr/src/sys/modules/splash/bmp/splash_bmp.c: At top level:
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"return"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:47: warning: 'splash_mode' 
defined but not used
/usr/src/sys/modules/splash/bmp/splash_bmp.c:48: warning: 'splash_on' defined 
but not used
/usr/src/sys/modules/splash/bmp/splash_bmp.c:50: warning: 'bmp_start' used but 
never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:51: warning: 'bmp_end' used but 
never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:52: warning: 'bmp_splash' used 
but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:53: warning: 'bmp_Init' declared 
`static' but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:54: warning: 'bmp_Draw' declared 
`static' but never defined
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: warning: 
'splash_bmp_modevent' defined but not used
*** Error code 1

Stop in /usr/src/sys/modules/splash/bmp.
*** Error code 1

Stop in /usr/src/sys/modules/splash.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/i386/compile/ROBERT_20041113.

So, I tried to compile GENERIC kernel only with:

#cpu  I486_CPU
#cpu  I586_CPU
cpu  I686_CPU

Unfortunately, it failed the same way:

===> splash
===> splash/bmp
cc -O -pipe  -D_KERNEL -DKLD_MODULE -nostdinc -I-   
-include /usr/src/sys/i386/compile/ROBERT_20041113_0/opt_global.h -I. -I@ 
-I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common  
-I/usr/src/sys/i386/compile/ROBERT_20041113_0 -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -fformat-extensions -std=c99 
-c /usr/src/sys/modules/splash/bmp/splash_bmp.c
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"mod"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: warning: function declaration 
isn't a prototype
/usr/src/sys/modules/splash/bmp/splash_bmp.c: In function 
`splash_bmp_modevent':
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `modeventtype_t' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: (Each undeclared 
identifier is reported only once
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: for each function it 
appears in.)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"type"
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `MOD_UNLOAD' 
undeclared (first use in this function)
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: case label not within 
a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: `default' label not 
within a switch statement
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: break statement not 
within loop or switch
/usr/src/sys/modules/splash/bmp/splash_bmp.c: At top level:
/usr/src/sys/modules/splash/bmp/splash_bmp.c:60: error: syntax error before 
"return"
/usr/src/sys/

can i safely remove /boot/kernel.old after successful kernel compilation

[ashadul hoque]

Hi everybody,

Following the advice on this list I re-compiled my kernel and got 
significant improvement in boot speed.

No my question is can the old kernel (/boot/kernel.old/) be safely 
deleted?

Thanks in advance.

regards
Ashadul
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

kernel compilation gives error

[Dino Vliet]

Hi there,

on my laptop I get the following error when doing
"make buildkernel KERNCONF=MYKERNEL"

The last part of the error message is:
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
echo "#define INET 1" > opt_inet.h
perl @/kern/vnode_if.pl -h @/kern/vnode_if.src
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE
-I- -I. -I@ -I@/../include
-I/usr/obj/usr/src/i386/usr/include 
/usr/src/sys/modules/if_tun/../../net/if_tun.c
===> if_vlan
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
echo "#define INET 1" > opt_inet.h
rm -f .depend
mkdep -f .depend -a   -nostdinc -DNVLAN=0 -D_KERNEL
-DKLD_MODULE -I- -I. -I@ -I@/../include
-I/usr/obj/usr/src/i386/usr/include 
/usr/src/sys/modules/if_vlan/../../net/if_vlan.c
===> iir
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
touch opt_scsi.h
touch opt_cam.h
perl @/kern/makeops.pl -h @/kern/device_if.m
perl @/kern/makeops.pl -h @/kern/bus_if.m
perl @/kern/makeops.pl -h @/pci/pci_if.m
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE
-I- -I. -I@ -I@/../include
-I/usr/obj/usr/src/i386/usr/include 
/usr/src/sys/modules/iir/../../dev/iir/iir.c
/usr/src/sys/modules/iir/../../dev/iir/iir_ctrl.c
/usr/src/sys/modules/iir/../../dev/iir/iir_pci.c
*** Error code 1

Stop in /usr/src/sys/modules/iir.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/MYKERNEL.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.




My Kernel configuration file MYKERNEL is:

# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.59
2004/04/07 20:29:01 vkashyap Exp $

machine i386
cpu I686_CPU
ident   MYKERNEL
maxusers0

#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug
symbols

#optionsMATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options INET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep
this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big
directories
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, NFS
required
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660
required
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP
THIS!]
#optionsSCSI_DELAY=15000#Delay (in ms) before
probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time
extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
#To hide firewall from traceroute
options IPSTEALTH
options IPFIREWALL_FORWARD
options RANDOM_IP_ID
#To add web server support
options ACCEPT_FILTER_DATA
options ACCEPT_FILTER_HTTP
options KBD_INSTALL_CDEV# install a CDEV entry in
/dev
options AHC_REG_PRETTY_PRINT# Print register
bitfields in debug
# output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register
bitfields in debug 
# output.  Adds ~215k to driver.

# To make an SMP kernel, the next two are needed
#optionsSMP # Symmetric MultiProcessor Kernel
#optionsAPIC_IO # Symmetric (APIC) I/O

device  isa
device  eisa
device  pci

# Floppy drives
device  fdc0at isa? port IO_FD1 irq 6 drq 2
device  fd0 at fdc0 drive 0
#device fd1 at fdc0 drive 1
#
# If you have a Toshiba Libretto with its Y-E Data
PCMCIA floppy,
# don't use the above line for fdc0 but the following
one:
#device fdc0

# ATA and ATAPI devices
#device ata0at isa? port IO_WD1 irq 14
#device ata1at isa? port IO_WD2 irq 15
device  ata
device

Kernel compilation error on DS20E

[andrea . crisanti]

Hy,

I just installed FreeBSD 5.2.1 on a Alpha DS20E server.

The installation was without problems.

The problem comes when I try to compile the kernel.

Following both the "traditional" or the "new" procedure
I always gets the forrlowing error:

- CUT CUT CUT -

awk -f /usr/src/sys/modules/linprocfs/../../conf/kmod_syms.awk 
linprocfs.kld  
/usr/src/sys/alpha/compile/SERVER/modules/usr/src/sys/modules/linprocfs/export_syms 
|  xargs -J% objcopy % linprocfs.kld
ld -Bshareable  -d -warn-common -o linprocfs.ko linprocfs.kld
===> linux
@ -> /usr/src/sys
ln: @/sys: File exists
*** Error code 1

Stop in /usr/src/sys/modules/linux.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/alpha/compile/SERVER.


--- END END END ---

The only reference to this problem I found in the web is an old
mail from  09/30/2001 with the same problem was seen with 
reeBSD 4.4 RELEASE. However no solution was given.

Does anyonwe knows how to solve this problem?

I had no problem in building the kernel from the FreeBSD 5.2.1 release
on a i386 compuer.

Bye
Andrea

-- 

Prof. Andrea Crisanti   http://castore.phys.uniroma1.it/KR
Dipartimento di Fisica  Tel. +39-06 4991 3431
Universita' di Roma "La Sapienza"   Fax. +39-06 4463158
P.le A. Moro 2  [EMAIL PROTECTED]
I-00185 Roma, Italy [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: problems with kernel compilation

[Kris Kennaway]

On Tue, Mar 02, 2004 at 01:15:35AM +, bryan m wrote:
> I'm trying to compile a new kernel to add IPFilter support, albeit getting 
> some compiler errors:
> (this is with a 5.2 kernel by the way)

From src/sys/conf/NOTES (also documented in UPDATING)

# PFIL_HOOKS enables an abtraction layer which is meant to be used in
# network code where filtering is required.  See the pfil(9) man page.
# This option is required by the IPFILTER option.

Kris


pgp0.pgp
Description: PGP signature

problems with kernel compilation

[bryan m]

I'm trying to compile a new kernel to add IPFilter support, albeit getting 
some compiler errors:
(this is with a 5.2 kernel by the way)

   ../../../contrib/ipfilter/netinet/ip_fil.c: In function 
`fr_check_wrapper':
   ../../../contrib/ipfilter/netinet/ip_fil.c:319: error: `PFIL_OUT' 
undeclared (first use in this function)
   ../../../contrib/ipfilter/netinet/ip_fil.c:319: error: (Each undeclared 
identifier is reported only once
   ../../../contrib/ipfilter/netinet/ip_fil.c:319: error: for each function 
it appears in.)
   ../../../contrib/ipfilter/netinet/ip_fil.c: In function `iplattach':
   ../../../contrib/ipfilter/netinet/ip_fil.c:376: warning: unused variable 
`ph_inet'
   ../../../contrib/ipfilter/netinet/ip_fil.c: At top level:
   ../../../contrib/ipfilter/netinet/ip_fil.c:317: warning: 
`fr_check_wrapper' defined but not used
   *** Error code 1

   Stop in /usr/src/sys/i386/compile/ROUTER.

Here is my kernel configuration:

   machine i386
   cpu I686_CPU
   ident ROUTER
   options SCHED_4BSD
   options INET
   options FFS
   options SOFTUPDATES
   options UFS_ACL
   options UFS_DIRHASH
   options MD_ROOT
   options PROCFS
   options PSEUDOFS
   options COMPAT_43
   options COMPAT_FREEBSD4
   options KTRACE
   options SYSVSHM
   options SYSVMSG
   options SYSVSEM
   options _KPOSIX_PRIORITY_SCHEDULING
   options KBD_INSTALL_CDEV
   options AHC_REG_PRETTY_PRINT
   options AHD_REG_PRETTY_PRINT
   options INVARIANT_SUPPORT
   device isa
   device eisa
   device pci
   device fdc
   device ata
   device atadisk
   device atapicd
   options ATA_STATIC_ID
   device atkbdc
   device atkbd
   device psm
   device vga
   device splash
   device sc
   device agp
   device npx
   device pmtimer
   device sio
   device miibus
   device fxp
   device vr
   device random
   device loop
   device ether
   device tun
   device pty
   device gif
   device bpf
   options IPFILTER
   options IPFILTER_LOG
   options IPFILTER_DEFAULT_BLOCK
Would someone please tell me what's wrong here?
Thanks in advance
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation issues/5.2-CURRENT/AMD64

[Jason Lixfeld]

On Feb 23, 2004, at 12:38 AM, Peter Wemm wrote:

On Sunday 22 February 2004 08:29 pm, Jason Lixfeld wrote:
make buildkernel keeps failing here:

===> accf_data
cc -O -fPIC   -D_KERNEL -DKLD_MODULE -nostdinc -I-   -include
Stop right here!  You've removed the 'makeoptions NO_MODULES=notyet'
from your config file.  Put it right back in there immediately.
*gulp* when I built my custom kernel, I looked in 
/usr/src/sys/conf/NOTES and /usr/src/sys/amd64/conf/NOTES and found 
nothing pertaining to the use of this makeoption.  I checked google, 
forums, lists, etc and found nothing specific on the use of this so I 
removed it.

Perhaps add a comment saying that you will have weird stuff happen if 
this is not here will help deter people from overzealously removing it, 
as I did.

Thanks!  I'll give it a shot and see what happens.

We don't support kld modules yet.  Your buildkernel is failing because
you're trying to do something that isn't possible with our  toolchain.
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compilation issues/5.2-CURRENT/AMD64

[Peter Wemm]

On Sunday 22 February 2004 08:29 pm, Jason Lixfeld wrote:
> make buildkernel keeps failing here:
>
> ===> accf_data
> cc -O -fPIC   -D_KERNEL -DKLD_MODULE -nostdinc -I-   -include

Stop right here!  You've removed the 'makeoptions NO_MODULES=notyet'
from your config file.  Put it right back in there immediately.

We don't support kld modules yet.  Your buildkernel is failing because 
you're trying to do something that isn't possible with our  toolchain.
-- 
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kernel Compilation issues/5.2-CURRENT/AMD64

[Jason Lixfeld]

make buildkernel keeps failing here:

===> accf_data
cc -O -fPIC   -D_KERNEL -DKLD_MODULE -nostdinc -I-   -include 
/usr/obj/usr/src/sys/ESHARA/opt_global.h -I. -I@ -I@/../include 
-finline-limit=8000 -fno-common  -I/usr/obj/usr/src/sys/ESHARA 
-mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx 
-mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding 
-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -c /usr/src/sys/netinet/accf_data.c
cc1: sorry, unimplemented: code model kernel not supported in PIC mode
cc1: error: code model `kernel' not supported in the 64 bit mode
*** Error code 1

Stop in /usr/src/sys/modules/accf_data.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/obj/usr/src/sys/ESHARA.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.

I added in CFLAGS= -O -fPIC to /etc/make.conf.

Here's the diff between my custom kernel and the plain vanilla GENERIC. 
 GENERIC compiles fine, but for some reason, there is something missing 
from mine that's in GENERIC that's causing it to fail but I have no 
idea what.  I thought I checked out NOTES pretty thoroughly but I guess 
not.

su-2.05b# diff ESHARA GENERIC
3c3,5
< ident ESHARA
---
> ident GENERIC
> makeoptions   DEBUG=-g# Build kernel with gdb(1) 
debug symbols
> makeoptions   NO_MODULES=not_yet
5a8
> options   INET6   # IPv6 communications protocols
7a11
> options   UFS_ACL # Support for access control 
lists
8a13,17
> options   MD_ROOT # MD is a potential root device
> options   NFSCLIENT   # Network Filesystem Client
> options   NFSSERVER   # Network Filesystem Server
> options   NFS_ROOT# NFS usable as /, requires 
NFSCLIENT
> options   MSDOSFS # MSDOS Filesystem
9a19,20
> options   PROCFS  # Process filesystem (requires 
PSEUDOFS)
> options   PSEUDOFS# Pseudo-filesystem framework
11a23,24
> options   SCSI_DELAY=15000# Delay (in ms) before probing 
SCSI
> options   KTRACE  # ktrace(1) support
16a30,38
> options   AHC_REG_PRETTY_PRINT# Print register bitfields in 
debug
> options   AHD_REG_PRETTY_PRINT# Print register bitfields in 
debug
> options   PFIL_HOOKS  # pfil(9) framework
> options   DDB # Enable the kernel debugger
> options   INVARIANTS  # Enable calls of extra sanity 
checking
> options   INVARIANT_SUPPORT   # Extra sanity checks of 
internal structures, required by INVARIANTS
> options   WITNESS # Enable checks to detect 
deadlocks and cycles
> options   WITNESS_SKIPSPIN# Don't run witness on 
spinlocks for speed
> options   SMP # Symmetric MultiProcessor Kernel
21a44,45
> devicepcm
> devicefdc
25a50,51
> deviceatapifd # ATAPI floppy drives
> deviceatapist # ATAPI tape drives
26a53,83
> deviceahb # EISA AHA1742 family
> deviceahc # AHA2940 and onboard AIC7xxx 
devices
> deviceahd # AHA39320/29320 and onboard 
AIC79xx devices
> deviceamd # AMD 53C974 (Tekram DC-390(T))
> deviceisp # Qlogic family
> devicempt # LSI-Logic MPT-Fusion
> devicesym # NCR/Symbios Logic (newer 
chipsets + those of `ncr')
> devicetrm # Tekram DC395U/UW/F DC315U 
adapters
> deviceadv # Advansys SCSI adapters
> deviceadw # Advansys wide SCSI adapters
> deviceaha # Adaptec 154x SCSI adapters
> deviceaic # Adaptec 15[012]x SCSI 
adapters, AIC-6[23]60.
> devicebt  # Buslogic/Mylex MultiMaster 
SCSI adapters
> devicescbus   # SCSI bus (required for SCSI)
> devicech  # SCSI media changers
> deviceda  # Direct Access (disks)
> devicesa  # Sequential Access (tape etc)
> devicecd  # CD
> devicepass# Passthrough device (direct 
SCSI access)
> deviceses # SCSI Environmental Services 
(and SAF-TE)
> deviceamr # AMI MegaRAID
> deviceciss# Compaq Smart RAID 5*
> devicedpt # DPT Smartcache III, IV - See 
NOTES for options
> deviceiir # Intel Integrated RAID
> deviceips # IBM 

No sound (was Re: kernel compilation problems - 5.1 (long) )

[Tadimeti Keshav]

Hello all
Thanks Mike and Peter. I have been able to
successfully compile the new kernel & install it.

BUT, though I compiled with:
device  pcm #TK: for sound blaster pro 16.
I get no sound.
(I tried to play an audio file with amp).
The sound card is a SOUND BLASTER PRO 16 Compatible.
Here is a copy of dmesg. I can make no sense of it.
Note: I connected a USB2 hard disk with NTFS, but did
not know how to mount.
Thanks in advance
Tk
--
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
1991, 1992, 1993, 1994
The Regents of the University of California. All
rights reserved.
FreeBSD 5.1-RELEASE #1: Thu Feb 12 21:03:55 SGT 2004
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/CUSTOM
Preloaded elf kernel "/boot/kernel/kernel" at
0xc04fb000.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 200457161 Hz
CPU: Pentium/P55C (200.46-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x543  Stepping = 3
 
Features=0x8001bf
real memory  = 67108864 (64 MB)
avail memory = 59797504 (57 MB)
Intel Pentium detected, installing workaround for F00F
bug
npx0:  on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 6 entries at 0xc00f6bd0
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
pci0:  at device 3.0 (no driver
attached)
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port
0xecd0-0xecdf at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0:  port
0xece0-0xecff irq 10 at device 7.2 on pci0
usb0:  on
uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00,
addr 1
uhub0: 2 ports with 2 removable, self powered
pci0:  at device 7.3 (no driver
attached)
pci0:  at device 17.0 (no driver
attached)
orm0:  at iomem 0xc-0xc7fff on isa0
pmtimer0 on isa0
atkbdc0:  at port
0x64,0x60 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0:  at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on
isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0:  on ppc0
plip0:  on ppbus0
ppi0:  on ppbus0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem
0xa-0xb on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (irq)
pcm0:  at port
0x220-0x22f,0x388-0x38b,0x530-0x533 irq 5 drq 1,3 on
isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
Timecounters tick every 10.000 msec
ad0: 9787MB  [19885/16/63]
at ata0-master UDMA33
acd0: CDROM  at ata1-master
PIO3
Mounting root from ufs:/dev/ad0s1a
sio0: 1 more silo overflow (total 1)
pid 521 (opera), uid 1001: exited on signal 11 (core
dumped)
umass0: Genesys Logic USB TO IDE, rev 2.00/0.02, addr
2
da0 at umass-sim0 bus 0 target 0 lun 0
da0:  Fixed Direct Access
SCSI-0 device 
da0: 1.000MB/s transfers
da0: 117800MB (241254720 512 byte sectors: 255H 63S/T
15017C)
(da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not
supported, increasing minimum_cmd_size to 10.
lock order reversal
 1st 0xc1602b90 vm object (vm object) @
vm/vm_object.c:512
 2nd 0xc082f110 system map (system map) @
vm/vm_kern.c:325
--

=
-- K E S H A V  T A D I M E T I --
BeOS Air
You have to pay for the tickets, but they're half the price of Windows Air, and if you 
are an aircraft mechanic you can probably ride for free. It only takes 15 minutes to 
get to the airport and you are cheuferred there in a limozine. BeOS Air only has 
limited types of planes that only hold new luggage. All planes are single seaters and 
the model names all start with an "F" (F-14, F-15, F-16, F-18, etc.). The plane will 
fly you to your destination on autopilot in half the time of other Airways or you can 
fly the plane yourself. There are limited destinations, but they are only places you'd 
want to go to anyway. You tell all your friends how great BeOS Air is and all they say 
is "What do you mean I can't bring all my old baggage with me?"





___
BT Yahoo! Broadband - Free modem offer, sign up online today and save £80 
http://btyahoo.yahoo.co.uk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compilation problems - 5.1 (long)

[Peter Risdon]

Tadimeti Keshav wrote:

hi all,
I am having problems compiling my kernel. 
 

Your immediate problem is a common one. Your kernel config includes the 
line:

device		umass		# Disks/Mass storage - Requires scbus and da

But scbus and da are commented out. Uncomment them, and compile.

PWR.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

re: kernel compilation problems - 5.1 (long)

[Mike Bowie]

   -- snip --
>>  umass.o: In function `umass_cam_quirk_cb':
>>  umass.o(.text+0x23eb): undefined reference to
>>  `xpt_done'
>>  *** Error code 1
>>
>>  Stop in /usr/src/sys/i386/compile/CUSTOM.
   -- snip --
>>  # SCSI peripherals
>>  #device& nbsp;   scbus# SCSI bus (required)
>>
>>  #device& nbsp;   ch# SCSI media changers
>>
>>  #device& nbsp;   da# Direct Access (disks)
   -- snip --

>>  deviceumass  &n bsp; # Disks/Mass storage - Requires
   scbus and da
   IIRC, the umass device depends on the scbus, da devices... uncomments
   them and start the build again.



   HTH,



   Mike.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

kernel compilation problems - 5.1 (long)

[Tadimeti Keshav]

hi all,
I am having problems compiling my kernel. 

FreeBSD 5.1
Intel Pentium 200 MMX. 64MB ram. 
Digital PC 5000. 
I am having problems while linking the objects (.o
files). Why is it compiling for PentiumPRO?
I am attaching the kernel config file.
Sorry if I have sent it to the wrong list.
I appreciate any help.
Thanks v much in advance
Tk.
--
OUTPUT (only last part)
---
standing -Werror  vnode_if.c
touch hack.c
cc  -shared -nostdlib hack.c -o hack.So
rm -f hack.c
sh ../../../conf/newvers.sh CUSTOM
cc -c -O -pipe -mcpu=pentiumpro 
 ^^ (WHY!!!)
-Wall -Wredundant-decls -Wnested-externs -Wstr
ict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -ff ormat-extensions -std=c99  

-nostdinc -I-  -I. -I../../.. -I../../../dev -I../.
./../contrib/dev/acpica -I../../../contrib/ipfilter
-D_KERNEL -include opt_glo bal.h -fno-common  

-mno-align-long-strings -mpreferred-stack-boundary=2
-ffree standing -Werror  vers.c


linking kernel

umass.o: In function `umass_cam_attach_sim':
umass.o(.text+0x19f7): undefined reference to
`cam_simq_alloc'

umass.o(.text+0x1a48): undefined reference to
`cam_sim_alloc'

umass.o(.text+0x1a57): undefined reference to
`cam_simq_free'

umass.o(.text+0x1a77): undefined reference to
`xpt_bus_register'
umass.o: In function `umass_cam_rescan_callback':

umass.o(.text+0x1ab3): undefined reference to
`xpt_free_path'

umass.o: In function `umass_cam_rescan':
umass.o(.text+0x1b25): undefined reference to
`xpt_periph'

umass.o(.text+0x1b34): undefined reference to
`xpt_create_path'

umass.o(.text+0x1b50): undefined reference to
`xpt_setup_ccb'

umass.o(.text+0x1b6d): undefined reference to
`xpt_action'

umass.o: In function `umass_cam_detach_sim':

umass.o(.text+0x1c5c): undefined reference to
`xpt_bus_deregister'

umass.o(.text+0x1c78): undefined reference to
`cam_sim_free'

umass.o: In function `umass_cam_action':
umass.o(.text+0x20ed): undefined reference to
`xpt_done'

umass.o: In function `umass_cam_cb':
umass.o(.text+0x225b): undefined reference to
`xpt_done'

umass.o: In function `umass_cam_sense_cb':
umass.o(.text+0x23c1): undefined reference to
`xpt_done'

umass.o: In function `umass_cam_quirk_cb':
umass.o(.text+0x23eb): undefined reference to
`xpt_done'

*** Error code 1
 
Stop in /usr/src/sys/i386/compile/CUSTOM.



=
-- K E S H A V  T A D I M E T I --
BeOS Air
You have to pay for the tickets, but they're half the price of Windows Air, and if you 
are an aircraft mechanic you can probably ride for free. It only takes 15 minutes to 
get to the airport and you are cheuferred there in a limozine. BeOS Air only has 
limited types of planes that only hold new luggage. All planes are single seaters and 
the model names all start with an "F" (F-14, F-15, F-16, F-18, etc.). The plane will 
fly you to your destination on autopilot in half the time of other Airways or you can 
fly the plane yourself. There are limited destinations, but they are only places you'd 
want to go to anyway. You tell all your friends how great BeOS Air is and all they say 
is "What do you mean I can't bring all my old baggage with me?"





___
BT Yahoo! Broadband - Free modem offer, sign up online today and save £80 
http://btyahoo.yahoo.co.uk#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386

#
# For more information on this file, please read the handbook section on 
# Kernel Configuration Files:

#
#http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html

#
# The handbook is also available locally in /usr/share/doc/handbook

# if you've installed the doc distribution, otherwise always see the

# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the

# latest information.

#
# An exhaustive list of options and more detailed explanations of the

# device lines is also present in the ../../conf/NOTES and NOTES files. 

# If you are in doubt as to the purpose or necessity of a line, check first 

# in NOTES.

#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.384.2.2 2003/05/31 15:18:41 scottl Exp $


machine i386

#cpuI486_CPU # - not 486:TK

cpu I586_CPU

#cpuI686_CPU # - not P!!! or P4:TK

ident   CUSTOM


#To statically compile in device wiring instead of /boot/device.hints

#hints  "GENERIC.hints" 
#Default places to look for devices.


#makeoptionsDEBUG=-g
#Build kernel with gdb(1) debug symbols


options SCHED_4BSD  #4BSD scheduler

options INET#InterNETworking

options INET6   #IPv6 communications protocols

options FFS #Berkeley Fast Filesystem

options SOFTUPDATES #Enable FFS soft updates support

options UFS_ACL #Supp

Re: 5.2 kernel compilation error

[Melvyn Sopacua]

On Saturday 31 January 2004 01:29, paul wrote:
> after i fresh 5.2 install i cvsup using the tag releng_5_2 do a make
> world i then tryed doing a custom kernel and recieve the following error
> i also tryed make buildkernel make kernel and recieve the same error
>
> sh ../../../conf/newvers.sh GENERIC
> cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
> -Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../..
> -I../../../contrib/dev/acpica -I../../../contrib/ipfilter
> -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd
> -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common
> -finline-limit=15000 -fno-strict-aliasing  -mno-align-long-strings
> -mpreferred-stack-boundary=2 -ffreestanding -Werror  vers.c
> vers.c:30:18: unknown escape sequence '\.'
> *** Error code 1
>

Which directory is this (make reports it after the error code)?
-- 
Melvyn

===
FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 
18:01:18 CET 2004 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG  
i386
===


pgp0.pgp
Description: signature

5.2 kernel compilation error

[paul]

after i fresh 5.2 install i cvsup using the tag releng_5_2 do a make 
world i then tryed doing a custom kernel and recieve the following error 
i also tryed make buildkernel make kernel and recieve the same error

sh ../../../conf/newvers.sh GENERIC
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../.. 
-I../../../contrib/dev/acpica -I../../../contrib/ipfilter 
-I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd 
-I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common 
-finline-limit=15000 -fno-strict-aliasing  -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Werror  vers.c
vers.c:30:18: unknown escape sequence '\.'
*** Error code 1

any help would be appreciated
regards -Paul
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Error during 'make' phase of kernel compilation

[Daniel Cody]

Thanks, that did the trick!

-Original Message-
From: Daniel Bye [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 11:31 AM
To: [EMAIL PROTECTED]
Subject: Re: Error during 'make' phase of kernel compilation


On Thu, Jul 31, 2003 at 11:05:58AM -0400, Daniel Cody wrote:

[---snip---]

> aic.o: In function `aic_detach':
> aic.o(.text+0x1b66): undefined reference to `xpt_async'
> aic.o(.text+0x1b6e): undefined reference to `xpt_free_path'
> aic.o(.text+0x1b7c): undefined reference to `xpt_bus_deregister'
> aic.o(.text+0x1b86): undefined reference to `cam_sim_free'
> *** Error code 1
> 
> Stop in /usr/src/sys/compile/KERNATTICUS.

Do you have any SCSI devices attached to the system?  If so, you need to
enable:

device scbus
device da  # for direct access devices, such as disks

and recompile.  You might also want to uncomment `options
SCSI_DELAY=15000'
as well.  If 15 seconds is too long to wait (most modern SCSI devices
settle
much more quickly than this - I set this down to 5 seconds) you can tune

this value down.

If you have no SCSI devices, then disable:

device  adw
device  aha0at isa?
device  aic0at isa?
device  ncv # NCR 53C500
device  stg # TMC 18C30/18C50

and try again.

HTH

Dan

-- 
Daniel Bye

PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Error during 'make' phase of kernel compilation

[Daniel Bye]

On Thu, Jul 31, 2003 at 11:05:58AM -0400, Daniel Cody wrote:

[---snip---]

> aic.o: In function `aic_detach':
> aic.o(.text+0x1b66): undefined reference to `xpt_async'
> aic.o(.text+0x1b6e): undefined reference to `xpt_free_path'
> aic.o(.text+0x1b7c): undefined reference to `xpt_bus_deregister'
> aic.o(.text+0x1b86): undefined reference to `cam_sim_free'
> *** Error code 1
> 
> Stop in /usr/src/sys/compile/KERNATTICUS.

Do you have any SCSI devices attached to the system?  If so, you need to
enable:

device scbus
device da  # for direct access devices, such as disks

and recompile.  You might also want to uncomment `options SCSI_DELAY=15000'
as well.  If 15 seconds is too long to wait (most modern SCSI devices settle
much more quickly than this - I set this down to 5 seconds) you can tune 
this value down.

If you have no SCSI devices, then disable:

device  adw
device  aha0at isa?
device  aic0at isa?
device  ncv # NCR 53C500
device  stg # TMC 18C30/18C50

and try again.

HTH

Dan

-- 
Daniel Bye

PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \


pgp0.pgp
Description: PGP signature

Error during 'make' phase of kernel compilation

[Daniel Cody]

I just got my first FreeBSD box up a couple of days ago, and I decided to try creating 
a custom kernel. I followed the directions in the handbook. Unfortunately, I received 
this output after issuing the 'make' command:

.
.
.
aic.o(.text+0x129e): undefined reference to `xpt_done'
aic.o: In function `aic_timeout':
aic.o(.text+0x12d4): undefined reference to `xpt_print_path'
aic.o(.text+0x1340): undefined reference to `xpt_print_path'
aic.o(.text+0x1379): undefined reference to `xpt_freeze_simq'
aic.o: In function `aic_intr':
aic.o(.text+0x15c5): undefined reference to `xpt_async'
aic.o: In function `aic_reset':
aic.o(.text+0x180c): undefined reference to `xpt_async'
aic.o: In function `aic_attach':
aic.o(.text+0x1a36): undefined reference to `cam_simq_alloc'
aic.o(.text+0x1a6b): undefined reference to `cam_sim_alloc'
aic.o(.text+0x1a7b): undefined reference to `cam_simq_free'
aic.o(.text+0x1a92): undefined reference to `xpt_bus_register'
aic.o(.text+0x1aae): undefined reference to `xpt_create_path'
aic.o(.text+0x1ac1): undefined reference to `xpt_bus_deregister'
aic.o(.text+0x1acb): undefined reference to `cam_sim_free'
aic.o: In function `aic_detach':
aic.o(.text+0x1b66): undefined reference to `xpt_async'
aic.o(.text+0x1b6e): undefined reference to `xpt_free_path'
aic.o(.text+0x1b7c): undefined reference to `xpt_bus_deregister'
aic.o(.text+0x1b86): undefined reference to `cam_sim_free'
*** Error code 1

Stop in /usr/src/sys/compile/KERNATTICUS.





I had already done a '/usr/sbin/config KERNATTICUS' and a 'make depend' in the proper 
directories. Attached is a copy of my configuration file.
Any help would be greatly appreciated.

Cody
 <> 


KERNATTICUS
Description: KERNATTICUS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Fwd: Newbie Right of Passage -- Kernel Compilation Problems :-)

[Lowell Gilbert]

Kris Kerwin <[EMAIL PROTECTED]> writes:

> I have forwarded a message that's about two weeks old from the -newbies list.  
> As you'll see, the problem is related to kernel compilation.

The way to track down this kind of problem is to start with a
known-working configuration, like GENERIC, and then make your changes
one (or a few) at a time.  This way, when it breaks, you know which
changes to look at as the cause of the problem.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Newbie Right of Passage -- Kernel Compilation Problems :-)

[Derrick Ryalls]

> Hello all,
> 
> I have forwarded a message that's about two weeks old from 
> the -newbies list.  
> As you'll see, the problem is related to kernel compilation.
> 
> One bit of update to this old message:
> 
> I got wise to it (slightly), and decided that despite the 
> fact that I didn't 
> have an ISA card, it might be intuitive to add the line:
> 
>   device  isa
> 
> to my kernel config file, seeing as how the file 'npx.c' is 
> contained in a 
> directory named 'isa.'  Thinking I had some sort of sourcecode level 
> dependency solved, I proudly attempted to recompile.  Fate 
> had other ideas, 
> and the compile failed again, this time before reaching 
> npx.c.  Here's the 
> error:
> 
>   In file included from 
> /usr/target/src/sys/dev/sound/pcm/sound.h   
> :98,
>  from 
> /usr/target/src/sys/dev/sound/isa/sbc.c:2 
>
> 8:
> /usr/target/src/sys/dev/sound/pcm/channel.h:69:24: 
> channel_if.h
> : No such file or directory
> mkdep: compile failed

Do you have device pcm in your kernel?  I think that was the solution
for me with that error

> 
> Clearly, this smacks of problems with the isa driver.
> 
> Again, thanks for your help.
> 
> Kris Kerwin
> 
> 
> --  Forwarded Message  --
> 
> Subject: Newbie Right of Passage -- Kernel Compilation Problems :-)
> Date: Tuesday 17 June 2003 10:56 pm
> From: Kris Kerwin <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> 
> Hello all,
> 
> This might be more of a question for the freebsd-questions 
> mailing list, but, knowing my luck, I probably just made a 
> newbie mistake.  :-)
> 
> While compiling my kernel (using the 5.1-RELEASE source), I 
> ran into an error while trying to compile 
> /usr/src/sys/i386/isa/npx.c.  I did my homework, and learned 
> that NPX is one of those device drivers that you really can't 
> live without (it takes care of Floating Point Math), so, I 
> can't just comment that line out of my kernel config.
> 
> The error?  I cut the output of 'make buildkernel KERNCONF=MYKERNEL':
> 
>   cc1: warnings being treated as errors
>   /usr/target/src/sys/i386/isa/npx.c:1075: warning: 
> `npx_driver' defined but not used
>   /usr/target/src/sys/i386/isa/npx.c:1081: warning: 
> `npx_devclass' defined but not used
> 
> I resynced my source tree, and tried to recompile;  no joy, 
> same errors.
> 
> I tried running with the -k argument to ignore errors, and it 
> told me at the end of the compile that making 'all' failed.
> 
> I tried the traditional '/usr/sbin/config' 'make depend' 
> 'make' 'make install', still got teh same errors.
> 
> I tried looking at the source for npx.c itself, and couldn't 
> make heads or tales of it.  :-) ... I'm more of an end-user 
> than a developer, the only tutorial I've done is 'Hello 
> World!'  I did 'grep -n' the file and searched for those two 
> functions, and did find them, but wasn't sure if I should 
> risk commenting them out.  My luck, my mistake was made long 
> before it got to the source code.
> 
> As of yet, I havn't been able to find an FAQ with an answer 
> to this one, and no amount of googling the rest of the 
> internet or freebsd.org has been able to help me either.
> 
> Any ideas?  Did I just make another goof?  Thanks for all of 
> your help.
> 
> Kris Kerwin
> 
> ___
> [EMAIL PROTECTED] mailing list 
> http://lists.freebsd.org/mailman/listinfo/free> bsd-newbies
> To 
> unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
> 
> ---
> 
> ___
> [EMAIL PROTECTED] mailing list 
> http://lists.freebsd.org/mailman/listinfo/free> bsd-questions
> 
> To unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
> 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Fwd: Newbie Right of Passage -- Kernel Compilation Problems :-)

[Kris Kerwin]

Hello all,

I have forwarded a message that's about two weeks old from the -newbies list.  
As you'll see, the problem is related to kernel compilation.

One bit of update to this old message:

I got wise to it (slightly), and decided that despite the fact that I didn't 
have an ISA card, it might be intuitive to add the line:

device  isa

to my kernel config file, seeing as how the file 'npx.c' is contained in a 
directory named 'isa.'  Thinking I had some sort of sourcecode level 
dependency solved, I proudly attempted to recompile.  Fate had other ideas, 
and the compile failed again, this time before reaching npx.c.  Here's the 
error:

In file included from /usr/target/src/sys/dev/sound/pcm/sound.h
   
:98,
 from /usr/target/src/sys/dev/sound/isa/sbc.c:2

8:
/usr/target/src/sys/dev/sound/pcm/channel.h:69:24: channel_if.h

: No such file or directory
mkdep: compile failed

Clearly, this smacks of problems with the isa driver.

Again, thanks for your help.

Kris Kerwin


--  Forwarded Message  --

Subject: Newbie Right of Passage -- Kernel Compilation Problems :-)
Date: Tuesday 17 June 2003 10:56 pm
From: Kris Kerwin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]

Hello all,

This might be more of a question for the freebsd-questions mailing list, but,
knowing my luck, I probably just made a newbie mistake.  :-)

While compiling my kernel (using the 5.1-RELEASE source), I ran into an error
while trying to compile /usr/src/sys/i386/isa/npx.c.  I did my homework, and
learned that NPX is one of those device drivers that you really can't live
without (it takes care of Floating Point Math), so, I can't just comment that
line out of my kernel config.

The error?  I cut the output of 'make buildkernel KERNCONF=MYKERNEL':

cc1: warnings being treated as errors
/usr/target/src/sys/i386/isa/npx.c:1075: warning: `npx_driver' defined but
not used
/usr/target/src/sys/i386/isa/npx.c:1081: warning: `npx_devclass' defined but
not used

I resynced my source tree, and tried to recompile;  no joy, same errors.

I tried running with the -k argument to ignore errors, and it told me at the
end of the compile that making 'all' failed.

I tried the traditional '/usr/sbin/config' 'make depend' 'make' 'make
install', still got teh same errors.

I tried looking at the source for npx.c itself, and couldn't make heads or
tales of it.  :-) ... I'm more of an end-user than a developer, the only
tutorial I've done is 'Hello World!'  I did 'grep -n' the file and searched
for those two functions, and did find them, but wasn't sure if I should risk
commenting them out.  My luck, my mistake was made long before it got to the
source code.

As of yet, I havn't been able to find an FAQ with an answer to this one, and
no amount of googling the rest of the internet or freebsd.org has been able
to help me either.

Any ideas?  Did I just make another goof?  Thanks for all of your help.

Kris Kerwin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

---

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel compilation error

[Fernando Gleiser]

On Wed, 18 Jun 2003, Matias Pascaner wrote:

>
> cc: Internal error: Segmentation fault (program cpp0)
> Please submit a full bug report.
> See http://www.gnu.org/software/gcc/bugs.html> for instructions.
> makdep: compile failed
>
> *** Error code 1
>
> So i compile try to compile the generic kernel and happened the same.
>
> what's the problem?

Bad hardware. Google for "+gcc+SIG11+FAQ" for the details.


Fer

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel compilation error

[Gary Jennejohn]

"Matias Pascaner" writes:
> Hi, my name's Matias and it's the first time that i'm using freebsd or other 
> linux based system. i'm trying to compile a kernel and it gives me this 
> error
> 

Please! FreeBSD is !!NOT!! Linux based.

> cc: Internal error: Segmentation fault (program cpp0)
> Please submit a full bug report.
> See http://www.gnu.org/software/gcc/bugs.html> for instructions.
> makdep: compile failed
> 
> *** Error code 1
> 
> So i compile try to compile the generic kernel and happened the same.
> 
> what's the problem?
> 

Almost definitely hardware. Bad memory, overheating CPU, overclocked CPU,
etc. Also the BIOS settings for memory may be too aggressive leading
to memory errors (I've done that).

---
Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kernel compilation error

[Matias Pascaner]

Hi, my name's Matias and it's the first time that i'm using freebsd or other 
linux based system. i'm trying to compile a kernel and it gives me this 
error

cc: Internal error: Segmentation fault (program cpp0)
Please submit a full bug report.
See http://www.gnu.org/software/gcc/bugs.html> for instructions.
makdep: compile failed
*** Error code 1

So i compile try to compile the generic kernel and happened the same.

what's the problem?

_
Charla con tus amigos en línea mediante MSN Messenger: 
http://messenger.yupimsn.com/

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compilation error

[Kris Kennaway]

On Wed, Jun 11, 2003 at 09:20:20AM -0700, Vaida Bogdan wrote:
> Please cc this answer to me because I'm not in the
> mailling list.
> I'm using Freebsd 5.0-RELEASE. I sysinstall
> /usr/src/ sys,tools,usr.bin then I cvsup those. I try
> to compile the kernel (GENERIC) using: 
> make buildkernel KERNCONF=BUGNERIC
> and I get the following errors:

If you're trying to upgrade to current you need to subscribe to the
current mailing list and read it before sending in bug reports.  This
bug has been reported already.

Kris


pgp0.pgp
Description: PGP signature

kernel compilation error

[Vaida Bogdan]

Please cc this answer to me because I'm not in the
mailling list.
I'm using Freebsd 5.0-RELEASE. I sysinstall
/usr/src/ sys,tools,usr.bin then I cvsup those. I try
to compile the kernel (GENERIC) using: 
make buildkernel KERNCONF=BUGNERIC
and I get the following errors:
.c
/usr/src/sys/netgraph/bluetooth/socket/ng_btsocket.c:43:23:
bitstring.h: No such file or directory
/usr/src/sys/netgraph/bluetooth/socket/ng_btsocket_hci_raw.c:51:23:
bitstring.h: No such file or directory
/usr/src/sys/netgraph/bluetooth/socket/ng_btsocket_l2cap_raw.c:51:23:
bitstring.h: No such file or directory
/usr/src/sys/netgraph/bluetooth/socket/ng_btsocket_l2cap.c:52:23:
bitstring.h: No such file or directory
mkdep: compile failed
*** Error code 1

/usr/include/bitstring.h exists and the functions
there work (I made a dummy C proggie)

__
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: mkdep error on kernel compilation

[taxman]

On Saturday 15 March 2003 09:01 pm, [EMAIL PROTECTED] wrote:
> Hello,
>   I am trying to compile a kernel under FreeBSD 4.62, and I am getting an
> error that I couldn't find in the archives.  After executing "make depend
> && make all install", I get an error like this:

Considering this is a nonstandard way to build a kernel, I'm not too surprised 
you got an error.  Try the standard way before hunting down the problem.
The standard way is method 2 listed in the handbook.

Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

mkdep error on kernel compilation

[bptimm]

Hello,
  I am trying to compile a kernel under FreeBSD 4.62, and I am getting an error 
that I couldn't find in the archives.  After executing "make depend && make all 
install", I get an error like this:

/usr/src/sys/modules/icbs2/../../i386/icbs2/icbs2_isc_sysent.c: 38: 
unterminated macro call

has anybody seen this error before or have some idea of what I can do?  I'm 
assuming that it's telling me there's a syntax error on line 38 of the file 
icbs2_isc_sysent.c, but coming from C++ (not C) I've never worked with macros 
and am not sure how I would go about fixing and unterminated one.  Thanks for 
the help!
Cheers
b.timm


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: PRoblem with kernel compilation

[John Bleichert]

On Thu, 12 Dec 2002, Radoslaw Bolforski wrote:

> Date: Thu, 12 Dec 2002 21:08:07 +0100 (CET)
> From: Radoslaw Bolforski <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: PRoblem with kernel compilation
> 
> Hi!
> 
> I have a very slow machine (p133 and 16mb ram) when I compile the freebsd
> kernel I have some error when kernel is linking:
> 
> linking kernel
> kbd.o: In function `kbd_register':
> kbd.o(.text+0x35c): undefined reference to `kbddriver_set'
> kbd.o(.text+0x363): undefined reference to `kbddriver_set'
> kbd.o: In function `kbd_get_switch':
> kbd.o(.text+0x49d): undefined reference to `kbddriver_set'
> kbd.o(.text+0x4a2): undefined reference to `kbddriver_set'
> kbd.o: In function `kbd_configure':
> kbd.o(.text+0x77b): undefined reference to `kbddriver_set'
> kbd.o(.text+0x780): more undefined references to `kbddriver_set' follow
> *** Error code 1
> 
> Stop in /usr/src/sys/compile/HOME.
> 
> 

Looks like maybe you've forgotten to include (or more likely erroneosuly 
deleted) support for a keyboard? Can you post your kernel config here?

#  John Bleichert 
#  http://vonbek.dhs.org/latest.jpg


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

PRoblem with kernel compilation

[Radoslaw Bolforski]

Hi!

I have a very slow machine (p133 and 16mb ram) when I compile the freebsd
kernel I have some error when kernel is linking:

linking kernel
kbd.o: In function `kbd_register':
kbd.o(.text+0x35c): undefined reference to `kbddriver_set'
kbd.o(.text+0x363): undefined reference to `kbddriver_set'
kbd.o: In function `kbd_get_switch':
kbd.o(.text+0x49d): undefined reference to `kbddriver_set'
kbd.o(.text+0x4a2): undefined reference to `kbddriver_set'
kbd.o: In function `kbd_configure':
kbd.o(.text+0x77b): undefined reference to `kbddriver_set'
kbd.o(.text+0x780): more undefined references to `kbddriver_set' follow
*** Error code 1

Stop in /usr/src/sys/compile/HOME.


Thanks from the moutain ;-)
Radoslaw Bolforski
[EMAIL PROTECTED]

#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ./LINT configuration file. If you are
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.49 2002/10/12 15:25:13 kuriyama Exp $

machine i386
cpu I386_CPU
cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident   GENERIC
maxusers128

#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols

#optionsMATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
#optionsINET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big directories
#optionsMFS #Memory Filesystem
#optionsMD_ROOT #MD is a potential root device
#optionsNFS #Network Filesystem
#optionsNFS_ROOT#NFS usable as root device, NFS required
#optionsMSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660 required
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
#optionsSCSI_DELAY=15000#Delay (in ms) before probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
#optionsAHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
#optionsAHD_REG_PRETTY_PRINT# Print register bitfields in debug 
# output.  Adds ~215k to driver.

# To make an SMP kernel, the next two are needed
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O

device  isa
device  eisa
device  pci

# Floppy drives
#device fdc0at isa? port IO_FD1 irq 6 drq 2
#device fd0 at fdc0 drive 0
#device fd1 at fdc0 drive 1
#
# If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy,
# don't use the above line for fdc0 but the following one:
#device fdc0

# ATA and ATAPI devices
device  ata0at isa? port IO_WD1 irq 14
device  ata1at isa? port IO_WD2 irq 15
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options 

Re: extracting kernel compilation options

[paul beard]

Doug Poland wrote:


Hi Paul,

Thanks for the tip.  I suppose it goes without saying that if a kernel
is not compiled with this option, then the config is not available.



My guess is that's case. I have been stung by this and now do it 
all the time, hang the extra kernel size.

--
Paul Beard / 8040 27th Ave NE / Seattle WA 98115 /
paulbeard [at] mac [ dot] com / 206 529 8400

weblog @ 

In the force if Yoda's so strong, construct a sentence with words in
the proper order then why can't he?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: extracting kernel compilation options

[Doug Poland]

paul beard said:
> Doug Poland wrote:
>> I need to see what options a kernel was compiled with.  I
>> remember a few years back that there is a command that will show
>> you all the kernel options and devices.  Does anyone know how to
>> do that?
>>
>
> You can compile in that option:
>
> options INCLUDE_CONFIG_FILE  # Include this file in
> kernel
>
> and use this to extract it later:
> strings -n 3 /kernel | sed -n 's/^___//p' > MYKERNEL
>
Hi Paul,

Thanks for the tip.  I suppose it goes without saying that if a kernel
is not compiled with this option, then the config is not available.

-- 
Regards,
Doug



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: extracting kernel compilation options

[paul beard]

Doug Poland wrote:

Hello,

I need to see what options a kernel was compiled with.  I remember a
few years back that there is a command that will show you all the
kernel options and devices.  Does anyone know how to do that?



You can compile in that option:

options INCLUDE_CONFIG_FILE  # Include this file in kernel

and use this to extract it later:
strings -n 3 /kernel | sed -n 's/^___//p' > MYKERNEL

--
Paul Beard / 8040 27th Ave NE / Seattle WA 98115 /
paulbeard [at] mac [ dot] com / 206 529 8400

weblog @ 

Surprise due today.  Also the rent.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

extracting kernel compilation options

[Doug Poland]

Hello,

I need to see what options a kernel was compiled with.  I remember a
few years back that there is a command that will show you all the
kernel options and devices.  Does anyone know how to do that?

-- 
Regards,
Doug





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

kernel compilation error (emergency)

[z x]

>From: "Rodrigo Reis" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: kernel compilation error (emergency)
>Date: Thu, 26 Sep 2002 06:34:53 -0700
>
>hi,
>
>I`m trying to put up ipfw to work in my computer. I followed the directions 
>in placing the lines in the kernel:
>
>options IPFIREWALL
>options IPFIREWALL_VERBOSE
>options IPFIREWALL_DEFAULT_TO ACCEPT
>
>now i have tried removing or simply commenting the "default to accept" 
>line, since what i want is to deny all.
>
>now when running # make buildkernel (...)
>i get errors like this:
>
>/TMP/ccX10334.s : 2462 : ERROR : subtraction of two symbols in different 
>sections "Idle PTD" {. data section} - "KERNBASE" {*UND* section} at file 
>address 1554
>
>this is one of many similar error lines that appear (with some different 
>numbers and file addresses)
>
>and at the end I get a :
>
>***Error Code 1
>
>stop in /usr/obj/usr/src/sys/GENERIC.
>***Error Code 1
>
>stop in /usr/src.
>***Error code 1
>
>stop in /usr/src.
>
>
>
>
>
>please, i looked for this and couldn`t find a solution.
>i appreciate your help
>
>R.
>
>
>House music all night long...
>http://www.housemusic.com
>
>
>-
>Express yourself with a super cool email address from BigMailBox.com.
>Hundreds of choices. It's free!
>http://www.bigmailbox.com
>-




_
Tenha você também um MSN Hotmail, o maior webmail do mundo: 
http://www.hotmail.com/br


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[twig les]

Yes I'd like to announce my idiocy to the
world...sigh.  I cvs'd to stable today (during Mystery
Science Theater 3000 as promised) and built everything
just fine.  My kernel built in a few easy steps like
before, and now I am proud to say I have nice, tinny
sound coming from my laptop (crappy speakers-whole
'nother problem).

The one thing I noticed is that after CVSing to stable
I did another diff on my FW kernel against GENERIC and
FW had a bunch of stuff that GENERIC didn't.  So it
seems that 4.6Release (what I was initially running)
and had some stuff in its GENERIC that wasn't in
Stable's GENERIC.  I'm not sure, hectic week.

Again, thnx for the steady stream of common sense.


--- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 20, 2002 at 06:59:59PM -0700, twig les
> wrote:
> > I did that, it just found another line to error on
> > until I did the cp GENERIC FW and manually added
> the
> > lines I wanted.  I must have corrupted the file
> > somehow (it didn't screw itself up).  Now the new
> > error is something odd.  I think I'm going to
> remake
> > world in case I screwed something up.
> 
> Are you really trying to upgrade to 5.0-CURRENT? 
> You've got at least
> part of a 5.0-CURRENT source tree.
> 
> Kris
> 

> ATTACHMENT part 2 application/pgp-signature 



=
---
Heavy metal made me do it.
---

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[Kris Kennaway]

On Fri, Sep 20, 2002 at 06:59:59PM -0700, twig les wrote:
> I did that, it just found another line to error on
> until I did the cp GENERIC FW and manually added the
> lines I wanted.  I must have corrupted the file
> somehow (it didn't screw itself up).  Now the new
> error is something odd.  I think I'm going to remake
> world in case I screwed something up.

Are you really trying to upgrade to 5.0-CURRENT?  You've got at least
part of a 5.0-CURRENT source tree.

Kris



msg02444/pgp0.pgp
Description: PGP signature

Re: kernel compilation failure, ack!

[Giorgos Keramidas]

On 2002-09-20 18:00, twig les <[EMAIL PROTECTED]> wrote:
> L# cd /usr/src
> L# make buildkernel KERNCONF=FW
> make: no target to make.
> "/usr/src/Makefile.inc1", line 140: warning: "make -f
> /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> CPUTYPE" returned non-zero status

Hmmm, it looks like you are trying to build -current on a 4.x system.
Is that so?  That would explain the following error:

> --
> ===> FW
> mkdir -p /usr/obj/usr/src/sys
> cd /usr/src/sys/i386/conf; 
> 
>PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
>  config  -d /usr/obj/usr/src/sys/FW 
> /usr/src/sys/i386/conf/FW
> /usr/src/sys/i386/conf/FW:256: option
> "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
> ../../conf/files: coda/coda_fbsd.c must be optional,
> mandatory or standard
> Your version of config(8) is out of sync with your
> kernel source.
> *** Error code 1

You have to complete successfully a "make buildworld" before using
"make buildkernel".  Or update config(8) before trying to buildkernel.

Giorgos.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[twig les]

I would like to say yes because I know that that is
the correct procedure, but right now I'm on the 6th
straight hour of a retarded phone call and I can't
remember.  I'll remake world tomorrow during Mystery
Science Theater 3000.  At least then if the problem
persists I'll be in a good mood.  Thanks again, if I
find an answer I'll post it.

--- Dru <[EMAIL PROTECTED]> wrote:
> 
> 
> On Fri, 20 Sep 2002, twig les wrote:
> 
> > Well you caught me.  I had a bunch of garbage in
> my FW
> > file that I never put there (not intentionally).
> So I
> > did a quick cp GENERIC FW, added my lines and
> redid
> > the diff.  This is what I got:
> >
> >
> > L# pwd
> > /usr/src/sys/i386/conf
> > L# diff GENERIC FW
> > 251a252,261
> > >
> > > #To enable IPFW with default deny all packets
> > > options IPFIREWALL
> > > options IPFIREWALL_VERBOSE
> > > options IPFIREWALL_VERBOSE_LIMIT=10
> > > options TCP_DROP_SYNFIN #drop
> TCP
> > packets with SYN+FIN
> > > options IPFIREWALL_VERBOSE_LIMIT=100
> > #limit verbosity
> > >
> > > #device pcm0 at isa? irq5 drq 1 flags
> 0x0
> > >
> > L#
> >
> >
> > So I gained heart and pushed onward, only to see
> this
> > error:
> >
> > L# cd /usr/src
> > L# make buildkernel KERNCONF=FW
> > make: no target to make.
> > "/usr/src/Makefile.inc1", line 140: warning: "make
> -f
> > /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> > CPUTYPE" returned non-zero status
> >
> >
>
--
> > >>> Kernel build for FW started on Fri Sep 20
> 17:55:43
> > PDT 2002
> >
>
--
> > ===> FW
> > mkdir -p /usr/obj/usr/src/sys
> > cd /usr/src/sys/i386/conf;
> >
>
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> >  config  -d /usr/obj/usr/src/sys/FW
> > /usr/src/sys/i386/conf/FW
> > /usr/src/sys/i386/conf/FW:256: option
> > "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to
> 10
> > ../../conf/files: coda/coda_fbsd.c must be
> optional,
> > mandatory or standard
> > Your version of config(8) is out of sync with your
> > kernel source.
> > *** Error code 1
> 
> 
> OK, how exactly did you do your cvsup and rebuild?
> e.g., did you:
> 
> cvsup
> make -j4 buildworld
> make buildkernel  (where this was GENERIC)
> make installkernel
> make installworld
> reboot
> 
> then try your own kernel?
> 
> Dru
> 


=
---
Heavy metal made me do it.
---

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[twig les]

I did that, it just found another line to error on
until I did the cp GENERIC FW and manually added the
lines I wanted.  I must have corrupted the file
somehow (it didn't screw itself up).  Now the new
error is something odd.  I think I'm going to remake
world in case I screwed something up.

--- Giorgos Keramidas <[EMAIL PROTECTED]>
wrote:
> On 2002-09-20 20:42, Dru <[EMAIL PROTECTED]>
> wrote:
> > On Fri, 20 Sep 2002, twig les wrote:
> > >
> > > The error I get is thus:
> > >
> > > L# make buildkernel KERNCONF=FW
> > > make: no target to make.
> > > "/usr/src/Makefile.inc1", line 140: warning:
> "make -f
> > > /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> > > CPUTYPE" returned non-zero status
> > >
> > >
>
--
> > > >>> Kernel build for FW started on Fri Sep 20
> 16:56:19
> > > PDT 2002
> > >
>
--
> > > ===> FW
> > > mkdir -p /usr/obj/usr/src/sys
> > > cd /usr/src/sys/i386/conf;
> > >
>
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> > >  config  -d /usr/obj/usr/src/sys/FW
> > > /usr/src/sys/i386/conf/FW
> > > /usr/src/sys/i386/conf/FW:260: option
> "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
> > > /usr/src/sys/i386/conf/FW:56: unknown option
> "ICMP_BANDLIM"
> > > *** Error code 1
> 
> Read carefully the second from last line above. 
> This is the last
> error message that is printed by make, before it
> aborts.
> 
> The solution should be obvious :)
> 
> Remove or comment out the ICMP_BANDLIM option at
> line 56 of the FW
> configuration file and try again.
> 
> Giorgos.


=
---
Heavy metal made me do it.
---

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[Giorgos Keramidas]

On 2002-09-20 20:42, Dru <[EMAIL PROTECTED]> wrote:
> On Fri, 20 Sep 2002, twig les wrote:
> >
> > The error I get is thus:
> >
> > L# make buildkernel KERNCONF=FW
> > make: no target to make.
> > "/usr/src/Makefile.inc1", line 140: warning: "make -f
> > /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> > CPUTYPE" returned non-zero status
> >
> > --
> > >>> Kernel build for FW started on Fri Sep 20 16:56:19
> > PDT 2002
> > --
> > ===> FW
> > mkdir -p /usr/obj/usr/src/sys
> > cd /usr/src/sys/i386/conf;
> > 
>PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> >  config  -d /usr/obj/usr/src/sys/FW
> > /usr/src/sys/i386/conf/FW
> > /usr/src/sys/i386/conf/FW:260: option "IPFIREWALL_VERBOSE_LIMIT" redefined from 
>100 to 10
> > /usr/src/sys/i386/conf/FW:56: unknown option "ICMP_BANDLIM"
> > *** Error code 1

Read carefully the second from last line above.  This is the last
error message that is printed by make, before it aborts.

The solution should be obvious :)

Remove or comment out the ICMP_BANDLIM option at line 56 of the FW
configuration file and try again.

Giorgos.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[Dru]

On Fri, 20 Sep 2002, twig les wrote:

> Well you caught me.  I had a bunch of garbage in my FW
> file that I never put there (not intentionally). So I
> did a quick cp GENERIC FW, added my lines and redid
> the diff.  This is what I got:
>
>
> L# pwd
> /usr/src/sys/i386/conf
> L# diff GENERIC FW
> 251a252,261
> >
> > #To enable IPFW with default deny all packets
> > options IPFIREWALL
> > options IPFIREWALL_VERBOSE
> > options IPFIREWALL_VERBOSE_LIMIT=10
> > options TCP_DROP_SYNFIN #drop TCP
> packets with SYN+FIN
> > options IPFIREWALL_VERBOSE_LIMIT=100
> #limit verbosity
> >
> > #device pcm0 at isa? irq5 drq 1 flags 0x0
> >
> L#
>
>
> So I gained heart and pushed onward, only to see this
> error:
>
> L# cd /usr/src
> L# make buildkernel KERNCONF=FW
> make: no target to make.
> "/usr/src/Makefile.inc1", line 140: warning: "make -f
> /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> CPUTYPE" returned non-zero status
>
> --
> >>> Kernel build for FW started on Fri Sep 20 17:55:43
> PDT 2002
> --
> ===> FW
> mkdir -p /usr/obj/usr/src/sys
> cd /usr/src/sys/i386/conf;
> 
>PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
>  config  -d /usr/obj/usr/src/sys/FW
> /usr/src/sys/i386/conf/FW
> /usr/src/sys/i386/conf/FW:256: option
> "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
> ../../conf/files: coda/coda_fbsd.c must be optional,
> mandatory or standard
> Your version of config(8) is out of sync with your
> kernel source.
> *** Error code 1


OK, how exactly did you do your cvsup and rebuild? e.g., did you:

cvsup
make -j4 buildworld
make buildkernel(where this was GENERIC)
make installkernel
make installworld
reboot

then try your own kernel?

Dru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[twig les]

Well you caught me.  I had a bunch of garbage in my FW
file that I never put there (not intentionally). So I
did a quick cp GENERIC FW, added my lines and redid
the diff.  This is what I got:


L# pwd
/usr/src/sys/i386/conf
L# diff GENERIC FW
251a252,261
> 
> #To enable IPFW with default deny all packets
> options IPFIREWALL
> options IPFIREWALL_VERBOSE
> options IPFIREWALL_VERBOSE_LIMIT=10
> options TCP_DROP_SYNFIN #drop TCP
packets with SYN+FIN
> options IPFIREWALL_VERBOSE_LIMIT=100   
#limit verbosity
> 
> #device pcm0 at isa? irq5 drq 1 flags 0x0
> 
L# 


So I gained heart and pushed onward, only to see this
error:

L# cd /usr/src
L# make buildkernel KERNCONF=FW
make: no target to make.
"/usr/src/Makefile.inc1", line 140: warning: "make -f
/dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
CPUTYPE" returned non-zero status

--
>>> Kernel build for FW started on Fri Sep 20 17:55:43
PDT 2002
--
===> FW
mkdir -p /usr/obj/usr/src/sys
cd /usr/src/sys/i386/conf; 
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 config  -d /usr/obj/usr/src/sys/FW 
/usr/src/sys/i386/conf/FW
/usr/src/sys/i386/conf/FW:256: option
"IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
../../conf/files: coda/coda_fbsd.c must be optional,
mandatory or standard
Your version of config(8) is out of sync with your
kernel source.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
L# 


Now I'm scratching my head trying to figure out how to
update my configure (I tried pkg_version and its not
there).  Sigh.  Thanks for the lead, any additional
help will gain you a smile.



--- Dru <[EMAIL PROTECTED]> wrote:
> 
> 
> On Fri, 20 Sep 2002, twig les wrote:
> 
> > Hello *, for weeks I haven't been able to cut a
> new
> > kernel, which means I can't add my sound driver
> (pcm0)
> > which means I can't get one more step toward the
> goal
> > of replacing all windows tasks in my life with
> BSD.
> > The error I get is thus:
> >
> > L# make buildkernel KERNCONF=FW
> > make: no target to make.
> > "/usr/src/Makefile.inc1", line 140: warning: "make
> -f
> > /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> > CPUTYPE" returned non-zero status
> >
> >
>
--
> > >>> Kernel build for FW started on Fri Sep 20
> 16:56:19
> > PDT 2002
> >
>
--
> > ===> FW
> > mkdir -p /usr/obj/usr/src/sys
> > cd /usr/src/sys/i386/conf;
> >
>
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> >  config  -d /usr/obj/usr/src/sys/FW
> > /usr/src/sys/i386/conf/FW
> > /usr/src/sys/i386/conf/FW:260: option
> > "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to
> 10
> > /usr/src/sys/i386/conf/FW:56: unknown option
> > "ICMP_BANDLIM"
> > *** Error code 1
> >
> > Stop in /usr/src.
> > *** Error code 1
> >
> > Stop in /usr/src.
> > L#
> >
> >
> > 
> >
> > Now I just cvs'd the source because I was
> desperate so
> > my new uname -a is:
> >
> > L# uname -a
> > FreeBSD L.liza.com 4.6.2-RELEASE-p2 FreeBSD
> > 4.6.2-RELEASE-p2 #0: Mon Sep 16 13:41:26 PDT 2002
> > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FW.safe  i386
> > L#
> >
> >
> > I have no idea why this started happening.  I
> built a
> > custom kernel about 1.5 months ago and it works
> fine.
> > This FW kernel I'm trying to build is simply
> GENERIC
> > with some well-known options added for IPFW, plus
> now
> > I'm adding the pcm0 line.  Regardless, when I try
> to
> > compile GENERIC it fails.  Please help me, I've
> put a
> > ton of time into getting my laptop just where I
> want
> > it...so close to Valhalla...so close
> 
> 
> Can you send the list the output of:
> 
> cd /usr/src/sys/i386/conf
> diff GENERIC FW
> 
> Dru
> 


=
---
Heavy metal made me do it.
---

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: kernel compilation failure, ack!

[Dru]

On Fri, 20 Sep 2002, twig les wrote:

> Hello *, for weeks I haven't been able to cut a new
> kernel, which means I can't add my sound driver (pcm0)
> which means I can't get one more step toward the goal
> of replacing all windows tasks in my life with BSD.
> The error I get is thus:
>
> L# make buildkernel KERNCONF=FW
> make: no target to make.
> "/usr/src/Makefile.inc1", line 140: warning: "make -f
> /dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
> CPUTYPE" returned non-zero status
>
> --
> >>> Kernel build for FW started on Fri Sep 20 16:56:19
> PDT 2002
> --
> ===> FW
> mkdir -p /usr/obj/usr/src/sys
> cd /usr/src/sys/i386/conf;
> 
>PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
>  config  -d /usr/obj/usr/src/sys/FW
> /usr/src/sys/i386/conf/FW
> /usr/src/sys/i386/conf/FW:260: option
> "IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
> /usr/src/sys/i386/conf/FW:56: unknown option
> "ICMP_BANDLIM"
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> L#
>
>
> 
>
> Now I just cvs'd the source because I was desperate so
> my new uname -a is:
>
> L# uname -a
> FreeBSD L.liza.com 4.6.2-RELEASE-p2 FreeBSD
> 4.6.2-RELEASE-p2 #0: Mon Sep 16 13:41:26 PDT 2002
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FW.safe  i386
> L#
>
>
> I have no idea why this started happening.  I built a
> custom kernel about 1.5 months ago and it works fine.
> This FW kernel I'm trying to build is simply GENERIC
> with some well-known options added for IPFW, plus now
> I'm adding the pcm0 line.  Regardless, when I try to
> compile GENERIC it fails.  Please help me, I've put a
> ton of time into getting my laptop just where I want
> it...so close to Valhalla...so close


Can you send the list the output of:

cd /usr/src/sys/i386/conf
diff GENERIC FW

Dru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

kernel compilation failure, ack!

[twig les]

Hello *, for weeks I haven't been able to cut a new
kernel, which means I can't add my sound driver (pcm0)
which means I can't get one more step toward the goal
of replacing all windows tasks in my life with BSD. 
The error I get is thus:

L# make buildkernel KERNCONF=FW
make: no target to make.
"/usr/src/Makefile.inc1", line 140: warning: "make -f
/dev/null -m /usr/src/share/mk  CPUTYPE=dummy -V
CPUTYPE" returned non-zero status

--
>>> Kernel build for FW started on Fri Sep 20 16:56:19
PDT 2002
--
===> FW
mkdir -p /usr/obj/usr/src/sys
cd /usr/src/sys/i386/conf; 
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 config  -d /usr/obj/usr/src/sys/FW 
/usr/src/sys/i386/conf/FW
/usr/src/sys/i386/conf/FW:260: option
"IPFIREWALL_VERBOSE_LIMIT" redefined from 100 to 10
/usr/src/sys/i386/conf/FW:56: unknown option
"ICMP_BANDLIM"
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
L# 




Now I just cvs'd the source because I was desperate so
my new uname -a is:

L# uname -a
FreeBSD L.liza.com 4.6.2-RELEASE-p2 FreeBSD
4.6.2-RELEASE-p2 #0: Mon Sep 16 13:41:26 PDT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/FW.safe  i386
L# 


I have no idea why this started happening.  I built a
custom kernel about 1.5 months ago and it works fine. 
This FW kernel I'm trying to build is simply GENERIC
with some well-known options added for IPFW, plus now
I'm adding the pcm0 line.  Regardless, when I try to
compile GENERIC it fails.  Please help me, I've put a
ton of time into getting my laptop just where I want
it...so close to Valhalla...so close

=
---
Heavy metal made me do it.
---

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message