Re: Running an Old Kernel

[Martin McCormick]

"b. f." writes:
> On 6/25/10, b. f.  wrote:
> Looking at Matthew Seaman's earlier response, I find that his
> suggestion to make  changes to ${PREFIX}/etc/pam.d/sudo is more
> appropriate than my guess above.  But you probably need to look into
> the details, because judging from the comments in the
> ${PREFIX}/etc/pam.d/sudo.default file, there seems to be some
> subtleties involving sudo and pam_lastlog.  Look at the pertinent
> manpages, the sudo docs, and:
> 
> http://www.freebsd.org/doc/en/articles/pam/index.html

I do not believe any longer that this has anything to do
with the FreeBSD version or patch level or the kernel. I have
not solved the problem yet, but someone sent me a message off
list with several good suggestions for comparing files on one
system to those on another. I began to test to see which of our
existing systems show the last login message and which do not.

The fortunate thing is that there are several FreeBSD
systems spread out over 3 campuses. All run FreeBSD6.3 at the
same patch level. Three out of the 6 work normally. The other 3
also work normally except for that "last login" message.

The FreeBSD8.0 system that also shows the message is
patterned after one of the systems that is also displaying the
unwanted message.

The 3 systems that show the message are all essentially
copies of each other so I am unwittingly copying  the behavior
even across FreeBSD versions.

I expect to find the corruption in /usr/local
as that is the one directory tree in which many files and
scripts from the old system are copied to the new system. I may
be accidentally getting some libraries or some of /usr/local/bin
that should not come across.

I will post a message when I find out because this
behavior should not be happening.

Martin McCormick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Running an Old Kernel

[b. f.]

On 6/25/10, b. f.  wrote:
> On 6/25/10, b. f.  wrote:
>> Martin McCormick wrote:
>>> I have been attempting to shut off that "last login" message
>>> that occurs on some FreeBSD systems every time one runs a sudo
>>> command. I decided to bring back the last kernel which was the
> ...
>> Why on earth are you tinkering with your kernels in order to change
>> sudo output?  You should instead be editing configuration files
>> associated with sudo and related base system utilities, or patching
>> sudo.
>
> I should be more specific: I think you should be able to disable the
> message by commenting out the lines that refer to pam_lastlog.so in
> /etc/pam.d/system, /etc/pam.d/xdm, and /etc/pam.d/telnetd.  But in
> doing so, you will lose some of the security and accounting benefits
> of last(1) and friends.  Is it really worth it, just to silence some
> console messages? In any event, don't tinker with your kernel because
> of this.  It won't help, and it may break your system.

Looking at Matthew Seaman's earlier response, I find that his
suggestion to make  changes to ${PREFIX}/etc/pam.d/sudo is more
appropriate than my guess above.  But you probably need to look into
the details, because judging from the comments in the
${PREFIX}/etc/pam.d/sudo.default file, there seems to be some
subtleties involving sudo and pam_lastlog.  Look at the pertinent
manpages, the sudo docs, and:

http://www.freebsd.org/doc/en/articles/pam/index.html

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Running an Old Kernel

[Martin McCormick]

"b. f." writes:
> Why on earth are you tinkering with your kernels in order to change
> sudo output?  You should instead be editing configuration files
> associated with sudo and related base system utilities, or patching
> sudo.

Absolutely. I couldn't remember if this happened with the
original kernel so I wanted to put it back long enough to see if
the problem went away. If it is gone under the original kernel
and here with the patched kernel, this might tell me something
useful. I have a 8.0 system here that has a patched kernel that
is a little older and it does not exhibit that behavior. Sudo is
configured exactly the same way on both systems.

The environment looks the same. This really makes no sense so
there is something different on the system with the problem and
I just have not found it yet.

Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Running an Old Kernel

[b. f.]

On 6/25/10, b. f.  wrote:
> Martin McCormick wrote:
>> I have been attempting to shut off that "last login" message
>> that occurs on some FreeBSD systems every time one runs a sudo
>> command. I decided to bring back the last kernel which was the
...
> Why on earth are you tinkering with your kernels in order to change
> sudo output?  You should instead be editing configuration files
> associated with sudo and related base system utilities, or patching
> sudo.

I should be more specific: I think you should be able to disable the
message by commenting out the lines that refer to pam_lastlog.so in
/etc/pam.d/system, /etc/pam.d/xdm, and /etc/pam.d/telnetd.  But in
doing so, you will lose some of the security and accounting benefits
of last(1) and friends.  Is it really worth it, just to silence some
console messages? In any event, don't tinker with your kernel because
of this.  It won't help, and it may break your system.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Running an Old Kernel

[b. f.]

Martin McCormick wrote:
> I have been attempting to shut off that "last login" message
> that occurs on some FreeBSD systems every time one runs a sudo
> command. I decided to bring back the last kernel which was the
> original Generic kernel from the FreeBSD distribution disk for
> FreeBSD8.0 to see if the problem went away. If it did, that
> would indicate that the problem starts after one applies the
> latest patches and rebuilds the kernel.
>
>     The handbook covers building a new kernel very well, but
> I appear to be missing something. In /boot is loader and
> loader.old. Isn't loader.old the image of the previous kernel? I
> copied loader to loader.new since it should be the current image
> and then copied loader.old to loader and rebooted.
>

I don't think you've read the sections regarding kernel very
carefully.  The loader is built and installed as part of buildworld
and installworld, not buildkernel or installkernel.  It is not the
kernel, which is usually installed in /boot/kernel, with the old
kernel usually being moved to /boot/kernel.old when a new kernel is
installed.

> The "last login" message was still there and dmesg still
> showed the production date of the new kernel. In other words,
> nothing changed.
>
> Shouldn't I have seen the production date of the
> original kernel? Thank you.
>
> I have actually built many kernels and most were simply
> a rebuild of the generic kernel after applying patches so I
> don't roll back a kernel very often. Fortunately, both the old
> and new kernels work. I think the "last login" nuisance started
> right after installing the patched kernel.
>

Why on earth are you tinkering with your kernels in order to change
sudo output?  You should instead be editing configuration files
associated with sudo and related base system utilities, or patching
sudo.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Running an Old Kernel

[Martin McCormick]

I have been attempting to shut off that "last login" message
that occurs on some FreeBSD systems every time one runs a sudo
command. I decided to bring back the last kernel which was the
original Generic kernel from the FreeBSD distribution disk for
FreeBSD8.0 to see if the problem went away. If it did, that
would indicate that the problem starts after one applies the
latest patches and rebuilds the kernel.

The handbook covers building a new kernel very well, but
I appear to be missing something. In /boot is loader and
loader.old. Isn't loader.old the image of the previous kernel? I
copied loader to loader.new since it should be the current image
and then copied loader.old to loader and rebooted.

The "last login" message was still there and dmesg still
showed the production date of the new kernel. In other words,
nothing changed.

Shouldn't I have seen the production date of the
original kernel? Thank you.

I have actually built many kernels and most were simply
a rebuild of the generic kernel after applying patches so I
don't roll back a kernel very often. Fortunately, both the old
and new kernels work. I think the "last login" nuisance started
right after installing the patched kernel.

Martin McCormick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

kernel module krpc required for zfs on amd64, but not needed on ia64?

[Anton Shterenlikht]

On ia64 to get zfs I only need to have
makeoptions MODULES_OVERRIDE="opensolaris zfs"
in the kernel config:

# kldstat
Id Refs AddressSize Name
 19 0xe400 cc6688   kernel
 21 0xe4cc8000 1ff4a8   zfs.ko
 32 0xe4ec8000 14b60opensolaris.ko



On amd64 it seems one also needs krpc kernel module:

KLD zfs.ko: depends on krpc - not available or version mismatch

Is this expected?

Perhaps on ia64 krpc is included via some other
kernel config option?

many thanks

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Building amd64 kernel problems (missing kernel configuration files)

[b. f.]

> I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64
> kernel.
>
> I have copied /usr/src/sys/amd64/conf/GENERIC to
> /usr/src/sys/amd64/conf/JERRY

Support for cross-building is limited in the FreeBSD base system.
/usr/src/Makefile states:

"# If TARGET=machine (e.g. ia64, sparc64, ...) is specified you can
# cross build world for other machine types using the buildworld target,
# and once the world is built you can cross build a kernel using the
# buildkernel target."


but there are unwritten limitations, and this requires some care.
See, for example, developers running into problems even with i386 -->
amd64:

http://bsdimp.blogspot.com/2006/09/cross-building-freebsd.html

The fact that you are asking how to do this on the freebsd-questions
list probably means that you should _not_ be cross-building.

_Don't_ try to run an amd64 kernel with i386 world, or vice versa.
With some patches and tweaking you may get a few things to work, but
you're asking for trouble.

It would be better to get an amd64 installation disk, back up your
data, and do a re-installation from scratch, or at least a binary
upgrade of the existing base system, and then build a custom kernel
and world, if that's what you want to do.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Building amd64 kernel problems (missing kernel configuration files)

[Adam Vande More]

On Wed, Jun 9, 2010 at 8:38 PM, Jerry Bell  wrote:

> I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64
> kernel.
>
> I have copied /usr/src/sys/amd64/conf/GENERIC to
> /usr/src/sys/amd64/conf/JERRY
>
> Then, I run "make buildkernel KERNCONF=JERRY" in /usr/src and get the
> following error:
> ERROR: Missing kernel configuration file(s) (JERRY).
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
> It seems to want JERRY to be in i386/conf.  If I copy JERRY to i386/conf
> and
> run "make buildkernel KERNCONF=JERRY", I get the following error:
> --
> >>> Kernel build for JERRY started on Wed Jun  9 20:50:30 EDT 2010
> --
> ===> JERRY
> mkdir -p /usr/obj/usr/src/sys
>
> --
> >>> stage 1: configuring the kernel
> --
> cd /usr/src/sys/i386/conf;
>
> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> config  -d /usr/obj/usr/src/sys/JERRY  /usr/src/sys/i386/conf/JERRY
> /usr/src/sys/i386/conf/JERRY: unknown option "HAMMER"
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
> I know I'm missing something simple, but can't quite figure out what it is.
>



I think you have to set TARGET_ARCH=amd64

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Building amd64 kernel problems (missing kernel configuration files)

[Jerry Bell]

 Hello,

I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64
kernel.

I have copied /usr/src/sys/amd64/conf/GENERIC to
/usr/src/sys/amd64/conf/JERRY

Then, I run "make buildkernel KERNCONF=JERRY" in /usr/src and get the
following error:
ERROR: Missing kernel configuration file(s) (JERRY).
*** Error code 1

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

Stop in /usr/src.


It seems to want JERRY to be in i386/conf.  If I copy JERRY to i386/conf and
run "make buildkernel KERNCONF=JERRY", I get the following error:
------
>>> Kernel build for JERRY started on Wed Jun  9 20:50:30 EDT 2010
--
===> JERRY
mkdir -p /usr/obj/usr/src/sys

--
>>> stage 1: configuring the kernel
--
cd /usr/src/sys/i386/conf;
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
config  -d /usr/obj/usr/src/sys/JERRY  /usr/src/sys/i386/conf/JERRY
/usr/src/sys/i386/conf/JERRY: unknown option "HAMMER"
*** Error code 1

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

Stop in /usr/src.


I know I'm missing something simple, but can't quite figure out what it is.

Thanks,

Jerry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel: calcru: runtime went backwards

[Lowell Gilbert]

Frank Bonnet  writes:

> OK thank you Antonio :-)

Also, see the FAQ entry if you haven't already.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel: calcru: runtime went backwards

[Frank Bonnet]

OK thank you Antonio :-)


On 06/08/2010 03:11 PM, Antonio Vieiro wrote:
> This may be of help:
> 
> http://forums.freebsd.org/archive/index.php/t-2805.html
> 
> Cheers,
> Antonio
> 
> 2010/6/8 Frank Bonnet :
>> Hello All
>>
>> since few days I get those messages into console and /var/log/messages
>>
>> The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu
>> related but I am a bit confused in it.
>>
>> Does any guru could show me the light on how to stop those messages
>> if possible , this has side effects on Dovecot IMAP server that kill
>> himself when it trap that kind of error messages.
>>
>>
>> Thank you
>>
>>
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1721
>> usec to 1377 usec for pid 684 (rpc.lockd)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 528
>> usec to 459 usec for pid 678 (rpc.statd)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1928
>> usec to 1906 usec for pid 643 (ypbind)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 2241
>> usec to 1793 usec for pid 643 (ypbind)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 9373
>> usec to 7545 usec for pid 628 (rpcbind)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 556
>> usec to 539 usec for pid 538 (devd)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 12152
>> usec to 9722 usec for pid 538 (devd)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 287
>> usec to 229 usec for pid 143 (adjkerntz)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec
>> to 14 usec for pid 42 (sctp_iterator)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 711
>> usec to 569 usec for pid 39 (irq15: ata1)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec
>> to 40 usec for pid 36 (usb3)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec
>> to 31 usec for pid 35 (usb2)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1325
>> usec to 1060 usec for pid 23 (swi6: task queue)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 21246
>> usec to 20041 usec for pid 2 (g_event)
>> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 8572
>> usec to 7530 usec for pid 0 (swapper)
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

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

Re: kernel: calcru: runtime went backwards

[Antonio Vieiro]

This may be of help:

http://forums.freebsd.org/archive/index.php/t-2805.html

Cheers,
Antonio

2010/6/8 Frank Bonnet :
> Hello All
>
> since few days I get those messages into console and /var/log/messages
>
> The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu
> related but I am a bit confused in it.
>
> Does any guru could show me the light on how to stop those messages
> if possible , this has side effects on Dovecot IMAP server that kill
> himself when it trap that kind of error messages.
>
>
> Thank you
>
>
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1721
> usec to 1377 usec for pid 684 (rpc.lockd)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 528
> usec to 459 usec for pid 678 (rpc.statd)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1928
> usec to 1906 usec for pid 643 (ypbind)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 2241
> usec to 1793 usec for pid 643 (ypbind)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 9373
> usec to 7545 usec for pid 628 (rpcbind)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 556
> usec to 539 usec for pid 538 (devd)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 12152
> usec to 9722 usec for pid 538 (devd)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 287
> usec to 229 usec for pid 143 (adjkerntz)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec
> to 14 usec for pid 42 (sctp_iterator)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 711
> usec to 569 usec for pid 39 (irq15: ata1)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec
> to 40 usec for pid 36 (usb3)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec
> to 31 usec for pid 35 (usb2)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1325
> usec to 1060 usec for pid 23 (swi6: task queue)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 21246
> usec to 20041 usec for pid 2 (g_event)
> Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 8572
> usec to 7530 usec for pid 0 (swapper)
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

kernel: calcru: runtime went backwards

[Frank Bonnet]

Hello All

since few days I get those messages into console and /var/log/messages

The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu
related but I am a bit confused in it.

Does any guru could show me the light on how to stop those messages
if possible , this has side effects on Dovecot IMAP server that kill
himself when it trap that kind of error messages.


