Sign up here and you can log into the forum!

1.05.04 wdlxtv beta root.bins

The place for n00b questions, anything goes...no n00b too n00bish.

Re: 1.05.04 wdlxtv beta root.bins   

Postby xeyes » Fri Nov 11, 2011 7:50 am

Sent a donation last night. Looking forward to the newest firmware so I can access Netflix Canada.

You guys have done some awesome work here. Thanks!!
xeyes
Donor
 
Posts: 3
Joined: Wed Nov 09, 2011 5:43 am
Location: Ontario, Canada

Re: 1.05.04 wdlxtv beta root.bins   

Postby crazie » Fri Nov 11, 2011 9:26 am

Donated on the 9th and patiently waiting for my supporter upgrade.. I found the same 5.1.1 posting, and have grabbed the ext3 root bins, but am unable to get it booting.. I have 2 of these guys, and looking to get a 3rd to leave at work.. I would really like to get 5.1.1 working.. I have even tryied tagging it as -511 and telling config to use 511 tag to boot, but it always comes up with the below FW info.

Firmware
Device: WDLXTV_PLUS FW Base: 1.03.49
Current version: 0.4.7.3 Latest version: 0.5.1.1
1) WD TV Live+ running 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] USB booting 1.05.04_B_WDLXTV_Plus-0.5.1.1 [EXT3] 2) WD TV Live+ 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] 3/4) Ordering them soon.
crazie
Donor
 
Posts: 7
Joined: Tue Nov 08, 2011 10:45 pm

Re: 1.05.04 wdlxtv beta root.bins   

Postby KAD » Fri Nov 11, 2011 9:45 am

supporter upgrade will have to wait till b-rad is back, he's expected in december, and will probably have quite a log of things to catch up
as for the 5.1.1 the root tag needs to be exactly as the file ending is named

it should look something like this
Code: Select all
1.05.04_V


KAD
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: 1.05.04 wdlxtv beta root.bins   

Postby crazie » Fri Nov 11, 2011 4:49 pm

KAD wrote:supporter upgrade will have to wait till b-rad is back, he's expected in december, and will probably have quite a log of things to catch up
as for the 5.1.1 the root tag needs to be exactly as the file ending is named

it should look something like this
Code: Select all
1.05.04_V


KAD


KAD;

Got any pointers for me getting this working ? I'm currently at work, but have remote access to my network. I setup the current settings after reading your post. The previous is what I was attempting when I posted originally.

Here is the info that I used for setting up the ext3 booting.. found at http://forum.wdlxtv.com/viewtopic.php?f=3&t=491

Now if you want write access and boot from USB drive:

1) Download EXT3-BOOT-Live ( http://forum.wdlxtv.com/viewforum.php?f=10 )
2) Delete all files from USB drive and replace it with firmware files from EXT3-BOOT-LIVE
3) Make any changes to S00custom-options and smb.conf.
4) Add any additional app.bin to the USB Drive
5) Plug USB Drive into WDTV LIVE
6) Power cycle the device
7) It should now boot as EXT3-BOOT-LIVE
8) LEAVE THE USB DRIVE PLUGGED IN AT ALL TIMES

Current:

Advanced: Booting

UUID_TAG sda (port 1)
ROOT_TAG 1.05.04_V
Filename on sda root.bin

Previous:

Advanced: Booting

UUID_TAG sda (port 1)
ROOT_TAG 511
Filename on sda root.bin-511
1) WD TV Live+ running 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] USB booting 1.05.04_B_WDLXTV_Plus-0.5.1.1 [EXT3] 2) WD TV Live+ 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] 3/4) Ordering them soon.
crazie
Donor
 
Posts: 7
Joined: Tue Nov 08, 2011 10:45 pm

Re: 1.05.04 wdlxtv beta root.bins   

Postby recliq » Sat Nov 12, 2011 4:18 am

