Looks like "TheWayEnd" has done alot of damage all over the web so it's probably not a direct hit against ripper and CO.
Printable View
Looks like "TheWayEnd" has done alot of damage all over the web so it's probably not a direct hit against ripper and CO.
Now the azbox-enigma.eu site is down, so they are probably working on it.
And todays the Azbox daily update site is working again, fw.azupd.com/
All the firmware releasedates are reset, so they all show date 2010.11.12
Then all the ones that is nagging about new firmware every day can stay busy all day, trying all the "new firmwares" (ok, bad joke) :)
now we have to check _http://fw.azupd.nl/ for the original date.Quote:
Originally Posted by amyren
For the scard you have to adapt the scard patch to newer kernel.
./smp86xx_kernel_source_2.8.0.1/linux-2.6.15/README.1010.scard.patch
./smp86xx_kernel_source_2.8.0.1/pf/patches/linux-2.6.15/1010.scard.patch
Maybe this will be enough.
I am just waiting when svn goes public so I can setup proper tool chain with kernel, e2 and build tools
when drivers are stable enough :)=
Makes me wonder how the team behind the DS release got their image done..Quote:
Originally Posted by luky
Or was it just a normal 1.0.31 image with some addons and skins?
Thayt's a good question????????????Quote:
Originally Posted by amyren
please guys add the card reader. AFAIK oscam have some azbox cardreader sources.
@tx0: That takes some time to adapt patch and test the kernel. It is easy to write please do it then do it on your own. if my OE toolchain is working I'll try to fix the scard part.
That patch is included in the WDTV kernel.Quote:
Originally Posted by 4@@@@
Edit: Looking at The_Ripper's .config there's so scard patch is definitely included.
Quote:
# CONFIG_TANGOX_SCARD is not set
Sigma SCARD driver (internal smart card reader) isnt compatible with Dreambox SCI driver IOCTL commands, so Sigma driver needs patching/adjusting, 4@@@@ gave location of the source code ...
We to assume that the internal smart card reader is also turns to workQuote:
Originally Posted by The_Ripper
thanks
As far as I have seen the patches are all applied. The only thing is to uncomment
CONFIG_TANGOX_SCARD=m
I can't test it because I'm building a wrong kernel format at the moment which will not be loaded.
@4@@@@
What patches you are refer to ?
One for linux source from Sigma that enable SCARD HW interface to work
or someone else patches for Sigma SCARD driver regarding supporting Dreambox SCI IOCTL commands/work flow ?
@The_Ripper,
Does azbox E2 support ntfs write, ntfs-3g ? Latest azbox firmware runs ntfs-3g but fails to load fuse.ko.
Off topic
Quote:
by Guardian
axbox-enigma.eu up again
yep in the air again:king-042:
@The_Ripper: It looks that the patches from ./smp86xx_kernel_source_2.8.0.1/pf/patches/linux-2.6.15/1010.scard.patch are applyed in the WDTV-kernel-source.
But I have to get the kernel built not as elf to get booted to test the new modul and to see if I was right.
Now I have a working kernel - tomorrow I'll test the modules.
here is module to scard:
dmesg:
Quote:
scard: SMP86xx driver loaded (rd_buffer_size = 256, wr_buffer_size = 256, freq = 2000000, interfaces = 1)
scard0: scard present detected.
scard0: scard activation starts ..
scard0: scard present detected.
scard0: scard activation starts ..
Trap instruction in kernel code[#2]:
Cpu 0
$ 0 : 00000000 90970000 00000000 0006c300
$ 4 : c88df7d4 00000174 c88df814 00000000
$ 8 : 95205fe0 00001c00 00000000 96022000
$12 : 0887ac80 000001ce 00000009 00440001
$16 : c88e0d30 1fffffff 95205f68 00000001
$20 : c88e0d9c 00000001 900237c0 90048a68
$24 : 00000000 903bc254
$28 : 95204000 95205f58 c88ddb10 c88dea88
Hi : 00000174
Lo : ffffffff
epc : c88deac4 scard_negotiate+0x218/0x2dc [sckernel] Tainted: PF
ra : c88dea88 scard_negotiate+0x1dc/0x2dc [sckernel]
Status: 10001c03 KERNEL EXL IE
Cause : 70808034
PrId : 00019069
Modules linked in: sckernel(F) em8634dvb(PF) stv6110x stv090x cx24116 em8xxx(PF) llad(P) irvfd(P) tangox_ehci_hcd
Process scard0 (pid: 2059, threadinfo=95204000, task=967cc4b8)
Stack : c88ddb10 1fffffff a0000000 c88e0d30 ee0110ff c88e0d9c 1fffffff a0000000
c88e0d30 c88df41c 00000000 c88e0d9c a0000000 9098c3a4 c88e0dc8 c88e0fcc
c88dd620 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 90028a74 10001c03 00000000 00000000 00000000
00000000 90028a64 2d657361 702d6e65 00000068 00000011 00734000 00733fb0
...
Call Trace:
[<c88deac4>] scard_negotiate+0x218/0x2dc [sckernel]
[<c88df41c>] scard_monitor+0x894/0xaa8 [sckernel]
[<90028a74>] kernel_thread_helper+0x10/0x18
Code: 8cc20000 8e030050 00a2001b <004001f4> 3c02a000 24630030 00711824 00621825 8c640000
@buyukbang
I think I enabled all NTFS stuff inside kernel, sorry didnt tried that nor fuse usage.
@Heinz
Driver crash is in this function
at position 0x218 from function start in HEX-ASM, 0x2dc is full length of this function in HEXCode:static int scard_negotiate(struct scard_private *priv)
Code:scard_negotiate+0x218/0x2dc