Thank you


Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1721
usec to 1377 usec for pid 684 (rpc.lockd)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 528
usec to 459 usec for pid 678 (rpc.statd)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1928
usec to 1906 usec for pid 643 (ypbind)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 2241
usec to 1793 usec for pid 643 (ypbind)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 9373
usec to 7545 usec for pid 628 (rpcbind)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 556
usec to 539 usec for pid 538 (devd)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 12152
usec to 9722 usec for pid 538 (devd)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 287
usec to 229 usec for pid 143 (adjkerntz)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec
to 14 usec for pid 42 (sctp_iterator)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 711
usec to 569 usec for pid 39 (irq15: ata1)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec
to 40 usec for pid 36 (usb3)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec
to 31 usec for pid 35 (usb2)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 1325
usec to 1060 usec for pid 23 (swi6: task queue)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 21246
usec to 20041 usec for pid 2 (g_event)
Jun  8 10:16:34 mail kernel: calcru: runtime went backwards from 8572
usec to 7530 usec for pid 0 (swapper)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD 8.0 linux emulator kernel panic

[Pieter de Goeje]

On Sunday 06 June 2010 19:31:00 Bogdan Webb wrote:
> I'm having issues with the Fedora Core6 linux emulator on FreeBSD 8.0 it
> panics when i run HLDS, the same issue was addressed by Daniel Ballenger in
> http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/054646.html
>but i did not get the fix. Giovanni Trematerra gave a response that it was
> fix in a "r200768" now it is clear that i do not know that that code means
> (in my eyes it's a bsd build or smth) but i'm currently running the latest
> 8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic.

r200768 uniquely identifies a single change to the FreeBSD source code. In 
this case it identifies a bugfix to linux_signal.c.

You need to run 8-STABLE (currently it will show up as 8.1-PRERELEASE) to get 
the fix. I know it works because I also run multiple HLDS processes on 
FreeBSD.

To get 8-STABLE: cvsup/csup the sources to RELENG_8, then follow these 
instructions to upgrade:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

Good luck!

--
Pieter de Goeje
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

FreeBSD 8.0 linux emulator kernel panic

[Bogdan Webb]

I'm having issues with the Fedora Core6 linux emulator on FreeBSD 8.0 it
panics when i run HLDS, the same issue was addressed by Daniel Ballenger in
http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/054646.htmlbut
i did not get the fix. Giovanni Trematerra gave a response that it was
fix in a "r200768" now it is clear that i do not know that that code means
(in my eyes it's a bsd build or smth) but i'm currently running the latest
8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel build fails - ".depend", line 27905: Need an operator --- SOLVED

[Peter Cornelius]

Re.

lest I forget.

> (...) I now will build
> world & kernel and hope that it'll come out fine.

And so it did.

  kldxref /boot/kernel

The kernel runs now. So back to my ezjails.

Thanks to all,

Rgds.,

Peter.
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel build fails - ".depend", line 27905: Need an operator

[Peter Cornelius]

Re...

> Can you build GENERIC?

Yes.

However.

I just diff'ed against GENERIC, switched any option on/off that was different 
to GENERIC, without any change. Finally,

[r...@netserv /usr/src/sys/i386/conf]# mv NETSERV NETSERV.bakk
[r...@netserv /usr/src/sys/i386/conf]# cp -p GENERIC NETSERV
[r...@netserv /usr/src/sys/i386/conf]# ( cd /usr/src/ && make kernel 
KERNCONF=NETSERV )
------
>>> Kernel build for NETSERV started on Wed May 26 06:19:45 UTC 2010
--
===> NETSERV
mkdir -p /usr/obj/usr/Src-RELENG_8/sys

--
>>> stage 1: configuring the kernel
--
cd /usr/Src-RELENG_8/sys/i386/conf;  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/Src-RELENG_8/sys/NETSERV  
/usr/Src-RELENG_8/sys/i386/conf/NETSERV
Kernel build directory is /usr/obj/usr/Src-RELENG_8/sys/NETSERV
Don't forget to do ``make cleandepend && make depend''

--
>>> stage 2.1: cleaning up the object tree
--
cd /usr/obj/usr/Src-RELENG_8/sys/NETSERV; MAKEOBJDIRPREFIX=/usr/obj  
MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
GROFF_BIN_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/groff_font  
GROFF_TMAC_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/tmac  
_SHLIBDIRPREFIX=/usr/obj/usr/Src-RELENG_8/tmp  VERSION="FreeBSD 8.0-STABLE i386 
800505"  INSTALL="sh /usr/Src-RELENG_8/tools/install.sh"  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 NO_CTF=1 make KERNEL=kernel cleandir
".depend", line 27905: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1

Stop in /usr/Src-RELENG_8.
*** Error code 1

Stop in /usr/Src-RELENG_8.

I just built from that KERNCONF !!! as long as it was named GENERIC, all was 
fine!

Now, that's time for the big bat, then.

[r...@netserv /usr/src/sys/i386/conf]# rm -rf /usr/obj/usr/Src-RELENG_8

And all of a sudden, life seems well again, see below. I now will build world & 
kernel and hope that it'll come out fine.

So thanks to all who wasted their time with me,

All the best regards,

Peter.

---

[r...@netserv /usr/src/sys/i386/conf]# mv NETSERV.bakk NETSERV
[r...@netserv /usr/src/sys/i386/conf]# ( cd /usr/src/ && make kernel 
KERNCONF=NETSERV )

--
>>> Kernel build for NETSERV started on Wed May 26 06:26:40 UTC 2010
--
===> NETSERV
mkdir -p /usr/obj/usr/Src-RELENG_8/sys

--
>>> stage 1: configuring the kernel
--
cd /usr/Src-RELENG_8/sys/i386/conf;  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/Src-RELENG_8/sys/NETSERV  
/usr/Src-RELENG_8/sys/i386/conf/NETSERV
Kernel build directory is /usr/obj/usr/Src-RELENG_8/sys/NETSERV
Don't forget to do ``make cleandepend && make depend''

--
>>> stage 2.1: cleaning up the object tree
--
cd /usr/obj/usr/Src-RELENG_8/sys/NETSERV; MAKEOBJDIRPREFIX=/usr/obj  
MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
GROFF_BIN_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/groff_font  
GROFF_TMAC_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/tmac  
_SHLIBDIRPREFIX=/usr/obj/usr/Src-RELENG_8/tmp  VERSION="FreeBSD 8.0-STABLE i386 
800505"  INSTALL="sh /usr/Src-RELENG_8/tools/install.sh"  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/

Re: kernel build fails - ".depend", line 27905: Need an operator

[Lowell Gilbert]

"Peter Cornelius"  writes:

> Re.
>
>> > do the makebuildworld first.
>> 
>> That's odd - I even *installed* world without any issue?

You installed world without a new kernel?
That would be a good way to make unnecessary trouble for yourself.  

>> Will try now anyways, though. Life's a mystery.
>
> Nope, no change.
>
> Any other ideas?

Can you build GENERIC?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel build fails - ".depend", line 27905: Need an operator

[Peter Cornelius]

Re.

> > do the makebuildworld first.
> 
> That's odd - I even *installed* world without any issue?
> 
> Will try now anyways, though. Life's a mystery.

Nope, no change.

Any other ideas?

Thanks,

Peter.
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel build fails - ".depend", line 27905: Need an operator

[Peter Cornelius]

Estimado Jorge,

> do the makebuildworld first.

That's odd - I even *installed* world without any issue?

Will try now anyways, though. Life's a mystery.

Gracias por apoyar,

Saludos cordiales,

Peter.
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel build fails - ".depend", line 27905: Need an operator

[Jorge Medina]

On Tue, May 25, 2010 at 11:00 AM, Peter Cornelius  wrote:
> Dear list,
>
> This probably is obvious but I don't seem to be able to figure out where I 
> should look in order to learn why I can't compile the bloomin' kernel, pse 
> see below.
>
> Every time I update my KERNCONF, I try to remember to keep a copy of GENERIC 
> so I can diff against the updated one. This diff shows no change hence I 
> believe my KERNCONF is in order. Which I did not expect since the running 
> kernel is not that old:
>
> FreeBSD 8.0-STABLE #17: Thu May  6 10:21:19 UTC 2010
>
> I also read that config(8) was updated so I finally tried to remake world 
> hoping that that's where it comes from but (well in agreement with my 
> expectations that /usr/src should be self-contained :)) without avail.
>
> Any enlightenment appreciated...
>
> Thanks all,
>
> All the best,
>
> Peter.
>
> ---
>
> P.S.: Is it still worthwhile to report lock order reversals on 8-STABLE?
>
> ---
>
> [r...@netserv /usr/src]# ( DISPLAY="" cvsup -Pm ~/etc/cvsup.netserv.src-all 
> && cd /usr/src/ && make kernel KERNCONF=NETSERV )
> Connected to cvsup4.de.FreeBSD.org
> Updating collection src-all/cvs
> Finished successfully
>
> --
>>>> Kernel build for NETSERV started on Tue May 25 14:35:46 UTC 2010
> ------
> ===> NETSERV
> mkdir -p /usr/obj/usr/Src-RELENG_8/sys
>
> --
>>>> stage 1: configuring the kernel
> --
> cd /usr/Src-RELENG_8/sys/i386/conf;  
> PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
>   config  -d /usr/obj/usr/Src-RELENG_8/sys/NETSERV  
> /usr/Src-RELENG_8/sys/i386/conf/NETSERV
> Kernel build directory is /usr/obj/usr/Src-RELENG_8/sys/NETSERV
> Don't forget to do ``make cleandepend && make depend''
>
> --
>>>> stage 2.1: cleaning up the object tree
> --
> cd /usr/obj/usr/Src-RELENG_8/sys/NETSERV; MAKEOBJDIRPREFIX=/usr/obj  
> MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
> GROFF_BIN_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin  
> GROFF_FONT_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/groff_font  
> GROFF_TMAC_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/tmac  
> _SHLIBDIRPREFIX=/usr/obj/usr/Src-RELENG_8/tmp  VERSION="FreeBSD 8.0-STABLE 
> i386 800505"  INSTALL="sh /usr/Src-RELENG_8/tools/install.sh"  
> PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
>  NO_CTF=1 make KERNEL=kernel cleandir
> ".depend", line 27905: Need an operator
> make: fatal errors encountered -- cannot continue
> *** Error code 1
>
> Stop in /usr/Src-RELENG_8.
> *** Error code 1
>
> Stop in /usr/Src-RELENG_8.
>
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>

do the makebuildworld first.

-- 
Jorge Andrés Medina Oliva.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

kernel build fails - ".depend", line 27905: Need an operator

[Peter Cornelius]

Dear list,

This probably is obvious but I don't seem to be able to figure out where I 
should look in order to learn why I can't compile the bloomin' kernel, pse see 
below.

Every time I update my KERNCONF, I try to remember to keep a copy of GENERIC so 
I can diff against the updated one. This diff shows no change hence I believe 
my KERNCONF is in order. Which I did not expect since the running kernel is not 
that old:

FreeBSD 8.0-STABLE #17: Thu May  6 10:21:19 UTC 2010

I also read that config(8) was updated so I finally tried to remake world 
hoping that that's where it comes from but (well in agreement with my 
expectations that /usr/src should be self-contained :)) without avail.

Any enlightenment appreciated...

Thanks all,

All the best,

Peter.

---

P.S.: Is it still worthwhile to report lock order reversals on 8-STABLE?

---

[r...@netserv /usr/src]# ( DISPLAY="" cvsup -Pm ~/etc/cvsup.netserv.src-all && 
cd /usr/src/ && make kernel KERNCONF=NETSERV )
Connected to cvsup4.de.FreeBSD.org
Updating collection src-all/cvs
Finished successfully

------
>>> Kernel build for NETSERV started on Tue May 25 14:35:46 UTC 2010
--
===> NETSERV
mkdir -p /usr/obj/usr/Src-RELENG_8/sys

------
>>> stage 1: configuring the kernel
--
cd /usr/Src-RELENG_8/sys/i386/conf;  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/Src-RELENG_8/sys/NETSERV  
/usr/Src-RELENG_8/sys/i386/conf/NETSERV
Kernel build directory is /usr/obj/usr/Src-RELENG_8/sys/NETSERV
Don't forget to do ``make cleandepend && make depend''

--
>>> stage 2.1: cleaning up the object tree
--
cd /usr/obj/usr/Src-RELENG_8/sys/NETSERV; MAKEOBJDIRPREFIX=/usr/obj  
MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
GROFF_BIN_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/groff_font  
GROFF_TMAC_PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/share/tmac  
_SHLIBDIRPREFIX=/usr/obj/usr/Src-RELENG_8/tmp  VERSION="FreeBSD 8.0-STABLE i386 
800505"  INSTALL="sh /usr/Src-RELENG_8/tools/install.sh"  
PATH=/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/legacy/usr/games:/usr/obj/usr/Src-RELENG_8/tmp/usr/sbin:/usr/obj/usr/Src-RELENG_8/tmp/usr/bin:/usr/obj/usr/Src-RELENG_8/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 NO_CTF=1 make KERNEL=kernel cleandir
".depend", line 27905: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1

Stop in /usr/Src-RELENG_8.
*** Error code 1

Stop in /usr/Src-RELENG_8.

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Fw: qemu error mounting cd and no internet connection with custom kernel

[Heshmat Ismail]

--- On Sun, 5/23/10, Heshmat Ismail  wrote:

From: Heshmat Ismail 
Subject: qemu error mounting cd and no internet connection with custom kernel
To: freebsd-emulat...@freebsd.org
Date: Sunday, May 23, 2010, 8:35 PM

Hi all,
I have  built and installed a custom kernel on a freebsd 8.0-RELEASE machine 
(host os),then i installed qemu from the packages and used the following 
commands:-
# qemu-img create -f qcow2 freebsd.image 10G
# qemu -m 256 -hda freebsd.image -cdrom /dev/acd0 -boot d
# qemu freebsd.image
So, the  guest os is the same as the host os and i installed it from the same 
DVD (freebsd 8.0-RELEASE).
I face two problems with the guest os (the host os is working fine):-
Problem#1
When i try to install any packages from the DVD by running 
# sysinstall
   =>configure=>packages=>Install from freebsd CD/DVD
i got : Error
 mounting /dev/acd0 on /dist: Input/output error (5).
Problem#2
I put these lines in /etc/rc.conf:
hald_enable="YES"
dbus_enable="YES"
ifconfig_ed0="DHCP"
but i can not connect to the internet (the above configuration in the host os 
works fine).When i use the GENERIC kernel i get no problems.Here are the 
differences between the two kernels,the GENERIC and MYKERNEL.  


# cd /usr/src/sys/i386/conf
# diff -u GENERIC MYKERNEL
--- GENERIC 2009-11-09 23:48:01.0
 +
+++ MYKERNEL    2010-05-12 17:06:41.0 +
@@ -1,4 +1,4 @@
-#
+
 # GENERIC -- Generic kernel configuration file for FreeBSD/i386
 #
 # For more information on this file, please read the config(5) manual page,
@@ -18,10 +18,10 @@
 #
 # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 
kensmith Exp $
 
