to the kernel config,
following sys/amd64/conf/NOTES
On buildkernel I get:
unknown option COMPAT_LINUX
What am I missing?
Do you also have those (from a working i386 system):
# Linux support
options
COMPAT_LINUX
options COMPAT_LINUX32
to the kernel config,
following sys/amd64/conf/NOTES
On buildkernel I get:
unknown option COMPAT_LINUX
What am I missing?
Do you also have those (from a working i386 system
:
This is on amd64 r246552
I added
options COMPAT_43
options COMPAT_LINUX
options COMPAT_LINUX32
to the kernel config,
following sys/amd64/conf/NOTES
emulation (requires COMPAT_43 and
COMPAT_FREEBSD32)
options COMPAT_LINUX32
I think I first ran up against this when I moved to 9.0 some
time ago, but yes, amd64 uses a different kernel config
option than i386 for linux compat.
I tend to leave it as a module load it if I perchance
need
I'm a FreeBSD novice, experienced with Linux audio. If on Linux the
network does work, than it works.
What is needed to have a working network on FreeBSD for all situations?
http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/
German FTP:
Unable to transfer the sbase distribution
On Mon, 21 Jan 2013 12:09:36 +0100, Ralf Mardorf
ralf.mard...@rocketmail.com wrote:
http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/
I'm sorry, I missed the link from the last comment.
http://forums.freebsd.org/showthread.php?t=29172
A long thread :S
What is your distribution for installing FreeBSD, CD , DVD ?
You can also use DVD for installing kernel.
First , download FreeBSD 8.x or 9.x DVD distribution then try to install kernel
with same way which is showing on cyberciti.biz.
or reinstall your freebsd with FreeBSD 9.1 which ask to you
On Mon, 21 Jan 2013 12:25:57 +0100, Emre Çamalan mail...@yandex.com
wrote:
What is your distribution for installing FreeBSD, CD , DVD ?
You can also use DVD for installing kernel.
First , download FreeBSD 8.x or 9.x DVD distribution then try to install
kernel with same way which is showing
On Mon, 21 Jan 2013, Ralf Mardorf wrote:
I'm a FreeBSD novice, experienced with Linux audio. If on Linux the network
does work, than it works.
What is needed to have a working network on FreeBSD for all situations?
http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/
Those
On Mon, 21 Jan 2013, Ralf Mardorf wrote:
I had to installed FreeBSD from the 8.3 DVD, because partitioning doesn't
work on my machine, when I used 9.0. I updated the Kernel to 9.1, world and
the ports tree.
The ports tree is not branched (ports are identical for all versions of
FreeBSD), so
Thank you Warren.
Regards,
Ralf
___
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
to NetC.
HostFoo has a default route (only) to GW2 and can ping a host on NetC
because it gets an ICMP redirect from GW2 (FreeBSD) to GW3. However, if
HostFoo pings a a host on NetA it DOES NOT get a ICMP redirect from GW2.
Looking through the kernel code, which is where I need help, it seems
routes
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
Unread portion of the kernel message buffer:
panic: sbflush_internal: cc 4294965848 || mb 0 || mbcnt 0
cpuid = 0
KDB: stack
Hello,
if I wanna build a kernel module standalone (without the kernel e.g. for
testing) I do it the following way (wlan in this example):
cd /usr/src/sys/modules/wlan
make all
maybe make install if I wanna install it.
Now I want do build the linux.ko module with the symbol DEBUG defined
On 01/03/2013 06:57 AM, Martin Laabs wrote:
Hello,
if I wanna build a kernel module standalone (without the kernel e.g. for
testing) I do it the following way (wlan in this example):
cd /usr/src/sys/modules/wlan
make all
maybe make install if I wanna install it.
Now I want do build
Hi
This can be considered a follow up to the message How to keep
freebsd-update from trashing custom kernel? sent to this list by Brett
Glass on August 13th 2012 (see [1]). Unfortunately there is no solution
to the problem in that thread (or I cannot see it).
I am running currently running 9.0
--On January 2, 2013 6:45:50 PM +0100 andreas scherrer
ascher...@gmail.com wrote:
Hi
This can be considered a follow up to the message How to keep
freebsd-update from trashing custom kernel? sent to this list by Brett
Glass on August 13th 2012 (see [1]). Unfortunately there is no solution
The confusion comes from the fact that the original behavior of
freebsd-update was NOT to update the kernel binaries if a custom kernel was
detected.
FYI my /etc/freebsd-update.conf has
# Components of the base system which should be kept updated.
#Components src world kernel
Components src
on 2.1.13 19:15 Paul Schmehl said the following:
--On January 2, 2013 6:45:50 PM +0100 andreas scherrer
And from experience this is what it will do: replace /boot/kernel/kernel
which is my custom kernel with a GENERIC kernel.
As it seems that freebsd-update works by comparing a hash
On Wed, Jan 2, 2013 at 11:18 AM, andreas scherrer ascher...@gmail.comwrote:
This is no longer true, though it was true at the time that was written...
-
However, freebsd-update will detect and update the GENERIC kernel in
/boot/GENERIC (if it exists), even if it is not the current (running
--On January 2, 2013 8:18:38 PM +0100 andreas scherrer
ascher...@gmail.com wrote:
on 2.1.13 19:15 Paul Schmehl said the following:
--On January 2, 2013 6:45:50 PM +0100 andreas scherrer
And from experience this is what it will do: replace /boot/kernel/kernel
which is my custom kernel
this is what it will do: replace
/boot/kernel/kernel which is my custom kernel with a GENERIC kernel.
As it seems that freebsd-update works by comparing a hash of
/boot/kernel/kernel with the GENERIC kernel's hash I checked the md5
and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel
On 02/01/2013 20:55, Paul Schmehl wrote:
I wasn't thinking when I wrote this. Freebsd-update pulls *binary*
copies of files, so you're not ever going to get the src files to
rebuild your kernel from freebsd-update. You need to pull those in
using svn.
Not so. Take a look at /etc/freebsd
Hi,
I would like to know why quota is not enabled in the stock kernel..
I remembered that it is not enabled since freebsd 3.5 or freebsd 4 generation.
Now in freebsd 9.0, it still neeed a kernel rebuild.
I have heard it has performance issue (GIANT lock) about quota.
Regards,
Patrick
I was going ahead and attempting to install libreoffice 3.5.7 and it was
going along nicely until the kernel panicked. When I rebooted, I tried
to start the install again but it aborted so I went to make clean in
/usr/ports/editors/libreoffice when the kernel panicked again. I have
two of all
Hi all,
Two days ago, I have installed a FreeBSD 9.1 RC-3 machine and I am
receiving a lot of messages every day like this:
Nov 30 14:41:41 newfbsd kernel: in_arp: 03:bf:0a:c4:00:3d is multicast
Nov 30 15:18:40 newfbsd last message repeated 111 times
It is a MAC address used by Microsoft NLB
Hi All,
I posted a blog yesterday with regards to a FreeBSD kernel panic in
FreeBSD 8.3 at
http://blog.hostileadmin.com/2012/11/05/freebsd-kernel-panic-in-udp_input/
in case anyone has any interest...
--
Take care
Rick Miller
___
freebsd-questions
I'm seeing that on 9.1-RC2 (i386), clang can no longer build a kernel
that boots. Any kernel I build would get stuck at Timecounters tick
every 1.000 msec. However, building the same kernel with gcc has no
problems. Also, if I build the kernel with clang from 9.0-RELEASE, it
also works fine. I
Let me clarify. If I build the 9.1-RC2 kernel using the clang binary
from 9.0-RELEASE, it boots fine.
On Sun, Oct 28, 2012 at 9:41 AM, Mike Cui cui...@gmail.com wrote:
I'm seeing that on 9.1-RC2 (i386), clang can no longer build a kernel
that boots. Any kernel I build would get stuck
Hi,
what controls how parts of kernel are built, that is, built-in or modular ?
For example, I want to:
- build a kernel that has eveything built in
- build a kernel that has everything possible (what controls the impossible ?)
built as modules
- build a kernel that has mixed support, e.g
Hi,
On Thu, 25 Oct 2012 06:41:44 + (UTC)
jb jb.1234a...@gmail.com wrote:
Hi,
what controls how parts of kernel are built, that is, built-in or
modular ? For example, I want to:
- build a kernel that has eveything built in
this is normally not possible as some thing conflict which each
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
Just check how a custom kernel is build. You can then build three
versions of it. One with nothing, one with the modules you want and one
with the non-conflicting modules build-in.
Just read the handbook regarding custom kernels
Hi,
On Thu, 25 Oct 2012 07:26:27 + (UTC)
jb jb.1234a...@gmail.com wrote:
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
Just check how a custom kernel is build. You can then build three
versions of it. One with nothing, one with the modules you want and
one
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
What decides about that (built-in or module) ?
# kldstat -v |grep cd9660
414 cd9660
# kldstat -v |grep ext2fs
151 0xc9911000 11000ext2fs.ko (/boot/kernel/ext2fs.ko)
538 ext2fs
jb
On Thu, 25 Oct 2012 14:51:38 +0700, Erich Dollansky wrote:
The modules are always build, at least to my knowledge. So, you do not
need any options for this. You just need to load them later.
The means of /etc/src.conf can be used to skip certain things
during a kernel + world build. For example
jb jb.1234abcd at gmail.com writes:
...
What decides about that (built-in or module) ?
# kldstat -v |grep cd9660
414 cd9660
# kldstat -v |grep ext2fs
151 0xc9911000 11000ext2fs.ko (/boot/kernel/ext2fs.ko)
538 ext2fs
That was already clarified.
jb
Hello,
On 09/29/12 13:02, Fabian Keil wrote:
Martin Laabs mailingli...@martinlaabs.de wrote:
So - is there a way (i.e. a loader.conf entry) how I can tell the loader
which partition I wanna have attached with a passphrase?
Whether or not the kernel requests the passphrase depends
on whether
Martin Laabs mailingli...@martinlaabs.de wrote:
I have two partitions encrypted with GELI: ada0s2 and ada0s3. The loader
(located at an unencrypted part of the harddisk) loads the kernel and the
kernel asks me for the passphrase for ada0s2 to attach it afterwards.
However - my root file
Hello,
I have two partitions encrypted with GELI: ada0s2 and ada0s3. The loader
(located at an unencrypted part of the harddisk) loads the kernel and the
kernel asks me for the passphrase for ada0s2 to attach it afterwards.
However - my root file system is not at ada0s2.elia but on ada0s3.elia
Hi All,
I've generated a DVD iso and imported it into a provisioning platform.
After this integration, a decision was made to rebuild the kernel
with an option enabled. As opposed to executing a full `make
release`, I just want to build the kernel distribution. In reading
the manpage, it looks
On Sep 24, 2012, at 6:03 AM, Rick Miller wrote:
Hi All,
I've generated a DVD iso and imported it into a provisioning platform.
After this integration, a decision was made to rebuild the kernel
with an option enabled. As opposed to executing a full `make
release`, I just want to build
On 19/09/2012 23:59, Polytropon wrote:
The terminology is simple and as follows:
A disk is a disk, e. g. /dev/ad0.
A slice is a DOS primary partition on the disk, e. g. /dev/ad0s1.
A partition is a subdivision of a slice, e. g. /dev/ad0s1a.
Partitions can be used without a slice that
the filesystems. I'm
also running the GENERIC-kernel, I've done this using the FreeSBIE
live CD.
What procedure did you use to clone? There basically is
the one way, using dump + restore on partitions (not
slices!), or dd on either partitions, slices, or the
whole disk.
I maybe not so
machine, edited /etc/fstab to match the filesystems. I'm
also running the GENERIC-kernel, I've done this using the FreeSBIE
live CD.
However, when I boot I get to BTX loader (so I guess boot0 and boot2
is correct), that can't load kernel nor kernel.old. see attached
img1.png . I can't ls
on the target machine, ran dump the source machine and restore
on the target machine, edited /etc/fstab to match the filesystems. I'm
also running the GENERIC-kernel, I've done this using the FreeSBIE
live CD.
What procedure did you use to clone? There basically is
the one way, using dump + restore
to clone. I've setuped an identical copy of the
slices on the target machine, ran dump the source machine and restore
on the target machine, edited /etc/fstab to match the filesystems. I'm
also running the GENERIC-kernel, I've done this using the FreeSBIE
live CD.
What procedure did you use
an old (yes, very old) BSD 4.7 machine on
my work that I need to clone. I've setuped an identical copy of the
slices on the target machine, ran dump the source machine and restore
on the target machine, edited /etc/fstab to match the filesystems. I'm
also running the GENERIC-kernel, I've done
the 'ndis' device back in, but when I follow the
directions on the ndis(4) manpage, and add:
options NDISAPI device ndis and try to re-compile the kernel
(config, cd, make depend, make), linking fails, with:
if_ndis.o(.text+0x1104): In function 'ndis_detach':
: undefined
-compile the kernel (config, cd, make depend, make), linking
fails, with:
if_ndis.o(.text+0x1104): In function 'ndis_detach':
: undefined reference to 'ndis_free_amem'
if_ndis.o(.text+0x1194): In function 'ndis_attach':
: undefined reference to 'ndis_alloc_amem'
Obviously, the config
Date: Mon, 10 Sep 2012 15:32:30 -0400
Subject: Re: trouble building 'ndis' device driver into stripped-down custom
kernel.
From: Gardner Bell gardnerb...@gmail.com
On 10 September 2012 15:23, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
Enviorment is FreeBSD 8.3, i386
I'm
on the ndis(4) manpage, and add:
options NDISAPI
device ndis
and try to re-compile the kernel (config, cd, make depend, make), linking
fails, with:
if_ndis.o(.text+0x1104): In function 'ndis_detach':
: undefined reference to 'ndis_free_amem'
if_ndis.o(.text+0x1194
Does this procedure hold good for a device driver module's patch as well?
On Thu, Sep 6, 2012 at 3:40 PM, Julian H. Stacey j...@berklix.com wrote:
Venkat Duvvuru wrote:
Hi,
Could somebody please point me to a procedure to apply a patch to the
sources?
I have a driver patch that I would
Venkat Duvvuru wrote:
Does this procedure hold good for a device driver module's patch as well?
Yes
On Thu, Sep 6, 2012 at 3:40 PM, Julian H. Stacey j...@berklix.com wrote:
Venkat Duvvuru wrote:
Hi,
Could somebody please point me to a procedure to apply a patch to the
sources?
Hi,
Could somebody please point me to a procedure to apply a patch to the
sources?
I have a driver patch that I would like to commit.
/Venkat
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
Venkat Duvvuru wrote:
Hi,
Could somebody please point me to a procedure to apply a patch to the
sources?
I have a driver patch that I would like to commit.
If you want to send from local mail client
man send-pr
If you want to send via web
Hi,
here is a kernel dump I got recently:
# ls -al /var/crash/
total 285944
drwxr-x--- 2 root wheel512 Sep 5 06:21 .
drwxr-xr-x 25 root wheel512 Sep 5 08:30 ..
-rw-r--r-- 1 root wheel 2 Sep 5 06:21 bounds
-rw--- 1 root wheel 105813 Sep 5 06:21
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
You left out some devices that are required by other devices in your
configuration
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
Or just stay
Jamie Paul Griffin ja...@kode5.net writes:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never
got such a one; here is my kernel configuration file and the
building
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ]
Jamie Paul Griffin ja...@kode5.net writes:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never
got
have a problem when I try to build my own kernel. I had never
got such a one; here is my kernel configuration file and the
building errors that it makes.
Or just stay with GENERIC; most consumer PCs have no real reason to need
a customized kernel.
I agree. It boots quickly
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
i am beginning to question how computers work.
i am using darwin 10.0.0.
is there a place or way that i can get a thoroughly commented kernel of this
version of unix so that i can learn from it and ask inteligent questions.
i think this would be a good place to start from
a thoroughly commented kernel of this
version of unix so that i can learn from it and ask inteligent questions.
i think this would be a good place to start from.
FreeBSD ( other BSDs Linuxes all) offer full sources on web ftp sites.
See http://www.freebsd.org download.
There's various books.
Books
Hi,
I have FreeBSD 9.0 (p4) with custom kernel.
uname -i says it:
HOMEWIFI90
However, when I run freebsd-update fetch command it would like to
update my kernel as well:
freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.0-RELEASE
On Mon, Aug 20, 2012 at 11:47 AM, Denis piloy...@gmail.com wrote:
Hi,
I have FreeBSD 9.0 (p4) with custom kernel.
uname -i says it:
HOMEWIFI90
However, when I run freebsd-update fetch command it would like to
update my kernel as well:
freebsd-update fetch
Looking up
Hi Alexandre,
Have you rebuilt your custom kernel after ?
This is described in the Handbook in the section 25.2.2
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html
Yes, I rebuilt my custom kernel after. But this doesn't help - every
time I run
On Sun, 19 Aug 2012 19:43:14 -0400
Michael Powell articulated:
{snip}
Keep in mind whenever you install a new kernel your present kernel
(and its matching modules) get moved to kernel.old. What this means
is that the GENERIC you have with a base install will be moved to
kernel.old and can
On Mon, 20 Aug 2012 14:37:40 +0400, Denis wrote:
Hi Alexandre,
Have you rebuilt your custom kernel after ?
This is described in the Handbook in the section 25.2.2
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html
Yes, I rebuilt my custom
Then why not follow my suggestion of _letting_ freebsd-update
update the kernel, but _use_ a different one instead which it
won't touch? In /boot/loader.conf:
kernel=mykernel
bootfile=/boot/mykernel/kernel
Now freebsd-update can happily alter the default kernel without
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
Keep in mind whenever you install a new kernel your present kernel (and its
matching modules) get moved to kernel.old. What this means is that the
GENERIC you have with a base install will be moved to kernel.old and can be
used
the sort of problem you are referring
to and would make it easier to revert to a specific kernel if required.
I never received even a single response so I guess it was not a well
received concept.
I think it's a valid and idiot-proof suggestion; however, the handbook
information regarding building
On Mon, 20 Aug 2012 14:13:44 +0100, Jamie Paul Griffin wrote:
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
Keep in mind whenever you install a new kernel your present kernel (and its
matching modules) get moved to kernel.old. What this means is that the
GENERIC you have
Polytropon writes:
Very good point! I'd clear the /usr/src/obj directory as pointed out,
then build a generic kenel, install it and boot from it. Then you
know you've got a working kernel to fall back on.
You could then make a copy of that kernel, e. g. from its initial
On Mon, 20 Aug 2012 09:46:30 -0400, Robert Huff wrote:
Polytropon writes:
Very good point! I'd clear the /usr/src/obj directory as pointed out,
then build a generic kenel, install it and boot from it. Then you
know you've got a working kernel to fall back on.
You could
== Denis wrote on Mon 20.Aug'12 at 16:41:56 +0400 ==
Then why not follow my suggestion of _letting_ freebsd-update
update the kernel, but _use_ a different one instead which it
won't touch? In /boot/loader.conf:
kernel=mykernel
bootfile=/boot/mykernel/kernel
Now
If you're building your own customised kernel, why don't you just build the
entire system from source? I've not used freebsd-update yet and probably
won't. Is it just a matter of time, i.e. waiting for the compilation to
finish?
Actually I built this system from source. And now use freebsd
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
antonin tessier wrote:
Hi,
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
[snip]
# make kernel KERNCONF=GOLLUM
MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM
Stop
On Sun, 12 Aug 2012 20:50:43 -0600, Brett Glass wrote:
Everyone:
Just ran freebsd-update (fetch, then install) on a system on which
I run a customized kernel, and discovered that it has overwritten
my custom kernel... even though I'd copied the original to
/boot/GENERIC when I first
At 05:24 AM 8/13/2012, Polytropon wrote:
That seems to be the default behaviour, as freebsd-update is
not supposed to be used with a custom kernel. It works with
GENERIC kernels (because it updates them by overwriting).
Actually, freebsd-update is claimed to respect custom kernels. See
On Mon, Aug 13, 2012 at 9:35 AM, Brett Glass br...@lariat.net wrote:
Actually, freebsd-update is claimed to respect custom kernels. ...
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone
On Mon, 13 Aug 2012 10:35:12 -0600, Brett Glass wrote:
At 05:24 AM 8/13/2012, Polytropon wrote:
That seems to be the default behaviour, as freebsd-update is
not supposed to be used with a custom kernel. It works with
GENERIC kernels (because it updates them by overwriting).
Actually
At 11:33 AM 8/13/2012, Michael Sierchio wrote:
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
That is what I thought it would do, based on the docs. However,
when I recently ran freebsd
At 12:59 PM 8/13/2012, Polytropon wrote:
I've never seen a system having a /boot/GENERIC directory
containing the GENERIC kernel.
It does not come that way. The Handbook recommends that one
manuall copy the original kernel from the distribution into
/boot/GENERIC before building a custom
On Mon, Aug 13, 2012 at 1:07 PM, Brett Glass br...@lariat.net wrote:
At 11:33 AM 8/13/2012, Michael Sierchio wrote:
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
That is what I thought
Everyone:
Just ran freebsd-update (fetch, then install) on a system on which
I run a customized kernel, and discovered that it has overwritten
my custom kernel... even though I'd copied the original to
/boot/GENERIC when I first installed the system. I was under the
impression that creating
telecommunication business, yesterday night we experience a strange kernel
panic and our server hanged, just contact collocation as asked for physical
reboot,
in attached, you can find screen shot of rebooting the server . i really thank
full if you take a look and advise me any update.
looking forward
on it and do
telecommunication business, yesterday night we experience a strange
kernel panic and our server hanged, just contact collocation as asked
for physical reboot,
in attached, you can find screen shot of rebooting the server . i
really thank full if you take a look and advise me any
I think it's likely that it is a 64-bit installation.
Not sure about that. How could the amd64 OS be installed
and run on a i386 machine?
it cannot.
___
freebsd-questions@freebsd.org mailing list
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an
i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So
I tried both:
you've got into wrong directory
/usr/src/sys/i386/conf is right
/usr/src/sys/amd64/conf is wrong, unless you have 64-bit
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an i686
CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So I
tried both:
you've got into wrong directory
/usr/src/sys/i386/conf is right
/usr/src/sys/amd64/conf is wrong, unless you have 64-bit
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on your
nonsense. 64-bit distribution doesn't run on 32-bit computer.
___
freebsd-questions@freebsd.org mailing list
set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on your
nonsense. 64-bit distribution doesn't run on 32-bit computer.
*PRECISELY* why the OP is having problems. He _is_ trying to build amd64
kernel
...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on
your
nonsense. 64-bit distribution doesn't run on 32-bit computer
To: Chris Hill ch...@monochrome.org
Cc: RW rwmailli...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit
distribution on your
: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Chris Hill ch...@monochrome.org
Cc: RW rwmailli...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may
: unknown option I586_CPU
How can I set 586/686 (you're supposed to set both) in my kernel conf ?
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd
I686_CPU
(I also tried them both lowercase, like i686_cpu)
But all of these fail:
GENERIC: unknown option I586_CPU
How can I set 586/686 (you're supposed to set both) in my kernel conf ?
You're sure it's an i686? Do you have the amd64 distribution, or i386?
If the former, then in /usr
On Mon, 6 Aug 2012 16:53:04 -0700 (PDT)
Jason Usher wrote:
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's
an i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working.
So I tried both:
That's the amd64 (64-bit) GENERIC
101 - 200 of 4710 matches
Mail list logo
