Package: apex-nslu2 Version: 1.4.15 Severity: normal Hi Marc
The apex-nslu2 package currently sets CONFIG_RAMDISK_SIZE to 0x00400000 whereas the Ramdisk partition on the NSLU2 is 0x00600000 bytes. The boot log indicates that APEX computes the size of the partition (line after "copy -s fis://ramdisk 0x01000000" below). # copy -s $kernelsrc $bootaddr # copy -s fis://kernel 0x00008000 1441760 bytes transferred # copy -s $ramdisksrc $ramdiskaddr # copy -s fis://ramdisk 0x01000000 6291440 bytes transferred Note that 6291440 = 0x005FFFF0 which is the size of the Ramdisk partition minus 16 bytes. However, the value for CONFIG_RAMDISK_SIZE that is used in the ATAG header is the value set in the APEX .config file (0x00400000) when building APEX. ATAG_HEADER ATAG_MEM: start 0x00000000 size 0x02000000 ATAG_CMDLINE: (67 bytes) 'console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug rootdelay=2' ATAG_INITRD2: start 0x01000000 size 0x00400000 ATAG_END Booting kernel at 0x00008000... Is it possible to change APEX such that the computed value is used to set the ATAG header? If not, it would great if you would upload a version of APEX that has CONFIG_RAMDISK_SIZE set to 0x005FFFF0. Martin recently updated flash-kernel so that it correctly handles initial ramdisks that are larger than 4 MiB, but we need to change APEX for completeness. The results of the test I have done are CONFIG_RAMDISK_SIZE flash-kernel ramdisk size Result 0x00400000 1.1 < 4 MiB OK (etch) 0x00400000 1.1 > 4 MiB Does not boot 0x00400000 SVN < 4 MiB OK 0x00400000 SVN > 4 MiB Does not boot 0x005FFFF0 1.1 < 4 MiB OK 0x005FFFF0 1.1 > 4 MiB OK 0x005FFFF0 SVN < 4 MiB OK 0x005FFFF0 SVN > 4 MiB OK Thanks. Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
