Hi everybody;
I load RouterOS 5.0beta1 to CF card and tried on PC Engines’s alix6e2. Result is not good.
RouterOs is not starting in 10-20 minutes and staying as follow (RouterOS 4.6 is working with same way);
PC Engines ALIX.2 v0.99h
640 KB Base Memory
261120 KB Extended Memory
01F0 Master 848A SanDisk SDCFB-128
Phys C/H/S 980/8/32 Log C/H/S 980/8/32
SYSLINUX 3.84 2009-12-18 EBIOS Copyright (C) 1994-2009 H. Peter Anvin et al
Loading linux...................
Loading initrd.rgz...............ready.
I tried two different way to upload to ROS v5 beta;
I have no any licence yet but I want to work on Level number 0 (FREE) mode first.
first I installed v4.6 via netinstall and board is working properly with that version, after I select the downloaded v5 files with my mouse, and drag it to the Files menu but winbox is freezing and connection dropping. It can not allow to copy files in to “file list”.
second I uploaded v5 files to “file list” via File Zilla FTP , I can upload all v5 files (21 files totals) properly and I am starting reboot procedure but board is starting with v4.6 again.
May be my problem is licence. ROS is confusing without licence?
But that is my first experience with any x86 board for ROS , I want to be sure every things ok before install licence.
I can say yes because; I am working on 3G bridge/router and 4.6 has bug for static route and that version needs fix for that problem. MT guys know that and they fixed that problem in v5.0beta1
Latest version is working properly with my 3G card. That’s why I want to load that version.
v5.0beta1 is working without any problem on RB411U but I could not success on alix6e2 yet.
Note my message about WRAP boards. There is a bug in the 5beta1 boot for these archs… But it’s not your fault or a license issue. Tried 5 ways from sunday to get it to boot but it will not. Somewhere there is a bad piece of code…
if you have a problem with RouterOS, send us detailed report to support. We can’t help just by guessing what the problem is. Send us console output and full information on what you did and what happened.
What is your CF card brand and size? I tried 3 different CF card. v4.6 is working but v5 can not start of all.
first try- It can not allow to copy v5beta1 files in to “file list”.
second try - I can upload all v5 files (21 files totals) properly and I am starting reboot procedure but board is starting with v4.6 again.
don’t add any, if there is problem, it will be there already.
if after reboot still have old version, you probably uploaded files into the wrong place. make sure they are at the TOP of the files list, not in some folder.
Normis,
How many systems did you test with. We sucessfully upgraded 4 systems and had 2 fail. That’s why you see some who have no problem. It seems to be on a board by board basis. I sent in a supout.rif from 4.6 of a board that failed. Let me know if that helps. This is a thorny problem…
ALSO please fix the 4.6 netinstall on the download page!!! Can’t believe it’s still broken a day after being reported…
When I connect to board via FTP Client I am sending version files to root ( also I have one packet for v5beta1 and I tried with this instead of 21 files)
and log output as follow
Jan/01/2000 00:16:45 system,info log rule changed by admin
Jan/01/2000 00:16:48 system,info log rule changed by admin
Jan/01/2000 00:17:17 system,info,account user admin logged in from 192.168.1.11 via ftp
Jan/01/2000 00:17:32 system,info,account user admin logged in from 192.168.1.11 via ftp
Jan/01/2000 00:17:56 system,info,account user admin logged out from 192.168.1.11 via winbox
Jan/01/2000 00:17:56 system,info,account user admin logged out from 192.168.1.11 via ftp
Jan/01/2000 00:17:56 system,info,account user admin logged out from 192.168.1.11 via ftp
Jan/01/2000 00:17:58 kvm,error no hardware virtualization support
Jan/01/2000 00:18:39 system,info verified routeros-x86-5.0beta1.npk
Jan/01/2000 00:18:39 system,info installed routeros-x86-5.0beta1
Jan/01/2000 00:18:39 system,info router rebooted
Jan/01/2000 00:18:42 kvm,error no hardware virtualization support
Jan/01/2000 00:20:15 system,info,account user admin logged in from 192.168.1.11 via winbox