You are not logged in.

#1 2013-08-09 06:46:12

xintron
Member
From: Sweden
Registered: 2008-09-25
Posts: 32
Website

[Solved] New computer, old install

I got my new computer parts this week, built the machine and put in my old
disks (with Arch Linux + Win XP using syslinux for dualboot). Now I'm having
problems booting the existing OS.

Symptoms When I booted the first couple of times it just froze when
trying to access the root disk (both by UUID and /dev/sdx1). I booted the arch
install and modified the kernel to run the autodetect hook which seems to have
solved the issue with not finding the disks. The current problem is that it
freezes a while into the boot process (mounting the disks but it stops at
different points each time so it doesn't seem to be a specific disk that is the
cause). Mounting them manually (and running checks) worked with the arch
installer so the disks are working accordingly.

I then added debugging to the kernel line to get some more info and all of the
sudden I saw issues about the CPU (don't remember the problem exactly and at
work atm).

Hardware changes
I went from a quad core AMD CPU, 4GB RAM and an older Nvidia card. The new
setup is a new i7 4770, 32GB RAM (lower timings) and a Nvidia GTX 770.

My partitiontable is MBR so might this be a problem (I'm guessing it shouldn't
because I'm able to mount the disks during boot and if this was the issue no
partitions should be mounted)?


If possible I would like to resolve this without reinstalling the OS, otherwise
I'll take the extra time to get me a new disk, setup RAID5 and fix the current
mess of partitions (as well ass migrating from MBR -> GPT).

Is there any problems with UEFI I should be aware of if going for Linux +
Win7/8 or is it just to install them as before and then have syslinux/grub
handle it?

-- Solution --
The problem was with the motherboard. When the kernel set the mode it switched to send output to the motherboard instead of the GPU which just left the screen in a frozen state. Adding "nomodeset" to the kernel line solved the issue but I also disabled the motherboard internal GPU for now.

Last edited by xintron (2013-08-10 13:15:55)

Offline

Board footer

Powered by FluxBB