Re: Kernel 2.6.37 on QNAP TS-419P
Martin Michlmayr wrote: > * Benoît Knecht [2011-03-23 12:20]: > > Now that linux-image-2.6.38-1-kirkwood is out, I tried that one too, > > but it seems to fail in the same way (there's some disk activity, > > but then it just hangs and the status led keeps blinking red and > > green forever). I'll try to get a serial cable to see what's > > happening. > > Maybe you ran into #621137. Can you try again with the latest busybox > from unstable? If it still doesn't boot, I can get my TS-419P out > next week and take a look. Oh, I'm sorry, I wanted to update this thread last week but somehow kept delaying it... Bottom line is, it works now, and the problem was btrfs related (busybox was fine). Once I got hold of a serial cable, I could see that the boot process failed during the execution of some initscript that was trying to write to the disk. It seems that the way of computing when a btrfs filesystem is full has changed sometime between 2.6.32 and 2.6.37, and so the boot process was going fine with 2.6.32 (the initscripts could write to the disk), while it would fail on 2.6.37 and 2.6.38 (because of a "no space left on device" error). After copying the system files to a newly formatted btrfs disk, updating the UUID in the initramfs, and rebooting, everything went fine, and I was able to selectively copy the rest of my data from the old disk. Thanks a lot for offering to look into this problem, and sorry it took me so long to investigate it myself. -- Benoît Knecht -- 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/20110426150905.gc21...@marvin.lan
Re: Kernel 2.6.37 on QNAP TS-419P
Benoît Knecht wrote: > I've been trying to get the Debian sid kernel to boot on my QNAP TS-419P > (currently linux-image-2.6.37-2-kirkwood, but I tried > linux-image-2.6.37-1-kirkwood before that), and unfotunately it just > hangs upon reboot (the status led keeps blinking alternatively green and > red) and I have to use the rescue mode to flash the squeeze kernel back. Now that linux-image-2.6.38-1-kirkwood is out, I tried that one too, but it seems to fail in the same way (there's some disk activity, but then it just hangs and the status led keeps blinking red and green forever). I'll try to get a serial cable to see what's happening. -- Benoît Knecht -- 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/20110323112056.gb12...@debian.lan
Kernel 2.6.37 on QNAP TS-419P
Hi everyone, I've been trying to get the Debian sid kernel to boot on my QNAP TS-419P (currently linux-image-2.6.37-2-kirkwood, but I tried linux-image-2.6.37-1-kirkwood before that), and unfotunately it just hangs upon reboot (the status led keeps blinking alternatively green and red) and I have to use the rescue mode to flash the squeeze kernel back. Since I don't have a serial cable, I really don't know what's going on, so I was wondering if anyone tried this (on this or a similar kirkwood system) and could report on sucess/failure. I'd like to know if the problem is specific to my configuration or if others have the same issue. The most particular thing about my system is that it's using btrfs as the root filesystem, so it could be related to that, although I'm pretty sure all the required modules are included in the initramfs (I even listed them explicitly in /etc/initramfs-tools/modules just to make sure). Any feedback/ideas welcome. Thanks. -- Benoît Knecht -- 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/20110312163609.gb15...@debian.lan
Re: qcontrol development
Hi Bas, Bas Delfos wrote: > I also have an old P4 running squeeze on it, can i some how build the > qcontrol executable on an i386 with another target architecture? > Because I already build the last sources of qcontrol on the P4, but > the executable doesn't run on the QNAP (I have the build param -aarmel > specified)? I'm sure there are many other solutions, but what has worked best for me so far is qemubuilder. It runs a complete debian armel system in qemu and compiles your package there. Once you have a dsc file for your software, it's as simple as running $ qemubuilder --build yourpackage.dsc Hope this helps. -- Benoît Knecht -- 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/20110312122448.ga15...@debian.lan
Re: QNAP TS-209: kernel 2.6.32-5-orion5x does not fit in flash
Martin Michlmayr wrote: > * Benoît Knecht [2011-02-21 13:27]: > > I have the same issue when trying to upgrade my Qnap TS-209. Did > > anyone find a solution for this? > > Do you have btrfs-tools installed? This was the cause of Marcus' > problems because btrfs-tools causes modules to be put into the ramdisk > that you don't actually need (see #584714). As a matter of fact, I did. Removing that package made the problem go away. Thanks a lot for your help! Cheers, -- Benoît Knecht -- 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/20110221171612.gb8...@debian.lan
Re: QNAP TS-209: kernel 2.6.32-5-orion5x does not fit in flash
Hi, Martin Michlmayr wrote: > * Marcus Better [2011-01-15 21:07]: > > I now get the "kernel does not fit in flash" problem with the squeeze > > kernel: > > > > linux-image-2.6.32-5-orion5x 2.6.32-30 > > > > update-initramfs: Generating /boot/initrd.img-2.6.32-5-orion5x > > The RootFS1 doesn't fit in flash. > > I'm on holidays at the moment but I'll try to take a look. Can you > make /boot/initrd.img-2.6.32-5-orion5x (the one that does not fit) and > /boot/initrd.img-2.6.32-5-orion5x.bak (the one that fits) available > somewhere and send me an URL. I have the same issue when trying to upgrade my Qnap TS-209. Did anyone find a solution for this? I suspect it has to do with my removing of http://people.debian.org/~tbm/orion from /etc/apt/sources.list (as there is no squeeze distribution there). So I'm currently running kernel 2.6.32-5-orion5x from Martin's repository, but when "upgrading" to 2.6.32-5-orion5x from the main squeeze repository, I get the error reported above. At least I think that's what's happening. Anyway, if you don't have them yet, I can make the initrd.img files available, although I'm not sure I have the one that fits anymore. I ran the upgrade command twice, and the only 2.6.32-5 initrd files that I have are: -rw-r--r-- 1 root root 4217759 Feb 21 13:04 /boot/initrd.img-2.6.32-5-orion5x -rw-r--r-- 1 root root 4217762 Feb 21 13:03 /boot/initrd.img-2.6.32-5-orion5x.dpkg-bak Thanks in advance for looking into this, and let me know if I should provide any more information. Cheers, -- Benoît Knecht -- 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/20110221122709.gc8...@debian.lan
Re: Bug #522583: fping broken on some arm systems?
Niko Tyni wrote: > Could a few armel users please install fping 2.4b2-to-ipv6-16.1 from > squeeze or sid (it's also installable on a plain lenny system) and report > back (either privately to me or to 522...@bugs.debian.org) if they see > things like [...] Nothing weird on my Qnap 209 Pro II: $ uname -a Linux Qnap-209-Pro-II 2.6.32-5-orion5x #1 Sat Sep 18 21:31:50 UTC 2010 armv5tel GNU/Linux $ cat /proc/cpuinfo Processor : Feroceon rev 0 (v5l) BogoMIPS: 332.59 Features: swp half thumb fastmult edsp CPU implementer : 0x41 CPU architecture: 5TEJ CPU variant : 0x0 CPU part: 0x926 CPU revision: 0 Hardware: QNAP TS-109/TS-209 Revision: Serial : $ fping -C 1 127.0.0.1 127.0.0.1 : [0], 84 bytes, 0.42 ms (0.42 avg, 0% loss) 127.0.0.1 : 0.42 $ fping -ei 1000 -c 10 194.109.5.227 194.109.5.227 : [0], 84 bytes, 25.1 ms (25.1 avg, 0% loss) 194.109.5.227 : [1], 84 bytes, 177 ms (101 avg, 0% loss) 194.109.5.227 : [2], 84 bytes, 350 ms (184 avg, 0% loss) 194.109.5.227 : [3], 84 bytes, 391 ms (235 avg, 0% loss) 194.109.5.227 : [4], 84 bytes, 73.0 ms (203 avg, 0% loss) 194.109.5.227 : [5], 84 bytes, 252 ms (211 avg, 0% loss) 194.109.5.227 : [6], 84 bytes, 273 ms (220 avg, 0% loss) 194.109.5.227 : [7], 84 bytes, 210 ms (219 avg, 0% loss) 194.109.5.227 : [8], 84 bytes, 233 ms (220 avg, 0% loss) 194.109.5.227 : [9], 84 bytes, 299 ms (228 avg, 0% loss) 194.109.5.227 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 25.1/228/391 No problem on my Qnap 419P either: $ uname -a Linux Qnap-419P 2.6.32-5-kirkwood #1 Sat Sep 18 15:20:08 UTC 2010 armv5tel GNU/Linux $ cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS: 1199.30 Features: swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part: 0x131 CPU revision: 1 Hardware: QNAP TS-41x Revision: Serial : $ fping -C 1 127.0.0.1 127.0.0.1 : [0], 84 bytes, 0.16 ms (0.16 avg, 0% loss) $ fping -ei 1000 -c 10 194.109.5.227 194.109.5.227 : [0], 84 bytes, 242 ms (242 avg, 0% loss) 194.109.5.227 : [1], 84 bytes, 390 ms (316 avg, 0% loss) 194.109.5.227 : [2], 84 bytes, 330 ms (321 avg, 0% loss) 194.109.5.227 : [3], 84 bytes, 26.3 ms (247 avg, 0% loss) 194.109.5.227 : [4], 84 bytes, 249 ms (247 avg, 0% loss) 194.109.5.227 : [5], 84 bytes, 238 ms (246 avg, 0% loss) 194.109.5.227 : [6], 84 bytes, 155 ms (233 avg, 0% loss) 194.109.5.227 : [7], 84 bytes, 115 ms (218 avg, 0% loss) 194.109.5.227 : [8], 84 bytes, 143 ms (210 avg, 0% loss) 194.109.5.227 : [9], 84 bytes, 119 ms (201 avg, 0% loss) 194.109.5.227 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 26.3/201/390 -- Benoît Knecht -- 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/20101119003241.ga4...@debian.lan
Re: Debian installer on Qnap TS-419P
Martin Michlmayr wrote: > * Benoît Knecht [2010-10-01 22:48]: > > From what I understand, since the > > kernel and initrd are in flash, there's no need for a separate boot > > partition. So I created one anyway, but if someone can confirm I > > don't > > need it, I'll remove it. > > You're correct that there's no need for a separate /boot partition. > This error is produced by partman-btrfs's check.d/no_btrfs_boot > script. I suggest you file a bug on the partman-btrfs package about > this issue. OK, thanks for your advice. I've filed a bug on partman-btrfs at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599417. -- Benoît Knecht -- 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/20101007140806.gb5...@debian.lan
Debian installer on Qnap TS-419P
Hi, I just wanted to report success on using the debian installer on a Qnap TS-419P. Martin's instructions [1] still recommend a manual installation, but I found this post [2] where he suggests the installer might work just fine. For some reason, I first found this installer [3] which booted okay, but I decided to try the regular sid installer [4] anyway; I completed the installation of debian squeeze with the sid installer (in expert mode). After making a backup of the original firmware, I used the recovery mode with a TFTP server to get the installer image on the device (after I finally noticed that it's trying to get the image from ethernet port 2, not 1). Everything went fine except two glitches. First, partman wouldn't let me format any partition with btrfs, although mkfs.btrfs was present and I saw partman-btrfs being downloaded. After formating the partition manually (i.e. using mkfs.btrfs) and unsuccessfully trying to mount it, I noticed the btrfs kernel module wasn't loaded; trying to modprobe it gave me the error: FATAL: Error inserting btrfs (/lib/modules/2.6.32-5-kirkwood/kernel/fs/btrfs/btrfs.ko): Unknown symbol in module, or unknown parameter (see dmesg) Turns out, btrfs.ko depends on crc32c.ko, which wasn't included. So I downloaded linux-image-2.6.32-5-kirkwood_2.6.32-23_armel.deb and extracted it on a USB stick, from which I copied crc32c.ko to /lib/modules/2.6.32-5-kirkwood/kernel/crypto/. After running depmod, btrfs loaded successfully. From there, the "Partition disks" step in the installer offered me the option of btrfs. The second issue I encountered, right after formatting the disk, was that it wouldn't let me proceed with no boot partition (I had only swap and a big btrfs root partition). From what I understand, since the kernel and initrd are in flash, there's no need for a separate boot partition. So I created one anyway, but if someone can confirm I don't need it, I'll remove it. And that's it. I just wanted to let other people tempted by having debian on their Qnap TS-419P that they can do it rather easily with the installer (and feel free to contact me if you need any help). Also, if some testing is needed on this NAS, I'd be happy to give it a try. Cheers. -- Benoît Knecht --- [1] http://www.cyrius.com/debian/kirkwood/qnap/ts-41x/ [2] http://forum.qnap.com/viewtopic.php?f=147&t=32552 [3] http://people.debian.org/~joeyh/d-i/armel/images/daily/kirkwood/network-console/qnap/ts-41x/ [4] http://ftp.de.debian.org/debian/dists/sid/main/installer-armel/current/images/kirkwood/network-console/qnap/ts-41x/ -- 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/20101001204806.ga26...@debian.lan
Re: Apple partition table
On Wed, Nov 19, 2008 at 18:47, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > This will be in the next kernel upload. Thanks for the suggestion, > Benoît. Great, thank you very much!
Re: Apple partition table
To clarify a bit, I'm talking about the CONFIG_MAC_PARTITION kernel option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Apple partition table
On Wed, Nov 19, 2008 at 15:06, Gordon Farquharson <[EMAIL PROTECTED]> wrote: > On Wed, Nov 19, 2008 at 06:30, Benoît Knecht <[EMAIL PROTECTED]> wrote: > >> I have installed debian on my Qnap TS-209, and except for some >> (apparently known) performance issues, everything went fine. >> Then I tried to use my external USB disk, which I partitioned using >> apple partition table. This partition type is not recognized by the >> current kernel (2.6.26-1-orion5x), and since I'm not familiar with the >> debian way of kernel building, I would like to ask if it's possible to >> include this option in the next release. > > In /boot/config-2.6.26-1-orion5x, > > CONFIG_HFSPLUS_FS=m > > so, it looks like the HPS Plus file system support is built as a > module in the Debian kernel. No, no, I'm talking about the apple partition table, not the filesystem (on my disk, it's actually ReiserFS).
Apple partition table
Hi, I have installed debian on my Qnap TS-209, and except for some (apparently known) performance issues, everything went fine. Then I tried to use my external USB disk, which I partitioned using apple partition table. This partition type is not recognized by the current kernel (2.6.26-1-orion5x), and since I'm not familiar with the debian way of kernel building, I would like to ask if it's possible to include this option in the next release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
