Re: What current NAS platform is recommended for installing Debian?

[Björn Wetterbom]

Excellent news. Need to consider a replacement for my current box when
armel reaches end of life.

(Skickat från min telefon == Sent from my phone)

On Dec 3, 2016 20:51, "Romain Francoise" <rfranco...@debian.org> wrote:

> On Sat, Dec 03, 2016 at 07:49:40PM +0100, Björn Wetterbom wrote:
> > Does the Debian installer work on the Intel Qnaps?
>
> Yes, there's a standard AMI BIOS which lets you select the boot device,
> and you can install Debian on the main drives (the built-in 512MB USB
> DOM is a bit small). You just need to pick a model w/ HDMI out.
>
> --
> Romain Francoise <rfranco...@debian.org>
> https://people.debian.org/~rfrancoise/
>
>

Re: What current NAS platform is recommended for installing Debian?

[Björn Wetterbom]

Does the Debian installer work on the Intel Qnaps?

(Skickat från min telefon == Sent from my phone)

On Dec 3, 2016 6:33 PM, "Romain Francoise"  wrote:

> On Sat, Dec 03, 2016 at 04:53:23PM +0100, Victor Hooi wrote:
> > However, I'm curious - what platforms or units do people recommend
> > these days?
>
> The QNAP TS-251C can be found for around 180€ in Europe right now and it
> has a dual-core CPU, 1GB of RAM, an HDMI port, and everything works
> right out of the box: fan control, temperature sensors, etc. But of
> course it's an Intel Atom so it runs amd64, which may not be what you're
> looking for. Still, a great little box to run Debian on.
>
> --
> Romain Francoise 
> https://people.debian.org/~rfrancoise/
>
>

Re: How to instaal empty hdd debian for seagate personal cloud

[Björn Wetterbom]

See http://lmgtfy.com/?q=seagate+personal+cloud+debian

On Wed, Sep 28, 2016 at 8:35 AM, Mikronet Bilgi İşlem <
mikronetbilgiis...@gmail.com> wrote:

> Hi
> My seagate personal cloud hdd was died.
> I want to install debian but i don't now how to install emty hdd
> please help me, thanks.
>

Re: Summary of the ARM ports BoF at DC15

[Björn Wetterbom]

On Fri, Sep 11, 2015 at 5:58 PM, Steve McIntyre  wrote:

> Summary: if people care about armel for Stretch, they should make
> noise NOW and convince people it's needed and can/should be supported
> in future.
>

I'd hate to see my two QNAP NAS:es unsupported. Setting them up again with
new hardware would really be a pain. I'm ever so grateful for the hard work
done by all of the Debian team.

/Björn

Re: Latest Debian for Sheevaplug?

[Björn Wetterbom]

You should start at

http://cyrius.com/debian/kirkwood/sheevaplug/

I think you'll find everything you need there.

(Skickat från min telefon == Sent from my phone)
On Mar 25, 2015 5:50 PM, Gilles codecompl...@free.fr wrote:

 Hello

 I'm no expert and would like to upgrade a Sheevaplug to the latest
 stable release of Debian.

 Sheevaplug manufacturer GlobalScale provides two files:

 Sheeva-Debian7-SW.rar
 sheevaplug_env.tar.rar
 http://globalscaletechnologies.com/download/

 Should I go ahead with those files or are there better alternatives?

 Also, to minimize use of the NAND flash memory and the SD card, I'd
 like to keep /tmp and other temporary files in RAM. Is this OK?

 Thank you.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 https://lists.debian.org/bgp5ha1mq2tsrub363ee03bvh92s09u...@4ax.com

Re: QNAP 219 P II, Luks, Debian

[Björn Wetterbom]

On Thu, Aug 14, 2014 at 12:09 AM, peng li...@f2f10.com wrote:

 So, here's my test.

 1. Sole relying U-boot/kernel/initramd, with /root on hard disk, I can
 enter passphrase for luks (for /root), but will land in shell and complain
 lacking of /dev/ram.
 2. Creating a seperate /boot either on harddisk or separate usb disk, with
 /boot on luks on harddisk, I can enter passphrase for luks , but will land
 in shell and it complains lacking of /dev/ram.
 3. without luks, it works.

 So, What seems to have caused this problem of not making luks work?

 Put /boot on a separate, unencrypted, partition formatted with ext2 and it
should work. I have had that running myself on Qnap TS-419. AFAICT you
haven't tried that. Why you are able to enter a passphrase, I don't know.


 The other question is, whether the following are correct boot sequence?
 U-boot Kernel on flash--initramd on flash-- /boot/kernel on hard
 disk and /boot/initramd on harddisk --- /root.

 or
 U-boot Kernel on flash--initramd on flash-- --- /root.

 This is the correct sequence. /boot is only used when flash-kernel writes
the kernel and ramdisk to flash.


 On a typical linux system, it would be , Grub---/boot/kernel+initramd on
 hardisk/root.

 Please help to clarrify.

 thakns

 peng


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/0ed514927fab186ca35c1e80eb3eb7
 3...@f2f10.com

Re: QNAP 219 P II, Luks, Debian

[Björn Wetterbom]

On Sat, Aug 9, 2014 at 8:17 PM, peng li...@f2f10.com wrote:

 Hi All,
 I followed http://www.cyrius.com/debian/kirkwood/qnap/ts-219/ and
 converted my NAS to Debian. I tried the following,

 1. raid0 (1G) as swap(encrypted as well with random key) and raid1 (rest
 of 2x1T); luks on raid1; lvm on luks; /root and /home on lvm
 2. raid0 (1G) and raid1 (rest of 2x1T); lvm on luks; /root and /home on
 lvm.


 Seceraio  2 works. sceraio 1 doesn't. Even I was able to put in passphrase
 during initial boot via console, it's landing in initram sys mode.


I don't understand the difference between the two scenarios, your
description is not very clear.


 My intention is to have a fully encrypted NAS. I thought that
 kernel/initramdisk on the internal Flash of NAS (which was instralled by
 installer script) would good enough to serve as function of a seperate
 /boot (which would host kernel/initramdisk image). It seems not so.

 My question is , do we still have to rely on /boot on disk (be it on
 Harddisk or a seperate usb), even we have kernel/initramd on the flash, to
 make this full encryption working?


I would assume yes. If you encrypt /boot, flash-kernel will write an
encrypted kernel to flash, and it will not be able to decrypt itself.


 many thanks
 Peng



 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/75a5756e1ecab2e6bffce1d2c8f959
 1...@f2f10.com

Re: Encrytion on a QNAP

[Björn Wetterbom]

On Tue, Jun 24, 2014 at 7:56 PM, Ian Campbell i...@hellion.org.uk wrote:

 On Tue, 2014-06-24 at 17:18 +0200, Lee Williams wrote:


Lee, are you on the list or should we continue to cc?

 Hello,
 
 
  since I have to reinstall my NAS on a new HDD, I thought it would be a
  good idea to set up encryption this time. But I'm not sure how exactly
  I should start on this.
 
 
  I think the standard way to do this is using the dm-crypt facilities
  built into the Debian installer. Now, will this work with a headless
  machine where I can't enter anything on boot time?

 That was my thought too. Out of the box? Probably not.


If you have serial console, it will work OOTB. I've done it on the
SheevaPlug and it worked just fine entering the passphrase on the console.




  If it's possible to disable SWAP and encrypt /home,

 The installer will allow this I think (you'll need to ignore the warning
 about no swap)


You can encrypt swap too, but you use the option to generate a random key
at every boot (the option is available in the installer). There are plenty
of guides around, just Google it.



   could it be mounted remotely after boot?

 You'd likely have to arrange for all that yourself and you'd be going
 pretty far of the beaten track I think, which probably means hacking
 something up yourself (even after googling for prior art would be my
 guess) but if you are willing to spend the time making it work it ought
 to be possible in theory.


I've done this too, and it's not even hard. What you do is put dropbear in
the initrd so you can ssh to the box pre-boot-time and enter the
passphrase. Look e.g. at
https://www.google.com/search?q=dropbear%20in%20initrd



   And what about services that run on those volumes, they should surely
  start after the mount, shouldn't they?

 They would certainly normally start after the mount, but if you were
 deferring the mount somehow then you might need to arrange to defer
 those services too. Or otherwise to stall the boot process until things
 were remotely enabled somehow.

  Finally, is this even a good idea? Will it cost too much performance?
  I'm using a TS-119 and am not sure if any crypto would be accelerated.

 TS-119 is kirkwood based I think, so there is some hardware acceleration
 (md5, sha-1, aes) and an associated kernel driver (mv_cesa). I don't
 know to what extent that is useful for dm-crypt etc though (md5
 obviously not so much ;-)).


If you use the installer, as I have, your performance will suffer severely.
I used it for a torrent box, which was fine, but if you e.g. plan to stream
HD content it's another story completely. I never tried custom kernels or
the like.

Good luck
Björn



 Ian.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 https://lists.debian.org/1403632594.1829.25.ca...@dagon.hellion.org.uk

Re: Information needed from owners/users of Debian on ARM/kirkwood base QNAP devices (should take 1min to gather)

[Björn Wetterbom]

On Tue, Jun 17, 2014 at 9:49 AM, Ian Campbell i...@hellion.org.uk wrote:

 Hello,

 TL;DR: Please run the attached kirkwood-qnap script on your ARM based
 QNAP systems as ./kirkwood-qnap --info and report the results in this
 thread along with the model/kind of your QNAP device (as precisely as
 you can).


 Device # 1: Qnap TS-419P II 
$ ./kirkwood-qnap --info
Kernel: Linux rockan 3.2.0-4-kirkwood #1 Debian 3.2.57-3+deb7u2
armv5tel GNU/Linux
cpuinfo:Hardware: QNAP TS-41x
dt model:   n/a

PCI devices:
00:00.0 0600: 11ab:6282 (rev 01)
00:01.0 0100: 11ab:7042 (rev 02)
01:00.0 0600: 11ab:6282 (rev 01)
01:01.0 0c03: 1b6f:7023 (rev 01)

PHY devices (/sys/bus/mdio_bus/devices/):
0:00  0:01

Soc Bus:n/a

QNAP TS-41x
kirkwood-qnap: machine: QNAP TS-41x
kirkwood-qnap: success: PCI = kirkwood-ts419-6282.dtb
kirkwood-qnap: success: PHY = kirkwood-ts419-6282.dtb

 Device # 2: Qnap TS-119 
$ ./kirkwood-qnap --info
Kernel: Linux geten 3.2.0-4-kirkwood #1 Debian 3.2.57-3+deb7u2
armv5tel GNU/Linux
cpuinfo:Hardware: QNAP TS-119/TS-219
dt model:   n/a

PCI devices:

PHY devices (/sys/bus/mdio_bus/devices/):
0:08

Soc Bus:n/a

QNAP TS-119/TS-219
kirkwood-qnap: machine: QNAP TS-119/TS-219
kirkwood-qnap: success: PHY = kirkwood-ts219-6281.dtb

Re: Dropping armel/ixp4xx

