• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: 3.1.6 new kernel available  (Read 5103 times)
cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« on: December 21, 2011, 07:48:54 PM »

3.1.6 is now available.

For everything besides Dreamplugs:
sudo ./README-PLUG-UPDATE.sh 3.1.6--nandkernel (installs to nand)
or:
sudo ./README-PLUG-UPDATE.sh 3.1.6 --rootkernel (installs to /boot)

For Dreamplugs:
sudo ./README-DREAM-UPDATE.sh 3.1.6 (installs to /boot)

Kernel and modules are available from the following locations:
The plugapps.com mirror is back online, it'll take it a day or two to get back in sync.

http://www.plugapps.com/mirror/with-linux/
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.

The kernel source is here, for those of you who need to compile custom modules.  The availability will be limited by my 2 Gig dropbox account limit, but I will keep the most recent versions available.

http://dl.dropbox.com/u/38673799/sheeva-3.1.6-KernelSource.tar.xz
« Last Edit: December 22, 2011, 03:40:43 PM by cbxbiker61 » Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #1 on: December 22, 2011, 02:14:11 AM »

I have tested on two Dreamplugs DS2-112* and DS2-114*
The older one DS2-112* is fine

On the DS2-114*
The new wifi and bluetooth (SD8787 0x02df:0x9119) may have an easy way to make it work, but I had no luck.
I could not get wifi or bluetooth working (I tried a few different approaches).

The kernel that comes with the DS2-114* is 2.6.33.7 plus Marvell bt8xxx.ko (bluetooth) sd8xxx.ko and mlan.ko wifi modules. These all seem to work fine on the original kernel.

So where do we get the source for these drivers?

Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #2 on: December 22, 2011, 06:18:59 PM »

I have tested on two Dreamplugs DS2-112* and DS2-114*
The older one DS2-112* is fine

On the DS2-114*
The new wifi and bluetooth (SD8787 0x02df:0x9119) may have an easy way to make it work, but I had no luck.
I could not get wifi or bluetooth working (I tried a few different approaches).

The kernel that comes with the DS2-114* is 2.6.33.7 plus Marvell bt8xxx.ko (bluetooth) sd8xxx.ko and mlan.ko wifi modules. These all seem to work fine on the original kernel.

So where do we get the source for these drivers?



If it's the bt8xxx.ko, mcypt.ko and sd8xxx.ko modules you're after, then I've just rebuilt 3.1.6 with those modules.  Not sure about the mlan.ko, is mcypt.ko a replacement?

With these modules added, you'll probably have to blacklist conflicting modules.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #3 on: December 23, 2011, 01:07:00 AM »

If it's the bt8xxx.ko, mcypt.ko and sd8xxx.ko modules you're after, then I've just rebuilt 3.1.6 with those modules.  Not sure about the mlan.ko, is mcypt.ko a replacement?
With these modules added, you'll probably have to blacklist conflicting modules.

I have been building the bt8xxx.ko, mcypt.ko and sd8xxx.ko modules for your Dream kernel since 2.6.38 and they worked OK on the earlier Dreamplugs. The mlan.ko appears to be an mcypt.ko replacement.
The sd8xxx.ko and bt8xxx.ko on the new Dreamplugs have modinfos that are very different, I posted details at http://www.plugcomputer.org/plugforum/index.php?topic=6007.msg19647#msg19647.
they are also loaded as

insmod /root/mlan.ko
insmod /root/sd8xxx.ko fw_name=mrvl/sd8787_uapsta.bin


The sd8xxx.ko has the same name but is clearly nothing like its predecessor.

The interesting thing is that the new sd8xxx provides both mlan0(client) and uap0(ap mode). So it would seem that this module also obsoletes the uap8xxx patch that you provide. A brief look indicates lots of enhancements to both wifi and more so bluetooth.

My enquiries, so far, have resulted in responses like "Marvell is not prepared to release the source code for these drivers".

On the bright side, your 3.1.6 kernel is good for eeverything else on the new Dreamplug, just no bluetooth or wifi.

On the not so bright side it appears that the new Dreamplugs only have wifi available if you use the kernel provided Globalscale. This is a binary only distribution (source code free zone).

Do you have access to the sd8xxx source for the SD8787?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #4 on: December 23, 2011, 01:56:08 AM »

If it's the bt8xxx.ko, mcypt.ko and sd8xxx.ko modules you're after, then I've just rebuilt 3.1.6 with those modules.  Not sure about the mlan.ko, is mcypt.ko a replacement?
With these modules added, you'll probably have to blacklist conflicting modules.

I have been building the bt8xxx.ko, mcypt.ko and sd8xxx.ko modules for your Dream kernel since 2.6.38 and they worked OK on the earlier Dreamplugs. The mlan.ko appears to be an mcypt.ko replacement.
The sd8xxx.ko and bt8xxx.ko on the new Dreamplugs have modinfos that are very different, I posted details at http://www.plugcomputer.org/plugforum/index.php?topic=6007.msg19647#msg19647.
they are also loaded as

insmod /root/mlan.ko
insmod /root/sd8xxx.ko fw_name=mrvl/sd8787_uapsta.bin


The sd8xxx.ko has the same name but is clearly nothing like its predecessor.

The interesting thing is that the new sd8xxx provides both mlan0(client) and uap0(ap mode). So it would seem that this module also obsoletes the uap8xxx patch that you provide. A brief look indicates lots of enhancements to both wifi and more so bluetooth.

My enquiries, so far, have resulted in responses like "Marvell is not prepared to release the source code for these drivers".