your previous config was correct, your current isn't. If your file is named just root.bin the ROOT_TAG should be empty.
­WDLXTV Project Maintainer
-:] If you like my contributions feel free to donate for a beer or a new flash drive. ...and always remember: RTFM! (README, FAQ, WIKI) [:-
User avatar
recliq
WDLXTV Team
 
Posts: 5513
Joined: Thu Apr 15, 2010 8:09 am
Location: Kiel, Germany

Re: 1.05.04 wdlxtv beta root.bins   

Postby crazie » Sat Nov 12, 2011 1:12 pm

recliq wrote:your previous config was correct, your current isn't. If your file is named just root.bin the ROOT_TAG should be empty.


I've went back to my original settings of the following, and it still isn't booting it. Does the USB need to be formatted to EXT3 or can it be fat32 ? Its currently fat32 so I can power the unit down and copy files over to it via my windows box.

Is there anyway for me to get access to the download area before b-rad gets back ? I read that donations to 2 or 3 other major developers, do they have access to update my status ?

Advanced: Booting

UUID_TAG sda (port 1)
ROOT_TAG
Filename on sda root.bin
1) WD TV Live+ running 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] USB booting 1.05.04_B_WDLXTV_Plus-0.5.1.1 [EXT3] 2) WD TV Live+ 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] 3/4) Ordering them soon.
crazie
Donor
 
Posts: 7
Joined: Tue Nov 08, 2011 10:45 pm

Re: 1.05.04 wdlxtv beta root.bins   

Postby KAD » Sat Nov 12, 2011 6:19 pm

Filename on sda root.bin-511


now that I see this I wonder where you got this or if you changed it yourself, I can't think of any downloads I've seen that are formatted that way, so I'd guess you added the -511 bit yourself

basic options, if file name is root.bin leave all advance boot settings empty and it should boot from the root.bin

if it's a tagged root.bin, don't change it and type exactly the file ending into the root tag field in webend

KAD
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: 1.05.04 wdlxtv beta root.bins   

Postby crazie » Sat Nov 12, 2011 11:49 pm

KAD wrote:
Filename on sda root.bin-511


now that I see this I wonder where you got this or if you changed it yourself, I can't think of any downloads I've seen that are formatted that way, so I'd guess you added the -511 bit yourself

basic options, if file name is root.bin leave all advance boot settings empty and it should boot from the root.bin

if it's a tagged root.bin, don't change it and type exactly the file ending into the root tag field in webend

KAD


I tagged it myself, since I was going to do testing with different version, and wanted an easy way to boot them.

The first time that I tried it, and the way I am currently trying it, is w/ blank settings and root.bin filename. It still does not boot to 0.5.1.1.

Below is a screen shot after a fresh unplug/plug of power cable of my WEC and USB root. And my settings.

http://www3.xboxapps.org/~crazie/img/wdlxtv_511.jpg
http://www3.xboxapps.org/~crazie/img/wdlxtv_511_settings.jpg

And here is dmesg from the unit.

Code: Select all
# dmesg
erver) (gcc version 4.3.2 (Sourcery G++ Lite 4.3-51) ) #13 PREEMPT Mon May 10 17                                                                                     :11:28 CST 2010
Physical map 0xc0000000 to 0x04000000, max remap/kernel size: 0x0c000000/0x18000                                                                                     000.
Configured for SMP865x, detected SMP8654 (revision unknown).
Detected CPU/System/DSP Frequencies: 499.50/333.00/333.00MHz
SMP86xx Enabled Devices under Linux/XENV 0xcfd0bcbc = 0x001b3efc
PCIHost Ethernet Ethernet1 IR FIP I2CM I2CS USB PCIDev1 PCIDev2 PCIDev3 PCIDev4                                                                                      SATA SCARD SCARD1
CPU revision is: 0001937c
FPU revision is: 01739300
Determined physical RAM map:
memory: 05000000 @ 04000000 (usable)
Modified physical map 0xc0000000 to 0x04000000, max remap/kernel size: 0x1000000                                                                                     0/0x18000000.
User-defined physical RAM map:
memory: 0c800000 @ 04000000 (usable)
Wasting 131072 bytes for tracking 4096 unused pages
Initrd not found or empty - disabling initrd
On node 0 totalpages: 16896
  DMA zone: 33 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 16863 pages, LIFO batch:3
  Normal zone: 0 pages used for memmap