[Björn Wetterbom]

On Mon, Apr 14, 2014 at 3:02 AM, Ben Hutchings b...@decadent.org.uk wrote:

 The ixp4xx kernel is now too big to fit in the flash partitions:

 https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armelver=3.14-1~exp1stamp=1397151242

 I intend to disable this flavour for the next upload of 3.14 and remove
 it for 3.15 if no-one provides a configuration fix.

 Does this mean that ixp4xx won't be supported in jessie?


 Ben.

 --
 Ben Hutchings
 I say we take off; nuke the site from orbit.  It's the only way to be sure.

Re: U-Boot on QNAP TS-421

[Björn Wetterbom]

On Wed, Feb 12, 2014 at 12:14 PM, Gordan Bobic gor...@bobich.net wrote:

 TS-421 doesn't save it's u-boot variables on NAND. As
 far as I can tell, they are always saved on a virtual
 MTD partition (mtdblock4) in RAM, and overwritten on
 every boot with the presets hard-coded in the u-boot
 binary (mtdblock0).


Can't you just do 'saveenv' in u-boot after setting your variables? I
haven't tried it on the TS-421, but on several other u-boots.

Re: Unable to boot QNAP TS-119 since update on 12 Nov

[Björn Wetterbom]

I can make my ts 119 kernel image available for download. Would that help?
It's wheezy.

(Skickat från min telefon == Sent from my phone)
On Nov 15, 2013 6:25 PM, Martin Michlmayr t...@cyrius.com wrote:

 * Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-15 16:39]:
  I was following debian testing on a QNAP TS 119. Since the update
  late on 12 Nov 2013, I am unable to boot the device. While I haven't
  been able to root cause my problems, I suspect it might have to do
  with the kernel update included in that version.

 I take it you have no serial console?

  Is there any well known way to re-flash a current debian kernel without
 wiping the contents of the HD?

 You can generate a recovery image with the old kernel from disk.
 I thought there were intructions for this on my web site but I just
 checked and there aren't. :(

 --
 Martin Michlmayr
 http://www.cyrius.com/


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/20131115172439.ge3...@jirafa.cyrius.com

Re: Removing lvm and crypto from rootfs

[Björn Wetterbom]

 Are you sure flash-kernel got called by update-initramfs (it should on
 wheezy).

 How did you configure u-boot?  Maybe you're passing a root parameter
 via u-boot.

  Yeah, I checked all that. After trying *really* hard to figure out how
the initramfs hooks for lvm2 and cryptsetup work I ended up chrooting into
the rootfs and doing apt-get purge cryptsetup lvm2 dropbear. That removed
all the hooks in /usr/share/initramfs-tools. After that I did
update-initramfs -u again and all was ok.

Removing lvm and crypto from rootfs

[Björn Wetterbom]

Hello list!

I'm having an issue with my sheevaplug. Previously it booted off an
encrypted lvm. I have now rsynced the entire rootfs to a standard partition
on a usb stick and I am trying to get it to boot.

My strategy is to update the initramfs from a chroot, inspired by this:
http://www.cyrius.com/journal/debian/orion/d-link/dns-323/fix-initramfs-tools

I have updated /etc/fstab and replaced all occurrences of /dev/mapper/vg-lv
with the UUIDs of the partitions. However, after running update-initramfs
-u, it still tries to boot from my old lvm, which obviously fails. There is
something more than /etc/fstab that needs to be changed.

I'm guessing I need to fiddle with the hooks for initramfs-tools, but I am
completely unfamiliar with that. Any hints?

TIA
B

Re: Debian on QNAP 419P II

[Björn Wetterbom]

Just wanted to report a successful install. Compared to my old TS209 the
throughput increased vastly. I have a gigabit network and with the TS209 I
got about 140 Mbit/s (RAID1 with two disks). Now I get about 700 Mbit/s
(RAID6 with four disks). Tests were performed with iperf against a very
capable Dell laptop with SSD, Win 7 and Cygwin. Just for kicks I'm going to
try a RAID0 with four disks to see if I can push that number even higher.

BTW Martin, on http://cyrius.com/debian/kirkwood/qnap/ts-41x/uboot/ it's
not enough to set 'ipaddr'. You also have to set 'eth1addr'. They have to
be both set, I don't know why. I ended up using 'fatload' instead (inspired
by http://cyrius.com/debian/kirkwood/sheevaplug/install/), which is easier
and faster IMO.

/Björn


On Thu, Oct 17, 2013 at 3:26 PM, Martin Michlmayr t...@cyrius.com wrote:

 * Björn Wetterbom bj...@wetterbom.se [2013-10-17 15:16]:
  How right you are. Well, Martin is a thorough guy, so I'm sure it's not
  there by accident, i.e. it's supported.

 Obviously not thorough enough. ;)  I'll add it to the index and install
 pages.

 --
 Martin Michlmayr
 http://www.cyrius.com/

Debian on QNAP 419P II

[Björn Wetterbom]

Would I have any problems installing Debian on said device? It's not
specifically mentioned on cyrius.com as far as I can tell.

I've done several installs before and know how to use serial.

/B

Re: Debian on QNAP 419P II

[Björn Wetterbom]

How right you are. Well, Martin is a thorough guy, so I'm sure it's not
there by accident, i.e. it's supported.

Just found one at a good price and offered the seller SEK 4500 (roughly €
490, £ 410) for it, including 4*2TB disk. Let's see how it goes. It's about
time to replace my good old TS-209.

/B


On Thu, Oct 17, 2013 at 3:06 PM, Ian Campbell i...@hellion.org.uk wrote:

 On Thu, 2013-10-17 at 14:40 +0200, Björn Wetterbom wrote:
  Would I have any problems installing Debian on said device? It's not
  specifically mentioned on cyrius.com as far as I can tell.

 The information at http://www.cyrius.com/debian/kirkwood/qnap/ts-41x/
 applies to this one I'm reasonable sure.

 It's listed in the link to that page at
 http://www.cyrius.com/debian/kirkwood/qnap/ but not on the page itself
 AFAICT.

 Ian.

Re: Sheevaplug hangs after u-boot upgrade

[Björn Wetterbom]

The same happened to me. See my pasted mail to Martin below.

B

---

Hi Martin!

I recently upgraded u-boot according to
http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/, which went
smoothly. But after the install the plug would not boot beyond
uncompressing the kernel. Eventually I realised that it used the kernel in
nand since I hadn't updated the bootargs.

So, it would be helpful to add to the upgrade instructions that the
bootargs are reset on upgrade and that they have to be set again according
to http://www.cyrius.com/debian/kirkwood/sheevaplug/install/.

(Skickat från min telefon == Sent from my phone)
On Sep 20, 2013 6:18 PM, willem de jong willemdej...@gmx.net wrote:

 Hi All,

 After upgrading u-boot from original u-boot 1.1.x to lastest following
 Martin's guide exactly:
 http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/

 The sheevaplug hangs at 'done, now booting the kernel'.
 Output is below. It seems the IDE disc is not being recognized. The setup
 was working fine before, 2 years without a reboot.
 Can anyone point me in the right direction please?

 Thanks
 Willem


 U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
 Marvell-Sheevaplug - eSATA - SD/MMC

 SoC:   Kirkwood 88F6281_A0
 DRAM:  512 MiB
 WARNING: Caches not enabled
 NAND:  512 MiB
 In:serial
 Out:   serial
 Err:   serial
 Net:   egiga0
 88E1116 Initialized on egiga0
 Hit any key to stop autoboot:  0

 NAND read: device 0 offset 0x10, size 0x40
  4194304 bytes read: OK
 (Re)start USB...
 USB:   Register 10011 NbrPorts 1
 USB EHCI 1.00
 scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... EHCI timed out on TD -
 token=0x2008d80
 1 Storage Device(s) found

 Reset IDE: ide_preinit failed
 ## Booting kernel from Legacy Image at 0640 ...
Image Name:   Linux-2.6.22.18
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:2106696 Bytes = 2 MiB
Load Address: 8000
Entry Point:  8000
Verifying Checksum ... OK
Loading Kernel Image ... OK
 OK

 Starting kernel ...

 Uncompressing
 Linux
 done, booting the kernel.

Re: Will it work for QNAP 420?

[Björn Wetterbom]

I can't imagine that would be a problem. I'm running samba + raid1 on a
5-year-old (ish) ts-209 without any problems. It's got a 500 MHz CPU iirc.

My only issue is that I only get about 1 MB/s throughput on a Gbit LAN. But
I haven't yet had the time to isolate the issue, so I'm not sure the
problem is with the ts-209.

Even my Asus rt-n66u router can do samba+transmission+openvpn (not tried it
though), so you should be fine.

/B


On Tue, Aug 27, 2013 at 1:04 PM, George Sedov radist.mo...@gmail.comwrote:

 Hi guys,

 Thanks for your replies.

 I have another question: everybody tells me that ARM processors are a
 way too slow for raid5+samba+transmission+openvpn, but the only
 information I got on ARM's performance is that Marvell's 1.6 GHz
 kirkwood chips are close to atom N270.

 I guess you have some practical experience with ARMs, can you tell me if
 Marvell's chips will be able to run all these tasks?

 Cheers,
 George


 В Сб, 24/08/2013 в 08:39 +0200, Martin Michlmayr пишет:
  * George Sedov radist.mo...@gmail.com [2013-08-23 19:27]:
   1) First of all, will it work?
 
  Yes, see http://www.cyrius.com/debian/kirkwood/qnap/ts-41x/
 
   3) Can I install rootfs not on the SATA drives, but rather on the usb
   flash-stick, thus leaving all of the drives completely system-free?
 
  Yes, that's supported.
 
   4) Will I manage all this without any experience with debian? :) I used
   gentoo for several years though.
 
  As long as you have experience with Linux, you should be fine.  I
  wouldn't recommend it to people new to Linux, though.



 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/1377601499.2244.9.ca...@atlassedov2.desy.de

Re: Will it work for QNAP 420?

[Björn Wetterbom]

Having the root file system on a usb flash drive will work fine. I would
advice you to get two identical sticks and dd the data from your installed
stick to a backup stick once installation is finished. Usb sticks tend to
wear over time. They last 2-3 years for me.

/B


On Fri, Aug 23, 2013 at 9:26 PM, Hoshpak mailingl...@pozimski.eu wrote:

 Am 23.08.2013 20:23, schrieb Shawn Landden:
  On Fri, Aug 23, 2013 at 10:27 AM, George Sedov radist.mo...@gmail.com
 wrote:

  3) Can I install rootfs not on the SATA drives, but rather on the usb
  flash-stick, thus leaving all of the drives completely system-free?
  Maybe there are some other ways to keep the system off the disks?
 
  i'm wondering how they do it with only 16MB of flash anyways, you
 could
  always netboot it via tftp from u-boot

 Only kernel, initrd and uboot are installed into the internal flash
 memory. If you use the original Qnap firmware, they only have a pretty
 minimal system installed by default and install the bigger part of the
 firmware onto the harddrives once you plug them in and run the
 initialization wizard.

 If you use the Debian installer, you have the option to use the
 harddrives for the root file system or some other attached storage like
 an usb drive. I use the later option with my Qnap TS219 P II and it
 works fine. Since the 420 doesn't seem to be that different (probably
 the same chipset with minor modifications), I don't see a reason why it
 wouldn't work with this device also.

 Kind Regards
 Helmut


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/5217b773.1090...@pozimski.eu

Re: Dropping support for the smallest armel machines

[Björn Wetterbom]

Dropping support for nslu2 is fine with me. As noted above, I can continue
running it with an older kernel and be equally happy. Or I could retire it
and get (another) rpi.

What would be (a little) worse for me though is dropping orion5 support. I
rely on security updates for my ts-209. OTOH, by 2016 it may well be ready
to be replaced by something faster.

/B


On Wed, Jun 26, 2013 at 11:29 AM, Martin Guy martinw...@gmail.com wrote:

 On 26 June 2013 11:06, Mark Morgan Lloyd
 markmll.debian-...@telemetry.co.uk wrote:
  Another issue for tiny devices is the amount of RAM the Debian installer
  assumes is available, which now appears to be 256Mb.

 I just debootstrapped wheezy onto an armel board with 64MB RAM and no swap.
 Everything worked fine with the single exception of packages that
 contain files compressed with .xz, which died for lack of RAM - there
 were were one or two. Enabling a few MB of swap made the second stage
 run smoothly to completion.

M

 Ignore my -Os stupidity. Of course it is already enabled in linux
 through CONFIG_OPTIMIZE_FOR_SIZE.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/cal4-wqpbepv4cke+ceg11rccu2qgcctox0p+5ytpcwdsqso...@mail.gmail.com

Re: Installing ftp Server on debian slug

[Björn Wetterbom]

Silly question perhaps, but are you root?

(Skickat från min telefon == Sent from my phone)
On Mar 25, 2013 6:27 PM, Tobias Wagner broadwa...@live.de wrote:

 Hi all,

 for access to log files and creating backups I`d like to install ftp
 server on my nslu2. It is set up as advised on cyrius.com and running
 well.

 I tried:
  apt-get install proftpd

 and got:
  E: Could not open lock file /var/lib/dpkg/lock - open (2: No such file
 or directory)

 Indeed, the directory doesn't exist, so I created it and upon reentering
 the install command I got:
  E: Unable to write to /var/cache/apt/

 How can I make this work?

 Thanks, Tobias.

Re: Plug computer with two eth

[Björn Wetterbom]

http://www.newit.co.uk/ doesn't seem to have it right now, but since they
carry other Globalscape products (and have done for years), the Mirabox
will likely turn up there.

/B


On Tue, Mar 5, 2013 at 9:16 AM, Mike Howard m...@dewberryfields.co.ukwrote:

 On 03/03/2013 16:43, DrEagle wrote:

 Le 03/03/2013 16:12, Przemysław Kwiatkowski a écrit :

 Hello,

 Could anyone suggest any small Linux-based device with two ethernet
 ports? I would like it to be as small as possible, something like
 scheevaplug.

 P. Kwiatkowski

 The new and very promising generation of Plug devices like the Mirabox[1]
 Development Kit.

 I have received one for my own testing and future review.

 The device is like a small modem.
 Fast and powerfull.
 1.2 Ghz Marvell Armada with 1GB DDR3 (technical specifications and
 comparison on my wiki [2])

 Come with uboot and debian.
 Can boot from NAND (1GB), microSD, USB or Network.

 Short describe from the User Guide[3]

 [1] https://www.**globalscaletechnologies.com/p-**
 58-mirabox-development-kit.**aspxhttps://www.globalscaletechnologies.com/p-58-mirabox-development-kit.aspx
 [2] 
 https://doukki.net/doku.php?**id=wiki:notes:arm-features-**charthttps://doukki.net/doku.php?id=wiki:notes:arm-features-chart
 [3] https://www.**globalscaletechnologies.com/**
 download/MiraboxUserGuide_US_**V1-Sep-20-2012.pdfhttps://www.globalscaletechnologies.com/download/MiraboxUserGuide_US_V1-Sep-20-2012.pdf

 drEagle


  Are there any UK suppliers of this that you know of?

 Mike.
 --
 Any question is easy if you know the answer!



 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**5135A9D3.1000608@**dewberryfields.co.ukhttp://lists.debian.org/5135a9d3.1000...@dewberryfields.co.uk

Re: Flash-Kernel, IPv6 and Kirkwood CPU

[Björn Wetterbom]

Have you tried running flash-kernel as root and then rebooting, as
suggested by
http://permalink.gmane.org/gmane.linux.debian.devel.kernel/82575?

(Found by googling the error message)

/B

(Skickat från min platta == Sent from my tablet)
On Dec 2, 2012 2:36 PM, Rash r.kra...@tu-bs.de wrote:

 Hi,

 I have a kirkwood based plug computer running debian 6.06 and updated the
 kernel via aptitude. So far, so good, but the performance maybe decreased a
 bit and I got IPv6 error messages. I don't know why.

 ipv6: Unknown symbol sock_queue_err_skb

 I used:

 aptitude install linux-image-2.6.32-5-kirkwood

 which worked fine. It worked a long time with the old kernel there were no
 problems.

 apt-get install flash-kernel
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 flash-kernel is already the newest version.

 Any idea how to fix it?

 This looks promising but not sure what it means.

 http://lists.debian.org/debian-arm/2012/05/msg00029.html

 Kind regards


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/20121202132017.30f0726d7877f368e90f2...@tu-bs.de

Re: arm, both disk able to boot (raid1)

[Björn Wetterbom]

I have a raid1 setup on my ts-209 (from the original install). See my fstab
below.

If your raid1 setup is done, just update your fstab and run
update-initramfs -u  flash-kernel to update the initramfs with the new
fstab and install the initramfs to flash. I'd advice you to have a serial
console in case something goes wrong.

/B

--- 8 

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point   type  options
dump  pass
proc/proc   procdefaults0
0
/dev/md0/   ext3noatime,errors=remount-ro   0
1
/dev/md2/home   ext3noatime 0
2
/dev/md1noneswapsw  0
0
none/proc/bus/usb   usbfs   defaults0
0

--- 8 ---

On Wed, Oct 10, 2012 at 10:53 AM, rosea.grammostola 
rosea.grammost...@gmail.com wrote:

 On 10/10/2012 06:53 AM, Johnson Chetty wrote:


 you need u-boot to set up the environment for the device and
 u-boot will then load the kernel..


 Thanks. Do you've pointers for how to do this?



 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**50753797.7010...@gmail.comhttp://lists.debian.org/50753797.7010...@gmail.com

Re: arm, both disk able to boot (raid1)

[Björn Wetterbom]

http://www.cyrius.com/debian/orion/qnap/ts-209/

On Wed, Oct 10, 2012 at 11:46 AM, rosea.grammostola 
rosea.grammost...@gmail.com wrote:

 On 10/10/2012 11:07 AM, Björn Wetterbom wrote:

 I have a raid1 setup on my ts-209 (from the original install). See my
 fstab below.

 If your raid1 setup is done, just update your fstab and run
 update-initramfs -u  flash-kernel to update the initramfs with the
 new fstab and install the initramfs to flash. I'd advice you to have a
 serial console in case something goes wrong.


 Thanks. I've no experience with a serial console. Tutorials on the web
 seems to edit also the grub files, which aren't on this ARM install.
 What should be done different on a ARM in comparison with this method for
 instance?
 http://www.cyberciti.biz/faq/**howto-setup-serial-console-on-**
 debian-linux/http://www.cyberciti.biz/faq/howto-setup-serial-console-on-debian-linux/




  /B

 --- 8 

 $ cat /etc/fstab
 # /etc/fstab: static file system information.
 #
 # file system mount point type options dump pass
 proc/proc   procdefaults
   0   0
 /dev/md0/   ext3noatime,errors=remount-ro
 0   1
 /dev/md2/home   ext3noatime
 0   2
 /dev/md1noneswapsw
   0   0
 none/proc/bus/usb   usbfs   defaults
   0   0

 --- 8 ---

 On Wed, Oct 10, 2012 at 10:53 AM, rosea.grammostola
 rosea.grammost...@gmail.com 
 mailto:rosea.grammostola@**gmail.comrosea.grammost...@gmail.com
 wrote:

 On 10/10/2012 06:53 AM, Johnson Chetty wrote:


  you need u-boot to set up the environment for the
 device and
  u-boot will then load the kernel..


 Thanks. Do you've pointers for how to do this?



 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.__deb**ian.orghttp://debian.org
 
 mailto:debian-arm-REQUEST@**lists.debian.orgdebian-arm-requ...@lists.debian.org
 

 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org 
 mailto:listmaster@lists.**debian.orglistmas...@lists.debian.org
 
 Archive: 
 http://lists.debian.org/__**50753797.7010...@gmail.comhttp://lists.debian.org/__50753797.7010...@gmail.com
 
 http://lists.debian.org/**50753797.7010...@gmail.comhttp://lists.debian.org/50753797.7010...@gmail.com
 

Re: arm, both disk able to boot (raid1)

[Björn Wetterbom]

That's the one.

/B

On Wed, Oct 10, 2012 at 12:59 PM, rosea.grammostola 
rosea.grammost...@gmail.com wrote:

 On 10/10/2012 12:26 PM, Björn Wetterbom wrote:

 http://www.cyrius.com/debian/**orion/qnap/ts-209/http://www.cyrius.com/debian/orion/qnap/ts-209/


 Thx. Hmm ok so I need this hardware to connect the qnap to my laptop?
 http://apple.clickandbuild.**com/cnb/shop/ftdichip?**
 productID=53op=catalogue-**product_info-null**prodCategoryID=47http://apple.clickandbuild.com/cnb/shop/ftdichip?productID=53op=catalogue-product_info-nullprodCategoryID=47

  On Wed, Oct 10, 2012 at 11:46 AM, rosea.grammostola
 rosea.grammost...@gmail.com 
 mailto:rosea.grammostola@**gmail.comrosea.grammost...@gmail.com
 wrote:

 On 10/10/2012 11:07 AM, Björn Wetterbom wrote:

 I have a raid1 setup on my ts-209 (from the original install).
 See my
 fstab below.

 If your raid1 setup is done, just update your fstab and run
 update-initramfs -u  flash-kernel to update the initramfs
 with the
 new fstab and install the initramfs to flash. I'd advice you to
 have a
 serial console in case something goes wrong.


 Thanks. I've no experience with a serial console. Tutorials on the
 web seems to edit also the grub files, which aren't on this ARM
 install.
 What should be done different on a ARM in comparison with this
 method for instance?
 http://www.cyberciti.biz/faq/_**_howto-setup-serial-console-**
 on-__debian-linux/http://www.cyberciti.biz/faq/__howto-setup-serial-console-on-__debian-linux/

 http://www.cyberciti.biz/faq/**howto-setup-serial-console-on-**
 debian-linux/http://www.cyberciti.biz/faq/howto-setup-serial-console-on-debian-linux/
 




 /B

 --- 8 

 $ cat /etc/fstab
 # /etc/fstab: static file system information.
 #
 # file system mount point type options dump pass
 proc/proc   procdefaults
0   0
 /dev/md0/   ext3noatime,errors=remount-ro
 0   1
 /dev/md2/home   ext3noatime
 0   2
 /dev/md1noneswapsw
0   0
 none/proc/bus/usb   usbfs   defaults
0   0

 --- 8 ---

 On Wed, Oct 10, 2012 at 10:53 AM, rosea.grammostola
 rosea.grammost...@gmail.com
 mailto:rosea.grammostola@**gmail.comrosea.grammost...@gmail.com
 
 mailto:rosea.grammostola@__gm**ail.com http://gmail.com

 mailto:rosea.grammostola@**gmail.comrosea.grammost...@gmail.com
 wrote:

  On 10/10/2012 06:53 AM, Johnson Chetty wrote:


   you need u-boot to set up the environment for the
  device and
   u-boot will then load the kernel..


  Thanks. Do you've pointers for how to do this?



  --
  To UNSUBSCRIBE, email to
 debian-arm-REQUEST@lists.__deb**__ian.org http://deb__ian.org 
 http://debian.org
 
 mailto:debian-arm-REQUEST@__l**ists.debian.orghttp://lists.debian.org

 
 mailto:debian-arm-REQUEST@**lists.debian.orgdebian-arm-requ...@lists.debian.org
 

  with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org 
 mailto:listmaster@lists.**debian.orglistmas...@lists.debian.org
 
 mailto:listmaster@lists.__deb**ian.org http://debian.org
 mailto:listmaster@lists.**debian.orglistmas...@lists.debian.org
 
  Archive:
 
 http://lists.debian.org/**50753797.7010...@gmail.comhttp://lists.debian.org/50753797.7010...@gmail.com
 
 http://lists.debian.org/__**50753797.7010...@gmail.comhttp://lists.debian.org/__50753797.7010...@gmail.com
 
 
 http://lists.debian.org/__**50753797.7010...@gmail.comhttp://lists.debian.org/__50753797.7010...@gmail.com
 
 http://lists.debian.org/**50753797.7010...@gmail.comhttp://lists.debian.org/50753797.7010...@gmail.com
 

Re: Debian qnap 109 - qnap 209

[Björn Wetterbom]

Well, you could try to install the ramdisk to flash using the Debian
installer. See http://www.cyrius.com/journal/debian/installer-flash-kernel.
Since the 109 and the 209 are very similar, it might work (they have the
same machine architecture).

I'm not sure if update-initramfs -u will flash, so to be extra sure issue
flash-kernel as well. If you use the same medium as in your 109 it should
be pretty straightforward. If you change medium you must update your UUIDs
in /etc/fstab.

Since I'm no expert, something probably will go wrong if you try this. But
it won't break anything.

/B

On Fri, Oct 5, 2012 at 11:44 AM, rosea.grammostola 
rosea.grammost...@gmail.com wrote:

 Hi,

 I've a working Debian installation on a qnap 109. Is it possible to make
 that boot in a qnap 209 in some way?

 How can I move the working 109 to my 209?

 Best regards,
 \r


 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**506eac0f.10...@gmail.comhttp://lists.debian.org/506eac0f.10...@gmail.com

Re: Debian qnap 109 - qnap 209

[Björn Wetterbom]

 Thx for your reply.
 First I'm wondering how I start the debian-installer having the unbootable
 109 disk in the 209. Unfortunately I installed debian already on the qnap
 209.

 I can boot that install with also the 109 drive in it, but how do I launch
 the d-i then? And how do I make sure the commands you suggested are
 executed for the right drive?

 If you have Debian on the 209 you already have the correct ramdisk on the
209 flash (both installs must be the same Debian version). Try changing the
UUIDs on the 109 disk to match those of the 209 disk and see if it boots.
If it does not boot it should drop to a shell where you can try to find the
error.

This is a rather complicated procedure, and unfortunately I can't help you
further. I have only fiddled with the ramdisk on one or two occasions and
my knowledge is really very shallow in that area.

/B


 Regards
















  /B

 On Fri, Oct 5, 2012 at 11:44 AM, rosea.grammostola
 rosea.grammost...@gmail.com 
 mailto:rosea.grammostola@**gmail.comrosea.grammost...@gmail.com
 wrote:

 Hi,

 I've a working Debian installation on a qnap 109. Is it possible to
 make that boot in a qnap 209 in some way?

 How can I move the working 109 to my 209?

 Best regards,
 \r


 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.__deb**ian.orghttp://debian.org
 
 mailto:debian-arm-REQUEST@**lists.debian.orgdebian-arm-requ...@lists.debian.org
 

 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org 
 mailto:listmaster@lists.**debian.orglistmas...@lists.debian.org
 
 Archive: 
 http://lists.debian.org/__**506eac0f.10...@gmail.comhttp://lists.debian.org/__506eac0f.10...@gmail.com
 
 http://lists.debian.org/**506eac0f.10...@gmail.comhttp://lists.debian.org/506eac0f.10...@gmail.com
 




 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**506ec1e3.6080...@gmail.comhttp://lists.debian.org/506ec1e3.6080...@gmail.com

Re: Help needed after updating Debian on QNAP TS-109 Pro II

[Björn Wetterbom]

I'd reboot if I were you. On the other hand, I have a serial console, which
has helped me through the rough on at least one occasion.

Worst case, you have to order a ttl converter to get serial access. But I
_think_ your reboot will go well.

B
On Sep 22, 2012 10:37 PM, Juha Larjomaa juha.larjo...@iki.fi wrote:

 Thanks!

 I ran both of those now but I still have not dared to reboot because
 starting cupsd seems to hang forever. I am concerned that my boot could get
 stuck.

 This is what it is running:

 13874 pts/9S+ 0:00  \_ /bin/sh
 /usr/sbin/invoke-rc.d cups start
 13890 pts/9S+ 0:00  \_ /bin/sh
 /etc/init.d/cups start
 13897 pts/9S+ 0:05  \_ modprobe -q -b
 parport_pc

 Any ideas? I suspect this might also be related to why smbd crashes. Or
 should I just take the leap and reboot?

 Juha


 On Sat, Sep 22, 2012 at 11:03 PM, Björn Wetterbom bjohv...@gmail.comwrote:

 Wait! You must also run flash-kernel as root to move the initramfs to
 flash. Sorry I missed that.

 B

 (Sent from my phone.)
 On Sep 22, 2012 9:57 PM, Björn Wetterbom bjohv...@gmail.com wrote:

 You should have no problems. The part about boot loader is because grub
 or lilo can't be found. That's normal since you boot from flash.

 Run update-initramfs -u as root before reboot and you will be fine. I'm
 not sure it's needed nowadays, but it certainly won't cause any harm.

 Björn

 (Sent from my phone.)
 On Sep 22, 2012 9:48 PM, Juha Larjomaa juha.larjo...@iki.fi wrote:

 Hi,

 I have been happily running Squeeze from a USB stick on my QNAP TS-109
 Pro II for a long time. Today, I decided to update my system with 'apt-get
 upgrade'. Some packages were updated but I saw that some files were kept
 back by apt-get - so I decided to run 'apt-get dist-upgrade' without
 knowing any better.

 This is when problems started. Would anyone be able to help?

 Apparently the update changed the mgmt of hard disks to some UUID-based
 plot that I am not familiar with. For example, my /etc/fstab was changed as
 follows:

 kaappikone# less /etc/fstab
 # /etc/fstab: static file system information.
 #
 # file system mount point   type  options   dump  pass
 proc/proc   procdefaults0   0
 # /dev/sda2   /   ext3errors=remount-ro,noatime
 0   1
 UUID=59c82707-e5bd-4538-a2ad-b697635e9313   /   ext3
 errors=remount-ro,noatime 0   1
 # /dev/sda1   /boot   ext2defaults0   2
 UUID=42cacc9b-4dfd-4cd9-85dc-8810a82af109   /boot   ext2
 defaults0   2
 # /dev/sda5   noneswapsw  0   0
 UUID=0f4c0b92-afd9-45de-b9b1-40b93d458ffa   noneswap
 sw  0   0
 # /dev/sdb2   /bigdisk  ext3noatime 0   1
 UUID=af48689a-1f86-4a8b-ab86-be90915b37d9   /bigdiskext3
 noatime 0   1

 The bit that worries me is that the upgrade program gave me the
 following warning:

  │ Boot loader configuration check
 needed│
  │
 │
  │ The boot loader configuration for this system was not recognized.
 These   │
  │ settings in the configuration may need to be
 updated: │
  │
 │
  │  * The root device ID passed as a kernel
 parameter;   │
  │  * The boot device ID used to install and update the boot
 loader. │
  │
 │
  │
 │
  │ You should generally identify these devices by UUID or label.
 However,│
  │ on MIPS systems the root device must be identified by name.

 Would anyone be able to help me how to do that? Or, more generally, how
 to ensure that my QNAP box will be able to boot again?

 I have not yet rebooted since the update. I am able to login with SSH
 but for some reason smb crashes as soon as I try to connect to it. This did
 not happen before the update.

 Thanks!

 Juha

Re: Help needed after updating Debian on QNAP TS-109 Pro II

[Björn Wetterbom]

You should have no problems. The part about boot loader is because grub or
lilo can't be found. That's normal since you boot from flash.

Run update-initramfs -u as root before reboot and you will be fine. I'm not
sure it's needed nowadays, but it certainly won't cause any harm.

Björn

(Sent from my phone.)
On Sep 22, 2012 9:48 PM, Juha Larjomaa juha.larjo...@iki.fi wrote:

 Hi,

 I have been happily running Squeeze from a USB stick on my QNAP TS-109 Pro
 II for a long time. Today, I decided to update my system with 'apt-get
 upgrade'. Some packages were updated but I saw that some files were kept
 back by apt-get - so I decided to run 'apt-get dist-upgrade' without
 knowing any better.

 This is when problems started. Would anyone be able to help?

 Apparently the update changed the mgmt of hard disks to some UUID-based
 plot that I am not familiar with. For example, my /etc/fstab was changed as
 follows:

 kaappikone# less /etc/fstab
 # /etc/fstab: static file system information.
 #
 # file system mount point   type  options   dump  pass
 proc/proc   procdefaults0   0
 # /dev/sda2   /   ext3errors=remount-ro,noatime
 0   1
 UUID=59c82707-e5bd-4538-a2ad-b697635e9313   /   ext3
 errors=remount-ro,noatime 0   1
 # /dev/sda1   /boot   ext2defaults0   2
 UUID=42cacc9b-4dfd-4cd9-85dc-8810a82af109   /boot   ext2
 defaults0   2
 # /dev/sda5   noneswapsw  0   0
 UUID=0f4c0b92-afd9-45de-b9b1-40b93d458ffa   noneswap
 sw  0   0
 # /dev/sdb2   /bigdisk  ext3noatime 0   1
 UUID=af48689a-1f86-4a8b-ab86-be90915b37d9   /bigdiskext3
 noatime 0   1

 The bit that worries me is that the upgrade program gave me the following
 warning:

  │ Boot loader configuration check
 needed│
  │
 │
  │ The boot loader configuration for this system was not recognized.
 These   │
  │ settings in the configuration may need to be
 updated: │
  │
 │
  │  * The root device ID passed as a kernel
 parameter;   │
  │  * The boot device ID used to install and update the boot
 loader. │
  │
 │
  │
 │
  │ You should generally identify these devices by UUID or label.
 However,│
  │ on MIPS systems the root device must be identified by name.

 Would anyone be able to help me how to do that? Or, more generally, how to
 ensure that my QNAP box will be able to boot again?

 I have not yet rebooted since the update. I am able to login with SSH but
 for some reason smb crashes as soon as I try to connect to it. This did not
 happen before the update.

 Thanks!

 Juha

Re: Help needed after updating Debian on QNAP TS-109 Pro II

[Björn Wetterbom]

Wait! You must also run flash-kernel as root to move the initramfs to
flash. Sorry I missed that.

B

(Sent from my phone.)
On Sep 22, 2012 9:57 PM, Björn Wetterbom bjohv...@gmail.com wrote:

 You should have no problems. The part about boot loader is because grub or
 lilo can't be found. That's normal since you boot from flash.

 Run update-initramfs -u as root before reboot and you will be fine. I'm
 not sure it's needed nowadays, but it certainly won't cause any harm.

 Björn

 (Sent from my phone.)
 On Sep 22, 2012 9:48 PM, Juha Larjomaa juha.larjo...@iki.fi wrote:

 Hi,

 I have been happily running Squeeze from a USB stick on my QNAP TS-109
 Pro II for a long time. Today, I decided to update my system with 'apt-get
 upgrade'. Some packages were updated but I saw that some files were kept
 back by apt-get - so I decided to run 'apt-get dist-upgrade' without
 knowing any better.

 This is when problems started. Would anyone be able to help?

 Apparently the update changed the mgmt of hard disks to some UUID-based
 plot that I am not familiar with. For example, my /etc/fstab was changed as
 follows:

 kaappikone# less /etc/fstab
 # /etc/fstab: static file system information.
 #
 # file system mount point   type  options   dump  pass
 proc/proc   procdefaults0   0
 # /dev/sda2   /   ext3errors=remount-ro,noatime
 0   1
 UUID=59c82707-e5bd-4538-a2ad-b697635e9313   /   ext3
 errors=remount-ro,noatime 0   1
 # /dev/sda1   /boot   ext2defaults0   2
 UUID=42cacc9b-4dfd-4cd9-85dc-8810a82af109   /boot   ext2
 defaults0   2
 # /dev/sda5   noneswapsw  0   0
 UUID=0f4c0b92-afd9-45de-b9b1-40b93d458ffa   noneswap
 sw  0   0
 # /dev/sdb2   /bigdisk  ext3noatime 0   1
 UUID=af48689a-1f86-4a8b-ab86-be90915b37d9   /bigdiskext3
 noatime 0   1

 The bit that worries me is that the upgrade program gave me the following
 warning:

  │ Boot loader configuration check
 needed│
  │
 │
  │ The boot loader configuration for this system was not recognized.
 These   │
  │ settings in the configuration may need to be
 updated: │
  │
 │
  │  * The root device ID passed as a kernel
 parameter;   │
  │  * The boot device ID used to install and update the boot
 loader. │
  │
 │
  │
 │
  │ You should generally identify these devices by UUID or label.
 However,│
  │ on MIPS systems the root device must be identified by name.

 Would anyone be able to help me how to do that? Or, more generally, how
 to ensure that my QNAP box will be able to boot again?

 I have not yet rebooted since the update. I am able to login with SSH but
 for some reason smb crashes as soon as I try to connect to it. This did not
 happen before the update.

 Thanks!

 Juha

RE: Running on usb flash

[Björn Wetterbom]

Could be a file system check. Leave it alone over night and see what
happens. I can't see anything wrong with your fstab. If it's not fsck, you
may need a serial console.

B

Sent from my nexus 7
On Sep 2, 2012 4:57 PM, Brian Platt brianpl...@hotmail.com wrote:

  Did I make a mistake on the below fstab as slug no longer boots

 --
 From: brianpl...@hotmail.com
 To: debian-arm@lists.debian.org
 Subject: RE: Running on usb flash
 Date: Sat, 1 Sep 2012 21:56:39 +0100

  Thanks

 I've added


 # /etc/fstab: static file system information.
 #
 # file system mount point   type  options   dump  pass
 proc/proc   procdefaults0   0
 /dev/sda2   /   ext3errors=remount-ro,noatime 0   1
 /dev/sda1   /boot   ext2defaults,noatime0   2
 /dev/sda6   /home   ext3defaults,noatime0   2
 /dev/sda5   noneswapsw  0   0

 to fstab, is it worth minimzing or disabling swap?

 I've just bought some decent fast kingston drives, like you say it's not
 worth the risk using cheap drives.

 --
 Date: Sat, 1 Sep 2012 22:03:20 +0200
 Subject: Re: Running on usb flash
 From: bjohv...@gmail.com
 To: brianpl...@hotmail.com
 CC: debian-arm@lists.debian.org

 I've run several devices from usb flash for years and have always followed
 the advice of Martin Michlmayr to use -noatime. Through the years I've had
 a few crashes, but they have consistently been on cheap usb devices. My
 advice is to use noatime and sandisk memory, other measures give little in
 return.
 /B
 (Skickat från min mobiltelefon, därför kanske något kortfattat.)
 On Sep 1, 2012 9:55 PM, Brian Platt brianpl...@hotmail.com wrote:

  I'm running lenny on my nslu2 on a usb flash stick and found a few guides
 on how to reduce wear and tear on it but not sure which ones are upto
 date/relevant. Could someone have a look at these and let me know what ones
 I should be doing is seems ott to do them all.

 http://www.cyrius.com/debian/nslu2/linux-on-flash.html

 http://wiki.pcprobleemloos.nl/my_debian_linux_on_the_nslu2_installation_and_configuration_guide/#preventing_flash_writes_reduce_wear_on_flash_memory
 http://www.rawsontetley.org/ref_slug.html

Re: Running on usb flash

[Björn Wetterbom]

I've run several devices from usb flash for years and have always followed
the advice of Martin Michlmayr to use -noatime. Through the years I've had
a few crashes, but they have consistently been on cheap usb devices. My
advice is to use noatime and sandisk memory, other measures give little in
return.

/B

(Skickat från min mobiltelefon, därför kanske något kortfattat.)
On Sep 1, 2012 9:55 PM, Brian Platt brianpl...@hotmail.com wrote:

  I'm running lenny on my nslu2 on a usb flash stick and found a few guides
 on how to reduce wear and tear on it but not sure which ones are upto
 date/relevant. Could someone have a look at these and let me know what ones
 I should be doing is seems ott to do them all.

 http://www.cyrius.com/debian/nslu2/linux-on-flash.html

 http://wiki.pcprobleemloos.nl/my_debian_linux_on_the_nslu2_installation_and_configuration_guide/#preventing_flash_writes_reduce_wear_on_flash_memory
 http://www.rawsontetley.org/ref_slug.html

Re: QNap Hard drive upgrade (Boot Sequence)

[Björn Wetterbom]

   1. Try changing the UUIDs on the new disk to match those of the old disk
   and leave fstab unchanged.
   2. As you mentioned, try not changing to ext4.
   3. Try to get help at  http://forum.qnap.com/viewforum.php?f=147
   4. Get a serial console and run 'update-initramfs -u  flash-kernel'
   from within initramfs-tools accordning to
   
http://www.cyrius.com/journal/debian/orion/d-link/dns-323/fix-initramfs-tools.tbm

I'm not sure why it does not work for you. I have done this several time
with HDDs and USB thumb drives, albeit not with SSDs.

Good luck!

/Björn

If that does not work you could try a serial console and

On Wed, May 30, 2012 at 11:31 PM, David Pottage da...@electric-spoon.comwrote:

  It is not working for me.

 To summarize what I have done, I setup my SSD with the same partition as
 the original hard drive, but with different sizes, to reflect usage. I kept
 the /boot partition as ext2, and the root partition as ext3, but changed
 the format of all other partitions to ext4 so as to have support for trim.

 When I put the SSD into my Qnap device, and turned it on. I got the status
 light slow flashing red and green, and LAN light flickering. The box did
 not respond to pings, or SSH access. I left it in that state for 5 minutes
 in case it was slow booting.

 Thing I have tried:

 I ran fsck on all partitions to check for errors.
 I changed the mount options in /etc/fstab to remove anything problematic
 (eg discard on an ext2 partition)
 I have double checked that the UUIDs are correct.
 I have connected the SSD to the Qnap device's eSATA port, and confirmed
 that the Qnap box can access the SSD and mount the partitions.

 Was it a mistake to change the partition format to ext4 and re-size them?
 Could there be an issue with the partition layout that is preventing uboot
 or the kernel from finding what it needs?
 I have enabled boot logging, but a boot log was not created. Presumably
 this means that the boot process failed before it could mount /var

 Can you suggest anything else I might try?

 Thanks.


 On 27/05/2012 20:58, Björn Wetterbom wrote:

 Don't worry, just run rsync -aHX (iirc) from the old disk to the new and
 update fstab with new UUIDs and it will work. I've done it on several
 occasions.

 The kernel is stored in flash memory (if you watch kernel updates, they
 are always finalized with flash-kernel), so the mbr of the disk is not
 used.

 A brief explanation, I know, but the keyboard of my phone isn't that
 comfy. Use Google for more info.

 Good luck.

 (Sent from my phone.)
 On May 27, 2012 5:06 PM, David Pottage da...@chrestomanci.org wrote:

 Hello

 I have a Qnap TS-110, which I am using as a home server for the past
 year. It runs Debian Squeeze.

 I have decided to replace the internal hard drive with a much smaller
 SSD, but I am concerned about how the Kirkwood boot sequence works, and how
 I make sure that u-boot can find the kernel image and other necessary files
 to boot on the new SSD drive.

 Many years ago, when I used desktop based linux distros that used lilo to
 boot, I recall that the boot block contained raw hard drive offsets to the
 kernel an intrid image files, and if you moved the files on disc without
 re-writing the lilo boot block then the boot sequence would fail as the
 kernel would not be found, despite the fact that the pathname remained the
 same.

 Is there a similar issue with u-boot on Kirkwood devices? Do I need to
 make an exact copy of the boot partition in order for it to work, or is
 u-boot able to mount and understand the ext2 filesystem and find the boot
 image by pathname?

 Are there any similar issues with the root or any other partition on the
 system?

 Thank you.

 --
 David Pottage


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4fc23e99.1040...@chrestomanci.org

Re: QNap Hard drive upgrade (Boot Sequence)

[Björn Wetterbom]

Update: point 1 below should be the correct answer. A background is at
http://forum.qnap.com/viewtopic.php?f=147t=58300 .

Please report back.

/B

On Thu, May 31, 2012 at 9:11 AM, Björn Wetterbom bjohv...@gmail.com wrote:


1. Try changing the UUIDs on the new disk to match those of the old
disk and leave fstab unchanged.
2. As you mentioned, try not changing to ext4.
3. Try to get help at  http://forum.qnap.com/viewforum.php?f=147
4. Get a serial console and run 'update-initramfs -u  flash-kernel'
from within initramfs-tools accordning to

 http://www.cyrius.com/journal/debian/orion/d-link/dns-323/fix-initramfs-tools.tbm

 I'm not sure why it does not work for you. I have done this several time
 with HDDs and USB thumb drives, albeit not with SSDs.

 Good luck!

 /Björn

 If that does not work you could try a serial console and


 On Wed, May 30, 2012 at 11:31 PM, David Pottage 
 da...@electric-spoon.comwrote:

  It is not working for me.

 To summarize what I have done, I setup my SSD with the same partition as
 the original hard drive, but with different sizes, to reflect usage. I kept
 the /boot partition as ext2, and the root partition as ext3, but changed
 the format of all other partitions to ext4 so as to have support for trim.

 When I put the SSD into my Qnap device, and turned it on. I got the
 status light slow flashing red and green, and LAN light flickering. The box
 did not respond to pings, or SSH access. I left it in that state for 5
 minutes in case it was slow booting.

 Thing I have tried:

 I ran fsck on all partitions to check for errors.
 I changed the mount options in /etc/fstab to remove anything problematic
 (eg discard on an ext2 partition)
 I have double checked that the UUIDs are correct.
 I have connected the SSD to the Qnap device's eSATA port, and confirmed
 that the Qnap box can access the SSD and mount the partitions.

 Was it a mistake to change the partition format to ext4 and re-size them?
 Could there be an issue with the partition layout that is preventing
 uboot or the kernel from finding what it needs?
 I have enabled boot logging, but a boot log was not created. Presumably
 this means that the boot process failed before it could mount /var

 Can you suggest anything else I might try?

 Thanks.


 On 27/05/2012 20:58, Björn Wetterbom wrote:

 Don't worry, just run rsync -aHX (iirc) from the old disk to the new and
 update fstab with new UUIDs and it will work. I've done it on several
 occasions.

 The kernel is stored in flash memory (if you watch kernel updates, they
 are always finalized with flash-kernel), so the mbr of the disk is not
 used.

 A brief explanation, I know, but the keyboard of my phone isn't that
 comfy. Use Google for more info.

 Good luck.

 (Sent from my phone.)
 On May 27, 2012 5:06 PM, David Pottage da...@chrestomanci.org wrote:

 Hello

 I have a Qnap TS-110, which I am using as a home server for the past
 year. It runs Debian Squeeze.

 I have decided to replace the internal hard drive with a much smaller
 SSD, but I am concerned about how the Kirkwood boot sequence works, and how
 I make sure that u-boot can find the kernel image and other necessary files
 to boot on the new SSD drive.

 Many years ago, when I used desktop based linux distros that used lilo
 to boot, I recall that the boot block contained raw hard drive offsets to
 the kernel an intrid image files, and if you moved the files on disc
 without re-writing the lilo boot block then the boot sequence would fail as
 the kernel would not be found, despite the fact that the pathname remained
 the same.

 Is there a similar issue with u-boot on Kirkwood devices? Do I need to
 make an exact copy of the boot partition in order for it to work, or is
 u-boot able to mount and understand the ext2 filesystem and find the boot
 image by pathname?

 Are there any similar issues with the root or any other partition on the
 system?

 Thank you.

 --
 David Pottage


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4fc23e99.1040...@chrestomanci.org

Re: QNap Hard drive upgrade (Boot Sequence)

[Björn Wetterbom]

Don't worry, just run rsync -aHX (iirc) from the old disk to the new and
update fstab with new UUIDs and it will work. I've done it on several
occasions.

The kernel is stored in flash memory (if you watch kernel updates, they are
always finalized with flash-kernel), so the mbr of the disk is not used.

A brief explanation, I know, but the keyboard of my phone isn't that comfy.
Use Google for more info.

Good luck.

(Sent from my phone.)
On May 27, 2012 5:06 PM, David Pottage da...@chrestomanci.org wrote:

 Hello

 I have a Qnap TS-110, which I am using as a home server for the past year.
 It runs Debian Squeeze.

 I have decided to replace the internal hard drive with a much smaller SSD,
 but I am concerned about how the Kirkwood boot sequence works, and how I
 make sure that u-boot can find the kernel image and other necessary files
 to boot on the new SSD drive.

 Many years ago, when I used desktop based linux distros that used lilo to
 boot, I recall that the boot block contained raw hard drive offsets to the
 kernel an intrid image files, and if you moved the files on disc without
 re-writing the lilo boot block then the boot sequence would fail as the
 kernel would not be found, despite the fact that the pathname remained the
 same.

 Is there a similar issue with u-boot on Kirkwood devices? Do I need to
 make an exact copy of the boot partition in order for it to work, or is
 u-boot able to mount and understand the ext2 filesystem and find the boot
 image by pathname?

 Are there any similar issues with the root or any other partition on the
 system?

 Thank you.

 --
 David Pottage


 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**4FC23E99.1040103@chrestomanci.**orghttp://lists.debian.org/4fc23e99.1040...@chrestomanci.org

Re: Support for the D-Link DNS-320?

[Björn Wetterbom]

I don't know about the DNS-320, but I would heartily recommend the QNAP
products, preferrably the ones with official Debian support via
www.cyrius.com.

I'm running two older Qnaps as servers 24/7 with excellent track record.

/Björn

2012/2/20 Rogério Brito rbr...@ime.usp.br

 Hi, people.

 I just saw a guy selling a D-Link DNS-320 and, according to D-Link
 themselves, these devices run Linux. Looking on the Linux kernel tree
 I see that there is a file called dns323-setup.c (for the 323), but
 there is no mention of the 320.

 Of course, if I happen to buy one of these, I would wipe everything
 and install a real debian system.

 So, my question is: are there successful reports of people using the
 DNS-320? Some googling seems to indicate so, but I don't know which
 kernel would be appropriate, if everything works correctly etc.

 Also, is this a good purchase? I would love to get a NAS device that
 can hold 2 HDs, but I have no brand loyalty and I mostly only care
 about installing Debian on it. If you happen to know other devices
 that would be a better choice, I would love to know.

 Thanks in advance for any recommendation,
 Rogério Brito.

 P.S.: As I am not currently subscribed to debian-arm, I would kindly
 ask if you could include me in CC.
 --
 Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
 http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
 DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/caotrxkogy064pqqfauy+cmvfz0+dbdhacg_q8qucu7eufdu...@mail.gmail.com

Re: Choose kernel in NSLU2

[Björn Wetterbom]

 I want to know:

 a) how can I choose that other linux version boots my system:
 dpkg-reconfigure what?


I believe you want to run flash-kernel to put your desired kernel in flash.
Try 'man flash-kernel' as root.


 b) can I follow the general howto to build my own kernel and make dpkg -i
 my-kernel.deb ?

 I'm interested, overall, in (a).


 Thanks in advance,
 Xan.


 --
 To UNSUBSCRIBE, email to 
 debian-arm-REQUEST@lists.**debian.orgdebian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/**4EFA1DAC.2040402@telefonica.**nethttp://lists.debian.org/4efa1dac.2040...@telefonica.net

nslu2 does not start - hw error

[Björn Wetterbom]

When pressing the power button on my nslu2 I can hear a click inside
the device and the power button lights up briefly. Then it's dead
again. After repeating this several times (up to, say, 20 times), the
device starts. When it's running I can issue a reboot command without
problems.

I have tried with two different voltage adapters and the results are
the same. I'm guessing something is about to give up on the inside of
the nslu2. Is there something anyone knows that can be done about
this?

TIA
Björn


--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTik0KsameD7Kyk=okfhcrbdl5i_...@mail.gmail.com

Re: QNAP TS-110: how to replace HDD?

[Björn Wetterbom]

What's the output on the serial console? I probably won't be any better than
you interpreting it, but perhaps someone else will.

On Wed, Apr 20, 2011 at 17:45, Hardy Griech nt...@mardys.de wrote:

 On 20.04.2011 10:27, Björn Wetterbom wrote:
 :

 You are correct, if you update UUIDs in /etc/fstab, a ' update-initramfs
 -u ' is required. What you can do is change the UUIDs on the new disk so
 that they are identical to those of the old disk. Use tune2fs for
 ext2/3/4 partitions and mkswap for swap partition. I did this on my
 TS-119 a while back.


 Forgot to mention in my procedure that I modified the UUIDs with tune2fs to
 reflect the old state.

 Nevertheless the system did not start.

 Perhaps an important 'detail': the new HDD had 2TB, while the old one had
 1TB.  What I meant with layout did not include the size, only that sda1 was
 boot for both, sda2 root and sda6 home.


 Hardy


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4daeff8a.4080...@mardys.de

Re: QNAP TS-110: how to replace HDD?

[Björn Wetterbom]

-- Snip ---

 - how to actually replace the HDD?

Since you have the same disk layouts, I would rsync the data from the old to
the new disk. Then update /etc/fstab with the UUIDs of the new disk. After
that you're good to go.

 - how to start the Debian installer?

With a serial console, use tftp:
http://www.cyrius.com/debian/kirkwood/qnap/ts-119/uboot.html

 - is recovery using DHCP or BOOTP?

I don't know.


 Hardy


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4dadea44.50...@mardys.de

Re: Re: QNAP TS-110: how to replace HDD?

[Björn Wetterbom]

Yes, the installer can be flashed from the command line. See
http://forum.qnap.com/viewtopic.php?f=147t=37149p=164507sid=dee8c64d1a8772fc2325acbebe529079

Disclamer: I don't know if the mentioned commands are valid for TS-110.

You are correct, if you update UUIDs in /etc/fstab, a 'update-initramfs -u'
is required. What you can do is change the UUIDs on the new disk so that
they are identical to those of the old disk. Use tune2fs for ext2/3/4
partitions and mkswap for swap partition. I did this on my TS-119 a while
back.

/Björn

On Wed, Apr 20, 2011 at 09:42, nt...@mardys.de wrote:

  Since you have the same disk layouts, I would rsync the data from the old
 to the new disk. Then update /etc/fstab with the UUIDs of the new disk.
 After that you're good to go.

  I tried it actually that way:

 - same HDD layout

 - copy data (cp -a)

 - insert new disk

 - try to start


 But that resulted in a non-starting system.  It seems to me, that 
 'update-initramfs
 -u' is required.


 - how to start the Debian installer?
  With a serial console, use tftp:
 http://www.cyrius.com/debian/kirkwood/qnap/ts-119/uboot.html

 Any other way directly from the command line?  Would be nice to 'activate'
 the installer running with the old HDD, replace the HDD (prepared as
 above) and then follow the procedure from
 http://www.cyrius.com/journal/debian/installer-flash-kernel.

 Hardy

Re: Suggestions for a SheevaPlug replacement

[Björn Wetterbom]

Or the TS-119, which is fanless.

/B

On Sat, Mar 26, 2011 at 15:44, KaruppuSwamy T karuppusw...@gmail.comwrote:

 Hi,

 I suggest QNAP TS-110, which takes just 5W power. I am very much happy with
 this home server, powered by Debian Squeeze. It fits well with arm branch of
 Debian.


 http://karuppuswamy.com/wordpress/2010/08/04/diy-planning-to-build-home-nas-box-cum-digital-photo-frame/

 Regards
 KaruppuSwamy.T


 On Sat, Mar 26, 2011 at 5:12 PM, David Given d...@cowlark.com wrote:

 Hello,

 I'm looking for some hardware to replace my elderly SheevaPlug house
 server --- it's working very well, but there are ongoing niggling
 problems with USB and storage, and I'd like something with more ports.

 I'm very intrigued by the new Dreamplug, which looks ideal.
 Unfortunately it's not cost effective. Here in the UK it would cost 160
 pounds (including JTAG module so I get a console), and I can buy a Revo
 R3700 mini-PC for only 180, and that's got 2GB RAM, a dual-core D525
 Atom processor, 160GB HDD, etc. I don't want to switch away from ARM but
 I've got to be realistic.

 So can anyone suggest any Debian-friendly hardware I should look at?
 Ideally I want something with two ethernet ports and eSATA; I've had
 enough of ethernet via slightly unreliable USB...

 --
 ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─
 │
 │ I have a mind like a steel trap. It's rusty and full of dead mice.
 │ --- Anonymous, on rasfc

Re: Using nslu2 as remote console

[Björn Wetterbom]

Thank you for your input. Special thanks to Daniel who made me think a
little about kernel and bootloader output to the console. I was planning on
using the onboard serial, but my solution will now include one of these:

http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm

I have used it before and it works out of the box on Debian.

/Björn


On Sun, Mar 6, 2011 at 16:50, Luke Kenneth Casson Leighton l...@lkcl.netwrote:

 2011/3/6 Daniel Kahn Gillmor d...@fifthhorseman.net:

  If you're using a separate USB serial adapter, i think you should have
  no problems, as long as (as you suggest) you don't have a getty or other
  process attached to the USB device.

  PL2303-based USB-to-serial converters: available from maplin's for
 about £15.  absolutely great, i use one to connect my laptop - ok
 _used_ to (it's dead) - to an embedded serial box, ran console on
 that, worked perfectly.  bizarre, going back to 30-year-old
 technology, but there you go.

 l.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/aanlktinbkogp50ovaelxuq+2nedb3uxuw3pihooie...@mail.gmail.com

Re: Reports of successful Squeeze upgrades

[Björn Wetterbom]

Yup, that's it.

On Thu, Feb 24, 2011 at 09:51, John Winters j...@sinodun.org.uk wrote:

 On 23/02/11 18:42, Martin Michlmayr wrote:
 [snip]


 I upgraded a NSLU2 to squeeze yesterday without any problems but the
 system was a base system of lenny without any additional software
 installed.

 It would be great if other users could comment.  So far, I've seen one
 problem report about the RAID uuid changing.


 I have a turbo-slug which isn't doing much and is running pretty
 vanilla Lenny. I could upgrade that to Squeeze as a test case if it
 would help.

 Are there any particular parameters which you'd like set first in order
 to test them? Is it just the usual


 Edit /etc/apt/sources.list
 apt-get update
 apt-get install linux-image-mumble
 apt-get install udev
 reboot
 apt-get upgrade
 apt-get dist-upgrade

 ?

 Cheers,
 John







 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4d661bf9.8080...@sinodun.org.uk

Reports of successful Squeeze upgrades

[Björn Wetterbom]

Following the recent conversations regarding upgrade problems I would
appreciate some success stories before I attempt the upgrade on my
(production) machines. Anyone willing to share? Please state your device
type as well (I run an NSLU2 and a TS-209 with Lenny).

Thanks
Björn

Re: flashing fails due to size issue during upgrade

[Björn Wetterbom]

So what's the bottom line of this for the average user? Should I take any
precautionary measures before upgrading my slug to Squeeze (I will of course
follow the instructions in the release notes)? Is it clear why Jeffrey's
ramdisk didn't fit in the flash?

Regards
Björn
On Feb 21, 2011 8:39 PM, Jeffrey B. Green j...@kikisoso.org wrote:
 On 02/21/2011 11:18 AM, Martin Michlmayr wrote:
 * Jeffrey B. Greenj...@kikisoso.org [2011-02-18 13:53]:
 # /etc/initramfs-tools/initramfs.conf
 # replace most with dep
 MODULES=dep

 Anyone out there know of any pitfalls in this approach?? I.e. are all
 the crucial modules included in the initrd?

 Yeah, it should work fine.

 Make sure to make a backup of your flash before you install the new
 ramdisk:
 cat /dev/mtdblock? backup


 It did indeed reboot okay. I waited about a day or so and then made the
 plunge.

 The only thing now that is not working quite right after the upgrade is
 IPv6 on the overclocked slug. It configures okay from boot on the stock
 slug. However, the overclocked one doesn't seem to configure the IPv6
 interface on boot. Maybe a timing issue.

 If you have an idea as to why that may be so, then that would be great.

 Thanks for the feedback regarding the mods.

 -jeff


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
 Archive: http://lists.debian.org/4d62bb7f.8010...@kikisoso.org

Re: SD not detected when installing to sheevaplug

[Björn Wetterbom]

Try re-downloading the installer, that solved the modules problem for me.

On Jul 17, 2010 4:55 PM, Carles Pagès bona...@gmail.com wrote:

I'm trying to install debian lenny to a sheeva plug following the
instructions on Martin's page. When the installer finishes the
hardware detection, I get an error stating that no partitionable media
was found. I have an SD card in the slot, which I previously had used
with a debian tarball (so it should work).

Has anyone experienced something similar? During the installation I
received a warning that no modules were found for the current kernel?
Is this normal or could it be the cause of the error I'm getting?

Thanks


--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktin87cfyyzocag_eeetssyrflmajqtk3rk9_6...@mail.gmail.com

Re: John Holland's eSATA support for the Sheevaplug

[Björn Wetterbom]

 I just aked on IRC and was told that the latest blocker was #572618,
 which was fixed in the kernel upload done yesterday.  So hopefully the
 kernel will move to squeeze soon and then we can update the installer.

Can you please announce on the list when this happens. I'm considering
an nslu2-to-esatasheeva upgrade.

/Björn


--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktilzg1ruqgs9rqihde8kkxejp_yic81zzynpw...@mail.gmail.com

Re: Managed to brick my sheevaplug -- not getting any serial output

[Björn Wetterbom]

I threw my cable away months ago after big problems with it
disconnecting serial access. Now I just use any mini-USB cable lying
around.

On Thu, Mar 11, 2010 at 09:18, Shiva Bhattacharjee shiva...@gmail.com wrote:
 Is it necessary for me to use the same mini-usb cable that came with the
 sheevaplug? It seems my host machines ( windows, linux, mac) all recognize
 the sheevaplug  but when I try connecting to the serial port I get
 nothing...

 I think I am running into the same problem with the installer as well,
 .
 jtag_nsrst_delay: 200
 jtag_ntrst_delay: 200
 dcc downloads are enabled
 Error: unable to open ftdi device: device not found
 Runtime error, file command.c, line 469:
     openocd FAILED
     Is the mini USB cable connected?
     Try powering down, then replugging the Sheevaplug

 This particular snapshot is from my windows box, but I have installed the
 ftdi driver and the USB Serial Device shows up both under Device Manager
 and putty seems to connect on the correct COM4 port, but just doesn't show
 anything


 On Wed, Mar 10, 2010 at 1:48 PM, Martin Michlmayr t...@cyrius.com wrote:

 * Lluís Batlle virik...@gmail.com [2010-03-10 22:41]:
  The plugcomputer.org wiki or places like that will give you
  information on how to do that.

 Exactly.  Search for installer v1.0.
 --
 Martin Michlmayr
 http://www.cyrius.com/




--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3005d6291003110154s6b556cadx9873f55a11df1...@mail.gmail.com

Re: Managed to brick my sheevaplug -- not getting any serial output

[Björn Wetterbom]

Newer kernels don't use /dev/ttyUSB0 for JTAG. It is used for serial
access and no /dev/ttyUSB1 will appear.

Check out 
http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux

On Thu, Mar 11, 2010 at 11:29, Lluís Batlle virik...@gmail.com wrote:
 2010/3/11 Shiva Bhattacharjee shiva...@gmail.com:
 Is it necessary for me to use the same mini-usb cable that came with the
 sheevaplug? It seems my host machines ( windows, linux, mac) all recognize
 the sheevaplug  but when I try connecting to the serial port I get
 nothing...

 I think I am running into the same problem with the installer as well,
 .
 jtag_nsrst_delay: 200
 jtag_ntrst_delay: 200
 dcc downloads are enabled
 Error: unable to open ftdi device: device not found

 Device not found? Are you sure your system has /dev/ttyUSB0 in place,
 after connecting the cable? You should configure openocd to access
 that device.
 In a typical udev-enabled linux, you will see /dev/ttyUSB0 only with
 the cable connected.

 Regards,
 Lluís.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/45219fb01003110229n36771deemd43ddc401bd25...@mail.gmail.com




--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3005d6291003111400r4fd454d0se09997fdc0017...@mail.gmail.com

Re: Very newbe help/pointers required about building a distribution from scratch

[Björn Wetterbom]

Could Linux from scratch provide you with at least some of the
information you need?

http://www.linuxfromscratch.org/

On Wed, Mar 10, 2010 at 19:10, Jonathan Wilson
piercing_m...@hotmail.com wrote:
 Ok I'm quite a newbe to both Linux and PC development, however I know
 what I want to do but don't know where to start!

 What I'd like to know is how do I build a distribution entirely from
 scratch/source like the pro's do.

 ie. Get all the debian source for the latest arm port (just the source)
 and then compile/build it till I have a working system.

 Why would I want to do this? Well first of I want to optimize the final
 code to specific processors (OMAP3530 and ARM926EJ-S) and also customise
 the builds to use different application/graphic components such as
 gnome, E17, samba, etc. I also figure this is a great way to learn about
 Linux/debian and fixing any bugs will give me some insight into the
 various languages (C/C++ specifically)

 I'm sure there must be some product or methodoligy that the pro's use to
 build debian distributions with different tweaks where the code has to
 branch (eg, Ubuntu desktop V NBR) so that all the common code remains
 common and some kinds of config files then set the options (some kind of
 global system makefile? or .config file?)

 Surely its not a case of downloading each package source manually,
 checking that all the dependents are downloaded, then manually doing a
 make config / make / make install for each and every package and having
 one directory structure for each distribution?

 Any pointers would be welcome as google is not my friend as I can't find
 anything about taking a current distribution and compiling the whole.
 (it did find stuff about making packages, and rebuilding an already
 installed distribution, both of which are not what I want, lol)

 JonXx


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/blu0-smtp589ce1ec813b4cac037faa98...@phx.gbl




-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3005d6291003101108g32166979vaf02b5de6dfba...@mail.gmail.com

Re: Very newbe help/pointers required about building a distribution from scratch

[Björn Wetterbom]

It was a while ago since I did any reading on LFS, but as far as I can
remember it simply gives you instructions on how to build a custom
Linux OS from scratch by downloading all the sources one by one
yourself. I guess that means that the answer to all of your questions
is no.

2010/3/10 Luke Kenneth Casson Leighton l...@lkcl.net:
 2010/3/10 Björn Wetterbom bjohv...@gmail.com:
 Could Linux from scratch provide you with at least some of the
 information you need?

  is that available for debian?  does it rebuild _debian_ packages,
 entirely and recursively, recreating a debian mirror with a specific
 set of architecture-specific compiled packages?

  l.



--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3005d6291003101131v192169fbrcab97928a8ac5...@mail.gmail.com

Re: Alternative to using USB-Stick as mass storage on NSLU2

[Björn Wetterbom]

I've used a Freecom 2.5 drive for a couple of years with good
results. USB powered of course.

I've also used an external WD 3.5 drive which I am very pleased with,
and since WD offers a wide variety of 2.5 drives at good prices I
would go for one of those.

/Björn



On Thu, Feb 18, 2010 at 18:02,  u7l1...@mail.lrz-muenchen.de wrote:
 John Holland wrote

 You could use a 2.5 HDD. The Momentus has a typical usage specified @
 1.5W seek and .7W idle.

 Thanks for pointing out the low energy consumption of modern 2.5 HDs.
 Since others mentioned that SD is even less suitable for my purpose, I
 think I'll go that route.

 Can anybody recommend a specific model of an external 2.5 drive that
 works well with a slug under Debian (Lenny armel), preferably USB-powered
 so I don't need an extra power supply?

 I've read a lot on nslu2-linux.org about spindown issues with HDs
 connected to a slug. Since my slug is logging data continuously 24/7, I
 guess I shouldn't let the HD spin down at all. Is that assumption correct?

 Regards, Richard


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/64062.84.150.195.114.1266512576.squir...@webmail.lrz-muenchen.de




--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3005d6291002180955g2be49839w3ea5270e09492...@mail.gmail.com

News from GlobalScale Technologies

[Björn Wetterbom]

Have you guys seen the coming products from GST? (Announced Jan 24
according to the web site.)

http://www.globalscaletechnologies.com/c-4-guruplugs.aspx

Incredible what they can pack into these things, the new plugs look
sooo cool. The only thing I can't figure out is the configuration of
the two version of the GuruPlug Display. One is said to have HDMI, and
the other touch panel display. But neither can be seen in the
pictures. Anyone got a clue?

/Björn


--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Need help to boot debian on USB with more devices connected

[Björn Wetterbom]

Isn't this a well known issue with usb-booted devices? See e.g.
http://www.nslu2-linux.org/wiki/Debian/TroubleShooting (section The slug
fails to reboot with 2 drives connected). I guess you have already figured
out that you can boot by detaching all devices except the boot disk.

Will it perhaps be solved when (if?) Squeeze introduces UUIDs in /etc/fstab,
or is it an unsolvable problem since the kernel doesn't pick up the boot
device from /etc/fstab (according to the above link)?

Hmm, seems I came up with more questions than answers. Help, anyone?

/Björn


On Wed, Oct 7, 2009 at 21:19, Douglas Lopes Pereira 
douglaslopespere...@gmail.com wrote:

 Hi guys,

 I'm trying to power up my Sheeva Plug (which is configured to boot
 Martin's debian from USB drive) with my USB drive connected over an
 USB hub with other devices on it (i.e Usb headset).

 Uboot identifies the devices connected but does not recognize my USB
 drive and get stuck.

 This is what I see from my terminal:

 === TERMINAL OUTPUT =
 U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

 U-Boot code: 0060 - 0067FFF0  BSS: - 006CF100

 Soc: 88F6281 A0 (DDR2)
 CPU running @ 1200Mhz L2 running @ 400Mhz
 SysClock = 400Mhz , TClock = 200Mhz

 DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
 DRAM CS[0] base 0x   size 256MB
 DRAM CS[1] base 0x1000   size 256MB
 DRAM Total size 512MB  16bit width
 Flash:  0 kB
 Addresses 8M - 0M are saved for the U-Boot usage.
 Mem malloc Initialization (8M - 7M): Done
 NAND:512 MB

 CPU : Marvell Feroceon (Rev 1)

 Streaming disabled
 Write allocate disabled


 USB 0: host mode
 PEX 0: interface detected no Link.
 Net:   egiga0 [PRIME], egiga1
 Hit any key to stop autoboot:  0
 (Re)start USB...
 USB:   scanning bus for devices...
  USB device not responding, giving up (status=20)
 4 USB Device(s) found
   scanning bus for storage devices...

 === TERMINAL OUTPUT =

 Does anyone know how to boot my system without removing other stuff
 from my usb hub?

 Thanks for your attention.

 Regards,
 Douglas


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org

Re: QNAP TS 209 software RAID?

[Björn Wetterbom]

I have run hardware raid in the past, and have heard opinions from
several others. To make a long story short, software raid is now the
only way I go. I believe the TS-209 does not support hardware raid. I
run software raid 1 on mine with an excellent track record.

On Wed, Aug 12, 2009 at 16:56, Zarick Lauzar...@gmail.com wrote:
 Hi list,
 I've recently bought a QNAP TS 209 and I'm going to install debian on it.
 While I've started the debian installer, I just think I missed one thing.
 Does this box provide hardware RAID?
 As I never used hardware RAID before, and QNAP website haven't said anything
 about how the RAID functionality is implemented in the original firmware.
 I believe it should be software RAID only, but want to get some advice here!
 Best regards,
 Zarick


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Sheevaplug late? - Call them!

[Björn Wetterbom]

Seems to me that several people have reported a speedy delivery of
their sheevaplug after calling Globalscale. Yesterday the same thing
happened to me. When calling (+1-714-632-9239), I was told that
expected delivery was a week or more away, which would have meant a
total delivery time of more than six weeks. Four hours later, a
tracking number was issued by FedEx. Coincidence? I think not.

Now I must quickly get my hands on a suitable usb stick, while waiting
for Martins tar ball to work on my SD card. Huge amount of cred to
Martin for his outstanding work.


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [SheevaPlug] Order not received

[Björn Wetterbom]

Well, I ordered mine on the 30th of March and I'm still waiting for
any word on when delivery will be. The only clue is given at

http://www.globalscaletechnologies.com/c-2-globalscale-technologies-products.aspx

It would be nice if any list member that receives a plug could
announce this on the list.

On Tue, Apr 7, 2009 at 17:39, Hector Oron hector.o...@gmail.com wrote:
 Hi,

 Encouraged to help on the sheevaplug debian integration, I ordered a
 while ago (3/10/2009) from GlobalScale Technologies such device, but it
 never arrived to my place. I am not sure if you have had similar
 troubles. I have mailed them a couple or three times with no answer.

 Kind Regards,
  Hector Oron


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org




--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Regarding Kirkwood cpu support

[Björn Wetterbom]

I'd love to help out to the best of my abilities. Please tell me how.

2009/3/25 Wouter Verhelst wou...@debian.org:
 On Wed, Mar 25, 2009 at 04:56:37PM +0100, Björn Wetterbom wrote:
 What kind of time frames are we talking about when it comes to Debian
 support for Kirkwood for us ordinary users who don't compile our own
 kernels and want our machine to start every day, every time?

 Will initial support consist of install packages from Martin or
 others, and official Debian support be available only in Debian
 Squeeze?

 That's what it looks like for now.

 The reason I am asking is that I am thinking Should I buy a
 SheevaPlug now or wait a couple of months?

 I'd suggest the latter, unless you want to help out -- there are ways to
 do that, even if you don't know how to write code.

 --
 Lo-lan-do Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22



--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Regarding Kirkwood cpu support

[Björn Wetterbom]

What kind of time frames are we talking about when it comes to Debian
support for Kirkwood for us ordinary users who don't compile our own
kernels and want our machine to start every day, every time?

Will initial support consist of install packages from Martin or
others, and official Debian support be available only in Debian
Squeeze?

The reason I am asking is that I am thinking Should I buy a
SheevaPlug now or wait a couple of months?

On Tue, Mar 17, 2009 at 10:30, Lennert Buytenhek buyt...@wantstofly.org wrote:

 On Tue, Mar 17, 2009 at 09:34:18AM +0100, Thomas Boehne wrote:

   On the 6281 at 1.2 GHz, I get wire speed TCP transmit when GSO is
   enabled, and wire speed TCP receive when LRO is enabled (which
   mv643xx_eth supports since recently -- it's currently in net-next).
 
  Wirespeed sounds extremely interesting. I guess the CPU load is
  near 100% then, correct? Thanks for your input so far.

 CPU load on wire speed TCP receive is ~70% when copying everything
 to userspace (i.e. a userland recv() loop on the socket).  When
 discarding all the data in kernelspace (e.g. splice() to /dev/null,
 with a hack to make sure that the linear part of skbuffs doesn't get
 copied into a separate area first or with a patch to make mv643xx_eth
 receive into pages), it's closer to ~30%.  This are measured with
 cyclesoak with MTU=1500, and are pretty consistent.

 CPU load on wire speed TCP transmit is pretty variable, due to GSO
 behaving eratically when there isn't enough CPU to transmit wire
 speed without using GSO.  (I.e. it seems that GSO will always converge
 into a stable state where it will saturate the wire at the same low CPU
 usage if the CPU is powerful enough to transmit wire speed without using
 GSO, but if you only get ~90MB/s-ish without using GSO, it seems that
 there are different stable states you can get into depending on
 burstiness of ACKs from the other side and some other factors.  So
 sometimes it converges to 2 real segments per GSO skbuff and stays
 there, sometimes to 3 real segments per GSO skbuff, etc.)  I sent
 some emails about this to netdev@ some time ago, but didn't find a
 good way of dealing with this yet.


 --
 To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Regarding Kirkwood cpu support

[Björn Wetterbom]

I just joined the list and sifted through a couple of months of the archive.
With regards to Martin Michlmayr starting up work on Kirkwood support (
http://lists.debian.org/debian-arm/2009/02/msg00057.html) I wanted to share
a link concerning a Kirkwood application:

http://techreport.com/discussions.x/16466

Although 512 Mb worth of flash is a bit tiny (I mean, what would it cost to
add another 4 Gb?) it's a neat application. I'm sure I could think of some
cool use for it.

While I'm at it, thank you Martin for all your work! I just upgraded my
nslu2 to armel. That and my ts209 are so much fun.