On Thu, Jul 03, 2008 at 01:25:29AM +0200, Krzysztof J?druczyk wrote:
> Pyun YongHyeon pisze:
> > Would you try attached patch?
> >The patch is just for checking code path of fiber media.
>
> It's slightly better - some media gets detected, but looks weird to me
> (and doesn't communicate w
Kian Mohageri wrote:
> On Sun, May 18, 2008 at 3:33 AM, Johan Ström <[EMAIL PROTECTED]> wrote:
>> On May 18, 2008, at 9:19 AM, Matthew Seaman wrote:
>>
>>> Johan Ström wrote:
>>>
drop all traffic)? A check with pfctl -vsr reveals that the actual rule
inserted is "pass on lo0 inet from 123
On 02/07/2008, Chris Rees <[EMAIL PROTECTED]> wrote:
> > Date: Wed, 2 Jul 2008 10:55:07 +0200
> > "Daniel Eriksson" <[EMAIL PROTECTED]> wrote:
> > Jeremy Chadwick wrote:
> >
> >> Can the OP get some non-Samsung disks for testing?
> >
> > I've got a 750 GB Western Digital that I've been planni
Pyun YongHyeon pisze:
> Would you try attached patch?
The patch is just for checking code path of fiber media.
It's slightly better - some media gets detected, but looks weird to me
(and doesn't communicate with other machines on the switch):
# ifconfig
msk0: flags=8802 metric 0 mtu 1500
Alexander Sack wrote:
Hello:
I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based
notebook, a MSI-1710A (GX710Ax) which has a generic embedded
controller. During boot up I notice that ATH complains with:
ath_rate: version 1.2
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111
Ronald Klop wrote:
I just upgraded a machine from FreeBSD 6 to 7. Very nice.
But my portupgrade -fa failed after a while.
...
How do I know which ports I still need to update?
Run "portupgrade -fan" and see which ones it says still need upgrading.
Graham
> Date: Wed, 2 Jul 2008 10:55:07 +0200
> "Daniel Eriksson" <[EMAIL PROTECTED]> wrote:
> Jeremy Chadwick wrote:
>
>> Can the OP get some non-Samsung disks for testing?
>
> I've got a 750 GB Western Digital that I've been planning to use to
> verify if it's a SATA-150 / SATA-300 problem (it can be ju
Hi,
I recently had a patch accepted to the ports collection that took out an msync()
call that seriously detrimented performance for rrdtool updates. It seems that
in FreeBSD, msync() waits for bits to be committed to disk even when MS_ASYNC
is specified. Under Linux, there is not such a wait fo
Hi
kern.cp_time seems is reporting wrong values (most time too high) with Phenom
and amd64 (i386 Ido not know)
but with snmpget I get the correct machine values when consulting
ssCpuRawUser.0 ssCpuRawNice.0 ssCpuRawSystem.0 ssCpuRawInterrupt.0
ssCpuRawIdle.0
kern.cp_time on RELENG6 reports
Jeremy Chadwick wrote:
> Can the OP get some non-Samsung disks for testing?
I've got a 750 GB Western Digital that I've been planning to use to
verify if it's a SATA-150 / SATA-300 problem (it can be jumpered to
SATA-150), but the drive is packed with valuable data that I'd have to
move elsewhere
On Jul 2, 2008, at 1:04 AM, Marian Hettwer wrote:
puuuh, well, with your suggested change, I do get a login prompt now
(at
ttyd1 it says), but I don't see any bootup messages anymore.
It seems that the sio0 is irq 4 while booting and becomes irq3 later.
That's odd.
If I remember correctly, one
On Wed, 2 Jul 2008 00:16:41 -0700, Jo Rhett <[EMAIL PROTECTED]>
wrote:
> I'll bet you that sio is deciding that com1 or not, it's sio1 (not
> sio0) which can be fixed with the changes I mention below.
>
puuuh, well, with your suggested change, I do get a login prompt now (at
ttyd1 it says), but I
Hi Jeremy,
On Wed, 2 Jul 2008 00:27:41 -0700, Jeremy Chadwick <[EMAIL PROTECTED]>
wrote:
> On Wed, Jul 02, 2008 at 12:16:41AM -0700, Jo Rhett wrote:
>> I'll bet you that sio is deciding that com1 or not, it's sio1 (not sio0)
>> which can be fixed with the changes I mention below.
>>
>> On Jul 1, 2
Hi there,
On Tue, 1 Jul 2008 23:36:51 -0700, Ulf Zimmermann <[EMAIL PROTECTED]> wrote:
> Also remember that the blades have 2 serial ports, one can be accessed
via
> a dongle in the front of the blade and I believe that is what usual would
> be
> called COM1 by default. The virtual serial via ilo
Hi there,
On Tue, 1 Jul 2008 21:42:16 -0700, Jo Rhett <[EMAIL PROTECTED]>
wrote:
> This rhymes with sio deciding that your TTY is something other than
> ttyd0. We had this same problem on Rackable -- even though the proper
> tty was setup 0x3f8 irq 4 it was being assigned to sio1. You can see
>
Jeremy Chadwick wrote:
Which makes me wonder if there's multiple revisions of the MCP55, or, if
Samsung drives simply don't behave properly with that chipset (this has
my vote).
Daniel has the same revision (as I can see from pciconf).
--
WBR, Andrey V. Elsukov
Hi
May be this will be useful for you (from man portupgrade):
Rebuild and reinstall all that ports that were installed
prior to the
date 2001-09-20:
portupgrade -f '<2001-09-20'
On 1 июля 2008, at 18:12, Ronald Klop wrote:
Hello,
I just upgraded a machine from FreeB
On Wed, Jul 02, 2008 at 11:17:48AM +0400, Andrey V. Elsukov wrote:
> Daniel Eriksson wrote:
>>> I have two motherboards with MCP55. They work well and I didn't
>>> see any data corruption.
>>
>> Do you have SATA-150 or SATA-300 drives connected to the motherboards?
>
> All drives are SATA-300:
> Fr
On Wed, Jul 02, 2008 at 12:16:41AM -0700, Jo Rhett wrote:
> I'll bet you that sio is deciding that com1 or not, it's sio1 (not sio0)
> which can be fixed with the changes I mention below.
>
> On Jul 1, 2008, at 11:38 PM, Ulf Zimmermann wrote:
>> I take that back, on blades the virtual serial is on
Daniel Eriksson wrote:
I have two motherboards with MCP55. They work well and I didn't
see any data corruption.
Do you have SATA-150 or SATA-300 drives connected to the motherboards?
All drives are SATA-300:
FreeBSD 6.2:
1x WDC WD3200YS-01PGB0/21.00M21
FreeBSD 8.0:
5x WDC WD5001ABYS-01YNA0/59
I'll bet you that sio is deciding that com1 or not, it's sio1 (not
sio0) which can be fixed with the changes I mention below.
On Jul 1, 2008, at 11:38 PM, Ulf Zimmermann wrote:
I take that back, on blades the virtual serial is on COM1.
On Tue, Jul 01, 2008 at 11:36:51PM -0700, Ulf Zimmermann
I take that back, on blades the virtual serial is on COM1.
On Tue, Jul 01, 2008 at 11:36:51PM -0700, Ulf Zimmermann wrote:
> Also remember that the blades have 2 serial ports, one can be accessed via
> a dongle in the front of the blade and I believe that is what usual would be
> called COM1 by de
Also remember that the blades have 2 serial ports, one can be accessed via
a dongle in the front of the blade and I believe that is what usual would be
called COM1 by default. The virtual serial via ilo takes up the COM2 by
default. This is at least the default on DL series servers and I haven't
ch
23 matches
Mail list logo