-cpu    I486_CPU
-cpu    I586_CPU
+#cpu   I486_CPU
+#cpu  
 I586_CPU
 cpu    I686_CPU
-ident  GENERIC
+ident  MYKERNEL
 
 # To statically compile in device wiring instead of /boot/device.hints
 #hints "GENERIC.hints" # Default places to look for devices.
@@ -42,30 +42,30 @@
 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_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    NFSLOCKD    # Network Lock Manager
-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   NFSCLIENT   # Network Filesystem Client
+#options   NFSSERVER   # Network Filesystem Server
+#options  
 NFSLOCKD    # Network Lock Manager
+#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 (sgtty)
-options    COMPAT_FREEBSD4 # Compatible with FreeBSD4
-options    COMPAT_FREEBSD5 # Compatible with
 FreeBSD5
-options    COMPAT_FREEBSD6 # Compatible with FreeBSD6
+#options   COMPAT_FREEBSD4 # Compatible with FreeBSD4
+#options   COMPAT_FREEBSD5 # Compatible with FreeBSD5
+#options   COMPAT_FREEBSD6 # Compatible with FreeBSD6
 options    COMPAT_FREEBSD7 # Compatible with FreeBSD7
-options    SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
-options   
 KTRACE  # ktrace(1) support
+#options   SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
+#options   KTRACE  # ktrace(1) support
 options    STACK   # stack(9) support
 options    SYSVSHM # SYSV-style shared memory
-options   
 SYSVMSG # SYSV-style message queues
-options    SYSVSEM # SYSV-style semaphores
+#options   SYSVMSG # SYSV-style message queues
+#options   SYSVSEM

[solved] startx couldn't create cookie with custom kernel

[Heshmat Ismail]

Hi all,

I enabled device random in my kernel configuration file , rebuilt and installed 
my kernel , now startx works flawlessly , thank you Alexander Best and thank 
you all.

Heshmat Ismail



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

Re: startx couldn't create cookie with custom kernel

[Alexander Best]

you need to re-enable "device random". X needs it.

-- 
Alexander Best
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: startx couldn't create cookie with custom kernel

[Chuck Swiger]

Hi--

On May 13, 2010, at 9:34 AM, Heshmat Ismail wrote:
> -cpuI486_CPU
> -cpuI586_CPU
> +#cpu   I486_CPU
> +#cpu   I586_CPU
>  cpuI686_CPU

You don't really want to disable these.  There are some kernel optimizations 
which are only enabled if I586_CPU is set, and are not enabled even if I686_CPU 
is set.  In particular, look at i386/i386/support.s

Regards,
-- 
-Chuck

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

Fw: Re: startx couldn't create cookie with custom kernel

[Heshmat Ismail]

--- On Thu, 5/13/10, Heshmat Ismail  wrote:

From: Heshmat Ismail 
Subject: Re: startx couldn't create cookie with custom kernel
To: "Yuri Pankov" 
Date: Thursday, May 13, 2010, 1:19 PM

# cd /usr/src/sys/i386/conf
# diff -u GENERIC MYKERNEL
--- GENERIC 2009-11-09 23:48:01.0 +
+++ MYKERNEL    2010-05-12 17:06:41.0 +
@@ -1,4 +1,4 @@
-#
+
 # GENERIC -- Generic kernel configuration file for FreeBSD/i386
 #
 # For more information on this file, please read the config(5) manual page,
@@ -18,10 +18,10 @@
 #
 # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 
kensmith Exp $
 
-cpu    I486_CPU
-cpu    I586_CPU
+#cpu   I486_CPU
+#cpu  
 I586_CPU
 cpu    I686_CPU
-ident  GENERIC
+ident  MYKERNEL
 
 # To statically compile in device wiring instead of /boot/device.hints
 #hints "GENERIC.hints" # Default places to look for devices.
@@ -42,30 +42,30 @@
 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_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    NFSLOCKD    # Network Lock Manager
-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   NFSCLIENT   # Network Filesystem Client
+#options   NFSSERVER   # Network Filesystem Server
+#options  
 NFSLOCKD    # Network Lock Manager
+#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 (sgtty)
-options    COMPAT_FREEBSD4 # Compatible with FreeBSD4
-options    COMPAT_FREEBSD5 # Compatible with
 FreeBSD5
-options    COMPAT_FREEBSD6 # Compatible with FreeBSD6
+#options   COMPAT_FREEBSD4 # Compatible with FreeBSD4
+#options   COMPAT_FREEBSD5 # Compatible with FreeBSD5
+#options   COMPAT_FREEBSD6 # Compatible with FreeBSD6
 options    COMPAT_FREEBSD7 # Compatible with FreeBSD7
-options    SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
-options   
 KTRACE  # ktrace(1) support
+#options   SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
+#options   KTRACE  # ktrace(1) support
 options    STACK   # stack(9) support
 options    SYSVSHM # SYSV-style shared memory
-options   
 SYSVMSG # SYSV-style message queues
-options    SYSVSEM # SYSV-style semaphores
+#options   SYSVMSG # SYSV-style message queues
+#options   SYSVSEM # SYSV-style semaphores
 options    P1003_1B_SEMAPHORES # POSIX-style semaphores
 options    _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
 extensions
 options    PRINTF_BUFR_SIZE=128    # Prevent printf output being 
interspersed.
@@ -84,86 +84,86 @@
 device cpufreq
 
 # Bus support.
-device acpi
-device eisa
+#device    acpi
+#device    eisa
 device pci
 
 # Floppy drives
-device fdc
+#device    fdc
 
 # ATA and ATAPI
 devices
 device ata
 device atadisk # ATA disk drives
-device ataraid # ATA RAID drives
+#device    ataraid # ATA RAID drives
 device atapicd # ATAPI CDROM drives
-device atapifd # ATAPI floppy drives
-device atapist # ATAPI tape
 drives
+#device    atapifd # ATAPI floppy drives
+#device    atapist # ATAPI tape drives
 options    ATA_STATIC_ID   # Static device numbering
 
 #

Re: 7.3-RELEASE: unable to compile custom kernel

[Antonio Kless]

That's right!
Thanks a lot, now it builts well.


2010/5/13 Lowell Gilbert 

> Antonio Kless  writes:
>
> > if_rum.o(.text+0x3868):/usr/src/sys/dev/usb/if_rum.c:2324: undefined
> > reference to `ieee80211_free_node'
>
> At a guess, you've got the rum device without wlan.
>
> --
> Lowell Gilbert, embedded/networking software engineer, Boston area
>
> http://be-well.ilk.org/~lowell/
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>



-- 
Best regards,
Antonio Kless,
http://kless.spb.ru/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: 7.3-RELEASE: unable to compile custom kernel

[Lowell Gilbert]

Antonio Kless  writes:

> if_rum.o(.text+0x3868):/usr/src/sys/dev/usb/if_rum.c:2324: undefined
> reference to `ieee80211_free_node'

At a guess, you've got the rum device without wlan.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: startx couldn't create cookie with custom kernel

[Yuri Pankov]

On Thu, May 13, 2010 at 03:54:21AM -0700, Heshmat Ismail wrote:
> I have built and installed a custom kernel on i386 machine with the
> 8-RELEASE then installed xorg from the DVD,when i ran startx i got:
> couldn't create cookie.When using GENERIC kernel startx works
> flawlessly,but with my custom kernel i got this error.
> 
> Heshmat Ismail

Post `diff -u GENERIC YOURKERNCONF` output please.


Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

startx couldn't create cookie with custom kernel

[Heshmat Ismail]

I have built and installed a custom kernel on i386 machine with the
8-RELEASE then installed xorg from the DVD,when i ran startx i got:
couldn't create cookie.When using GENERIC kernel startx works
flawlessly,but with my custom kernel i got this error.

Heshmat Ismail



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

Re: 7.3-RELEASE: unable to compile custom kernel

[Antonio Kless]

# make buildkernel KERNCONF=ALTERKERN
<...snip...>
MAKE=make sh /usr/src/sys/conf/newvers.sh
ALTERKERN

cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign
-fformat-extensions -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100
--param large-function-growth=1000  -mcmodel=kernel -mno-red-zone
-mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -Werror
vers.c
linking
kernel.debug

if_ural.o(.text+0x74d): In function
`ural_free_tx_list':

/usr/src/sys/dev/usb/if_ural.c:627: undefined reference to
`ieee80211_free_node'

if_ural.o(.text+0x8fc): In function
`ural_detach':

/usr/src/sys/dev/usb/if_ural.c:567: undefined reference to
`ieee80211_ifdetach'

if_ural.o(.text+0xd8c): In function
`ural_attach':

/usr/src/sys/dev/usb/if_ural.c:499: undefined reference to
`ieee80211_init_channels'

if_ural.o(.text+0xd94):/usr/src/sys/dev/usb/if_ural.c:501: undefined
reference to
`ieee80211_ifattach'

if_ural.o(.text+0xdac):/usr/src/sys/dev/usb/if_ural.c:513: undefined
reference to
`ieee80211_media_status'

if_ural.o(.text+0xe04):/usr/src/sys/dev/usb/if_ural.c:513: undefined
reference to
`ieee80211_media_init'

if_ural.o(.text+0xe1d):/usr/src/sys/dev/usb/if_ural.c:515: undefined
reference to
`ieee80211_amrr_init'

if_ural.o(.text+0xe88):/usr/src/sys/dev/usb/if_ural.c:531: undefined
reference to
`ieee80211_announce'

if_ural.o(.text+0x112c): In function
`ural_raw_xmit':

/usr/src/sys/dev/usb/if_ural.c:2402: undefined reference to
`ieee80211_free_node'

if_ural.o(.text+0x1178):/usr/src/sys/dev/usb/if_ural.c:2408: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x1306):/usr/src/sys/dev/usb/if_ural.c:2438: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x156d): In function
`ural_set_chan':

/usr/src/sys/dev/usb/if_ural.c:1823: undefined reference to
`ieee80211_chan2ieee'

if_ural.o(.text+0x1d25): In function
`ural_start':

/usr/src/sys/dev/usb/if_ural.c:1486: undefined reference to
`ieee80211_find_txnode'

if_ural.o(.text+0x1d59):/usr/src/sys/dev/usb/if_ural.c:1493: undefined
reference to
`ieee80211_encap'

if_ural.o(.text+0x1f29):/usr/src/sys/dev/usb/if_ural.c:1503: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x1f58):/usr/src/sys/dev/usb/if_ural.c:1479: undefined
reference to
`ieee80211_cancel_scan'

if_ural.o(.text+0x1f7a):/usr/src/sys/dev/usb/if_ural.c:1366: undefined
reference to
`ieee80211_crypto_encap'

if_ural.o(.text+0x21c6):/usr/src/sys/dev/usb/if_ural.c:1495: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x22bd): In function
`ural_txeof':

/usr/src/sys/dev/usb/if_ural.c:882: undefined reference to
`ieee80211_process_callback'

if_ural.o(.text+0x233d):/usr/src/sys/dev/usb/if_ural.c:901: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x2c14): In function
`ural_amrr_update':

/usr/src/sys/dev/usb/if_ural.c:2508: undefined reference to
`ieee80211_amrr_choose'

if_ural.o(.text+0x2cd3): In function
`ural_media_change':

/usr/src/sys/dev/usb/if_ural.c:705: undefined reference to
`ieee80211_media_change'

if_ural.o(.text+0x2e03): In function
`ural_ioctl':

/usr/src/sys/dev/usb/if_ural.c:1578: undefined reference to
`ieee80211_ioctl'

if_ural.o(.text+0x3111): In function
`ural_task':

/usr/src/sys/dev/usb/if_ural.c:755: undefined reference to
`ieee80211_beacon_alloc'

if_ural.o(.text+0x3289):/usr/src/sys/dev/usb/if_ural.c:2450: undefined
reference to
`ieee80211_amrr_node_init'

if_ural.o(.text+0x3883): In function
`ural_rxeof':

/usr/src/sys/dev/usb/if_ural.c:990: undefined reference to
`ieee80211_find_rxnode'

if_ural.o(.text+0x38b2):/usr/src/sys/dev/usb/if_ural.c:993: undefined
reference to
`ieee80211_input'

if_ural.o(.text+0x38ba):/usr/src/sys/dev/usb/if_ural.c:996: undefined
reference to
`ieee80211_free_node'

if_ural.o(.text+0x21af): In function
`ural_start':

/usr/src/sys/dev/usb/if_ural.c:1461: undefined reference to
`ieee80211_free_node'

if_rum.o(.text+0x8ad): In function
`rum_free_tx_list':

/usr/src/sys/dev/usb/if_rum.c:668: undefined reference to
`ieee80211_free_node'

if_rum.o(.text+0xa7f): In function
`rum_detach':

/usr/src/sys/dev/usb/if_rum.c:607: undefined reference to
`ieee80211_ifdetach'

if_rum.o(.text+0x12d5): In function
`rum_attach':

/usr/src/sys/dev/usb/if_rum.c:508: undefined reference to
`ieee80211_init_channels'

if_rum.o(.text+0x12f4):/usr/src/sys/dev/usb/if_rum.c:540: undefined
reference to
`ieee80211_ifattach'

if_r

Re: 7.3-RELEASE: unable to compile custom kernel

[Jiansong Liu]

Try to compile it again without the -j option, will help to figure out
where is going wrong exactly.

Cheers,
Jiansong




