Serious Problems with 64-bit OS'es

P

projectle

Guest
Ok, first off...

I recently got a custom build system, this MB, 3400+ FX proc. 2 1GB sticks of Kingston HyperX memory, 2 Maxtor 250GB SATA drives, 2 Maxtor 200GB IDE Drives, 2 Pioneer DVR-A06 DVD-RWs, nVidia GeForce 5950 Ultra... All wrapped up in a Koolance Liquid Cooled case...

When running any 32-bit operating system, everything runs just fine.
When running Windows XP 64, everything runs mostly fine.
When running any 64-bit Linux Distribution, everything goes up in smoke...
(Not literally)

When I try to install any Linux Distribution which has been compiled for 64-bit AMD processors, I get a blue screen, and several substantial errors (too many to write here)

All of it seems tied in with a "RIP Error!"

I am not entirely sure what this problem is, and I would like to check here before I go complaining to 4 different distributions that the screwed up in their compilation. Has anyone else seen this problem? If so, did you manage to fix it or have any idea what is causing it?

I find it a little unusual that any 32-bit Linux distribution runs flawlesly on this system... It is just the 64-bit versions. (And yes, I have validated the checksums in order to ensure that the Discs are not corrupt.)

Thank you for your assistance,
Tyson Edwards
 
Sort by date Sort by votes
I am not sure exactly what your problem with Linux -AMD64 OS is. What Linux is it ? To give you a perspective and as a test bed I have a 15GB hd partitioned (with Partition Magic) like this:
1: FS: FAT 32,Partition C: (HDA1) Windows 98 (1st edition) Total MBs=2110.1
2. (Extended) (no Partition) Total MBs=12715.5
3. FS: FAT 32,Partition D: (HDA5) Trial Windows XP AMD64 Total MBs=5412.5
4. FS:Reiserfs, HDA6 Linux SuSE v9.0 for AMD64 Total MBs=6628.4
5. FS: Linux Swap, HDA7 Linux Swap Total MBs=509.9

I like Partition Magic because the LEAST/MINORest HD error it will quit !
But if you dont have it you can still use the archaic Partitioner MS and Linux FDISK.
I preformat the HD in advance and write it down so I dont forget.
Unless you are new to Linux you should know that Linux can read and access FAT 32 Windows Partitions but not vice-versa. Item 2 (above) is automatically setup when you partition any HD with Windows. I am not sure which HDA it is, I dont remember. HDx where x =IDE channel."A" is primary master "B" is slave. My DVD ROM is on secondary master so it is listed as HDC. The number after HDA is logically recognized by Linux. HDA1 is the first Partition on the HD and it is also known to Windows as Partition C: I dont know what happened to HDA3 or HDA4 because they are not listed in Linux's FDISK but I assume they are accounted for.
As usual you always start with a clean virgin HD first then install the lowest/oldest Windows next. The last OS you install is Linux. If for some odd reason you cant boot with Linux after install then you have no other resort than to do the Rescue Floopy routine. Always create one BEFORE you exit install. If Linux "GRUB" or "LILO" fails then run in DOS MS fdisk /mbr. This will restore the original Windows boot. To reboot Linux use the floopy you just created.
All OSs above work ok except the trial version of Windows XP for AMD 64. The problems I have is not installation but with Drivers for sound, RAID and my specific printer. They are not available yet for this platform.
 
Upvote 0 Downvote
I've used Mandrake 9.2 for AMD64 (RC1) without any major problems. WinXP 64 seems to run fairly fine too, especially after the new nVIDIA drivers.
I tried to boot with a Gentoo LiveCD for AMD64 but it doesn't really work. Havn't giving it alot of thought yet but I'd like to try Gentoo 64.
But atleast 1 64 bit dist of Linux worked on my machine.
 
Upvote 0 Downvote
RIP could mean something entirely different here, but it's normally an
acronymn for router protocol. Are you connected to a LAN while you're
installing?

Could be some strange bug in the firmware for the network card that
only gets triggered from a 64 driver.
 
Upvote 0 Downvote
Back
Top