Re: [SlimDevices: Radio] Dead WiFi on SB Radio
Does look like the chip is still detected but is obviously not actually doing anything. Given that the firmware is a flash ROM and therefore theoretically cannot be corrupted there's likely nothing to can do here. (Linux has changed how it name Ethernet devices almost yearly since 2005 so I'm not that surprised that the WiFi is eth0/eth1. It makes just as much sense as any other naming scheme..) -Transcoded from Matt's brain by Tapatalk- -- Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with Debian+LMS 7.9.0 Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k albums.. drmatt's Profile: http://forums.slimdevices.com/member.php?userid=59498 View this thread: http://forums.slimdevices.com/showthread.php?t=108221 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Dead WiFi on SB Radio
@drmatt: thank you for the quick reply. Unfortunately the Radio has WiFi embedded in a chip on the mainboard. If it failed it's probably beyond repair. Something is clearly wrong with that puppy. I used Putty to SSH into it (connected to Ethernet of course) and there are no network related problems detected in the OS either: # dmesg [0.00] linux version 2.6.26.8-rt16 (parabu...@ec2mbubld01.idc.logitech.com) (gcc version 4.4.1 (sourcery g++ lite 2010q1-202) ) #1 preempt rt fri feb 14 09:02:51 pst 2014 [0.00] cpu: arm926ej-s [41069264] revision 4 (armv5tej), cr=00053177 [0.00] machine: logitech mx25 baby board [0.00] memory policy: ecc disabled, data cache writeback [0.00] on node 0 totalpages: 16384 [0.00] dma zone: 48 pages used for memmap [0.00] dma zone: 0 pages reserved [0.00] dma zone: 6096 pages, lifo batch:0 [0.00] normal zone: 80 pages used for memmap [0.00] normal zone: 10160 pages, lifo batch:1 [0.00] movable zone: 0 pages used for memmap [0.00] cpu0: d vivt write-back cache [0.00] cpu0: i cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [0.00] cpu0: d cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [0.00] real-time preemption support (c) 2004-2007 ingo molnar [0.00] built 1 zonelists in zone order, mobility grouping on. total pages: 16256 [0.00] kernel command line: console=ttymxc1,115200 noinitrd init=/linuxrc ubi.mtd=1 root=/dev/mtdblock:cramfs [0.00] preemptible rcu implementation. [0.00] mxc irq initialized [0.00] pid hash table entries: 256 (order: 8, 1024 bytes) [0.00] mxc gpt timer initialized, rate = 1200 [0.00] warning: clock divider has been truncated, clock error 333 [ps] per 83 [ns] [0.00] console: colour dummy device 80x30 [0.00] dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] memory: 64mb = 64mb total [0.00] memory: 61992kb available (2564k code, 248k data, 120k init) [...snip...] [0.799815] brd: module loaded [0.823273] loop: module loaded [0.826505] fec enet version 0.2 [0.831790] fec: phy @ 0x1, id 0x001cc815 -- rtl8201e [0.838814] eth0: ethernet 00:04:20:2b:bf:ca [0.844841] mxc mtd nand driver 2.5 [0.849739] nand device: manufacturer id: 0xec, chip id: 0xf1 (samsung nand 128mib 3,3v 8-bit) [0.859009] bad block table found at page 65472, version 0x01 [0.859460] bad block table found at page 65408, version 0x01 [0.859715] nand_read_bbt: bad block at 0x01ba [0.860242] searching for redboot partition table in nand 128mib 3,3v 8-bit at offset 0x7f6 [0.881056] no redboot partition table detected in nand 128mib 3,3v 8-bit [0.888143] creating 2 mtd partitions on \"nand 128mib 3,3v 8-bit\": [0.894423] 0x-0x0008 : \"redboot\" [0.903950] 0x0008-0x07f4 : \"ubi\" [...snip...] [2.779340] net: registered protocol family 17 [2.795384] msp430 1-0010: setting system clock to 1970-01-01 00:00:20 utc (20) [2.809627] vfs: mounted root (cramfs filesystem) readonly. [2.816103] freeing init memory: 120k [3.939925] ubifs: recovery needed [4.009624] ubifs: recovery completed [4.013360] ubifs: mounted ubi device 0, volume 2, name \"ubifs\" [4.019329] ubifs: file system size: 9418752 bytes (9198 kib, 8 mib, 73 lebs) [4.026691] ubifs: journal size: 1032193 bytes (1008 kib, 0 mib, 6 lebs) [4.033967] ubifs: media format: w4/r0 (latest is w4/r0) [4.039838] ubifs: default compressor: lzo [4.043969] ubifs: reserved for root: 444870 bytes (434 kib) [ 17.534662] requesting msp430 firmware msp430-0007.txt(version 0.1) [ 17.540992] firmware: requesting msp430-0007.txt [ 17.731110] msp430: firmware ok (1598) [ 20.802116] ar6000 reg code = 0x4060 [ 581.298697] eth0: enable rmii gasket [ 581.314570] eth0: config: auto-negotiation on, 100fdx, 100hdx, 10fdx, 10hdx. [ 581.331290] eth0: status: link down. [ 583.331227] eth0: status: link up, 100mbit full duplex, auto-negotiation complete. [ 583.338980] eth0: enable rmii gasket At the end, the Ethernet interface -eth0 -is up and working. WiFi registers as -eth1 -by the way, not -wlan0-, which I find a bit surprising: # ifconfig eth0 link encap:ethernet hwaddr 00:04:20:2b:bf:ca inet addr:192.168.74.47 bcast:192.168.74.255 mask:255.255.255.0 up broadcast running multicast mtu:1500 metric:1 rx packets:3623 errors:0 dropped:0 overruns:0 frame:0 tx packets:2183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 rx bytes:734990 (717.7 kib) tx bytes:877651 (857.0 kib) base address:0x8000 eth1 link encap:ethernet hwaddr 00:04:20:2b:bf:ca up broadcast multicast mtu:1500 metric:1 rx packets:6 errors:0 dropped:0 overruns:0 frame:0 tx
Re: [SlimDevices: Radio] Dead WiFi on SB Radio
Seems likely the WiFi chip is dead, so when it attempts to initiate a scan it returns right away as there is no WiFi driver loaded. (I.e. no wlan0 interface). The rest of the UI is presumably not smart enough to check for presence of the device until it attempts to configure it. I don't know if the Radio uses a daughtercard for WiFi like the Boom did but if you open it up you may find something relevant. Otherwise, I'm sure you got it cheap enough to use wired without feeling hard done by.. -Transcoded from Matt's brain by Tapatalk- -- Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with Debian+LMS 7.9.0 Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k albums.. drmatt's Profile: http://forums.slimdevices.com/member.php?userid=59498 View this thread: http://forums.slimdevices.com/showthread.php?t=108221 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
[SlimDevices: Radio] Dead WiFi on SB Radio
Hi all, does anybody know this? My Squeezebox Radio (bought on eBay as fully defective) refuses to do anything WiFi-related. It registers with Ethernet, no problem, it plays well, something appears to be wrong about WiFi though. Attempted factory and Xilinx resets, both to no avail. My observations so far: - switching to WiFi will immediately abort the scan for available networks (if it happens at all), and show that no networks could be found, although every WiFi other device is giving me 3 to 5 networks, two of which are my own. One access point is sitting less than one meter from the SBR - WiFi status info shows everything unset, and the WiFi symbol in the bottom right corner stays red all the time - entering valid WiFi information for the desired network ends in the SBR not being able to connect to it (takes ~ 30 seconds to find that out) If the WiFi chip in the Radio were defective, I would assume that the scan would still take a while to return without success, or the entire device crashing during hardware access to the WiFi chip. It seems more as if there is a driver issue and the SBR does not even attempt to make use of the WiFi hardware at all. There are no error codes being shown or anything else happening that points out anything unusual. I'm clueless. Regards and thank you all in advance! :) Joe 1x Squezeebox Classic SB2 5x Squeezebox Classic SB3 (one waiting for repair) 7x Squeezebox Boom (two waiting for repair) 1x Transporter 1.5x Controller (one waiting for repair) 1.5x Touch (one waiting for repair) JoeMuc2009's Profile: http://forums.slimdevices.com/member.php?userid=23131 View this thread: http://forums.slimdevices.com/showthread.php?t=108221 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Replace Radio screen
Okay, it's harder than i thought, sorry. The display does not show an evident model number or even manufacturer. The display module is glued into a plastic frame that covers its entire backside and most of the connector. I am afraid that digging into it will destroy something. Would be a shame as the display is fully functional. But what I found is that the Logitech G19 keyboard apparently uses the same display. So the cheapest way out might be acquiring one of them and extracting the LCD from it as described here: 'http://squeezeboxman.blogspot.de/2015/07/fixing-logitech-squeezebox-radio-white.html ' (http://squeezeboxman.blogspot.de/2015/07/fixing-logitech-squeezebox-radio-white.html) 1x Squezeebox Classic SB2 5x Squeezebox Classic SB3 (one waiting for repair) 7x Squeezebox Boom (two waiting for repair) 1x Transporter 1.5x Controller (one waiting for repair) 1.5x Touch (one waiting for repair) JoeMuc2009's Profile: http://forums.slimdevices.com/member.php?userid=23131 View this thread: http://forums.slimdevices.com/showthread.php?t=107874 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
