Page 1 of 1

i7 2600 "Series 2 chipset" CAN'T GET THROUGH INSTA

PostPosted: Sat May 07, 2011 10:42 am
by Pynk Global
Hi All,

New hardware and new install and I just can't complete install.

NOTE: 2ND Gen i7 Processor. (Is quite different to 1st Gen i7)

Processor i7 2600 (2nd version overclocking model) http://ark.intel.com/Product.aspx?id=52213
MSI G31TM-P35 Motherboard http://www.msi.com/product/mb/H61MU-E35--B3-.html
Sata 250 gig hdd
Single 4gig Ram

Have tried many cd burn and many CD Rom.
No issue install on i3 and i5 model.

Have tried all of the following.
VICIBOX
3.0.6 32 bit.
3.0.9 32 and 64 bit
3.1.9 32 and 64 bit

Stopping at all different areas.

sometimes get through os-install and when reboot get black screen on server monitor but can still ssh in, after I run zypper update I cant ssh in after.
Other times get to 35% of starting screen kernal update and hangs.
Other times get through kernal update and hangs on next screen

I hope is not a compatibility issue or I am way out of pocket when I thought I was doing a killer machine.

Any Help appreciated.

I am still tinkering and will post more info or errors when I get them. For now just asking if anyone knows or has same issues.

PostPosted: Sat May 07, 2011 11:03 am
by jlamconsulting
Try the 3.1.7 I had some issues with kernel hang on the 3.1.9 redux. Or there is the scratch install for Ubuntu http://wiki.vicidial.org/index.php/VICI:UbuntuInstall or GoAutoDial CentOS

32 bit or 64 bit

PostPosted: Sat May 07, 2011 11:23 am
by Pynk Global
I'll give 3.1.7 a shot and post back before I try the others.
Would you recommend 32 or 64 Bit???
I am trying something else out at the moment. Will feedback if anything worth mentioning.

3.1.7 went further but still no good

PostPosted: Sat May 07, 2011 2:05 pm
by Pynk Global
Vicibox 3.1.7 went further but still no good
Got through to reboot after os-install. past local selection and log in. But kicked my usb keyboard off (PS2 still worked) But lost internet.
I went in Yast lan and it duplicated my network settings ( I have 2 x Nic and now at 4 Nic)
The ones that are working are on the bottom and seemsd to be using the duplicates Lan. Cant edit them (Grayed option).

Anyway any advise appreciated. Just going to give goautodial a go for now but not my preference.

PostPosted: Sat May 07, 2011 4:11 pm
by jlamconsulting
You could try deleting the 2 extra nics in Yast then hit back and let it find the nics again. 64 bit for database if you are clustering or 32 bit for all on one

PostPosted: Sun May 08, 2011 12:30 am
by williamconley
You should definitely NEVER get the "Latest Greatest" and then pop Linux on it before drivers have been created. And when installing on a custom .iso, be sure the drivers have been universally available long enough to get into the various distros.

that being said:

First try GoAutoDial (while praying). Then consider a scratch install. Find out if there are appropriate drivers for Ubuntu, OpenSuSE, CentOS, Debian ... Gentoo ... it's possible to scratch install Vicidial on many OSs, but you need to be able to have a full installation of an OS upon which to build.

Since they are all free, a valid method would be to download the .iso for each and fire it up until one actually installs all the way.

You need to stay away from "Desktop" os's, and stick with the Server versions, though (if you can). Preferably "Long Term Service" or "LTS" which at least Ubuntu has (which means they'll be providing updates to that OS for several years).

jlamconsulting Cant delete Nic in yast

PostPosted: Sun May 08, 2011 12:57 am
by Pynk Global
When it duplicated the 2 NIC, Delete, Edit is Grey out so cant delete so stuck on that.

