[OpenWrt-Devel] Only have 0 available blocks on filesystem /
Hi, I have Asus wl500gp, and wanted to upgrade: /# opkg upgrade and got the following message: ... * Only have 0 available blocks on filesystem / ... ... the 'df' output is: FilesystemSize Used Avail Use% Mounted on rootfs1.4M 1.4M 0 100% / /dev/root 1.4M 1.4M 0 100% /rom tmpfs 15M 840K 14M 6% /tmp tmpfs 512K 0 512K 0% /dev /dev/mtdblock35.7M 1.2M 4.5M 21% /jffs mini_fo:/jffs 1.4M 1.4M 0 100% / /dev/sda2 3.7G 1021M 2.5G 29% /mnt/usbdrive I don't really understand the filesystem structure used on OpenWrt. AFAIK, the root filesystem always shows 0 available blocks, however, e.g. 1Mb sized files can be created in directories /, /lib, /bin, etc., using the 4.5M free space from /jffs. Why opkg cannot do it? Thanx in advance K. Gy. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Jabber/XMPP Lua Server
Hi Florian, I tested the packages and I find a little bug in the luasocket package , here the patch. Ciao! Lorenzo Florian Fainelli ha scritto: Hey again Lorenzo, Patches integrated in changesets 14518 to 14521. Thanks a lot ! Index: luasocket/Makefile === --- luasocket/Makefile (revision 14531) +++ luasocket/Makefile (working copy) @@ -22,7 +22,7 @@ SUBMENU:=LUA SECTION:=lang CATEGORY:=Languages - TITLE:=LUASec + TITLE:=LUASocket URL:=http://luasocket.luaforge.net/ DEPENDS:=lua endef ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Jabber/XMPP Lua Server
Hey Lorenzo, Le Tuesday 17 February 2009 14:41:16 OrazioPirataDelloSpazio (Lorenzo), vous avez écrit : Hi Florian, I tested the packages and I find a little bug in the luasocket package , here the patch. Patch applied in changeset 14538, thanks ! -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] (no subject)
Index: sound/mpc/patches/01-uclibc.patch
===
--- sound/mpc/patches/01-uclibc.patch (Revision 0)
+++ sound/mpc/patches/01-uclibc.patch (Revision 0)
@@ -0,0 +1,15 @@
+Index: mpc-0.15/src/main.c
+===
+--- mpc-0.15.orig/src/main.c
mpc-0.15/src/main.c
+@@ -190,7 +190,9 @@ static mpd_Connection * setup_connection
+ static struct command *
+ find_command(const char *name)
+ {
+- for (unsigned i = 0; mpc_table[i].command != NULL; ++i)
++ unsigned i = 0;
++
++ for (i = 0; mpc_table[i].command != NULL; ++i)
+ if (strcmp(name, mpc_table[i].command) == 0)
+ return mpc_table[i];
+
Index: sound/mpc/Makefile
===
--- sound/mpc/Makefile (Revision 14534)
+++ sound/mpc/Makefile (Arbeitskopie)
@@ -9,12 +9,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=mpc
-PKG_VERSION:=0.14
+PKG_VERSION:=0.15
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=...@sf/musicpd
-PKG_MD5SUM:=f4218602342cf322872a41dfe0cc72e1
+PKG_MD5SUM:=48897aeb3a7ee5c64f30e56789f105a8
include $(INCLUDE_DIR)/package.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] update mpc to 0.15 and fix compilaton
Index: sound/mpc/patches/01-uclibc.patch
===
--- sound/mpc/patches/01-uclibc.patch (Revision 0)
+++ sound/mpc/patches/01-uclibc.patch (Revision 0)
@@ -0,0 +1,15 @@
+Index: mpc-0.15/src/main.c
+===
+--- mpc-0.15.orig/src/main.c
mpc-0.15/src/main.c
+@@ -190,7 +190,9 @@ static mpd_Connection * setup_connection
+ static struct command *
+ find_command(const char *name)
+ {
+- for (unsigned i = 0; mpc_table[i].command != NULL; ++i)
++ unsigned i = 0;
++
++ for (i = 0; mpc_table[i].command != NULL; ++i)
+ if (strcmp(name, mpc_table[i].command) == 0)
+ return mpc_table[i];
+
Index: sound/mpc/Makefile
===
--- sound/mpc/Makefile (Revision 14534)
+++ sound/mpc/Makefile (Arbeitskopie)
@@ -9,12 +9,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=mpc
-PKG_VERSION:=0.14
+PKG_VERSION:=0.15
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=...@sf/musicpd
-PKG_MD5SUM:=f4218602342cf322872a41dfe0cc72e1
+PKG_MD5SUM:=48897aeb3a7ee5c64f30e56789f105a8
include $(INCLUDE_DIR)/package.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] update mpd to 0.14.2 and bump release
Index: sound/mpd/Makefile === --- sound/mpd/Makefile (Revision 14534) +++ sound/mpd/Makefile (Arbeitskopie) @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=mpd -PKG_VERSION:=0.14 -PKG_RELEASE:=1 +PKG_VERSION:=0.14.2 +PKG_RELEASE:=2 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=...@sf/musicpd -PKG_MD5SUM:=ee282390146ead636f3d992399ed3c20 +PKG_MD5SUM:=66817a4b4c05454e6488f6b821f2a6a3 include $(INCLUDE_DIR)/package.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Marvell Orion platform help
Hi! I have managed to port Freecom Datatank Gateway to vanilla kernel Marvell Orion architecture, but I need some help. Is there anyone who could help me with proper registers settings? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
Hi, i have the same problem using kexec with buffalo whr g54s openwrt rc2 kernel 2.4: kexec_load failed: Success entry = 0x298000 flags = 0 nr_segments = 2 segment[0].buf = 0x2ac37008 segment[0].bufsz = 27307b segment[0].mem = 0x1000 segment[0].memsz = 297000 segment[1].buf = 0x456338 segment[1].bufsz = 1a4 segment[1].mem = 0x298000 segment[1].memsz = 1000 is there any solution for this? Am 07.02.2009 12:25, schrieb Florian Fainelli: Hi Brian, Le Saturday 07 February 2009 05:45:44 Brian J. Murrell, vous avez écrit : I have an asus wl500gp that I'm trying to kexec a kernel on. I had written about this before but have another bit of info and I'm hoping it rings a bell for someone so that I don't have to through the painful process of printk() instrumenting the kernel and flashing new kernels with more and more debug. Anyway, my command line is: # kexec -l /vmlinux-2.6.25.20 --append=root=/dev/sda1 rootfstype=ext3 noinitrd console=ttyS0,115200 init=/etc/preinit That's a valid command line. where /vmlinux-2.6.25.20 is build_dir/linux-brcm47xx/vmlinux.elf from my build tree. kexec -l returns: kexec_load failed: Success result = 89 entry = 0x29f000 flags = 0 nr_segments = 2 segment[0].buf = 0x2ac33008 segment[0].bufsz = 27a07a segment[0].mem = 0x1000 segment[0].memsz = 29e000 segment[1].buf = 0x458440 segment[1].bufsz = 194 segment[1].mem = 0x29f000 segment[1].memsz = 1000 It seems to me like the entry is not valid here, it should be around 0x8001 or so, but I need to check whether the entry reported here is the entry point i the ELF header. and result, 89 is what is returned from kexec_load() in my_load() in the kexec-tools package. I dug a bit but could not really find anything in sys_kexec_load() or it's callees that would return 89, Anyone with any ideas at all? Anyone actually using kexec on a mips architecture with success, just so I know I am not chasing a pipe-dream? I have been using kexec successfully on rb532 w/ 2.6.24, and apart that it did mangle the serial console ouput, the kexec'd kernel booted fine, but that was prior to upgrading to kexec-tools-2.0.0. I will give it a try and report back here. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
Hi Holger, Le Tuesday 17 February 2009 18:36:40 Holger Gross, vous avez écrit : Hi, i have the same problem using kexec with buffalo whr g54s openwrt rc2 kernel 2.4: 2.4 kernel ? are you sure ? If so, you will not be able to kexec into a new kernel, this is a 2.6 specific feature. kexec_load failed: Success entry = 0x298000 flags = 0 nr_segments = 2 segment[0].buf = 0x2ac37008 segment[0].bufsz = 27307b segment[0].mem = 0x1000 segment[0].memsz = 297000 segment[1].buf = 0x456338 segment[1].bufsz = 1a4 segment[1].mem = 0x298000 segment[1].memsz = 1000 is there any solution for this? Am 07.02.2009 12:25, schrieb Florian Fainelli: Hi Brian, Le Saturday 07 February 2009 05:45:44 Brian J. Murrell, vous avez écrit : I have an asus wl500gp that I'm trying to kexec a kernel on. I had written about this before but have another bit of info and I'm hoping it rings a bell for someone so that I don't have to through the painful process of printk() instrumenting the kernel and flashing new kernels with more and more debug. Anyway, my command line is: # kexec -l /vmlinux-2.6.25.20 --append=root=/dev/sda1 rootfstype=ext3 noinitrd console=ttyS0,115200 init=/etc/preinit That's a valid command line. where /vmlinux-2.6.25.20 is build_dir/linux-brcm47xx/vmlinux.elf from my build tree. kexec -l returns: kexec_load failed: Success result = 89 entry = 0x29f000 flags = 0 nr_segments = 2 segment[0].buf = 0x2ac33008 segment[0].bufsz = 27a07a segment[0].mem = 0x1000 segment[0].memsz = 29e000 segment[1].buf = 0x458440 segment[1].bufsz = 194 segment[1].mem = 0x29f000 segment[1].memsz = 1000 It seems to me like the entry is not valid here, it should be around 0x8001 or so, but I need to check whether the entry reported here is the entry point i the ELF header. and result, 89 is what is returned from kexec_load() in my_load() in the kexec-tools package. I dug a bit but could not really find anything in sys_kexec_load() or it's callees that would return 89, Anyone with any ideas at all? Anyone actually using kexec on a mips architecture with success, just so I know I am not chasing a pipe-dream? I have been using kexec successfully on rb532 w/ 2.6.24, and apart that it did mangle the serial console ouput, the kexec'd kernel booted fine, but that was prior to upgrading to kexec-tools-2.0.0. I will give it a try and report back here. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] update mpc to 0.15 and fix compilaton
changes since v1: fix compilation the proper way Signed-off-by: Jan Willies j...@willies.info === --- sound/mpc/Makefile (Revision 14534) +++ sound/mpc/Makefile (Arbeitskopie) @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=mpc -PKG_VERSION:=0.14 +PKG_VERSION:=0.15 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=...@sf/musicpd -PKG_MD5SUM:=f4218602342cf322872a41dfe0cc72e1 +PKG_MD5SUM:=48897aeb3a7ee5c64f30e56789f105a8 include $(INCLUDE_DIR)/package.mk @@ -40,6 +40,7 @@ define Build/Compile $(call Build/Compile/Default,\ + CFLAGS=$(TARGET_CFLAGS) -std=gnu99 \ prefix=/usr \ all \ ) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] update mpc to 0.15 and fix compilaton
hey michu and list, Thanks for updating the packages.Sorry for the patch-v2-confusion, but I think you forgot to svn delete sound/mpc/patches, because 001-uclibc.patch is not needed anymore. I'm however hunting down a real nasty bug in uclibc or somewhere, which has something to do with threading behaving really weird :/ Have you noticed something with latest trunk and mpd or scmpc? On my x86 machine they don't work when sent into the background. I have to kill -32 (RTMIN) the lowest PID, after that it works. strace: http://pastebin.com/m62495427 I'm currently building a kernel with ELF_CORE and try to get a corefile for better debugging, but I really have no clue :S When started in the foreground, mpd/scmpc work just fine. cheers - jan Am Dienstag, den 17.02.2009, 19:53 +0100 schrieb Jan Willies: changes since v1: fix compilation the proper way Signed-off-by: Jan Willies j...@willies.info === --- sound/mpc/Makefile(Revision 14534) +++ sound/mpc/Makefile(Arbeitskopie) @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=mpc -PKG_VERSION:=0.14 +PKG_VERSION:=0.15 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=...@sf/musicpd -PKG_MD5SUM:=f4218602342cf322872a41dfe0cc72e1 +PKG_MD5SUM:=48897aeb3a7ee5c64f30e56789f105a8 include $(INCLUDE_DIR)/package.mk @@ -40,6 +40,7 @@ define Build/Compile $(call Build/Compile/Default,\ + CFLAGS=$(TARGET_CFLAGS) -std=gnu99 \ prefix=/usr \ all \ ) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] update mpc to 0.15 and fix compilaton
hey jan no i didn't forget, your patch didn't remove the dir ;) but i just removed it... ill test the new mpd source asap, x86 and bcm47xx. cheers On Tue, 2009-02-17 at 20:20 +0100, Jan Willies wrote: hey michu and list, Thanks for updating the packages.Sorry for the patch-v2-confusion, but I think you forgot to svn delete sound/mpc/patches, because 001-uclibc.patch is not needed anymore. I'm however hunting down a real nasty bug in uclibc or somewhere, which has something to do with threading behaving really weird :/ Have you noticed something with latest trunk and mpd or scmpc? On my x86 machine they don't work when sent into the background. I have to kill -32 (RTMIN) the lowest PID, after that it works. strace: http://pastebin.com/m62495427 I'm currently building a kernel with ELF_CORE and try to get a corefile for better debugging, but I really have no clue :S When started in the foreground, mpd/scmpc work just fine. cheers - jan Am Dienstag, den 17.02.2009, 19:53 +0100 schrieb Jan Willies: changes since v1: fix compilation the proper way Signed-off-by: Jan Willies j...@willies.info === --- sound/mpc/Makefile (Revision 14534) +++ sound/mpc/Makefile (Arbeitskopie) @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=mpc -PKG_VERSION:=0.14 +PKG_VERSION:=0.15 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=...@sf/musicpd -PKG_MD5SUM:=f4218602342cf322872a41dfe0cc72e1 +PKG_MD5SUM:=48897aeb3a7ee5c64f30e56789f105a8 include $(INCLUDE_DIR)/package.mk @@ -40,6 +40,7 @@ define Build/Compile $(call Build/Compile/Default,\ + CFLAGS=$(TARGET_CFLAGS) -std=gnu99 \ prefix=/usr \ all \ ) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] bcm47xx: Fix GPIO API return codes
On Wednesday 18 February 2009 01:29:18 Andrew Morton wrote:
On Sat, 14 Feb 2009 21:27:19 +0100
Michael Buesch m...@bu3sch.de wrote:
The GPIO API is supposed to return 0 or a negative error code,
but the SSB GPIO functions return the bitmask of the GPIO register.
Fix this by ignoring the bitmask and always returning 0. The SSB GPIO
functions can't fail.
Signed-off-by: Michael Buesch m...@bu3sch.de
---
Index: linux-2.6/arch/mips/include/asm/mach-bcm47xx/gpio.h
===
--- linux-2.6.orig/arch/mips/include/asm/mach-bcm47xx/gpio.h
2009-01-01 19:27:06.0 +0100
+++ linux-2.6/arch/mips/include/asm/mach-bcm47xx/gpio.h 2009-02-14
21:26:14.0 +0100
@@ -31,24 +31,28 @@ static inline void gpio_set_value(unsign
static inline int gpio_direction_input(unsigned gpio)
{
- return ssb_gpio_outen(ssb_bcm47xx, 1 gpio, 0);
+ ssb_gpio_outen(ssb_bcm47xx, 1 gpio, 0);
+ return 0;
}
static inline int gpio_direction_output(unsigned gpio, int value)
{
- return ssb_gpio_outen(ssb_bcm47xx, 1 gpio, 1 gpio);
+ ssb_gpio_outen(ssb_bcm47xx, 1 gpio, 1 gpio);
+ return 0;
}
-static int gpio_intmask(unsigned gpio, int value)
+static inline int gpio_intmask(unsigned gpio, int value)
{
- return ssb_gpio_intmask(ssb_bcm47xx, 1 gpio,
- value ? 1 gpio : 0);
+ ssb_gpio_intmask(ssb_bcm47xx, 1 gpio,
+value ? 1 gpio : 0);
+ return 0;
}
-static int gpio_polarity(unsigned gpio, int value)
+static inline int gpio_polarity(unsigned gpio, int value)
{
- return ssb_gpio_polarity(ssb_bcm47xx, 1 gpio,
-value ? 1 gpio : 0);
+ ssb_gpio_polarity(ssb_bcm47xx, 1 gpio,
+ value ? 1 gpio : 0);
+ return 0;
}
What are the consequences of the bug which you fixed? User-visible
runtime failures? Something else?
Please always include this information in the changelogs - without it I
cannot make which-kernel-needs-this decisions.
Well, it fixes all users of the API that don't ignore the return value.
Fixes means turns them from completely not working at all into - working
properly.
This is the case for gpio-spi, for example. gpio-spi doesn't work on bcm47xx
without
this fix. gpio-spi is in 2.6.29.
I didn't search for other API-users that might be broken.
So I'd like to see this going to Linus as soon as possible.
--
Greetings, Michael.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Only have 0 available blocks on filesystem /
On Tuesday 17 February 2009 18:22:38 Kövesdi György wrote: Hi, I have Asus wl500gp, and wanted to upgrade: /# opkg upgrade and got the following message: * Only have 0 available blocks on filesystem / ... ... the 'df' output is: Filesystem Size Used Avail Use% Mounted on rootfs 1.4M 1.4M 0 100% / /dev/root 1.4M 1.4M 0 100% /rom tmpfs 15M 840K 14M 6% /tmp tmpfs 512K 0 512K 0% /dev /dev/mtdblock3 5.7M 1.2M 4.5M 21% /jffs mini_fo:/jffs 1.4M 1.4M 0 100% / ^^^ This is your problem. /jffs contains all the stuff you have added to your FS.. so have a look in here at what's taking up all the room. It's a standard 'union' type filesystem - where you have a mounted drive which is readonly (this is often a compressed filesystem or a ROM filesystem), and you 'overlay' another mount point, which contains all the files that you modify. In this case jffs2 -which is a filesystem designed for flash memory. /dev/sda2 3.7G 1021M 2.5G 29% /mnt/usbdrive I don't really understand the filesystem structure used on OpenWrt. AFAIK, the root filesystem always shows 0 available blocks, however, e.g. 1Mb sized files can be created in directories /, /lib, /bin, etc., using the 4.5M free space from /jffs. Why opkg cannot do it? Thanx in advance K. Gy.wrt-devel //.ichael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
