I had this problem recently as well. On my machine I had to recompile
xorg-server using gcc vrs clang.
~Peg
On 06/14/13 19:12, Anton Shterenlikht wrote:
> In addition to what I wrote already for sparc64,
> I now get this failure on amd64 r249781:
>
> (EE) Jun 14 18:17:27 NVIDIA(0): Failed to ini
On Sunday 04 March 2012 16:27:56 Manfred Antar wrote:
> At 05:25 AM 3/4/2012, O. Hartmann wrote:
> >Buildworld of FBSD 10.o-CUR/amd64 fails with the below shown error
> >messages since this weekend:
> >
> >
> >clang -O2 -pipe -O2 -fno-strict-aliasing -pipe -pipe -O3
> >-fno-strict-aliasing -march=n
On Sunday 20 November 2011 15:24:41 Andriy Gapon wrote:
> > I have tried issuing a TUR to all my drives to see if it was controller
> > or drive specific, but all of them return the same error (The drives are
> > Seagate, Hitachi and WD).
> >
> > What am I doing wrong?
>
> You are sending SCSI co
Hi Nima,
I have tried your latest patch against current, but I am having
difficulty
getting it to work. I was wondering, is this feature limited to SCSI drives?
I have been trying it against my SATA drives but it looks like it is failing
on issuing a TUR.
IE:
feathers# camcontrol
>>
>>To me, the only difference between borking a drive because of
>> bad firmware and typing "rm -rf *" from root is about £40. You still
>> lose at least a day rebuilding/restoring everything.
>>
>
>You clearly haven't bought a hard drive recently.
>
>Chris
Laughs!
Yea, trus
>> The linux hdparm program is so paranoid about this that you have to use
>> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
>
>I concur. Loudly. The ability to brick your hardware is just too
>large to not make people go through the "I tell you three times"
>dance. It's n
>> If it's only one process, the machine (usually) doesn't hang, even
>> when that process is copying big files back and forth for a long
>> period of time (it's a backup process). But interleave that process
>> with another one accessing the same disk, and poof!, almost
>> immediately ahci tim
Hi Current,
Should the new Beta 3 have "options COMPAT_FREEBSD8" in the GENERIC
kernel config file? Or, does this happen when it goes RC?
Ta
Peg
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
On Monday 19 September 2011 20:20:18 Alisson wrote:
> if the machine doesn't have a PS2 port to use keyboard... and have only USB
> port its impossible to use an keyboard on mountroot prompt
Hi Alisson,
I dont know the complete ins and outs of this, but I think it has a lot
to do with
On Saturday 27 August 2011 13:11:43 Erich Dollansky wrote:
> Hi,
>
> On Friday 26 August 2011 07:56:04 Pegasus Mc Cleaft wrote:
> > I have recently installed this into a new machine and had chance to
>
> did you solve your problem?
>
> I have had a similar proble
Hello Current,
I have recently discovered a problem and I was wondering if anyone
has experienced this or if they can verify that it is not just my hardware.
I am running FreeBSD 9.0-BETA1 r225125 compiled with LLVM on a Xeon
processor (CPUTYPE=core2 and CFLAGS= -mmmx -msse -mss
On Sunday 25 April 2010 11:17:40 Ulrich Spörlein wrote:
> On Sat, 24.04.2010 at 16:42:37 +0000, Pegasus Mc Cleaft wrote:
> > It may already be implemented, but it would be nice if there was
> > something defined while the kernel and/or world is being built to that a
> > n
Hello Hackers & Current,
I was wondering it if is possible, or if it can be done so a separate
set
of CC, CXX, etc can be specified for building the world and kernel
independently of a ports build?
Right now, I use the base GCC to compile the world and kernel, and
GCC44
for
-Original Message-
From: Pegasus Mc Cleaft [mailto:k...@mthelicon.com]
Sent: 23 March 2010 09:57
To: 'Alexander Best'
Subject: RE: build failures after stdlib update
-Original Message-
>2. i wasn't able to reproduce your `make -V MACHINE_CPU -DCPUTYPE=native`
> > it would be nice if people with arch i386 and amd64 could try to
> > reproduce this (i believe the other archs don't support CPUTYPE=native).
> > again the easiest way to trigger this (you don't need to edit your
> > /etc/make.conf for this) should be running:
> >
> > gcc -v -x c -E -mtune=nati
On Wednesday 17 March 2010 02:22:48 Alexander Best wrote:
> so is there no way to fix this? this is what i've tried and still the
> problem exists:
Alex,
I finally got my machine all back up and running. I'll tell you what I
did and maybe it might help your situation. The only differen
On Wednesday 17 March 2010 02:22:48 Alexander Best wrote:
> so is there no way to fix this? this is what i've tried and still the
> problem exists:
One thing I am trying (and I have no idea if it will work yet) is
seeing
if replacing the /usr/lib/libc* archives with a working set from a
> >
> >Can anyone give me advice on how to track this problem down or fix
> > it? I suspect I still have a lib that still trying to use the broken
> > libc.so.7 or something else depended on it, but I am not sure..
>
> Some of the items in this commit may be causing the bad juju
> you'
Hello Current,
I am wondering if someone could help me please.
I built the 9.0-current kernel and world while there was still a bug in
the updated strlen(). Unfortunately this rendered the machine unbootable as
gptzfsloader crashed and would just echo an endless stream of spac
give it a shot. If it is the case, then the
> RootOnZFS wiki guides need to be updated to account for that. They all
> currently say to use vfs.root.mountfrom="zfs:zroot" in loader.conf
>
> Thanks,
> Chris
>
> On Wed, Feb 17, 2010 at 1:40 PM, Pegasus Mc Cle
Hello Chris, Scott & Current
I use gptzfsboot on my AMD64 (current) machine all the time and also on
my laptop. I am not sure if this will cause the problem you are seeing but I
know I ran into a lot of trouble depending on what type of pool I was
creating.
I believe this is co
21 matches
Mail list logo
