Quantcast
Channel: Linux Device Hacking
Viewing all 47022 articles
Browse latest View live
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 4:52 am
$
0
0
Hey, unfortunately it will take some time until I have access to my nsa310 again.

One question: is the networking device issue resolved?

Thanks for your work!
↧
Search

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 5:09 am
$
0
0
marlemion Wrote:
-------------------------------------------------------
> Hey, unfortunately it will take some time until I
> have access to my nsa310 again.
>
> One question: is the networking device issue
> resolved?
>
> Thanks for your work!

Hi marlemion!

I was not aware that the Nsa310 has networking issue, could you describe it? Also, when you have access, you could boot this with UART and check it out at the serial cosole prompt.
↧
↧

Re: PogoPlug 4: cant access external usb drive on network

August 20, 2015, 7:44 am
$
0
0
Hi
I have debian installed with your help. That is working great. Now i have a problem with external usb HD. It shows up in network. On windows machine but can not access
Thank you
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 9:10 am
$
0
0
Hey bodhi,

I already got uboot booted with UART a while ago. See this post here:

http://forum.doozan.com/read.php?3,12381,21223#msg-21223

So I will certainly will test it ASAP.

However, I did not get the network device to be initialized, as it is a different one than in NSA320 or NSA310s. See 'EDIT5' and the following in the mentioned post. The post is quite lengthy and confusing, sorry about that. :)
↧

Re: Debian on NSA320s - possible?

August 20, 2015, 10:13 am
$
0
0
with stock U-Boot: 

Marvell>> md f1010140
f1010140: 00000000 ffffffff 00000000 00000000    ................
f1010150: 00000009 00000009 00000000 00000000    ................
f1010160: 00000000 00000000 00000000 00000000    ................
f1010170: 00000000 00000000 00000000 00000000    ................
f1010180: 00000000 00000000 00000000 00000000    ................
f1010190: 00000000 00000000 00000000 00000000    ................
f10101a0: 00000000 00000000 00000000 00000000    ................
f10101b0: 00000000 00000000 00000000 00000000    ................
f10101c0: 00000000 00000000 00000000 00000000    ................
f10101d0: 00000000 00000000 00000000 00000000    ................
f10101e0: 00000000 00000000 00000000 00000000    ................
f10101f0: 00000000 00000000 00000000 00000000    ................
f1010200: 00000000 76543210 3210ba98 000100ff    .....2Tv...2....
f1010210: 00000000 00000000 00000000 00000000    ................
f1010220: 00000000 00000000 00000000 00000000    ................
f1010230: 00000000 00000000 00000000 00000000    ................
Marvell>>

Marvell>> mw.l f1010140  0x02
Marvell>>

Marvell>> md f1010140
f1010140: 00000002 ffffffff 00000000 00000000    ................
f1010150: 00000009 00000009 00000000 00000000    ................
f1010160: 00000000 00000000 00000000 00000000    ................
f1010170: 00000000 00000000 00000000 00000000    ................
f1010180: 00000000 00000000 00000000 00000000    ................
f1010190: 00000000 00000000 00000000 00000000    ................
f10101a0: 00000000 00000000 00000000 00000000    ................
f10101b0: 00000000 00000000 00000000 00000000    ................
f10101c0: 00000000 00000000 00000000 00000000    ................
f10101d0: 00000000 00000000 00000000 00000000    ................
f10101e0: 00000000 00000000 00000000 00000000    ................
f10101f0: 00000000 00000000 00000000 00000000    ................
f1010200: 00000000 76543210 3210ba98 000100ff    .....2Tv...2....
f1010210: 00000000 00000000 00000000 00000000    ................
f1010220: 00000000 00000000 00000000 00000000    ................
f1010230: 00000000 00000000 00000000 00000000    ................
Marvell>>


Marvell>> ide reset

Reset IDE: 
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: SAMSUNG SP2504C                          Firm: VT100-41 Ser#: S09QJ1GL612451      
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

Marvell>>

as you can see, only one drive is recognzied
↧
↧

Re: [SOLVED] Pogo Plug v4 blinks green then red and reboots (Thank you Bodhi)

August 20, 2015, 10:33 am
$
0
0
That was it. It worked perfectly. Thank you for the help. I was able to get the ip address and ssh back in Thank you so Much!
↧

Re: XFCE desktop on Pogoplug Debian

