"Booting to init 2 still started X and if I killed X, it would restart... I had to kill gdm and that crashed X without restarting. Then I could finally install the Nvidia video card driver."

Just a note, but you can start up in single user mode, and X won't start. I think the nVidia installer gives a warning message or two, but these haven't given me any problems so far.

Steve,

I actually tried that in single user mode, but I didn't want to take any chances when it gave me that warning. Killing gdm worked quite well, though. Back to the 2 problems I was having...

The internet still isn't responding all that well. I was able to use other things online and on the network without any hesitation, so I think it might just be another setting that I need to change... it does seem slightly better with the IPv6 disabled.

Installing 32-bit firefox, I did not complete last night. I was doing several things at once, and midway through it messed up my XOrg settings or something with the Nvidia drivers. I'll probably try again tonight. The problem is that I don't know anything about chroot, so I need to understand that probably rather than just following step by step instructions.

Again, I will keep you informed.

The utility chroot helps you setup another root instead of using your setup that could damage your configuration using a certain program. chroot is also used to minimize hacker attack and to separate multiple installations. Apache has a chroot module that can be setup to automatically create its own chroot, so you do not have to.

In the BIOS, you may need to disable hardware firewall.

My comments are not over the top. Not a lot of people do not understand that ECC memory is required with multiple processors.

Flash player plug-in can be compiled and it may be compiled with -m64 switch (probably with some editing of the code). Adobe has information how to compile their code which is the same as compiling libraries. Make sure before compiling that you uncomment ALSA in the code and comment the line for OSS to disable OSS. You could compile with both OSS and ALSA. With the some extensive patching to the Flash player plug-in it could actually be better than Windows and MAC. I can not find the link for it, so Adobe could have took it off.

knappster - congrats on the new system. Personally I think you made the right choice by going with AMD over Intel (I use both, but as JimBass mentioned, on price, power, and heat, AMD wins).

Installing Firefox should be relatively straightforward. To my knowledge there is no official 64 bit version, but going with the 32 bit version works just fine. Lastly, Flash 9 for Linux might be of interest/use. Have fun

I have an interesting story to tell about my chroot experience. I followed the directions in the link above. I tried first to do an apt-get install mozilla-firefox, and it went ahead and installed everything. When I tried to run it, it still ran the 64-bit version of Iceweasel . I downloaded the firefox tar package and tried:
and Iceweasel still came up!

Now, if I leave out the portion, and just run then it loads the 32-bit version of firefox! Is there something that I am doing wrong or am incorrectly assuming? It doesn't matter THAT much, but it seems very strange.

I did, however, get JRE and flash plugins installed on that 32-bit version, which I am happy about

I installed firefox in wine as well, and it would run, but had no internet connectivity. Any thoughts on why that might be?

Lastly, can anybody link me a good tutorial on samba... mostly basics... server and client stuff, sharing folders, browsing folders, mounting folders. Thanks

To make sure programs run reliable and predictable, include /bin/bash when using chroot. You do not have to follow the line by line of the tutorial. You could have placed the root directory some where else and name the root directory debian_32bit or debian-32bit. Also you will have to run scripts that sets environmental variables, so programs like JAVA and many others can run correctly in the chroot setup. What I am trying to explain is chroot just makes another Linux installation and should be treated as one. One problem using two separate machine codes is playing sounds.

Java can be recompiled for your machine, so you do not have to do the chroot trick.

Correction, Adobe has provided an API called flashsupport for the Linux community to expand Flash. The following is the link that I have been looking for.
http://labs.adobe.com/wiki/index.php...port_for_Linux

Nothing is better than reading through the man pages of smb.conf. First, I suggest planning what you want and then read through the pages for smb.conf. One tip is change security to share to test your configuration.

knappster,
Congrats on the new system.
Judging by the number of views your thread has received you are not the only one interested in a new system's hardware support in Linux.

Just wanting to give everyone an update. As far as hardware is concerned, this machine has been working very well. I believe that the onboard NIC is having some trouble communicating with my DNS. I have ordered a PCI NIC to see if it solves the problem. That is the only complaint that I really have

Thanks to all those that helped me build this machine

Did you get the Samsung SH-S183L to work in Linux. I am thinking of buying this DVD burner along with a Seagate Sata HDD

I actually ended up getting the Pioneer DVR-111D instead. I don't see any reason why that samsung would not work, though. Somebody has to have tried it by now...

Monsieur Knappster...

This has been a great forum thread. I designed my system in part on the basis of this on-going discussion. (It boots and mostl works! Details on request... ) Have you resolved the DNS, NIC issue? Is it the on-board NIC or openSUSE 10.2 that is the source of the problem?

Thanks.

--Eric

--------
OpenSuse 10.2 System:
abit KN9 nVidia NF4 Ultra; AMD Dual-Core Athlon 64 X2 4600+ (65W)
CORSAIR XMS2 (2 x 1GB) 240-Pin SDRAM DDR2 800 (PC2 6400)
XFX GeForce 7600GT Fatal1ty (passive cooling); M-Audio Revolution 5.1 sound card
Western Digital 7200 rpm SATA drives: 80GB, 160GB; Plextor 716 DVD burner; Toshiba CD/DVD reader
Enermax Liberty 500W power supply
---------

Eric,

I am sorry to say that I have not discovered the source of the problem. I have determined that it is not the NIC, however. I currently have the onboard NIC disabled in BIOS and am using a cheapo PCI card. Here's the link to my last post on a thread where I was trying to figure it out:

http://www.linuxquestions.org/questi...47#post2650147

I would love to know what the cause is. It seems worse at peak hours, but only on this system... I have 3 other computers that have no problems... I believe it is definitely software related, because I think I tried Knoppix on the same machine with no DNS problems. But you're using OpenSUSE and I'm using Debian Etch, so it's not the flavor of Linux. It's very puzzling.

Bummer... I was hoping that you had resolved the DNS problem.

We may be seeing symptoms of the same problem. In my case I noticed that after some time DNS lookups would fail. However I could use IP addressing to connect to other hosts. As you have pointed out in you other thread, this is not a DNS server problem. By virtue of being able to connect via IP address to another host, we can rule out hardware failure to some degree. I agree, this _feels_ like a software/driver problem. In my case, rebooting cleared the problem. Hmmm. More when I know it. (I think it will may be more appropriate for me to follow up with any resolutions on the other thread.)

Thanks.

--Eric

Hi Electro,

In http://www.linuxquestions.org/questi...32#post2639132 you stated:


I'm setting up a system and was having problems with booting Fedora
Core 7 and am looking for different possibilities of what could be the
problem. See my ongoing thread at
http://forums.fedoraforum.org/showth...5&page=1&pp=15

Does the type of memory I have indicated in that first post seem to you problematic with that processor?

Thanks for your time.
bgoodr

With multiple processors perhaps, but not with a single multicore processor. I have been running dual-core with non-ECC RAM for a couple of years now, and it has been by far the most stable computer I have ever had the pleasure of owning. Do not confuse multi-core with multi-processor.