Slackware inside Pandora.


Linux-SWAT

Forum Addict!
Joined
Feb 13, 2010
Messages
9,168
################################################

Below is the development thread.

For stable releases, see the Slackware for Pandora Wiki :
https://pandorawiki.org/Software_projects/OS/Slackware

################################################

http://arm.slackware.com/
Old link: http://www.armedslack.org/


Slackware ARM 13.1 and onwards is built for ARMv4t, little endian, soft float, EABI.


As i'm a total ARM rookie, i'm not yet able to answer this ^^'


BTW, official OP's ARM page :


http://www.arm.com/p...a/cortex-a8.php


----EDIT :


Spoiler :


Yes, i succeeded.


Check this out:


http://pandorawiki.org/Software_projects/OS/Slackware
 
Last edited:
With the right kernel it should work, but it will be sub-optimal. For best performance userspace should be compiled for ARMv7a VFP EABI.
 
Last edited by a moderator:
Ok, thanks for the info.


My first try just failed miserably ^^. New things to learn. Good.
 
Went further : the Kernel Panic ^^


Followed :


http://www.armedslack.org/doku.php?id=installation


Mini root filesystems for unsupported platforms.


slack-current-miniroot_18Jan11.tar.xz


Ext2 filesystem.


1- Boot : only the logo.


2- Took autoboot from http://vminko.org/gentoo_manuals/pandora


Adapted it.

setenv bootargs root=/dev/mmcblk0p1 rw rootdelay=2 vram=6272K omapfb.vram=0:3000K quiet
ext2load mmc 0 0x80300000 /boot/zImage-versatile-2.6.36.3


bootm 0x80300000

Boot : only the logo.


3- Took kernel from http://vminko.org/gentoo_manuals/pandora


Adapted autoboot


Boot :


[ 7.545959] USB: No board-specific platform config found


[11.104731] Kernel panic - not syncing: Attempted to kill init!


What is this "board-specific platform config" ?
 
Last edited by a moderator:
Built my own kernel.


Fun to see its tiny .config compared to PC ones.


Not tried it yet.


---Edit : Boot : only the logo. :/


Followed http://pandorawiki.org/Kernel_build_instructions


Choosed the hard way :


http://www.codesourcery.com/sgpp/lite/arm/portal/release1592


Sourcery G++ Lite 2010.09-51 for ARM EABI

cd /home/ME/arm-2010.09-51-arm-none-eabi-i686-pc-linux-gnu/arm-2010.09/bin/


ln -s arm-none-eabi-objcopy arm-none-linux-gnueabi-objcopy


ln -s arm-none-eabi-nm arm-none-linux-gnueabi-nm


ln -s arm-none-eabi-ld arm-none-linux-gnueabi-ld


ln -s arm-none-eabi-gcc arm-none-linux-gnueabi-gcc


ln -s arm-none-eabi-ar arm-none-linux-gnueabi-ar


ln - arm-none-eabi-ar arm-none-linux-gnueabi-ar


ln -s arm-none-eabi-ld arm-none-linux-gnueabi-ld


etc...


cd /home/ME/pandora-kernel/


export PATH=$PATH:/home/ME/arm-2010.09-51-arm-none-eabi-i686-pc-linux-gnu/arm-2010.09/bin/


export CROSS_COMPILE=arm-none-linux-gnueabi-


make omap3_pandora_defconfig


make menuconfig


make uImage

Questions :


1- Magic sysrq : i suppose power on + pandora button = hard reset aka alt-printscr + b ?


Other combination ?


2- Is that supposed to be off in the default .config ?


Power management options --> none


CPU Frequency scaling --> none


3- No iptables ?


4- No utf8 for fat mounting ?


5- At power on, is it possible to see a message, not the very fist pandora logo ?


6- And same question as above post : What is this "board-specific platform config" ?
 
Last edited by a moderator:
1- Magic sysrq : i suppose power on + pandora button = hard reset aka alt-printscr + b ?


Other combination ?
power+pandora is handled by hardware, don't know how to make use of magic sysreq with custom keypads.

2- Is that supposed to be off in the default .config ?


Power management options --> none


CPU Frequency scaling --> none
Yeah, this is still not implemented for OMAP3.

3- No iptables ?


4- No utf8 for fat mounting ?
The default config is only for hardware support, you add extra features yourself.

5- At power on, is it possible to see a message, not the very fist pandora logo ?
Remove 'quiet' from autoboot bootargs?


Note that for output kernel has to reach display driver stage, there is no x86-like VGA mode that could be used for very early messages.

6- And same question as above post : What is this "board-specific platform config" ?
That's something USB related, not the reason it doesn't boot for you.


I'm guessing the real problem is it doesn't mount rootfs, what fs do you have on your SD?
 
1- Magic sysrq : i suppose power on + pandora button = hard reset aka alt-printscr + b ?


Other combination ?
power+pandora is handled by hardware, don't know how to make use of magic sysreq with custom keypads.

I should have known that because it works even before kernel boot... :/


Any Pandora sysrq guru around ?

2- Is that supposed to be off in the default .config ?


Power management options --> none


CPU Frequency scaling --> none
Yeah, this is still not implemented for OMAP3.