August 20, 2015, 10:47 am
$
0
0
brought out my inner comic :-D

There's only one thing this lacks on the E02, either a browser that supports Ghostery or a standalone file downloader that's break resistant. The company I beta test has files for me at app.box - a dropbox-style uploader that's probably real secure (and supposedly resumable but only one Windows app works and i can't afford it).

Any ideas?
↧

Re: Debian on NSA320s - possible?

August 20, 2015, 1:38 pm
↧
Search

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 1:45 pm
$
0
0
I see, it was a little bit confusing :) but this is the network problem:

Quote

EDIT5: The problem is that the NSA310 has a Realtek 8169 network chip instead of a Marvell Alaska 88E1318.

Let me know if you can ping your router at the serial prompt.
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 2:05 pm
$
0
0
I will, but it may take some time, as the nsa310 is happily running as a mini server at my parents home and I don't know yet when I will be there again.
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 2:13 pm
$
0
0
marlemion,

When you do have access the first thing to check for is which version your NSA310 is (if you don't already know).

Quote
http://zyxel.nas-central.org/wiki/Category:NSA-310
There are at least two versions of the NSA-310 'in the wild'. The rebranded TDC Homedisk, and the 'genuine' NSA-310. Yet another version was presentd at CeBIT 2007, but I never found evidence that it has actually been sold. According to the GPL sources there are at least 3 different versions, the TDC, the OBM and the SGW.

Stock u-boot envs should show the model ID. That will give us a hint where to find the source in the GPL tarball. And if you keep the serial boot log with you then you can post dmesg and/or u-boot envs here.

Also, I don't have the NSA310, but I did a sanity boot test on a GoFlex Home to verify the image. It did show the network is running, even though it has a different LAN chip.
↧

Re: XFCE desktop on Pogoplug Debian

August 20, 2015, 10:14 pm
$
0
0
Well, just to say Iceweasel doesn't run after install, but lots of people everywhere have that problem - I've seen some real small versions of Firefox too in my Thin clients on Linux but they're way earlier versions. But my policy is usually:

1. not to run Flash on any machine I care about,
2. use Ghostery with bubble alert turned off and every possible thing blocked except two Facebooks (to view comments at news-type websites only)
3. paranoid settings in general
And usually browsers like that fly - if only Midori ran ghostery I'd be set, but Firefox and Iceweasel usually can, and in addition run nice download manager addons too, a big plus.

And the name Iceweasel, it's a cool name. Not known to be particularly stable, but we don't need a browser much anyway. Still, to obsess, great GUI and I'm more enthusiastic with a pink pogoplug than I am with a newly-upgraded quadcore with 8G RAM...

5 WATTS! omg
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 10:47 pm
$
0
0 
U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56)
ZyXEL NSA310 1-Bay Power Media Server 


SoC:   Kirkwood 88F6281_A1
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0

the networking issue is still present, when setting ipaddr and serverip nothing is pingable.


as marlemion mentioned, the NSA310 has a different LAN chip. 

r8168 Gigabit Ethernet driver 8.023.00-NAPI loaded
r8168 0000:00:01.0: no MSI. Back to INTx.
 Set LED ... 
eth%d: RTL8168B/8111B at 0xd0900000, 00:00:00:00:00:30, IRQ 9


MODEL_ID=A203
This shold be the TDC Homedisk.
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 11:18 pm
$
0
0
pengu Wrote:
-------------------------------------------------------
> 
> U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56)
> ZyXEL NSA310 1-Bay Power Media Server 
> 
> 
> SoC:   Kirkwood 88F6281_A1
> DRAM:  256 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> PHY reset timed out
> MV88E1318 PHY initialized on egiga0
> Hit any key to stop autoboot:  0 
>
>
> the networking issue is still present, when
> setting ipaddr and serverip nothing is pingable.
>
>
> as marlemion mentioned, the NSA310 has a different
> LAN chip.
>
> 
> r8168 Gigabit Ethernet driver 8.023.00-NAPI
> loaded
> r8168 0000:00:01.0: no MSI. Back to INTx.
>  Set LED ... 
> eth%d: RTL8168B/8111B at 0xd0900000,
> 00:00:00:00:00:30, IRQ 9
>
>
>
> 
> MODEL_ID=A203
>
> This shold be the TDC Homedisk.

