Some bits of information that may help.
On a project taking one drive from Atom system into MSI U100.
I booted external usb dvd.
boot: linux repair nonet
this will run a repair without network. If you try a install or repair without the nonet, it will show a blue screeen with a bucnh of cryptic letters and freeze.
in my case i was able to run the upgrade option. I also created a new mbr since the old system was ide and the U100 is SATA. I wanted to make sure grup pointed to a sata drive instead of ide.
ref:
http://translate.google.com/translate?hl=en&sl=fr&u=http://www.microlinux.fr/article.php3%3Fid_article%3D47&ei=gMWdSaWrNZm0sQPL-MjLCQ&sa=X&oi=translate&resnum=1&ct=result&prev=/search%3Fq%3DInstaller%2BLinux%2Bsur%2Bun%2Bultra-portable%2BMSI%2BWind%26hl%3Den%26client%3Dfirefox-a%26rls%3Dorg.mozilla:en-US:official%26hs%3DEla
Realtek driver is on above link. the env proxy had to be set. leaving it blank would cause yum to fail.
also turned iptables off, but not sure if that was needed.
Ubuntu is a PITA (Pain in the Ass) when it comes to graphic cards…. wow, i have wasted soooooo much time fixing and helping others fix graphic problems with Ubuntu…. They just havent figured out the video thing yet…. anyway….here are some fixes regarding graphics in Ubuntu….
You know, when you try to set a resolution for your kicking video card… and it only displays 800×400 and all your configuration buttons are off the screen, so you have to guess what button is highlighted….yeah thats the problem!
For the first example i will use an Nvidia GeForce 7800GT PCIexpress
Goto Nvidia, download most current driver
Boot into recovery mode
sh NVIDIA blah blah blah
overide all stupid warnings
ok to install open GL
exit and reboot
all is as it should be
http://www.komando.com/myvideo/
http://www.pcdecrapifier.com/home
This will remove all the junk software that comes with store purchased PC’s
run “chmod a+x xstartup” and “chmod a+x xinitrc”
(located at /root/.vnc/xstartup and /etc/X11/xinit/xinitrc).
A great site to find out why that process is running on your system and what it is doing to your system.
http://www.processlibrary.com/
make sure you install grub on the windows drive, normally this would be sda.
don’t install on the Linux drive, or windows will not boot with grub.
This is assuming you have windows on your first drive and installing linux on the second.
ls /dev/disk/by-uuid/ -alh
total 0
drwxr-xr-x 2 root root 100 2006-10-19 13:32 .
drwxr-xr-x 5 root root 100 2006-10-19 13:32 ..
lrwxrwxrwx 1 root root 10 2006-10-19 13:32 77755aaf-f843-424c-aabd-46d52cc05d5c -> ../../hda2
lrwxrwxrwx 1 root root 10 2006-10-19 13:32 8038788838787F4A -> ../../hda1
lrwxrwxrwx 1 root root 10 2006-10-19 13:32 ba8e5cfb-12fb-4601-b5ff-2f2787c69cb3 -> ../../hda5
this way you can tie back the sda to uuid.
example
vol_id -u /dev/sda1
or for more information use
vol_id /dev/sda1
very handy if you have ubuntu and the fstab is using uuid
it is more robust… i am learning to hate that word.
ref:http://ubuntuforums.org/showthread.php?t=223182&highlight=uuid&page=2