> How is data transmission related to power management?
They are pretty intimately related over a wireless link. If
the power management at one end decided it can use less transmit
power and gets it wrong then your data stops getting through.
___
freebsd
As I seem to recallt sme discussion of Adaptec RAID in the not so
disatnt past, could anyone let me know if these cards work well
under FreeBSD 6 or not ? I've just inherited a server which
needs RAIDing and it has a slot for one of these on the board. I
only have expereience of Compaq SMART RAID m
> I obtained a Compaq(COMPAQ PROLIANT 5500) machine by chance.
> By the way, is possible install FreeBSD this machine?
I used to run FreeBSD 4 on this machine very successfully. The
only thing you need to know is that if you want SMP to work
then you need to go into the Compawq BIOS and tell it t
> I disagree, I would like to have an notice about it. Even though it might
> not say much. Just a "The code of the stable branch has been freezed due
> to the upcomming release of X.Y"
It is kind of useful, because it's the code freeze point at which I start
re-scheduling my work day so I can do
> I have a problem with dovecot eating sometimes up to 90% CPU.
Are you using kqueue support ? I also had this problem and the solution
for me was to recompile it without kqueue support. Now it runs fine.
-pete.
___
freebsd-stable@freebsd.org mailing li
> Yes, I'm using kqueue support.
Try taking it out and the problem should go away.
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> this is indeed a nice workaround (at least if it helps :-)), but
> somebody(tm) should have a look why the kqueue support is broken
> there in the first place.
I think it's a problem in Dovecot, not FreeBSD - there are a number of
messages regarding this on the Dovecot lists, including a nunmber
> On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <[EMAIL PROTECTED]> wrote:
>
>2. Building a kernel with config is not officially supported. It's at
> your risk and may not work in all cases. Build a kernel with:
> cd /usr/src
> make buildkernel
I was not aware that you wern't supposed
> Hello, I would like to convert RSSI to dBm (in fact I would love if
> ifconfig cound display SNR in dBM), so I would like to know if this
> formula is any right:
Take a look here:
http://www.wildpackets.com/elements/whitepapers/Converting_Signal_Strength.pdf
Especially at the top of page 5. RS
> Is this paper's information accurate regarding atheros?
I have no idea - I think you would be best off calibrating it yourself
with a dBm metre if you can. The antenna will have an effect as well, as
will cabling between it and the receiver chip - all the usual things to
do with working with rad
> On many of our servers, we have bge cards and I can see a lot of
> watchdog timeouts. We always disable USB in the bios and they didn't
> share irq.
I see the same thing - we have a number of HP blades which use bge interfaces
and I get many watchdog timeouts on them. These are also not sharin
>Attached is a simple user program that will immediately cause pretty much
> all of the network drivers (at least the ones I own) to stop working and
> get watchdog timeouts.
I am runnign this on a single processor machine with an SMP kernel and
it does not have any effect. I dont tink I have
>Do you have any history of seeing the watchdog timeout problem on your
> machine?
On this machine no - but it's the only one running em0. On other
machines running bge0 then, yes, I see it a lot. But those are all
SMP machines, aside from one. On that one I am currently building
the latest 6-
>Do you have any history of seeing the watchdog timeout problem on your
> machine?
O.K., I just finished compiing up a uniprocessor kenel for the machine
on which I had been seeing bge0 timeouts, and the lopppoll.c code
has no effect there. The kerenl I am running is the latest STABLE from
a c
> Are you enabling an option, like IPv6, that puts Giant over the network
> stack?
Am not enabling anything, but if INET6 is part of GENERIC (which I think it is
isn't it?) then I would have that in my kernels as they basically look
like this:
include GENERIC
options SMP
> The FTDI devices keep the device descriptors etc. in an EEPROM, so my
> approach to the 'which port is which' problem was to change the textual
> part of the descriptor - "usbdevs -d" then immediately tells you what is
> going on. The EEPROM is writable over the USB connection - I have a
> progr
> This is a known problem. It is fixed in HEAD, but unfortunately it
> isn't mergeable to RELENG_6. The problem isn't related to either pf,
> ipf or NIC drivers.
This is a little alarming - because what you seem to be saying is that
if you have DL360's then you need to either run current, or accep
> Doesn't the increased number of registers available when running amd64
> really, really help when compared with the traditionally register-starved
> i386?
Yes, it seems to - evereything soemone else said about context switch
verhead and compiles is true of course, but the FreeBSD compiler seems
> This doesn't tally with my experiences. I've had an amd64 laptop
Me neither - but then I think this is a large case of 'your mileage
may vary', as it entirely depends on what you are doing. I did
find, like the original poster, that a number of language ports didn't
work properly when I first t
> Is it causing stuck connections or other messy problems? Also, is it
> any worse than 6.1?
I am also seeing the same thing - hard to tell if it is better or worse
under 6.2 than 6.1 as I dont have 6.2 out on any production webservers
so the only machine running it is a lot more lightly loaded (
I recently overhauled my RAID array - I now have 4 drives arranged
as RAID 0+1, all being 15K 147gig Fujitsu's, and split across two
buses, which are actively terminated to give U160 speeds (and I have
verified this). The card is a 5304 (128M cache) in a PCI-X slot.
This replaces a set of 6 7200 r
> - Is the controller cache enabled?
Yes - split 50% read, 50% write.
> - Do you have the battery for it and is write cache enabled? (You won't
> make full use of the cache without the battery)
yes - battery is attached and fully charged
> - How does your performance compare when using dd on t
> You might be able to speed up the read by playing with the vfs.read_max
> sysctl (try 16 or 32).
Wow! That makes a huge difference, thanks. Should this not be in 'man tuning' ?
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.o
> > Raw dd gives 50 meg/second
> On /dev/da1, with a reasonable block size (1m)?
Block size is 2meg. I was using da1s1 and da1s2 which were giving
me 50 and 47 meg/second resepctively - if I switch to da1 on it's
own I get 59 meg/second.
reading from the filesystem with the vfs.read_max set to 64
> It would be interesting for you to track iostat (i.e. run "iostat 1")
> with and without modified vfs.read_max and see if there's a difference.
On the file: KB/t is about 127.5 with both sizes. Rate is 39 on with
the read_max set to 8, but 115 with read_max set to 64.
On the raw device: KB/t i
> There's something unusual going on and I don't know what else to try.
> Finally, after fiddling with various options, I've sort-of got it to
> work by creating two slices (s1, s2), setting root partition on s1a and
> the rest (/usr, /var, etc.) on s2. Now, the "F1 prompt" boot stage
> behaves
In the configuration for 6to4 in /etc/rc.conf I have to fill in
a value for 'stf_interface_ipv4addr'. Which is all well and good, except
that I get my IPv4 address via DHCP. Is there a way whereby I can tell
6to4 to take the IPv4 address from a particular interface ?
-pete.
___
> I'd really like to see support for the AMD64 architecture become rock solid,
> too, because 64 bit Athlons are starting to sell at great prices.
Sadly I went back to running i386 on my AMD64's - not because of problems
with FreeBSD, but because of problems with ports. It seems that theres a lot
> It's the C language. While it's claimed to be "portable," it really doesn't
> address integer size and endianism well enough.
All the more reason to be careful you might have thought :-) Mind you,
trying to explain to students why 'long x = 65535;' set x equal to -1
always made me feel like I wa
> Buggy compilers are indefensible, yes, but why try to apologise for it?
I dont see it as a bug. Without an 'L' the right hand side of that
expression is a 16 bit int. For which 65536 is out of range. If I
wrote 'int y = 65535; long x = y;' then I would get the same result for
the same reason.
T
> The type of a decimal integer constant without any suffix is the first
> of 'int', 'long', 'long long' in which the constant can be represented.
It is ? Well, you learn something new every day I guess! I stand
corrected in that case. Appologies.
> (For C89 it was the first of 'int', 'long', 'un
Just giving 4.11 a whirl. Thought I would try and get dri working
with my mga card. It's never worked in the past, so I am not too
worried that it doesnt work now.
But it's getting closer to woorking, so I thought I would ask
to see if anyone had any good ideas. I have agp and mgadrm compiled
into
> What hardware are you on? The radeon driver had 64-bit issues on
> amd64. Maybe Matrox has a similar problem?
It's just straight i386 (aP4) - though I am interested in what you
say above, as I also have an amd64 machine running 5-STABLE with
a Radeon which also will not do drm for love nor money
> You know, I don't really care what NIC I use - I really don't. I'm not
> so much interested in trying to figure out why this NIC is giving me
> grief as much as I am in finding one that will work. I would just like
> someone somewhere to tell me what is a stable NIC to use for FreeBSD,
As seve
I understand that recent changes mean that when I cvsup the
ports I also need to do a 'make fetchindex' to get the index
file right ?
But that will give me the most recent index file will it not ?
So if I am supping the ports with a tag of tag=RELEASE_4_11_0
to get the 4.11 ports, how do I fetch
> > So if I am supping the ports with a tag of tag=RELEASE_4_11_0
> > to get the 4.11 ports, how do I fetch the index file that goes
> > with them ?
>
> You can find it here [1].
> [1]
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/INDEX
Stupid me! Should have t
I have a machine with three interfaces on it, two onto
internal networks, one ointo the outside world. I only want
NFS to be accessible on the two internal interfaces so I have this line
in my /etc/rc.conf:
nfs_server_flags="-u -t -n 4 -h 192.168.3.1 -h 192.168.4.1"
That works - but it ony enable
> Try the patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/25826
> That worked for me. I've also attached the patch to this email.
Thats. I didnt realise it was a known problem - and an *old* known
problem at that it seems! In the end I simply decided to direct
all the requests to the othe
> Ruben's message to provide a data point. Am I the only one for whom
> Firefox and www/flashplugin-firefox doesn't work?
No, it doesnt work for me either - but I dont care enough about
websites with mflash to bother looking into it.
-pcf.
___
freebsd
The man page for getrusage says that the frequency of the statistics
clock is given by sysconf(_SC_CLK_TCK).
The source code to /usr/bin/time uses a function 'getstathz' to get
the frequency of the statistics clock which is does using sysctl
and KERN_CLOCKRATE
On my system the first returns 100Hz
> 'sysctl kern.clockrate' will return this information if you don't want to
> write a program to do it for you :)
I was just using the code from time(1). Inteesring though - heres the
output:
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 100, stathz =
100 }
So that thinks stat
> Why does sysconf(_SC_CLK_TCK) always returns 128? Check out sysconf()
> in src/lib/libc/gen/sysconf.c (lines 83-84 of rev. 1.10):
[follow through of code showing it is defined as a constant snipped]
> To determine how stathz can vary, we'll have to dig deeper. Check out
> initclocks() in sr
> getrusage(2) says that ru_ixrss is based on "statistics clock ticks"
> with a frequency of sysconf(_SC_CLK_TCK). This cannot be right.
H... it was trying to interpret the results from getrusage which lead
me to finding the bug. I notice that /usr/bin/time does a sysctl to get
the clock rate
> I am a little bit confused.
> amd64 with a dual xeon?
Preseumably one of the newer 64 bit Xeons. I would home amd64
supports them doesnt it ?
-pcf.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
> dear all,
> I would like to buy SCSI card which must:
> - support Ultra 320
> - support RAID 0,1,5, and 1/0
> any recommendation for FreeBSD-5.x ?
The Compaq SMART series have always worked well for me. Have
a 3200 here on FreeBSD 5, and have tried almost all of them
on FreeBSD 4 (from the old
> I'm running a 6.2-RC1 box (cvsup'd today) that has two broadcom nics. One
> is an internal network (nfs) and the other is external.
...
> Doing something like "ls /usr/ports" will just hang until interrupted.
> Using tcp for nfs makes it workable, but very slow.
Oddly enough I hit precisely t
> As Luke already pointed out, "no-df" on the scrub rule should help. As=20
> for the "bad cksum!" - this is a symptom of checksumming done in=20
> hardware. ifconfig bge1 -rxcsum -txcsum should get rid of them.
I am a bit concerned by this - we use a lot of bge interfaces, and I have
hardware c
> You are misunderstanding. The problem is simply that the bpf device sees=20
> bad checksums as it sees the packet before the hardware has calculated=20
> it. On the receiver the checksum will be correct.
Ah, gotcha. That makes perfect sense now.
-pete.
> I pulled the "scrub in all" line and replaced it with a "scrub in on
> bge0". I don't really care about scrubbing on the internal network. All
> works as expected now.
I dont really care about scrubbing my intrenal nbetwork either - but I do care
about NAT working on the outside, which requi
> Because everybody knows that odd numbered releases aren't stable.
I've been 20 years in electronics & comouting and thats the first
time I have ever heard anyone say that! Steer clear of '.0' releases
is well known, but suspecting something just because of the odd or
evenness of it's numbering s
> If you had any idea how many RFC's IE violates and and how many bugs there
> are in it you would never have made a statement like that.
I don't think here ever said that IE was *better*, just that it was
necessary for certain sites (which is undeniably true) and that if
all you have available i
I have a network with a 6.2-RELEASE machine as a gateway to
the outside world, and on the inside three machines hung off it,
running OSX, XPx64 and 6.2-RELEASE as well. The gateway machine
NATs the internal network under Ipv4 and runs IPv6 via 6to4. It
has routing advertised on the internal network
> 2) rtsol(8) is used to initiate stateless autoconfiguration. You might=20
> want to try "rtsol -d interface".
Aha... this does not work...
> 3) Check the net.inet6.ip6.accept_rtadv sysctl. ipv6_enable should take=20
> care of this.
...because this is 0
All of which appears to be because a s
I have a machine with two interfaces in it - bge0 and beg1. I now
find I need to usse ng_fec to make these into one interface due to
the way out networking contractors are installign a new site.
Seems like no problem from the command line, but what I can't
find anywhere in the documentation is how
> http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/104884
Now that's an excellent patch - but not yet applied to STABLE I guess,
and I don't want to have to re-patch every time I do an
install unfortunately. Though if it gets commited in the near future
I would definitely do it this way.
tha
> Except that the original mail was talking about greylisting. This won't
> reject any mail sent from a MTA that correctly implements SMTP. According
> to the SMTP specs, I am perfectly at liberty to tell you that I can't
> accept your mail right now, please try again later. =20
But isn't the po
Am trying to solve a little problem with 'pf'. I have a ruleset which
has some firewall rules for the IPv6 interface stf0. This works fine,
except when I rreboot the machine, as the pf script is run before the
network_ipv6 script - so stf0 does not exist. but I cannot work out
how to arrange for st
> 1) You use the interface name as address w/o dynamic lookup.
> i.e. "... from stf0 ..."
Yes, thats it - I hadn't come across this 'dynamic lookup' thing before
though, so I didn't realise what it was. I still cant find it in the PF
manual, aside from a reference that you need to do it for NAT.
> The "(ifnX)" syntax is only for places where you use the interface as an
> address. The "on ifnX" part stays unchanged in any case and it does not
> matter if the interface exists already or not.
h, so whats going on with mine then ?
*goes and has a closer look*
gah! there was a 'loginter
> Just for my edification, what is the point of "keep state" on an
> "any-to-any" rule?
It's a 'pass out' rule - without the 'keep state' the returning packets
wont get back in.
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
> Configtest says it's fine. apachectl start says it starts. But it
> actually doesn't. Nothing in /var/log/messages, nothing in
> /var/log/httpd-error.log - and nothing in
> /usr/local/etc/apache/logs/error_log.
I had the same problem at the weekend. I upgrade by
uninstalling all packages,
> For a set of IPs in the same subnet on the same interface, wouldn't the
> primary IP be the one with the proper netmask, and all IPs with netmasks
> of /32 be secondary? In that situation, wouldn't deleting the primary IP
> cause connection issues for the rest of the IPs?
Indeed. I too am no
> I'd like an AMD 64 (or dual core) box (lower cost) with SATA/EIDE
> disk support. I plan on running FreeBSD mostly and occasionally Red
I run a Shuttle SK21G which I am very happy with - takes the old S754
processors which are cheap these days, but a 3700+ is pelnty fast enough
for development w
> Maybe HP is your way to go if you want to use FReeBSD on blades :)
I run FreeBSD on a lot of HP blades and can confirm that it works very
nicely and is rock solid stable. have been doing this since 5.X and
am now running 6.2
-pcf.
___
freebsd-stable@f
> Assume you refer to the older hp-blades and *not* the newer c-class
> ones. The c-class-blades do *not* currently support the build-in NIC
> due to a SerDes-issue.
Ah, thats worth knowing! yes, our blades are a couple of years old
so would be b-class ones.
___
> which type of hp blade work with 6.2?
Ours are BL20p G3 and BL20p G2 blades according to the iLo.
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROT
> How did you install FreeBSD on them? Using RDP?
RDP ? I installed using iLo - just connect the ISO image of
the CD as virtual media and you can then boot and install as
if it was a normal PC with a drive in the front of it.
-pete.
___
freebsd-stable@
> last days with exim connecting to the local socket I have exim
> now connecting to localhot:3310 by tcp. The difference is, that before
> clamd scanned all files in the directory given by exim. Effectively exim
> was unpacking the whole MIME structure and placed all parts in the dir
Interest
> What configuration in exim is needed to make it use tcp instead of sockets?
av_scanner = clamd:127.0.0.1 3310
instead of
av_scanner = clamd:/var/run/clamav/clamd
and then in clamd.conf, comment out 'LocalSocket' and uncomment the
'TCPSocket' and 'TCPAddr' settings so it looks
> I have a server with FreeBSD 6.1 and i try to install tomcat. But the tomcat
> daemon can't run. And the error is
What version of Java did you install ?
-ete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't think it should
ever be th
> I think you will want RELENG_6_2_0_RELEASE.
thanks (and to the others who responded)
> What happens with RELENG_6_2, IIRC there was only very limited changes
> to kernel which should only affect IPv6...
Indeed! Part of the reason I want to do the revert is to make absolutely
sure that it runs
> I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
> should add it to DEFAULTS some day...
never seen it before - if it does what it sounds like it does then it
would be very useful!
-pete.
___
freebsd-stable@freebsd.org mailing list
> I have made bge(4) patch for -STABLE (sorry, not suitable for
> RELENG_6_2):
What dates stable is this relative to ? I am trying to apply your
patch to a cvsup of stable pulled on the day/time you sent your email,
but parts of it are failing for me unfortunately. I would like to test this
as I
> Mine applied cleanly to sources from last Friday.
O.K., that works (now I have the correct date in my supfile). Will
give it a shot...
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
> regression that was introduced late in the 6.2 release cycle. I'm
> personally pretty skeptical that this could cause a problem, although
> I'm admittedly a little biased, plus there weren't a lot of details in
> your email as to what the problem is.
Well, you are right - it wont run a stock -R
what would happen if I made a machine which contained a mirrored
geom pair consiting of one local driive and one drive accessed via iscsi on
a remote machine ? would this work ?
what I am considering is two such machines, geographicly distinct. one is
a 'master' and boots off the mirrored drive, t
I dont know how backward compatible ports are ggenerally, but I
have a 4.11 machine that I really want to upgrade the ports on.
But I dont know if they will alla ctually compile, and I dont wnat to
start doing the process only to find that I cant build one of them
possibly. Does anybody know if thi
> 99.9% of ports seems to work ... I've hit a few that are marked as BROKEN,
> like postgis stuff, but nothing that I'd considered "mainstream" ...
Ah, thats great to know, hanks. It's the exim/clamav/spamassassin stuff
which I really want to upgrade.
cheers,
-pcf.
_
> I still share a part of your trepidation about getting oneself into
> a bind with uncooperative dependencies, etc. However, I have had
> more success than I would have imagined.
Thats good to hear. What I am intending to do is to backup the
whole ports tree, try and do the upgrade, and if it do
Just spent an afternoon working throuhg 6.1 on amd64 to try and report on
any on the problems I;ve been having with it since 5, but they have all
gone away. Very impressed - I can't find a single issue with it so far.
Nice piece of work!
-pcf.
___
freeb
Is there any way of telling from this line whether the processor is capable
of supporting amd64/emt64 ? Am trying to doo an audit of our FreeBSD machines
to see whcih ones will need replacing if and when we move to 64 bits.
thanks,
-pete.
___
freebsd-st
I have an MSI K8D Master, wth an Opteron 242 installed, on which I have been
happily running 6.0-RELEASE. I did have one problem wuth the board, which was
that if I had ACPI enabled then the operating system would not boot, it froze
at the point where it waited for the SCSI devices to settle. I got
> when you boot, at the FreeBSD menu, break to the command prompt and
> type this:
>
> debug.acpi.disabled=timer
> boot
O.K., I will give this a try - that might fix theoriginal problem
with ACPI booting too I guess ?
Cant try this for a few hours though as the machine is remote,
thanks for th
> debug.acpi.disabled=timer
>
> and see if it works. I have one system on which 5.4 works
> flawlessly, but anything from 6.0-REL and up requires I disable the
> ACPI timer.
Thanks - that does make it work with ACPI enabled, which is good. It
still won't boot SMP however - and despite the fca
> If your running a desktop, I'd recommend sticking with 32-bit. For a
> server doing a lot of I/O, go with 64-bit. The Athlon will run very
> fast in both modes, but your software compatibility is better in i386
> mode.
Interesting comment - I have a server at home with a pair of Opteron
> Let me comment that my 64-bit commentary about I/O is based on
> experience with Opterons, which have excellent I/O bandwidth. The
> Intel EM64T boxes do ok, too, but I have no experience with other 64-
> bit CPUs. The opterons are just a notch above anything else that
> I've used.
Ah,
> Note that using different slices may change your results. All modern
> disks are faster near the outside (start of the disk) then the inside
> (I get more than 50% increase from inside to outside on one system).
I am thinking this will not be an issue, given that it is the performance
of the ne
About an hour ago I started getting regular
messages from cron running /usr/libexec/save-entropy which
contail the single line "IPv4: not found"
Anybody got any ideas ? The only thing I did at that porint
was to do an 'rm' of /usr/obj in preparation for compiling
this mornings 61 code to test it.
> What happens if you run it from the command line?
Same thing. The problem's now gone away though following an installworld.
-pcf.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
> OK, I found out that my array has been already set up as RAID 5, which
> is what I'm looking for. Do you think it is time now to configure the
> volumes or is there something else needs to be done before that?
If the array has been set up as RAID 5 then just go ahead and install
FreeBSD on it. I
Have just changed a machine from 4.11 to 6.1 by re-installing. It all
works fine, but I cannot work out how to make the SMB filesystems in fstab
mount at boot time.
I used to do this by copying /usr/src/contrib/smbfs/examples/smbfs.sh.sample
to one of the rc directories, but this script does not s
> Since you say mount -a works, it sounds likely you have something in your
> fstab preventing auto mounting (noauto??), or perhaps some error is being
> generated at boot time (check /var/log/messages?). Maybe if you post your
> fstab someone will spot something.
Actually, after much oainful d
> What is the best approach to keep dhclient from overwriting
> /etc/resolv.conf every time it gets a new lease on an IP address?
in /etc/dhclient.conf add a couple of lines:
supersede domain-name "mydomain";
supersede domain-name-servers 192.168.3.1;
replacing as appropoiate...
Not that 6.1 is out the dor I monder if anyone wuld like to give me
a hand with an SMP problem I have. I am running a system with two
Opterorn 242 processors in a K8D Master-F motherboard, each with 512M
of RAM attached. The processors both work and the system will run SMP
under wndows 2000 quite h
> You say you can boot 'safe', can you boot with just ACPI disabled?
Not using an SMP kernel, no. I did another experiment though, I
installed amd64 onto an IDe drive, and that will boot SMP with
APCI disabled, but still only recognises a single processor.
> One suggestion, boot in SAFE or non-AC
> We (Intel networking group) have seen issues with SMP and amd64
> as well, although I dont know that its fully characterized (what works
> and what doesnt) yet.
When I tried mine under amd64 it seemed to behave slightly better oddly
enough - it would at least boot up the SMP kernel without ACPI,
> If just non-ACPI isnt sufficient, the other thing SAFE does is turn
> off disk DMA. I have an as-yet unreleased system that has this
> same type of issue, and the problem is that two PCI device ID's
> are not recognized, so maybe that will be your problem.
So, I got around to booting the system
> What is the correct way for 6-STABLE to achieve what I want to do?
> (i.e. write the rc.conf from a rc script)
I thought rc.conf was simply a script that set some variables. If
this is the case then you don't need to overwrite it - you simply need to
make your script set the appropriate variable
> Setting the variables can't work. As far as I can see, rc.conf is
> sourced from rc.subr. And every single script in /etc/rc.d/ sources
> rc.subr, so they reload the rc.conf file for each call.
Actually I was suggesting you overwrite rc.conf *itself* with the variable
setting code - so every s
601 - 700 of 789 matches
Mail list logo
