Re: [suse-amd64] Installing directly to SATA drive on Asus SK8N
No, you're trying the right thing. Have you tried not compiling the nvaudio driver at all and just make make install in the nvnet directory? That way you can avoid nvaudio and nvgart which ain't working anyway Martin On Sun, 2003-08-31 at 17:03, Phil Chapman wrote:
ok,
I'd already tried -mathlon -m64 and the -march still causes a problem. Taking out -mathlon gets past there but there are many compile errors.
Looking in the mobo manual though, the LAN is described as a
CK8 MAC+ Realtek RTL8201BL PHY
Is this nvidia?? I'm not so sure, so we might be trying the wrong thing anyway.
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hi,
Alright, I found the following in the GCC manual:
-m64 Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any i386 system. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits and generates code for AMD's x86-64 architecture.
First, simply try to add the -m64 parameter to the CFLAGS options and use "-march=athlon". If that doesn't work either, delete the -march parameter and use -m64 only.
Martin
On Sun, 2003-08-31 at 16:25, Phil Chapman wrote:
hmmm,
uname -m returns x86_64
uname -p returns unknown
I changed the CFLAGS to be -march=x86_64
but it gets an unknown value for march when doing the make.
tried -march=i686 and again it gets CPU does not cuppot x86_64 instruction set??
Any more ideas??
How can I tell if I'm in 64-bit mode?
Regards
Phil
Yes, the errors are actually coming from the nvnet pieces :( I just downloaded the drives from the asus site and they are exactly the same. I'll keep searching some of the nvidia sites, see if I can come up with anything, otherwise I'll just put in a standard nic. Thanks for your help!! Phil On Sun, 31 Aug 2003, Martin Jungowski wrote:
No, you're trying the right thing. Have you tried not compiling the nvaudio driver at all and just
make make install
in the nvnet directory? That way you can avoid nvaudio and nvgart which ain't working anyway
Martin
On Sun, 2003-08-31 at 17:03, Phil Chapman wrote:
ok,
I'd already tried -mathlon -m64 and the -march still causes a problem. Taking out -mathlon gets past there but there are many compile errors.
Looking in the mobo manual though, the LAN is described as a
CK8 MAC+ Realtek RTL8201BL PHY
Is this nvidia?? I'm not so sure, so we might be trying the wrong thing anyway.
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hi,
Alright, I found the following in the GCC manual:
-m64 Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any i386 system. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits and generates code for AMD's x86-64 architecture.
First, simply try to add the -m64 parameter to the CFLAGS options and use "-march=athlon". If that doesn't work either, delete the -march parameter and use -m64 only.
Martin
On Sun, 2003-08-31 at 16:25, Phil Chapman wrote:
hmmm,
uname -m returns x86_64
uname -p returns unknown
I changed the CFLAGS to be -march=x86_64
but it gets an unknown value for march when doing the make.
tried -march=i686 and again it gets CPU does not cuppot x86_64 instruction set??
Any more ideas??
How can I tell if I'm in 64-bit mode?
Regards
Phil
Hi, Anytime. I'll try to find out when these Beta drivers are going to be release and keep you up to date ;) FYI, since I'm using Rev 1.02, I also have to use an extra NIC so at least you're not alone ;) Martin On Sun, 2003-08-31 at 17:16, Phil Chapman wrote:
Yes,
the errors are actually coming from the nvnet pieces :( I just downloaded the drives from the asus site and they are exactly the same.
I'll keep searching some of the nvidia sites, see if I can come up with anything, otherwise I'll just put in a standard nic.
Thanks for your help!!
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
No, you're trying the right thing. Have you tried not compiling the nvaudio driver at all and just
make make install
in the nvnet directory? That way you can avoid nvaudio and nvgart which ain't working anyway
Martin
On Sun, 2003-08-31 at 17:03, Phil Chapman wrote:
ok,
I'd already tried -mathlon -m64 and the -march still causes a problem. Taking out -mathlon gets past there but there are many compile errors.
Looking in the mobo manual though, the LAN is described as a
CK8 MAC+ Realtek RTL8201BL PHY
Is this nvidia?? I'm not so sure, so we might be trying the wrong thing anyway.
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hi,
Alright, I found the following in the GCC manual:
-m64 Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any i386 system. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits and generates code for AMD's x86-64 architecture.
First, simply try to add the -m64 parameter to the CFLAGS options and use "-march=athlon". If that doesn't work either, delete the -march parameter and use -m64 only.
Martin
On Sun, 2003-08-31 at 16:25, Phil Chapman wrote:
hmmm,
uname -m returns x86_64
uname -p returns unknown
I changed the CFLAGS to be -march=x86_64
but it gets an unknown value for march when doing the make.
tried -march=i686 and again it gets CPU does not cuppot x86_64 instruction set??
Any more ideas??
How can I tell if I'm in 64-bit mode?
Regards
Phil
participants (2)
-
Martin Jungowski -
Phil Chapman