Heads up!

I'll release kernel 3.14 build hopefully in about a week.
http://www.phoronix.com/scan.php?page=news_item&px=MTYzNDg

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Can the dvb_demux.h header file be included in the header file? I need it to compile the dvbhdhomerun program...

http://sourceforge.net/apps/trac/dvbhdhomerun/wiki/Building

Termo Wrote:
-------------------------------------------------------
> Can the dvb_demux.h header file be included in the
> header file? I need it to compile the dvbhdhomerun
> program...
>
> [url=http://sourceforge.net/apps/trac/dvbhdhomerun
> /wiki/Building]http://sourceforge.net/apps/trac/dv
> bhdhomerun/wiki/Building[/url]

It should be in there already.

-bodhi
===========================
[color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Forum Wiki[/url][/color]
[url=https://mibodhi.blogspot.com]bodhi's corner (buy bodhi a beer)[/url]



Edited 1 time(s). Last edit at 03/23/2014 06:46PM by bodhi.

Hi Bodhi.

I can't find it.

"find /usr/src/linux-headers-3.13.1-kirkwood-tld-2/ -name dvb_demux.h" return nothing...

anyhow I found a very nice updated fork of dvbhdhomerun that takes care of this change in the newer debian kernels, by pulling down the headers from https://github.com/torvalds/linux/

For others that need to compile the dvbhdhomerun module on newer kernels please use this fork:
https://github.com/h0tw1r3/dvbhdhomerun

The only problem I had now was that the <include mach/irqs.h> in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/irq.h points to a file that is not there. I found an irqs.h file for kirkwood and put it in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/mach/ and everything compiled...


Best regards
Termo

Termo,

Could you post the lsmod output when you got your modules running? I might have missed some config options (I'm not running DVB on my plugs).

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

My lsmod output:

Module                  Size  Used by
dvb_hdhomerun_fe        5691  2 
dvb_hdhomerun          11495  4 
dvb_hdhomerun_core      1993  2 dvb_hdhomerun_fe,dvb_hdhomerun
dvb_core               75539  1 dvb_hdhomerun
ext4                  447033  1 
jbd2                   86895  1 ext4
ipv6                  288370  48 
hmac                    2441  0 
orion_wdt               2993  0 
sha1_generic            1760  0 
sha1_arm                3397  0 
mv_cesa                10625  0 
ext2                   58385  1 
mbcache                 5678  2 ext2,ext4
sg                     20647  0 
sd_mod                 34456  4 
crc_t10dif              1032  1 sd_mod
crct10dif_common        1126  1 crc_t10dif
usb_storage            36835  3 
scsi_mod              157867  3 sg,usb_storage,sd_mod

Thanks Termo.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel 3.14.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

My Pink Pogogplug hangs after the booting message.
For testing I installed
Debian-3.13.1-kirkwood-tld-2-rootfs-bodhi.tar.bz2 .

Before I was using Debian Wheezy with 3.2 kernel. Now I cannot even boot my old system.

Could anyone help please?


U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
No link on egiga0
ping failed; host 192.168.2.2 is not alive
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/uImage" from usb device 0:1 (usbda1)
2399792 bytes read
Loading file "/uInitrd" from usb device 0:1 (usbda1)
6568066 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.13.1-kirkwood-tld-2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2399728 Bytes = 2.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.13.1-kirkwood-tld-2
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6568002 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.




#####
My environment variables

u-boot>> env print
arcNumber=3542
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0
x01100000
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /uImage; ext2load usb 0:1 0x0
1100000 /uInitrd
bootdelay=3
ceboardver=PPV2
cesvcid=2LMC9A3VZFLQTQ54Y6L26ZMW42
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:59:FB
fileaddr=1000000
filesize=DDC600
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.2.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.2.2
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2859/131068 bytes
u-boot>>

elcaramba,

Do these 2 things:

1. Make sure you have extracted the rootfs to a USB drive as root user, as stated in the instruction (sudo won't work). If you did not, then redo the rootfs.
2. Take your rootfs drive to anothe Linux box and fsck it for errors.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/05/2014 06:14PM by bodhi.

Hi bodhi,

thank you for the quick reply.

I checked your recommendations.
1) the rootfs was extracted from a livecd as running user root.
2) fsck -f on the usb partition was run with success and no errors.
BTW: In the provided rootfs I had to copy uInitrd and uImage from /boot to / to start with the predefined boot command as defined in the environment variables.

I wonder if the environment variables arcNumber and machid have any effect. I also tried with different arcNumbers {2097, 2998, 3542} and machid {dd6, bb6}

Any other ideas? I also tried finding another version of u-boot binary, but I could not find anything which would fit to the pinkpogo.

elcaramba,

bootargs env looks wrong. Substitue $(bootargs_console) then you got only console=ttyS0,115200

bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2 
bootargs_console=console=ttyS0,115200 
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0x01100000

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello bodhi,

indeed the bootargs were wrong.
I had to adjust them. Now I can boot even my old system again.

I appreciate your support! Thank you!

During the recovery process I observed that most of the time the boot process of linux was interrupted by failed fsck checks. (Here caused by unavailable USB disk which were referenced in the fstab)

Is there a way to have a netconsole active during the boot process. This would make the maintenance task much easier.

Best,
elcaramba

Hi bodhi,

on the iConnect I was able to test the 3.14 kernel this weekend, everything is
running smoothly, however the dvb-usb-dw2102 driver was not able to recognize the usb-id of the tt-s2-4600,..
(i.e 0b48:3011 from Technotrend ),

the other device I could test is the 0ccd:00a8 TerraTec dvb-s2 usb card, this is working fine so far,..

when I applied the linux-3.14.0-tld-1-kirkwood.patch in a dry run on a plain
3.14 source tree, in this combined patch everything applied well, except that the part for the dw2102.c patch was missing,
(which explains the missing usb id's),..

the test of my tt-s2-4600 patch on the 3.14 kernel revealed rejects with dw2102.c,..

I am going to have a closer look into that in the next days and will resend the patch to you when the
problems are solved,

best wishes pbg4



Edited 2 time(s). Last edit at 04/08/2014 02:59PM by pbg4.

Hi pbg4,

My bad :) I should have consulted with you earlier (I totally forgot to do that), when I saw this and I assumed that the patch was already in the mainline (the date of the file is the same).

patching file drivers/media/usb/dvb-usb/dw2102.c
Reversed (or previously applied) patch detected!  Assume -R? [n] n
Apply anyway? [n] n

Please create a patch for this when you're ready and let me know, I'll repatch it to build linux-3.14.0-tld-2.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/06/2014 04:33PM by bodhi.

Just updated kernel to 3.14 on my pogo E02, and it seems to work great - thank you for your work!!

I still have the weird issue of two header files when I compile my dvbhdhomerun kernel module. It is the timex.h and the irq.h header files in the /include/asm.

timex.h http://lxr.free-electrons.com/source/arch/arm/include/asm/timex.h:
Has the line

#include <mach/timex.h>

to a file that does not exist. This can be solved by changing it to

#include <asm/timex.h>

and by this refering to it self?!?

irq.h http://lxr.free-electrons.com/source/arch/arm/include/asm/irq.h:
Has the line

#include <mach/irqs.h>

to a file that does not exist. I have found this file for kirkwood online somewhere and put it in /asm/mach/ , but the line also needs to be changed to

#include <asm/mach/timex.h>

for the compiler to find it correctly.

I guess you should include the correct /asm/mach/irqs.h file for kirkwood right? In regards of the others issues should they be filed as bugs on debian?

Regards
Termo

elcaramba,

Unfortunately, not without serial console. With netconsole, we can see a good part of the boot process, but rootfs mounting activities won't show. Yes, it's a bit of a hassle to figure out problem with bootargs and rootfs mouting. The reason is that network is halt by U-Boot before booting kernel. So even though it is there in the log, but we can't see it with netconsole.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Termo,

It is indeed a weird problem because the kernel was built fine! I wonder what's in the dvbhdhomeru module code that triggers the error. I agree, it does seem to me they are bugs. Please file as bugs and see what people will say.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I've uploaded a new kernel 3.14 build that supports the Netgear Stora:

linux-image-3.14.0-kirkwood-tld-2_2.0_armel.deb
md5:
ea79aa9ee167a8105c95947660b75e49

Anyone with the Stora, please try this and post feedback if it works for you, and if there is any problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bodhi,

First of all, thank you for your work! I have installed kernel 3.14 on my Pogoplug E02 and it works great.

However, when I tried to install the Realtek driver for my USB Wifi stick I got this error:

make ARCH=armv5tel CROSS_COMPILE= -C /lib/modules/3.14.0-kirkwood-tld-1/build M=/root/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911  modules
make: *** /lib/modules/3.14.0-kirkwood-tld-1/build: No such file or directory.  Stop.
make: *** [modules] Error 2

Is there a way to compile kernel modules like this driver?

lukami,

Which driver do you need for this USB wifi stick? RTL8188C or RTL8192C? have you tried other simlar modules currently in the kernel?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

The adapter is TP-LINK TL-WN725N. I beleive it uses the 8188eu chip. I downloaded the driver from here: link.


Which existing modules do you think I could use for this adapter?

lukami

lukami,

The module is named r8188eu.

Try

modprobe r8188eu

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Rootfs Debian-3.14.0-kirkwood-tld-1 was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel linux-3.14.0-kirkwood-tld-2 package was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello! My NSA310S on this kernel doesn't power off completly, only HDD turned off but rest of device is still on. How fix it ?

karolp,

Please post in this NSA325 thread:
http://forum.doozan.com/read.php?2,14351

Somebody might have ideas how to troubleshoot this. Even though this kernel has NSA310 patch, it is basically still untested (not enough feedback, so I have no idea if it works well or not).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi,

the latest Kernel linux-3.14.0-kirkwood-tld-2 package uploaded recently now includes
support for some additional tevii, terratec and technotrend dvb-s2 devices based on
the latest patch which I have send to bodhi before building the new kernel package,

on my iConnect everything is working fine so far,.. those users of bodhi's kernel package who are interested
to test the driver, please run modinfo dvb-usb-dw2102 after the latest linux-3.14.0-kirkwood-tld-2 package
is installed, to verify wether usb device and vendor id of your dvb-s device are supported, the list is rather long by now:

Drivers for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-C 3101 USB2.0, TeVii S600, S630, S650, S660, S480, S421, S632, S662, S482 Technotrend S2-4600, Terratec Cinergy S2 USB BOX, Terratec Cinergy S2 PCIe Dual, Prof 1100, 7500 USB2.0, Geniatech SU3000, T220 devices,...

basically the patch relies on https://bitbucket.org/CrazyCat/s2-liplianin-v39 i.e. crazycat's fork of the s2-liplianin repo,

however since kernel 3.14 introduced the new rc-core framework, where all the legacy remote keymap definitions
inside the dw2102.c driver have been moved outside and transformed to rc-core keymap modules in drivers/media/rc/keymaps, there was some additional coding necessary to get this working again, e.g. rc-tt-4600.ko now is loaded
for the technotrend tt-s2-4600 device within the rc-core framework,... etc.,.. there is also some more debug output
concerning the frontend/decoder attach of ts2012 and ds3103, which sometimes has timing issues,..

as I can only test two devices which are currently used in my setup on the iConnect (a terratec cinergy s2 usb hd
and the tt-s2-4600 from technotrend, which are both working fine including built in remotes,..)
please report back your findings for other users,..

best wishes pbg4

A (very, very) small matter

Hi bodhi,

first of all, thanks once more for all the effort you are putting into supporting our little toys!

I just germanized and beautified your basic install, as I always do to get my own base system. It booted ok, can't say anything about stability, though. Will test VDR on it soon.

One thing is strange, however. Compared with the last of your kernels I used before (3.8.11-tld3), 3.14.0-tld2 seems to think that there is no processor and it runs with 0,00 BogoMIPS (see the attached screenshots, both taken with the same Pogo E02 running).

I traced this back to cpuinfo, which still shows the processor, but no BogoMIPS (so linuxlogo must compute the number of processors from the number of lines it sees containing BogoMIPS info, which seems a bit silly, but whatever):

With the new 3.14.0-tld2 (no BogoMIPS line):

┌─[root@debian-bodhi-314-basic-de]─[~]
└──> cat /proc/cpuinfo
processor	: 0
model name	: Feroceon 88FR131 rev 1 (v5l)
Features	: swp half thumb fastmult edsp 
CPU implementer	: 0x56
CPU architecture: 5TE
CPU variant	: 0x2
CPU part	: 0x131
CPU revision	: 1

Hardware	: Pogoplug E02
Revision	: 0000
Serial		: 0000000000000000

With the old 3.8.11-tld3:

┌─[root@debian-bodhi-3811-basic-de]─[~]
└──> cat /proc/cpuinfo 
processor	: 0
model name	: Feroceon 88FR131 rev 1 (v5l)
BogoMIPS	: 1191.11
Features	: swp half thumb fastmult edsp 
CPU implementer	: 0x56
CPU architecture: 5TE
CPU variant	: 0x2
CPU part	: 0x131
CPU revision	: 1

Hardware	: Pogoplug E02
Revision	: 0000
Serial		: 0000000000000000

Also tested on a Dockstar for good measure and, as expected, the same thing happens. While this (as I said) is a very small matter only, it would still be interesting to know what the reason is?

Cheers,

chessplayer

---
Standart ist der Standardfehler

Hi chessplayer,

> I just germanized and beautified your basic install, as I always do to get my own base system.

Cool :)

Thanks for pointing out, I did not notice that. Will take a look, perhaps something has changed in the mainline code. And you probably refered to this above: the same info can be extracted from dmesg, too.

root@tldDebian:~# dmesg | grep -i bogomips
[   19.633692] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)