Kimi wrote:
xorg-driver-nv will be more then good enough, providing 3D is not needed.
2D can also be pretty sluggish at times. The following shows the nv
driver in its fully glory as I was leafing through a page of photos:
http://home.no/tl18/misc/mincemeat.jpg
Moreover, the nv driver does
http://home.no/tl18/misc/mincemeat.jpg
Moreover, the nv driver does not provide a way to properly control
brightness and contrast. I would say it is strictly necessary for
anyone who is into photography to use the nvidia-driver, even if they
are not remotely interested in 3D.
--
for desktop i
of where else
to look for any hints as to what's going on.
Here're the details on the machine (IBM T61p):
$ uname -a
FreeBSD ibm-t61p.snipped.snipped 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0:
Sun Feb 3 15:42:51 GMT 2008
snipped@ibm-t61p.snipped.snipped:/usr/obj/usr/src/sys/STEEL amd64
$
Package
I find that clicking on the linux-opera menu item fails to start Opera.
Nothing gets logged to messages / security, and I can't think of where else
to look for any hints as to what's going on.
start linux opera from xterm and read what's up.
do you have
linprocfs
Hi Wojciech!
Thanks for getting back to me.
On Sun, 03 Feb 2008, Wojciech Puchar wrote:
I find that clicking on the linux-opera menu item fails to start Opera.
Nothing gets logged to messages / security, and I can't think of where else
to look for any hints as to what's going on.
$ linux-opera
[1] 2263
[EMAIL PROTECTED] ~]$ shm_allow_removed is disable, set OPERA_NUM_XSHM to 0
to disable shared memory.
ELF binary type 0 not known.
ELF binary type 0 not known.
ELF binary type 0 not known.
^^^
this is strange - like no linux emulation active at all.
no more
$ cat /etc/fstab
# DeviceMountpoint FStype Options DumpPass#
/dev/ad4s2b noneswapsw 0 0
/dev/ad4s2a / ufs rw 1 1
/dev/ad4s2e /home ufs rw
Hi Wojciech!
Thanks for the response.
On Sun, 03 Feb 2008, Wojciech Puchar wrote:
$ cat /etc/fstab
# DeviceMountpoint FStype Options Dump
Pass#
/dev/ad4s2b noneswapsw 0 0
/dev/ad4s2a /
so please ask some else :)
i have no other ideas.
and please check your mailserver (respond on priv please)
Feb 3 21:42:04 wojtek sm-mta[7276]: m13Kf36P007273:
to=[EMAIL PROTECTED], ctladdr=[EMAIL PROTECTED]
(1003/1003), delay=00:01:01, xdelay=00:01:01, mailer=esmtp, pri=31239,
On Sun, 3 Feb 2008 20:33:10 + Stacey Roberts wrote:
On Sun, 03 Feb 2008, Wojciech Puchar wrote:
and turn ON linux emulation because this is probably your problem :)
Err., if you meant to ensure that linux_enable=YES is in /etc/rc.conf,
and that linux-base is installed, then these
On Sun, 3 Feb 2008 21:07:06 + Stacey Roberts wrote:
% kldstat | grep linux
$ kldstat | grep linux
$
Nothing was returned..,
OK. Can you try kldload linux as root, repeat that kldstat... and
if it shows linux.ko then try to run linux-opera?
WBR
--
bsam
@snipped.snipped.snipped:/usr/obj/usr/src/sys/STEEL amd64
$
% kldstat | grep linux
$ kldstat | grep linux
$
Nothing was returned..,
% sysctl -a | grep linux
$ sysctl -a | grep linux
hw.snd.compat_linux_mmap: 0
$
% ls -ld /var/db/pkg/linux*
$ ls -ld /var/db/pkg/linux*
drwxr-xr-x 2 root wheel 512
Hi Boris,
Good to hear from you..,
On Mon, 04 Feb 2008, Boris Samorodov wrote:
On Sun, 3 Feb 2008 21:07:06 + Stacey Roberts wrote:
% kldstat | grep linux
$ kldstat | grep linux
$
Nothing was returned..,
OK. Can you try kldload linux as root, repeat that kldstat... and
if
On Sun, 3 Feb 2008 21:39:57 + Stacey Roberts wrote:
On Mon, 04 Feb 2008, Boris Samorodov wrote:
On Sun, 3 Feb 2008 21:07:06 + Stacey Roberts wrote:
% kldstat | grep linux
$ kldstat | grep linux
$
Nothing was returned..,
OK. Can you try kldload linux as root,
graphics should suffice. I've been looking at a few specs, many of
them use Nvidia chipsets and I understand that there isn't a Nvidia graphics
driver for FreeBSD on the AMD64 platform.
If I choose a Nvidia based motherboard would I have to install the i386
version of FreeBSD if I wanted to use
a Nvidia graphics
driver for FreeBSD on the AMD64 platform.
by general there are lots of problems with nvidia as it's closed source.
i always avoid closed source.
If I choose a Nvidia based motherboard would I have to install the i386
version of FreeBSD if I wanted to use the onboard graphics
with
integrated graphics should suffice. I've been looking at a few specs, many of
them use Nvidia chipsets and I understand that there isn't a Nvidia graphics
driver for FreeBSD on the AMD64 platform.
If I choose a Nvidia based motherboard would I have to install the i386
version of FreeBSD
It was an Athlon X2 4600+ and the onboard graphics was GeForce 7100.
Usually the integrated graphics come from the lower-spec graphic chipsets and
are well supported by the open source nv driver. As long as you don't need
good to know at least partially things changed to better.
,
many of them use Nvidia chipsets and I understand that there isn't a
Nvidia graphics driver for FreeBSD on the AMD64 platform.
by general there are lots of problems with nvidia as it's closed source.
i always avoid closed source.
That's a very unfounded statement.
Nvidia is probably the best
On Saturday 02 February 2008, Wojciech Puchar wrote:
After running a 90 hour portupgrade job on my current Duron 1600 based
system
I've persuaded myself that a hardware upgrade is due.
simply use precompiled ones if it's a problem.
anyway - i don't what bloatware you have compiled but on
On 02/02/2008, Wojciech Puchar [EMAIL PROTECTED] wrote:
[...]
i needed few hours to install things i use.
not a very helpful comment at all. Durons were pretty crap.
[...]
by general there are lots of problems with nvidia as it's closed source.
i always avoid closed source.
again, not
and overclocking so a relatively low end motherboard with
integrated graphics should suffice. I've been looking at a few specs, many of
them use Nvidia chipsets and I understand that there isn't a Nvidia graphics
driver for FreeBSD on the AMD64 platform.
There are nvidia chipsets such as nforce4
On 02/02/2008, Mel [EMAIL PROTECTED] wrote:
[...]
I'd really stay away from ATI, for your purposes, either go with nvidia or
Intel onboard.
nothing wrong with xorg-driver-radeonhd or xorg-driver-ati for
ATi/AMDs graphics cards, providing you don't need 3D now on newer
hardwares.
--
Mel
--
and overclocking so a relatively low end
motherboard with integrated graphics should suffice. I've been
looking at a few specs, many of them use Nvidia chipsets and I
understand that there isn't a Nvidia graphics driver for FreeBSD on
the AMD64 platform.
As others have said it's only
Daniel Rucci wrote:
Kris Kennaway wrote:
No, it's not convenient. There is a large maintenance cost for
keeping the fortran compiler in the base system for little gain
(nothing in FreeBSD uses it), and it is also only of use to a small
subset of FreeBSD users, so this is a perfect situation
Kris Kennaway wrote:
No, it's not convenient. There is a large maintenance cost for
keeping the fortran compiler in the base system for little gain
(nothing in FreeBSD uses it), and it is also only of use to a small
subset of FreeBSD users, so this is a perfect situation where moving
it to
Hello people,
I'd like to ask, whether there is, or will be a paravirtualized
version of freebsd for amd64?
Kind regards,
Denis Maligin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Hi all
I've just try to install FreeBSD 7.0RC1 on my new Dell PowerEdge 2900 with
PERC 6/i with two raid volumes on with 2 disk (2*80Go) and one 6 disk
(6*750 raid5).
The first volume (80Go) is perfectly working and the server boot normaly.
But on the second volume I've got
A
System: FreeBSD 6.2 amd64, release #13
Xorg X Server 1.4.0 Release date Sept. 5, 2007
X Protocol ver. 11, Rev 0
gnucash-2.2.0_1
gnucash-docs-2.2.0_2
yelp-2.20.0
FreeBSD GNOME Project: GNOME 2.20 Upgrading FAQ / GNOME 2.20 problems
and their solutions
Some users have
Hello!
I'm struggling with a 32-bit FreeBSD executable, which is identified as:
ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically
linked (uses shared libs), stripped
Unfortunately, the executable would not run:
/libexec/ld-elf.so.1: /lib/libm.so.4: unsupported file
O. Hartmann wrote:
Kris Kennaway wrote:
O. Hartmann wrote:
Sorry about the noise, but I miss g77 or f77 on my FreeBSD 7.0-PRE
box. Where is it? Hasn't gcc 4.2 as incorporated in FreeBSD as the
native compiler also a native fortran 90 compiler?
No, you need to install the gfortran port.
Kris Kennaway wrote:
O. Hartmann wrote:
Sorry about the noise, but I miss g77 or f77 on my FreeBSD 7.0-PRE
box. Where is it? Hasn't gcc 4.2 as incorporated in FreeBSD as the
native compiler also a native fortran 90 compiler?
No, you need to install the gfortran port. This is presumably
Hi,
I'm experiencing some problems while attempting to export a ZVOL with
ggated on a gigabit network.
All servers are running FreeBSD 7.0-RC1 on amd64, and using bce NICs.
client# ggatec create -t 6 -u 0 172.16.100.200 /dev/zvol/storage/vol0
client# ls -l /dev/ggate*
crw-r- 1 root
Hugo Silva wrote:
Hi,
I'm experiencing some problems while attempting to export a ZVOL with
ggated on a gigabit network.
All servers are running FreeBSD 7.0-RC1 on amd64, and using bce NICs.
client# ggatec create -t 6 -u 0 172.16.100.200 /dev/zvol/storage/vol0
client# ls -l /dev/ggate
to conclusion that this would be the
right time to switch to amd64.
My old machine was an AthlonXP at 1500MHz running FreeBSD7.0RC1 with a
ZFS pool doing DNS, DHCP, NFS, serving websites with Apache, Mail. As
you can see there are quite some services/ports installed and
configured.
I searched the net
On Thu, Jan 03, 2008 at 06:44:45PM +0100, Christian Walther wrote:
[...]
I searched the net for some information on migrating from i386 to
amd64. I'd like to build a new kernel for amd64, reboot. Do a
buildworld and installworld and a portupgrade -afk --batch
afterwards.
The approach that I
Sorry about the noise, but I miss g77 or f77 on my FreeBSD 7.0-PRE box.
Where is it? Hasn't gcc 4.2 as incorporated in FreeBSD as the native
compiler also a native fortran 90 compiler?
Regards,
Oliver
___
freebsd-questions@freebsd.org mailing list
O. Hartmann wrote:
Sorry about the noise, but I miss g77 or f77 on my FreeBSD 7.0-PRE box.
Where is it? Hasn't gcc 4.2 as incorporated in FreeBSD as the native
compiler also a native fortran 90 compiler?
No, you need to install the gfortran port. This is presumably
documented in the release
snowcrash+freebsd wrote:
hi,
i've FBSD/amd64 62Rp9 installed. kernel world are my own builds
from latest cvsup.
on boot I see:
FreeBSD/i386 bootstrap loader
odd. i'd expect a native loader ...
checking in,
/usr/src/sys/boot ls
Makefile alpha/arm/ efi/ forth
On Dec 22, 2007, at 3:32 AM, Bruce Cran wrote:
AMD64 CPUs are backwards compatible with i386; they boot in 16-bit
real mode and only get switched into 64-bit 'long mode' by the kernel
later on. Since both i386 and amd64 start booting in the same way,
there's no need for separate bootloaders
hi,
i've FBSD/amd64 62Rp9 installed. kernel world are my own builds
from latest cvsup.
on boot I see:
FreeBSD/i386 bootstrap loader
odd. i'd expect a native loader ...
checking in,
/usr/src/sys/boot ls
Makefile alpha/arm/ efi/ forth/ia64/ pc98
This is not a priority, but I'm suprised that both the downloaded
(ariff?) and the built-from-source snd*.ko files give me a:
kldload: can't load snd_hda: Exec format error
When I try to load them...guess my kernel is out of date with the
latest 6.2-stable source?
Best,
Steve
6.2 - amd64
from.
System is a SA6i RAID5-array with 6x300GB disks. Possibly I need to
enter drive geometry manually but have no idea where to get that
info from, perhaps somebody knows where to look?
i386 does not boot either - same
A RAID1+0 array with 4x36GB disks boots fine both amd64 and i386.
Right
no idea where to get that
info from, perhaps somebody knows where to look?
i386 does not boot either - same
A RAID1+0 array with 4x36GB disks boots fine both amd64 and i386.
Right. If I create two slices, one 50G and one 1.3T and use the first
for /, /var etc. then the system will boot
need to
enter drive geometry manually but have no idea where to get that info
from, perhaps somebody knows where to look?
i386 does not boot either - same
A RAID1+0 array with 4x36GB disks boots fine both amd64 and i386.
So the logical drive size is a problem
Hi,
What am I doing wrong?
7-Beta3 vanilla install from CD, I let sysinstall do automatic
partitions and slices, then stops at F1 FreeBSD prompt and beeps.
Obviously it cannot find anything to boot from.
System is a SA6i RAID5-array with 6x300GB disks. Possibly I need to
enter drive
is a SA6i RAID5-array with 6x300GB disks. Possibly I need to
enter drive geometry manually but have no idea where to get that
info from, perhaps somebody knows where to look?
i386 does not boot either - same
A RAID1+0 array with 4x36GB disks boots fine both amd64 and i386.
Right. If I create
with 6x300GB disks. Possibly I need to
enter drive geometry manually but have no idea where to get that info
from, perhaps somebody knows where to look?
i386 does not boot either - same
A RAID1+0 array with 4x36GB disks boots fine both amd64 and i386.
Right. If I create two slices, one 50G and one
suggestions. I don't need this laptop for a few weeks,
so I'm open to just about any type of debugging folks could ask me to
do.
Are you running an amd64 build? I came across the same issue on my
Dell laptop and found the following code in acpi_ReqSleepState:
#if !defined(__i386__
Been spending some time setting up my new Lenovo T61 laptop.
7.0 ... just cvsupped and build world/kernel yesterday. Ports have
installed nicely, have xfce4, Firefox, Sylpheed, OpenOffice.org.
So far, the only snag I'm getting is suspending the laptop. Entering
zzz returns:
acpiconf: request
for a few weeks,
so I'm open to just about any type of debugging folks could ask me to
do.
Are you running an amd64 build? I came across the same issue on my
Dell laptop and found the following code in acpi_ReqSleepState:
#if !defined(__i386__)
/* This platform does not support acpi suspend/resume
Dear FreeBSD,
I have tried to install 6.2 and 7.1beta onto a new computer. The
installs seem to start up fine, whether via FTP or from an install disc1
CD, but during the loading of the binaries, the installs reliably
encounter a Signal 10 caught! That's bad! or the Checksum fails on
the
Hi all,
I just bought an Inspiron 1721 b/c I had a ridiculous deal.
Its
CPU:AMD Turion 64 x2 TL-64 (2.2GHz/1MB)
RAM:4GB pc25300 sodimm (2x2GB) (upgraded manually)
Screen: 17.0 wide screen (1920x1200)
VGA:ATI RADEON Xpress1270 256MB HyperMemory
HD: 320G (2x 160) 5400RPM SATA
Hi Josh and others
Has anybody been able to solve this problem yet?
I pulled in a friend who has a zillion years of experience with BSD and
was not able to solve the problem.
It looks like it is not even possible to start the X when the machine
has a monitor attched to it.
I installed
Roland Smith wrote:
Than they should run i386. You only _need_ (as opposed to nice to play
with :-) amd64 if you run out of address space on a typical workload.
What if you have more than 3Gb of RAM to play with... would you have to
use amd64 then?
Steve
On Wed, Oct 31, 2007 at 10:27:32AM +, Stephen Allen wrote:
Roland Smith wrote:
Than they should run i386. You only _need_ (as opposed to nice to play
with :-) amd64 if you run out of address space on a typical workload.
What if you have more than 3Gb of RAM to play with... would you have
Hi!
I just created an i386 chroot on an amd64 host (make TARGET=i386
TARGET_ARCH=i386 ...). The host is compiled with lib32 support.
I'm trying to chroot into the directory to install a port (ports dir is
nullfs_mount'ed):
chroot /path/to/chroot /bin/sh -c cd /usr/ports/my/port; make
monster# uname -a
FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30
18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64
monster# csup -h cvsup8.us.freebsd.org /usr/share/examples/cvsup/ports-supfile
Connected to 216.165.129.134
Updating collection ports-all/cvs
Checkout
On Thu, Nov 01, 2007 at 03:06:54AM +, Aryeh Friedman wrote:
monster# uname -a
FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30
18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64
monster# csup -h cvsup8.us.freebsd.org /usr/share/examples/cvsup/ports-supfile
On 11/1/07, Steve Kargl [EMAIL PROTECTED] wrote:
On Thu, Nov 01, 2007 at 03:06:54AM +, Aryeh Friedman wrote:
monster# uname -a
FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30
18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64
monster# csup -h cvsup8
On Mon, 2007-10-29 at 22:32 +, Tino Engel wrote:
Dear all,
Does anyone see any chance to get the nvidia display driver (with OpenGL
support) set up on amd64?
Or someone has even succeded?
The ports driver tell me they are only for i386, the downloaded driver from
nvidia stops
Hi,
I have seen that recently on the mailing list there has been a discussion on
running i386 FreeBSD binaries under an amd64 system. As far as I have been
able to read there does not appear to be anyway of achieving this except
though either a chroot/jail or vitalization. I think
On Tue, Oct 30, 2007 at 09:39:24AM +0200, David Naylor wrote:
Hi,
I have seen that recently on the mailing list there has been a discussion on
running i386 FreeBSD binaries under an amd64 system. As far as I have been
able to read there does not appear to be anyway of achieving this except
Yuri Pankov wrote:
On Mon, 2007-10-29 at 22:32 +, Tino Engel wrote:
Dear all,
Does anyone see any chance to get the nvidia display driver (with OpenGL
support) set up on amd64?
Or someone has even succeded?
The ports driver tell me they are only for i386, the downloaded driver from
FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #5: Wed Oct 24 18:14:31
EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MONSTER amd64
gnome 2.20.1
abiword will not start from menu or command line (no error messages
given)... the starting abiword window appears but after it completes
What version of VNC are you running.. ?
Anyone here tried Ultra VNC ?
Thanks
Hakan
http://dominor.com
On 10/28/07, Josh Carroll [EMAIL PROTECTED] wrote:
So VNC server will run, and I can connect to it from a VNC-client, but
the window manager fails to start correctly.
I am having
What version of VNC are you running.. ?
vnc-4.1.2_2 from ports. I wonder if this is related to it compiling
against ancient XFree86 source?
Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
vnc-4.1.2_2 from ports. I wonder if this is related to it compiling
against ancient XFree86 source?
The tightvnc port has the same problem, actually. Same message in the
vnc log, but also another:
X Error of failed request: BadValue (integer parameter out of range
for operation)
Major
Dear all,
Does anyone see any chance to get the nvidia display driver (with OpenGL
support) set up on amd64?
Or someone has even succeded?
The ports driver tell me they are only for i386, the downloaded driver from
nvidia stops with:
ld: Relocatable linking with relocations from format elf32
So VNC server will run, and I can connect to it from a VNC-client, but
the window manager fails to start correctly.
I am having the same problem. My vnc log looks similar:
*snip*
X Error of failed request: BadValue (integer parameter out of range
for operation)
Major opcode of failed
I am writing some demo code (for teaching C) and need to have the same
program run on a 32 bit machine and a 64 bit machine (showing that int's
are always word length)... I have 8-current amd64 how do I force it to
compile with 32 bit words?
___
freebsd
I am writing some demo code (for teaching C) and need to have the same
program run on a 32 bit machine and a 64 bit machine (showing that int's
are always word length)... I have 8-current amd64 how do I force it to
compile with 32 bit words?
Add the following to your gcc command line:
-m32
On Wed, 24 Oct 2007 16:49:24 -0400
Aryeh M. Friedman [EMAIL PROTECTED] wrote:
I am writing some demo code (for teaching C) ... showing that
int's are always word length
s/always/typically/
C has been around for a long time and there is always a counter-example
to any sweeping generalisation
RW wrote:
On Wed, 24 Oct 2007 16:49:24 -0400
Aryeh M. Friedman [EMAIL PROTECTED] wrote:
I am writing some demo code (for teaching C) ... showing that
int's are always word length
s/always/typically/
C has been around for a long time and there is always a counter-example
to any
On Wed, 24 Oct 2007 21:56:50 -0400
Aryeh M. Friedman [EMAIL PROTECTED] wrote:
RW wrote:
On Wed, 24 Oct 2007 16:49:24 -0400
Aryeh M. Friedman [EMAIL PROTECTED] wrote:
I am writing some demo code (for teaching C) ... showing that
int's are always word length
On Oct 24, 2007, at 8:56 PM, Aryeh M. Friedman wrote:
RW wrote:
On Wed, 24 Oct 2007 16:49:24 -0400
Aryeh M. Friedman [EMAIL PROTECTED] wrote:
I am writing some demo code (for teaching C) ... showing that
int's are always word length
s/always/typically/
C has been around for a long time
I experience if i
recall correctly were similar to the ones you outline in your log. Lisandro
Grullon
Date: Fri, 19 Oct 2007 14:19:58 +0200
From: [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Subject: Problem with VNC on AMD64
Hi
I have been using FreeBSD for several years now
Hi
I have been using FreeBSD for several years now on intel32. Now I
installed it on my new server which is a AMD64. Most things go well, but
I can't get a Window Manager working under VNC anymore. Here you find
the VNC log:
---
Xvnc Free
Trying to make a bootable CD, I did the following according to
FreeBSD doc:
#mkisofs -R -no-emul-boot -b /boot/cdboot -o /home/user/0S to
be burned /home/user/cdboot
And I got the message: uh, oh I can't find the boot image /boot/cdboot
Suggestions?
[EMAIL PROTECTED] wrote:
Trying to make a bootable CD, I did the following according to
FreeBSD doc:
Where does one find this FreeBSD doc?
#mkisofs -R -no-emul-boot -b /boot/cdboot -o /home/user/0S to
be burned /home/user/cdboot
And I got the message: uh, oh I
c++ -DDRIVER_TABLE_FILE=\/usr/local/share/cdrdao/drivers\ -O2
-fno-strict-aliasing -pipe -march=nocona -o cdrdao main.o ./libdao.a
../paranoia/libcdda_paranoia.a ../trackdb/libtrackdb.a
-L../scsilib/export -lscg -lschily -L/usr/local/lib -lmad -lm
-L/usr/local/lib -lvorbisfile -lvorbis -lm
On Tue, Oct 16, 2007 at 01:03:32PM +, Aryeh M. Friedman wrote:
c++ -DDRIVER_TABLE_FILE=\/usr/local/share/cdrdao/drivers\ -O2
-fno-strict-aliasing -pipe -march=nocona -o cdrdao main.o ./libdao.a
../paranoia/libcdda_paranoia.a ../trackdb/libtrackdb.a
-L../scsilib/export -lscg -lschily
Aryeh Friedman wrote:
Even though I know this is asking for it I want to test the new nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one) is src/nv-kernel.o is branded elf-i386-32 and
amd64 wants it branded elf-amd64-64. This file comes from them
On 10/11/07, Kris Kennaway [EMAIL PROTECTED] wrote:
Aryeh Friedman wrote:
Even though I know this is asking for it I want to test the new nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one) is src/nv-kernel.o is branded elf-i386-32 and
amd64
On Oct 11, 2007, at 1:34 AM, Aryeh Friedman wrote:
On 10/11/07, Kris Kennaway [EMAIL PROTECTED] wrote:
Aryeh Friedman wrote:
Even though I know this is asking for it I want to test the new
nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one
Aryeh Friedman wrote:
On 10/11/07, Kris Kennaway [EMAIL PROTECTED] wrote:
Aryeh Friedman wrote:
Even though I know this is asking for it I want to test the new nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one) is src/nv-kernel.o is branded elf
Aryeh Friedman wrote:
On 10/11/07, Kris Kennaway [EMAIL PROTECTED] wrote:
Aryeh Friedman wrote:
Even though I know this is asking for it I want to test the new nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one) is src/nv-kernel.o is branded elf
There are several kernel features that need to be implemented before an
amd64 nVidia driver will work - see
http://wiki.freebsd.org/NvidiaFeatureRequests for more info. nVidia do
want to create an amd64 driver, but they need the kernel work to be done
first.
I just sent nVidia an offer
Even though I know this is asking for it I want to test the new nVidia
driver on amd64 and the only issue with a hand compile (from nVidia's
tar not the ports one) is src/nv-kernel.o is branded elf-i386-32 and
amd64 wants it branded elf-amd64-64. This file comes from them as a
precompiled object
since 20 years of industry experience (15 with FreeBSD)
and reading hardware.txt did not give a clue on this.
What's confusing?
i386 is for 386 compatible processors - a 32-bit OS for 32-bit
processors, which is therefore limited to 2^32 bytes (4GiB) without the
PAE workaround.
amd64 is for AMD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
So, I did an SMP/i386 install. I cannot say I regret it since everything
runs absolutely smooth and fast here.
On the tecnical side (not practical) was it correct to give up 64 bit
processing?
This is a question to
On Friday 05 October 2007, Matthew Seaman wrote:
[EMAIL PROTECTED] wrote:
So, I did an SMP/i386 install. I cannot say I regret it since everything
runs absolutely smooth and fast here.
On the tecnical side (not practical) was it correct to give up 64 bit
processing?
This is a question
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as amd64-marcel-freebsd...(no debugging
symbols found)...
(gdb) r comments.db
On Oct 2, 2007, at 7:07 AM, Maxim Khitrov wrote:
On 10/2/07, Chad Leigh -- Shire. Net LLC [EMAIL PROTECTED] wrote:
Hi
In installing trac I ran across a segmentation fault in the initenv
command.
This seems to be the same problem as shown here:
copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as amd64-marcel-freebsd...(no debugging
symbols found)...
(gdb) r comments.db CREATE TABLE comments (page, name, email, url,
body);
Starting program: /usr/public/bin
) without the
PAE workaround.
amd64 is for AMD 64 compatible processors operated in 64-bit mode.
First of all there are several possible 64 bit intel like processors
to choose from for example unless one reads carefully ia64 looks like
what you want. Second of all in many peoples minds (including
well the procedure *ALMOST* worked turns out that sysinstall
clobbers any unmodified bsdlabels (bug?)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
hw.snd.verbose: 1
hw.snd.maxautovchans: 16
hw.snd.default_unit: 0
hw.snd.version: 2007061600/amd64
hw.snd.default_auto: 0
monster# ls /dev
acd0cuad0.lock mixer0 stdout ttyvb
acpidcons net sysmousettyvc
ad10
On 2007-09-30 07:24, Aryeh Friedman [EMAIL PROTECTED] wrote:
well the procedure *ALMOST* worked turns out that sysinstall
clobbers any unmodified bsdlabels (bug?)
Which 'procedure' would that be?
You haven't quoted anything from the previous messages, and your mailer
hasn't included an
On Sun, 30 Sep 2007 06:55:15 +
Aryeh Friedman [EMAIL PROTECTED] wrote:
Second of all in many peoples minds (including mine)
we are used to there being subtle diffs between AMD and intel for the
same class of processor thus would naturally think if it was lableb
amd64 it is for Advanced
1101 - 1200 of 2012 matches
Mail list logo