Ah! that makes a lot of sense. The orginal NSA310 network should work fine. I'll see if I can find and incorporate this TDC Homedisk version.

Was this from dmesg? 
> r8168 Gigabit Ethernet driver 8.023.00-NAPI
> loaded
> r8168 0000:00:01.0: no MSI. Back to INTx.
>  Set LED ... 
> eth%d: RTL8168B/8111B at 0xd0900000,
> 00:00:00:00:00:30, IRQ 9

And does your box has TDC label in front plate?
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 20, 2015, 11:27 pm
$
0
0
bodhi Wrote:
-------------------------------------------------------
> pengu Wrote:
> --------------------------------------------------
> -----


> > 
> > MODEL_ID=A203
> >
> > This shold be the TDC Homedisk.
>
> Ah! that makes a lot of sense. The orginal NSA310
> network should work fine. I'll see if I can find
> and incorporate this TDC Homedisk version.

no it's the seme on the original NSA310 because it uses the same LAN chip

>
> Was this from dmesg?
> 
> > r8168 Gigabit Ethernet driver 8.023.00-NAPI
> > loaded
> > r8168 0000:00:01.0: no MSI. Back to INTx.
> >  Set LED ... 
> > eth%d: RTL8168B/8111B at 0xd0900000,
> > 00:00:00:00:00:30, IRQ 9
>

dmesg on ZyXEL OS 


[    1.959239] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[    1.965135] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[    1.965291] r8169 0000:01:00.0: enabling bus mastering
[    1.965954] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.975602] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
debian


> And does your box has TDC label in front plate?

yes TDC and only SYS and HDD LED were shown
↧
Search

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 12:32 am
$
0
0
pengu,

> no it's the seme on the original NSA310 because it
> uses the same LAN chip

That's not the same LAN chip, if it shows RTL8169 

> > > r8168 Gigabit Ethernet driver 8.023.00-NAPI
> > > loaded
> > > r8168 0000:00:01.0: no MSI. Back to INTx.
> > >  Set LED ... 
> > > eth%d: RTL8168B/8111B at 0xd0900000,
> > > 00:00:00:00:00:30, IRQ 9
> 
> dmesg on ZyXEL OS 
>
> [    1.959239] r8169 0000:01:00.0: enabling device
> (0140 -> 0143)
> [    1.965135] r8169 0000:01:00.0: enabling
> Mem-Wr-Inval
> [    1.965291] r8169 0000:01:00.0: enabling bus
> mastering
> [    1.965954] r8169 0000:01:00.0 eth0:
> RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30,
> XID 083000c0 IRQ 83
> [    1.975602] r8169 0000:01:00.0 eth0: jumbo
> features [frames: 9200 bytes, tx checksumming:
> ko]
>
> debian
>
>
> > And does your box has TDC label in front
> plate?
>
> yes TDC and only SYS and HDD LED were shown

Does it have the red USB LED?
Does dmesg show PCI controller being initialized?

Please post/pastebin serial log.
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 12:41 am
$
0
0
bodhi Wrote:
-------------------------------------------------------


> That's not the same LAN chip, if it shows RTL8169

both is from the same box so ZyXEL OS uses a different driver for the same chip

http://abload.de/img/nsa310_lanbisgx.jpg

> Does it have the red USB LED? 

ls /sys/class/leds/nsa310:red:usb
.  ..  brightness  device  max_brightness  power  subsystem  trigger  uevent

> Does dmesg show PCI controller being initialized? 

dmesg | grep PCI
[    0.268538] PCI: CLS 0 bytes, default 32
[    0.913091] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.913683] PCI: bus0: Fast back to back transfers disabled
[    0.914498] PCI: bus1: Fast back to back transfers disabled
[    0.914796] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.990971] ehci-pci: EHCI PCI platform driver

lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 03)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 12:57 am
$
0
0
pengu,

> both is from the same box so ZyXEL OS uses a
> different driver for the same chip

So when you opened it, the chip inside is Marvell Alaska?

But does it "really" have a USB LED that turns red? And I should have asked "does PCI appear to be used in anything, e.g. USB 3.0".
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 1:09 am
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 1:11 am
$
0
0
Btw. even though I don't have the device here, I can confirm that my NSA310 has the same RTL chip as shown by the picture of pengu above! I saw it when I opened the case.

I'll get back to you when having more information.
↧
Viewing all 47022 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>