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

Karma: 38
Posts: 497


View Profile
« on: December 11, 2010, 05:11:36 PM »

2.6.36.2 is now available.

Plugapps is now mirroring the kernels on a nightly basis, so kernels won't typically show up there until the following day after the announcement.  They do have much more bandwidth than I do, so it's probably preferred to get them from Plugapps.  The README files attempt to download from Plugapps first and then fallback to sheeva.with-linux.com.

Kernel and modules are available from the following locations:

http://dev.plugapps.com/with-linux/
http://sheeva.with-linux.com/sheeva/

Features e-sata, dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp.
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #1 on: December 28, 2010, 12:04:40 PM »

cbxbiker61 et al.,

I saw folks had set up their SheevaPlug with DVB-* USB-device as e.g. streaming servers. [2,3]

I thought giving it a try with a TeVii S660 DVB-S2 box [3], but though I think I got HTS TVheadend [1] properly compiled and installed on the plug, it can't find any "TV card".

Is that kernel suitable for this exercise (compared to the settings in [5]) or should I use another one?
--
thx & cheers

[1] http://lonelycoder.com/hts/tvheadend_overview.html
[2] http://plugcomputer.org/plugwiki/index.php/Webcams
[3] http://plugcomputer.org/plugwiki/index.php/DVB-T
[4] http://www.linuxtv.org/wiki/index.php/DVB-S2_USB_Devices
[5] http://crichton.homelinux.org/~marc/downloads/sheeva-config-2.6.32.2
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #2 on: December 29, 2010, 05:07:54 AM »

Hm, same with 2.6.35.10 #2

Device is attached

root@Sheeva:~# lsusb
Bus 001 Device 002: ID 9022:d660
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


However not recognised?!

root@Sheeva:~# dmesg | grep usb
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 1-1: new high speed USB device using orion-ehci and address 2
root@Sheeva:~# dmesg | grep dvb
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #3 on: December 29, 2010, 12:58:10 PM »

I've been running powertop on my plug (kernel 2.6.36).  Here are two suggestions from powertop:

Suggestion: Enable the CONFIG_CPU_FREQ_GOV_ONDEMAND kernel configuration option.
The 'ondemand' CPU speed governor will minimize the CPU power usage while

Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.

http://cateee.net/lkddb/web-lkddb/CPU_FREQ_GOV_ONDEMAND.html
This one might save some heat by being able to throttle down a CPU.

http://cateee.net/lkddb/web-lkddb/HPET_TIMER.html
Not sure this one would be useful at all (does the guruplug/sheevaplug have a HPET timer?  can it even be enabled for a ARM processor?)
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #4 on: December 29, 2010, 03:00:30 PM »

I've been running powertop on my plug (kernel 2.6.36).  Here are two suggestions from powertop:

Suggestion: Enable the CONFIG_CPU_FREQ_GOV_ONDEMAND kernel configuration option.
The 'ondemand' CPU speed governor will minimize the CPU power usage while

Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.

http://cateee.net/lkddb/web-lkddb/CPU_FREQ_GOV_ONDEMAND.html
This one might save some heat by being able to throttle down a CPU.

http://cateee.net/lkddb/web-lkddb/HPET_TIMER.html
Not sure this one would be useful at all (does the guruplug/sheevaplug have a HPET timer?  can it even be enabled for a ARM processor?)

HPET only exists on x86.

ONDEMAND is only valid for cpu's that scale frequency.  Which the sheevaplug can't do.

Since powertop was written by Intel for Intel, quite a few of it's recommendations are x86 specific.  Someone could submit a patch to the powertop maintainers that would turn off invalid recommendations for the sheevaplug.
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #5 on: December 31, 2010, 07:25:13 AM »

Quote from: odoll
I thought giving it a try with a TeVii S660 DVB-S2 box [3], but though I think I got HTS TVheadend [1] properly compiled and installed on the plug, it can't find any "TV Adapters".

Is that kernel suitable for this exercise (compared to the settings in [5]) or should I use another one?

I guess it is, though my actual findings are based on Debian Squeeze (Linux Sheeva 2.6.32-5-kirkwood #1 Sat Dec 11 05:09:52 UTC 2010 armv5tel) to which I recently switched:

HTS Tvheadend (SVN-R5780) couldn't find the TeVii S660 DVB-S2 device neither, but I recalled, that as I still had a TerraTec Cingery DVB-T USB-adapter in my drawer (because -T coverage/signal strength is very poor where I live Wink).

However attaching it to the SheevaPlug I can see it, now :-) (thou no channels as to the above issue).

root@Sheeva:~# lsusb
Bus 001 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T² DVB-T Receiver
root@Sheeva:~# dmesg|grep usb
[   23.721107] usb 1-1: new high speed USB device using orion-ehci and address 2
[   23.871492] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[   23.880415] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[   23.889859] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0038
[   23.896610] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   23.903796] usb 1-1: Product: Cinergy T²
[   23.907819] usb 1-1: Manufacturer: TerraTec GmbH
[   23.913714] usb 1-1: configuration #1 chosen from 1 choice
[   30.794180] dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
[   30.806476] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   30.840589] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input0
[   30.855847] dvb-usb: schedule remote query interval to 50 msecs.
[   30.862727] dvb-usb: TerraTec/qanu USB2.0 Highspeed DVB-T Receiver successfully initialized and connected.
[   30.872657] usbcore: registered new interface driver cinergyT2


