yes I know.Quote:
Originally Posted by jromero
I've asked to KANBER_KAV what means"Fake pictures. Frame buffer device problem. not runing enigma2."
Printable View
yes I know.Quote:
Originally Posted by jromero
I've asked to KANBER_KAV what means"Fake pictures. Frame buffer device problem. not runing enigma2."
see visual evidence of enigma2 on azbox on islaremota site
guys, what da hell is this?
Enigma Setup. v 1.4.10, azbox ?
http://www.kosnet.ru/~elite/patch/
http://www.kosnet.ru/~elite/mpcs-i/
Yeah they most likely are fake because its really easy to output text(Booting E2) to the LED's on the front of the box using the ACC so these screenies are more crap to make people think it’s just round the corner which it will be if they manage to get the rest of the driver issues fixed but as many a development there’s always small issues like these.
Be patient it will come as soon as it runs on the box I’m sure the people working on it right now will release it ASAP
:respect-062:
what about the links that i posted? do u guys know what's that?
ЕТО ТОЛКА ДЛЈА ИПБОКС :-)Quote:
citat: Hflms
what about the links that i posted? Do u guys know what's that?
HelloQuote:
Originally Posted by arian
Those pictures are from April´s fools day.
One of them was taken from my cell phone (Booting E2) :D Not to hard to do that with AZBox Control... :sifone:
Regards
Juka
@ Hfmls : If there is a installer for enigma there will be or come enigma for Azbox. It's useless to make an installer for something wich doesn't exist... It looks like the installer works, it connect with my Azbox.
Hi,
if anybody is working on new azbox kernel and need tangoX board patches for kernel v2.6.25 please PM me.
regards, satcamd
Yes the installer may well be there but whos to say theres an E2 image that will run on the azbox as yet its just a waiting game hopefully soon
although im already putting plan B in action lol
HTPC on the way i wont sell me azbox as its a good box for what it does atm:respect-046:
great m8. nothing can beat an htpc especially linux with xbmc-pvr branch. nice choiceQuote:
Originally Posted by auldy
Quote:
Originally Posted by satcamd
I cant get why to keep the patch in secret. There is 2.6.15
patched kernel available. So wtf all these secrets? If you have *working* patch God bless you and upload it or make a torrent for all people.
If you want I can give it server space! Have unlimited bandwidth.
Psi
why do u guys want that file?
what can u do with it?
@tx0
Do you allready have the 2.6.15 patched kernel?
Or you are talking about the implemented azbox's kernel (that is a 2.6.15 kernel)?
With that kernel we can do nothing, because it's compiled without the fb (frame buffer) options and dfb (direct frame buffer) can't be implemented without fb device.
In azbox you can verify that (missing fb device) just giving the command from command linie:
fbset -i /dev/fb0.
So, for the first step we (or the development team, if it exist) have to recompile the kernel with the fb options, then recompile dfb within the mruaXXX or dccXXX having the toolchain and rootfs installed. Then compile the linuxdvb api and at last compile enigma2.
the kernel I have is hereat the bottom of the page.PHP Code:hxxp://www.networkedmediatank.com/download/firmware/nmt/gpl/
I've used it to compile some modules that successfully loaded. I haven't installed the main kernel tho but I think
that its working since compiled for 8634
Found this on *************** (by sasa76x)Quote:
Originally Posted by hfmls
http://www.kosnet.ru/~elite/patch/
To install:
Manual:
* Download the file and extract it through unpack, either:
Auto:
* Connect to the receiver via Enigma Setup
* Connect a drive through the button mount (choose the correct drive sda or sdb)
* Click the button PATCH, note the correct patch, click confirmation (patch)
* Sometimes you have to reboot the receiver to activate the patch
* Configure patch automatically produce
Enigma Setup. v 1.4.10
http://www.kosnet.ru/~elite/mpcs-i/
----------------------------------------
Don't know what that tool is for!!.... & of course I didn't make the "patch" cause I don't trust.
Attached the screen shot.
It's for IPBOX - another box that have nothing common with azbox. forget itQuote:
Originally Posted by halabessa
So how come that we have the azbox listed in "profile"? did you try the tool?Quote:
Originally Posted by tx0
By the way I followed the first 2 steps in the manual... and it works but I didn't try the "patch" step as I said before I don't know much about the source.
;)
Attached the 1st. & second manual steps (screenshots)
By the way: I have a 1TB usb hdd attached to my azbox.
:respect-052:
?????????celrun---azbox
h*tp://celrun.tv/uploadFile/down/patch_1.4.03/Patch.zip
h*tp://celrun.tv/uploadFile/down/patch_1.4.03/fb.zip
h*tp://celrun.tv/uploadFile/down/patch_ ... ersion.txt
-------------
MMPx1y2z3
-------------
????????????????????????????????? ????????????????????????????????'
:cheers2::rofl:
this isnt enigma this is celrun firmware why is this relivent?
In the fb.zip there is a file called usbupgrade, do you know the meaning of that?Quote:
Originally Posted by trool
The latest official firmware is released.
개선된 사항은 다음과 같습니다. Improvements are as follows.
- AUDIO(SPDIF 5.1CH) 디지털/아날로그 설정 오류 수정 - AUDIO (SPDIF 5.1CH) digital / analog setup error correction
- 부팅시 USB 외장하드 자동인식 하도록 수정 - Modified at boot time to automatically recognize USB External Hard Drive
- TV포탈 광고 재생 불능 현상 수정 - TV Ads Portal Fix for your inability to
- 지역방송사의 EPG정보 추출 문제 및 EPG 갱신 문제 수정 - Local broadcasters update EPG EPG information extraction problems and problem
- 동영상 코텍 안정화 (AVI 포멧 지원강화) - Video Codec Stabilization (AVI format support strengthening)
- 영화보기 중 미지원 코덱 안내 후 문제발생 현상 수정 - Unsupported codec of movie viewing guide Fix for the problem
펌웨어 설치 방법은 고객지원-> 업그레이드 항목에서 확인할 수있습니다. How to install the firmware support -> you can see from the upgrade item.
감사합니다. Thank you.
Looks like files are old.. but..
Unpack fw and use libs inside (can help) :respect-055:
I think those files are for Head Medialink ML9700 (version 1.4.03 of firmware) the other product from Celrun. Interesting for example is the file emXXXfb.ko on the directory modules from the file fb.zip (the kernel module for the frame buffer), but those are protected with password. Maybe we can compile the module by ourselves and enable the frame buffer device on Azbox and compile dfb as next (also as module).
Ciao,
em8xxxfb.ko driver is the ****(IMHO) !!
Not the reall FB hardware support driver.
Forget for serius usage!
Ok, but we even don't have it (is Celryn ****y password protected). What is your way of getting it? Recompile the kernel with fb options and dfb as next? Then how can we flash the new kernel (i only have one azbox premium and i can't prove anything on that :-), because not serial connection on that sh... receiver or modifying the original firmware?
Pass is : MMPx1y2z3
...useful....
http://wiki.opentvix.com/Sigma_Tools#SMP86XX_Toolchain
http://www.azupd.com/SDK/AZBox-Toolchain-0.1.0.tgz
:respect-057:
Can I try to update my box with this driver?Quote:
Originally Posted by The_Ripper
@voki081
You will need osdbuf_control application from MRUA package to create OSD memory buffer and then to pass some memory allocation datas that osdbuf_control app will give you after creation, to em8xxxfb.ko driver because he is attaching to that OSD memory buffer, it's simple sceleton driver, after that he use all software functions for drawing :S.
@all
Good news regarding new linux kernel 2.6.22.19-19 + libc , I menage to compile it and bring it up, some small output logs
It needs a lot of changing in startup scripts because I just copy all Azbox startup scripts so not all of this script works ...Code:
YAMON> net init
Ethernet driver for EM86XX (v1.0)
(MAC 00:02:xx:xx:xx:ec, tx_desc/rx_desc = 16/32)
em86xx_eth::open(em86xx_eth) - Full-duplex mode
em86xx_eth::open(em86xx_eth) - 100 Mbit/s
em86xx_eth ethernet start
ipaddr: 192.168.1.5
subnetmask: 255.255.255.0
gateway: 192.168.1.1
YAMON> net initpci
net have been initialized
ipaddr: 192.168.1.5
subnetmask: 255.255.255.0
gateway: 192.168.1.1
YAMON> net up
em86xx_eth ethernet start
YAMON> load -b tftp://192.168.1.3/vmlinux.bin 0***020000
About to load tftp://192.168.1.3/vmlinux.bin
Press Ctrl-C to break
................................................................
................................................................
................................................................
...........................................................
Start = 0***020000, range = (0***020000,0***7fec02), format = BINARY
Length = 0x7dec03 (8252419)
Checksum = 0xca181ecb
YAMON> go 0***020000
Linux version 2.6.22.19-19-the_ripper (root@debian) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #64 Sun Apr 4 20:33:29 CEST 2010
Configured for SMP863x (revision ES6+/RevA+), detected SMP8634 (revision ES9/RevC).
Detected CPU/System/DSP Frequencies: 300.37/200.25/300.37MHz
SMP86xx Enabled Devices under Linux/XENV 0x48000000 = 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
Valid MEMCFG found at 0x10000fc0.
CPU revision is: 00019069
Determined physical RAM map:
memory: 02fe0000 @ 10020000 (usable)
User-defined physical RAM map:
memory: 040e0000 @ 10020000 (usable)
Wasting 2098176 bytes for tracking 65568 unused pages
Initrd not found or empty - disabling initrd
On node 0 totalpages: 82176
DMA zone: 642 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 81534 pages, LIFO batch:15
Normal zone: 0 pages used for memmap
Built 1 zonelists. Total pages: 81534
Kernel command line: mem=65m console=ttyS0,115200
Primary instruction cache 16kB, 2-way, physically tagged, linesize 16 bytes.
Primary data cache 16kB, 2-way, virtually tagged, cache aliases, linesize 16 bytes
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
Using 150.188 MHz high precision timer.
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 55168k/66432k available (2564k kernel code, 11228k reserved, 427k data, 5064k init, 0k highmem)
Calibrating delay loop... 296.96 BogoMIPS (lpj=148480)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
tangox: creating TLB mapping for 0x20000000 at 0xc0000000, size 0x08000000.
PCI: Initializing SMP86xx PCI host controller
PCI: Remapped PCI I/O space 0x58000000 to 0xc8020000, size 64 kB
PCI: Remapped PCI config space 0x50000000 to 0xc8004000, size 10 kB
PCI: device 1 disabled
PCI: device 4 disabled
PCI: Configured SMP86xx as PCI slave with 128MB PCI memory
PCI: Region size is 16384KB
PCI: Map DMA memory 0x10020000-0x14100000 for PCI at 0x11000000
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Time: TANGOX clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
Created /proc/cpucache_info entry.
Tango2 frequency scaling module installed.
JFFS2 version 2.2. © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 9) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 10) is a 16550A
loop: module loaded
nbd: registered device at major 43
tango2_enet: ethernet driver for SMP863x internal mac
tango2_enet: detected phy at address 0x01
tango2_enet: mac address 00:02:xx:xx:xx:xx
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: SMP86xx Bus Mastering IDE controller
Probing IDE interface ide0...
hda: DMS55610V010, ATA DISK drive
hda: no 80 conductors cable, falling back to lower udma mode
hda: selected mode 0x42
hda: set to Ultra DMA mode 2
ide0: DMA enabled for ATA DISK hda
ide0 at 0x223c0-0x223c7,0x22398 on irq 26
hda: max request size: 128KiB
hda: 501760 sectors (256 MB) w/1KiB Cache, CHS=980/16/32, UDMA(33)
hda: hda1 hda2 hda3 hda4
physmap flash device CS2: 0x800000 at 0x48000000
CS2: Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Using physmap partition definition
Adding partition #1-#5
Creating 5 MTD partitions on "CS2: Physically mapped flash":
0x00000000-0x00020000 : "CS2-Part1"
0x00020000-0x00040000 : "CS2-Part2"
0x00040000-0x00080000 : "CS2-Par**"
0x00080000-0x00700000 : "CS2-Part4"
0x00700000-0x00800000 : "CS2-Part5"
pktgen v2.68: Packet Generator for packet performance testing.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 5064k freed
Algorithmics/MIPS FPU Emulator v1.5
mount: cannot read /proc/mounts: No such file or directory
hostname: /etc/hostname: No such file or directory
/etc/init.d/S01sysinit: line 9: /sbin/ldconfig: No such file or directory
Initializing random number generator... done.
Starting network...
udh*** (v1.5.0) started
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Sending discover...
Sending select for 192.168.1.5...
Lease of 192.168.1.5 obtained, lease time 86400
deleting routers
route: SIOC[ADD|DEL]RT: No such process
adding dns 192.168.1.1
Starting MMP custom setting...
(none) login: root
login[659]: root login on 'ttyS0'
BusyBox v1.5.0 (2010-04-04 18:30:26 CEST) multi-call binary
Ahhh yes, finally CCcam can be run with no patching, no fakeroot
PS. This is just small step people,left to compile MRUA kernel drivers/apps and to see if it will work on new kernel and on libc not anymore on uclibc. :king-041:
That's a goog job. Thank you.
So, you mange connecting to serial? Can you plese explain how do you done it? And which box are you using (elite ?).
@shklifo
Hello, yes I use serial interface because JTAG is disabled.
I got interface from my friend, I will ask him if he wants to explain how he did it.
Currently I am testing this on Elite model.
nice work, will you publish libc patches?
Hmm Libc patches ?
I didnt patched nothing regarding libc, Debian inside had allready compiled cross compiler/libc libs etc.. for mipsel CPU, I just install it and from smp86xx rootfs package point to this compiler not one from toolchain/uclibc and Makefile from rootfs package copy all libc libs files to root folder for ramfs creation.
I didnt test to much stability because kernel needs to recompiled again , I didnt activate usb and others support, I wanted first to managed to boot kernel and ramfs based on libc just to see if it works.
Kernel 2.6.22.19-19 can be downloaded from WD Live support home page.
It is patched for sigma cpu.
Great work!!!Quote:
Originally Posted by The_Ripper
:respect-051:
You are our only hope to change the face of this decoder.
I hope that at least Opensat realize the work you are doing for us and therefore also for them that they can not even fix the bugs in their miserable firmware.
thats a nice step. thank you. how did it end up with directfb?Quote:
Originally Posted by The_Ripper
Quote:
Originally Posted by The_Ripper
m8 you are greattttttttttttttttttttt best thing it's abut cccam i love u m8 :cup-006::king-041::king-041:
AFAIK Dfb was compiled for this platform about 2 yrs ago.Quote:
Originally Posted by sattommy
"AFAIK" every box has different hdmi initialization... If you say it is already compiled and working on azbox then show us...Quote:
Originally Posted by tx0