OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: ZDevil on October 27, 2007, 04:47:54 am
-
I know this has been discussed in some other thread(s), but perhaps it is not a bad idea to have a clean discussion.
So, my question is: How does Poky EABI kernel work with Debian EABI system?
How do speed, wifi, bluetooth, usb, sound, video, etc work in this combo?
Cortez says he is experimenting with building Poky kernel and armel system from the start. Here are a couple of nice pointers he gives:
What is EABI?: http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305 (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305)
Debian Installer 2007-08-28 (armel): http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442 (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442)
Poky homepage: http://www.pokylinux.org/ (http://www.pokylinux.org/)
Poky readme (with build instructions): http://svn.o-hand.com/repos/poky/trunk/README (http://svn.o-hand.com/repos/poky/trunk/README)
If the Poky kernels build and run well then we'll have alternatives to Angstrom.
-
Thanks for the information. :-)
-
The Poky and Angstrom kernels are equal, so there won't be any difference as far as I know. I simply like Poky more because of the simple way to setup a build environment. It's already preconfigured, and worked for me out of the box, unlike Angstrom.
Is it time already for a step by step installation guide then? I have it all set up all the way to the base system including networking. Most of the boot-errors are gone, for what it's worth. I know you are working on a huge all in one Debian guide ZDevil, but maybe I'll start a separate thread for a dedicated EABI Debian, since I have it all documented anyway. It took me a lot of time to figure out all the tweaks and configuration steps, so maybe a few of you can take advantage of that and make a quick start.
-
The Poky and Angstrom kernels are equal, so there won't be any difference as far as I know. I simply like Poky more because of the simple way to setup a build environment. It's already preconfigured, and worked for me out of the box, unlike Angstrom.
Is it time already for a step by step installation guide then? I have it all set up all the way to the base system including networking. Most of the boot-errors are gone, for what it's worth. I know you are working on a huge all in one Debian guide ZDevil, but maybe I'll start a separate thread for a dedicated EABI Debian, since I have it all documented anyway. It took me a lot of time to figure out all the tweaks and configuration steps, so maybe a few of you can take advantage of that and make a quick start.
How about including basic X and then creating a new tarball ?
Anyway, please do start the seperate thread.
This is sounding great,
Chero.
-
I second that.
Anyway I am going to posts the (slightly) revised version of the big guy tonight.
I do know that Angstrom and Poky are built out of OE, but I just wanna not to follow the "angstrom laws".
-
I'm compiling a new Poky kernel right now, and after that I will try to build the Poky X11 for use in Debian.
I made a big mistake by doing a apt-get dist-upgrade which messed up pretty much of my carefully tweaked system.
Well, let's say it's a good way of checking my documentation so far.
-
I'm compiling a new Poky kernel right now, and after that I will try to build the Poky X11 for use in Debian.
I made a big mistake by doing a apt-get dist-upgrade which messed up pretty much of my carefully tweaked system.
Well, let's say it's a good way of checking my documentation so far.
I have also experienced messing things up when apt-get dist-upgrading mixed with my own manual upgrading, resulting in glibc and libstdc++ version confusions which renders the whole system basically useless . A careful manual copying in the emergency mode seem to be able to fix that.
So now the first thing I do after setting up a reasonably working environment is to copy all the important setting files and scripts to a backup folder with a mini dir hierarchy, then make a tarball, and do a simple extraction to the new/reinstalled system when bad karma comes.
-
i'm using Debian sid with a rootfs on SD and poky's 2.6.21 kernel. It works great.
I only have some problems with X configuration (i mean, to get a usable desktop configuration)
gonna configure out to run openbox and fbpanel
i certainly will be able to share a bigger and better configured rootfs if anyone is interested...