Debian Squeeze/Wheezy on NSA-310

Marvell Kirkwood based
Post Reply
fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Mon Jan 30, 2012 8:07 pm

I forgot something. For me the serial console was only possible with

|*|-|*|*|*| --> pinout on the board: |GND|NC|TX|RX|VCC|

peeter123
Posts: 37
Joined: Sun Dec 04, 2011 12:38 am
Location: Enschede, the Netherlands

Re: Debian Squeeze/Wheezy on NSA-310

Post by peeter123 » Mon Jan 30, 2012 8:09 pm

Haha, yeah TX - RX is always a bitch. It's always the question, do you look from the device you are connecting or the device you are connecting to ;)

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Tue Jan 31, 2012 1:32 am

Until now, everything works better than expected and so i am very thankful for your guide. I am not finished with installation and configuration, but i love the device. So cheap and so powerful.

At the end you describe the "apt-get full-upgrade" and i think you mean "apt-get dist-upgrade". Thank you very much.

MoTTaFuKKa
Posts: 7
Joined: Mon Jan 23, 2012 11:48 am

Re: Debian Squeeze/Wheezy on NSA-310

Post by MoTTaFuKKa » Tue Jan 31, 2012 10:34 am

Will this work on a TDC HomeDisk ?
will it remove original FW or is the FW even deeper in NAND than the flash described ?

and i guess this is a bit off topic, but will this procedure make it possible to upgrade/reflash/crossflash firmware from usb ?
A fellow HomeDisk owner contacted Zyxel's partner support and got the message that the amount of memory on a HomeDisk is insufficient to do a flash ???
(Did they put on preflashed NANDS on the board themselfs, or do they just try to make an excuse for not being allowed to support the issue ?)

Hopefull expectations, and props for the effort put in this
MoFu
*edit: Typo's*

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Tue Jan 31, 2012 12:11 pm

I am very new in this topic and a absolute novice. I could mention that it should be possible to boot another firmware from harddisk or usb, even if the memory is to insufficient. But... You know. I am a novice in this topic and i dont know the HomeDisk expect of some pictures googles a few minutes ago.

For me it was a long night with installing and configure the NSA-310 with debian and now it works like a charm. But there are some new questions by my side. Are there any news about Hardware Monitoring and control of the Fan speed?

I figured out to get sensors-detect find this:

Code: Select all

Driver `lm85':
  * Bus `mv64xxx_i2c adapter'
    Busdriver `UNKNOWN', I2C address 0x2e
    Chip `National Semiconductor LM96000 or PC8374L' (confidence: 7)
The chip-driver should be "lm85" but i think it is a kernel module, or not? I am not able to get this running. It would be a perfect device, if we figure out, how to get the control of Fan-Speed an System-Temperature, or not?

When these information are right, it should be the way like descriped here: http://forum.dsmg600.info/viewtopic.php?id=4037. insmod these modules ending with a "error inserting 'lm85.ko': -1 Invalid module format". I think because of the new kernel 3.2 i use now. Is there a chance to get it running with compiling the kernel by myself with including these modules. The log says:

Code: Select all

lm85: version magic '2.6.18.6 mod_unload ARMv5 gcc-4.3' should be '3.2.0 mod_unload ARMv5 p2v8 '
Or do you have any other ideas?

Sorry for my bad english. Reading is just fine, but writing is very hard for me.

MoTTaFuKKa
Posts: 7
Joined: Mon Jan 23, 2012 11:48 am

Re: Debian Squeeze/Wheezy on NSA-310

Post by MoTTaFuKKa » Tue Jan 31, 2012 12:52 pm

Wouldn't it be possible just to compile the module, and the put it with the existing modules and insmod/modprobe it ? instead of redoing the whole kernel

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Tue Jan 31, 2012 1:01 pm

Hmm... I think you are right. As I mentioned i am very new in these things. But it would be very cool hearing something from peeter123 about the hardware monitoring and system fan. Perhaps there are more information about that.

Edit: Cant get my hands from the Zyxel. Is it possible to get Wake-On-Lan?

peeter123
Posts: 37
Joined: Sun Dec 04, 2011 12:38 am
Location: Enschede, the Netherlands

Re: Debian Squeeze/Wheezy on NSA-310

Post by peeter123 » Tue Jan 31, 2012 3:41 pm

Because I love u guys :)

http://www.scintilla.utwente.nl/~petero ... rs-3.2.tar

*Extract to /lib/modules/3.2.0/kernel/drivers/hwmon/
*Run sudo depmod -a

Code: Select all