On Wed, May 12, 2010 at 5:50 PM, Antonio Kless  wrote:
> Hello. I trying to build custom kernel to enable packet-filter.
>
> # uname -a
> FreeBSD host.net 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC
> 2010     r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>
> # export
> declare -x BLOCKSIZE="K"
> declare -x FTP_PASSIVE_MODE="YES"
> declare -x HISTCONTROL="ignorespace"
> declare -x HOME="/root"
> declare -x LOGNAME="root"
> declare -x MAIL="/var/mail/root"
> declare -x MC_CONTROL_FILE="/tmp/mc.822.control"
> declare -x MC_CONTROL_PID="822"
> declare -x OLDPWD="/usr/src/sys/amd64"
> declare -x PAGER="more"
> declare -x
> PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin"
> declare -x PWD="/usr/src/sys/amd64/conf"
> declare -x SHELL="/usr/local/bin/bash"
> declare -x SHLVL="2"
> declare -x SSH_CLIENT=""
> declare -x SSH_CONNECTION=""
> declare -x SSH_TTY="/dev/ttyp0"
> declare -x TERM="xterm"
> declare -x USER="root"
>
> # pwd
> /usr/src/sys/amd64/conf
>
> # diff GENERIC
> ALTERKERN
>
> 22c22
>
> < ident
> GENERIC
>
> ---
>
>> ident
> ALTERKERN
>
> 43c43
>
> < options       NFS_ROOT                # NFS usable as /, requires
> NFSCLIENT
>
> ---
>
>> #options      NFS_ROOT                # NFS usable as /, requires
> NFSCLIENT
>
> 76a77,92
>
>> #
> PF
>
>> device          pf              # enable PF OpenBSD packet-filter
> firewall
>
>> device          pflog           # logging support interface for
> PF
>
>> device          pfsync          # Synchronization interface for
> PF
>
>> device          carp            # Common Address Redundancy
> Protocol
>
>>
>
>> # PF traffic
> shaper
>
>> options
> ALTQ
>
>> options         ALTQ_CBQ        # Class Bases
> Queueing
>
>> options         ALTQ_RED        # Random Early
> Detection
>
>> options         ALTQ_RIO        # RED
> In/Out
>
>> options         ALTQ_HFSC       # Hierarchical Packet
> Scheduler
>
>> options         ALTQ_CDNR       # Traffic
> conditioner
>
>> options         ALTQ_PRIQ       # Priority
> Queueing
>
>> options         ALTQ_NOPCC      # Required for SMP
> build
>
>>
>
> 238,252c254,268
>
> < device                wlan            # 802.11
> support
>
> < device                wlan_wep        # 802.11 WEP
> support
>
> < device                wlan_ccmp       # 802.11 CCMP
> support
>
> < device                wlan_tkip       # 802.11 TKIP
> support
>
> < device                wlan_amrr       # AMRR transmit rate control
> algorithm
>
> < device                wlan_scan_ap    # 802.11 AP mode
> scanning
>
> < device                wlan_scan_sta   # 802.11 STA mode scanning
> < device                an              # Aironet 4500/4800 802.11 wireless
> NICs.
> < device                ath             # Atheros pci/cardbus NIC's
> < device                ath_hal         # Atheros HAL (Hardware Access
> Layer)
> < options               AH_SUPPORT_AR5416       # enable AR5416 tx/rx
> descriptors
> < device                ath_rate_sample # SampleRate tx rate control for ath
> < device                awi             # BayStack 660 and others
> < device                ral             # Ralink Technology RT2500 wireless
> NICs.
> < device                wi              # WaveLAN/Intersil/Symbol 802.11
> wireless NICs.
> ---
>> #device               wlan            # 802.11 support
>> #device               wlan_wep        # 802.11 WEP support
>> #device               wlan_ccmp       # 802.11 CCMP support
>> #device               wlan_tkip       # 802.11 TKIP support
>> #device               wlan_amrr       # AMRR transmit rate control
> algorithm
>> #device               wlan_scan_ap    # 802.11 AP mode scanning
>> #device               wlan_scan_sta   # 802.11 STA mode scanning
>> #device               an              # Aironet 4500/4800 802.11 wireless
> NICs.
>> #device               ath             # Atheros pci/cardbus NIC's
>> #device               ath_hal         # Atheros HAL (Hardware Access
> Layer)
>> #options              AH_SUPPORT_AR5416       # enable AR5416 tx/rx
> de

7.3-RELEASE: unable to compile custom kernel

[Antonio Kless]

Hello. I trying to build custom kernel to enable packet-filter.

# uname -a
FreeBSD host.net 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC
2010 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

# export
declare -x BLOCKSIZE="K"
declare -x FTP_PASSIVE_MODE="YES"
declare -x HISTCONTROL="ignorespace"
declare -x HOME="/root"
declare -x LOGNAME="root"
declare -x MAIL="/var/mail/root"
declare -x MC_CONTROL_FILE="/tmp/mc.822.control"
declare -x MC_CONTROL_PID="822"
declare -x OLDPWD="/usr/src/sys/amd64"
declare -x PAGER="more"
declare -x
PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin"
declare -x PWD="/usr/src/sys/amd64/conf"
declare -x SHELL="/usr/local/bin/bash"
declare -x SHLVL="2"
declare -x SSH_CLIENT=""
declare -x SSH_CONNECTION=""
declare -x SSH_TTY="/dev/ttyp0"
declare -x TERM="xterm"
declare -x USER="root"

# pwd
/usr/src/sys/amd64/conf

# diff GENERIC
ALTERKERN

22c22

< ident
GENERIC

---

> ident
ALTERKERN

43c43

< options   NFS_ROOT# NFS usable as /, requires
NFSCLIENT

---

> #options  NFS_ROOT# NFS usable as /, requires
NFSCLIENT

76a77,92

> #
PF

> device  pf  # enable PF OpenBSD packet-filter
firewall

> device  pflog   # logging support interface for
PF

> device  pfsync  # Synchronization interface for
PF

> device  carp# Common Address Redundancy
Protocol

>

> # PF traffic
shaper

> options
ALTQ

> options ALTQ_CBQ# Class Bases
Queueing

> options ALTQ_RED# Random Early
Detection

> options ALTQ_RIO# RED
In/Out

> options ALTQ_HFSC   # Hierarchical Packet
Scheduler

> options ALTQ_CDNR   # Traffic
conditioner

> options ALTQ_PRIQ   # Priority
Queueing

> options ALTQ_NOPCC  # Required for SMP
build

>

238,252c254,268

< devicewlan# 802.11
support

< devicewlan_wep# 802.11 WEP
support

< devicewlan_ccmp   # 802.11 CCMP
support

< devicewlan_tkip   # 802.11 TKIP
support

< devicewlan_amrr   # AMRR transmit rate control
algorithm

< devicewlan_scan_ap# 802.11 AP mode
scanning

< devicewlan_scan_sta   # 802.11 STA mode scanning
< devicean  # Aironet 4500/4800 802.11 wireless
NICs.
< deviceath # Atheros pci/cardbus NIC's
< deviceath_hal # Atheros HAL (Hardware Access
Layer)
< options   AH_SUPPORT_AR5416   # enable AR5416 tx/rx
descriptors
< deviceath_rate_sample # SampleRate tx rate control for ath
< deviceawi # BayStack 660 and others
< deviceral # Ralink Technology RT2500 wireless
NICs.
< devicewi  # WaveLAN/Intersil/Symbol 802.11
wireless NICs.
---
> #device   wlan# 802.11 support
> #device   wlan_wep# 802.11 WEP support
> #device   wlan_ccmp   # 802.11 CCMP support
> #device   wlan_tkip   # 802.11 TKIP support
> #device   wlan_amrr   # AMRR transmit rate control
algorithm
> #device   wlan_scan_ap# 802.11 AP mode scanning
> #device   wlan_scan_sta   # 802.11 STA mode scanning
> #device   an  # Aironet 4500/4800 802.11 wireless
NICs.
> #device   ath # Atheros pci/cardbus NIC's
> #device   ath_hal # Atheros HAL (Hardware Access
Layer)
> #options  AH_SUPPORT_AR5416   # enable AR5416 tx/rx
descriptors
> #device   ath_rate_sample # SampleRate tx rate control for ath
> #device   awi # BayStack 660 and others
> #device   ral # Ralink Technology RT2500 wireless
NICs.
> #device   wi  # WaveLAN/Intersil/Symbol 802.11
wireless NICs.

# cd ../../../ && make -j16 buildkernel KERNCONF=ALTERKERN
<...snip...>
===> zyd
(all)

cc -O2 -fno-strict-aliasing -pipe  -D_KERNEL -DKLD_MODULE -std=c99
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/ALTERKERN/opt_global.h -I. -I@ -I@/contrib/altq
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
-I/usr/obj/usr/src/sys/ALTERKERN -mcmodel=kernel -mno-red-zone  -mfpmath=387
-mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -m

Re: Problem with Custom Kernel

[Tim Judd]

On 5/11/10, Heshmat Ismail  wrote:
> Dear Sir,
> My name is Heshmat Ismail.The output of uname-a is:-
> FreeBSD  8.0-RELEASE FreeBSD 8.0-RELEASE #12: Tue May 11 11:05:22 UTC
> 2010 heshmat@:/usr/obj/usr/src/sys/MYKERNEL  i386
> After I have built and installed my custom kernel  (MYKERNEL),i installed
> xorg and ran the command startx but i got: couldn't create cookie.What could
> be the problem with MYKERNEL? my kernel configuration file is attached with
> this message.
> Thanks,
> Heshmat Ismail
>


An XORG cookie is dealing with X authority, not with a kernel config.
Make sure all parts of xorg are installed.

Give us the scenario on what you do after login with all your commands
leading up to this error.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Problem with Custom Kernel

[Heshmat Ismail]

Dear Sir,
My name is Heshmat Ismail.The output of uname-a is:-
FreeBSD  8.0-RELEASE FreeBSD 8.0-RELEASE #12: Tue May 11 11:05:22 UTC 2010 
heshmat@:/usr/obj/usr/src/sys/MYKERNEL  i386
After I have built and installed my custom kernel  (MYKERNEL),i installed xorg 
and ran the command startx but i got: couldn't create cookie.What could be the 
problem with MYKERNEL? my kernel configuration file is attached with this 
message.
Thanks,
Heshmat Ismail



  

MYKERNEL
Description: Binary data
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: what does kernel option UWX_TRACE_ENABLE do?

[Anton Yuzhaninov]

On Thu, 6 May 2010 10:51:59 +0100, Anton Shterenlikht wrote:
AS> What does kernel option UWX_TRACE_ENABLE do?
AS> 
AS> I did a quick search on the net, but no help.
AS> 

from sys/ia64/conf/NOTES

# Build the unwinder with tracing support. This option is used to debug the
# unwinder itself and the glue around it.

-- 
WBR,
 Anton Yuzhaninov

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

what does kernel option UWX_TRACE_ENABLE do?

[Anton Shterenlikht]

What does kernel option UWX_TRACE_ENABLE do?

I did a quick search on the net, but no help.

many thanks
anton


-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: KSE (Kernel Supported Threading) support in FreeBSD 8.0

[Alejandro Imass]

On Tue, May 4, 2010 at 5:33 AM, Ivan Voras  wrote:
> On 05/04/10 00:38, Bruce Cran wrote:
[...]
>
> Note that only KSE was removed; threading is of course fully supported by
> other mechanisms.


Does anyone know of a paper(s) that compare the different threading
model of say FBSD, Linux and OpenSolaris, etc. ?

As a programmer, I know the basic theory and _effects_ of using
threads vs. processes vs. EDA/SEDA, etc., and in fact I use threads in
several applications, like Perl Gtk2 and also web-based software using
Apache mod_worker and mod_perl. But I haven't stumbled uppon
information that does a comparison of the different threading models
in the most popular Open Source OSs.

I have 'heard' people say the OpenSolaris' threading model is quite
different and supposedly better that other *nix´s in general, but is
that actualy true? Or is that just applied to Java? How would one know
especially in Open Source systems where you may have different
threading models (like in FBSD uthreads, kse, etc.)?

Thanks beforehand,
Alejandro Imass


>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: KSE (Kernel Supported Threading) support in FreeBSD 8.0

[Ivan Voras]

On 05/04/10 00:38, Bruce Cran wrote:

On Monday 03 May 2010 15:52:48 Traiano Welcome wrote:


  Is KSE support still in FreeBSD (8.0 and upward)?


No. KSE support was removed over 2 years ago:
http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084248.html


Note that only KSE was removed; threading is of course fully supported 
by other mechanisms.


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

Re: KSE (Kernel Supported Threading) support in FreeBSD 8.0

[Bruce Cran]

On Monday 03 May 2010 15:52:48 Traiano Welcome wrote:

>  Is KSE support still in FreeBSD (8.0 and upward)?

No. KSE support was removed over 2 years ago: 
http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084248.html

-- 
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

KSE (Kernel Supported Threading) support in FreeBSD 8.0

[Traiano Welcome]

Hi List

 Is KSE support still in FreeBSD (8.0 and upward)?

Thanks in Advance,
Traiano Welcome


NOTE: This e-mail message and all attachments thereto contain confidential 
information intended for a specific addressee and purpose. If you are not the 
addressee (a) you may not disclose, copy, distribute or take any action based 
on the contents hereof; (b) kindly inform the sender immediately and destroy 
all copies hereof. Any copying, publication or disclosure of this message, or 
part hereof, in any form whatsoever, without the sender's express written 
consent, is prohibited. No opinion expressed or implied by the sender 
necessarily constitutes the opinion of MTN. This message does not constitute a 
guarantee or proof of the facts mentioned herein. No Employee or intermediary 
is authorised to conclude a binding agreement on behalf of MTN Group Limited, 
or any of its subsidiary companies, by e-mail without the express written 
confirmation by a duly authorised representative of MTN Group Limited.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: lighten kernel

[harvey dent]

Ok
I understand.
Thank you very much for your answer.

On Mon, Apr 26, 2010 at 11:00 AM, Da Rock <
freebsd-questi...@herveybayaustralia.com.au> wrote:

> On Fri, 2010-04-23 at 07:09 +0200, xyz wrote:
> > Those numbers mean the size in mo, of linux kernel (3.2mo), and freebsd
> > kernel (33,9mo) for the same hardware configuration.
> >
>
> Linux is based more on a minimalist kernel with user mode modules - add
> the modules and you'll find its larger, or take away the modules out of
> the FreeBSD kernel to get a more accurate reading.
>
> FreeBSD uses kernel mode modules; so it makes it faster, but it makes
> the kernel "look" bigger.
>
> And to stave off a flame session, these comments are very subjective and
> many will argue on both sides, but the proof is in the pudding as far as
> I'm concerned - I run both and my linux is CRAP by my reckoning. My
> drivers on the linux break constantly, and render the system useless
> without a reboot (and I'm NOT saying that it is anywhere near as bad as
> Windows: if I only had a choice of the two the linux would win for
> stability). My FreeBSD's have NEVER needed rebooting except for
> extraordinary circumstances, and the top stats don't lie either.
>
> > Is it difficult to update the patch?
> >
> >
> > On 04/22/10 23:54, Paul B Mahol wrote:
> > > On 4/22/10, xyz  wrote:
> > >
> > >> Hi
> > >> Thank you for your answer
> > >> But "I can't believe" that lighten the kernel of useless drivers,
> saves
> > >> only few bytes, by removing whole useless modules (sound, ata/sata,
> agp...).
> > >> Furthermore, I think about free space that could be save too, in the
> > >> hard drive this time.
> > >> Why for the same configuration, linux kernel is lighter than the
> Freebsd
> > >> kernel? (3.2mo ; 33.9mo)
> > >>
> > > Can you be more specific? What those numbers mean?
> > >
> > >
> > >> And, can you release your patch please?
> > >>
> > > I can, but it may be out of sync.
> > >
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: lighten kernel

[Da Rock]

On Fri, 2010-04-23 at 07:09 +0200, xyz wrote:
> Those numbers mean the size in mo, of linux kernel (3.2mo), and freebsd 
> kernel (33,9mo) for the same hardware configuration.
> 

Linux is based more on a minimalist kernel with user mode modules - add
the modules and you'll find its larger, or take away the modules out of
the FreeBSD kernel to get a more accurate reading.

FreeBSD uses kernel mode modules; so it makes it faster, but it makes
the kernel "look" bigger.

And to stave off a flame session, these comments are very subjective and
many will argue on both sides, but the proof is in the pudding as far as
I'm concerned - I run both and my linux is CRAP by my reckoning. My
drivers on the linux break constantly, and render the system useless
without a reboot (and I'm NOT saying that it is anywhere near as bad as
Windows: if I only had a choice of the two the linux would win for
stability). My FreeBSD's have NEVER needed rebooting except for
extraordinary circumstances, and the top stats don't lie either.