Built 1 zonelists.  Total pages: 16863
Kernel command line: console=ttyS0 mem=200M
Primary instruction cache 32kB, 4-way, physically tagged, linesize 32 bytes.
Primary data cache 32kB, 4-way, physically tagged, no aliases, linesize 32 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).
Cache parity protection disabled
PID hash table entries: 2048 (order: 11, 8192 bytes)
Using 249.750 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 4, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 3, 131072 bytes)
Memory: 197872k/204800k available (3517k kernel code, 6688k reserved, 755k data,                                                                                      944k init, 0k highmem)
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 2048
NET: Registered protocol family 16
PCI: Initializing SMP86xx PCI host controller
PCI: Remapped PCI I/O space 0x58000000 to 0xc0000000, size 64 kB
PCI: Remapped PCI config space 0x50000000 to 0xc0018000, size 10 kB
PCI: Configured SMP86xx as PCI slave with 1024MB PCI memory
PCI: Region size is 131072KB
PCI: Map DMA memory 0x04000000-0x10800000 for PCI at 0x48000000
SCSI subsystem initialized
libata version 2.21 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: TANGOX clocksource has been installed.
IP route cache hash table entries: 4096 (order: 0, 16384 bytes)
TCP established hash table entries: 16384 (order: 3, 131072 bytes)
TCP bind hash table entries: 16384 (order: 2, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NTFS driver 2.1.28 [Flags: R/O].
fuse init (API version 7.8)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
tango3dog: Hardware Watchdog Timer for SMP864x/SMP865x 0.1 (def. timeout: 30 sec                                                                                     )
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
tangox_enet0: detected phy  at address 0x01
tangox_enet0: Ethernet driver for SMP864x/SMP865x internal MAC core 0: 100Mbps B                                                                                     ase at 0x26000
tangox_enet0: mac address 00:90:a9:9f:xx:xx
tangox_enet1: unable to autodetect phy
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
tangox_bmide: bmide support is disabled
k_name=Tangox SATA 0 driver=Tangox SATA 0
SATA version 0x3139302a ID 0x0 is detected
scsi0 : Tangox SATA 0
ata1: SATA max UDMA/133 cmd 0xa0023000 ctl 0xa0023020 bmdma 0xcdcdcdcd irq 49
ata1: SATA link down (SStatus 0 SControl 300)
k_name=Tangox SATA 1 driver=Tangox SATA 1
SATA version 0x3139302a ID 0x0 is detected
scsi1 : Tangox SATA 0
ata2: SATA max UDMA/133 cmd 0xa0023800 ctl 0xa0023820 bmdma 0xcdcdcdcd irq 62
ata2: SATA link down (SStatus 0 SControl 300)
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
driver tangox-ehci-hcd, 10 Dec 2004
TangoX USB initializing...
tangox-ehci-hcd tangox-ehci-hcd: TangoX USB 2.0
tangox-ehci-hcd tangox-ehci-hcd: new USB bus registered, assigned bus number 1
tangox-ehci-hcd tangox-ehci-hcd: irq 48, io mem 0xa0021400
tangox-ehci-hcd tangox-ehci-hcd: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
tangox-ohci-hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
TangoX USB was initialized.
Initializing TangoX USB OHCI Controller Membase=0xa0021500, irq=47
tangox-ohci-hcd tangox-ohci-hcd: USB Host Controller
tangox-ohci-hcd tangox-ohci-hcd: new USB bus registered, assigned bus number 2
tangox-ohci-hcd tangox-ohci-hcd: irq 47, io mem 0xa0021500
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usb 1-1: new high speed USB device using tangox-ehci-hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ieee80211_crypt: registered algorithm 'NULL'
Freeing unused kernel memory: 944k freed
sigmablock: module license 'Proprietary' taints kernel.

CS 0 vendor id 0x2c.......
CS 0 device id 0xda.......
................................................................................                                                                                     ................................................................................                                                                                     ................................................................................                                                                                     ................

********************** Parition configureations for CS 0 *******************
**** parition 1  offset [0x00000000] + size [0x00080000] = [0x00080000] ****
**** parition 2  offset [0x00080000] + size [0x00040000] = [0x000c0000] ****
**** parition 3  offset [0x000c0000] + size [0x00300000] = [0x003c0000] ****
**** parition 4  offset [0x003c0000] + size [0x00300000] = [0x006c0000] ****
**** parition 5  offset [0x006c0000] + size [0x01000000] = [0x016c0000] ****
**** parition 6  offset [0x016c0000] + size [0x00800000] = [0x01ec0000] ****
**** parition 7  offset [0x01ec0000] + size [0x05a00000] = [0x078c0000] ****
**** parition 8  offset [0x078c0000] + size [0x05a00000] = [0x0d2c0000] ****
**** parition 9  offset [0x0d2c0000] + size [0x00020000] = [0x0d2e0000] ****
**** parition 10  offset [0x0d2e0000] + size [0x00020000] = [0x0d300000] ****
**** parition 11  offset [0x0d300000] + size [0x00020000] = [0x0d320000] ****
chip_index 0 pos 0

CS 1 vendor id 0x00.......
CS 1 device id 0x00.......
nand_probe Error on chip 1 ret code -13
scsi 2:0:0:0: Direct-Access     Multi    Flash Reader     1.00 PQ: 0 ANSI: 0
sd 2:0:0:0: [sda] 3970048 512-byte hardware sectors (2033 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 3970048 512-byte hardware sectors (2033 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: unknown partition table
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
em8xxx: no version for "llad_open" found: kernel tainted.
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1613]                                                                                      init_module: begun
em8xxx0 [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_                                                                                     SMP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1464]                                                                                      identify: board as unknown subid
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1599]                                                                                      identify: device 0x8654 0x5 accepted with software tango3ES3
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1678]                                                                                      mumk_register_tasklet 0xc009c000
mumk_register_tasklet: (0) tasklet c009c000 status @c02118b4
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[0] 0xc00a4000: pE=0xc0211690 ch_idx=33 module_id=0x                                                                                     3c 0xc02116b0
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[1] 0xc00ac000: pE=0xc0211690 ch_idx=35 module_id=0x                                                                                     3c 0xc02116bc
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[2] 0xc00b4000: pE=0xc0211690 ch_idx=41 module_id=0x                                                                                     13c 0xc02116c8
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[3] 0xc00bc000: pE=0xc0211690 ch_idx=43 module_id=0x                                                                                     13c 0xc02116d4
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[4] 0xc00c4000: pE=0xc0211690 ch_idx=37 module_id=0x                                                                                     23c 0xc02116e0
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[5] 0xc00cc000: pE=0xc0211690 ch_idx=39 module_id=0x                                                                                     23c 0xc02116ec
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] m                                                                                     umk_register_channel_tasklet[6] 0xc00d4000: pE=0xc0211690 ch_idx=69 module_id=0x                                                                                     3f 0xc02116f8
em8xxx [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_S                                                                                     MP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1775]                                                                                      init_module: done. Found 1 em8xxx
ir: cannot get major number
SMP86xx ir (253:0): driver loaded (wait_period = 30ms, buffer_size = 2)
led_rst: cannot get major number
led_rst: cannot get major number
SMP86xx led_rst (252:0): driver loaded.
ufsd: driver loaded at c00f4000 built on Aug 17 2009 19:48:53
UFSD version 7.04 (Aug 17 2009, 19:47:43)
NTFS read/write support included
Hfs+/HfsX read/write support included
$Id: ufsdvfs.c,v 1.213.2.13 2009/07/29 16:43:15 shura Exp $ (LBD=ON)
Tango3 frequency scaling module installed, (standby mode supported).
UDF-fs: No VRS found
kjournald starting.  Commit interval 5 seconds
EXT3 FS on loop1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
attempt to access beyond end of device
loop2: rw=0, want=2052, limit=2048
attempt to access beyond end of device
loop2: rw=0, want=2052, limit=2048
UDF-fs: No partition found (1)
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
UDF-fs: No VRS found
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
UDF-fs: No VRS found
kjournald starting.  Commit interval 5 seconds
EXT3 FS on loop4, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
FAT: Filesystem panic (dev sda)
    fat_free_clusters: deleting FAT entry beyond EOF
    File system has been set read-only