#sensors
lm85-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0:          +1.82 V  (min =  +0.00 V, max =  +3.32 V)
Vcore:        +1.09 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:        +3.23 V  (min =  +2.96 V, max =  +3.61 V)
+5V:          +5.03 V  (min =  +4.45 V, max =  +5.47 V)
+12V:        +12.25 V  (min =  +0.00 V, max = +15.94 V)
fan1:        4144 RPM  (min =    0 RPM)
temp1:        +30.0°C  (low  = -127.0°C, high = +127.0°C)
temp2:        +30.0°C  (low  = -127.0°C, high = +127.0°C)
temp3:        +36.0°C  (low  = -127.0°C, high = +127.0°C)
Relevant /etc/sensors3.conf

Code: Select all

chip "lm85-*" "lm85b-*" "lm85c-*" "adm1027-*" "adt7463-*" "adt7468-*" \
     "emc6d100-*" "emc6d102-*" "emc6d103-*" "emc6d103s-*"

    label in1 "Vcore"
    label in2 "+3.3V"
    label in3 "+5V"
    label in4 "+12V"

    ignore fan2
    ignore fan3
    ignore fan4

    ignore cpu0_vid

    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10
    set in3_min  5.0 * 0.90
    set in3_max  5.0 * 1.10
# Depending on how your chip is hardwired, you may or may not have
# +12V readings.
#    set in4_min 12.0 * 0.90
#    set in4_max 12.0 * 1.10
Last edited by peeter123 on Tue Jan 31, 2012 4:07 pm, edited 1 time in total.

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Tue Jan 31, 2012 4:05 pm

Wow... You are very quick. I did what you describe, but unhappily without success:

Code: Select all

root@nas-debian:/etc# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@nas-debian:/etc#

root@nas-debian:/etc# sensors lm85-i2c-0-2e
Specified sensor(s) not found!
I checked for:

Code: Select all

root@nas-debian:/etc# lsmod
Module                  Size  Used by
hwmon                    716  0
I have no idea how to fix it.

peeter123
Posts: 37
Joined: Sun Dec 04, 2011 12:38 am
Location: Enschede, the Netherlands

Re: Debian Squeeze/Wheezy on NSA-310

Post by peeter123 » Tue Jan 31, 2012 4:09 pm

Ah you also need to restart after you copied your modules. Or insmod them manually.

*sudo insmod /lib/modules/3.2.0/kernel/drivers/hwmon/hwmon.ko
*sudo insmod /lib/modules/3.2.0/kernel/drivers/hwmon/hwmon-vid.ko
*sudo insmod /lib/modules/3.2.0/kernel/drivers/hwmon/lm85.ko

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Tue Jan 31, 2012 4:40 pm

Sorry... Insmod for one of the modules failed and i downloaded the whole package again. Now everthings works perfect. I think you are responsible that the Zyxel NSA-310 is a perfect and cheap kirkwood-device for Debian.

I love you!

The last open topic is getting Wake on Lan working. With ethtool i get

Code: Select all

Supports Wake-on: pumbg
        Wake-on: g
but i can´t get this running. Did you managed WakeOnLan with the device? Another Topic for me is getting installed a Tevii S660 DVB-S2 Device (USB), but i think thats very personal wishes.

So far you did a really good job and i am really thankful for your good support.

PiotrGozdur
Posts: 6
Joined: Wed Feb 08, 2012 6:33 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by PiotrGozdur » Wed Feb 08, 2012 6:59 pm

Hi.
I made a patch for SATA Read/Write LED support. Green=read, Red=write.
This was tested on NSA310/kernel 3.2.5 with internal sata disk but should work with external too.

UPDATED PATCH (v3):
http://pastebin.com/zbvZNdx7

scoobie
Posts: 34
Joined: Wed Jan 11, 2012 11:35 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by scoobie » Thu Feb 09, 2012 1:28 pm

At the risk of sounding dumb, I will relay the issues I have with this instalation process which has failed for me om my 3 month old NSA310
I downloaded Uimage: NSA310 uImage-2.6.38.6, Uimage: NSA310 uImage-3.2 and Debian installation ramdisk: Debian 6
I set up my terminal emulator (ANSI) via hacked nokia cable - works a treat!
I first renamed 3.2 uimage and placed it and the ramdisk on a USB drive, follwed the instructions and it booted fine (thinks - plain sailing now - big mistake!)
3.2 came up and said that I needed to load a paid for network driver.
Ok - tried the same for 2.6 and I can get past that point, and barring a few errors get to the point where it will start loading debian, but it crashes saying that there are no (modules ?) available.
tried a number of mirrors - same problem.
I'm now wondering whether I needed to follow the instructions at the beginning of the guide (which I skipped) to cross-compile things.
I had assumed that the files I downloaded where the result of the compile.
Where am I going wrong?
Thanks
Mark :cry:

fynfyn
Posts: 17
Joined: Mon Jan 30, 2012 5:57 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by fynfyn » Fri Feb 10, 2012 12:10 pm

