Mark Andrews wrote:
From unlink(2).
[ENOTDIR] A component of the path prefix is not a directory.
I suppose that is why rm is not working. The question was "Why don't
some man pages install?"
I think I have found the problem. Somewhere along the way a DOCSUPFILE
make va
I did get X.org running on 6-STABLE. As you have mentioned,
starting X via "X -probeonly" with an Asus SLI motherboard and an
NVidia 7800 GTX video card fails multiply; the internal configuration
tries and fails to load module "fbdev", meanwhile, the probe of the
card dials the contrast of
On Fri, Jan 27, 2006 at 08:57:26PM -0600, [EMAIL PROTECTED] wrote:
> Hello,
> In 6.0-STABLE when trying to build world i get a undefine refernce to
> calloc from libc.so right when it starts to build libexec/atrun but when i
> compile it stand alone it compiles fine same with libc but with the make
Hello,
In 6.0-STABLE when trying to build world i get a undefine refernce to
calloc from libc.so right when it starts to build libexec/atrun but when i
compile it stand alone it compiles fine same with libc but with the make
buildworld var this error shows up sames place every time.
Regards,
Chris
I think the newest D-link DWL-AG530 must use the AR5213 chipset too.
Before I got it I had done some checking and read somewhere that it used
the AR5212, so I thought I'd be ok.
When I tried it recently I got:
FreeBSD rock 6.0-STABLE FreeBSD 6.0-STABLE #1: Sun Jan 22 10:45:11 EST
2006 [EM
Kostik Belousov wrote:
Revision 1.48.8.1 of lib/libc/stdlib/Makefile.inc removed calloc.c from the list
of the source files. As result, freshly built libc does not contain
calloc symbol,
that completely broke my stable box. The only solution for me was booting
from 6.0-RELEASE disc1 and copying
On Saturday 28 January 2006 07:31, [EMAIL PROTECTED] wrote:
> A demonstration program is included below. I've verified this on a
> fairly recently 5.4 client system, with both Linux and FBSD 5.4 NFS
> servers. I don't have 6 or -current available to me at the moment.
> There's the obvious work-ar
Revision 1.48.8.1 of lib/libc/stdlib/Makefile.inc removed calloc.c from the list
of the source files. As result, freshly built libc does not contain
calloc symbol,
that completely broke my stable box. The only solution for me was booting
from 6.0-RELEASE disc1 and copying libc.so.6 into /lib. After
I've found an interesting little quirk that doesn't seem like it
should be working this way. If I:
fd = open(file)
write(fd, data)
fchmod(fd, 04711) /* or anything set{u,g}id */
close(fd)
The set{u,g}id bits get cleared by the close, but only if the amount
of dat
Er, more on that network card I said that screwed up the firewall, it's lnc.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> What do
>
> # sysctl machdep.hlt_cpus
> # sysctl machdep.logical_cpus_mask
> # sysctl machdep.hyperthreading_allowed
machdep.hlt_cpus: 10
machdep.logical_cpus_mask: 10
machdep.hyperthreading_allowed: 0
-pete.
___
freebsd-stable
On Jan 26, 2006, at 3:50 AM, Niki Denev wrote:
i have this added to my kernel conf :
options BREAK_TO_DEBUGGER
options KDB
options DDB
I recommend ALT_BREAK_TO_DEBUGGER instead of BREAK_TO_DEBUGGER
especially if you use cyclades terminal servers. They send BREAK on
power-up so if you
Pete French wrote:
>> If you look at top(1), which processors do you see actually running
>> processes?
>
> Errr, 0, 1, 2 and 3!
What do
# sysctl machdep.hlt_cpus
# sysctl machdep.logical_cpus_mask
# sysctl machdep.hyperthreading_allowed
say?
Colin Percival
Hi guys
Here is where I am at now.
Before we start, heres a DETAILED link to my exact wireless card:
http://www.netgate.com/product_info.php?products_id=279
A nice guy named Eric from Germany e-mailed me with some information,
saying to check out this website:
http://lists.freebsd.org/pipermail
> You misunderstand the point of this sysctl. All
> machdep.hlt_logical_cpus does is prevent anything from scheduling
> anything on the extra logical CPUs.
Sadly I am seeing all 4 processors running httpd in top (see other email)
-pete.
___
freebsd-sta
> If you look at top(1), which processors do you see actually running
> processes?
Errr, 0, 1, 2 and 3!
That was my first clue that it hadn't worked as advertised!
last pid: 2529; load averages: 0.53, 0.49, 0.34up 0+00:19:50 19:35:04
62
Pete French wrote:
> I have:
>
> websvr04# sysctl machdep.hlt_logical_cpus
> machdep.hlt_logical_cpus: 1
>
> but I am still seeing 4 CPU's as I have two physical processors, each with
> two logical ones onboard.
The way machdep.hlt_logical_cpus works is by telling the scheduler to
ignore the ext
On Fri, Jan 27, 2006 at 07:24:06PM +, Pete French wrote:
> > Disable it in the BIOS. The kernel can't use what isn't advertised as
> > available. :)
>
> true - but surely this is a bug in FreeBSD ?
>
> man smp says:
>
> "Since using logical CPUs can cause performance penalties under certa
> Disable it in the BIOS. The kernel can't use what isn't advertised as
> available. :)
true - but surely this is a bug in FreeBSD ?
man smp says:
"Since using logical CPUs can cause performance penalties under certain
loads, the logical CPUs can be disabled by setting the
machdep.hlt_logical
Yeah, someone told me about this exact card, I guess he figured it used
Atheros so that meant it would work.. I wish I was so lucky.
A nice fellow from Germany sent me an e-mail with a link to patching a file
in the kernel, but I'm not sure how to do it.. But I guess I'll give it a
try
Does anyon
On Friday 27 January 2006 02:16 am, Pete French wrote:
> I though that machdep.hyperthreading_allowed had to be set to 1 to
> turn on hyperthreading ? I have a dual processor HP blade, and
> when I boot it up with an SMP kernel I get 4 CPU's. Setting that flag
> does not have any effect!
Disable i
On Thursday 26 January 2006 08:10 pm, resonant evil wrote:
> Hi there.. So I can't use this wireless card at all right now? Damn
> why did I buy this thing then.. People from the mailing list showed me
> this one so I ordered it :-(
All the posts on BSDForums.org list that the ath(4) driver in F
Some change between Sun Nov 13 14:58:40 EET 2005 and Wed Jan 25 17:21:02
EET 2006 causes this message on boot:
Jan 27 14:59:46 xx kernel: ad0: req=0xc306baf0 SETFEATURES SET TRANSFER
MODE semaphore timeout !! DANGER Will Robinson !!
Jan 27 14:59:47 xx kernel: ad0: TIMEOUT - READ_DMA retrying (1
It was some PCI 100MB card with an AMD chipset on it. Also, my
connection is much faster now, so I suspect that the network card was
going in the first place.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
On Fri, Jan 27, 2006 at 07:01:53PM +0200, husnu demir wrote:
h> I tried
"http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/bge/if_bge.c?rev=1.91.2.7&content-type=text/plain";
version and replaced VLAN_INPUT_TAG with VLAN_INPUT_TAG_NEW (only one
occurance). And the following errors com
On Fri, Jan 27, 2006 at 07:30:55PM +0300, Gleb Smirnoff wrote:
> On Fri, Jan 27, 2006 at 05:58:18PM +0200, husnu demir wrote:
> h> By the way the problem exists on bge2 (with Multimode F/O connector.)
>
> Oh, this is an important information.
>
> Can you please upgrade to STABLE and then test sev
On Fri, Jan 27, 2006 at 05:58:18PM +0200, husnu demir wrote:
h> By the way the problem exists on bge2 (with Multimode F/O connector.)
Oh, this is an important information.
Can you please upgrade to STABLE and then test several versions of if_bge.c?
The breakage is somewhere between rev. 1.101 an
> Also it is important to know whether doing 'ifconfig bge0 -rxcsum -txcsum'
> fixes operation on 6.0-STABLE.
No, It does not fixed. I will go back to STABLE if you need further detail.
Husnu Demir.
(Note: I may leave the office. will try to contact you las soon as possible.)
For RELEASE vers
On Fri, Jan 27, 2006 at 06:30:36AM -0800, Will Froning wrote:
> Kelly,
>
> On Sun, 22 Jan 2006, Kelly D. Grills wrote:
> =>On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote:
> =>>
> =>> I reported this problem a few OS versions back... pre-6. I'm on
> =>> FreeBSD-6-STABLE, and I'v
By the way the problem exists on bge2 (with Multimode F/O connector.)
Husnu Demir.
On Fri, Jan 27, 2006 at 06:35:12PM +0300, Gleb Smirnoff wrote:
> On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote:
> h> I upgraded my pc after "2006-01-25 FreeBSD-SA-06:06.kmem" issue. After
> that it
Nothing changed.
and the other infos;
Thanks for the quick response.
[EMAIL PROTECTED] ifconfig
bge0: flags=8843 mtu 1500
options=1b
inet6 fe80::211:9ff:fe9b:6a7d%bge0 prefixlen 64 scopeid 0x1
inet x.x.3.138 netmask 0xff80 broa
On Fri, Jan 27, 2006 at 06:11:51PM +0200, husnu demir wrote:
h> I upgraded to the 6_RELEASE;
h>
h> $ uname -a
h> FreeBSD nrouter.cc.metu.edu.tr 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Fri Jan
27 18:03:39 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NON-GENERIC
i386
h>
h> and now it is worki
Hi Again,
I upgraded to the 6_RELEASE;
$ uname -a
FreeBSD nrouter.cc.metu.edu.tr 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Fri Jan 27
18:03:39 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NON-GENERIC i386
and now it is working. But the CRC errors still exists. I only see the CRC
errors on en
On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote:
h> I upgraded my pc after "2006-01-25 FreeBSD-SA-06:06.kmem" issue. After that
it also upgrade the bge drivers and now it is not working. In fact my "Broadcom
BCM5703 Gigabit Ethernet, ASIC rev. 0x1002" is not working. The other bge's
On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote:
h> Hi,
h>
h> I upgraded my pc after "2006-01-25 FreeBSD-SA-06:06.kmem" issue. After that
it also upgrade the bge drivers and now it is not working. In fact my "Broadcom
BCM5703 Gigabit Ethernet, ASIC rev. 0x1002" is not working. The ot
Kelly,
On Sun, 22 Jan 2006, Kelly D. Grills wrote:
=>On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote:
=>>
=>> I reported this problem a few OS versions back... pre-6. I'm on
=>> FreeBSD-6-STABLE, and I've found the dhclient once again "wedged" in a
=>> mode that was eating a lo
Hi,
I upgraded my pc after "2006-01-25 FreeBSD-SA-06:06.kmem" issue. After that it
also upgrade the bge drivers and now it is not working. In fact my "Broadcom
BCM5703 Gigabit Ethernet, ASIC rev. 0x1002" is not working. The other bge's
working properly. Most probly last update may cause that. I
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote:
On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote:
> Kris Kennaway wrote:
> >On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote:
> >
> >>On Thursday 26 January 2006 10:40
I though that machdep.hyperthreading_allowed had to be set to 1 to
turn on hyperthreading ? I have a dual processor HP blade, and
when I boot it up with an SMP kernel I get 4 CPU's. Setting that flag
does not have any effect!
Any thoughts ? I dont think I have two CPU's each with dual
core and wi
On Thu, 2006-Jan-26 20:10:56 -0800, resonant evil wrote:
>Hi there.. So I can't use this wireless card at all right now? Damn why
>did I buy this thing then.. People from the mailing list showed me this one
>so I ordered it :-(
That exact card, or that model number? One major problem with PC
ha
On Wednesday 18 January 2006 00:36, Pyun YongHyeon wrote:
> > >
> > >atm I have no clue. How about updated sk(4)?
> > >http://people.freebsd.org/~yongari/sk/if_sk.c
> > >http://people.freebsd.org/~yongari/sk/if_skreg.h
> >
Hi again
I am running your both versions (UP and SMP) now for almost
Steve Hodgson wrote:
Mike Jakubik wrote:
Jan 26 17:01:47 desktop kernel: smb_maperror: Unmapped error 1:158
Jan 26 17:02:18 desktop last message repeated 52 times
Jan 26 17:04:19 desktop last message repeated 646 times
Jan 26 17:14:20 desktop last message repeated 6342 times
I get this messag
TB --- 2006-01-27 08:19:11 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2006-01-27 08:19:11 - starting RELENG_6 tinderbox run for sparc64/sparc64
TB --- 2006-01-27 08:19:11 - cleaning the object tree
TB --- 2006-01-27 08:19:48 - checking out the source tree
TB --- 2006-01-27 08:19:48
Russell Doucette wrote:
Mike Jakubik wrote:
It's either a hardware problem, or some serious issue with ipf. As a
side note, i would highly recommend you ditch ipf and switch to pf
instead, its a much better firewall.
Yeah, I fixed it. I switched network cards and the BSD box works fine
no
Atanas wrote:
Kris Kennaway said the following on 1/26/2006 3:46 PM:
On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote:
On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote:
Kris Kennaway wrote:
On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote:
On Thursday 26
TB --- 2006-01-27 07:02:52 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2006-01-27 07:02:52 - starting RELENG_6 tinderbox run for i386/pc98
TB --- 2006-01-27 07:02:52 - cleaning the object tree
TB --- 2006-01-27 07:03:36 - checking out the source tree
TB --- 2006-01-27 07:03:36 - cd
Kris Kennaway said the following on 1/26/2006 3:46 PM:
On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote:
On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote:
Kris Kennaway wrote:
On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote:
On Thursday 26 January 2006 1
47 matches
Mail list logo