On the bright side, your 3.1.6 kernel is good for eeverything else on the new Dreamplug, just no bluetooth or wifi.

On the not so bright side it appears that the new Dreamplugs only have wifi available if you use the kernel provided Globalscale. This is a binary only distribution (source code free zone).

Do you have access to the sd8xxx source for the SD8787?

No I don't.

If they're not going to release the source code, it could be bad sign for the long-term viability of the platform.  We don't need more throw-away junk.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #5 on: December 23, 2011, 02:50:52 AM »

Quote
No I don't.

If they're not going to release the source code, it could be bad sign for the long-term viability of the platform.  We don't need more throw-away junk.

I know of one group whose Dreamplug solution is based on a recent kernel and wifi, so I guess they will be looking for something new.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #6 on: December 23, 2011, 05:20:59 PM »

Another question cbxbiker does

Code:
# cat /proc/mwlan/mlan0/info
driver_name = "wlan"
driver_version = SD8787-14.57.5.p41-M2614130.p4-GPL-(FP57)
interface_name="mlan0"
...

Imply that the driver has a GPL license (at least the sd8xxx part, even if not the mlan.ko part)?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #7 on: December 23, 2011, 05:47:22 PM »

Another question cbxbiker does

Code:
# cat /proc/mwlan/mlan0/info
driver_name = "wlan"
driver_version = SD8787-14.57.5.p41-M2614130.p4-GPL-(FP57)
interface_name="mlan0"
...

Imply that the driver has a GPL license (at least the sd8xxx part, even if not the mlan.ko part)?


I'd say yes.  You could do a "strings modname.ko | grep -i gpl" to see if it's embedded in the module.

It's possible that they have the "intention" of releasing the code after they've tweeked it a bit.  Of course if it indicates GPL,  all you should have to do is request the code and they should comply.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #8 on: December 24, 2011, 04:34:44 PM »

Merry Christmas cbxbiker, and a big thank you for providing kernels to all.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #9 on: December 25, 2011, 01:39:26 PM »

Happy holidays to everyone!

I just made some oreo cookie/mandarin orange salad.  It's a big hit with my nephews.
Logged

justincormack
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #10 on: December 27, 2011, 06:25:46 AM »

3.1.6 is now available.


3.1.2 works perfectly for me (Dreamplug), but my compiled kernels from this source just hung. Used your one from the script and I finally got an oops, although it does boot:

kernel BUG at drivers/mmc/core/sdio_io.c:369!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 817 [#1] PREEMPT
Modules linked in: uap8xxx(+) snd_usb_audio snd_pcm snd_page_alloc snd_hwdep snd_usbmidi_lib snd_seq_ma
CPU: 0    Not tainted  (3.1.6 #17)
PC is at __bug+0x1c/0x28
LR is at __bug+0x18/0x28
pc : [<c000b4d0>]    lr : [<c000b4cc>]    psr: 40000013
sp : de411f60  ip : c05497b5  fp : 00000000
r10: 00000000  r9 : 00000000  r8 : 00000000
r7 : 00000001  r6 : df320000  r5 : df065600  r4 : de411f84
r3 : 00000000  r2 : de411f54  r1 : c04653b8  r0 : 00000034
Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 0005397f  Table: 1f1dc000  DAC: 00000017
Process ksdioirqd/mmc0 (pid: 1222, stack limit = 0xde410270)
Stack: (0xde411f60 to 0xde412000)
1f60: 00000005 c02d5db0 00000000 00000005 de411f84 00000007 00000002 bf136190
1f80: df065600 00000000 df8c8c00 df8c9400 7fffffff c02d6644 df0bdd40 c02d65d0
1fa0: 00000001 00000000 00000000 df0bdd30 df8c8c00 c02d65d0 00000013 00000000
1fc0: 00000000 00000000 00000000 c003bac0 00000000 00000000 df8c8c00 00000000
1fe0: de411fe0 de411fe0 df0bdd30 c003ba40 c00094b8 c00094b8 00000000 00000000
[<c000b4d0>] (__bug+0x1c/0x28) from [<c02d5db0>] (sdio_readb+0x20/0x6c)
[<c02d5db0>] (sdio_readb+0x20/0x6c) from [<bf136190>] (sbi_interrupt+0xa4/0x1e4 [uap8xxx])
[<bf136190>] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [<c02d6644>] (sdio_irq_thread+0x74/0x254)
[<c02d6644>] (sdio_irq_thread+0x74/0x254) from [<c003bac0>] (kthread+0x80/0x88)
[<c003bac0>] (kthread+0x80/0x88) from [<c00094b8>] (kernel_thread_exit+0x0/0x8)
Code: e59f0010 e1a01003 eb0e6388 e3a03000 (e5833000)
---[ end trace 3473ba6d92ee45e9 ]---


Will look into the changes between versions, but has anyone else had any issues at all?

« Last Edit: December 27, 2011, 06:28:27 AM by justincormack » Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #11 on: December 28, 2011, 08:46:02 PM »

I have had no issues with 3.1.6 (my build using cbxbikers .config).
Can I ask what the serial number is?
DS2-11??

Fill in the ??
Logged

justincormack
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #12 on: December 30, 2011, 04:41:16 AM »

I have had no issues with 3.1.6 (my build using cbxbikers .config).
Can I ask what the serial number is?
DS2-11??

Fill in the ??

DS2-1131-001217
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #13 on: January 01, 2012, 06:30:07 PM »

More testing. I have issues with 3.1.6 and 3.1.5, you are not alone.
Logged

Pages: [1]
Print
Jump to: