Re: AMD64 SK8N - Thanks

From: William Strider (striderw_at_aragorn.net)
Date: 01/26/04


Date: Mon, 26 Jan 2004 06:49:23 -0600

Thank you all for replying! My responses are under each person's
contribution.

Al Hawley

Try putting the IPaddress(es) of your DNS in /etc/resolv.conf like this:
nameserver <DNS IPaddress>
#repeat for each DNS addr your ISP provides...

*** I've done this but it doesn't help, whether I configure the onboard
(nVIDIA?) LAN port or my Linksys LNE100TX. The Linksys worked fine on
my previous PC, a Dell Dimension B733r.

I put these at the beginning of the file. It works for me.
I'll bet that there is a warning message during startup (hit F2 to
watch)
and in /var/log/messages that complains about a router (possibly a NIC)
that does not support IPv6...

*** Yes, I have a messeage about an invalid parameter for the IPV6
module.

David Speight

I had many problems as well top begin with.
I am ruunnning an Athlon 64 on a Giga-byte K8N Pro.
It was anything but stable and I was lucky to get it to boot 2-3 times
with no lock ups.
The problem was solved when I flashed the ROM with an update.
It looks like the nVidia nForce3 and the AWARD BIOS.
Funny thing is the SuSE 8.2 (32 bit) was as stable as a rock.
Now SuSE 9.0 (Athlon-64) is doing great.

*** I've updated my BIOS to 1004 this morning but it makes no
difference. It did clobber my settings for X and resulted in YaST
recognizing the RAID controller (but not the drive connected to it) and
treating my NIC and sound card as new hardware.

Don't give up hope.
Thy theory is that the nForse3 150 chip has problems and the BIOS
manufacturers had to put out a patch.
The fact that they are coming out with a revised 150 and the new 250
chip so far leads me to believe this.

As far as the NIC, you might try a D-Link 530+.

My experience is that SuSE is a little week in NIC support, Red Hat on
sound & Mandrake on Video.

Also on the internet connection can you give me more details?
It could just be that if you are using a router, its address is not set
up as your gateway.

*** Tried that too but no help.

Also did you use acpi=off apic?

*** Same result!

Kevin Nathan

> Thank you, SuSE, for bringing out an OS package that I cannot use
> and that you will not help me to use.

That's not good -- SUSE is going to take bad hits if this is how they
handle the 64bit crowd. Did they just refuse to help you, or did you
not like the answer? . . .

*** They took the view that my problems didn't come under the heading
of 'installation support'.

Are you sure you've used Linux for three years? In all that time,
you've never learned that cutting-edge hardware takes time to be
supported in Linux? (Because, of course, manufacturers don't support
Linux and you have to wait for people to get their own equipment and
reverse-engineer it -- and then it has to match what you bought --
you were obviously aware of part of this problem based on statements
you made in your post.)

*** In normal circumstances, I'd agree with you. However, SuSE
advertised an OS for the new CPU, which I'd have thought would include
mobos on which that CPU would be mounted. In the UK, where I live, the
Asus SK8N was the only mobo used by firms supplying the FX-51 CPU in
their systems.

Give it time, it'll get there. I'm not planning on a 64-bit machine
for at least two years. There is no real need for one right now
(for me, anyway), and there are virtually no 64 bit programs out
there yet. In two years, the 64-bit landscape will have improved. Too
bad you just didn't get a screaming 32-bit box to tide you over till
then . . . :-)

*** I thought I was well on the way to using Linux for most things.
Microsoft's business practices, its cosy relationship to the RIAA and
the US government, its desire to control my PC and my data - all these
are reasons for my wish to do my serious work using an OS that doesn't
do things behind my back. Funds don't permit me to buy PCs often (I'm
retired), so I thought I'd get a system that would cope with software
over the next decade or so. It was a judgement call and I got it wrong
because I trusted a commercial company to do better than the Beast of
Redmond!

sleazy

;snip:
> The problem was solved when I flashed the ROM with an update.
> It looks like the nVidia nForce3 and the AWARD BIOS.
> Funny thing is the SuSE 8.2 (32 bit) was as stable as a rock.
> Now SuSE 9.0 (Athlon-64) is doing great.

Which BIOS update did you use? 1004? Im at my wits end too!

(yeah, I know its a short trip)

David Speight

sleazy wrote:
> On Sat, 24 Jan 2004 14:27:03 -0500, David Speight wrote:
> ;snip:
>
>>The problem was solved when I flashed the ROM with an update.
>>It looks like the nVidia nForce3 and the AWARD BIOS.
>>Funny thing is the SuSE 8.2 (32 bit) was as stable as a rock.
>>Now SuSE 9.0 (Athlon-64) is doing great.
>
>
> Which BIOS update did you use? 1004? Im at my wits end too!
>
> (yeah, I know its a short trip)

The latest on the giga-byte we page listed for my motherboard at the
time F9, they now have a F10 but I haven't bothered with it yet.

Synchrodude

The Nforce3 chip set is still under going major refinments. That is why
when
my computer blew up I just upgraded to the fastest 32 bit stuff. I am
running a Nforce2 chip set and from everything I have read through on
the
onboard lan chips are a pain in the ass to get going for both the
Nforce2
and Nforce3 boards. The good thing is that Nvidia is a big player with
Linux so hopfully later down the road the Nforce chip sets will have
better
support from different distro's out there. I was lucky and was using a
kingston lan card and put that back in my system to get back online so I
didn't have to go through and rebuilt my kernel for the onboard lan.

*** It looks as though 'wait and see' is the best bet for me for now. I
shall leave SuSE 9.0 for AMD64 on my system in the hope that it may
become usable eventually. Without Internet access, though, updating it
to a usable state may be difficult.

William Strider



Relevant Pages

  • Re: AMD64 SK8N - Thanks
    ... > that does not support IPv6... ... > Are you sure you've used Linux for three years? ... > The Nforce3 chip set is still under going major refinments. ... > didn't have to go through and rebuilt my kernel for the onboard lan. ...
    (alt.os.linux.suse)
  • Re: Breaking 137GB Barrier 440BX
    ... older computer and scratching my head a bit about the 48-bit LBA ... support in the BIOS and patched OS's that will ... BIOS available, but I had already flashed the last released BIOS ... selected -- either win or LILO in the beginning of a Linux part. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Continuous beeping and Machine_check_exception STOP:A 0X000000
    ... FDD Connections 􀂊 1 FDD connection, allows connection of 1 FDD device ... I will also try to make and boot the Linux CD but I am not at> all ... I have tried resetting the bios and hitting f12 while>>> booting. ... add support as time ...
    (microsoft.public.windowsxp.general)
  • Re: Aktuelle Linux Distribution fuer FSC Esprimo P5615 gesucht
    ... SUSE Linux Enterprise Desktop 10 ... man beim Installieren hängen bleibt weil er auf irgendwelche IRQs wartet. ... Zudem wird der Bugfix wohl bald ins BIOS eingebaut werden, ... bei FSC bin und mein Job genau Linux auf den Desktops ist. ...
    (de.comp.os.unix.linux.misc)
  • Re: Continuous beeping and Machine_check_exception STOP:A 0X000000
    ... FDD Connections 􀂊 1 FDD connection, allows connection of 1 FDD device ... I will also try to make and boot the Linux CD but I am not at all ... I have tried resetting the bios and hitting f12 while booting. ... add support as time ...
    (microsoft.public.windowsxp.general)