> Is it difficult to update the patch?
> 
> 
> On 04/22/10 23:54, Paul B Mahol wrote:
> > On 4/22/10, xyz  wrote:
> >
> >> Hi
> >> Thank you for your answer
> >> But "I can't believe" that lighten the kernel of useless drivers, saves
> >> only few bytes, by removing whole useless modules (sound, ata/sata, 
> >> agp...).
> >> Furthermore, I think about free space that could be save too, in the
> >> hard drive this time.
> >> Why for the same configuration, linux kernel is lighter than the Freebsd
> >> kernel? (3.2mo ; 33.9mo)
> >>  
> > Can you be more specific? What those numbers mean?
> >
> >
> >> And, can you release your patch please?
> >>  
> > I can, but it may be out of sync.
> >
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


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

Re: lighten kernel

[Paul B Mahol]

On 4/23/10, xyz  wrote:
> Those numbers mean the size in mo, of linux kernel (3.2mo), and freebsd
> kernel (33,9mo) for the same hardware configuration.

My kernel is 2.8 MB and ~30 MB are modules (all of them).

> Is it difficult to update the patch?

Is it difficult to stop top posting.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: lighten kernel

[xyz]

Those numbers mean the size in mo, of linux kernel (3.2mo), and freebsd 
kernel (33,9mo) for the same hardware configuration.


Is it difficult to update the patch?


On 04/22/10 23:54, Paul B Mahol wrote:

On 4/22/10, xyz  wrote:
   

Hi
Thank you for your answer
But "I can't believe" that lighten the kernel of useless drivers, saves
only few bytes, by removing whole useless modules (sound, ata/sata, agp...).
Furthermore, I think about free space that could be save too, in the
hard drive this time.
Why for the same configuration, linux kernel is lighter than the Freebsd
kernel? (3.2mo ; 33.9mo)
 

Can you be more specific? What those numbers mean?

   

And, can you release your patch please?
 

I can, but it may be out of sync.
   

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

Re: lighten kernel

[Paul B Mahol]

On 4/22/10, xyz  wrote:
> Hi
> Thank you for your answer
> But "I can't believe" that lighten the kernel of useless drivers, saves
> only few bytes, by removing whole useless modules (sound, ata/sata, agp...).
> Furthermore, I think about free space that could be save too, in the
> hard drive this time.
> Why for the same configuration, linux kernel is lighter than the Freebsd
> kernel? (3.2mo ; 33.9mo)

Can you be more specific? What those numbers mean?

> And, can you release your patch please?

I can, but it may be out of sync.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: lighten kernel

[xyz]

Hi
Thank you for your answer
But "I can't believe" that lighten the kernel of useless drivers, saves 
only few bytes, by removing whole useless modules (sound, ata/sata, agp...).
Furthermore, I think about free space that could be save too, in the 
hard drive this time.
Why for the same configuration, linux kernel is lighter than the Freebsd 
kernel? (3.2mo ; 33.9mo)

And, can you release your patch please?

Best regards

On 04/21/10 21:02, Paul B Mahol wrote:

On 4/21/10, xyz  wrote:
   

Thank you for your answer.
But how I can only choose the intel agp driver, without all others by
puting "agp" in the kernel configuration file?
 

Currently you can not pick only intel agp code, agp module have
support for other vendors too.
I made patch but it was never committed because it saves only few
bytes of running kernel memory and thats all.
Because bunch of new agp* modules are created it increase kernel size
on disk, if you build all agp modules.

But if you have very little memory you better not to use Xorg and
direct rendering at all.
   

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

Re: lighten kernel

[Paul B Mahol]

On 4/21/10, xyz  wrote:
> Thank you for your answer.
> But how I can only choose the intel agp driver, without all others by
> puting "agp" in the kernel configuration file?

Currently you can not pick only intel agp code, agp module have
support for other vendors too.
I made patch but it was never committed because it saves only few
bytes of running kernel memory and thats all.
Because bunch of new agp* modules are created it increase kernel size
on disk, if you build all agp modules.

But if you have very little memory you better not to use Xorg and
direct rendering at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: lighten kernel

[Michael Powell]

xyz wrote:

> Thank you for your answer.
> But how I can only choose the intel agp driver, without all others by
> puting "agp" in the kernel configuration file?
> 

Please don't top post - it is bad form.

I think you may be confusing "agp" driver and video driver. The agp support 
in the kernel is for the agp slot on the motherboard chipset. If your 
motherboard uses an agp slot this is where an agp video card would be 
inserted. You would want this kernel support if such were the case.

Video drivers, on the other hand, are part of the Xorg installation. This is 
a third party software installed from the ports system. The "all the others" 
you mention are probably the myriad of video card drivers installed along 
with Xorg. For the most part, the bulk of this software is not kernel 
related; the exception(s) being certain kernel modules such as dri and 
nvidia. The "all the others" video drivers are not kernel related.

-Mike



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

Re: lighten kernel

[xyz]

Thank you for your answer.
But how I can only choose the intel agp driver, without all others by 
puting "agp" in the kernel configuration file?


On 04/21/10 15:20, Ivailo Tanusheff wrote:
As far as I understand this is one of the main reasons to make a 
custom kernel :)

So yes, you can do that if you do not need those kernel modules.

Regards,

Ivailo Tanusheff
Deputy Head of IT Department
ProCredit Bank (Bulgaria) AD



*xyz *
Sent by: owner-freebsd-questi...@freebsd.org

21.04.2010 15:54


To
freebsd-questions@freebsd.org
cc

Subject
    lighten kernel









Hi everybody

I want to build a custom kernel, because my pc doesn't have much memory.
So I would like reduce the size of the kernel load in the memory, to
save her.
My question is, is it possible to save more memory, by removing the
whole agp drivers, and keeping only the driver needed?
And so on for the rest of the drivers (sound, ...).drivers.

Thank you

Disclaimer: The information contained in this message is intended 
solely for the use of the individual or entity to whom it is addressed 
and to others authorised to receive it. It may contain confidential or 
legally privileged information. It you are not the intended recipient 
you are hereby notified that any disclosure, copying, distribution, or 
taking any action based on the contents of this message is strictly 
prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by responding to 
this e-mail and then delete it from your system. ProCredit Bank is 
neither liable for the proper and complete transmission for the 
information contained in this message nor for any delay in its receipt. 

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

Re: lighten kernel

[Ivailo Tanusheff]

As far as I understand this is one of the main reasons to make a custom 
kernel :)
So yes, you can do that if you do not need those kernel modules.

Regards,

Ivailo Tanusheff
Deputy Head of IT Department
ProCredit Bank (Bulgaria) AD




xyz  
Sent by: owner-freebsd-questi...@freebsd.org
21.04.2010 15:54

To
freebsd-questions@freebsd.org
cc

Subject
lighten kernel






Hi everybody

I want to build a custom kernel, because my pc doesn't have much memory. 
So I would like reduce the size of the kernel load in the memory, to 
save her.
My question is, is it possible to save more memory, by removing the 
whole agp drivers, and keeping only the driver needed?
And so on for the rest of the drivers (sound, ...).drivers.

Thank you

Disclaimer: The information contained in this message is intended solely 
for the use of the individual or entity to whom it is addressed and to 
others authorised to receive it. It may contain confidential or legally 
privileged information. It you are not the intended recipient you are 
hereby notified that any disclosure, copying, distribution, or taking any 
action based on the contents of this message is strictly prohibited and 
may be unlawful. If you have received this communication in error, please 
notify us immediately by responding to this e-mail and then delete it from 
your system. ProCredit Bank is neither liable for the proper and complete 
transmission for the information contained in this message nor for any 
delay in its receipt.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

lighten kernel

[xyz]

Hi everybody

I want to build a custom kernel, because my pc doesn't have much memory. 
So I would like reduce the size of the kernel load in the memory, to 
save her.
My question is, is it possible to save more memory, by removing the 
whole agp drivers, and keeping only the driver needed?

And so on for the rest of the drivers (sound, ...).drivers.

Thank you
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: Force reboot after kernel panic.

[Terrence Koeman]

> -Original Message-
> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
> questi...@freebsd.org] On Behalf Of Paul Halliday
> Sent: Tuesday, April 13, 2010 3:17 PM
> To: questi...@freebsd.org
> Subject: Force reboot after kernel panic.
> 
> How can I enforce this? Presently the system just hangs.

Add to kernconf:

options KDB_UNATTENDED

-- 
Regards,
T. Koeman, MTh/BSc/BPsy; Technical Monk

MediaMonks B.V. (www.mediamonks.com)
Please quote all replies in correspondence.


smime.p7s
Description: S/MIME cryptographic signature

Force reboot after kernel panic.

[Paul Halliday]

How can I enforce this? Presently the system just hangs.

Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Ian Smith]

On Fri, 9 Apr 2010, per...@pluto.rain.com wrote:
 > Ian Smith  wrote:
 > >  > >  http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
 > > 
 > > This is absolutely the worst section of an otherwise great
 > > handbook ...  Nothing short of a rewrite from scratch could
 > > fix it ...
 > 
 > As always, I'm sure a patch -- to provide that rewrite --
 > would be welcome.

You're quite right, of course.  It's a huge job, and I'm not sure I can 
do it; just picked up the latest chapter.sgml for another look.  I know 
I should STFU or fix it, but I can't help at least warning people who, 
unless they're at least familiar with ipfw(8), are going to be either 
put off or - in my view - misled or confused.

I'll see if I can't come up with at least some updates and corrections.

Thanks for the kick :)

cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Custom kernel & atheros

[harvey dent]

hi everybody
I try to make a custom kernel (for a "emachines" notebook), but i always get
this same error or a similar (dependent of choosing ath_hal or for example
ath_rf2425):

*ar2425.o(.text+0x582): In function
`ar2425RfAttach':

/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:691: undefined reference to
`ath_hal_malloc'

ar2425.o(.text+0x5d4):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:705:
undefined reference to
`ar5212GetNfAdjust'
ar2425.o(.text+0x614): In function
`ar2425RfDetach':

/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:674: undefined reference to
`ath_hal_free'

ar2425.o(.text+0x6fd): In function `ar2425SetRfRegs':
/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:193: undefined reference to
`ar5212ModifyRfBuffer'
ar2425.o(.text+0x725):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:194:
undefined reference to `ar5212ModifyRfBuffer'
ar2425.o(.text+0xa84): In function `ar2425SetChannel':
/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:99: undefined reference to
`ath_hal_reverseBits'
ar2425.o(.text+0xb4c):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:113:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xb62):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:115:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xbba):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:117:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xbd0):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:119:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xc21):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:121: more
undefined references to `ath_hal_reverseBits' follow
sample.o(.text+0x404): In function `ath_rate_sysctl_stats':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:916: undefined reference to
`ieee80211_iterate_nodes'
sample.o(.text+0x539): In function `calc_usecs_unicast_packet':
/usr/src/sys/dev/ath/ath_rate/sample/sample.h:236: undefined reference to
`ath_hal_computetxtime'
sample.o(.text+0x5b5):/usr/src/sys/dev/ath/ath_rate/sample/sample.h:246:
undefined reference to `ath_hal_computetxtime'
sample.o(.text+0x745): In function `ath_rate_newassoc':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:771: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x7ea):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:801:
undefined reference to `ieee80211_note'
sample.o(.text+0xcec): In function `update_stats':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:530: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x1040): In function `ath_rate_findrate':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:273: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x1216):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:316:
undefined reference to `ieee80211_note_mac'
sample.o(.text+0x160c): In function `ath_rate_tx_complete':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:572: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x16e3):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:590:
undefined reference to `ieee80211_note_mac'
sample.o(.text+0x18bc):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:636:
more undefined references to `ieee80211_note_mac' follow
*** Error code 1

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

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

Stop in /usr/src.*

I ran "config", and no problem were find.
When I build a GENERIC kernel, there's no any problem.

Here the uname -a:
*FreeBSD pcbsd-8040 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan  5
16:02:27 UTC 2010
r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
i386
*
Here the kernel config file:

*#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the config(5) manual page,
# and/or 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$

cpuI686_CPU
identPCBSD1

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

# Use the following to compile in values accessible to the kernel
# through getenv() (or kenv(1) in userland). The format of the file
# is 'variable=value', see kenv(1)
#
# env"GENERIC.env"

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

Re: Kernel Config for NAT

[perryh]

Ian Smith  wrote:
>  > >  http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
> 
> This is absolutely the worst section of an otherwise great
> handbook ...  Nothing short of a rewrite from scratch could
> fix it ...

As always, I'm sure a patch -- to provide that rewrite --
would be welcome.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Ian Smith]

On Fri, 9 Apr 2010, Robert Huff wrote:
 > Ian Smith writes:
 > 
 > >   >So ... double-checking I'm doing this right:
 > >   > 
 > >   > 1) in /boot/loader.conf:
 > >   > 
 > >   > ipfw_load="YES"
 > >   > ipdivert_load="YES"
 > >  
 > >  I thought from your earlier mail that you wanted to use in-kernel
 > >  NAT?
 > 
 >  I want whatever works.  :-)

natd works, as ever.  ipfw nat is reputed to work faster.

 >  Beyond that ... all other things being more-or-less equal I'll
 > do this with modules.
 >  Let's build that.  So in /etc/sysctl.conf:
 > 
 > net.inet.ip.fw.default_to_accept="1"
 > net.inet.ip.fw.verbose="1"
 > net.inet.ip.fw.verbose_limit="100"
 > 
 >  check.
 > 
 > >  I believe all these can be accomplished with modules on GENERIC
 > >  kernel, at least on 8.x, with the exception of FIREWALL_FORWARD
 > >  functionality which does require a custom kernel as it messes
 > >  with lots of ip paths.
 > 
 >  This machine has a custom kernel, so that's not a an issue.
 >  And in /boot/loader.conf:
 > 
 > ipfw_load="YES"
 > ipfw_nat="YES"   # in-kernel ipfw nat
 > libalias="YES"   # for in-kernel ipfw nat

ipfw_nat_load="YES"
libalias_load="YES"

 >  check.
 >  and in the kernel config:
 > 
 > #options  IPFIREWALL  #firewall
 > #options  IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
 > 
 > options  IPFIREWALL_FORWARD

Planning on using any 'fwd' rules?

 > #options  IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
 > #options  IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
 > #options  IPDIVERT
 > #options  IPFIREWALL_NAT  #ipfw kernel nat support
 > #options  LIBALIAS   # required for NAT
 > 
 >  check.
 >  This combination will get me a) ipfw, using the standard
 > rc.conf "firewall_" variables, and b) NAT ... do I still need to
 > have a "nat" setting in the firewall rules?

The 'client' ruleset now has rules for either natd or ipfw nat.  The 
'simple' ruleset works with natd (from natd_enable and natd_interface in 
rc.conf), but still lacks the patch for ipfw nat - my remiss for seeking 
comment in ipfw@ rather than sending it with a PR, as one should.

Time I redid it, you can be guinea pig :)  What freebsd version?

cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Robert Huff]

Ian Smith writes:

>   >   So ... double-checking I'm doing this right:
>   > 
>   > 1) in /boot/loader.conf:
>   > 
>   > ipfw_load="YES"
>   > ipdivert_load="YES"
>  
>  I thought from your earlier mail that you wanted to use in-kernel
>  NAT?

I want whatever works.  :-)
Beyond that ... all other things being more-or-less equal I'll
do this with modules.
Let's build that.  So in /etc/sysctl.conf:

net.inet.ip.fw.default_to_accept="1"
net.inet.ip.fw.verbose="1"
net.inet.ip.fw.verbose_limit="100"

check.

>  I believe all these can be accomplished with modules on GENERIC
>  kernel, at least on 8.x, with the exception of FIREWALL_FORWARD
>  functionality which does require a custom kernel as it messes
>  with lots of ip paths.

This machine has a custom kernel, so that's not a an issue.
And in /boot/loader.conf:

ipfw_load="YES"
ipfw_nat="YES"  # in-kernel ipfw nat
libalias="YES"  # for in-kernel ipfw nat

check.
and in the kernel config:

#options  IPFIREWALL  #firewall
#options  IPFIREWALL_VERBOSE  #enable logging to syslogd(8)

options  IPFIREWALL_FORWARD

#options  IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
#options  IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
#options  IPDIVERT
#options  IPFIREWALL_NAT  #ipfw kernel nat support
#options  LIBALIAS  # required for NAT

check.
This combination will get me a) ipfw, using the standard
rc.conf "firewall_" variables, and b) NAT ... do I still need to
have a "nat" setting in the firewall rules?

Less confused than last time,


Robert Huff

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

Re: Kernel Config for NAT

[Ian Smith]

In freebsd-questions Digest, Vol 305, Issue 9, Message: 1
On Thu, 8 Apr 2010 08:10:34 -0400 Robert Huff  wrote:
 > Adam Vande More writes:
 > 
 > >  >If compiled into the kernel, there's a set of optional settings
 > >  > (VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
 > >  >If using the module, how does one set these?
 > >  >
 > >  Logging is compiled into the modules and there are a few sysctl's.  AFAIK,
 > >  everything else is the same.

There are _lots_ of sysctls, even more recently with SCTP support.

 > >  http://www.freebsd.org/doc/handbook/firewalls-ipfw.html



This is absolutely the worst section of an otherwise great handbook.  
Apart from being way out of date it contains gratuitous deprecation, 
inaccuracies and a large number of plain untruths, was largely written 
by someone who doesn't use (or like) ipfw, and has examples styled to 
duplicate an IPFILTER setup.

Nothing short of a rewrite from scratch could fix it, despite efforts by 
several people to clarify aspects; only quite recently the invalid 'ipfw 
block' command was removed from it.  ipfw(8) is a complete (albeit very
terse) ipfw reference and I thoroughly recommend studying that instead.

Despite what the handbook section says, the sample rules eg the 'simple' 
ruleset in rc.firewall ARE these days suitable for immediate use using 
rc.conf variables, DO include NAT functionality (either with natd or 
ipfw nat) in the _correct_ place in the ruleset, and DO include some 
stateful rules; that and ipfw(8) are certainly a better place to start 
than the dreadful examples afflicting the handbook since some years.


 >  So ... double-checking I'm doing this right:
 > 
 > 1) in /boot/loader.conf:
 > 
 > ipfw_load="YES"
 > ipdivert_load="YES"

I thought from your earlier mail that you wanted to use in-kernel NAT?

If so, rather than divert sockets (using ipfw's divert action) you want:
ipfw_nat_load=YES
libalias_load=YES

 > 2) in the kernel config:
 > 
 > #options  IPFIREWALL  #firewall
 > #options  IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
 > #options  IPFIREWALL_VERBOSE_LIMIT=100    #limit verbosity
 > #options  IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
 > #options  IPDIVERT
 > #options  IPFIREWALL_NAT  #ipfw kernel nat support
 > options  LIBALIAS# required for NAT

I believe all these can be accomplished with modules on GENERIC kernel, 
at least on 8.x, with the exception of FIREWALL_FORWARD functionality
which does require a custom kernel as it messes with lots of ip paths.

If you want to use natd(8) then you'll need ipdivert.ko (as you have 
above), but if you want to use in-kernel NAT (not yet mentioned in the 
handbook sections for ipfw or natd, though there since 7.0) then you'll 
want IPFIREWALL_NAT and LIBALIAS in kernel, or loaded as modules:

ipfw.ko
ipfw_nat.ko # in-kernel ipfw nat
libalias.ko # for in-kernel ipfw nat
dummynet.ko # if wanted
ipdivert.ko # (or) for natd

Basically, natd uses userland libaliasand ipdivert but in-kernel NAT 
needs in-kernel libalias.  The syntax of nat commands is virtually 
identical for natd.conf and ipfw nat commands, see ipfw(8) & natd(8)

 > 3) in /etc/sysctl.conf:
 > 
 > net.inet.ip.fw.default_to_accept="1"

Interestingly, that one hasn't yet made it into ipfw(8) .. your choice, 
or you can use firewall_type="open" for rc.firewall without that, until 
you've got your ruleset in action (when default to deny is advisable)

 > net.inet.ip.fw.verbose="1"
 > net.inet.ip.fw.verbose_limit="100"
 > 
 > 
 >  That cover it?

Should do .. with the abovementioned exception, take ipfw(8) as being 
definitive, ignore the misleading and often just plain wrong handbook 
section, and prosper ..

cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Robert Huff]

>  IMHO, and according to Adam Vandr More, kernel options are no
>  longer required. 

The original reason I asked was:

30.6.2 Kernel Options

It is not a mandatory requirement to enable IPFW by
compiling the following options into the FreeBSD kernel,
unless NAT functionality is required. 


I do want NAT, and there is no unambiguous path in the
Handbook.


>  Still need entries in /etc/rc.conf. See  HB 30.9.5, 30.6.3,
>  30.6.5.7

Once ipfw is running, I should have the rulesets covered.



Robert Huff



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

Re: Kernel Config for NAT

[Gary Dunn]

On Thu, 8 Apr 2010 08:10:34 -0400 Robert Huff  wrote:

>   So ... double-checking I'm doing this right:
>
> 1) in /boot/loader.conf:
>
> ipfw_load="YES"
> ipdivert_load="YES"
yes; see NAT HB 31.9.3
>
> 2) in the kernel config:

IMHO, and according to Adam Vandr More, kernel options are no longer required.
>
> 3) in /etc/sysctl.conf:
>
> net.inet.ip.fw.default_to_accept="1"
see NAT HB 31.9.3

> net.inet.ip.fw.verbose="1"
> net.inet.ip.fw.verbose_limit="100"
see IPFW HB 30.6.1

I would use a smaller limit such as 5.
>
>
>   That cover
> it?

Still need entries in /etc/rc.conf. See  HB 30.9.5, 30.6.3, 30.6.5.7

I also have DHCP serving the downstream (private) network. Upstream gets 
configured by dhclient.
--
Gary Dunn, Honolulu
o...@aloha.com
http://openslate.net/
http://e9erust.blogspot.com/
Sent from a Newton 2100 via Mail V
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Adam Vande More]

On Thu, Apr 8, 2010 at 7:10 AM, Robert Huff  wrote:

>
> 1) in /boot/loader.conf:
>
> ipfw_load="YES"
> ipdivert_load="YES"
>
> 2) in the kernel config:
>
> #options  IPFIREWALL  #firewall
> #options  IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
> #options  IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
> #options  IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
> #options  IPDIVERT
> #options  IPFIREWALL_NAT  #ipfw kernel nat support
> options  LIBALIAS   # required for NAT
>
> 3) in /etc/sysctl.conf:
>
> net.inet.ip.fw.default_to_accept="1"
> net.inet.ip.fw.verbose="1"
> net.inet.ip.fw.verbose_limit="100
>

That's actually a good question considering the lack of documentation.  If
that works then great, but one wonders what the ipfw_nat modules is for?
...
looks like it's tied into libalias apparently a replacement for natd.

http://wiki.freebsd.org/Libalias

That seems to be a major problem with those GsoC projects, even if they get
something good working there is frequently no documentation with it.  Then
it sits there mostly unused waiting for bitrot to set in.  I don't know the
structure of GsoC, but if it's possible for the mentor to *strongly*
encourage documentation checkpoints(manpages, not wiki) I think these
projects would be better utilized.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Robert Huff]

Adam Vande More writes:

>  >If compiled into the kernel, there's a set of optional settings
>  > (VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
>  >If using the module, how does one set these?
>  >
>  Logging is compiled into the modules and there are a few sysctl's.  AFAIK,
>  everything else is the same.
>  
>  http://www.freebsd.org/doc/handbook/firewalls-ipfw.html

So ... double-checking I'm doing this right:

1) in /boot/loader.conf:

ipfw_load="YES"
ipdivert_load="YES"

2) in the kernel config:

#options  IPFIREWALL  #firewall
#options  IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
#options  IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
#options  IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default
#options  IPDIVERT
#options  IPFIREWALL_NAT  #ipfw kernel nat support
options  LIBALIAS   # required for NAT

3) in /etc/sysctl.conf:

net.inet.ip.fw.default_to_accept="1"
net.inet.ip.fw.verbose="1"
net.inet.ip.fw.verbose_limit="100"


That cover it?


Robert Huff

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

Re: Kernel Config for NAT

[Robert Huff]

Adam Vande More writes:

>  >If compiled into the kernel, there's a set of optional settings
>  > (VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
>  >If using the module, how does one set these?
>  >
>  Logging is compiled into the modules and there are a few sysctl's.  AFAIK,
>  everything else is the same.
>  
>  http://www.freebsd.org/doc/handbook/firewalls-ipfw.html

It would be nice if this were made explicit in that handvook.
And the other two secotions harmonized as well.


Robert Huff


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

Re: Kernel Config for NAT

[Adam Vande More]

On Wed, Apr 7, 2010 at 11:28 PM, Robert Huff  wrote:

>If compiled into the kernel, there's a set of optional settings
> (VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
>If using the module, how does one set these?
>
>
Logging is compiled into the modules and there are a few sysctl's.  AFAIK,
everything else is the same.

http://www.freebsd.org/doc/handbook/firewalls-ipfw.html

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel Config for NAT

[Robert Huff]

Adam Vande More writes:

>  > I am setting up a router to share one Wi-Fi link between a few computers
>  > that only support CAT-5. Like a wireless access point except wired and
>  > wireless sides are reversed. My question is about the ipfw packet filter.
>  > >From the handbook section on NAT, 31.9.3, I can achieve what I need with
>  > boot loader options. Section 31.9.4 describes alternatives for building a
>  > custom kernel. In contrast, the chapter on ipfw states several times that
>  > NAT requires a custom kernel - 30.6.1, 30.6.2, 30.6.5.7.
>  >
>  > I want to use freebsd-update and building a custom kernel eliminates that
>  > option.
>  >
>  > Which is correct? Do I need to build a custom kernel to use NAT?
>  
>  You don't need to do build a custom kernel anymore, that's a
>  relatively recent change.  Another option is to use pf instead
>  ipfw since it has built-in NAT.  I'm not saying you should change
>  as your current path has worked great for me for many years.

If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?



Robert Huff



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

Re: Kernel Config for NAT

[Adam Vande More]

On Wed, Apr 7, 2010 at 9:51 PM, Gary Dunn  wrote:

> I am setting up a router to share one Wi-Fi link between a few computers
> that only support CAT-5. Like a wireless access point except wired and
> wireless sides are reversed. My question is about the ipfw packet filter.
> >From the handbook section on NAT, 31.9.3, I can achieve what I need with
> boot loader options. Section 31.9.4 describes alternatives for building a
> custom kernel. In contrast, the chapter on ipfw states several times that
> NAT requires a custom kernel - 30.6.1, 30.6.2, 30.6.5.7.
>
> I want to use freebsd-update and building a custom kernel eliminates that
> option.
>
> Which is correct? Do I need to build a custom kernel to use NAT?
>

You don't need to do build a custom kernel anymore, that's a relatively
recent change.  Another option is to use pf instead ipfw since it has
built-in NAT.  I'm not saying you should change as your current path has
worked great for me for many years.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Kernel Config for NAT

[Gary Dunn]

I am setting up a router to share one Wi-Fi link between a few computers that 
only support CAT-5. Like a wireless access point except wired and wireless 
sides are reversed. My question is about the ipfw packet filter. >From the 
handbook section on NAT, 31.9.3, I can achieve what I need with boot loader 
options. Section 31.9.4 describes alternatives for building a custom kernel. In 
contrast, the chapter on ipfw states several times that NAT requires a custom 
kernel - 30.6.1, 30.6.2, 30.6.5.7.

I want to use freebsd-update and building a custom kernel eliminates that 
option.

Which is correct? Do I need to build a custom kernel to use NAT?

--
Gary Dunn, Honolulu
o...@aloha.com
http://openslate.net/
http://e9erust.blogspot.com/
Sent from a Newton 2100 via Mail V
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED] -ADDENDUM

[Mario Lobo]

Well, to tell the truth I wasn't that thrilled with the results. I didn't 

[snip]
--

Compiling vbox/vbox-devel with gcc43

1) /usr/include/cam/cam.h needed #include  for FILE define, 
complained by: 

[snip]

and /etc/src.conf

NO_WERROR=
WERROR=


--

New problems started to come when I tried to extend this to other ports, 

[snip]


You have to:

1) make patch
2) apply the mods
3) make


Best of luck, again

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED]

[Mario Lobo]

On Thursday 01 April 2010 16:53:36 Pegasus Mc Cleaft wrote:
> On Thursday 01 April 2010 15:27:41 Oliver Fromme wrote:
> > Mario Lobo  wrote:
> >  > [...]
> >  > It's compiling right now.
> >  >
> >  > I'll post my findings and impressions on results and performance right
> >  > after the next reboot.
> >
> > So, how is it going?  Any benchmarks yet?  I'm curious
> > if the new gcc version will really make a significant
> > difference.
> 
>   I would love to see the /etc/make.conf,  /etc/src.conf and
> /etc/libmap.conf files that were used for the build. I have tried compiling
>  in VBox a current kernel and world, but it usually just bombs out for me.
>  I would like to give this a go as well.
> 
> Peg
> 

Well, to tell the truth I wasn't that thrilled with the results. I didn't 
benchmark anything by my impressions were that at least disk access was a bit 
slower not only during booting but it was more noticeable to me particularly  
on a burning DVD session. Of course this is ultra abstract. 

In all previous experiences I had in burning CD/DVD with k3b, I recollect that 
during burning, the software buffer and device buffer gouges were always 100%, 
with the software buffer gouge dropping down occasionally to 89/92%.

After recompiling the kernel with gcc43, the software buffer was always empty 
and the device buffer rarely reached 40/50%. I think (if not mistaken) this 
means that the device is asking "where is my data??" and the OS is not 
providing it fast enough.

I could not get world to build with gcc43 so I gave that up. Then I moved on 
to VirtualBox. I managed to have it compiled and running. After long trial and 
error sessions, I could pin point what was breaking compilation and fixed it. 
Here are the steps:

--

Compiling vbox/vbox-devel with gcc43

1) /usr/include/cam/cam.h needed #include  for FILE define, 
complained by: 

 
work/VirtualBox-3.1.51.r27657_OSE/src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp:47:
 /usr/include/cam/cam.h:246: error: 'FILE' has not been declared

2)/usr/ports/emulators/virtualbox-
ose/work/VirtualBox-3.1.6_OSE/src/VBox/Main/generic/NetIf-generic.cpp 
  needed #include  because of popen() (this step is ONLY for 
virtualbox-ose)

3)/usr/ports/emulators/virtualbox-ose(-
devel)/work/VirtualBox-3.1.6_OSE/src/VBox/Main/freebsd/NetIf-freebsd.cpp 
  needed #include  because of malloc()/free()

4) Config.kmk needed some tweaks:

  a) line 1750 - $(APPEND) '$@' 'VBOX_GCC_mtune-generic ?= $(call 
VBOX_GCC_CHECK_CC,-mtune=amdfam10 -D__FreeBSD_cc_version=0,)' 
 to use instructions closer to Phenom and avoid cc complains.
  b) took out all references to "-fformat-extensions" and "-fno_format-
extensions"
  c) Preceeded all relevant locations of "/usr/lib \" with 
"/usr/local/lib/gcc43 \" so kbuild searched there for libraries first.
(except TEMPLATE_VBOXQT4GUIEXE_LIBPATH !)

  d) You can use the same Config.kmk for building kmods as well

5) took out -fformat-extensions from src/sys/conf/kern.mk

And I left /etc/libmap.conf 

libgcc_s.so.1   gcc43/libgcc_s.so.1
libgomp.so.1gcc43/libgomp.so.1
libobjc.so.3gcc43/libobjc.so.2
libssp.so.0 gcc43/libssp.so.0
libstdc++.so.6  gcc43/libstdc++.so.6

/etc/make.conf 

CC=/usr/local/bin/gcc43
CXX=/usr/local/bin/g++43
CPP=/usr/local/bin/cpp43
CFLAGS+=-mssse3 -D__FreeBSD_cc_version=0
CXXFLAGS+=-D__FreeBSD_cc_version=0
CPUTYPE=amdfam10
#MAKEOPTS+= -j4


and /etc/src.conf

NO_WERROR=
WERROR=


--

New problems started to come when I tried to extend this to other ports, 
breaking a lot of them, to point of making me revert everything back to what 
it was. In fact I am still in this process right now, and reving a lot of 
problems to rebuild kde4.

This is it for now, guys. If you find anything new, please post.

Best of luck,

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED]

[Vlad Galu]

On Thu, Apr 1, 2010 at 6:27 PM, Oliver Fromme  wrote:
> Mario Lobo  wrote:
>  > [...]
>  > It's compiling right now.
>  >
>  > I'll post my findings and impressions on results and performance right 
> after
>  > the next reboot.
>
> So, how is it going?  Any benchmarks yet?  I'm curious
> if the new gcc version will really make a significant
> difference.
>

I'm not as worried about performance as I am about compatibilty.
Various software suites have started using newer GCCisms in their
code. One example I can give from the top of my head is Wt
(www.webtoolkit.eu), which compiles with 4.4, but not with 4.2. I
shamefully haven't dug any deeper to check which particular
syntactical construct offended 4.2.

Yes, one might say, after all it's the upstream developers who ought
to make sure their software compiles on FreeBSD, but some aditional
overhead on the shoulders of our port maintainers should be expected.

> Best regards
>   Oliver
>
> --
> Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
> Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
> secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
> chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
>
> FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd
>
> "UNIX was not designed to stop you from doing stupid things,
> because that would also stop you from doing clever things."
>        -- Doug Gwyn
> ___
> freebsd-hack...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>



-- 
Good, fast & cheap. Pick any two.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED]

[Pegasus Mc Cleaft]

On Thursday 01 April 2010 15:27:41 Oliver Fromme wrote:
> Mario Lobo  wrote:
>  > [...]
>  > It's compiling right now.
>  >
>  > I'll post my findings and impressions on results and performance right
>  > after the next reboot.
> 
> So, how is it going?  Any benchmarks yet?  I'm curious
> if the new gcc version will really make a significant
> difference.

I would love to see the /etc/make.conf,  /etc/src.conf and 
/etc/libmap.conf files that were used for the build. I have tried compiling in 
VBox a current kernel and world, but it usually just bombs out for me. I would 
like to give this a go as well. 

Peg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED]

[Oliver Fromme]

Mario Lobo  wrote:
 > [...]
 > It's compiling right now.
 > 
 > I'll post my findings and impressions on results and performance right after 
 > the next reboot.

So, how is it going?  Any benchmarks yet?  I'm curious
if the new gcc version will really make a significant
difference.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things."
-- Doug Gwyn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Default labeling and space for rebuilding the kernel.

[Leon Meßner]

On Wed, Mar 31, 2010 at 08:34:59AM -0400, Michael Powell wrote:
> Leon Meßner wrote:
> 
> > Hi,
> > 
> > if one uses the default labeling with current installer it is not
> > possible to rebuild the kernel (GENERIC). It fails on installing the
> > wlan.ko.

> > /: write failed, filesystem is full
> > install: /boot/kernel/wlan.ko.symbols: No space left on device
> [snip]
> 
> There has been some discussion lately about possibly changing the defaults. 
> If you become faced with having to reinstall jot down your current partition 
> sizes and adjust manually making / larger.

On production machines i have some 2G. This was just an as fast as
possible installation.
 
> Since it is full, if you intend to try and recover it will entail deleting 
> something. This could get tricky, especially if the new 'kernel' space is 
> what filled up. This would presuppose that the kernel.old area was already 
> written out successfully. If the machine will not boot successfully with the 
> new kernel it is imperative that kernel.old still be healthy in order to 
> recover. However, if the new kernel does actually boot, with the result 
> being that some modules are missing you may be able to delete the kernel.old 
> in order to buy space. Messing around with this can potentially be 
> problematic, for obvious reasons. A strong 'YMMV' is indicated here.

I just went the easy way and moved the old kernel away from / . I
wouldn't have done so if this machine would be very critical though.

> If you can get past that, you may be able to mitigate the / being too small. 
> Place STRIP= -s into /etc/make.conf and WITHOUT_PROFILE= true into 
> /etc/src.conf. The con of this is that you lose some debugging ability. The 
> pro is new kernels will now fit. I have two servers set up this way at home, 
> and one uses 91MB while the other uses 93MB of space. The 91MB one only has 
> a / of 200MB total, and is nearly half empty. Allows for rebuilding and 
> installing a new kernel without running out of space.

Hm, never used this file. Looks like it was introduced in FBSD7
somewhere. Looks reasonable to split parameters for /usr/src into a
different file than /etc/make.conf

thanks,
Leon


pgpvRV7QIQqB5.pgp
Description: PGP signature

Re: Default labeling and space for rebuilding the kernel.

[Michael Powell]

Leon Meßner wrote:

> Hi,
> 
> if one uses the default labeling with current installer it is not
> possible to rebuild the kernel (GENERIC). It fails on installing the
> wlan.ko.
> 
> Isn't that wrong somehow ?
> 
> ===> wi (install)
> install -o root -g wheel -m 555   if_wi.ko /boot/kernel
> install -o root -g wheel -m 555   if_wi.ko.symbols /boot/kernel
> ===> wlan (install)
> install -o root -g wheel -m 555   wlan.ko /boot/kernel
> install -o root -g wheel -m 555   wlan.ko.symbols /boot/kernel
> 
> /: write failed, filesystem is full
> install: /boot/kernel/wlan.ko.symbols: No space left on device
[snip]

There has been some discussion lately about possibly changing the defaults. 
If you become faced with having to reinstall jot down your current partition 
sizes and adjust manually making / larger.

Since it is full, if you intend to try and recover it will entail deleting 
something. This could get tricky, especially if the new 'kernel' space is 
what filled up. This would presuppose that the kernel.old area was already 
written out successfully. If the machine will not boot successfully with the 
new kernel it is imperative that kernel.old still be healthy in order to 
recover. However, if the new kernel does actually boot, with the result 
being that some modules are missing you may be able to delete the kernel.old 
in order to buy space. Messing around with this can potentially be 
problematic, for obvious reasons. A strong 'YMMV' is indicated here.

If you can get past that, you may be able to mitigate the / being too small. 
Place STRIP= -s into /etc/make.conf and WITHOUT_PROFILE= true into 
/etc/src.conf. The con of this is that you lose some debugging ability. The 
pro is new kernels will now fit. I have two servers set up this way at home, 
and one uses 91MB while the other uses 93MB of space. The 91MB one only has 
a / of 200MB total, and is nearly half empty. Allows for rebuilding and 
installing a new kernel without running out of space.

-Mike



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

Default labeling and space for rebuilding the kernel.

[Leon Meßner]

Hi,

if one uses the default labeling with current installer it is not
possible to rebuild the kernel (GENERIC). It fails on installing the wlan.ko.

Isn't that wrong somehow ?

===> wi (install)
install -o root -g wheel -m 555   if_wi.ko /boot/kernel
install -o root -g wheel -m 555   if_wi.ko.symbols /boot/kernel
===> wlan (install)
install -o root -g wheel -m 555   wlan.ko /boot/kernel
install -o root -g wheel -m 555   wlan.ko.symbols /boot/kernel

/: write failed, filesystem is full
install: /boot/kernel/wlan.ko.symbols: No space left on device
*** Error code 71

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

regards,
Leon


pgp1J9IYK1Sgu.pgp
Description: PGP signature

Re: Custom Kernel to Memory Stick

[Giorgos Keramidas]

On Mon, 29 Mar 2010 10:49:08 -0500, Jay Hall  wrote:
> Ladies and Gentlemen,
>
> I have been asked to explore the possibility of booting FreeBSD from a
> memory stick.  This was not a problem; worked great when installed  from
> the distribution CD.
>
> What would be the best way to get our custom configuration onto the
> memory stick?

The fastest way I know is to create an image to an 'image' file stored
on disk or ramdisk and then dd the image to the USB disk.  You can
create a suitably large image with truncate(1), e.g.:

truncate -s 1g /var/tmp/image.bin

Then attach the image to an mdconfig device:

mdconfig -a -t vnode -u 20 -f /var/tmp/image.bin

Create a filesystem on it, and install everything from your buildworld
and buildkernel run:

fdisk -BI /dev/md20
bsdlabel -w -B /dev/md20s1
newfs -U /dev/md20s1a

Mount the new image partition before installkernel+installworld:

mount -t ufs /dev/md20s1a /mnt

Then you sould be able to install with DESTDIR pointing to the image
partition:

cd /usr/src
env DESTDIR=/mnt make installkernel installworld

Don't forgte to use mergemaster with -D /mnt to install the /mnt/etc
files from /usr/src/etc.  Then tweak the /mnt/etc/fstab file to point at
the USB disk as the root filesystem.

Finally detach the image and write it on a USB disk:

umount /mnt
mdconfig -du 20
dd if=/var/tmp/image.bin of=/dev/da0 bs=4m

One of the nice tricks you can use for the root filesystem of the USB
disk is to add a UFS label to the USB root filesystem.  This way you
don't have to assume that the USB root filesystem is called da0s1a but
you can use /dev/ufs/LABELNAME in the fstab file of the image partition.

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

Re: Custom Kernel to Memory Stick

[Jay Hall]

On Mar 29, 2010, at 6:30 PM, Aiza wrote:



This is the procedure you want to follow.

http://forums.freebsd.org/showthread.php?t=11680


And for greater detail

http://forums.freebsd.org/showthread.php?t=11715


Thanks for the links.  I will give them a try.

Jay

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

Re: Custom Kernel to Memory Stick

[Aiza]

Jay Hall wrote:

Ladies and Gentlemen,

I have been asked to explore the possibility of booting FreeBSD from a 
memory stick.  This was not a problem; worked great when installed from 
the distribution CD.


What would be the best way to get our custom configuration onto the 
memory stick?




This is the procedure you want to follow.

http://forums.freebsd.org/showthread.php?t=11680


And for greater detail

http://forums.freebsd.org/showthread.php?t=11715
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Custom Kernel to Memory Stick

[Jay Hall]

On Mar 29, 2010, at 10:49 AM, Jay Hall wrote:


What would be the best way to get our custom configuration onto the  
memory stick?




OK, I managed t get our custom configuration on to the memory stick  
using dump.  After getting everything configured, what I thought was  
correctly, I am able to boot from the memory stick until it is time to  
mount the root partition.


When mounting the root partition from /dev/da0s1a, I receive the  
following message:


Trying to mount root from ufs:/dev/da0s1a
ROOT MOUNT ERROR:
If you have invalid mount options, reboot and first try the following  
from the loader prompt:


I have tried the suggested courses of action without any success.

If I type ufs:/dev/da0s1a I receive the ROOT MOUNT ERROR again.

Following is what I have done to create the bootable memory stick.

Created two partitions on the memory stick each about 2 GB.   
sysinstall was used for this.


Used bsdlabel to create the necessary labels on the memory stick.   
sysinstall was used for this.


Ran newfs as on all of the labels.  This was done from the command  
prompt.


Once everything was created, I mounted the memory stick and created an  
image of my working installation using dump.


boot0cfg was run on the memory stick.  boot0cfg -v -B -o noupdate da0

Modified the fstab on the memory stick as follows

/dev/da0s1a /   rw,noatime  0   0

Everything other than the operating system was left on the hard drive.

If anyone has any suggestions how to fix this, please let me know.  I  
am out of ideas.  Or, if you can direct me to a howto, that would be  
fine also.


Thanks for all your help and patience.



Jay
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Custom Kernel to Memory Stick

[Jay Hall]

On Mar 29, 2010, at 10:49 AM, Jay Hall wrote:


What would be the best way to get our custom configuration onto the  
memory stick?


Ladies and Gentlemen,

This is what I have done, but now I cannot mount the memory stick.

I create an image of the s1a partition where the kernel I want to copy  
resides

dd if=/dev/ad0s1a of=/home/hallja/s1aimage bs=2048k

After preparing the memory stick I use the following command to  
transfer the image to the memory stick

dd if=/home/hallja/ s1aimage of=/dev/da0s1a bs=2048k

I am able to mount the memory stick without any problem before I add  
the image.  After adding the image, I try to mount the memory stick  
using


mount /dev/da0s1a /mnt1

And, I receive the following message

mount: /dev/da0s1a : Operation not permitted

Any suggestions would be greatly appreciated.

Thanks,


Jay
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Custom Kernel to Memory Stick

[Jay Hall]

Ladies and Gentlemen,

I have been asked to explore the possibility of booting FreeBSD from a  
memory stick.  This was not a problem; worked great when installed  
from the distribution CD.


What would be the best way to get our custom configuration onto the  
memory stick?


Thanks,



Jay
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43 [SOLVED]

[Mario Lobo]