William, Honestly was know to stay away (Stupid me)
But as I have build several i3 and i5 last gen, assumed may be ok (And no other processors avail.

Here is base feedback on new chipset.
The enhanced Video in 2nd gen is definately issue on some of the distro I tried. VGA Blank out a certain points.
Mortherboard is also much smarter (Smarter meaning Dumber) Bios has a LOT of extra options (and not just over clocking)
Tried Goautodial and Unbuntu direct and although it all looks good at start, Ends up loosing the Hard drive during the install (Weird).

No Doubt is above Linux for now. But did install windows for a test (10 min install from start) Still trying but assume may be lost. Looks like a agent is going to get a hot hot agent machine.

Guess is a warning to others and maybe notice that the advanced community may want to look into it.

Will post is any additional info

Possibe solution

PostPosted: Sun May 08, 2011 1:07 am
by Pynk Global
Over my experience level but decided to share.

Someone having a similar issue (Not vicidial related)
"Not sure if related to My other issues."

Just replaced my AMD Phenom II X2 550 + AMD 790GX board with an Intel i7-2600 CPU + Intel H67 chipset motherboard.

Built a new kernel (2.6.38), and done all that stuff to get Linux back up and running, and Virtualbox 4.0.4 working.

Linux VMs work just fine (CentOS, etc.). However, my XP VMs are inoperable. They just freeze during the bootup process, and don't come back. I can, however, boot them up in "Safe Mode".

Anyone running the latest/greatest new Intel chip, + Virtualbox, and running into this trouble with WindowsXP VMs specifically?

I've even done an Acronis "universal" restore of a VM backup, to no avail. Still get the freezing during bootup issue.

Oh when I go to poweroff the VM, this is what I get:

Code: Select all Expand viewCollapse view
root@linuxbox:~# VBoxManage controlvm "XP_Virt" poweroff
0%...10%...



And VBoxManage just sits there and hangs. Eventually I have to go in and manually kill the Linux process that is associated with it.

Not seeing anything in the bugtracker yet, but as this is a mixed Windows/Linux thing, I haven't a clue where to start in diagnosing. Don't know whether this issue belongs in the Windows forum (as its a Windows guest), or in the Linux host forum (as its a Linux host/hypervisor).

SOLUTION

Ended up replacing linux kernel 2.6.38 with 2.6.38.2 (just released the other day!). My error log (kernel messages) basically was matching what was in the 2.6.38.2 changelog. So problem solved :). Seemed to be a Sandy Bridge-specific issue with race conditions, and nothing to do specifically with the Virtualbox code.

PostPosted: Sun May 08, 2011 2:00 am
by williamconley
Have you tried turning off all the goodies in bios? (anything cool and new can usually be shut off ...)

Update

PostPosted: Sun May 08, 2011 3:32 am
by Pynk Global
I have done a bit of tinker in the bios. Lot of stuff I dont quite understand but still looking through installs.

I had hdd on sata 5 port on motherboard, so swapped to sata 1 port and got a successful goautodial install.
Problem, as I have 2 NIC (Public and private) I am used to single Gateway (on vicibox) which gateway is set to the public gateway. with IP is both public and private.
Been a while since I used go autodial and has 2 x Gateway. Can only get the private ip online. Tried placing both public and private gateway in the public gateway option.
Any ideas on that.

Also tried ubuntu install and still cant get the hdd detected, But may have a solution I will try.

NIC settings for now would help me out

Nic 1 192.168.1.9
255.255.255.0
Gateway 192.168.1.2 (Not needed in vicibox just usually place public gateway)

NIC 2

122.52.xxx.x
255.255.255.224
Gateway: 122.52.xxx.1

PostPosted: Sun May 08, 2011 4:48 am
by williamconley
Of course, you should not have a gateway set for your internal nic, as it has no internet access. Many distros standard networking setup will screw up with more than one gateway. So set the gateway for the nic that actually has internet.

And do remember that the double nic setup is by no means a "Vicidial" or "GoAutoDial" issue. That's pure CentOS. 8)

Feedback for series 2 i7/i5 processors

PostPosted: Fri May 20, 2011 11:41 pm
by Pynk Global
Still no solution on series 2 i7 processors. Friend of mine bought a i5 series 2 processor and has exact same issues. (No VGA, Cant find hdd and other issues, Goautodial crashes after complete boot up) So just a warning to all to stay away for now. I will keep plugging away on testing and will give feedback later.
Tried scratch and many versions of vicibox and goautodial but no joy (goautodial does complete install but has other issues on complete.)

Bought a replacement series 1 i5 and no issue.

Hope this helps someone out for making same mistake.

Maybe the community may want to look into this.
If anyone does make successful install on series 2, please share.

PostPosted: Sun May 22, 2011 12:18 am
by williamconley
You send me one to play with and I'll make it work.

But it might have to be Ubuntu or CentOS, whichever distro has drivers for the hardware on their server edition. 8)

Love To

PostPosted: Mon May 23, 2011 1:33 am
by Pynk Global
Would Love to William, But Fedex from Philippines or Australia would cost more than the unit itself. Just can't win. lol

PostPosted: Mon May 23, 2011 6:43 am
by boybawang
Ive had ubuntu 10.04 running on corei7, even centos 5 works well with corei7 processors