Page updated--> http://69.3.136.141/freebsd/installation/sysctl_variables_missing One
(1)
question is still outstanding ... Yes="I'm still researching this."
-
All incoming attachments get deleted.
Have a nice day.
-
_
Sorry to have to post this to the community at large, but the list maintainer hasn't
gotten back to me on other issues. With respect to the initial thread = Subject:
Re: Overheating attributed to Freebsd --sysctlvariablesnotavailable--
Any Idea why I'm not able to find this full thread in the arc
In order for me to find the thread I had to claw my way to:
http://lists.freebsd.org/pipermail/freebsd-questions/2003-November/thread.html. If
anyone
knows of an easier way to search for an entire thread, please respond.
Respectfully yours,
nw1
-
Al
Message -
From: "nw1" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, September 28, 2003 12:51 PM
Subject: Re: FreeBSD 4.8-P10 --Mouse doesn't move in the console or XFree86--
> Alex: please see the update/corrections to this p
If I remember correctly, FreeBSD (itself) doesn't use information from the BIOS. Frees
should be able to see the entire HDD. If you get geometry warnings when you attempt to
slice the drive, use an hdd utility to give you the correct geometry.
You may want to compare my suggestion with other sug
September 26, 2003
I initially installed 4.4 or 4.5 (Dec., 2001) subsequently cvsup'ing since then
(currently
at 4.8-p10); using the following hardware:
Main board - Tyan Tiger-MP (S-2460) | chipset: AMD-760 MPX
SMP using - AMD-MP 1800+'s
Ram - 768MB (crucial.com)
AGP - Matrox G450 eTV
Fl
September 26, 2003
I initially installed 4.4 or 4.5 (Dec., 2001) subsequently cvsup'ing since then
(currently
at 4.8-p10); using the following hardware:
Main board - Tyan Tiger-MP (S-2460) | chipset: AMD-760 MPX
SMP using - AMD-MP 1800+'s
Ram - 768MB (crucial.com)
AGP - Matrox G450 eTV
Floppy dr
Neither mouse will work in the console or in XFree86.
Gigabyte GA-6BXDS = main board
BIOS= AWARD (2A69KG01) ver. 4.51PG
In the PCI/ISA section of the BIOS, a USB setting of: "Assign IRQ For USB: Enabled" (is
set)
There is also a "USB Keyboard Support" setting within the BIOS's "INTERGRATED
PEROP
There were errors in an earlier post with a subject: FreeBSD 4.8-P10 --Mouse doesn't
move
in the console or XFree86--
The udated particulars are posted at: 69.3.136.141/freebsd/usb_mouse.txt
Cheese
___
[EMAIL PROTECTED] mailing list
http://lists.freeb
eating it, that still hasn't worked.
- Original Message -
From: "Kent Stewart" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, September 28, 2003 11:33 AM
Subject: Re: Update to earlier post (corrections)
&g
Alex: please see the update/corrections to this post at
http://69.3.136.141/freebsd/usb_mouse.txt
- Original Message -
From: "Alex de Kruijff" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, September 28, 200
ing further it would be most appreciated
Thanks. :-)
- Original Message -
From: "anubis" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Sent: Monday, September 29, 2003 6:23 AM
Subject: Re: FreeBSD-4.8-p10 <--> Random reboots after swapping motherboa
Our ntpd host syncs with the external public servers, but our local clients, using
ntpdate
to sync with the ntpd host (on the same sub-net), fails. Using ntpdate from the same
local clients to any external public time-server works without problems.
The details are posted at: http://69.3.136.141/
s are back online.
Would this be a case of:
a) Murphys' Law
b) Murphy & gigabyte/chipset/controller
c) Gigabyte/chipset/controller
d) Bad Karma
Thanks for your previous input.
- Original Message -
From: "Kent Stewart" <[EMAIL PROTECTED]>
To: "nw1" <[EMA
"Lowell Gilbert" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, October 09, 2003 8:52 AM
Subject: Re: 4.8-RELEASE-p13 -and- ntpd
> "nw1" <[EMAIL PROTECTED]> writes:
>
> > Our ntpd host s
This problem can be viewed @ http://69.3.136.141/freebsd/dump8/dump8_issue-1
-
All incoming attachments get deleted.
Have a nice day.
-
___
[EMAIL PROTECTED] mailing list
http://lis
FreeBSD 4.8-RELEASE-p13
This document can also be viewed @ https://69.3.136.141/freebsd/installation/geometry
Install 4.8 from CD-rom
Drive Geometry confusion.
My BIOS allows me a very limited amount of settings when it comes to an HDD.
The following are the only settings offered by my BIOS:
Rea
t.
in this instance, can someone explain what to do and, why? for future reference.
- Original Message -
From: "Jim" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 29, 2003 8:46 AM
Subject: RE: Drive Geo
FreeBSD 4.8-RELEASE-p13
The machine overheats. sysctl variables unable to be seen.
Box-1 = NFS-server (the problem machine)
Box-2 and above are NFS-clients
The short version of the problem: After some overheating issues using:
Two (2) AMD 1800+ MP processors
In a Tyan Tiger MP (S-2460),
it was
The problem can be viewed @:
http://69.3.136.141/freebsd/installation/sysctl_variables_missing
Basically, the machine is overheating (I believe) because the cpu's aren't cycling
down.
Previously I was able to cycle the processors down with the following sysctl variables:
machdep.apm_suspend_dela
hence my overheating problem is solved.
See what I mean?
>
> --- nw1 <[EMAIL PROTECTED]> wrote:
> > The problem can be viewed @:
> >
> http://69.3.136.141/freebsd/installation/sysctl_variables_missing
> >
> > Basically, the machine is overheating (I believe)
Original Message -
From: "C. Ulrich" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 03, 2003 10:10 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable--
> On Mon, 2003-11-03 at 1
complexity.
Wouldn't you think?
- Original Message -
From: "Jud" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>; "peter lageotakes" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 03, 2003 9:53 PM
Subject:
ing occurs.
Details @ http://69.3.136.141/freebsd/installation/sysctl_variables_missing
- Original Message -
From: "jon" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Sent: Monday, November 03, 2003 10:00 PM
Subject: Re: Overheating attributed to Freebsd --
on; Where are those sysctl variables
that i
was previously able to set? They are no longer available
>
> I doubt hardware manufactuers put out equipment that can't run at 100% at
> least.
>
> My 2 cents.
Your "2-cents" makes perfect sense, but as I posted above, I woul
Jud, Annotated below
- Original Message -
From: "Jud" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>; "peter lageotakes" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 6:06 AM
Subject: Re: Overheating
Paul mather,
Thanks for your response ...
See comments below (annotated)
- Original Message -
From: "Paul Mather" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 9:45 AM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
> On Mon,
annotated below
- Original Message -
From: "Technical Director" <[EMAIL PROTECTED]>
To: "Paul Mather" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 12:32 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
>
> > => I doubt har
Jud, (see below)
- Original Message -
From: "Jud" <[EMAIL PROTECTED]>
To: "nw1" <[EMAIL PROTECTED]>
Cc: "freebsd-questions" <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 3:17 PM
Subject: Re: Overheating attributed to Freebsd --sysctl
29 matches
Mail list logo
