Where We Are Now!

[ZDevil]

No apology. A long shot: Isn't it true that we first have to extract the kernel module tarball together with the rootfs before flashing the kernel?

[tux]

No apology. A long shot: Isn't it true that we first have to extract the kernel module tarball together with the rootfs before flashing the kernel?

 I was hoping to avoid all that!

I expect that the rootfs from bigbridge may have to be used for success here, unless I go through the install using neil's files until I get a command line system. Then copy the modules, flash the cortezkernel and hope to get the gui up. I'll keep reading your how to. Eventually sense will break through my foggy brain cells.

[ZDevil]

AFAIK the bigbridge rootfs has the kernel modules only for 2.6.17 and 2.6.20 (and they are EABI).  Does the kernel you are testing match this? (Sorry I lost track of which one you're playing with now ...)

[tux]

AFAIK the bigbridge rootfs has the kernel modules only for 2.6.17 and 2.6.20 (and they are EABI).  Does the kernel you are testing match this? (Sorry I lost track of which one you're playing with now ...)

 I'm not surprised!  I'm trying to get OABI + OABI working. So I am using the cortez 2.6.21 kernel   So I think I must  eventually try setting up the BigBridge way first. Copy the 2.6.21 modules over and flash cortez's kernel. I suppose what i just tried might work if I built a 2.6.20 OABI kernel: sometime before Christmas I think.  Cheers.. I'm going to see if the shell will let me cut my way out of this jungle.

[tux]

 Still trying to get OABI + OABI. I started again with the Bigbridge method. I did some twiddles to get the wifi card up. I cheated and copied my interfaces file and my sources.list to the SD card and then to BigZ.  I then used tar zxvf from the 2.6.21 modules file on the SD card to the root of the filesystem. Apparently successful.
In order to get the wifi up I had to modprobe the orinoco modules. Then ifup eth0.


  I then flashed the OABI 2.6.21 kernel. On booting, it gave the error messages concerning Neil's soundhack package. More significantly it tried to load the 2.6.21 module and said it couldn't find them.  What now? Any suggestions? Anybody?

This is crazy! It said it loaded the modules this time.... Which ones?


cortez, if you are around, am I missing something simple here? Is there a script to play with?

Any way wifi is up and I'm going to do dist-upgrade and leave it to stew....

[jpmatrix]

Still trying to get OABI + OABI. I started again with the Bigbridge method. I did some twiddles to get the wifi card up. I cheated and copied my interfaces file and my sources.list to the SD card and then to BigZ.  I then used tar zxvf from the 2.6.21 modules file on the SD card to the root of the filesystem. Apparently successful.
In order to get the wifi up I had to modprobe the orinoco modules. Then ifup eth0.


  I then flashed the OABI 2.6.21 kernel. On booting, it gave the error messages concerning Neil's soundhack package. More significantly it tried to load the 2.6.21 module and said it couldn't find them.  What now? Any suggestions? Anybody?

This is crazy! It said it loaded the modules this time.... Which ones?


cortez, if you are around, am I missing something simple here? Is there a script to play with?

Any way wifi is up and I'm going to do dist-upgrade and leave it to stew....

perhaps there's an automatic depmod -a command after boot...
anyway unless you absolutely want 2.6.21, you could also flash 2.6.23 from http://www.angstrom-distribution.org/unsta...spitz/20071024/
untar the module.tgz and depmod -a
then reboot

[tux]

perhaps there's an automatic depmod -a command after boot...
anyway unless you absolutely want 2.6.21, you could also flash 2.6.23 from http://www.angstrom-distribution.org/unsta...spitz/20071024/
untar the module.tgz and depmod -a
then reboot

  JP, I'm trying to match the OABI rootfs that comes from neil and the arm Debian side of thins and an OABI kernel. This in the naive hope that the sound/multimedia things would clear up!

   

[tux]

JP, I'm trying to match the OABI rootfs that comes from neil and the arm Debian side of thins and an OABI kernel. This in the naive hope that the sound/multimedia things would clear up!
   

   I think I'll put BigZ back on lenny with the original way of setting up. I think that if I want OABI kernel + OABI rootfs, without a lot of fiddles I'll need to do a 2.6.20 OABI kernel. I have the bitbake build system. This gives me a reason to use it.  One of my experiments allowed me to set up the OABI filesystem and flash the OABI 2.6.21 kernel. The matching modules had to be transplanted after install. Too many fiddles... too little success...

So I'm thinking that if I build OABI 2.6.20, as a first attempt with bitbake, I might be able to do that experiment again with this kernel. I know that the 2.6.20 modules that Neil's installer uses are EABI. So, I don't think it will work straight away. But if I then put the OABI 2.6.20 modules in, yes I'll need to build those I suppose, as replacements for the EABI ones, the system should be able to reboot with a chance of working as well as the original. I'll still have to do manual fixes instead of using zaurus-hardware-support. When I have a working system I can tarball it and use it like the Bigbridge one. So could other people?  

That looks like a plan, but for the long term.  

For the short term, back to the original and learn it thoroughly! So unless someone comes up with a cunning plan I'm leaving off this thread.

[cortez]

cortez, if you are around, am I missing something simple here? Is there a script to play with?

Sorry, but I'm afraid I currently can't help you out. I started from scratch again, using the EABI 2.6.23 Angstrom kernel in combination with the ADS EABI rootfs.

[tux]

cortez, if you are around, am I missing something simple here? Is there a script to play with?

Sorry, but I'm afraid I currently can't help you out. I started from scratch again, using the EABI 2.6.23 Angstrom kernel in combination with the ADS EABI rootfs.

 Not a problem. The route you are going looks interesting, I don't blame you in the least.   I'm having a few brain waves about the hardware support deb.  

That'll kep me busy!