e DEFAULTS and GENERIC files helpful.
> I have "makeoptions NO_MODULES=yes" statement in my kernel config file
> and the "blanktime" and "warp_saver" load modules don't get created.
Have a look at "man src.conf" for dealing with the creatio
file.
I have "makeoptions NO_MODULES=yes" statement in my kernel config file
and the "blanktime" and "warp_saver" load modules don't get created.
I need the options statements for those items so I can compile then into
the kernel.
Would it be /usr/src/sys/con
NO_MODULES=yes" statement in my kernel config file
and the "blanktime" and "warp_saver" load modules don't get created.
I need the options statements for those items so I can compile then into
the kernel.
Thanks
___
fr
Hi users!
I`ve got some trouble in the kernel configuration. I think,there is
somebody able to help me
See the attached files.
Many thanks for attention.
dmesg.boot
Description: Binary data
newkernel.2011-10-12
Description: Binary data
___
fre
On Sun, 26 Dec 2010, Bruce Cran wrote:
> On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
> Ian Smith wrote:
>
> > Probably should be easy, but from trying to parse that and lang.l I
> > get the vague impression (at best) that Rob's original should have
> > worked?
> >
> > Too much partying prob
On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
Ian Smith wrote:
> Probably should be easy, but from trying to parse that and lang.l I
> get the vague impression (at best) that Rob's original should have
> worked?
>
> Too much partying probably .. care to enlighten us?
The NOOPTION token doesn't accep
On Sun, 26 Dec 2010, Bruce Cran wrote:
> On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
> Ian Smith wrote:
>
> > Arguably unforgiving parsing and/or imprecise description. Try eg:
> >
> > nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT
> >
> > with no space[s] before comma[s], as is gener
On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
Ian Smith wrote:
> Arguably unforgiving parsing and/or imprecise description. Try eg:
>
> nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT
>
> with no space[s] before comma[s], as is generally conventional.
That doesn't work either. It should be fair
In freebsd-questions Digest, Vol 342, Issue 9, Message: 1
On Sat, 25 Dec 2010 04:38:08 -0800 Rob wrote:
> I read the guidelines in the man pages of config(5) on how to make a
> customized
> kernel config file:
>
> nooption name [, name [...]]
> noop
Hi,
I read the guidelines in the man pages of config(5) on how to make a customized
kernel config file:
nooption name [, name [...]]
nooptions name [, name [...]]
Remove the specified kernel options from the list of previously
defined options. This
2009/4/12 Robert Huff :
>
>
>> As to libusb:
>> -CURRENT does not need (actually needs to not have)
>> devel/libusb since its functionality(?) is part of the base system
>> now (post feb09).
>> What I did:
>
> This is after installing the new kernel+world, right?
>
Indeed. I didn't no
2009/4/12 Robert Huff :
>
> With respect to the changes in the USB stack:
> The old system was built in early February, before the new code
> went in. The config file has:
>
> device uhci
> device ohci
> device ehci
> device usb
> device
[posted here because could affect people who don't read curr...@]
I'm about to update a -CURRENT box, and came across this in
src/UPDATING:
GEOM_PART has become the default partition slicer for storage
devices, replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT
slic
im building a system with the amd64, version of freebsd, but the system is a
xeon nacona. the GENERIC kernel config files reads:
machine amd64
cpu HAMMER
ident GENERIC
does cpu HAMMER have a bad effect on a EM64 cpu? should that line be changed,
and if so, to wha
On 6/3/06 19:26, "Steve P." <[EMAIL PROTECTED]> wrote:
> Could someone please give me a url to a text listing of this file? I
> don't have access to fbsd right now.
http://cvsweb.FreeBSD.org/src/sys/i386/conf/GENERIC - click "download"
Ceri
--
That must be wonderful! I don't understand it at a
On Mon, 2006-03-06 at 14:26 -0500, Steve P. wrote:
> Could someone please give me a url to a text listing of this file? I
> don't have access to fbsd right now.
>
> Thanks.
>
> Steve.
I don't have a specific URL for you, but a suggestion: what about the
CVS interface on freebsd.org? I _assume_ t
Could someone please give me a url to a text listing of this file? I
don't have access to fbsd right now.
Thanks.
Steve.
--
___
Play 100s of games for FREE! http://games.mail.com/
___
freebsd-questions@
On Fri, Aug 01, 2003 at 01:37:35AM -0400, J. Seth Henry wrote:
> Stan,
> Could you describe your hardware in a bit more detail. I can't imagine
> why your system would hard lock, unless there is something seriously
> wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5
> (COM5 a
Stan,
Could you describe your hardware in a bit more detail. I can't imagine
why your system would hard lock, unless there is something seriously
wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5
(COM5 and COM6 respectively) Most mainboards only have sio0/COM1 and
sio1/COM2.
All you need in your kernel config is 'device puc'. You already appear
to have this in your config, as your system detected the adapter.
You will have to "sh MAKEDEV cuaa" (where 0 < n < NUM_PORTS) to get
the device nodes in your /dev directory.
Alternately, since they have sequential minor numbe
On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote:
> All you need in your kernel config is 'device puc'. You already appear
> to have this in your config, as your system detected the adapter.
>
Him
I've made some "progress" on this ;-(
I have created teh devices in /dev. I now have
to me like something is still not right.
Am I understnading you to say that I don't need any (nonstandard) sio
entries in my kernel config file? If that's the case, I must have a basic
misunderstanding (which is certainly possible). I thought the puc driver
was a "bridge" driver
OK, I've spent all night complaining kernels with no luck. I've read the man
page for puc, I've read the man page for sio, I've looked at the code for
puc, I've searched d Googlee, and STILL I can't get sio devices assigned to
my PCI serial port card.
It's detected as:
puc0: port 0xfce0-0xfcff i
23 matches
Mail list logo
