[RB-050/RB-100/RB-110] Build your Linux becomes easier
[RB-050/RB-100/RB-110] Build your Linux becomes easier
by gdo
Tue Jun 12, 2012 10:51 pm
Hello,
I have developed a script to create a Linux Ubuntu/Debian distro for your roboard from an existing Ubuntu/Debian install.
Use it as mentionned in my wiki to build a working minimal ubuntu for your RB-XXX :
As you can see I use the kernel provided by Roboard and the generic one from ubuntu. That's because I have a kernel panic problem with the Roboard one. I'm working on it.
But the generic kernel from ubuntu works perfectly.
When Roboard kernel panic will be solved, it should be possible to build a 12.04 ubuntu distro for your roboard with the same process.
Feel free to report bugs, new features, usage problems, etc...
Enjoy and share !
gdo
I have developed a script to create a Linux Ubuntu/Debian distro for your roboard from an existing Ubuntu/Debian install.
Use it as mentionned in my wiki to build a working minimal ubuntu for your RB-XXX :
- Code: Select all
sudo ./make_distro.sh -a install -p ubuntu-standard,linux-generic -o linux-image-2.6.34.10-vortex86-sg_1.2_i386.deb -b /dev/mmcblk0
As you can see I use the kernel provided by Roboard and the generic one from ubuntu. That's because I have a kernel panic problem with the Roboard one. I'm working on it.
But the generic kernel from ubuntu works perfectly.
When Roboard kernel panic will be solved, it should be possible to build a 12.04 ubuntu distro for your roboard with the same process.
Feel free to report bugs, new features, usage problems, etc...
Enjoy and share !
gdo
by gdo
Thu Jun 14, 2012 8:18 am
Hi demmeln,
My method is completly different than the classic one using an installer.
Based on debootstrap, I build my system from command line.
So yes I can build the base for a 12.04 distro. But I cannot boot it for now because I do not have a working kernel. It is coming soon
gdo
My method is completly different than the classic one using an installer.
Based on debootstrap, I build my system from command line.
So yes I can build the base for a 12.04 distro. But I cannot boot it for now because I do not have a working kernel. It is coming soon
gdo
by roboard
Thu Jun 14, 2012 11:18 am
Hi gdo and demmeln,
Processors(include Vortex86DX) without cmov instruction are no longer supported by Ubuntu team. All packages are built for i686 platform.
So, we think Ubuntu 10.04 is the latest version that could run on our roboard.
We suggest that you could try using Debian to replace Ubuntu.
Until now, Debian still supports i486(i586) platform.
Processors(include Vortex86DX) without cmov instruction are no longer supported by Ubuntu team. All packages are built for i686 platform.
So, we think Ubuntu 10.04 is the latest version that could run on our roboard.
We suggest that you could try using Debian to replace Ubuntu.
Until now, Debian still supports i486(i586) platform.
by gdo
Thu Jun 14, 2012 11:54 am
roboard wrote:Hi gdo and demmeln,
Processors(include Vortex86DX) without cmov instruction are no longer supported by Ubuntu team. All packages are built for i686 platform.
So, we think Ubuntu 10.04 is the latest version that could run on our roboard.
We suggest that you could try using Debian to replace Ubuntu.
Until now, Debian still supports i486(i586) platform.
+1
But it is just the kernel provided that does not support processors older than i686. Using the DMP kernel it should work. (with no support and maybe with some bugs but it should work for a minimal ubuntu install).
I will try it and tell you the result once I have a working kernel rebuilt.
By default my script build a lucid distro so you can try it.
++
gdo
by demmeln
Thu Jun 14, 2012 1:11 pm
Hm... I'm don't know so much, but woulnd't the i686 instruction problem also apply to all library / executable binaries outside the kernel?
I have a working lucid installation (via virtualbox) already, but I have to try you script just for the sake of it!
And yes please, keep us updated! Thanks!
demmeln
I have a working lucid installation (via virtualbox) already, but I have to try you script just for the sake of it!
And yes please, keep us updated! Thanks!
demmeln
by mbj
Thu Feb 21, 2013 4:48 pm
Hello mbj,
Could you give me the exact command you have used and the kernel panic trace ?
Kernel Panic coud have various reason.
gdo
Hello gdo, thanks for your fast answer.
Firstly, I downloaded your make_distro code and executed it with the next command:
- Code: Select all
sudo ./make_distro.sh -a install -p ubuntu-standard,linux-generic -o distros/linux-image-2.6.34.10-vortex86-sg_1.2_i386.deb -b /dev/sdb
I tried with "DEBIAN_VERSION=precise" (12.04) and this is the trace:
i49 [dot] tinypic [dot] com [slash] rtonet.jpg (Sorry I can't put url's yet)
I tried with the "DEBIAN_VERSION=lucid" and "works" (well, I get a terminal line where I can login if I execute the non-Vortex86 kernel, but I can't start the X server, that's normal?). In case that I execute the Vortex86 modified kernel, I get the next ouput:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0).
After that, I tried changing the destination source to /dev/sdb1, but fails when it's making the distro in the step "Prepare rw image".
Can you help me? Thank you very much.
by gdo
Thu Feb 21, 2013 5:14 pm
mbj wrote:Hello mbj,
Could you give me the exact command you have used and the kernel panic trace ?
Kernel Panic coud have various reason.
gdo
Hello gdo, thanks for your fast answer.
Firstly, I downloaded your make_distro code and executed it with the next command:
- Code: Select all
sudo ./make_distro.sh -a install -p ubuntu-standard,linux-generic -o distros/linux-image-2.6.34.10-vortex86-sg_1.2_i386.deb -b /dev/sdb
I tried with "DEBIAN_VERSION=precise" (12.04) and this is the trace:
i49 [dot] tinypic [dot] com [slash] rtonet.jpg (Sorry I can't put url's yet)
Ok I wait you could upload the trace.
I tried with the "DEBIAN_VERSION=lucid" and "works" (well, I get a terminal line where I can login if I execute the non-Vortex86 kernel, but I can't start the X server, that's normal?).
Yes it is normal since you did not specified any desktop or X package in the command line. If you try this command line, you will get a graphic session :
sudo ./make_distro.sh -a install -p ubuntu-standard,linux-generic,lubuntu-desktop -o distros/linux-image-2.6.34.10-vortex86-sg_1.2_i386.deb -b /dev/sdb
In case that I execute the Vortex86 modified kernel, I get the next ouput:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0).
Do you mean that you used the generic ubuntu kernel with lucid with success but that it fails with the vortex kernel ?
After that, I tried changing the destination source to /dev/sdb1, but fails when it's making the distro in the step "Prepare rw image".
That's normal since sdb1 is a partition and sdb is the full disk containing partition. You must provide path to the full disk so /dev/sdb to the script
Can you help me? Thank you very much.
Sure I can.
I will launch some tests tonight to reproduce.
by mbj
Thu Feb 21, 2013 6:35 pm
Ok I wait you could upload the trace.
Sorry but I don't know how to capture the trace, is for this reason that I uploaded the photo. I googled the topic and I found that the log should be at /var/log/ folder, but after search through I haven't saw any kernel panic trace or similar.
Can you point me out how can I correctly get the trace?
Do you mean that you used the generic ubuntu kernel with lucid with success but that it fails with the vortex kernel ?
Yes, I want to say that.
That's normal since sdb1 is a partition and sdb is the full disk containing partition. You must provide path to the full disk so /dev/sdb to the script
Ok, sorry, it was a stupid test... xD
Thank you again.
by gdo
Fri Feb 22, 2013 9:18 pm
Sorry I was a bite busy with work, I could not test yesterday. I'm working on it now and give you the results this week end.
You cannot find kernel panic traces with /var/log. But just take a photo of your screen.
Or write the error associated with the kernel panic.
There is some ways to debug kernel and get traces but it is a bit "difficult" to use and not really needed for now.
mbj wrote:Sorry but I don't know how to capture the trace, is for this reason that I uploaded the photo. I googled the topic and I found that the log should be at /var/log/ folder, but after search through I haven't saw any kernel panic trace or similar.
Can you point me out how can I correctly get the trace?
You cannot find kernel panic traces with /var/log. But just take a photo of your screen.
Or write the error associated with the kernel panic.
There is some ways to debug kernel and get traces but it is a bit "difficult" to use and not really needed for now.
by gdo
Sat Feb 23, 2013 10:48 am
Hi mbj,
I reproduced a kernel panic trace :
Do you have the same one ?
(I have no solution for now but I am looking for one ^^)
++
gdo
I reproduced a kernel panic trace :
- Code: Select all
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.34.10-vortex86-sg (root@debian) (gcc version 4.4.5 (Debian 4.4.5-8) ) #3 Tue Jul 12 02:05:36 CST 2011
[ 0.000000] CPU: vendor_id 'Vortex86 SoC' unknown, using generic init.
[ 0.000000] CPU: Your system may be unstable.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
[ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[ 0.000000] Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
[ 0.000000] DMI not present or invalid.
[ 0.000000] last_pfn = 0x10000 max_arch_pfn = 0x100000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000010000000
[ 0.000000] RAMDISK: 0fcb9000 - 0ffff000
[ 0.000000] 256MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 10000000
[ 0.000000] low ram: 0 - 10000000
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000001 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x00010000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000001 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00010000
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 10000000 (gap: 10000000:ef000000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64926
[ 0.000000] Kernel command line: init=/sbin/init --verbose root=/dev/disk/by-label/24084 initrd=/boot/initrd.img-2.6.34.10-vortex86-sg console=ttyS0,115200n8 console=tty0 BOOT_IMAGE=/boot/vmlinuz-2.6.34.10-vortex86-sg
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 1310700 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Subtract (23 early reservations)
[ 0.000000] #0 [0001000000 - 00013d8ca0] TEXT DATA BSS
[ 0.000000] #1 [000fcb9000 - 000ffff000] RAMDISK
[ 0.000000] #2 [000009fc00 - 0000100000] BIOS reserved
[ 0.000000] #3 [00013d9000 - 00013df000] BRK
[ 0.000000] #4 [0000007000 - 0000041000] PGTABLE
[ 0.000000] #5 [00013df000 - 00015df000] BOOTMEM
[ 0.000000] #6 [00013d8ca0 - 00013d8ca4] BOOTMEM
[ 0.000000] #7 [00013d8cb0 - 00013d8d30] BOOTMEM
[ 0.000000] #8 [00013d8d30 - 00013d8d48] BOOTMEM
[ 0.000000] #9 [00015df000 - 00015df800] BOOTMEM
[ 0.000000] #10 [00013d8d50 - 00013d8df8] BOOTMEM
[ 0.000000] #11 [00013d8e00 - 00013d8e40] BOOTMEM
[ 0.000000] #12 [00013d8e40 - 00013d8e80] BOOTMEM
[ 0.000000] #13 [00013d8e80 - 00013d8ec0] BOOTMEM
[ 0.000000] #14 [00013d8ec0 - 00013d8f00] BOOTMEM
[ 0.000000] #15 [00013d8f00 - 00013d8f40] BOOTMEM
[ 0.000000] #16 [00013d8f40 - 00013d8f50] BOOTMEM
[ 0.000000] #17 [00015df800 - 00015df8ba] BOOTMEM
[ 0.000000] #18 [00015df8c0 - 00015df97a] BOOTMEM
[ 0.000000] #19 [00015df980 - 00015e0980] BOOTMEM
[ 0.000000] #20 [00015e0980 - 0001600980] BOOTMEM
[ 0.000000] #21 [0001600980 - 0001610980] BOOTMEM
[ 0.000000] #22 [0001611000 - 0001750fec] BOOTMEM
[ 0.000000] Memory: 250676k/262144k available (2498k kernel code, 11076k reserved, 918k data, 260k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xfffe3000 ( 759 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] .init : 0xc1357000 - 0xc1398000 ( 260 kB)
[ 0.000000] .data : 0xc1270b52 - 0xc1356598 ( 918 kB)
[ 0.000000] .text : 0xc1000000 - 0xc1270b52 (2498 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:16
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] console [ttyS0] enabled
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 1000.148 MHz processor.
[ 0.010015] Calibrating delay loop (skipped), value calculated using timer frequency.. 2001.64 BogoMIPS (lpj=3333826)
[ 0.016787] Mount-cache hash table entries: 512
[ 0.020594] Initializing cgroup subsys debug
[ 0.023351] Initializing cgroup subsys ns
[ 0.026680] Initializing cgroup subsys cpuacct
[ 0.030013] Initializing cgroup subsys memory
[ 0.033376] Initializing cgroup subsys devices
[ 0.036681] Initializing cgroup subsys freezer
[ 0.040012] Initializing cgroup subsys blkio
[ 0.043498] Performance Events:
[ 0.046678] CPU: Vortex86 SoC 05/02 stepping 02
[ 0.051776] Checking 'hlt' instruction... OK.
[ 0.071811] NET: Registered protocol family 16
[ 0.088347] PCI: Using configuration type 1 for base access
[ 0.110357] bio: create slab <bio> at 0
[ 0.115343] vgaarb: loaded
[ 0.120785] SCSI subsystem initialized
[ 0.124457] PCI: Probing PCI hardware
[ 0.131802] vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.137492] pci 0000:00:07.0: default IRQ router [17f3:6031]
[ 0.143522] pci 0000:00:0a.0: address space collision: [mem 0x000e2000-0x000e2fff] conflicts with reserved [mem 0x000e0000-0x000fffff]
[ 0.146702] pci 0000:00:0a.1: address space collision: [mem 0x000e3000-0x000e30ff] conflicts with reserved [mem 0x000e0000-0x000fffff]
[ 0.150032] pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff] conflicts with reserved [mem 0x000e0000-0x000fffff]
[ 0.153365] pci 0000:00:0b.1: address space collision: [mem 0x000e1000-0x000e10ff] conflicts with reserved [mem 0x000e0000-0x000fffff]
[ 0.161121] Switching to clocksource tsc
[ 0.175536] pci 0000:00:0c.0: BAR 6: assigned [mem 0x10000000-0x1001ffff pref]
[ 0.182925] pci 0000:00:0a.0: BAR 0: assigned [mem 0x10020000-0x10020fff]
[ 0.189830] pci 0000:00:0a.0: BAR 0: set to [mem 0x10020000-0x10020fff] (PCI address [0x10020000-0x10020fff]
[ 0.199789] pci 0000:00:0b.0: BAR 0: assigned [mem 0x10021000-0x10021fff]
[ 0.206688] pci 0000:00:0b.0: BAR 0: set to [mem 0x10021000-0x10021fff] (PCI address [0x10021000-0x10021fff]
[ 0.216644] pci 0000:00:0a.1: BAR 0: assigned [mem 0x10022000-0x100220ff]
[ 0.223544] pci 0000:00:0a.1: BAR 0: set to [mem 0x10022000-0x100220ff] (PCI address [0x10022000-0x100220ff]
[ 0.233500] pci 0000:00:0b.1: BAR 0: assigned [mem 0x10022100-0x100221ff]
[ 0.240397] pci 0000:00:0b.1: BAR 0: set to [mem 0x10022100-0x100221ff] (PCI address [0x10022100-0x100221ff]
[ 0.250549] NET: Registered protocol family 2
[ 0.255180] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.262679] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.270113] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.276776] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.283219] TCP reno registered
[ 0.286449] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.292396] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.299009] NET: Registered protocol family 1
[ 1.634509] pci 0000:00:0a.1: EHCI: BIOS handoff failed (BIOS bug?) 01010001
[ 2.974209] pci 0000:00:0b.1: EHCI: BIOS handoff failed (BIOS bug?) 01010001
[ 2.981845] Unpacking initramfs...
[ 3.648847] Freeing initrd memory: 3352k freed
[ 3.669784] platform rtc_cmos: registered platform RTC device (no PNP device found)
[ 3.677603] apm: BIOS not found.
[ 3.683055] audit: initializing netlink socket (disabled)
[ 3.688695] type=2000 audit(1361643385.688:1): initialized
[ 3.725359] msgmni has been set to 496
[ 3.730639] alg: No test for stdrng (krng)
[ 3.734930] io scheduler noop registered
[ 3.738956] io scheduler deadline registered
[ 3.744097] io scheduler cfq registered (default)
[ 3.750576] isapnp: Scanning for PnP cards...
[ 4.111716] isapnp: No Plug & Play device found
[ 4.616466] Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled
[ 4.623432] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 4.630736] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 4.647922] loop: module loaded
[ 4.653092] scsi0 : pata_it821x
[ 4.657621] scsi1 : pata_it821x
[ 4.661705] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f4 bmdma 0xfff0 irq 14
[ 4.668801] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x374 bmdma 0xfff8 irq 14
[ 4.678492] PNP: No PS/2 controller found. Probing ports directly.
[ 4.933993] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 4.939505] ata1.00: ATA-6: SU02G RDC SD-IDE HOST CONTROLLER, 01000000, max UDMA/133
[ 4.947735] ata1.00: 3862528 sectors, multi 0: LBA
[ 4.952832] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 4.961072] mice: PS/2 mouse device common for all mice
[ 4.968204] input: PC Speaker as /devices/platform/pcspkr/input/input0
[ 4.975402] ata1.00: configured for UDMA/33
[ 4.980290] scsi 0:0:0:0: Direct-Access ATA SU02G RDC SD 0100 PQ: 0 ANSI: 5
[ 4.990840] NET: Registered protocol family 17
[ 4.999838] sd 0:0:0:0: [sda] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
[ 5.009721] sd 0:0:0:0: [sda] Write Protect is off
[ 5.014908] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 5.025627] sda: sda1 sda2
[ 5.036892] sd 0:0:0:0: [sda] Attached SCSI disk
[ 5.173912] Freeing unused kernel memory: 260k freed
[ 5.181451] Kernel panic - not syncing: Attempted to kill init!
[ 5.187513] Pid: 1, comm: init Not tainted 2.6.34.10-vortex86-sg #3
[ 5.193868] Call Trace:
[ 5.196406] [<c126e21a>] ? panic+0x37/0x91
[ 5.200697] [<c10251bd>] ? do_exit+0x56d/0x660
[ 5.205328] [<c10252d9>] ? do_group_exit+0x29/0x80
[ 5.210311] [<c1030e97>] ? get_signal_to_deliver+0x197/0x3a0
[ 5.216162] [<c10035b0>] ? do_invalid_op+0x0/0x80
[ 5.221049] [<c1001fc4>] ? do_signal+0x64/0x840
[ 5.225778] [<c1014a36>] ? do_page_fault+0x136/0x380
[ 5.230929] [<c1014aae>] ? do_page_fault+0x1ae/0x380
[ 5.236080] [<c1014a36>] ? do_page_fault+0x136/0x380
[ 5.241234] Clocksource tsc unstable (delta = 66578937 ns)
[ 5.246832] [<c1014aae>] ? do_page_fault+0x1ae/0x380
[ 5.251998] [<c1007b69>] ? sys_execve+0x39/0x70
[ 5.256712] [<c1002932>] ? ptregs_execve+0x12/0x20
[ 5.261694] [<c126fcbe>] ? work_notifysig+0x13/0x25
[ 5.266757] [<c10035b0>] ? do_invalid_op+0x0/0x80
[ 5.271645] [<c10027d8>] ? do_notify_resume+0x38/0x40
[ 5.276885] [<c126fcbe>] ? work_notifysig+0x13/0x25
[ 5.281949] [<c10035b0>] ? do_invalid_op+0x0/0x80
Do you have the same one ?
(I have no solution for now but I am looking for one ^^)
++
gdo
by gdo
Mon Feb 25, 2013 1:26 pm
Hi,
Then I have investigated this week end to know why you got this kernel panic.
I knew that the Ubuntu linux kernel was not supporting i586 arch any more since oneiric (11.10). But I was thinking that it was just the kernel. But it is wrong. The last available ubuntu distribution for roboard and generally for i586 is 10.04.
It is clearly writted on the ubuntu website :
The script is doing all fine. But it could not run any code from ubuntu since it is not build for i586 and lower, including in initrd and /sbin/init process.
gdo
Then I have investigated this week end to know why you got this kernel panic.
I knew that the Ubuntu linux kernel was not supporting i586 arch any more since oneiric (11.10). But I was thinking that it was just the kernel. But it is wrong. The last available ubuntu distribution for roboard and generally for i586 is 10.04.
It is clearly writted on the ubuntu website :
However, Ubuntu oneiric will not run on i586 or earlier processors. Despite the architecture name "i386", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian[2]. (No version of Linux has ever supported the 286 or earlier chips in the series.) Support for i586 and lower processors, as well as for i686 processors without the cmov instruction, was dropped in Ubuntu 10.10. Most i686 and later processors are still supported
The script is doing all fine. But it could not run any code from ubuntu since it is not build for i586 and lower, including in initrd and /sbin/init process.
gdo