 Show Posts
|
|
Pages: [1] 2 3 ... 33
|
|
1
|
Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels
|
on: May 15, 2013, 07:00:43 PM
|
Well I tried the precompiled 3.9.2 kernel on my compiler/test eSata Sheevaplug using the script but my system did not boot. It loaded the uImage but then failed to load. I am pretty sure that the problem is that I am using EXT4 on root (/dev/sda1) and by default, I see that EXT4 is not set up either as a module or builtin.
Therefore, I am starting to build a 3.9.2 kernel with Device Tree from scratch! Its edukayshun innit!
I'm not sure what you're looking at...but it's not the config I'm using, which has always had EXT4 built-in. |
|
|
|
|
2
|
Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels
|
on: May 14, 2013, 04:04:23 PM
|
Yes the same uImage. I really do not want to use different kernel variants for my Sheevaplugs depending on the type of storage used. The built xilka kernels (at least the last time I looked at the xilka .config files) still treated eSata as a module and thus would not boot from disk as I want.
Although I havn't checked yet, yes, I think my problem is use of .dtb (flattened device tree) files for hardware in the new kernel. Taking the .config (/proc/config.gz) file from an older kernel, not using fdt, will try and use the old style hardware setup. As the SDIO is (I think) now set up in fdt, there plainly is an incompatability. With eSata, it does not seem to matter. Obviously this is something I will have to check. As I also want to get newer kernels for Tonidoplug2 (Topkick) and previously had no success with the fdt version, I will have to see how these work in 3.9+. I will also try and understand the use of fdt in u-boot and kernel as documentation is a bit scattered in my opinion.
I've just updated 3.9.2 to build sata_mv into the kernel, this should work fine for sheevaplug-esata boot from sata. The main reason that I didn't build sata_mv into the kernel before was that the standard sheeva's were hanging on boot due to missing sata hardware. That should no longer be the case with .dtb kernels. |
|
|
|
|
3
|
Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels
|
on: May 13, 2013, 10:00:29 AM
|
I have also compiled 3.9.1 for my sheevaplugs with mixed results. Three of my Sheevaplugs use eSata to boot from and 3.9.1 works fine. However I tried the same kernel on a SD card based Sheevaplug and that failed when setting up the sdio subsytem. If I had known, I should have saved the console output but I needed to return the 'plug to service ASAP so reverted to an older kernel. I did notice that the console output differed around the sdio setup between 3.6.10 and 3.9.1. I am using a newer u-boot (2012-??) than stock. I don't think Sheevaplugs use flattened device tree yet (though it seems that Guruplugs may do so). I used the cbxbiker patches (3) and used 'make oldconfig' taking the current '/proc/config.gz' as a base.
So from my limited knowledge, I would say there is a problem with the Marvell sdio in the 3.9+ kernels and looking at the kernel changelogs, plainly there are changes afoot in that area. I think someone has to get the right combination of configuration, modules and possibly code changes in the sdio area to get Sheevaplugs working with 3.9+ kernels.
You're using the kernel's on e-SATA plugs and I'm using them on the original Sheevaplug (booting from SD), so it appears that they work on both. When you say using the "same" kernel, do you mean the same uImage? If so that would be the wrong thing to do. The uImage is a merged common zImage with the appropriate .dtb appended. The .dtb is what differentiates the different models (see UPDATE-KERNEL.sh). |
|
|
|
|
4
|
Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels
|
on: May 01, 2013, 02:06:06 AM
|
|
Yes, that's correct it created a wrong uImage. I think I need to rewrite it so that a second parameter will always override the assumed device. That should take care of that. I'm sure in the meantime you could patch the script to do that.
|
|
|
|
|
5
|
Linux Stuff / Kernel / 3.9.0+ Device-tree kernels
|
on: April 30, 2013, 02:01:29 AM
|
OK, well I've been converting to devicetree based kernels for arm. This will allow me to properly support quite a few variations of the kirkwood and dove based devices, others as well (DeviceTree is awesome from a distribution standpoint). UPDATE-KERNEL.sh will work with the kernel's starting at 3.9.0, for anything prior, continue to use the older scripts. The UPDATE-KERNEL.sh is a work-in-progress, right now I know it works properly on SheevaPlug's and CuBox's. Theoretically it will work for the other variations as well, feedback would be appreciated. UPDATE-KERNEL.sh attempts to identify the device based on entries in the /proc filesystem. In those cases where it id's the device correctly, all that is necessary is "sudo ./UPDATE-KERNEL.sh 3.9.0", for devices that aren't id'd correctly "sudo ./UPDATE-KERNEL.sh 3.9.0 device-type" should work. The earliest version of UPDATE-KERNEL.sh, wasn't optimal (from a distribution standpoint), and I rewrote it to download the zImage and a corresponding .dtb file, that will be the version that you want. You can grab it from http://www.xilka.com/sheeva/tmp/UPDATE-KERNEL.sh (the version in /sheeva should be OK after the web server caches have a chance to update). Keep in mind that I haven't got auto detection setup properly for devices other than SheevaPlug, SheevaPlug-eSATA and CuBox. After you have installed a device-tree kernel, from that point on the auto-detection should work reliably since I can use entries in /proc/device-tree. |
|
|
|
|
6
|
Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available
|
on: April 30, 2013, 01:59:36 AM
|
OK, well I've been converting to devicetree based kernels for arm. This will allow me to properly support quite a few variations of the kirkwood and dove based devices, others as well (DeviceTree is awesome from a distribution standpoint). UPDATE-KERNEL.sh will work with the kernel's starting at 3.9.0, for anything prior, continue to use the older scripts. The UPDATE-KERNEL.sh is a work-in-progress, right now I know it works properly on SheevaPlug's and CuBox's. Theoretically it will work for the other variations as well, feedback would be appreciated. UPDATE-KERNEL.sh attempts to identify the device based on entries in the /proc filesystem. In those cases where it id's the device correctly, all that is necessary is "sudo ./UPDATE-KERNEL.sh 3.9.0", for devices that aren't id'd correctly "sudo ./UPDATE-KERNEL.sh 3.9.0 device-type" should work. The earliest version of UPDATE-KERNEL.sh, wasn't optimal (from a distribution standpoint), and I rewrote it to download the zImage and a corresponding .dtb file, that will be the version that you want. You can grab it from http://www.xilka.com/sheeva/tmp/UPDATE-KERNEL.sh (the version in /sheeva should be OK after the web server caches have a chance to update). Keep in mind that I haven't got auto detection setup properly for devices other than SheevaPlug, SheevaPlug-eSATA and CuBox. After you have installed a device-tree kernel, from that point on the auto-detection should work reliably since I can use entries in /proc/device-tree. |
|
|
|
|
7
|
Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available
|
on: March 24, 2013, 07:54:16 PM
|
I just downloaded your 3.8.4 kernel, which behaves much better on the guruplug server plus with the SD8686 wireless. I can now load the libertas_sdio module without errors. Alas, this gives me client mode only.
Any chance you can enable the LIBERTAS_THINFIRM module in the next builds ? I think that with this module enable, we might be able (with the appropriate thin firmware, and hostapd) to use the SD8686 equipped machines as APs (how well, I cannot say, but it seems to work for the XO project)...
Thanks.
I've just made a 3.8.4 release 2 with LIBERTAS_THINFIRM module. See if that works for you.
|
|
|
|
|
8
|
Linux Stuff / Kernel / New sheeva/dream kernels
|
on: January 21, 2013, 05:10:59 PM
|
A Massive update which brings all of the long-term kernels up to date. 3.7.4, 3.6.11, 3.4.27, 3.2.37, 3.0.60, 2.6.34.14, 2.6.32.60 are now available. For everything besides Dreamplugs: sudo ./UPDATE-SHEEVA-KERNEL.sh 3.7.4 --nandkernel (installs to nand) or: sudo ./UPDATE-SHEEVA-KERNEL.sh 3.7.4 --rootkernel (installs to /boot) For Dreamplugs: sudo ./UPDATE-DREAM-KERNEL.sh 3.7.4 (installs to /boot) Kernel and modules are available from: http://www.xilka.com/sheeva/ |
|
|
|
|
9
|
Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available
|
on: December 18, 2012, 02:47:08 AM
|
|
As far as I know the mwifiex driver is supposed to work with that hardware. I personally don't have the hardware to test it though. I'm limited to the original SheevaPlug.
I'll build a 3.7.x kernel when I get a chance. Who knows maybe that will work.
|
|
|
|
|
10
|
Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available
|
on: December 01, 2012, 01:40:47 AM
|
|
Maybe you haven't installed the firmware file? This is from the README in the mwifiex kernel source directory. If that doesn't do it you'll have to figure out who the maintainer is for mwifiex.
1) FOR DRIVER INSTALL
a) Copy sd8787.bin to /lib/firmware/mrvl/ directory,
create the directory if it doesn't exist.
b) Install WLAN driver,
insmod mwifiex.ko
c) Uninstall WLAN driver,
ifconfig mlanX down
rmmod mwifiex
|
|
|
|
|
12
|
Linux Stuff / Kernel / sheeva/dream 3.6.6 new kernel available
|
on: November 12, 2012, 06:18:40 PM
|
3.6.6 is now available. For everything besides Dreamplugs: sudo ./README-PLUG-UPDATE.sh 3.6.6 --nandkernel (installs to nand) or: sudo ./README-PLUG-UPDATE.sh 3.6.6 --rootkernel (installs to /boot) For Dreamplugs: sudo ./README-DREAM-UPDATE.sh 3.6.6 (installs to /boot) Kernel and modules are available from: http://www.xilka.com/sheeva/Features systemd, e-sata, dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp. I'm sure you may have noticed that i haven't been frequenting the forum as often. Even though I'm not here too often that doesn't mean that I'm not updating kernels. So I would recommend checking http://www.xilka.com/sheeva/ for the latest version when you decide that you want to update. Just look in http://www.xilka.com/sheeva/3/3.6 (obviously 3.6 will increment as newer versions are released) for the latest supported version and then run the README-*sh script to pull down that version. I've been busy with CuBox related items, kernel's of course and xbmc on CuBox. I've also upgraded my main server from an AMD X6@3.4 to an FX-8350@4.7. Let me tell you...the FX-8350@4.7 really flies for the type of work (X264 encoding and software compiles) that I do on it. |
|
|
|
|
14
|
Linux Stuff / Kernel / Re: sheeva/dream 3.4.5 new kernel is available
|
on: July 22, 2012, 07:20:33 PM
|
Actually, the other locations are not all OK.
Accessing the source directory results in a 502 Bad Gateway error.
And the release directory contains a directory called 2, which seems to have the cubox 3.4.5 files.
Navy...poor choice of colors. I had to bring up the page source to read it. Yes, I'm aware of the cubox/source directory issue. I have to take the time to fix it. My python server doesn't seem to like the number of files in that directory. Anyway, that is cubox source, not sheevaplug. And yes the cubox files are in a subdirectory 2 which is my new strategy for dealing with revisions. The download scripts will automatically grab the latest revision. It avoids the hassle of flushing web server caches. I'll be changing the sheevaplug download scripts to use the same strategy as soon as I can find time. |
|
|
|
|
15
|
Linux Stuff / Kernel / sheeva/dream 3.4.5 new kernel is available
|
on: July 16, 2012, 07:26:04 PM
|
3.4.5 is now available. Please update your README*.sh file as it now points to www.xilka.com. For everything besides Dreamplugs: sudo ./README-PLUG-UPDATE.sh 3.4.5 --nandkernel (installs to nand) or: sudo ./README-PLUG-UPDATE.sh 3.4.5 --rootkernel (installs to /boot) For Dreamplugs: sudo ./README-DREAM-UPDATE.sh 3.4.5 (installs to /boot) Kernel and modules are available from: http://www.xilka.com/sheeva/Features systemd, e-sata, dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp. |
|
|
|
|
