Hello All
Kindly excuse the trouble please. I am trying to
compile a custom code I have written at the nfs layer and I am getting the
following error
/usr/src/sys/nfsclient/nfs_bio.c: In function 'nfs_read_disk':
/usr/src/sys/nfsclient/nfs_bio.c:1832: warning: implicit declarati
in the handbook -- i.e.,
> the kernel and userland components that are now obsolete, and their
> replacements -- might be of some help to users. The primary author of
> the new code did add some material to various notes and manpages, but
> he has been very busy writing and debugging co
> Now I think I'll try to rebuild the kernel with "options ATA_CAM" and drop
> "device atapicam".
>
> This question needs to be better resolved in time for FreeBSD 9.0-RELEASE.
>
> I cross-post this message to freebsd-curr...@freebsd.org so the develope
> On 11/27/11, Lowell Gilbert wrote:
> > "b. f." writes:
> >>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
> >>> > > config file?
> >>> > > Are they redundant? Kern
On 11/27/11, Lowell Gilbert wrote:
> "b. f." writes:
>
>>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
>>> > > config file?
>>>
>>> > > Are they redundant? Kernel will buil
"b. f." writes:
>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
>> > > config file?
>>
>> > > Are they redundant? Kernel will build with both these options, but will
>> > > it
> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
> > > config file?
>
> > > Are they redundant? Kernel will build with both these options, but will
> > > it make things go awry? Is ATA_CAM deprecated?
They a
from "b. f." :
> If the kernel versions were compatible, and the set of modules were
> the same, I suppose you could set MODULES_WITH_WORLD and
> KODIR=/boot/modules during buildworld and installworld, to build the
> modules as part of buildworld and install them i
"Thomas Mueller" writes:
> > What is the role of "options atapicam" and "device ATA_CAM" in kernel
> > config file?
> > Are they redundant? Kernel will build with both these options, but will it
> > make things go awry? Is ATA_CAM depr
On Fri, 25 Nov 2011 at 19:27:54, Damien Fleuriot wrote:
> On 11/24/11 4:17 PM, b. f. wrote:
>>
>> If you are going to build most of the modules, but only want to exclude
>> a few, then add the directories of the modules to be excluded (relative
>> to /usr/src/sys/modules) to WITHOUT_MODULES, for
TH_MODULES=geom_label if_lagg linprocfs linsysfs linux mfi_linux
I have then run, from /usr/src :
make buildkernel
make installkernel
I notice, at the end of installkernel:
[snip]
===> xl (install)
install -o root -g wheel -m 555 if_xl.ko /boot/kernel
install -o root -g wheel -m 555 if_xl
"Thomas Mueller" writes:
> What is the role of "options atapicam" and "device ATA_CAM" in kernel config
> file?
>
> Are they redundant? Kernel will build with both these options, but will it
> make things go awry? Is ATA_CAM deprecated?
Makefile and
>> /usr/src/sys/conf/kern.post.mk for details. You may also save some
>> time by using one of your faster machines to build the OS for the
>> slower machines.
>
> Suppose you want to build more than one kernel so as to be able to choose at
> boot time.
&
of
drivers that are not going to be linked statically into the kernel.
Build on an older Pentium II server took about 10-12% of the time!
Worth knowing about.
--Brett Glass
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
ys/modules/Makefile and
> > /usr/src/sys/conf/kern.post.mk for details. You may also save some
> > time by using one of your faster machines to build the OS for the
> > slower machines.
>
> Suppose you want to build more than one kernel so as to be able to choose at
> bo
o save some
> time by using one of your faster machines to build the OS for the
> slower machines.
Suppose you want to build more than one kernel so as to be able to choose at
boot time.
Then you might not want to build modules redundantly. So how would you make
the modules from /boot/kern
9.0-RC2
> kernels for various machines, and on some of the older and slower
> ones it's been taking quite a long time. One of the reasons for
> this is that even if you strip 98% of the drivers out of the
> kernel, they are all still built as loadable modules. The machines
> in quest
> Happy Thanksgiving! This week, I've been building FreeBSD 9.0-RC2
And to you, too.
> kernels for various machines, and on some of the older and slower
> ones it's been taking quite a long time. One of the reasons for
> this is that even if you strip 98% of the drivers out
ip 98% of the drivers out of the
> kernel, they are all still built as loadable modules. The machines
> in question will NEVER use those modules, so it's a waste of time
> and disk space.
>
> How hard would it be to create a build target for "make" that would
> avoid
Everyone:
Happy Thanksgiving! This week, I've been building FreeBSD 9.0-RC2
kernels for various machines, and on some of the older and slower
ones it's been taking quite a long time. One of the reasons for
this is that even if you strip 98% of the drivers out of the
kernel, th
What is the role of "options atapicam" and "device ATA_CAM" in kernel config
file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtool
I updated the sources on one of my FreeBSD-8.2-STABLE servers and
rebuilt the GENERIC kernel just last night. All went well. This morning I
updated the sources on another machine and rebuilt a custom kernel and
all went well.
This evening I updated the sources on a 3rd server and the make
On Thu, 3 Nov 2011 13:48:47 -0500 (CDT)
Robert Bonomi wrote:
[snip]
> I am likely _not_ the typical user -- I run a monolithic kernel, with
> everything I need 'compiled in'; *no* loadable modules. Yeah, it can
> be a nuisance if I need something that isn't compiled
Is it safe to interrupt (Ctrl + C) while building a port
> > or kernel?
>>
> > Is it clear to interrupt the building process just by pressing Ctrl
> > + ?
>
> Yes.
Whilst it's not strictly-speaking "building", I would avoid interrupting
an install.
__
epends".
> >
> > On what you 'did wrong", and what it takes to fix it.
> >
> > e.g., if you're building a kernel the 'classial' way, that is
> > 'configure, make depend, cd , make', and realize you left
> > something out o
r?B?4c7Uz84g68zF09M=?=
> > >> To: freebsd-questions@freebsd.org
> > >> Date: Thu, 03 Nov 2011 21:10:19 +0400
> > >> Subject: Is it safe to interrupt (Ctrl + C) while building a port or
> > >> kernel?
> > >>
> > >> Sometimes, while b
On Thu, 3 Nov 2011, ? ? wrote:
Is it clear to interrupt the building process just by pressing Ctrl + ?
If it's so, do I need to run "make clean" before I start "make" one more time?
With ports, a "make clean" before rebuilding is a good idea. The build
might not be able to continue
ate: Thu, 03 Nov 2011 21:10:19 +0400
> >> Subject: Is it safe to interrupt (Ctrl + C) while building a port or
> >> kernel?
> >>
> >> Sometimes, while building process of some port or system kernel are in
> >> progress, you suddenly remember that you did s
03.11.2011, 21:20, "Robert Bonomi" :
>> If it's so, do I need to run "make clean" before I start "make" one more
>> time?
> Authoritative answer: "It depends".
>
> On what you 'did wrong", and what it takes to
Sorry,all.
I will email same message.
I am not familiar with this webmail.
Thank you very much for the understandable explanations.
I appreciate it very much.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
pt (Ctrl + C) while building a port or kernel?
>>
>> Sometimes, while building process of some port or system kernel are in
>> progress, you suddenly remember that you did something wrong and have to
>> stop, solve your mistake and start one more time.
>>
>> I
---
Inexperienced FreeBSD user: Level 1
pow 1, spd 1, vit 1,int 1,luck 1
--- On Fri, 4/11/11, Alexandre wrote:
> From: Alexandre
> Subject: Re: freebsd-update (custom kernel)
> To: "Jason Helfman" , "Michael Sierchio"
> , "masayoshi"
> Cc: fre
> From owner-freebsd-questi...@freebsd.org Thu Nov 3 12:10:08 2011
> From: =?koi8-r?B?4c7Uz84g68zF09M=?=
> To: freebsd-questions@freebsd.org
> Date: Thu, 03 Nov 2011 21:10:19 +0400
> Subject: Is it safe to interrupt (Ctrl + C) while building a port or kernel?
>
> Some
Sometimes, while building process of some port or system kernel are in
progress, you suddenly remember that you did something wrong and have to stop,
solve your mistake and start one more time.
Is it clear to interrupt the building process just by pressing Ctrl + ?
If it's so, do I need t
On Thu, Nov 03, 2011 at 09:42:12AM -0700, Michael Sierchio thus spake:
This is simply not the case. freebsd-update works on the basis of
cryptographic hashes on the binaries. It is, after all, a binary
update program. If it detects a custom kernel, it will not update the
kernel, but updates
>
>
> I beg to differ. If you run a kernel called CUSTOM, it won't work. And if
> you run a custom kernel called GENERIC, the moment you upgrade, you custom
> kernel is no longer custom.
>
> All of this aside, I would be interested in hearing how you are able to
> avo
This is simply not the case. freebsd-update works on the basis of
cryptographic hashes on the binaries. It is, after all, a binary
update program. If it detects a custom kernel, it will not update the
kernel, but updates userland programs. It doesn't *care* what your
kernel config name i
On Thu, Nov 03, 2011 at 09:19:29AM -0700, Michael Sierchio thus spake:
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman wrote:
I does work fine with a custom kernel, as long as you are running and
maintaining the actual update server that distributes.
I don't think that's relevant.
On Thu, Nov 03, 2011 at 08:49:16AM -0700, masayoshi thus spake:
I would like to know about freebsd-update command.
It is rumoured that freebsd-update command does not work well with custom
kernel.
First question is the following :
su -
#freebsd-update fetch
#freebsd-update install
Does this
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman wrote:
> I does work fine with a custom kernel, as long as you are running and
> maintaining the actual update server that distributes.
I don't think that's relevant. It works fine with th
It will work fine - it won't attempt to update the kernel.
On Thu, Nov 3, 2011 at 8:49 AM, masayoshi wrote:
> I would like to know about freebsd-update command.
> It is rumoured that freebsd-update command does not work well with custom
> kernel.
> First question is the fo
I would like to know about freebsd-update command.
It is rumoured that freebsd-update command does not work well with custom
kernel.
First question is the following :
> su -
#freebsd-update fetch
#freebsd-update install
Does this command work well?
The answer is .
[A].Always work,
Compiling in options TCP_SIGNATURE solved the issue.
2011/10/18 Suicide Cries
> Hello FreeBSD team,
>
> I am setting up OpenBGP on FreeBSD 8.2 and encountering an issue. We are
> using md5 authentication with our ISP and "no kernel support for PF_KEY" and
> "m
Hello FreeBSD team,
I am setting up OpenBGP on FreeBSD 8.2 and encountering an issue. We are
using md5 authentication with our ISP and "no kernel support for PF_KEY" and
"md5sig not available, disabling". Am I missing a device in my kernel
configuraton? Other than the G
Hi!
Q1:
Is it possible to set different NICE priorities on different kernel
subsystems?
For example, can I prioritize the interrupt handling of the NIC bge1
([irq23: bge1]) over the interrupt handling of NIC bge0 ([irq22: bge0])?
...and can I make the usb subsystem ([usb0], [usb1], [usb2
On 08/31/2011 11:05 AM, Gene wrote:
In reference to the message " ia64 kernel conf error BRIDGE" I simply
deleted the option. Also had to delete option IPSEC_ESP.
Compile proceeded normally until I got:
xform_ipcomp.o(.text+0xe3c): In function
`ipcomp_output':
/usr/s
On Wed, Aug 31, 2011 at 09:28:55AM -0500, Gene wrote:
> While attempting to ecompile the 8.1 ia64 kernel, the following error was
I think you mean amd64.
> produced:
>
> /usr/src/sys/amd64/conf/BRIGHTSTAR: unknown optio
In reference to the message " ia64 kernel conf error BRIDGE" I simply
deleted the option. Also had to delete option IPSEC_ESP.
Compile proceeded normally until I got:
xform_ipcomp.o(.text+0xe3c): In function
`ipc
While attempting to ecompile the 8.1 ia64 kernel, the following error was
produced:
/usr/src/sys/amd64/conf/BRIGHTSTAR: unknown option
"BRIDGE"
*** Error code 1
Is this option no longer supported? Is there an a
eem to
be quite different from what is required to get things working
directly inside the kernel, such as the "Giant" locking mechanism
which doesn't seem to be supported anymore (according to the
compiler error messages).
The only thing I'm not sure is:
How am I supposed to c
is required to get things working
directly inside the kernel, such as the "Giant" locking mechanism
which doesn't seem to be supported anymore (according to the
compiler error messages).
The only thing I'm not sure is:
How am I supposed to change former k
2011-08-24 09:54, Polytropon skrev:
In the past years, I could use a very simple PCI TV card
with FreeBSD. It's a Haupauge WinTV supported by the
bktr driver (BT878) that I've always included in my
system kernel.
I have a winfast tv2000
I have copied this from my previous con
In the past years, I could use a very simple PCI TV card
with FreeBSD. It's a Haupauge WinTV supported by the
bktr driver (BT878) that I've always included in my
system kernel.
I have copied this from my previous configuration:
# TV
device bktr
Hello,
Kernel panics if clients hit the nfs server sufficiently hard -
happens repeatedly with 13 clients logging in at the same approximate
time, using nfsv4 mounted homes.
server is running freebsd 8.2-RELEASE-p2. clients are linux 2.6.38-10
Running a memtest on the server now to rule out bad
On Thu, Aug 18, 2011 at 3:25 PM, Clinton Adams wrote:
> Hello,
>
> Kernel panics if clients hit the nfs server sufficiently hard -
> happens repeatedly with 13 clients logging in at the same approximate
> time, using nfsv4 mounted homes.
>
> server is running freebsd 8.2-RE
> On 8/9/11 10:33 PM, Daryl Sayers wrote:
>> I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
>> had a few kernel panics over the last few weeks and would like to capture
>> a core dump. I have added the following to /etc/rc.conf
>>
>> dum
On 8/9/11 10:33 PM, Daryl Sayers wrote:
> I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
> had a few kernel panics over the last few weeks and would like to capture
> a core dump. I have added the following to /etc/rc.conf
>
> dumpdev="AUTO&q
hey folks,
i have a problem related to a fresh-installed freebsd8.2-server,
acting as host for 7 jails(mysql, apache, solr, ...).
we are using AMD64 / GENERIC at the moment.
this kind of kernel-panic occurs from time to time(about once a month,
no regular basis
I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
had a few kernel panics over the last few weeks and would like to capture
a core dump. I have added the following to /etc/rc.conf
dumpdev="AUTO"
dumpdir=/var/crash
The /var/crash is a 5G filesystem (with 4.8G f
Hello!
I can't use freebsd CURRENT kernel that was compiled by clang. It prints
"Unknown error: -512"
Use of world compiled by clang is possible and causes no problem.
But if I install kernel by clang it says "Unknow error: -512" in unexpected
places:
- while booting
- wh
On 7/2/2011 1:10 PM, ahmad javadi wrote:
hi
i am new in kernel socket programming in free bsd.is there any chance that
someone send me a simple code which creates a socket with an local host or
any address and begins to send some packets to the local host.im in a very
need of this help.
thanks
On 7/2/2011 1:10 PM, ahmad javadi wrote:
hi
i am new in kernel socket programming in free bsd.is there any chance that
someone send me a simple code which creates a socket with an local host or
any address and begins to send some packets to the local host.im in a very
need of this help.
thanks
hi
i am new in kernel socket programming in free bsd.is there any chance that
someone send me a simple code which creates a socket with an local host or
any address and begins to send some packets to the local host.im in a very
need of this help.
thanks
per...@pluto.rain.com writes:
> Frederic Perrin wrote:
>
>> ... I don't know what MCA, DRD, SNOOP and {D,G}CACHE stand for...
>
> MCA = Machine Check Architecture.
> DRD here probably refers to a data read cycle.
> SNOOP has to do with hardware-maintained cache coherency.
> DCACHE = data cache.
>
Frederic Perrin wrote:
> ... I don't know what MCA, DRD, SNOOP and {D,G}CACHE stand for...
MCA = Machine Check Architecture.
DRD here probably refers to a data read cycle.
SNOOP has to do with hardware-maintained cache coherency.
DCACHE = data cache.
Google and/or Wikipedia may help with the de
Hello list,
The following appeared in the dmesg buffer of my FreeBSD server. From my
reading of x86/x86/mca.c, this means that the CPU had two (correctable)
cache errors. This doesn't help me much, as I don't know what MCA, DRD,
SNOOP and {D,G}CACHE stand for... Is it a transient error? Should I
s
>> root@m6500.local:/usr/obj/usr/src/sys/GENERIC
>>>
>>> where r223017 is the current svn revision number from which my
>>> system is compiled (kernel and userland).
>> Does this only apply if you checkout with svn ?
>> I run current on a machine, upda
where r223017 is the current svn revision number from which my
>> system is compiled (kernel and userland).
> Does this only apply if you checkout with svn ?
> I run current on a machine, update with csup and have get r number with uname
>
>
Obviously only works if you checke
On 06/16/2011 02:32 PM, Brandon Gooch wrote:
> That would be uname(1):
>
> $ uname -v
> FreeBSD 9.0-CURRENT #0 r223017: Sun Jun 12 13:55:34 CDT 2011
> root@m6500.local:/usr/obj/usr/src/sys/GENERIC
>
> where r223017 is the current svn revision number from which my
> sy
On Thu, Jun 16, 2011 at 7:16 AM, Robert Huff wrote:
>
> For some time now, people have been referring to what build
> they're using by the 'r' number, which I believe to be part of svn.
> How would one go about determining this value
would one go about determining this value for the
>> installed kernel?
> I'm not sure you can: the revision only shows up if you have svn
> installed (devel/subversion-freebsd) and have built the kernel from code
> checked out from the svn server.
>
You might want to read:
http
On Thu, 16 Jun 2011 08:16:45 -0400
Robert Huff wrote:
> For some time now, people have been referring to what build
> they're using by the 'r' number, which I believe to be part of svn.
> How would one go about determining this value for the
> installed ke
For some time now, people have been referring to what build
they're using by the 'r' number, which I believe to be part of svn.
How would one go about determining this value for the installed
kernel?
On May 30, 2011, at 4:53 PM, Warren Block wrote:
> On Mon, 30 May 2011, Adam Vande More wrote:
>> Perhaps this is the one you meant?
>> http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
>
> That's the one! Thanks!
>
>> Actually the two threads touch on the same subjec
[...]
PS: I don't suppose anyone knows a real good simple blow by blow total
newby dialog, as to how to realiably and correctly create and setup Jails
on FreeBSD 8.0? All the man pages I've found so far, are way over my
head. Good "Reference" material admittedly, but no good as an
instruction
On 5 Jun 2011 at 16:55, Michael Powell wrote:
> per...@pluto.rain.com wrote:
> [snip]
> >
> > Power supplies do fail occasionally, and not always in obvious
> > ways such as failing to turn on at all. The output voltages may be
> > a little too high or too low, or they may be correct but with
>
per...@pluto.rain.com wrote:
[snip]
>
> Power supplies do fail occasionally, and not always in obvious
> ways such as failing to turn on at all. The output voltages may
> be a little too high or too low, or they may be correct but with
> excessive ripple or electrical noise; or the supply may be
p messing with the blessed things!
I have a sick Land Rover to fix too. Gearbox rear oil seal, also rear
drive shaft UJ's. At least I can use big hammers on that sometimes...
(Therapy!) Oh, the grass needs cutting, and I'm now also under
instruction to change the bed, when the cat's
x27;t sound like an issue to me either as it wouldn't touch the
kernel or any modules.
I remember on other boards that went on me in the past with
capacitor issues, a bunch of orange stuff starts leaking out
of them when they blow up.
A leaking capacitor has surely gone bad, but th
so much
nicer if you don't have to keep messing with the blessed things!
I have a sick Land Rover to fix too. Gearbox rear oil seal, also rear
drive shaft UJ's. At least I can use big hammers on that sometimes...
(Therapy!) Oh, the grass needs cutting, and I'm now also under
Kaya Saman wrote:
> > Did you apply any updates shortly before it started to fail?
>
> No updates! I did however, install unrar through ports.
Intuitively, that seems unlikely to have triggered the problem.
> I remember on other boards that went on me in the past with
> capacitor issues, a bunc
[...]
Hmmm Hard drives do not like heat! Check the PSU voltages with a
meter, for accuracy and ripple. Failing SMPS's can do all sorts of odd
things.
Capacitor problems. Been there done that. They can be changed for very
low cost, other than your time.
DaveB
You might guess by know, I k
> Everything was running fine until round about 2 days
> >> ago when the system started locking up on me?
> >>
> >> ... is there anyway to fix the kernel error quickly?
> >>
> > Did you apply any updates shortly before it started to fail?
> >
&g
; physically.
>
> Once backed up I powered down again and re-installed the 1TB SATA
> drive into ad4 position on system and completely removed the 2TB
> backup.
>
> When booted back into FreeBSD upon boot I received this error:
>
>
> WARNING: Kernel Errors Presen
the kernel error quickly?
Did you apply any updates shortly before it started to fail?
No updates! I did however, install unrar through ports.
If not, this is likely to be a hardware problem. I'd suggest
checking the power supply and the fans, running memtest86, and
taking a cl
Kaya Saman wrote:
> I have an ancient pre-HT PIV machine with <500MB RAM.
> ...
> Everything was running fine until round about 2 days
> ago when the system started locking up on me?
>
> ... is there anyway to fix the kernel error quickly?
Did you apply any updates shortly
backup.
When booted back into FreeBSD upon boot I received this error:
WARNING: Kernel Errors Present
ad4: FAILURE - WRITE_DMA48 status=51 error=4
LBA=1 ...: 1 Time(s)
g_vfs_done():ad4e[WRITE(offset=97691456, length=16384)]error = 5 ...:
1 Time(s)
The current status of the
On Fri, Jun 03, 2011 at 12:14:36AM +0200, Polytropon wrote:
> On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere
> wrote:
> > We need a kernel module to see some pdf with acrobat now?
>
> I was thinking exactly the same (without further investigation).
> Luckily xp
Polytropon wrote:
> On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere
> wrote:
> > We need a kernel module to see some pdf with acrobat now?
>
> I was thinking exactly the same (without further investigation).
I suspect it's because FreeBSD uses Linux Acroread, so
On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere
wrote:
> We need a kernel module to see some pdf with acrobat now?
I was thinking exactly the same (without further investigation).
Luckily xpdf and gv, as well as Gnome's and KDE's PDF viewer
don't need kernel modules. :-)
Le Thu, 2 Jun 2011 08:23:22 -0400,
Robert Huff a écrit :
> > think# /usr/local/etc/rc.d/linux_adobe start
> > kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko:
> > Exec format error
> > /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote:
>
> Jamie Paul Griffin writes:
>
> > Installed this port but the kernel won't load and produces the following
> > error:
> >
> > think# /usr/local/etc/rc.d/linux_adobe start
> > kldloa
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote:
>
> Jamie Paul Griffin writes:
>
> > Installed this port but the kernel won't load and produces the following
> > error:
> >
> > think# /usr/local/etc/rc.d/linux_adobe start
> > kldloa
Jamie Paul Griffin writes:
> Installed this port but the kernel won't load and produces the following
> error:
>
> think# /usr/local/etc/rc.d/linux_adobe start
> kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec
> format error
>
Hello
Installed this port but the kernel won't load and produces the following
error:
think# /usr/local/etc/rc.d/linux_adobe start
kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec
format error
/usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel m
On Wed, Jun 1, 2011 at 3:46 PM, Warren Block wrote:
> A little empirical testing:
>
> Times for buildworld after a fresh reboot, /usr/obj/usr deleted, GENERIC
> included, running ccache:
>
> default (486/586 included) 9:05.84
> nocpu I486, nocpu I586_CPU 9.27.88
> nocpu I486_CPU
On Mon, 30 May 2011, Warren Block wrote:
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it seems re
Warren Block wrote:
> On Mon, 30 May 2011, Adam Vande More wrote:
>
> > Perhaps this is the one you meant?
> >
> > http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
>
> That's the one! Thanks!
>
> > Actually the two threads touch on the same subject, and it seems
> > re
read, but that check isn't in the current code.
>
Yeah, there doesn't seem to be concrete answer that's within my ability to
diagnose. If you have some time and the burning desire, you could try some
benchmark runs on each kernel to see if 686 is as preformant as 686/586.
The f
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it seems
removal of those options is still desirable
401 - 500 of 4864 matches
Mail list logo
