Jump to content


Photo

ET kernel 3.8.7


  • Please log in to reply
108 replies to this topic

Re: ET kernel 3.8.7 #101 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 25 June 2013 - 20:14

je bedoelt via applicaties dan downloaden en dan naar drivers toe?



Re: ET kernel 3.8.7 #102 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 25 June 2013 - 20:18

Inderdaad

Re: ET kernel 3.8.7 #103 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 25 June 2013 - 20:24

als ik dat dus doe met twee stickjes er in blijft die hangen in bootloader

haal ik een stickje er uit dan start die wel op.... 

vervang ik dat ene bestandje waar ik het in me vorige post over had met die van kernel 3.6.0

dan start die wel op met twee stickjes er in

 

heb het net nog weer even getest


Edited by Xtrend77, 25 June 2013 - 20:26.


Re: ET kernel 3.8.7 #104 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 25 June 2013 - 20:28

Maar werken de sticks ook met die ko's van de 3.6.0 kernel?

In dat geval kan je de files vermoedelijk ook gewoon verwijderen, want volgens mij willen 3.6.0 ko's echt niet laden in een 3.8.7 kernel.

Re: ET kernel 3.8.7 #105 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 25 June 2013 - 20:32

nee ze werken niet..... maar het geeft wel aan dat er iets in die file zit wat fouten geeft zodat mijn xtrend niet wil booten toch



Re: ET kernel 3.8.7 #106 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 25 June 2013 - 20:37

ja dat klopt, maar zoals je het omschreef leek het er even op dat je bedoelde dat het met de 3.6.0 ko's zou werken, en dat leek mij vreemd ;)

Overigens blijft hij vast niet in de bootloader hangen, anders zou het niet helpen dat je de ko's verwijdert of vervangt (want de bootloader doet niks met ko's).

Dus je kan vermoedelijk gewoon inloggen (telnet), en met dmesg kijken wat hem dwars zit.
Mogelijk hangt hij op een ontbrekende firmware file bijvoorbeeld.
En als het met 2 sticks niet werkt, probeer dan eerst of je 1 werkend krijgt.

Re: ET kernel 3.8.7 #107 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 25 June 2013 - 20:39

dit geeft die weer met een stickje er in
 
dmesg
 

 

TCP bind hash table entries: 4096 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered

UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
fuse init (API version 7.20)
msgmni has been set to 567
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
sata_brcmstb 0000:01:00.0: version 4.0
__clk_enable: sata [1]
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
sata_brcmstb 0000:01:00.0: setting latency timer to 64
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac:
 registered interface #0 at 0x10080000 as 'eth0' (00:16:b4:03:6b:47)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
__clk_enable: usb [1]
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
Key type dns_resolver registered
EBI CS1: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000000
B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecf10095
After: N
andSelect=50000200, nandConfig=15142200
Block size=00020000, erase shift=17
NAND Config: Reg=15142200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
timing1 not adjusted: 5363444f
timing2 not adjusted: 00000fc6
eccLevel=15, 1Ksector=0, oob=16
nbrBitsPerCell=2, cellinfo=0, chip->cellinfo=00000000
<--brcmnand_set_acccontrol: acc b4: d7ff1010, after: d7ff1010
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS1