So the clocking user space tool controls what ? The processor itself ?

3- No iptables ?


4- No utf8 for fat mounting ?
The default config is only for hardware support, you add extra features yourself.

Are the official firmwares shipped with this default .config kernel ?

5- At power on, is it possible to see a message, not the very fist pandora logo ?
Remove 'quiet' from autoboot bootargs?


Note that for output kernel has to reach display driver stage, there is no x86-like VGA mode that could be used for very early messages.

Removing 'quiet' did nothing.


Ok.

6- And same question as above post : What is this "board-specific platform config" ?
That's something USB related, not the reason it doesn't boot for you.

Maybe the usb stack is mandatory at some point in the init process ?

I'm guessing the real problem is it doesn't mount rootfs, what fs do you have on your SD?

ext2


But it first needs to access the filesystem, therefore the SD device. :huh:


I just added some stuff in my kernel, checking around all options. seeing ext2 compiled inside kernel etc...


7- Is autoboot mandatory (on a SD) ?


----Edit : Went further again :)


Some documentation here :


http://neuvoo.org/wiki/index.php?title=Install_Pre-Built_Image


Just copied uImage, /lib/modules and /lib/firmware from http://openpandora.org/firmware/pandora-rootfs.tar.bz2


Had bluetooth lines


set system clock


waiting 2sec


mmcblk0: p1


EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended


VFS: Mounted root ext2


Freeing Init memory


Kernel panic ^^


Reading this thread :
 
Last edited by a moderator:
Tried what i can...


Recompiled my own kernel, took one from official rootfs : always the same.


VFS: Mounted root ext2


Freeing Init memory: 140K


Kernel panic


I'm stuck for now. Good fstab, good autoboot, a custom kernel which works on official firmware, ext2 compiled in...


I even copied /bin/busybox and linked it to /linuxrc


Copied official /dev/* to slack:/dev/
 
Last edited by a moderator:
No other messages?


What are your current bootargs?


Try enabling CONFIG_DEBUG and CONFIG_DEBUG_ERRORS, maybe that'll give better message.
 
Nothing more.



Code:
setenv bootargs root=/dev/mmcblk0p1 rw rootdelay=2 vram=6272K omapfb.vram=0:3000K

ext2load mmc 0 0x80300000 /boot/uImage

bootm 0x80300000



/boot/uImage is not a symbolic link.



Those DEBUG are configured in the default kernel.

I added some more debug things without producing more output...



My fstab :





Code:
/dev/mmcblk0p1       /                    ext2       defaults,noatime      1  1

proc                 /proc                proc       defaults              0  0

devpts               /dev/pts             devpts     mode=0620,gid=5       0  0

usbfs                /proc/bus/usb        usbfs      defaults              0  0

tmpfs                /var/volatile        tmpfs      defaults              0  0

tmpfs                /dev/shm             tmpfs      mode=0777             0  0

tmpfs                /media/ram           tmpfs      defaults              0  0


/dev/mmcblk0p1 replaced /rootfs


I use the stable 13.1 release now.


With the same exact result...


Mmm device mapper problem ?


Ext3 try ?


Separate /boot partition ?


. . . birds flying . . .
 
Tried it, their init process crashes, looks like it needs a newer kernel, as chrooting into that rootfs results in:



Code:
chroot /media/mmcblk0p2/

FATAL: kernel too old



Try building 2.6.37 kernel from pandora-37 branch at git.openpandora.org . Start with



Code:
make omap3_pandora_defconfig

and then do menuconfig for tuning.
 
Last edited by a moderator:
looks like it needs a newer kernel

Newer than 2.6.27, if i understand right ?


Will try.


A 2.6.37 ! ...Woot !


Thx for your time.


----EDIT :


$ git clone git://openpandora.org/pandora-kernel.git


Checking out files: 100% (24654/24654), done.


$ git checkout --track -b pandora-37 origin/pandora-37


Checking out files: 100% (34166/34166), done.


Branch pandora-37 set up to track remote branch refs/remotes/origin/pandora-37.


Switched to a new branch "pandora-37"


----EDIT :


$ make omap3_pandora_defconfig


HOSTLD scripts/kconfig/conf


***


*** Can't find default configuration "arch/x86/configs/omap3_pandora_defconfig"!


***


So i did a make mrproper, and then manually copied arch/arm/configs/omap3_pandora_defconfig to .config , followed by a make clean.


----EDIT :


$ make -j4 uImage


HOSTLD scripts/kconfig/conf


scripts/kconfig/conf --silentoldconfig Kconfig


make: *** Pas de règle pour fabriquer la cible « uImage ». Arrêt.


TT. Seems the kernel is going on x86 mode :


Processor type and features ---> Processor family (Pentium-Pro)


Of course i exported the path of compiler and the cross compile...


----EDIT :


Seems i have to :


$ export ARCH=arm


before :


$ make omap3_pandora_defconfig


----EDIT :


CRAP !


Built kernel fine, built modules fine, and :


# INSTALL_MOD_PATH="/mnt/sd/1/" make modules_install


cp: cannot stat `/home/me/pandora/pandora-kernel/modules.builtin': No such file or directory


make: *** [_modinst_] Error 1
 
Last edited by a moderator:
Back
Top