Mello <mello...@gmail.com> writes: Hi,
> More details... > I've re-installed and I've verified that the same error occurs at the same > step. Below the message: > Configuring flash memory to boot the system ..33%..66% > Make the system bootable > ------------------------ > > !! ERROR: Installation step failed > > An installation step failed. You can try to run the failing item again from > the > menu, or skip it and choose something else. The failing step is: Make the > system bootable > [Press enter to continue] d-i doesn't support iq31244/ep80219 so it's not suprising imho. > > I've once again chose to continue without that knowing that I could > interrupt the boot sequence and use TFTP. > This time I've managed to boot it almost properly with the following > sequence: > RedBoot> fis load ramdisk.gz > RedBoot> load -r -v -h 192.168.1.101 -b 0x01008000 -m tftp > vmlinuz-2.6.32-5-iop32x > -----------<suppressed output>------------- > Raw file loaded 0x01008000-0x0113a69f, assumed entry at 0x01008000 > RedBoot> exec -c "console=ttyS0,115200n8 rw root=/dev/sda1 > mem=512M@0xa0000000" -r 0x01800000 > > Eventually it hangs because of an error in communicating with the disk. Full > log is attached. > > Questions: > 1. how to correctly write boot image to flash? doing something like cat [vmlinuz] > /dev/mtdX should do the trick I guess but I would wait a little bit before doing it. > 2. anybody is able to decode what the disk error (ata4.00: exception Emask > 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen) means? Might be irq or timer troubles... [...] > RedBoot> exec -c "console=ttyS0,115200n8 rw root=/dev/sda1 > mem=512M@0xa0000000" -r 0x01800000 > Using base address 0x01008000 and length 0x001326a0 > The boot tags are located at 0xA0000100 > Booting the kernel... > Uncompressing Linux... done, booting the kernel. > [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 2.6.32-5-iop32x (Debian 2.6.32-29) > (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Fri Dec 10 > 19:47:27 UTC 2010 > [ 0.000000] CPU: XScale-80219 [69052e20] revision 0 (ARMv5TE), cr=0000397f > [ 0.000000] CPU: VIVT data cache, VIVT instruction cache > [ 0.000000] Machine: Intel IQ31244 > [ 0.000000] Memory policy: ECC disabled, Data cache writeback > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total > pages: 130048 > [ 0.000000] Kernel command line: console=ttyS0,115200n8 rw root=/dev/sda1 > mem=512M@0xa0000000 > [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) > [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > [ 0.000000] Memory: 512MB = 512MB total > [ 0.000000] Memory: 511744KB available (3080K code, 444K data, 112K init, > 0K highmem) > [ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, > CPUs=1, Nodes=1 > [ 0.000000] Hierarchical RCU implementation. > [ 0.000000] NR_IRQS:32 > [ 0.000000] Console: colour dummy device 80x30 > [ 0.000000] Calibrating delay loop... 394.85 BogoMIPS (lpj=1974272) > [ 0.220000] Security Framework initialized > [ 0.220000] SELinux: Disabled at boot. > [ 0.220000] Mount-cache hash table entries: 512 > [ 0.220000] Initializing cgroup subsys ns > [ 0.220000] Initializing cgroup subsys cpuacct > [ 0.220000] Initializing cgroup subsys devices > [ 0.220000] Initializing cgroup subsys freezer > [ 0.220000] Initializing cgroup subsys net_cls > [ 0.220000] CPU: Testing write buffer coherency: ok > [ 0.220000] devtmpfs: initialized > [ 0.220000] regulator: core version 0.5 > [ 0.220000] NET: Registered protocol family 16 > [ 0.220000] note: iq31244 board type has been selected > [ 0.220000] note: to select ep80219 operation: > [ 0.220000] 1/ specify "force_ep80219" on the kernel command line > [ 0.220000] 2/ update boot loader to pass the ep80219 id: 1281 So the kernel was booting in iq31244 mode but I would have tried something like ep80219 support. Can you try with force_ep80219 on kernel command line as advised ? Arnaud -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bozyw9qw....@lebrac.rtp-net.org