On Tue, Feb 10, 2009 at 03:28:09PM +0100, Uwe Laverenz wrote:
> On Tue, Feb 10, 2009 at 01:39:33PM +, Anton Shterenlikht wrote:
>
> > for me xorg 7.4 doesn't work at all on 7.1-stable i386 Compaq Armada 1700
>
> Sorry, do you really run FreeBSD with xorg on this machine? This laptop
> must be
On Tue, Feb 10, 2009 at 03:28:09PM +0100, Uwe Laverenz wrote:
> On Tue, Feb 10, 2009 at 01:39:33PM +, Anton Shterenlikht wrote:
>
> > for me xorg 7.4 doesn't work at all on 7.1-stable i386 Compaq Armada 1700
>
> Sorry, do you really run FreeBSD with xorg on this machine? This laptop
> must be
On Tue, Feb 10, 2009 at 01:39:33PM +, Anton Shterenlikht wrote:
> for me xorg 7.4 doesn't work at all on 7.1-stable i386 Compaq Armada 1700
Sorry, do you really run FreeBSD with xorg on this machine? This laptop
must be at least 10 years old, right?
> laptop, I get "no device found" at X -co
On Mon, Feb 09, 2009 at 09:31:41PM -0400, Marc G. Fournier wrote:
> On Mon, 9 Feb 2009, Glen Barber wrote:
>
> > On Mon, Feb 9, 2009 at 8:22 PM, Marc G. Fournier wrote:
> >>> Are you starting hald and dbus via rc.conf?
> >>
> >> Yes ... both mouse and keyboard have been working great ...
> >>
> >
Hi Deb ...
was this vs compiling from source?
On Mon, 9 Feb 2009, Deb Heller-Evans wrote:
Oops. Brain FART... I'm in a multi-OS environment... My answer was with
respect to a different OS, but it might be applicable to FreeBSD. I don't
have experience with nVidia on FreeBSD.
Deb Heller
Oops. Brain FART... I'm in a multi-OS environment... My answer was with
respect to a different OS, but it might be applicable to FreeBSD. I
don't have experience with nVidia on FreeBSD.
Deb Heller-Evans
Energy Science Network
MS-50A-3101
Berkeley, CA 94720
510/495-2243
Deb Heller-Evans wr
I ran into the same kind of issue. FWIW, I had better luck downloading
the nVidia drivers from the website which includes modifying the
kernel. I can now do all kinds of extra things, like spanning 2
monitors, etc (on workstations).
I can dig up my notes if you intend to go this route at so
Marc G. Fournier wrote:
On Mon, 9 Feb 2009, Glen Barber wrote:
On Mon, Feb 9, 2009 at 8:22 PM, Marc G. Fournier
wrote:
Are you starting hald and dbus via rc.conf?
Yes ... both mouse and keyboard have been working great ...
Well, that's good to hear. ;)
Thought I'd as to be safe.
Ya, t
On Mon, 9 Feb 2009, Glen Barber wrote:
On Mon, Feb 9, 2009 at 8:22 PM, Marc G. Fournier wrote:
Are you starting hald and dbus via rc.conf?
Yes ... both mouse and keyboard have been working great ...
Well, that's good to hear. ;)
Thought I'd as to be safe.
Ya, that was the easiest probl
On Mon, Feb 9, 2009 at 8:22 PM, Marc G. Fournier wrote:
>> Are you starting hald and dbus via rc.conf?
>
> Yes ... both mouse and keyboard have been working great ...
>
Well, that's good to hear. ;)
Thought I'd as to be safe.
--
Glen Barber
___
freeb
On Mon, 9 Feb 2009, Glen Barber wrote:
On Mon, Feb 9, 2009 at 8:15 PM, Marc G. Fournier wrote:
Okay, I've exhausted every google search I can think of, and not getting
anywhere, so now to ask ...
Just upgraded my motherboard / CPU (old one fried out) ... picked up an ASUS
P5Q with a Quad Co
On Mon, Feb 9, 2009 at 8:15 PM, Marc G. Fournier wrote:
>
>
> Okay, I've exhausted every google search I can think of, and not getting
> anywhere, so now to ask ...
>
> Just upgraded my motherboard / CPU (old one fried out) ... picked up an ASUS
> P5Q with a Quad Core Intel CPU ... everything boot
Okay, I've exhausted every google search I can think of, and not getting
anywhere, so now to ask ...
Just upgraded my motherboard / CPU (old one fried out) ... picked up an ASUS
P5Q with a Quad Core Intel CPU ... everything boots / runs fine, until I try
and start up X ...
If I use the 'n
Hello out there,
I run into trouble.
When looking for AutoFS in the net I find a lot about AutoFS on Linux
and, surprisingly, for FreeBSD 6.X, but those messages are dated to the
year 2004/2006.
I'm running FreeBSD 7.X and FreeBSD 8.0-CUR boxes and tried to find
something about AutoFS, but I
Citando "Philip M. Gollucci" <[EMAIL PROTECTED]>:
Brent Jones wrote:
Good morning -
After a 6.2 to 7-Current FreeBSD upgrade, do you need to rebuild your
ports?
If you have all the compat*x libraries installed you might not need to.
But if you don't, things will use the
Brent Jones wrote:
Good morning -
After a 6.2 to 7-Current FreeBSD upgrade, do you need to rebuild your
ports?
Yes (as with any major release upgrade). Old binaries will continue to
work, but if you ever plan to compile a new port you will have to
rebuild your existing ports first, because
On Tuesday 18 September 2007 22:24:47 Philip M. Gollucci wrote:
> Brent Jones wrote:
> > Good morning -
> >
> > After a 6.2 to 7-Current FreeBSD upgrade, do you need to rebuild your
> > ports?
>
> If you have all the compat*x libraries installed you might not ne
Brent Jones wrote:
> Good morning -
>
> After a 6.2 to 7-Current FreeBSD upgrade, do you need to rebuild your
> ports?
If you have all the compat*x libraries installed you might not need to.
But if you don't, things will use the old libraries and not the new ones
in 7.
I wou
Good morning -
After a 6.2 to 7-Current FreeBSD upgrade, do you need to rebuild your
ports?
Cheers,
Brent
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
yes. i got an answer on current. even though my host was not setup as a
NIS client, it was trying to resolve UID/GID information. the only line
in my rc.conf was NISDOMAIN=
--
Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.
On Tue, Jul 03, 2007 at 11:12:36AM -0500, Kevin Kramer wrote:
> thanks. I rebuild this morning with this and still no change. I can't
> even find any info on these flags...
Dunno if anyone ever gave you the real answer to your question, but if
not then here it is: your DNS is broken and taking ag
thanks. I rebuild this morning with this and still no change. I can't
even find any info on these flags...
Pieter de Goeje wrote:
On Friday 29 June 2007, Kevin Kramer wrote:
yes. that is where I have started, but I cannot get buildkernel to build
with those commented out. the UPDATING file
On Friday 29 June 2007, Kevin Kramer wrote:
> yes. that is where I have started, but I cannot get buildkernel to build
> with those commented out. the UPDATING file also lists heavy debugging
> turned on in userland, which I can't track down to any config files.
Add CFLAGS+= -DMALLOC_PRODUCTION to
he following on 06/29/07 11:13:
On Fri, 2007-06-29 at 09:34 -0500, Kevin Kramer wrote:
I know that debugging is turned on everywhere on 7-Current and I've read
UPDATING. But what I can't find is how to turn off debugging. I've tried
removing all debugging from the kernel, but it
On Fri, 2007-06-29 at 09:34 -0500, Kevin Kramer wrote:
> I know that debugging is turned on everywhere on 7-Current and I've read
> UPDATING. But what I can't find is how to turn off debugging. I've tried
> removing all debugging from the kernel, but it won't build.
I know that debugging is turned on everywhere on 7-Current and I've read
UPDATING. But what I can't find is how to turn off debugging. I've tried
removing all debugging from the kernel, but it won't build. I can't find
any userland debugging notes to turn it off.
..
Fatal error 'Exceeded maximum lock level' at line 201 in file
/usr/src/lib/libpthread/thread/thr_rtld.c (errno = 701428164)
Segmentation fault (core dumped)
kpax#
and the version built from port core dumped with no error messages.
The kernel
Hello,
I've installed beryl today (tried both: from packages and compiled from
updated ports) on a FreeBSD 7-CURRENT.
When I run beryl from console I get this:
# beryl
Something went wrong with Xgl detection.
Something went wrong with Nvidia detection.Something went wrong with system
On 5/8/06, Parv <[EMAIL PROTECTED]> wrote:
/^(((\d+)(?:\.\d+[^.\-]*?)?)-(\w+)(-\S+)?) (\w+)$/
Changing that regexp to pkgtools.rb made it work. thank you!
--
kpn @ IRCnet
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/
in message <[EMAIL PROTECTED]>,
wrote Perttu Laine thusly...
>
> Thank's. work fine. Now I have another question about 7-CURRENT.
> portupgrade and portversion are giving this error:
> ---
> uname(1) could be broken - cannot parse the output: 7-CURRENT-SNAP009 i386
>
..
Thank's. work fine. Now I have another question about 7-CURRENT. portupgrade
and portversion are giving this error:
---
uname(1) could be broken - cannot parse the output: 7-CURRENT-SNAP009 i386
** Error occured reading /usr/local/etc/pkgtools.conf:
uninitialized constant PkgC
On 2006-05-08 14:02, Perttu Laine <[EMAIL PROTECTED]> wrote:
> I have 7-CURRENT-SNAP009 on one testing computer and I'd like to update it
> to latest 7 sources. So can it be done via cvsup or how can update sources
> to latest? RELENG_7 seems to just delete everything with c
Hello Perttu,
Monday, May 8, 2006, 1:02:07 PM, you typed:
> I have 7-CURRENT-SNAP009 on one testing computer and I'd like to update it
> to latest 7 sources. So can it be done via cvsup or how can update sources
> to latest? RELENG_7 seems to just delete everything with cvsup...
I have 7-CURRENT-SNAP009 on one testing computer and I'd like to update it
to latest 7 sources. So can it be done via cvsup or how can update sources
to latest? RELENG_7 seems to just delete everything with cvsup...
--
kpn @ IRCnet
___
fr
Good Afternoon,
Firstly my apologies if this is the wrong list to post this to, but
since it was just a query - thought it was the best one.
I have recently built a test box which is currently running 7-CURRENT as
of April 16th. Everything is working, bar one thing, oidentd from ports
35 matches
Mail list logo