We have to wait, unfortunately. I am using a Linux partition with Wine
meanwhile. As long as it's not mainstream, it will be hard to do. Not to
mention port is at 1.4.
2012/5/16 alphachi alpha...@mediaspirit.org
Can anybody play diablo 3 with wine on FreeBSD 9R amd64?
Wine 1.5.4,1 64bit can't
Hi,
I have used FreeBSD since 2002, first on i386-arch-machines and from
October 2010 on an (Intel i5 750) amd64-arch-machine. On this new computer,
a Dell Precision T1500, I now have three operating systems on
/dev/ada1s1-3: FreeBSD 8.1-RELEASE, FreeBSD 8.2-RELEASE and FreeBSD
8.3-RELEASE
On 05/06/12 01:55, Dimitry Andric wrote:
On 2012-05-05 17:54, Hartmann, O. wrote:
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week, when obviously a
problematic update to the OS was made - it is a wild guess
On 5 May 2012 16:55, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week
On 05/05/12 18:34, Chris Rees wrote:
On 5 May 2012 16:55, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time
On 2012-05-05 17:54, Hartmann, O. wrote:
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week, when obviously a
problematic update
On 05/06/12 01:55, Dimitry Andric wrote:
On 2012-05-05 17:54, Hartmann, O. wrote:
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week
I've installed the compat6x libraries and made a symlink to /lib for
libc.so.6 as per some docs I found; however, the vmware tools
installation is still failing with:
Unable to copy the source file
/usr/local/lib/vmware-tools/modules/binary/FreeBSD8.0-amd64/vmxnet.ko to
the
destination file
Hi
I have Corei3 540
What is the best fit to this processor: ia64 or amd64?
and what one from those is more stable?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
ia64 is for the Intel Itanium chips, and not compatible with standard
Intel architecture.
amd64 is what you want to use. It's what you need for a standard x86
architecture chip that's 64bit.
On 4/16/2012 9:08 AM, Eugen Konkov wrote:
Hi
I have Corei3 540
What is the best fit
Hi,
On Monday 16 April 2012 20:08:13 Eugen Konkov wrote:
I have Corei3 540
only the amd64 will run on that CPU. If you have less than 4GB of RAM you could
also run the i386 version.
What is the best fit to this processor: ia64 or amd64?
and what one from those is more stable?
I do
ia64 is for itanium.
amd64 is for 64-bit X86 ISA, name is because AMD was first to introduce it
with opteron family.
On Mon, 16 Apr 2012, Eugen Konkov wrote:
Hi
I have Corei3 540
What is the best fit to this processor: ia64 or amd64?
and what one from those is more stable
On 07/03/2012 01:39, Da Rock wrote:
On 03/07/12 04:13, Adam Vande More wrote:
On Tue, Mar 6, 2012 at 11:36 AM, Bernt Hanssonb...@bananmonarki.se
wrote:
Again, a problem is that packages can only be generated
if the port has been installed
Why is that. I hope you can educate me on that.
On Tue, Mar 6, 2012 at 11:36 AM, Bernt Hansson b...@bananmonarki.se wrote:
Again, a problem is that packages can only be generated
if the port has been installed
Why is that. I hope you can educate me on that.
Because a package is the result of what is installed. It essentially works
On 03/07/12 04:13, Adam Vande More wrote:
On Tue, Mar 6, 2012 at 11:36 AM, Bernt Hanssonb...@bananmonarki.se wrote:
Again, a problem is that packages can only be generated
if the port has been installed
Why is that. I hope you can educate me on that.
Because a package is the result of
Hello list
I want to build packages from ports on AMD64 for use on i386
since the i386 system is;
pid 21629 (cc1plus), uid 0, was killed: out of swap space
When building firefox.
Added some swap as a file so it's building as I type.
Thinking that the AMD system I can access is a wee more
On 03/05/2012 12:42 AM, Bernt Hansson wrote:
Build the port on amd64 and install it on i386 as a package.
Is it possible? Pointers? Handholding? How-to?
http://filipenf.wordpress.com/2011/10/18/cross-compiling-for-x86-in-freebsd-64-bit
2012-03-05 10:20, Edward M. skrev:
On 03/05/2012 12:42 AM, Bernt Hansson wrote:
Build the port on amd64 and install it on i386 as a package.
Is it possible? Pointers? Handholding? How-to?
http://filipenf.wordpress.com/2011/10/18/cross-compiling-for-x86-in-freebsd-64-bit/
Thank you
On 05/03/2012 16:42, Bernt Hansson wrote:
Thank you for the pointer. I do find it a bit overkill to setup jails
and such, just to build a few ports. I was thinking more along the line of;
cd /usr/ports/random port
make it for i386 even if we are building it on amd64, ooh by the way
/random port
make it for i386 even if we are building it on amd64, ooh by the way
build it as a package, and all dependencies as packages as well
Again, a problem is that packages can only be generated
if the port has been installed, which is the make package
task typically following make install
are building it on amd64, ooh by the way
build it as a package, and all dependencies as packages as well
About the only way to cross-build ports is to set up a 32-bit jail on a
64-bit host. I believe that is do-able, but I could be delusional.
Could you do it in a tinderbox? This thread
http
On Thu, Feb 16, 2012 at 9:08 AM, Antonio Olivares
olivares14...@gmail.com wrote:
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as well:
On Thu, 16 Feb 2012 09:08:54 -0600
Antonio Olivares wrote:
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as
well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A
I have a system running FreeBSD/amd64 9.0-STABLE as of
Tue Jan 10 16:22:34 CET 2012.
Every attempt by the root user to use the mlock(2) system call results
in Resource temporarily unavailable (EAGAIN, 35).
I'm using bash and ulimit -l says there's no restriction on the amount
of locked memory
On Thu, 16 Feb 2012 09:47+0100, Trond Endrestøl wrote:
I have a system running FreeBSD/amd64 9.0-STABLE as of
Tue Jan 10 16:22:34 CET 2012.
Every attempt by the root user to use the mlock(2) system call results
in Resource temporarily unavailable (EAGAIN, 35).
I'm using bash and ulimit
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
should take care of the compilation failure. Afterward you should be
able to run
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I followed advice there to run
# portmaster -w devel/pcre
and I did this, and now machine won't get X. How can I bypass this
mistake? I am now hesitant to update the other machines :(, I will
get into
You can recompile all ports that depend on pcre so that they'll use the
new shared library.
You can do so with:
# portmaster -r pcre-8.30
Ryan
On 02/15/2012 08:42 PM, Antonio Olivares wrote:
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I followed
You can recompile all ports that depend on pcre so that they'll use the
new shared library.
You can do so with:
# portmaster -r pcre-8.30
Ryan
On 02/15/2012 08:42 PM, Antonio Olivares wrote:
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I
Antonio Olivares olivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
Antonio Olivares olivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7
# make install clean
=== License check disabled, port has not defined LICENSE
= ifstated-4.7.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
= Attempting to fetch
http://christianserving.org/ports/net/ifstated/ifstated-4.7.tar.gz
ifstated-4.7.tar.gz 100% of
On Wed, 01 Feb 2012 22:18:31 +0100
1126 mailingli...@elfsechsundzwanzig.de wrote:
Hi,
Please update your ports tree, we have fixed that.
- Martin
Hello list!
Today, I installed a fresh 9.0-RELEASE/amd64 and wanted to install
Xorg. There were no other packages installed before, so Xorg
Thanks! :)
Martin Wilke m...@freebsd.org wrote:
On Wed, 01 Feb 2012 22:18:31 +0100
1126 mailingli...@elfsechsundzwanzig.de wrote:
Hi,
Please update your ports tree, we have fixed that.
- Martin
Hello list!
Today, I installed a fresh 9.0-RELEASE/amd64 and wanted to install
Xorg
difficultites when starting up the desktop. The
desktop starts up automagically and when I start firefox or terminal
there is no border :(. Upon logging out and unchecking Save Settings,
and relogging back in the borders appear. I have had this happen once
on one of my FreeBSD 8.2 amd64 boxes
:(. Upon logging out and unchecking Save Settings,
and relogging back in the borders appear. I have had this happen once
on one of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
settings. Now I can't find the settings that cause this. All I know
is that if I log out and un check
this happen once
on one of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
settings. Now I can't find the settings that cause this. All I know
is that if I log out and un check save settings, the border appear
again and all is well. But if I reselect the save settings box, and
log
Hello list!
Today, I installed a fresh 9.0-RELEASE/amd64 and wanted to install
Xorg. There were no other packages installed before, so Xorg and all
it's run- and build-dependencies would be the first. But it fails. The
error message reads:
...
checking for XEXT... configure: error
of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
settings. Now I can't find the settings that cause this. All I know
is that if I log out and un check save settings, the border appear
again and all is well. But if I reselect the save settings box, and
log out and back
there is no border :(. Upon logging out and unchecking Save Settings,
and relogging back in the borders appear. I have had this happen once
on one of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
settings. Now I can't find the settings that cause this. All I know
is that if I log out
On 24 January 2012 02:12, Christer Solskogen
christer.solsko...@gmail.com wrote:
On Tue, Jan 24, 2012 at 12:22 AM, Lee Thomas lthomas_li...@lthomas.net
wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with FreeBSD
9.0-STABLE, and I'm not sure
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with
FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect
configuration on my part. The lang/lua port throws a linker error,
claiming to need -fPIC, which is odd because the port Makefile
On Mon, Jan 23, 2012 at 04:22:30PM -0700, Lee Thomas wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with
FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect
configuration on my part. The lang/lua port throws a linker error
On Tue, Jan 24, 2012 at 12:22 AM, Lee Thomas lthomas_li...@lthomas.net wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with FreeBSD
9.0-STABLE, and I'm not sure whether it's a bug or incorrect configuration
on my part. The lang/lua port throws
From: Antonio Olivares olivares14...@gmail.com
To: FreeBSD Questions freebsd-questions@freebsd.org
Sent: Thursday, January 19, 2012 9:07 PM
Subject: mplayer fails to compile on amd64 machine
Dear kind folks,
Running Amd64 FreeBSD 8.0 updated
l/live/groupsock/libgroupsock.a
program ported to run on FreeBSD and all the
subtle changes can never be thought completely through. Send an e-mail to the
port maintainer, they'll get it fixed in the next round.
___
Thank you Bill, I have three machines two running 8.2 amd64 and one
Dear kind folks,
Running Amd64 FreeBSD 8.0 updated
l/live/groupsock/libgroupsock.a -lm
-rpath=/usr/lib:/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46
-liconv /usr/lib/libncurses.so -lpng -lz -ljpeg -lungif
-L/usr/local/lib -lfreetype -lz -lbz2 -lfontconfig -lz
/usr/lib
Hello,
The CURRENT (9.0R) release notes have the following to say about the
AMD64 port:
--8-
As of this writing, the following processors are supported:
...
* All Intel Core 2 (not Core Duo) and later processors
Hi all,
Running FreeBSD 8.1-RELEASE-p6 here, we've noticed that both the amd64 build of
supfilesrv as installed by the sup-2.0.20060802 package AND the amd64 build
of cvsupd as installed by the cvsup-without-gui-16.1h_4 package, both
segmentation fault immediately upon connection.
The easiest
Update.
-Original Message-
From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
questi...@freebsd.org] On Behalf Of Devin Teske
Sent: Monday, January 09, 2012 12:05 PM
To: FreeBSD Questions
Subject: Broken amd64 packages: cvsup-without-gui and sup
Hi all,
Running
On Thu, Jan 5, 2012 at 7:16 PM, Bill Tillman btillma...@yahoo.com wrote:
Today I encountered a problem which has me stumped. I downloaded and
burned the ISO image for 9.0-RELEASE for amd64. I installed an older
IDE hard drive to test the new OS with and did the install.
...
Well
From: Waitman Gobble gobble...@gmail.com
To: Bill Tillman btillma...@yahoo.com
Cc: FreeBSD Questions freebsd-questions@freebsd.org
Sent: Friday, January 6, 2012 5:09 AM
Subject: Re: 9.0-RELEASE amd64 Bricked My Hard Drive
On Thu, Jan 5, 2012 at 7:16 PM
On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote:
I had been running a similar computer with Windows XP with it. The
drive was working fine a few moments before I did the install. I have
a utility to test hard drives which boots from CD but like I said, when
this drive
On Thu, 5 Jan 2012, Bill Tillman wrote:
Well the install finished and
then I attempted to reboot the system but nothing happened. And by that I
mean the computer's flash screen would come up and give me the choice
to enter the Bios Setup or Boot Menu and that's all.
The BIOS on some systems
El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble escribió:
On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote:
I had been running a similar computer with Windows XP with it. The
drive was working fine a few moments before I did the install. I
acer ?? i had this with acer.. remove hdd...acess bios change ahci mode
and try installing again.
On Fri, Jan 6, 2012 at 8:16 PM, Matthias Apitz g...@unixarea.de wrote:
El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble
escribió:
On Fri, Jan 6, 2012 at 3:21 AM, Bill
drive a slave and boot with another drive and
cleanup the mess. But no matter which computer I chose, and no matter
how I setup the Slave/Master drive, as long as this drive which I had
installed FreeBSD-9.0-amd64 was in the loop, the computer would
lockup at the bios screen. I could not get
Waitman Gobble wrote:
On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman btillma...@yahoo.com wrote:
I had been running a similar computer with Windows XP with it. The
drive was working fine a few moments before I did the install. I have
a utility to test hard drives which boots from CD but like I
Bill Tillman wrote:
Today I encountered a problem which has me stumped. I downloaded and
burned the ISO image for 9.0-RELEASE for amd64. I installed an older
IDE hard drive to test the new OS with and did the install. I was very
surprised at the (1) the dvd is actually a live CD if you wanted
Today I encountered a problem which has me stumped. I downloaded and
burned the ISO image for 9.0-RELEASE for amd64. I installed an older
IDE hard drive to test the new OS with and did the install. I was very
surprised at the (1) the dvd is actually a live CD if you wanted it to be
and (2
On Jan 5, 2012, at 7:16 PM, Bill Tillman wrote:
Today I encountered a problem which has me stumped. I downloaded and
burned the ISO image for 9.0-RELEASE for amd64. I installed an older
IDE hard drive to test the new OS with and did the install. I was very
surprised at the (1) the dvd
Bill Tillman btillma...@yahoo.com wrote:
... no matter which computer I chose, and no matter how I setup
the Slave/Master drive, as long as this drive which I had
installed FreeBSD-9.0-amd64 was in the loop, the computer would
lockup at the bios screen. I could not get anything to boot
On Mon, 02 Jan 2012 07:18:53 +0100
Marco Steinbach c...@executive-computing.de wrote:
Janos Dohanics wrote on 31.12.2011 19:56:
Buildworld stopped with this error (with updated source):
[...]
cc -O3 -DNEED_SOLARIS_BOOLEAN
[...]
I have posted the build log at
Janos Dohanics wrote on 02.01.2012 11:04:
On Mon, 02 Jan 2012 07:18:53 +0100
Marco Steinbach c...@executive-computing.de wrote:
Janos Dohanics wrote on 31.12.2011 19:56:
Buildworld stopped with this error (with updated source):
[...]
cc -O3 -DNEED_SOLARIS_BOOLEAN
[...]
I have posted the
On Mon, 02 Jan 2012 13:15:59 +0100
Marco Steinbach c...@executive-computing.de wrote:
Janos Dohanics wrote on 02.01.2012 11:04:
On Mon, 02 Jan 2012 07:18:53 +0100
Marco Steinbach c...@executive-computing.de wrote:
Janos Dohanics wrote on 31.12.2011 19:56:
Buildworld stopped with this
Janos Dohanics wrote on 31.12.2011 19:56:
Buildworld stopped with this error (with updated source):
[...]
cc -O3 -DNEED_SOLARIS_BOOLEAN
[...]
I have posted the build log at
http://wwwp.3dresearch.com/ALMAVIVA2011123101_buildworld
Would you please advise?
Quoting
Buildworld stopped with this error (with updated source):
[...]
cc -O3 -DNEED_SOLARIS_BOOLEAN
-I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris
-I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include
DISABLE_MAKE_JOBSi helps.
This doesn't work, either.
In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching
off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64.
I do not know whether OS versions below 10.0 do support the WITH_ICONV knob.
This maybe
in the snippet above).
In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching
off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64.
I do not know whether OS versions below 10.0 do support the WITH_ICONV knob.
This maybe is a hint to the problem.
iconv was only
On 2011-12-07 05:56, O. Hartmann wrote:
On FreeBSD 10.0-CURRENT/amd64 I run into the error shown below when
updating the installation of the gcc46 compiler suite.
If you report port compilation errors, always use DISABLE_MAKE_JOBS,
otherwise the actual error message will drown in multithreaded
Hello.
On FreeBSD 10.0-CURRENT/amd64 I run into the error shown below when
updating the installation of the gcc46 compiler suite.
The OS has been compiled via CLANG, binutils 2.22 are installed and has
been installed either with the UNAME_r settings and WITH_FBSD10_FIX set
in /etc/make.conf.
I
On Wed, Dec 07, 2011 at 05:56:31AM +0100, O. Hartmann wrote:
config.status: creating ada/Makefile
config.status: creating auto-host.h
config.status: executing default commands
gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build'
gmake[1]: *** [stage1-bubble] Error 2
gmake[1]:
On Sat, 19 Nov 2011 04:54:18 -0600, Jukka A. Ukkonen j...@iki.fi wrote:
Hello,
Has anyone else noticed a similar odd behavior with AMD64 and 9.0
prerelease (as well as RCs and betas)?
On my 12 core (2*4162EE) the whole system just freezes quite often
without any warning, without any messages
and r2880) on amd64
systems. print/pips* reports they require 386 and do not
compile on amd64.
print/gimp-gutenprint works pretty well from Gimp, although
I have not figured out how to get consistent color and brightness.
It supports both of those printers.
I'm sure I'm not alone
quality printing with
epson inkjet printers (in my case r2400 and r2880) on amd64
systems. print/pips* reports they require 386 and do not
compile on amd64.
print/gimp-gutenprint works pretty well from Gimp, although
I have not figured out how to get consistent color
, David Southwell wrote:
Anyone up to date on how to do high quality printing with
epson inkjet printers (in my case r2400 and r2880) on amd64
systems. print/pips* reports they require 386 and do not
compile on amd64.
print/gimp-gutenprint works pretty well from Gimp
Hello,
An amd64 running fbsd9-RC1 was shutdown overnight from the 'shutdown
-p' command. It reported an unclean shutdown and I ran 'fsck -y'.
Still it will not boot and the message is Journal timestamp does
not match fs mount time.
This is occurring for both /var and /usr.
How can I fix
Hello,
An amd64 running fbsd9-RC1 was shutdown overnight from the 'shutdown
-p now' command. It reported an unclean shutdown and I ran 'fsck
-y'. Still it will not boot and the message is Journal timestamp
does not match fs mount time.
This is occurring for both /var and /usr.
How can I fix
Hello,
Has anyone else noticed a similar odd behavior with AMD64 and 9.0
prerelease (as well as RCs and betas)?
On my 12 core (2*4162EE) the whole system just freezes quite often
without any warning, without any messages being logged. Neither is
there any panic message from the kernel
On 11/19/11 03:54, Jukka A. Ukkonen wrote:
Hello,
Has anyone else noticed a similar odd behavior with AMD64 and 9.0
prerelease (as well as RCs and betas)?
On my 12 core (2*4162EE) the whole system just freezes quite often
without any warning, without any messages being logged. Neither
On Sat, 19 Nov 2011 12:54:18 +0200 (EET)
j...@iki.fi (Jukka A. Ukkonen) wrote:
Hello,
Has anyone else noticed a similar odd behavior with AMD64 and 9.0
prerelease (as well as RCs and betas)?
Yes, I've seen a few of these myself, under both of the RCs and
PRERELEASE. No idea what
On Sun, 20 Nov 2011, per...@pluto.rain.com wrote:
Warren Block wbl...@wonkity.com wrote:
On Sat, 19 Nov 2011, David Southwell wrote:
Anyone up to date on how to do high quality printing with
epson inkjet printers (in my case r2400 and r2880) on amd64
systems. print/pips* reports they require
Sorry for the boring question, but is the default configuration file
/sys/amd64/conf/DEFAULTS anywhere include in a regular configuration
file for the kernel while building the kernel?
I looked for include statements in GENERIC, but didn't find one. I use
custom kernel config files and adapt most
On 11/08/11 12:36, O. Hartmann wrote:
Sorry for the boring question, but is the default configuration file
/sys/amd64/conf/DEFAULTS anywhere include in a regular configuration
file for the kernel while building the kernel?
I looked for include statements in GENERIC, but didn't find one. I use
Am 11/08/11 14:12, schrieb Niclas Zeising:
On 11/08/11 12:36, O. Hartmann wrote:
Sorry for the boring question, but is the default configuration file
/sys/amd64/conf/DEFAULTS anywhere include in a regular configuration
file for the kernel while building the kernel?
I looked for include
Hello.
I realised something weird in FreeBSD 10.-CURRENT/amd64 (CLANG
compiled), build as from today (buildworld).
Working the whole day coding some pyhton scripts and committing the code
to my subversion server (most recent subversion from the ports
collection, the server is a FreeBSD 9.0-RC1
On Thu, Nov 03, 2011 at 11:17:08PM +0100, O. Hartmann wrote:
Hello.
I realised something weird in FreeBSD 10.-CURRENT/amd64 (CLANG
compiled), build as from today (buildworld).
Working the whole day coding some pyhton scripts and committing the code
to my subversion server (most recent
Hello
I'v got a notebook (HP Elite 2560p) which can boot from an exteral eSATA drive.
Can FreeBSD boot from there? Is it supported?
Kind regards,
--
Martin Schweizer
off...@pc-service.ch
PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon
Tel. +41 55 243 30 00; Fax: +41 55 243
Martin Schweizer lists_free...@bluewin.ch wrote:
I'v got a notebook (HP Elite 2560p) which can boot from an exteral
eSATA drive. Can FreeBSD boot from there? Is it supported?
It seems as if it should work.
___
freebsd-questions@freebsd.org mailing
On 10/2/11 11:48 AM, Jukka A. Ukkonen wrote:
Greetings all,
Roughly a week ago I sent to this mailing list a question about
problems with installing FreeBSD 9 on an AMD64 system.
It seems that I now know the reason why booting from the install CD
failed. When buying the system I had
Greetings all,
Roughly a week ago I sent to this mailing list a question about
problems with installing FreeBSD 9 on an AMD64 system.
It seems that I now know the reason why booting from the install CD
failed. When buying the system I had not paid enough attention to
the fact that the SAS
research and found lots of posts several years
old that suggest that using wine on AMD64 is not possible or
requires binary packages that don't exist, and even if one can
install it, it doesn't run.
Has this situation improved meanwhile? Does anyone have a
recipe on how to get wine running
I've done some research and found lots of posts several years
old that suggest that using wine on AMD64 is not possible or
requires binary packages that don't exist, and even if one can
install it, it doesn't run.
Has this situation improved meanwhile? Does anyone have a
recipe on how
On Mon, 15 Aug 2011 09:37:06 +0200, Christian Barthel wrote:
I don't understand why you have chosen AMD64? You only have 2 GB memory,
which can be adressed under i386 too and you can avoid a lot of
problems.
Reason: The i386 platform is obsoleted, and there will be
less and less targets
On Mon, 15 Aug 2011 18:04:53 +1000, Ashley Williams wrote:
I've done some research and found lots of posts several years
old that suggest that using wine on AMD64 is not possible or
requires binary packages that don't exist, and even if one can
install it, it doesn't run.
Has
On Mon, Aug 15, 2011 at 9:37 AM, Christian Barthel b...@nyx.user-mode.org
wrote:
On Sun, Aug 14, 2011 at 10:27:08PM +0200, Polytropon wrote:
Current system is 8.2-STABLE/amd64. Should I better re-install
everything (Intel Core2 4300 1.80GHz / 1799.81-MHz K8-class CPU
here, and 2 GB RAM
Christian Barthel writes:
Current system is 8.2-STABLE/amd64. Should I better re-install
everything (Intel Core2 4300 1.80GHz / 1799.81-MHz K8-class CPU
here, and 2 GB RAM, that's why the AMD64 choice) and use i386
instead?
I don't understand why you have chosen AMD64? You only
that using wine on AMD64 is not possible or
requires binary packages that don't exist, and even if one can
install it, it doesn't run.
Has this situation improved meanwhile? Does anyone have a
recipe on how to get wine running?
Current system is 8.2-STABLE/amd64. Should I better re-install
everything
101 - 200 of 2012 matches
Mail list logo