On Thursday 25 March 2010 19:12:09 Edward Tomasz Napierała wrote:
> Wiadomość napisana przez Mario Lobo w dniu 2010-03-25, o godz. 17:24:
> > 2010/3/24 Mario Lobo 
> >
> >> Anyway,my question boils down to: Is there a way to build the kernel
> >> with gcc43, with minimal tweaking? Am i attempting something out of my
> >> league?
> 
> This is what I use to compile kernel on 9.0-CURRENT/amd64:
> 
> CC=/usr/local/bin/gcc44
> CXX=   /usr/local/bin/g++44
> CWARNFLAGS=-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>  \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \
>  -Wno-pointer-sign -D__FreeBSD_cc_version=0 \
>-Wno-unused-function -Wno-inline -Wno-format \
>-Wno-uninitialized -Wno-array-bounds -Wno-missing-prototypes
> 
> Note that this is GCC 4.4.4, installed from ports.  Also, this will not
> compile the world - only the kernel.  Also, they were a few fixes to make
> this work; they were not MFC-ed, iirc; removing -Werror altogether should
> work around these problems.
> 
> --
> If you cut off my head, what would I say?  Me and my head, or me and my
>  body?
> 

Adding 

NO_WERROR=
WERROR=

to src.conf did it. It's compiling right now.

I'll post my findings and impressions on results and performance right after 
the next reboot.

Thanks for all the help and info, Guys !!

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Edward Tomasz Napierała]

Wiadomość napisana przez Mario Lobo w dniu 2010-03-25, o godz. 17:24:
> 2010/3/24 Mario Lobo 
>> 
>> Anyway,my question boils down to: Is there a way to build the kernel with
>> gcc43, with minimal tweaking? Am i attempting something out of my league?

This is what I use to compile kernel on 9.0-CURRENT/amd64:

CC=/usr/local/bin/gcc44
CXX=   /usr/local/bin/g++44
CWARNFLAGS=-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \
   -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \
   -Wno-pointer-sign -D__FreeBSD_cc_version=0 \
   -Wno-unused-function -Wno-inline -Wno-format \
   -Wno-uninitialized -Wno-array-bounds -Wno-missing-prototypes

Note that this is GCC 4.4.4, installed from ports.  Also, this will not
compile the world - only the kernel.  Also, they were a few fixes to make
this work; they were not MFC-ed, iirc; removing -Werror altogether should
work around these problems.

--
If you cut off my head, what would I say?  Me and my head, or me and my body?

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

Re: Compiling kernel with gcc43

[Bruce Cran]

On Thu, Mar 25, 2010 at 02:18:34PM -0300, Mario Lobo wrote:

> All right !! Thanks for replying !
> 
> There are a lot of locations throughout the source code where -Werror is
> enabled
> How can I disable -Werror globally? via src.conf ? will it do it for
> world/kernel?
> will this "damage" the resulting kernel/world binaries?

You should be able to use NO_WERROR in src.conf to prevent -Werror 
being used.

-- 
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Garrett Cooper]

On Thu, Mar 25, 2010 at 10:18 AM, Mario Lobo  wrote:
> 2010/3/25 Ryan Stone 
>
>> If you just want to try it out you could disable -Werror for your own
>> build.  The reason that gcc 4.3 fails where 4.2 works fine is that the
>> gcc developers are adding new warnings with every compiler release, so
>> until somebody takes the time to fix all of the new warnings you won't
>> be able to build the kernel with -Werror.
>>
>
> All right !! Thanks for replying !
>
> There are a lot of locations throughout the source code where -Werror is
> enabled
> How can I disable -Werror globally? via src.conf ? will it do it for
> world/kernel?
> will this "damage" the resulting kernel/world binaries?

-Wno-error .
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Andrius Morkūnas]

On Thu, 25 Mar 2010 18:24:10 +0200, Mario Lobo  wrote:

Should I just dump the gcc43 idea and try this with clang/llvm?

I've seen http://wiki.freebsd.org/BuildingFreeBSDWithClang.

Anything else to watch out for when building world/kernel/ports?


ClangBSD had little to no runtime testing, so you should be careful
with it. I'm not saying it won't work, but make sure you have backups
in case something goes wrong.

Also, if you just want to build the kernel, you don't need ClangBSD,
you can just install llvm-devel from ports and use

make CC=/usr/local/bin/clang buildkernel

Some people ran or are running their systems with clang compiled kernel.
You should still be careful, and some things (like snd_hda on amd64)
are known to have problems.

--
Andrius
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Ryan Stone]

-Wnoerror should disable it, but I don't know enough about the FreeBSD
build infrastructure to tell you where it needs to go.  Worst comes to
worst you can just delete all of the -Werrors.

Disabling -Werror will not cause any problems.  -Werror means "treat
warnings as errors".  It's very useful for development but in your
case, where you're starting with a known good source tree with no
warnings with earlier compilers, it's not necessary to have the option
enabled.  If the warnings are pointing to legitimate bugs, those bugs
also exist in a kernel built by gcc 4.2, so your kernel can't be any
worse than what you already have.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Mario Lobo]

2010/3/25 Ryan Stone 

> If you just want to try it out you could disable -Werror for your own
> build.  The reason that gcc 4.3 fails where 4.2 works fine is that the
> gcc developers are adding new warnings with every compiler release, so
> until somebody takes the time to fix all of the new warnings you won't
> be able to build the kernel with -Werror.
>

All right !! Thanks for replying !

There are a lot of locations throughout the source code where -Werror is
enabled
How can I disable -Werror globally? via src.conf ? will it do it for
world/kernel?
will this "damage" the resulting kernel/world binaries?

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Ryan Stone]

If you just want to try it out you could disable -Werror for your own
build.  The reason that gcc 4.3 fails where 4.2 works fine is that the
gcc developers are adding new warnings with every compiler release, so
until somebody takes the time to fix all of the new warnings you won't
be able to build the kernel with -Werror.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling kernel with gcc43

[Mario Lobo]

2010/3/24 Mario Lobo 

> Hi;
>
> I followed the instructions from
> http://www.freebsd.org/doc/en/articles/custom-gcc/article.html
>
> to see if I can achieve some performance gain (8-STABLE r205630 amd64) and
> also get a more modern instruction set for my Phenom II (amdfam10), so I've
> done the following config settings:
>
> make.conf
>
> .if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc43)
> CC=/usr/local/bin/gcc43
> CXX=/usr/local/bin/g++43
> CPP=/usr/local/bin/cpp43
> CFLAGS+=-mssse3
> CPUTYPE=amdfam10
> .endif
>
> libmap.conf
>
> libgcc_s.so.1   gcc43/libgcc_s.so.1
> libgomp.so.1gcc43/libgomp.so.1
> libobjc.so.3gcc43/libobjc.so.2
> libssp.so.0 gcc43/libssp.so.0
> libstdc++.so.6  gcc43/libstdc++.so.6
>
>
> buildworld goes on normally it seems, but when I tried to build the kernel,
> the first stop came from the option used by the kernel build "-fformat-
> extensions", which is not accepted by gcc43, so I took it out of
> /usr/src/sys/conf/kern.mk, the ONLY place I found it.
>
> It seemed to solve the problem until gcc43 stopped because of the "-Werror"
> option, which is all over the place!. Funny that gcc42 (used by default)
> doesn't stop because of this option.
>
> Anyway,my question boils down to: Is there a way to build the kernel with
> gcc43, with minimal tweaking? Am i attempting something out of my league?
>
> Thanks,
> --
> Mario Lobo
>
>
Any suggestions/Comments?

Should I just dump the gcc43 idea and try this with clang/llvm?

I've seen http://wiki.freebsd.org/BuildingFreeBSDWithClang.

Anything else to watch out for when building world/kernel/ports?

Thanks,
-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Compiling kernel with gcc43

[Mario Lobo]

Hi;

I followed the instructions from 
http://www.freebsd.org/doc/en/articles/custom-gcc/article.html

to see if I can achieve some performance gain (8-STABLE r205630 amd64) and 
also get a more modern instruction set for my Phenom II (amdfam10), so I've 
done the following config settings:

make.conf

.if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc43)
CC=/usr/local/bin/gcc43
CXX=/usr/local/bin/g++43
CPP=/usr/local/bin/cpp43
CFLAGS+=-mssse3
CPUTYPE=amdfam10
.endif

libmap.conf

libgcc_s.so.1   gcc43/libgcc_s.so.1
libgomp.so.1gcc43/libgomp.so.1
libobjc.so.3gcc43/libobjc.so.2
libssp.so.0 gcc43/libssp.so.0
libstdc++.so.6  gcc43/libstdc++.so.6
 

buildworld goes on normally it seems, but when I tried to build the kernel, 
the first stop came from the option used by the kernel build "-fformat-
extensions", which is not accepted by gcc43, so I took it out of 
/usr/src/sys/conf/kern.mk, the ONLY place I found it.

It seemed to solve the problem until gcc43 stopped because of the "-Werror" 
option, which is all over the place!. Funny that gcc42 (used by default) 
doesn't stop because of this option.

Anyway,my question boils down to: Is there a way to build the kernel with 
gcc43, with minimal tweaking? Am i attempting something out of my league?

Thanks,
-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel panic when if_lagg is not loaded.

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/03/17 00:31, Leslie Jensen wrote:
> 
> I have set upp aggregation of my wlan and and wired NIC following the
> instructions in the handbook.
> 
> http://www.freebsd.org/doc/handbook/network-aggregation.html
> 
> I "forgot" to add the if_lagg_load="YES" in /boot/loader.conf. When I
> rebooted I got a kernel panic.
> 
> Should this be considerd normal or is it something I should report?
> 
> 
> 
> Secondly I see there'a a reference to the lagg(4) man page. I think it
> would help future readers of the above page if a comment about loading
> if_lagg_load="YES" in /boot/loader.conf would be added.

Panics can hardly be considered normal...  I was unable to reproduce the
issue though, is it possible for you to get a backtrace and tell us what
release are you using?

Cheers,
- -- 
Xin LI http://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLqWtUAAoJEATO+BI/yjfBHSkIAJC1Ooov8JiddJk+3cw9uZsK
f2LvLoQerHY+NVwG0yjdXjhj67FWht4piXewNngePzOzjcXJQybfbrFUxW2zDc3X
LSrOLSLtf8CKDhdVK+octUUjYyT1lbkeoyf1Ci1y2h/DE7QY360rzfXhA1VfHJCr
3PTcaHsony3AD6Fwcg3U+7hGseL+zxLfV0DwUtyNIhVZHIrp5hElPseVXnxVPFTT
nKaaw4AldH6JYOhT1IZWQObMNJgVhCs48LdAwSCCg7x9Bjias606yY3C1RNupXPM
5TxjmMpiQUhBc/MIAU7mAb27SQY2Lwx6+S9S+4HJoVgr2/eMwjCCOYvXxIt5hXs=
=BGMq
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel dump crash

[Alejandro Imass]

On Wed, Mar 17, 2010 at 10:04 AM, Alejandro Imass  wrote:
> On Wed, Mar 17, 2010 at 4:03 AM, Glenn Camilleri  wrote:
>> Hi,
>>
>>
>>
>> I have some processes and programs that are custom made to run on FreeBSD. I
>> suspect some poor implementation of tcp in these programs, but don’t have
>> the real proof.
> [...]
>>
>> Can you kindly advise ?
>>
>
> Using the core dump is wise but ktrace will probably be easier. Just
> run like this ktrace [program] 2>&1 | less
> You should be able to spot the precise failing system call quite easily
>

Ooops, my Linux background betrayed me, sorry (was thinking of
strace). ktrace will produce a file which you later need to analyze
with kdump. Running is the same but forget the output redirection,
there is a -f switch to specify the outfile.

> Best,
> Alejandro Imass
>
>>
>>
>> BR,
>>
>> Glenn Camilleri
>>
>> --
>> Best Regards,
>> Glenn Camilleri
>>
>>
>>
>> --
>> Best Regards,
>> Glenn Camilleri
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Kernel dump crash

[Alejandro Imass]

On Wed, Mar 17, 2010 at 4:03 AM, Glenn Camilleri  wrote:
> Hi,
>
>
>
> I have some processes and programs that are custom made to run on FreeBSD. I
> suspect some poor implementation of tcp in these programs, but don’t have
> the real proof.
[...]
>
> Can you kindly advise ?
>

Using the core dump is wise but ktrace will probably be easier. Just
run like this ktrace [program] 2>&1 | less
You should be able to spot the precise failing system call quite easily

Best,
Alejandro Imass

>
>
> BR,
>
> Glenn Camilleri
>
> --
> Best Regards,
> Glenn Camilleri
>
>
>
> --
> Best Regards,
> Glenn Camilleri
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kernel panic when if_lagg is not loaded.

[Nikos Vassiliadis]

Leslie Jensen wrote:


I'm on a 8.0-RELEASE-p2 system.

Actually after more testing I found out that the line

ifconfig_iwn0="ether 00:16:ea:61:01:e8"

in my rc.conf is the culprit. If I comment it out the system will start 
but only with the wired interface working.


If you don't comment the line it causes a kernel panic?
If that's the case, you should report it to n...@. If you
could include a backtrace of the panic, it would be most helpful.



I have if_lagg_load="YES" in /boot/loader.conf

and the following in /etc/rc.conf

wpa_supplicant_enable="YES"
ifconfig_em0="up"
# ifconfig_iwn0="ether 00:16:ea:61:01:e8"
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP"

/Leslie


hm, what you do really matches the process described in the handbook.
It should work, please report it.

Nikos

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

Re: kernel panic when if_lagg is not loaded.

[Leslie Jensen]

On 2010-03-17 09:36, Nikos Vassiliadis wrote:

Leslie Jensen wrote:


I have set upp aggregation of my wlan and and wired NIC following the
instructions in the handbook.

http://www.freebsd.org/doc/handbook/network-aggregation.html

I "forgot" to add the if_lagg_load="YES" in /boot/loader.conf. When I
rebooted I got a kernel panic.

Should this be considerd normal or is it something I should report?



No, it's not normal. Please, report it in an explicit way, commands
given and/or changes to rc.conf, loader.conf etc. Try first here
questions@ and then n...@.

Nonetheless I see no such behavior on my system. if_lagg loads
automatically when needed(ifconfig lagg create etc).



Secondly I see there'a a reference to the lagg(4) man page. I think it
would help future readers of the above page if a comment about loading
if_lagg_load="YES" in /boot/loader.conf would be added.



On 8.0-STABLE if_lagg loads automatically and I think it always
did load automatically, though I am not sure. What's the FreeBSD
version you are working on?

Nikos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"


I'm on a 8.0-RELEASE-p2 system.

Actually after more testing I found out that the line

ifconfig_iwn0="ether 00:16:ea:61:01:e8"

in my rc.conf is the culprit. If I comment it out the system will start 
but only with the wired interface working.


I have if_lagg_load="YES" in /boot/loader.conf

and the following in /etc/rc.conf

wpa_supplicant_enable="YES"
ifconfig_em0="up"
# ifconfig_iwn0="ether 00:16:ea:61:01:e8"
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP"

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"