em8xxx0 [/var/andy/WDTV/branch_bungalow_1.03.43_B_SDK385wd0/src/libs/3_8_0/mrua_                                                                                     SMP8654F_3_8_5_wd-0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:875]                                                                                      em8xxx_release: unclean exit (1 entries)
ir: Enable NEC decoder (0x00000000)
ir: Enable RC5 decoder (0x00000000)
usb_device usbdev2.1: uevent: unsupported action-string; this will be ignored in                                                                                      a future kernel version<3>usb_endpoint usbdev2.1_ep81: uevent: unsupported acti                                                                                     on-string; this will be ignored in a future kernel version<3>hub 2-0:1.0: uevent                                                                                     : unsupported action-string; this will be ignored in a future kernel version<3>u                                                                                     sb_endpoint usbdev2.1_ep00: uevent: unsupported action-string; this will be igno                                                                                     red in a future kernel version<3>usb usb2: uevent: unsupported action-string; th                                                                                     is will be ignored in a future kernel version<3>tangox-ohci-hcd tangox-ohci-hcd:                                                                                      uevent: unsupported action-string; this will be ignored in a future kernel vers                                                                                     ion<3>usb_device usbdev1.2: uevent: unsupported action-string; this will be igno                                                                                     red in a future kernel version<3>sd 2:0:0:0: uevent: unsupported action-string;                                                                                      this will be ignored in a future kernel version<3> target2:0:0: uevent: unsuppor                                                                                     ted action-string; this will be ignored in a future kernel version<3> host2: uev                                                                                     ent: unsupported action-string; this will be ignored in a future kernel version<                                                                                     3>usb_endpoint usbdev1.2_ep82: uevent: unsupported action-string; this will be i                                                                                     gnored in a future kernel version<3>usb_endpoint usbdev1.2_ep01: uevent: unsuppo                                                                                     rted action-string; this will be ignored in a future kernel version<3>usb-storag                                                                                     e 1-1:1.0: uevent: unsupported action-string; this will be ignored in a future k                                                                                     ernel version<3>usb_endpoint usbdev1.2_ep00: uevent: unsupported action-string;                                                                                      this will be ignored in a future kernel version<3>usb 1-1: uevent: unsupported a                                                                                     ction-string; this will be ignored in a future kernel version<3>usb_device usbde                                                                                     v1.1: uevent: unsupported action-string; this will be ignored in a future kernel                                                                                      version<3>usb_endpoint usbdev1.1_ep81: uevent: unsupported action-string; this                                                                                      will be ignored in a future kernel version<3>hub 1-0:1.0: uevent: unsupported ac                                                                                     tion-string; this will be ignored in a future kernel version<3>usb_endpoint usbd                                                                                     ev1.1_ep00: uevent: unsupported action-string; this will be ignored in a future                                                                                      kernel version<3>usb usb1: uevent: unsupported action-string; this will be ignor                                                                                     ed in a future kernel version<3>tangox-ehci-hcd tangox-ehci-hcd: uevent: unsuppo                                                                                     rted action-string; this will be ignored in a future kernel version<3> host1: ue                                                                                     vent: unsupported action-string; this will be ignored in a future kernel version                                                                                     <3>Tangox SATA 1 Tangox SATA 1: uevent: unsupported action-string; this will be                                                                                      ignored in a future kernel version<3> host0: uevent: unsupported action-string;                                                                                      this will be ignored in a future kernel version<3>Tangox SATA 0 Tangox SATA 0: u                                                                                     event: unsupported action-string; this will be ignored in a future kernel versio                                                                                     n<3>tty ttyS1: uevent: unsupported action-string; this will be ignored in a futu                                                                                     re kernel version<3>tty ttyS0: uevent: unsupported action-string; this will be i                                                                                     gnored in a future kernel version<3>serial8250 serial8250: uevent: unsupported a                                                                                     ction-string; this will be ignored in a future kernel version<3> platform: ueven                                                                                     t: unsupported action-string; this will be ignored in a future kernel version
1) WD TV Live+ running 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] USB booting 1.05.04_B_WDLXTV_Plus-0.5.1.1 [EXT3] 2) WD TV Live+ 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] 3/4) Ordering them soon.
crazie
Donor
 