The uImage from the beginning of the thread is a result of compiling. So with the files of peeter123 there is no need to compile your own kernel. As I mentioned, i am not an expert in the topic, but perhaps i can help you, because my installation is working very well.

It would be helpful when you post your log.

scoobie
Posts: 34
Joined: Wed Jan 11, 2012 11:35 pm

Re: Debian Squeeze/Wheezy on NSA-310

Post by scoobie » Sat Feb 11, 2012 4:11 pm

Fynfyn - I appreciate your help.
This is where it appears to start going wrong -

lqqqqqqqqqqqqqqqqu [!!] Download installer components tqqqqqqqqqqqqqqqqqk
x x
x No kernel modules were found. This probably is due to a mismatch x
x between the kernel used by this version of the installer and the x
x kernel version available in the archive. x
x x
x If you're installing from a mirror, you can work around this problem x
x by choosing to install a different version of Debian. The install x
x will probably fail to work if you continue without kernel modules. x
x x
x Continue the install without loading kernel modules? x
x x
x <Go Back> <Yes> <No> x

Leading up to this point -


Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0 (peter@Ubuntu) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #6 Sat Jan 7 16:43:55 CET 2012
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Zyxel NSA-310
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xb00000,0x900000 ramdisk=32768
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 245688k/245688k available, 16456k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xd0800000 - 0xfe800000 ( 736 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc0467000 (4476 kB)
.init : 0xc0467000 - 0xc048f000 ( 160 kB)
.data : 0xc0490000 - 0xc04b7540 ( 158 kB)
.bss : 0xc04b7564 - 0xc04d6a34 ( 126 kB)
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
Power resume enabled
Power-off GPIO enabled
Kirkwood PCIe port 0:
link up
PCI: bus0 uses PCIe port 0
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
pci 0000:00:01.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
pci 0000:00:01.0: BAR 4: set to [mem 0xe0010000-0xe0013fff 64bit pref] (PCI address [0xe0010000-0xe0013fff])
pci 0000:00:01.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
pci 0000:00:01.0: BAR 2: set to [mem 0xe0014000-0xe0014fff 64bit pref] (PCI address [0xe0014000-0xe0014fff])
pci 0000:00:01.0: BAR 0: assigned [io 0x1000-0x10ff]
pci 0000:00:01.0: BAR 0: set to [io 0x1000-0x10ff] (PCI address [0x1000-0x10ff])
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 9216K
NetWinder Floating Point Emulator V0.97 (double precision)
NTFS driver 2.1.30 [Flags: R/W].
msgmni has been set to 497
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler cfq registered (default)
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000020000
----CUT CUT CUT ----
Bad eraseblock 1022 at 0x000007fc0000
Bad eraseblock 1023 at 0x000007fe0000
sched: RT throttling activated
modprobe: FATAL: Could not load /lib/modules/3.2.0/modules.dep: No such file or directory


Creating 9 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "uboot_env"
0x000000180000-0x000000200000 : "key_store"
0x000000200000-0x000000280000 : "info"
0x000000280000-0x000000c80000 : "etc"
0x000000c80000-0x000001680000 : "kernel_1"
0x000001680000-0x000004640000 : "rootfs1"
0x000004640000-0x000005040000 : "kernel_2"
0x000005040000-0x000008000000 : "rootfs2"
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address c8:6c:87:0a:ef:7e
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:00:01.0: eth1: RTL8168d/8111d at 0xd0806000, 00:00:00:00:00:30, XID 083000c0 IRQ 9
r8169 0000:00:01.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
rtc-pcf8563 0-0051: chip found, driver version 0.4.3
rtc-pcf8563 0-0051: pcf8563_get_datetime: read error
rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc1
Orion Watchdog Timer: Initial timeout 21 sec
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
modprobe: FATAL: Could not load /lib/modules/3.2.0/modules.dep: No such file or directory


usbcore: registered new interface driver snd-usb-audio
ALSA device list:
No soundcards found.
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3982 buckets, 15928 max)
ctnetlink v0.93: registering with nfnetlink.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
L2TP core driver, V2.0
8021q: 802.1Q VLAN Support v1.8
Registering the dns_resolver key type
input: gpio-keys as /devices/platform/gpio-keys/input/input0
rtc-mv rtc-mv: setting system clock to 2012-02-11 15:42:50 UTC (1328974970)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
usb 1-1: new high-speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.3: new high-speed USB device number 3 using orion-ehci
ata1.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
scsi2 : usb-storage 1-1.3:1.0
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
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 0 SControl F300)
Freeing init memory: 160K
scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sdb] 1953792 512-byte logical blocks: (1.00 GB/954 MiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
FATAL: Could not load /lib/modules/3.2.0/modules.dep: No such file or directory

Post Reply