Community discussions

MikroTik App
 
bbruggers
just joined
Topic Author
Posts: 2
Joined: Wed Mar 12, 2008 11:36 am

upgrade to 3.4 failed

Wed Mar 12, 2008 11:39 am

i upgraded the system to 3.4. let the pc reboot.
the only text i get is now loading system loading e

nothing happens
 
User avatar
tjohnson
Member Candidate
Member Candidate
Posts: 127
Joined: Thu Aug 12, 2004 7:01 am

Re: upgrade to 3.4 failed

Thu Mar 13, 2008 6:37 am

Yes, I have this exact same problem. An x86 system with a CF IDE drive that was working perfectly with 3.3, and when upgraded to 3.4 it died the same. :(
 
User avatar
gmsmstr
Trainer
Trainer
Posts: 982
Joined: Fri Jun 04, 2004 2:22 am
Location: St. Louis, MO
Contact:

Re: upgrade to 3.4 failed

Thu Mar 13, 2008 8:12 am

Belive this is a known issue on SOME x86 devices. We are not recommending upgrades to 3.4 right this second. I'm sure give it a week and we will get it straighten out.
 
Alex
Member Candidate
Member Candidate
Posts: 214
Joined: Thu Sep 30, 2004 11:07 am

Re: upgrade to 3.4 failed

Thu Mar 13, 2008 11:10 pm

I had this issue too.resolved by disabling hiper treading in bios./system hardware multiplie cpu off.
 
uldis
MikroTik Support
MikroTik Support
Posts: 3446
Joined: Mon May 31, 2004 2:55 pm

Re: upgrade to 3.4 failed

Fri Mar 14, 2008 3:55 pm

please wait till v3.5 and post the results, looks like we were able to reproduce it and fix this problem.
New version will be out beginning of the next week.
 
User avatar
gmsmstr
Trainer
Trainer
Posts: 982
Joined: Fri Jun 04, 2004 2:22 am
Location: St. Louis, MO
Contact:

Re: upgrade to 3.4 failed

Fri Mar 14, 2008 5:49 pm

Thanks a bunch.
 
User avatar
ozcar2k7
just joined
Posts: 11
Joined: Wed May 23, 2007 8:14 pm
Location: Rancagua, Chile

Re: upgrade to 3.4 failed

Fri Mar 14, 2008 10:28 pm

After upgrade to 3.4, I`ve lost remote access to web box from my office :(
And I had to make some changes to scripts because they didn't work.
I think that one scripting changelog is needed too.

C ya
 
DesertTek
newbie
Posts: 43
Joined: Sun Feb 10, 2008 9:10 am

Re: upgrade to 3.4 failed

Fri Mar 14, 2008 11:57 pm

Disabling HT in BIOS works!
 
vklimovs
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Fri Dec 16, 2005 5:37 pm

Re: upgrade to 3.4 failed

Wed Mar 19, 2008 4:57 pm

Just upgraded to 3.5 and got the same problem.
 
User avatar
acim
Member
Member
Posts: 415
Joined: Mon Sep 12, 2005 12:26 am
Location: Serbia
Contact:

Re: upgrade to 3.4 failed

Wed Mar 19, 2008 8:23 pm

Disabling HT in BIOS works!
I didn't have this problem after upgrading from 3.3 to 3.4, but I have problem upgrading from 3.4 to 3.5. I think I've tried disabling HT, but it didn't work. And my CPU doesn't have HT at all.
 
riza
newbie
Posts: 30
Joined: Fri May 28, 2004 7:15 pm

Re: upgrade to 3.4 failed

Thu Mar 20, 2008 5:39 am

I got message "Loading E...." in console monitor after upgrade from 3.3 to 3.5.
My router was using Quad Core Xeon processor with Intel S5000 chipset.
You do not have the required permissions to view the files attached to this post.
 
mrxbgd
just joined
Posts: 3
Joined: Wed Oct 31, 2007 1:22 am

Re: upgrade to 3.4 failed

Thu Mar 20, 2008 6:48 am

The same problem "loading E" with 3.5
 
bbruggers
just joined
Topic Author
Posts: 2
Joined: Wed Mar 12, 2008 11:36 am

Re: upgrade to 3.4 failed

Wed Apr 02, 2008 6:14 pm

hello,

did a new install to 3.6 now i get loading system on the screen.
asus m2v-mx motherboard amd processor


worked fine with 2.9

who can help me
 
cybervolkan
just joined
Posts: 4
Joined: Tue Jun 10, 2008 2:48 pm

Re: upgrade to 3.4 failed

Wed Jun 18, 2008 11:17 am

I am getting this error with S5000VCL board and xeon E5405 cpu. :(

I am trying to make a fresh install with 3.9 and 3.10 version iso images...

Is there an exact solution of this problem???
 
User avatar
gmsmstr
Trainer
Trainer
Posts: 982
Joined: Fri Jun 04, 2004 2:22 am
Location: St. Louis, MO
Contact:

Re: upgrade to 3.4 failed

Wed Jun 18, 2008 8:08 pm

This is a known issue with anything above 3.3 .. 3.4 has kernal changes that caused this issue to occur. I think they will be using a new kernal in 3.11, hopefully that will fix this!

Who is online

Users browsing this forum: anav, Bing [Bot], Google [Bot], kevinlukas, mada3k, pe1chl and 87 guests