Hi, You'll be glad to hear that even though I did not have that problem, I seem to have found the glitch. The nvnet driver does not need a CPU detection, neither does the nvgart driver. The nvaudio does though, hence you can find the following in the nvaudio/Makefile: TARGET_CPU ?= $(shell uname -m) At this point, there is one thing I am not 100% sure of. There are two uname parameters to determine the CPU target and/or architecture: -m and -p. I remember, that one of'em returns "unknown" in Long Mode (64-bit mode) and the other returns "x86_64" Given your error message, I'd have to say it's the -m parameter that returns "unknown", since the target CPU "unknown" clearly does not support the x86_64 instruction set. But to be 100% sure, you'll have to test that on your SuSE yourself, right now I am not running SuSE 8.2/AMD64 so I can't help you with that. If I am correct and "uname -m" returns "unknown" then one simple change in the Makefile is going to solve your problem. Look for the CFLAGS option which should read like this: CFLAGS= -D__KERNEL__ $(ARCHDEFS) -I$(SYSINCLUDE) -Wall -Wstrict-prototypes \ -O -fno-strict-aliasing -mpreferred-stack-boundary=2 \ -march=$(TARGET_CPU) $(ALIGN) -DMODULE Change it to CFLAGS= -D__KERNEL__ $(ARCHDEFS) -I$(SYSINCLUDE) -Wall -Wstrict-prototypes \ -O -fno-strict-aliasing -mpreferred-stack-boundary=2 \ -march=x86_64 $(ALIGN) -DMODULE The important parameter is "-march", since uname -m returns a unknown architecture, it's up to you to force him to compile it for x86_64 so it'll support the x86_64 instruction set. If you do that, you should also edit the nvnet/Makefile and change the CFLAGS option from "-march=i386" to "-march=x86_64" But I might be also wrong and -p instead of -m might return unknown, in that case and if the above doesn't work, you'll have to change it to "-march=i686". I don't know whether that is going to work though, installing a 32-bit driver on a 64-bit OS might cause some big big trouble. Tell me how it went, I'm pretty sure that -m returns "unknown" but that you're gonna have to find out by yourself. If that ain't working as well (neither x86_64 nor i686) then you can always skip the nvaudio driver and just install the nvnet driver - it's always worth a shot if everything else fails. Martin On Sun, 2003-08-31 at 15:27, Phil Chapman wrote:
Martin,
did you have to change the Makefile to get the nvidia drivers compiled ??
I get
CC1 : error : CPU you selected does not support the x86-64 instruction set
I presume it's just the make options??
Thanks
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hi,
Alright, with 1.03 it should be working just fine. Download this driver:
http://download.nvidia.com/XFree86/nforce/1.0-0261/NVIDIA_nforce-1.0-0261.ta...
compile and install it. There's a file named "ReleaseNotes.html" in that package once you've untared it, follow the instructions given in that file. When everything's installed, loading the nvnet module via "modprobe nvnet" should solve your problem, just give it a shot. If it still ain't working, then you might just have to wait until these guys launch new drivers also supporting the nForce3 chipset.
Also, you should get ALSA 0.9.6 (www.alsa-project.org), you need alsa-driver, alsa-lib and alsa-utils. Install it, load soundcore support via modprobe (or insmod, whatever) then load the module "snd-intel8x0" that's the module that'll let you use the onBoard soundcard ;)
Martin
On Sun, 2003-08-31 at 02:01, Phil Chapman wrote:
sorry, wasn't thinking straight. Working on another box at the same time :) I was thinking of the BIOS. doh
It's a 1.03 revn board.
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hi,
The revision is right between the first blue RAM slot and the CPU socket, take a look at this picture, it may make finding it easier for you:
http://www.planet3dnow.de/artikel/hardware/opteronlinux/images/rev.jpg
and what is that 08.00.09, where'd you find that?
Martin
On Sun, 2003-08-31 at 01:15, Phil Chapman wrote:
hmmm,
all I can see is that it is revision 08.00.09, date 06/25/03
I don't see 1.02 or 1.03 anywhere ??
Regards
Phil
On Sun, 31 Aug 2003, Martin Jungowski wrote:
Hey Phil,
Whether the onBoard NIC is going to work or not depends on the revision of the mainboard. We got two of'em for testing and debugging, Rev. 1.02 is what I'm using right now and Rev 1.03 which another of our hardware testers is going to use starting next week (also getting a new AMD CPU :)).
I've had no trouble activating it on 1.03, what drivers are you using? We got Beta drivers from nVidia which seem to work just fine, however I am not allowed to give that driver away and it's not yet available to public :( However I've had a very similar problem with 1.02: I's able to load the module and I was also able to ping my server and several websites. I was not able to ssh to my server or to load any of the websites in any webbrowser. No trouble whatsoever with 1.03, what Revision do you have? You should have 1.03 since 1.02 wasn't available to public either and is still a prototype.
SuSE 8.2/AMD64 does not have the proper driver for the onBoard NIC yet, you'd have to use the nVidia driver. But first, could you be so kind and tell me what revision of the SK8N you have, 1.02 or 1.03? What version is your BIOS? Maybe there's something we can do about that onBoard NIC ;)
Martin
On Sun, 2003-08-31 at 00:47, Phil Chapman wrote: > Hi Martin, > > thanks for the tips. I've just installed it on an 80Gb WD. No problems > except for the network. Have you managed to get the on-board LAN working? > > It seemed to detect it during install, but then failed when doing it's > test connect :( > > Any ideas? At this stage I was just about to put in a different nic. > > It seems like a great board though!!! > > Thanks > > Phil > > > > On Sun, 31 Aug 2003, Martin Jungowski wrote: > > > Hi, > > > > You're lucky cause I got that exact same mainboard & CPU and I've been > > running SuSE x86-64 for a couple of weeks now ;) > > There are Drivers available for this S-ATA controller but I haven't > > tested them yet: > > > > http://www.busybox.net/pdc-ultra-1.00.0.10.tgz > > > > It should be working though, give it a shot. However I'd suggest you > > install SuSE x86-64 on a P-ATA drive connected to the onBoard onChipset > > IDE-Controller. Don't forget to enable UDMA and 32-bit mode for the > > harddrive afterwards: > > > > hdparm -d1 -c1 /dev/hda > > > > Note that this will only work with the SuSE default kernel 2.4.19 but > > not with any other self compiled kernel yet. Apparantly, SuSE updated > > the IDE-driver in that specific kernel and those patches are not part of > > 2.6 yet. > > > > Martin > > > > > > > > On Sat, 2003-08-30 at 20:20, Phil Chapman wrote: > > > Hi, > > > > > > just subscribed to the list. I got an opteron 144 on an Asus SK8N mobo > > > this week with a 120Gb seagate SATA drive. > > > > > > Can SuSE 8.2 be installed directly to the drive ? I can't get it to > > > recognise it at all, but am not sure which drivers to use? Or should I > > > just install to a default IDE drive and use the SATA drive seperately? > > > > > > Thanks for any help > > > > > > Phil Chapman > > > > > >