Posts: 7
Joined: Tue Nov 08, 2011 10:45 pm

Re: 1.05.04 wdlxtv beta root.bins   

Postby crazie » Sun Nov 13, 2011 4:55 pm

So I updated my stock one to 1.05.04_B_WDLXTV.COM_WDLXTV_PLUS-0.5.1.1, and booting of the official 1.06.16 firmware bin that I stripped/created works. It appears that there might be an issue w/ 1.03.49_B_WDLXTV.COM_WDLXTV_PLUS-0.4.7.3 booting root.bin off USB. But then I guess that is why there is the 1.05.04/0.5.1.1 release.. ;)
1) WD TV Live+ running 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] USB booting 1.05.04_B_WDLXTV_Plus-0.5.1.1 [EXT3] 2) WD TV Live+ 1.05.04_B_WDLXTV_Plus-0.5.1.1 [flash] 3/4) Ordering them soon.
crazie
Donor
 
Posts: 7
Joined: Tue Nov 08, 2011 10:45 pm

Re: 1.05.04 wdlxtv beta root.bins   

Postby kkib » Fri Dec 09, 2011 1:10 pm

Donation was sent on 6/12. Anxiously waiting to upgrade to the latest version: 0.5.1.1.

Has anyone heard from b-rad yet?
kkib
Donor
 
Posts: 3
Joined: Tue Dec 06, 2011 10:18 am
Location: Montreal

PreviousNext

Return to n00b central

Who is online

Users browsing this forum: No registered users and 2 guests

cron