Found NAND on CS1: ACC=d7ff1010, cfg=15142200, flashId=ecf10095, tim1=5363444f, tim2=00000fc6
BrcmNAND version = 0x0302 128MB @00000000
B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecf10095
After: NandSelect=50000200, nandConfig=15142200
Found NAND flash on Chip Select 1, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 50000200
brcmnand_scan: After nand_select = 50000200
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 3.2 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan:  mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Bad block table Bbt0 found at page 0000ffc0, version 0x01 for chip on CS1
Bad block table 1tbB found at page 0000ff80, version 0x01 for chip on CS1
nand_read_bbt: Bad block at 0x02c40000
nand_read_bbt: Bad block at 0x05240000
nand_read_bbt: Bad block at 0x076e0000
Adjust partition complete size from entire device to 7f00000 to avoid overlap with BBT reserved space
Adjust partition rootfs size from entire device to 7900000 to avoid overlap with BBT reserved space
Creating 3 MTD partitions on "brcmnand.0":
0x000000000000-0x000007f00000 : "complete"
0x000000000000-0x000000600000 : "kernel"
0x000000600000-0x000007f00000 : "rootfs"
PM: CP0 COUNT/COMPARE frequency depends on diviso
r
UBI: attaching mtd2 to ubi0
usb 1-1: new high-speed USB device number 2 using ehci-brcm
usb 2-1: new high-speed USB device number 2 using ehci-brcm
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
usb 2-1.2: new full-speed USB device number 3 using ehci-brcm
UBI: scanning is finished
UBI: attached mtd2 (name "rootfs", size 121 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 965, bad PEBs: 3, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 752957936
UBI: available PEBs: 0, total reserved PEBs: 965, PEBs reserved for bad PEB handling: 17
ALSA device list:
  No soundcards found.
Warning: unable to open an initial console.
UBI: background thread "ubi_bgt0d" started, PID 49
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: WDC WD10EADS-22M2B0, 01.00A01, max UDMA/133
ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD10EADS-22M 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link down (SStatus 4 SControl 300)
UBIFS: background thread "ubifs_bgt0_0" started, PID 51
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"(null)
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS: FS size: 118468608 bytes (112 MiB, 933 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS: reserved for root:
 0 bytes (0 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID 5C63D1C6-DA19-4E43-BFBC-9A6D8AD17B3F, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:10.
devtmpfs: mounted
Freeing unused kernel memory: 284k freed
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda1): recovery complete
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
usbcore: registered new interface driver tpm
dvb: module_layout: kernel tainted.
Disabling lock debugging due to kernel taint
Console: switching to colour frame buffer device 160x45
input: dreambox remote control (native) as /devices/virtual/input/input0
input: dreambox advanced remote control (native) as /devices/virtual/input/input1
DVB: registering new adapter (dvb0)
platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-S2)...
input: front panel as /devices/virtual/input/input2
NET: Registered protocol family 10
em28xx: New device TERRATEC TERRATCE H5 Rev.3 @ 480 Mbps (0ccd:10b6, interface 0, class 0)
em28xx: Audio Vendor Class interface 0 found
em28xx: Video interface 0 found
em28xx: DVB interface 0 found
em28xx #0: chip ID is em2884
Unhandled kernel unaligned access[#1]:
Cpu 0
$ 0   : 00000000 10008700 00000000 0f0f0f0f
$ 4   : cdcc3000 00000000 00000004 cf091c30
$ 8   : 34383832 807b7940 00000000 20706968
$12   : 0000010c e0ffffff 00000000 00000000
$16   : cdcc3000 00000001 cdcc3000 8004be40
$20   : 00000004 00000000 e15e539c cf091c30
$24   : 00000000 e15e5360                  
$28   : cf090000 cf091bc8 cdcc34e0 e15e5388
Hi    : 00000003
Lo    : 85a3b3c0
epc   : e15e5158 em28xx_read_reg_req_len+0x48/0x250 [em28xx]
    Tainted: GF          O
ra    : e15e5388 em28xx_read_reg_req+0x28/0x3c [em28xx]
Status: 10008703    KERNEL EXL IE 
Cause : 80800010
BadVA : 0f0f0f0f
PrId  : 0002a044 (Brcm4380)
Modules linked in: em28xx(+) videobuf_vmalloc videobuf_core tveeprom ipv6 dvb(OF) modloa
der2(O) modloader(O) tpm(O)
Process modprobe (pid: 209, threadinfo=cf090000, task=cf7cdb58, tls=7736d490)
Stack : 00000006 ce7ad9c8 00000000 00000000 00000000 00000000 807b70b2 0000001c
        00000000 ffffffff cfe93400 cfe93400 00000000 cdcc3000 8004be40 80724680
        00000000 e15e539c 00000001 e15e5388 00000001 802e731c 00000000 00000000
        00000001 cf091c44 cf091c44 cfe93400 00000000 e15e481c cdcfc600 cdcc3000
        00000000 805e6ec0 00000ccd 000010b6 00000000 00000000 cff48420 cff48400
        ...
Call Trace:
[<e15e5158>] em28xx_read_reg_req_len+0x48/0x250 [em28xx]
[<e15e5388>] em28xx_read_reg_req+0x28/0x3c [em28xx]
[<e15e481c>] em28xx_usb_probe+0x97c/0xcec [em28xx]
[<8040c3d8>] usb_probe_interface+0xf8/0x234
[<8034dbc0>] driver_probe_device+0xa0/0x2bc
[<8034de98>] __driver_attach+0xbc/0xc4
[<8034bf00>] bus_for_each_dev+0x5c/0xa8
[<8034d20c>] bus_add_driver+0x1b4/0x2b0
[<8034e234>] driver_register+0x90/0x1a0
[<8040b87c>] usb_register_driver+0x90/0x17c
[<80001588>] do_one_initcall+0x160/0x1e8
[<80073fcc>] load_module+0x1a1c/0x21b4
[<80074818>] sys_init_module+0xb4/0xec
[<8000e07c>] stack_done+0x20/0x40

Code: 8fb10060  30b500ff  30d4ffff <1440004f> 8c760000  2a220051  1040004e  3c12e15f  3c038000 
---[ end trace fb6b8ffbd1cefd35 ]---
Console: switching to colour dummy device 80x25


Re: ET kernel 3.8.7 #108 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 25 June 2013 - 20:58

met twee stickjes er in blijft in de beeldscherm staan booting zie een balkje knipperen 

en als ik dan probeer in te loggen via telnet kan ik geen verbinding maken



Re: ET kernel 3.8.7 #109 Xtrend77

  • Senior Member
  • 80 posts

0
Neutral

Posted 30 June 2013 - 07:20

Het werkt nog steeds niet... heb van alles geprobeert

 

gaat ut nog eens werken als er een nieuwe kernel komt of ook niet meer?

 

 

Mvg Maikel




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users