So I might have 'simply' a driver issue with the S660 which I have to nail down as my next task ...


* HTS_Tvheadend_w_TerraTec_Cingery.jpg (112.28 KB, 940x921 - viewed 797 times.)
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #6 on: January 01, 2011, 08:51:08 AM »

Think I got it somehow and somewhat working, now.
However I don't fully understand what's going on during the devices initialization phase:

[ 7545.111094] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 7545.261502] usb 1-1: New USB device found, idVendor=9022, idProduct=d660
[ 7545.268241] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7545.277552] usb 1-1: configuration #1 chosen from 1 choice
[ 7545.371008] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 7545.379562] usb 1-1: firmware: requesting dvb-usb-s660.fw
[ 7545.403096] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 7545.409572] dw2102: start downloading DW210X firmware
[ 7545.437008] usb 1-1: USB disconnect, address 2
[ 7545.541109] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 7545.548959] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7545.558031] DVB: registering new adapter (TeVii S660 USB)
[ 7555.801088] dvb-usb: MAC address: 40:40:40:40:40:40
[ 7555.871079] Invalid probe, probably not a DS3000
[ 7555.876041] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 7555.883975] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input0
[ 7555.899307] dvb-usb: schedule remote query interval to 150 msecs.
[ 7555.905488] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 7555.914371] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 7555.925346] usbcore: registered new interface driver dw2102
[ 7556.221092] usb 1-1: new high speed USB device using orion-ehci and address 3
[ 7556.371495] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[ 7556.380857] usb 1-1: New USB device found, idVendor=9022, idProduct=d660
[ 7556.387611] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7556.394791] usb 1-1: Product: DVBS2BOX
[ 7556.398560] usb 1-1: Manufacturer: TBS-Tech
[ 7556.405274] usb 1-1: configuration #1 chosen from 1 choice
[ 7556.414425] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 7556.422954] usb 1-1: firmware: requesting dvb-usb-s660.fw
[ 7556.439905] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 7556.446422] dw2102: start downloading DW210X firmware
[ 7556.571101] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 7556.577307] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7556.586625] DVB: registering new adapter (TeVii S660 USB)
[ 7566.831087] dvb-usb: MAC address: 00:18:bd:5c:4a:f0
[ 7566.951085] DS3000 chip version: 0.192 attached.
[ 7566.955725] dw2102: Attached ds3000+ds2020!
[ 7566.955730]
[ 7566.962037] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
[ 7566.971447] input: IR-receiver inside an USB DVB receiver as /devices/platform/orion-ehci.0/usb1/1-1/input/input1
[ 7566.982359] dvb-usb: schedule remote query interval to 150 msecs.
[ 7566.988489] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 7677.281117] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 7677.289164] usb 1-1: firmware: requesting dvb-fe-ds3000.fw
[ 7677.335611] ds3000_firmware_ondemand: Waiting for firmware upload(2)...



* HTS_Tvheadend_w_TeVii-S660.jpg (116.17 KB, 940x921 - viewed 772 times.)
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #7 on: January 01, 2011, 11:04:39 AM »

HPET only exists on x86.

ONDEMAND is only valid for cpu's that scale frequency.  Which the sheevaplug can't do.

Since powertop was written by Intel for Intel, quite a few of it's recommendations are x86 specific.  Someone could submit a patch to the powertop maintainers that would turn off invalid recommendations for the sheevaplug.


Makes sense.  Thanks for checking.
Logged

richard
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #8 on: January 01, 2011, 11:13:33 AM »

Will this work with the Guruplug?

Thanks

Rich
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #9 on: January 01, 2011, 11:45:32 AM »

2.6.36.2 is now available.


Is everything required for iSCSI target enabled again in the 2.6.36.x kernels?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #10 on: January 01, 2011, 12:48:53 PM »

2.6.36.2 is now available.


Is everything required for iSCSI target enabled again in the 2.6.36.x kernels?

No.  There won't be until the iscsi target project releases a newer version than 1.4.20.2 that supports kernels > 2.6.35.  Since 2.6.35.x is a long term support kernel it should be good to go for everything.  I can't think of any critical features .36 adds for sheevaplug.
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #11 on: January 04, 2011, 11:12:48 PM »


No.  There won't be until the iscsi target project releases a newer version than 1.4.20.2 that supports kernels > 2.6.35.  Since 2.6.35.x is a long term support kernel it should be good to go for everything.  I can't think of any critical features .36 adds for sheevaplug.


Interesting....  Before I saw your reply, I was messing around with scsi-target-utils and got my plug working as an iSCSI target...  Please don't tell my plug Smiley

Perhaps what you meant to say was that the kernel was complete but the iscsi target project userland is not compatible with the 2.6.36?
Logged

Pages: [1]
Print
Jump to: