Dominic Marks wrote:
Hello,
Is the php5-pcre module really incompatible with FreeBSD 6.1? If so,
is there a workaround or a version I can roll back to? Also, it is
just me (:-)) or is the php5 port complaining about a checksum
mismatch for everyone else?
I had some problems yesterday. Had to
misael wrote:
# Debugging for use in -current
#optionsDDB #Enable the kernel debugger
#optionsINVARIANTS #Enable calls of extra sanity checking
options INVARIANT_SUPPORT #Extra sanity checks of internal
structures, required by
Drew Tomlinson wrote:
So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to
suspect it's being loaded twice. I have it in /boot/loader.conf which
is where I thought it should be. Is there anywhere else to check?
If you have GEOM_STRIPE in kernel do you have to load it
Steve wrote:
If anyone has that link handy, please post. (for the patch)
http://people.freebsd.org/~sos/ATA/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
What could cause dhclient sometimes to fail renew the lease? I updated
world and moved to pf from ipfw same time so i don't know which to blame.
This happens from twice a day to every few days.
Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available
Jul 21 03:44:55 myserver
Pertti Kosunen wrote:
What could cause dhclient sometimes to fail renew the lease? I updated
world and moved to pf from ipfw same time so i don't know which to blame.
This happens from twice a day to every few days.
Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available
Chuck Swiger wrote:
Typically, that sort of message indicates that the firewall rules are
preventing traffic from going out, or packets are getting stuck in a
queue until it fills up, or maybe even a bug somewhere in the
particular combination of kernel firewall options enabled, high
Chuck Swiger wrote:
Does the problem go away if you use a trivial permit all PF ruleset?
When i took off scrub altq No buffer space available messages were
gone, but dhclient did still renew the same address.
Does the problem go away if you use a trivial IPFW permit all
instead of PF?
Mark Kane wrote:
I do have a tall Antec case, and have both 200's and the 160 in 5 1/4
inch trays so the cables for those are long (36 inches IIRC). Would it
be OK to have that setup, or would it be better to isolate them all on
their own cables/channels and get a Promise card or something
Sandro Noel wrote:
thank you all for the ULTRA fast reply,
i had an entry in the resolv.conf that did not belong there.
problem solved.
something is bothering me...
the entry stated that it was the ip of my gateway 10.0.5.1
wich is the same address that the DHCP server gives out.
why is it
Mike Tancsa wrote:
Hi,
The driver in RELENG_4 is essentially the same as in HEAD
and RELENG_6. Someone backported the changes from the RELENG_6
version to 5.x and posted a link in the mailling list perhaps a month
or so ago. Have a look through the archives for the patches.
Mike Tancsa wrote:
At 04:53 AM 21/09/2005, Pertti Kosunen wrote:
Do i need to do something special with gstripe when upgrading to
RELENG_6 from RELENG_5?
Sorry, dont know, but a search through the archives might have the
answer. I suspect it wont be an issue
Everything went fine even
Par Leijonhufvud wrote:
Nope, that does not do it, what it did was remove the old (6.3.6)
version and fail to install the new version. I also tried going to
/usr/ports/mail/fetchmail and doing a make install. Pretty much same
error (fetchmail -- TLS enforcement problem/MITM attack/password
JoaoBR wrote:
I don't agree to what you say
what sense does it make to have my forward rules up but natd still not?
what sense does it makes logging while syslog is not up?
What would it forward log when network isn't up?
___
Artem Kuchin wrote:
Well, i don't trust software raids. But 3ware is probably one of the most
expensive raid 0,1 controllers. There must be something around 40$ which
freebsd supports. Does anyone known any model?
Those cheap hardware raid 0,1 controllers are all really software
raids. Driver
Emanuel Strobl wrote:
Unfortunately there is no mini-inst anymore since install and fixit CD is
combined now. You have to download the whole 780MB.
Why 780MB? It doesn't fit on normal 700MB CD.
___
freebsd-stable@freebsd.org mailing list
James Seward wrote:
I am also attempting to upgrade my system to a newer cvs but
unfortunately I can't buildkernel on it - it'll either panic or
generate enough timeouts to make make fail. If anyone could point me
at a HOWTO or similar on cross-compiling then I'll compile it on my
other machine
Imobach Gonzlez Sosa wrote:
Ok, I think I have it correctly with this command:
ifconfig rl0 media 100baseTX -mediaopt full-duplex
(rl0 or dc0, I've used two different NICs).
Moreover, I connected my FreeBSD box to the ADSL router (directly, no
more machines connected) and forced the adapter
Matthias Buelow wrote:
The newer cards work very well. I have a X800se PCI-Express card and
it works like a charm with X.org 6.8.1 on 5.3. The only thing that's
missing in the newer Radeons under Xorg/XFree is 3d acceleration
(which the OP might or might not need on FreeBSD, since it's mostly
Android Andrew wrote:
Hello!
I have a problem with Intel(R) PRO/1000 card (Intel 82540) - it does
not initialize properly during boot process.
I've got these error messages in /var/log/messages:
...
Dec 16 19:27:36 zahrouer kernel: pci2: PCI bus on pcib2
Dec 16 19:27:36 zahrouer kernel: em0:
Arno J. Klaassen wrote:
dunno, I'd more suspect ACPI-APIC issues : untill now
I only had problems on nForce based systems, but today I
installed a brand new VIA based A7VT mini-server and
re-voila les XXX_DMA errors (and accompanying severe
system slow-down).
(Disk swapped from the old PII-233
C. Fischer wrote:
this has started bugging me ever since moving from 4-stable to 5-stable.
ad2, which had been recognized no problem on the former, fails on the
latter. since i have a multibooter, i can boot 4.10 residing on ad2 without
trouble. 4.10 can access ad0 and ad1 fine (this is how i
Karl M. Joch wrote:
Hello,
on a box with 3 re interfaces i get a lot of watchdog timeouts and
stopping/clow connections. only found 1 or 2 postings with the same problem,
but not much replys. the box worked great with 4.x.
any suggestions would be very appreziated.
I changed re nic to Intel gigE
Charles Ulrich wrote:
I too had problems with a SoundBlaster Live card on a workstation running
5.2.1. Sometimes the sound was nice and clean, but most of the time it was
just horrible. Nothing I did had any noticable effect and the mailing lists
unusually quiet on the issue, so I gave up. The
Søren Schmidt wrote:
ATA-mkIII first official snapshot.
This is the much rumoured ATA update that I've been working on for
some time.
Is this coming in 5.4-RELEASE?
___
freebsd-stable@freebsd.org mailing list
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
Pertti Kosunen wrote:
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
Kip Macy wrote:
I will be MFC'ing the newer ZFS support some time this afternoon. Both
world and kernel will need to be re-built. Existing pools will
continue to work without upgrade.
Mounting local file systems:.
internal error: out of memory
internal error: out of memory
internal error: out
Goran Lowkrantz wrote:
Ran into the same thing on -CURRENT when we went version 13. Some manual
intervention fixed it.
http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000508.html
mount -t zfs ...
cd /usr/src
make NO_FSCHG= installworld
This did the job with new kernel.
Kirk Strauser wrote:
So far so good here (amd64, Core2 Duo, ICH9 SATA) but I'm too chicken to
upgrade the on-disk format yet.
Me too, upgraded pool to v13 yesterday and everything still ok. Removed
also all loader.conf tunables. Many thanks for FreeBSD team.
(Tyan Tank GT20, 2GB memory,
Mikael Bak wrote:
Links to documentation, hints and advises are greatly appreciated.
http://phaq.phunsites.net/2007/02/14/convert-freebsd-iso-image-for-pxe-bootstrap/
___
freebsd-stable@freebsd.org mailing list
Ulrich Spörlein wrote:
2GB CF card + CF to ATA adapter (today, I would use 2x8GB USB sticks,
CF2ATA adapters suck, but then again, which Mobo has internal USB ports?)
Many has internal USB header.
http://www.logicsupply.com/products/afap_082usb
___
Larry Rosenman wrote:
On Tue, 15 Apr 2008, Jeremy Chadwick wrote:
And what the FAQ doesn't cover is here:
http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues
* EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+
motherboards (and possibly others)
* Symptom: kernel
Jeremy Chadwick wrote:
7.0-RELEASE (AMD64) didn't have this problem.
Are you absolutely positive about this (re: amd64 not having the
problem)? I can reproduce the issue documented in my Wiki page on i386
or amd64. The piece that seems to cause it, at least in the case of the
PDSMI+, is EIST
Pertti Kosunen wrote:
But i did have cpufreq compiled in kernel.. It seems to be working now
when loaded as module from loader.conf.
No it didn't help, calcru messages just came later.
___
freebsd-stable@freebsd.org mailing list
http
35 matches
Mail list logo