From mozes at slackware.com Fri Apr 1 21:29:11 2011 From: mozes at slackware.com (Stuart Winter) Date: Fri, 1 Apr 2011 14:29:11 -0700 (PDT) Subject: [ARMedslack] Slackware ARM 13.37 rc1 is ready! Message-ID: Hi That's right! Please get testing :) I expect a few things to be broken, but I've been meaning to get the updates out for a while now. This release is now up to date (at the time of writing) with x86's -current. I'm running some other checks at the moment which may find some packages that need a rebuild, but so far everything looks good. KDE is "known broken" and Niels is fixing it ;-) If KDE isn't fixed, 13.37 will still be released because as far as I know, only one person used KDE on ARMedslack. Cheers! s. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From niels.horn at gmail.com Fri Apr 1 21:48:52 2011 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 1 Apr 2011 18:48:52 -0300 Subject: [ARMedslack] Slackware ARM 13.37 rc1 is ready! In-Reply-To: References: Message-ID: On Fri, Apr 1, 2011 at 6:29 PM, Stuart Winter wrote: > > Hi > > That's right! ?Please get testing :) > > I expect a few things to be broken, but I've been meaning to get the > updates out for a while now. > This release is now up to date (at the time of writing) with x86's > -current. > > I'm running some other checks at the moment which may find some packages > that need a rebuild, but so far everything looks good. > > KDE is "known broken" and Niels is fixing it ;-) ?If KDE isn't fixed, > 13.37 will still be released because as far as I know, only one person > used KDE on ARMedslack. > And that person isn't me ;-) I'm without most of my equipment now, so my "build-farm" has been reduced to a single SheevaPlug. And compiling larger packages is no fun this way. I'll probably get back to this only in a few weeks time, after moving to my new place. In the mean time, if anyone wants to fix KDE, feel free to have a go at it and be forever remembered by us all! Well, at least by that one person... :p > Cheers! > s. > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org -- Niels Horn From unixjohn1969 at gmail.com Fri Apr 1 21:54:36 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 1 Apr 2011 17:54:36 -0400 Subject: [ARMedslack] Slackware ARM 13.37 rc1 is ready! In-Reply-To: References: Message-ID: Stop it already ;-) you literally have me laughing my butt off. Thank you. I feel "counted" I am still poking at the issue. So slow without distcc which was discouraged in the slackbuild. ** This message has been delivered via a Google Android ** On Apr 1, 2011 5:49 PM, "Niels Horn" wrote: On Fri, Apr 1, 2011 at 6:29 PM, Stuart Winter wrote: > > Hi > > That's right! ... And that person isn't me ;-) I'm without most of my equipment now, so my "build-farm" has been reduced to a single SheevaPlug. And compiling larger packages is no fun this way. I'll probably get back to this only in a few weeks time, after moving to my new place. In the mean time, if anyone wants to fix KDE, feel free to have a go at it and be forever remembered by us all! Well, at least by that one person... :p > Cheers! > s. > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslac... -- Niels Horn _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sun Apr 3 19:06:25 2011 From: louigi600 at yahoo.it (Davide) Date: Sun, 3 Apr 2011 20:06:25 +0100 (BST) Subject: [ARMedslack] kernel for zaurus In-Reply-To: Message-ID: <210466.34932.qm@web29707.mail.ird.yahoo.com> Has anyone got a kernel for a Zaurus to try out? armedslack on a c760, c860 or c1000 ? I used to run pdaxrom on my zauri so t5hat they already have uboot just need a kernel to replace the 2.6.16 that came with last stable pdaxrom. I'd be happy to do without having to patch and compile one myself. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From gwenhael.le.moine at gmail.com Sun Apr 3 23:33:06 2011 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Mon, 4 Apr 2011 06:33:06 +0700 Subject: [ARMedslack] kernel for zaurus In-Reply-To: <210466.34932.qm@web29707.mail.ird.yahoo.com> References: <210466.34932.qm@web29707.mail.ird.yahoo.com> Message-ID: 2011/4/4 Davide > Has anyone got a kernel for a Zaurus to try out armedslack on a c760, c860 > or c1000 ? > I used to run pdaxrom on my zauri so t5hat they already have uboot just > need a kernel to replace the 2.6.16 that came with last stable pdaxrom. > > I'd be happy to do without having to patch and compile one myself. > I make my own kernel for Tosa (SL-6000), a 2.6.31.14 I think just taking the 2.6.16 of pdaxrom wouldn't work because of glibc (or something...) Maybe see if you can take a kernel from the Angstrom guys, otherwise you can compile it yourself. About ArmedSlack on Tosa I have some doc and code @ https://github.com/cycojesus/ArmedZed Gwh -------------- next part -------------- An HTML attachment was scrubbed... URL: From rw at rlworkman.net Mon Apr 4 05:03:10 2011 From: rw at rlworkman.net (Robby Workman) Date: Mon, 4 Apr 2011 00:03:10 -0500 Subject: [ARMedslack] sysctl.conf not applied?? Message-ID: <20110404000310.6f18ae64@liberty.rlwhome.lan> I asked this on IRC a few moments ago, but I suspect there are a few more sets of eyes here, soo... Does anyone else try to set various params via /etc/sysctl.conf, and if so, does it work correctly? I set lockd (nfs) ports via sysctl params, and on x86* hosts, that works as expected, but not on arm hosts. Here's my /etc/sysctl.conf contents: fs.nfs.nlm_udpport=4045 fs.nfs.nlm_tcpport=4045 It's supposed to run from rc.S, and I don't see why it wouldn't be, but... on e.g. my NFS server, lockd gets random ports assigned. If I stop nfsd and run "/sbin/sysctl -e -p /etc/sysctl.conf" (which is exactly what rc.S does) and then restart rc.nfsd, lockd gets assigned to port 4045 as desired. Another set of eyes looking at that would be appreciated. -RW From rw at rlworkman.net Mon Apr 4 05:31:46 2011 From: rw at rlworkman.net (Robby Workman) Date: Mon, 4 Apr 2011 00:31:46 -0500 Subject: [ARMedslack] sysctl.conf not applied?? In-Reply-To: <20110404000310.6f18ae64@liberty.rlwhome.lan> References: <20110404000310.6f18ae64@liberty.rlwhome.lan> Message-ID: <20110404003146.7bea2587@liberty.rlwhome.lan> On Mon, 4 Apr 2011 00:03:10 -0500 Robby Workman wrote: > I asked this on IRC a few moments ago, but I suspect there are > a few more sets of eyes here, soo... > > Does anyone else try to set various params via /etc/sysctl.conf, > and if so, does it work correctly? I set lockd (nfs) ports via > sysctl params, and on x86* hosts, that works as expected, but > not on arm hosts. Here's my /etc/sysctl.conf contents: > fs.nfs.nlm_udpport=4045 > fs.nfs.nlm_tcpport=4045 > > It's supposed to run from rc.S, and I don't see why it wouldn't > be, but... on e.g. my NFS server, lockd gets random ports assigned. > If I stop nfsd and run "/sbin/sysctl -e -p /etc/sysctl.conf" (which > is exactly what rc.S does) and then restart rc.nfsd, lockd gets > assigned to port 4045 as desired. > > Another set of eyes looking at that would be appreciated. After more discussion on IRC, I *think* this might be a peculiarity of having / on nand. On my SheevaPlug, which has / on an MMC card, this works as expected without any manual intervention (IOW, lockd gets assigned to port 4045). On my Netgear Stora (the NFS server) and my GuruPlug, / is ubifs on /dev/mtd2, and both of them show the problem behavior. I don't know if that's related at all, but it's something to explore. However, I must go to bed now, and I'll not be able to do anything with this tomorrow, but at least I have an idea to pursue now... -RW From louigi600 at yahoo.it Mon Apr 4 07:23:56 2011 From: louigi600 at yahoo.it (Davide) Date: Mon, 4 Apr 2011 08:23:56 +0100 (BST) Subject: [ARMedslack] R: sysctl.conf not applied?? In-Reply-To: <20110404000310.6f18ae64@liberty.rlwhome.lan> Message-ID: <670868.19056.qm@web29707.mail.ird.yahoo.com> The firs thing that comes into my mins is that at the time rc.S loads your sysctl maybe not all the nfs modules have been bulled up. Make sure rc.modules has all the modules you need for your nfs server and add "/sbin/sysctl -e -p /etc/sysctl.conf" somewhere just after running rc.modules but before starting nfs. Regards David --- Lun 4/4/11, Robby Workman ha scritto: > Da: Robby Workman > Oggetto: [ARMedslack] sysctl.conf not applied?? > A: "Slackware ARM port" > Data: Luned? 4 Aprile 2011, 07:03 > I asked this on IRC a few moments > ago, but I suspect there are > a few more sets of eyes here, soo... > > Does anyone else try to set various params via > /etc/sysctl.conf, > and if so, does it work correctly?? I set lockd (nfs) > ports via > sysctl params, and on x86* hosts, that works as expected, > but > not on arm hosts.? Here's my /etc/sysctl.conf > contents: > ? fs.nfs.nlm_udpport=4045 > ? fs.nfs.nlm_tcpport=4045 > > It's supposed to run from rc.S, and I don't see why it > wouldn't > be, but... on e.g. my NFS server, lockd gets random ports > assigned. > If I stop nfsd and run "/sbin/sysctl -e -p > /etc/sysctl.conf" (which > is exactly what rc.S does) and then restart rc.nfsd, lockd > gets > assigned to port 4045 as desired. > > Another set of eyes looking at that would be appreciated. > > -RW > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From louigi600 at yahoo.it Tue Apr 5 07:00:50 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 5 Apr 2011 08:00:50 +0100 (BST) Subject: [ARMedslack] R: R: sysctl.conf not applied?? In-Reply-To: <670868.19056.qm@web29707.mail.ird.yahoo.com> Message-ID: <864552.35351.qm@web29720.mail.ird.yahoo.com> In support to what I supposed I had a look at my dockstar running current but no nfs services active: root at slackware:~# sysctl -a | grep nfs error: permission denied on key 'net.ipv4.route.flush' error: permission denied on key 'net.ipv6.route.flush' root at slackware:~# The two keys you mention do not yet exist until the nfsd module is loaded: root at slackware:/etc/rc.d# modprobe nfsd root at slackware:/etc/rc.d# sysctl -a | grep nfs fs.nfs.nlm_grace_period = 0 fs.nfs.nlm_timeout = 10 fs.nfs.nlm_udpport = 0 fs.nfs.nlm_tcpport = 0 fs.nfs.nsm_use_hostnames = 0 fs.nfs.nsm_local_state = 0 error: permission denied on key 'net.ipv4.route.flush' error: permission denied on key 'net.ipv6.route.flush' sunrpc.nfs_debug = 0 sunrpc.nfsd_debug = 0 root at slackware:/etc/rc.d# You can fix this by adding the sysctl -p.... just after loading nfsd module in rc.nfsd or just like I said by loading the module in rc.modules and making sure that sysctl.conf is reloaded after rc.modules. --- Lun 4/4/11, Davide ha scritto: > Da: Davide > Oggetto: [ARMedslack] R: sysctl.conf not applied?? > A: "Slackware ARM port" > Data: Luned? 4 Aprile 2011, 09:23 > The firs thing that comes into my > mins is that at the time rc.S loads your sysctl maybe not > all the nfs modules have been bulled up. > Make sure rc.modules has all the modules you need for your > nfs server and > add "/sbin/sysctl -e -p /etc/sysctl.conf" somewhere just > after running rc.modules but before starting nfs. > > Regards > David > > > > --- Lun 4/4/11, Robby Workman > ha scritto: > > > Da: Robby Workman > > Oggetto: [ARMedslack] sysctl.conf not applied?? > > A: "Slackware ARM port" > > Data: Luned? 4 Aprile 2011, 07:03 > > I asked this on IRC a few moments > > ago, but I suspect there are > > a few more sets of eyes here, soo... > > > > Does anyone else try to set various params via > > /etc/sysctl.conf, > > and if so, does it work correctly?? I set lockd > (nfs) > > ports via > > sysctl params, and on x86* hosts, that works as > expected, > > but > > not on arm hosts.? Here's my /etc/sysctl.conf > > contents: > > ? fs.nfs.nlm_udpport=4045 > > ? fs.nfs.nlm_tcpport=4045 > > > > It's supposed to run from rc.S, and I don't see why > it > > wouldn't > > be, but... on e.g. my NFS server, lockd gets random > ports > > assigned. > > If I stop nfsd and run "/sbin/sysctl -e -p > > /etc/sysctl.conf" (which > > is exactly what rc.S does) and then restart rc.nfsd, > lockd > > gets > > assigned to port 4045 as desired. > > > > Another set of eyes looking at that would be > appreciated. > > > > -RW > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From rw at rlworkman.net Wed Apr 6 04:05:09 2011 From: rw at rlworkman.net (Robby Workman) Date: Tue, 5 Apr 2011 23:05:09 -0500 Subject: [ARMedslack] R: R: sysctl.conf not applied?? In-Reply-To: <864552.35351.qm@web29720.mail.ird.yahoo.com> References: <670868.19056.qm@web29707.mail.ird.yahoo.com> <864552.35351.qm@web29720.mail.ird.yahoo.com> Message-ID: <20110405230509.0d93fde1@liberty.rlwhome.lan> On Tue, 5 Apr 2011 08:00:50 +0100 (BST) Davide wrote: > In support to what I supposed I had a look at my dockstar running > current but no nfs services active: root at slackware:~# sysctl -a | > grep nfs error: permission denied on key 'net.ipv4.route.flush' > error: permission denied on key 'net.ipv6.route.flush' > root at slackware:~# > > The two keys you mention do not yet exist until the nfsd module is > loaded: root at slackware:/etc/rc.d# modprobe nfsd > root at slackware:/etc/rc.d# sysctl -a | grep nfs > fs.nfs.nlm_grace_period = 0 > fs.nfs.nlm_timeout = 10 > fs.nfs.nlm_udpport = 0 > fs.nfs.nlm_tcpport = 0 > fs.nfs.nsm_use_hostnames = 0 > fs.nfs.nsm_local_state = 0 > error: permission denied on key 'net.ipv4.route.flush' > error: permission denied on key 'net.ipv6.route.flush' > sunrpc.nfs_debug = 0 > sunrpc.nfsd_debug = 0 > root at slackware:/etc/rc.d# > > You can fix this by adding the sysctl -p.... just after loading nfsd > module in rc.nfsd or just like I said by loading the module in > rc.modules and making sure that sysctl.conf is reloaded after > rc.modules. Yep, that's definitely it - just confirmed. Weird though, as it doesn't seem to make a difference unless / is on nand. Oh well, problem solved - good enough for me. Thanks!! :-) -RW From thenktor at gmx.de Wed Apr 6 18:31:45 2011 From: thenktor at gmx.de (Thorsten M.) Date: Wed, 6 Apr 2011 20:31:45 +0200 Subject: [ARMedslack] Audio devices not available after boot on current Message-ID: <20110406203145.6862b713@darkstar.example.net> Hi, an USB soundcard is connected to my Dockstar: us 001 Device 005: ID 08bb:2702 Texas Instruments Japan Speakers Alsa modules are loaded: snd_usb_audio 69452 0 snd_pcm 61029 2 snd_pcm_oss,snd_usb_audio snd_timer 18347 1 snd_pcm snd_page_alloc 4615 1 snd_pcm snd_hwdep 5129 1 snd_usb_audio snd_usbmidi_lib 15814 1 snd_usb_audio snd_rawmidi 16260 1 snd_usbmidi_lib snd 42908 7 snd_pcm_oss,snd_usb_audio,snd_pcm,snd_timer,snd_hwdep,snd_usbmidi_lib,snd_rawmidi soundcore 5443 1 snd But /dev/snd/ is not available after boot: thorsten at dreamtheater:~$ alsamixer cannot open mixer: No such file or directory After unplugging/plugging the sound card everything works fine. Did anyone else notice this or have any ideas? -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Thu Apr 7 05:56:03 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 7 Apr 2011 06:56:03 +0100 (BST) Subject: [ARMedslack] R: Audio devices not available after boot on current In-Reply-To: <20110406203145.6862b713@darkstar.example.net> Message-ID: <776860.70063.qm@web29715.mail.ird.yahoo.com> This is just a guess and unlike the nfs issue I've no way to test it out but here is my idea: The soune modules are pulled in by rc.modules before the usb device is recognised and hence are just loaded bud do nothing. When the usb sound device gets recognised the modules are already loaded and nothing else is done. I'd check out that the sound modules are not in rc.modules and just let udev do it's magic when nthe device is recognised. Regards David --- Mer 6/4/11, Thorsten M. ha scritto: > Da: Thorsten M. > Oggetto: [ARMedslack] Audio devices not available after boot on current > A: "Slackware ARM port" > Data: Mercoled? 6 Aprile 2011, 20:31 > Hi, > an USB soundcard is connected to my Dockstar: > us 001 Device 005: ID 08bb:2702 Texas Instruments Japan > Speakers > > Alsa modules are loaded: > snd_usb_audio? ? ? ? ? 69452? > 0 > snd_pcm? ? ? ? ? ? ? > ? 61029? 2 snd_pcm_oss,snd_usb_audio > snd_timer? ? ? ? ? ? ? > 18347? 1 snd_pcm > snd_page_alloc? ? ? ? ? 4615? > 1 snd_pcm > snd_hwdep? ? ? ? ? ? > ???5129? 1 snd_usb_audio > snd_usbmidi_lib? ? ? ? 15814? 1 > snd_usb_audio > snd_rawmidi? ? ? ? ? ? > 16260? 1 snd_usbmidi_lib > snd? ? ? ? ? ? ? ? > ? ? 42908? 7 > snd_pcm_oss,snd_usb_audio,snd_pcm,snd_timer,snd_hwdep,snd_usbmidi_lib,snd_rawmidi > soundcore? ? ? ? ? ? > ???5443? 1 snd > > But /dev/snd/ is not available after boot: > thorsten at dreamtheater:~$ alsamixer > cannot open mixer: No such file or directory > > After unplugging/plugging the sound card everything works > fine. > Did anyone else notice this or have any ideas? > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Thu Apr 7 07:30:10 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 7 Apr 2011 09:30:10 +0200 Subject: [ARMedslack] gdb python error Message-ID: <201104070930.10576.thenktor@gmx.de> gdb shows this error on arm current: (gdb) run Starting program: /usr/bin/mpd -h [Thread debugging using libthread_db enabled] Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-gdb.py", line 9, in from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in import gdb.backtrace ImportError: No module named backtrace It works on x86_64 current. So either I'm missing a dep (but cannot find the right one yet) or some other problem. Maybe different gdb configure options? -- Thorsten M?hlfelder Salix OS: www.salixos.org From thenktor at gmx.de Thu Apr 7 09:49:23 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 7 Apr 2011 11:49:23 +0200 Subject: [ARMedslack] gdb python error In-Reply-To: <201104070930.10576.thenktor@gmx.de> References: <201104070930.10576.thenktor@gmx.de> Message-ID: <201104071149.23952.thenktor@gmx.de> Am Thursday 07 April 2011 09:30:10 schrieb Thorsten M?hlfelder: > gdb shows this error on arm current: > > (gdb) run > Starting program: /usr/bin/mpd -h > [Thread debugging using libthread_db enabled] > Traceback (most recent call last): > File > "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-gdb.py", line > 9, in > from gobject import register > File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in > import gdb.backtrace > ImportError: No module named backtrace > > It works on x86_64 current. So either I'm missing a dep (but cannot find > the right one yet) or some other problem. Maybe different gdb configure > options? I have to correct myself: the x86_64 version shows the same error. On both arch it only comes up if the debugged program exits abnormally. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Thu Apr 7 12:04:12 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 7 Apr 2011 13:04:12 +0100 (BST) Subject: [ARMedslack] R: gdb python error In-Reply-To: <201104070930.10576.thenktor@gmx.de> Message-ID: <445935.57272.qm@web29717.mail.ird.yahoo.com> It looks like you're missing a Python module. Regards David --- Gio 7/4/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: [ARMedslack] gdb python error > A: armedslack at lists.armedslack.org > Data: Gioved? 7 Aprile 2011, 09:30 > gdb shows this error on arm current: > > (gdb) run > Starting program: /usr/bin/mpd -h > [Thread debugging using libthread_db enabled] > Traceback (most recent call last): > ? File > "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-gdb.py", > > line 9, in > ? ? from gobject import register > ? File "/usr/share/glib-2.0/gdb/gobject.py", line 3, > in > ? ? import gdb.backtrace > ImportError: No module named backtrace > > It works on x86_64 current. So either I'm missing a dep > (but cannot find the > right one yet) or some other problem. Maybe different gdb > configure options? > > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From m-lists at biscuit.org.uk Thu Apr 7 12:08:34 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 7 Apr 2011 13:08:34 +0100 (BST) Subject: [ARMedslack] R: gdb python error In-Reply-To: <445935.57272.qm@web29717.mail.ird.yahoo.com> References: <445935.57272.qm@web29717.mail.ird.yahoo.com> Message-ID: I didn't even know gdb used python! gdb probably just needs a rebuild. On Thu, 7 Apr 2011, Davide wrote: > It looks like you're missing a Python module. > > Regards > David > > --- Gio 7/4/11, Thorsten M?hlfelder ha scritto: > > > Da: Thorsten M?hlfelder > > Oggetto: [ARMedslack] gdb python error > > A: armedslack at lists.armedslack.org > > Data: Gioved? 7 Aprile 2011, 09:30 > > gdb shows this error on arm current: > > > > (gdb) run > > Starting program: /usr/bin/mpd -h > > [Thread debugging using libthread_db enabled] > > Traceback (most recent call last): > > ? File > > "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-gdb.py", > > > > line 9, in > > ? ? from gobject import register > > ? File "/usr/share/glib-2.0/gdb/gobject.py", line 3, > > in > > ? ? import gdb.backtrace > > ImportError: No module named backtrace > > > > It works on x86_64 current. So either I'm missing a dep > > (but cannot find the > > right one yet) or some other problem. Maybe different gdb > > configure options? > > > > > > -- > > Thorsten M?hlfelder > > Salix OS: www.salixos.org > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Thu Apr 7 12:12:34 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 7 Apr 2011 13:12:34 +0100 (BST) Subject: [ARMedslack] R: gdb python error In-Reply-To: References: <445935.57272.qm@web29717.mail.ird.yahoo.com> Message-ID: ah. It didn't used to use python but gdb does indeed link with it now. Can you email Pat about it? if it does just need a rebuild then we'd better do it prior to 13.37 being released. I'll let him have a heads up to look out for the mail. On Thu, 7 Apr 2011, Stuart Winter wrote: > > I didn't even know gdb used python! > gdb probably just needs a rebuild. > > > On Thu, 7 Apr 2011, Davide wrote: > > > It looks like you're missing a Python module. > > > > Regards > > David > > > > --- Gio 7/4/11, Thorsten M?hlfelder ha scritto: > > > > > Da: Thorsten M?hlfelder > > > Oggetto: [ARMedslack] gdb python error > > > A: armedslack at lists.armedslack.org > > > Data: Gioved? 7 Aprile 2011, 09:30 > > > gdb shows this error on arm current: > > > > > > (gdb) run > > > Starting program: /usr/bin/mpd -h > > > [Thread debugging using libthread_db enabled] > > > Traceback (most recent call last): > > > ? File > > > "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-gdb.py", > > > > > > line 9, in > > > ? ? from gobject import register > > > ? File "/usr/share/glib-2.0/gdb/gobject.py", line 3, > > > in > > > ? ? import gdb.backtrace > > > ImportError: No module named backtrace > > > > > > It works on x86_64 current. So either I'm missing a dep > > > (but cannot find the > > > right one yet) or some other problem. Maybe different gdb > > > configure options? > > > > > > > > > -- > > > Thorsten M?hlfelder > > > Salix OS: www.salixos.org > > > _______________________________________________ > > > ARMedslack mailing list > > > ARMedslack at lists.armedslack.org > > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Thu Apr 7 15:46:06 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 7 Apr 2011 17:46:06 +0200 Subject: [ARMedslack] Kernel kirkwood-2.6.38.2: CONFIG_N_HDLC Message-ID: <201104071746.06306.thenktor@gmx.de> Hi, is there any special reason why CONFIG_N_HDLC is disabled? In x86 it's build as a module. The only reason I'm asking is because the rp-pppoe documentation says: "Synchronous PPP is safe on Linux machines with the n_hdlc line discipline. (If you have a file called "n_hdlc.o" in your modules directory, you have the line discipline.)" It also says that synchronous mode "is much easier on CPU usage" than asynchronous mode. So I've thought it's worth a try. Location: -> Device Drivers -> Character devices -> Non-standard serial port support (SERIAL_NONSTANDARD [=y]) -- Thorsten M?hlfelder Salix OS: www.salixos.org From m-lists at biscuit.org.uk Thu Apr 7 18:39:16 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 7 Apr 2011 19:39:16 +0100 (BST) Subject: [ARMedslack] Kernel kirkwood-2.6.38.2: CONFIG_N_HDLC In-Reply-To: <201104071746.06306.thenktor@gmx.de> References: <201104071746.06306.thenktor@gmx.de> Message-ID: > is there any special reason why CONFIG_N_HDLC is disabled? No. >In x86 it's build as a module. The x86 configs don't have any bearing on ARM, apart from in cases where it alters the behaviour of something in user space, as you've identified. I'll add the kernel option before the 13.37 release - either as a kernel rebuild, or a kernel update - which ever comes first. From thenktor at gmx.de Sat Apr 9 13:33:08 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Sat, 9 Apr 2011 15:33:08 +0200 Subject: [ARMedslack] Kernel kirkwood-2.6.38.2: CONFIG_N_HDLC In-Reply-To: References: <201104071746.06306.thenktor@gmx.de> Message-ID: <20110409153308.32c8d98f@pinkfloyd.tm-net> Am Thu, 7 Apr 2011 19:39:16 +0100 (BST) schrieb Stuart Winter : > I'll add the kernel option before the 13.37 release - either as a > kernel rebuild, or a kernel update - which ever comes first. Thanks! Just noticed: pppoe uses about 11 % CPU with downstram fully loaded (16 MBit/s). -- Thorsten M?hlfelder Salix OS: www.salixos.org From m-lists at biscuit.org.uk Wed Apr 13 17:16:29 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 13 Apr 2011 18:16:29 +0100 (BST) Subject: [ARMedslack] Kernel kirkwood-2.6.38.2: CONFIG_N_HDLC In-Reply-To: <20110409153308.32c8d98f@pinkfloyd.tm-net> References: <201104071746.06306.thenktor@gmx.de> <20110409153308.32c8d98f@pinkfloyd.tm-net> Message-ID: > > I'll add the kernel option before the 13.37 release - either as a > > kernel rebuild, or a kernel update - which ever comes first. > > Thanks! > Just noticed: pppoe uses about 11 % CPU with downstram fully loaded (16 > MBit/s). I've compiled this and all of the other nonstandard serial thingies as modules (although some of them really aren't necessary since some of them are for terminal servers, but I'm not too fussed about the modules as long as having them doesn't break anything!). -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Thu Apr 14 13:23:01 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 14 Apr 2011 14:23:01 +0100 (BST) Subject: [ARMedslack] Some things I worked on that could be handy Message-ID: <544618.87580.qm@web29718.mail.ird.yahoo.com> Look at the README.txt that comes with my work for hints on configuring the featutes. Since no attachments are possible on this list all files are avalible on rapidshare (password for zip file is armedslack!): https://rapidshare.com/files/457383233/features.zip I've included the leds script in the 3G.tgz because some of my scripts use it to show that something is happening. Activating 3G internet connection upon usb 3G dongle plugin. This allows you to preconfigure all your 3G connections so that when you plug in a 3G modem dongle the correct ppp connection is initiated. I've an example of an on demand connection ti "wind Italy" operater setup. You may like to look at the README.txt and in /etc/ppp/peers/22288 for more info on this. This will work only if your 3G modem dongle is supported under linux and has the correct modeswitch stuff in place. Activating wifi dongles upon wifi dongle plugin {even in AP (Master) mode}. Here not much was changed for the normal wifi clinet setup (just worked around a problem) but the Master mode was added from scratch. I'll include in the tarball hostapd which is not packaged in slackware (but since I do niot have the sources with me right now I might forget something). Things have been taught in a way that will let you have different AP setups each bound to a specific hardware (mac address in the discriminator). You might like to see the README.txt for more details and the example setup in /etc/hostapd/wlan0* and dsnmasq.conf Automounting usb drives. This only works for normal partitions not lvm'd and only for filesystems that get auto recognized by kernel (ext? and dos/vfat work fine, I've tested personally). Things will be mounted somewhere in /media depending on vendor and partition. Regards David From louigi600 at yahoo.it Tue Apr 19 10:42:02 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 11:42:02 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: Message-ID: <589074.69059.qm@web29703.mail.ird.yahoo.com> This probably happens to all uboot versions but I've not had time to check. It's not strictly armedslack but the community might want to know anyway .... and someone might like to answer privately the question (avoiding filth in the list). I just setuo Jeff's uboot on my dockstar and it boots ok both from yhe onboard flash and from a usb flash drive. I setup a 2.5" usb HDU with a development environment, so that I could benefit from the better performing HDU to do some compiling, exactly like the usb flash drive. When I try to boot from it the uboot "usb start" actually turns off the usb HDU while scanning. The usb hdu I'm using has been tested to work properly with just the 500mA from a single usb port bothe from PC or from dockstar once Linux is up and running. Is there something I need to do in order to boot from a usb HDU that differs from booting from a usb flash drive ? Regards David From thenktor at gmx.de Tue Apr 19 10:48:58 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Tue, 19 Apr 2011 12:48:58 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <589074.69059.qm@web29703.mail.ird.yahoo.com> References: <589074.69059.qm@web29703.mail.ird.yahoo.com> Message-ID: <201104191248.58306.thenktor@gmx.de> Am Tuesday 19 April 2011 12:42:02 schrieb Davide: > Is there something I need to do in order to boot from a usb HDU that > differs from booting from a usb flash drive ? My Dockstar boots fine with Doozan's u-boot and the original Seagate Freeagent Go HD. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Tue Apr 19 12:14:17 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 13:14:17 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104191248.58306.thenktor@gmx.de> Message-ID: <626504.93789.qm@web29707.mail.ird.yahoo.com> Well yeah .... I've an update on this: I did nothing but change the usb port from closest to RJ45 to the one nets to the closest to RJ45. This time it boots. I'll investigate further on this ... This is on a brand new dockstar (I've now 2 of these things) but the seem to have small hardware differences ... read on Also Another thing I noticed: the led stopped working and things do not look rigth in /sys root at slackware:~# ls /sys/class/leds/ plug:green:health@ root at slackware:~# Where's the orange led gone ? and why os the green one not light up? root at slackware:~# cat /sys/class/leds/plug\:green\:health/trigger none nand-disk timer [default-on] mmc0 root at slackware:~# Regards David --- Mar 19/4/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > A: "Slackware ARM port" > Data: Marted? 19 Aprile 2011, 12:48 > Am Tuesday 19 April 2011 12:42:02 > schrieb Davide: > > Is there something I need to do in order to boot from > a usb HDU that > > differs from booting from a usb flash drive ? > > My Dockstar boots fine with Doozan's u-boot and the > original Seagate Freeagent > Go HD. > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Tue Apr 19 12:40:30 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Tue, 19 Apr 2011 14:40:30 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <626504.93789.qm@web29707.mail.ird.yahoo.com> References: <626504.93789.qm@web29707.mail.ird.yahoo.com> Message-ID: <201104191440.30637.thenktor@gmx.de> Am Tuesday 19 April 2011 14:14:17 schrieb Davide: > Well yeah .... I've an update on this: > I did nothing but change the usb port from closest to RJ45 to the one nets > to the closest to RJ45. This time it boots. > > I'll investigate further on this ... AFAIK the dockstar has native USB ports and some ports provided by an additional hub. Maybe this makes a difference. > This is on a brand new dockstar (I've now 2 of these things) but the seem > to have small hardware differences ... read on > > Also Another thing I noticed: the led stopped working and things do not > look rigth in /sys Do cat /proc/cpuinfo. Do you have "Hardware: Seagate FreeAgent DockStar"? If not the "arcNumber" that gives u-boot to the kernel is wrong. IIRC arcNumber 2998 is the right one for the Dockstar. 2097 is Sheevaplug. Please search for it in Doozans forum. The arcNumber sets some board specific details like LED setup. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Tue Apr 19 12:44:46 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 13:44:46 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <626504.93789.qm@web29707.mail.ird.yahoo.com> Message-ID: <541933.41539.qm@web29717.mail.ird.yahoo.com> Hum well the reboot after it worked failed again on all dockstar usb ports. No the only thing I recall different from when it worked is that I rebooted from Linux running on usb flashdrive with the lace usb HDU plugged in and modules loaded. The only explanation I've for that is that the lace USB HDU (more specifically the usb 2 sata adapter that is in the casing) requires firmware or something like that that uboot cannot handle. I tested a different usb HDU and it works ok ... it seems an issue with some specific models and not something that afflicts all usb HDUs. Concerning the leds ... while jeff's uboot is running the green led is flashing so the led is still working .... but there mist be something that goes wrong when 2.6.38-rc2 is loaded that does not happen on the other dockstar. Not sure if it;s something to do with jeff's uboot setup or with my brand new dockstar. If I notice any other odd stuff I'll update on this. Regards David --- Mar 19/4/11, Davide ha scritto: > Da: Davide > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > A: "Slackware ARM port" > Data: Marted? 19 Aprile 2011, 14:14 > Well yeah .... I've an update on > this: > I did nothing but change the usb port from closest to RJ45 > to the one nets to the closest to RJ45. > This time it boots. > > I'll investigate further on this ... > > This is on a brand new dockstar (I've now 2 of these > things) but the seem to have small hardware differences ... > read on > > Also Another thing I noticed: the led stopped working and > things do not look rigth in /sys > > root at slackware:~# ls /sys/class/leds/ > plug:green:health@ > root at slackware:~# > > Where's the orange led gone ? > and why os the green one not light up? > > root at slackware:~# cat > /sys/class/leds/plug\:green\:health/trigger > none nand-disk timer [default-on] mmc0 > root at slackware:~# > > Regards > David > > --- Mar 19/4/11, Thorsten M?hlfelder > ha scritto: > > > Da: Thorsten M?hlfelder > > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > > A: "Slackware ARM port" > > Data: Marted? 19 Aprile 2011, 12:48 > > Am Tuesday 19 April 2011 12:42:02 > > schrieb Davide: > > > Is there something I need to do in order to boot > from > > a usb HDU that > > > differs from booting from a usb flash drive ? > > > > My Dockstar boots fine with Doozan's u-boot and the > > original Seagate Freeagent > > Go HD. > > > > -- > > Thorsten M?hlfelder > > Salix OS: www.salixos.org > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Tue Apr 19 12:52:51 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Tue, 19 Apr 2011 14:52:51 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <589074.69059.qm@web29703.mail.ird.yahoo.com> References: <589074.69059.qm@web29703.mail.ird.yahoo.com> Message-ID: <201104191452.51534.thenktor@gmx.de> Another thing: Please don't use the "reply" button to start a new thread. Use "new mail" and add the ML address. Otherwise the thread view in mail clients is wrong. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Tue Apr 19 13:06:23 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 14:06:23 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104191440.30637.thenktor@gmx.de> Message-ID: <193808.35698.qm@web29718.mail.ird.yahoo.com> > > Well yeah .... I've an update on this: > > I did nothing but change the usb port from closest to > RJ45 to the one nets > > to the closest to RJ45. This time it boots. > > > > I'll investigate further on this ... > > AFAIK the dockstar has native USB ports and some ports > provided by an > additional hub. Maybe this makes a difference. As far as I know kirkwood has 1 usb port that is connected to an onboard 4 port hub ... so all external usb ports should be exactly the same. Anyway I've tracked the problem to be specific to the usb2sata adapter inside my lace usb HDU ... see an earlier mail I just sent. > > > This is on a brand new dockstar (I've now 2 of these > things) but the seem > > to have small hardware differences ... read on > > > > Also Another thing I noticed: the led stopped working > and things do not > > look rigth in /sys > > Do cat /proc/cpuinfo. Do you have "Hardware: Seagate > FreeAgent DockStar"? If > not the "arcNumber" that gives u-boot to the kernel is > wrong. IIRC arcNumber > 2998 is the right one for the Dockstar. 2097 is Sheevaplug. > Please search for > it in Doozans forum. > The arcNumber sets some board specific details like LED > setup. this is what my cpuinfo says on my new dockstar: Processor : ARM926EJ-S rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Cache type : write-back Cache clean : cp15 c7 ops Cache lockdown : format C Cache format : Harvard I size : 16384 I assoc : 4 I line length : 32 I sets : 128 D size : 16384 D assoc : 4 D line length : 32 D sets : 128 Hardware : Feroceon-KW Revision : 0000 Serial : 0000000000000000 But a swear I took this board out of a brand new dockstar case .... package sealed .... etc ... etc > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From louigi600 at yahoo.it Tue Apr 19 13:18:26 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 14:18:26 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104191440.30637.thenktor@gmx.de> Message-ID: <666656.59512.qm@web29711.mail.ird.yahoo.com> The last cpuinfo i sent was produced by pogoplug system ... from slackware it looks different but still is not what one would expect from a dockstar: root at slackware:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell SheevaPlug Reference Board Revision : 0000 Serial : 0000000000000000 root at slackware:~# The board actually looks the same as my other dockstar ... I guess it's just a different SOC that make sthe difference. Regards David From thenktor at gmx.de Tue Apr 19 13:32:59 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Tue, 19 Apr 2011 15:32:59 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <666656.59512.qm@web29711.mail.ird.yahoo.com> References: <666656.59512.qm@web29711.mail.ird.yahoo.com> Message-ID: <201104191533.00057.thenktor@gmx.de> Am Tuesday 19 April 2011 15:18:26 schrieb Davide: > The last cpuinfo i sent was produced by pogoplug system ... from slackware > it looks different but still is not what one would expect from a dockstar: > root at slackware:~# cat /proc/cpuinfo > Processor : Feroceon 88FR131 rev 1 (v5l) > BogoMIPS : 1192.75 > Features : swp half thumb fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant : 0x2 > CPU part : 0x131 > CPU revision : 1 > > Hardware : Marvell SheevaPlug Reference Board > Revision : 0000 > Serial : 0000000000000000 > root at slackware:~# > > The board actually looks the same as my other dockstar ... I guess it's > just a different SOC that make sthe difference. As I've said: you are using a wrong "arcNumber". Doozan's u-boot is patched so that the arcNumber can be set as u-boot environment variable. Basically arcNumber is just some term used by Doozan. In the Linux kernel it is called machine type. Have a look at /usr/src/linux/include/generated/mach-types.h for a complete list. There you'll find: #define MACH_TYPE_DOCKSTAR 2998 #define MACH_TYPE_SHEEVAPLUG 2097 If you want your kernel to recognize the dockstar you have to use 2998 as arcNumber in u-boot. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Tue Apr 19 14:25:00 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 15:25:00 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104191533.00057.thenktor@gmx.de> Message-ID: <393604.3123.qm@web29720.mail.ird.yahoo.com> --- Mar 19/4/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > A: "Slackware ARM port" > Data: Marted? 19 Aprile 2011, 15:32 > Am Tuesday 19 April 2011 15:18:26 > schrieb Davide: > > The last cpuinfo i sent was produced by pogoplug > system ... from slackware > > it looks different but still is not what one would > expect from a dockstar: > > root at slackware:~# cat /proc/cpuinfo > > Processor? ? ???: Feroceon > 88FR131 rev 1 (v5l) > > BogoMIPS? ? ? ? : 1192.75 > > Features? ? ? ? : swp half thumb > fastmult edsp > > CPU implementer : 0x56 > > CPU architecture: 5TE > > CPU variant? ???: 0x2 > > CPU part? ? ? ? : 0x131 > > CPU revision? ? : 1 > > > > Hardware? ? ? ? : Marvell > SheevaPlug Reference Board > > Revision? ? ? ? : 0000 > > Serial? ? ? ? ? : > 0000000000000000 > > root at slackware:~# > > > > The board actually looks the same as my other dockstar > ... I guess it's > > just a different SOC that make sthe difference. > > As I've said: you are using a wrong "arcNumber". Doozan's > u-boot is patched so > that the arcNumber can be set as u-boot environment > variable. > Basically arcNumber is just some term used by Doozan. In > the Linux kernel it > is called machine type. Have a look > at /usr/src/linux/include/generated/mach-types.h for a > complete list. There > you'll find: > #define MACH_TYPE_DOCKSTAR? ? ? ? > ? ???2998 > #define MACH_TYPE_SHEEVAPLUG? ? ? > ???2097 > If you want your kernel to recognize the dockstar you have > to use 2998 as > arcNumber in u-boot. > Did not understand you the first time .... but not much changes: I've done a saveenv avter having set setenv arcNumber 2998 and these are the other things I'm fiddling with to boot for my setup: setenv arcNumber 2998 ; setenv usb_root /dev/sda3 ; setenv usb_rootfstype ext3 ; usb start setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype ext2load usb 0:1 0x800000 uImage ; ext2load usb 0:1 0x1100000 uinitrd ; bootm 0x800000 0x1100000 But none the less once I'm up the green led stops flashing and cpuinfo still tells me that it's not a dockstar: root at slackware:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell SheevaPlug Reference Board Revision : 0000 Serial : 0000000000000000 root at slackware:~# I did check beforr booting that teh environment variable was set Marvell>> echo $arcNumber 2998 Marvell>> and also under pogoplud environment the led works and also cpuinfo still says that it's not a dockstar. Are the new dockstars using sheeva's SOC ? Regards David From louigi600 at yahoo.it Tue Apr 19 14:40:32 2011 From: louigi600 at yahoo.it (Davide) Date: Tue, 19 Apr 2011 15:40:32 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <393604.3123.qm@web29720.mail.ird.yahoo.com> Message-ID: <455389.74273.qm@web29719.mail.ird.yahoo.com> Oooops .... need to do a hardware reset o reboot for uboot to do the magic. Just setting the variable, saving it permanently and booting is not enough. Perhaps uboot uses that variable to do some initialization before you get the prompt. Sorry for making so much noise. Regards David --- Mar 19/4/11, Davide ha scritto: > Da: Davide > Oggetto: [ARMedslack] jeff Doozan's uboot > A: "Slackware ARM port" > Data: Marted? 19 Aprile 2011, 16:25 > > > --- Mar 19/4/11, Thorsten M?hlfelder > ha scritto: > > > Da: Thorsten M?hlfelder > > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > > A: "Slackware ARM port" > > Data: Marted? 19 Aprile 2011, 15:32 > > Am Tuesday 19 April 2011 15:18:26 > > schrieb Davide: > > > The last cpuinfo i sent was produced by pogoplug > > system ... from slackware > > > it looks different but still is not what one > would > > expect from a dockstar: > > > root at slackware:~# cat /proc/cpuinfo > > > Processor? ? ???: Feroceon > > 88FR131 rev 1 (v5l) > > > BogoMIPS? ? ? ? : 1192.75 > > > Features? ? ? ? : swp half thumb > > fastmult edsp > > > CPU implementer : 0x56 > > > CPU architecture: 5TE > > > CPU variant? ???: 0x2 > > > CPU part? ? ? ? : 0x131 > > > CPU revision? ? : 1 > > > > > > Hardware? ? ? ? : Marvell > > SheevaPlug Reference Board > > > Revision? ? ? ? : 0000 > > > Serial? ? ? ? ? : > > 0000000000000000 > > > root at slackware:~# > > > > > > The board actually looks the same as my other > dockstar > > ... I guess it's > > > just a different SOC that make sthe difference. > > > > As I've said: you are using a wrong "arcNumber". > Doozan's > > u-boot is patched so > > that the arcNumber can be set as u-boot environment > > variable. > > Basically arcNumber is just some term used by Doozan. > In > > the Linux kernel it > > is called machine type. Have a look > > at /usr/src/linux/include/generated/mach-types.h for > a > > complete list. There > > you'll find: > > #define MACH_TYPE_DOCKSTAR? ? ? ? > > ? ???2998 > > #define MACH_TYPE_SHEEVAPLUG? ? ? > > ???2097 > > If you want your kernel to recognize the dockstar you > have > > to use 2998 as > > arcNumber in u-boot. > > > > Did not understand you the first time .... but not much > changes: > I've done a saveenv avter having set > setenv arcNumber 2998 > > and these are the other things I'm fiddling with to boot > for my setup: > setenv arcNumber 2998 ; setenv usb_root /dev/sda3 ; setenv > usb_rootfstype ext3 ; usb start > setenv bootargs console=$console root=$usb_root > rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype > ext2load usb 0:1 0x800000 uImage ; ext2load usb 0:1 > 0x1100000 uinitrd ; bootm 0x800000 0x1100000 > > But none the less once I'm up the green led stops flashing > and cpuinfo still tells me that it's not a dockstar: > > root at slackware:~# cat /proc/cpuinfo > Processor? ? ???: Feroceon 88FR131 > rev 1 (v5l) > BogoMIPS? ? ? ? : 1192.75 > Features? ? ? ? : swp half thumb > fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant? ???: 0x2 > CPU part? ? ? ? : 0x131 > CPU revision? ? : 1 > > Hardware? ? ? ? : Marvell SheevaPlug > Reference Board > Revision? ? ? ? : 0000 > Serial? ? ? ? ? : > 0000000000000000 > root at slackware:~# > > I did check beforr booting that teh environment variable > was set > Marvell>> echo $arcNumber? ? ? ? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? > ??? > 2998 > Marvell>> > and also under pogoplud environment the led works and also > cpuinfo still says that it's not a dockstar. > Are the new dockstars using sheeva's SOC ? > > Regards > David > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From richard.lapointe at gmail.com Tue Apr 19 16:37:20 2011 From: richard.lapointe at gmail.com (richard.lapointe at gmail.com) Date: Tue, 19 Apr 2011 16:37:20 +0000 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <455389.74273.qm@web29719.mail.ird.yahoo.com> References: <393604.3123.qm@web29720.mail.ird.yahoo.com><455389.74273.qm@web29719.mail.ird.yahoo.com> Message-ID: <157005005-1303231046-cardhu_decombobulator_blackberry.rim.net-12874933-@bda282.bisx.prod.on.blackberry> Yeah, I got fooled by this. Would had replied but you had it solve before I finished reading the thread. BTW, I have three Dockstars all with their own Seagate Freeagent Go drives running ARMedSlack 13.37RC1 and booting from Doozan's uboot. I also use his Rescue System. I setup the first Dockstar using a serial cable but was able to get the last two up and running just using ssh. Regards Rich Lapointe Sent via BlackBerry by AT&T -----Original Message----- From: Davide Sender: armedslack-bounces at lists.armedslack.orgDate: Tue, 19 Apr 2011 15:40:32 To: Slackware ARM port Reply-To: Slackware ARM port Subject: [ARMedslack] jeff Doozan's uboot Oooops .... need to do a hardware reset o reboot for uboot to do the magic. Just setting the variable, saving it permanently and booting is not enough. Perhaps uboot uses that variable to do some initialization before you get the prompt. Sorry for making so much noise. Regards David --- Mar 19/4/11, Davide ha scritto: > Da: Davide > Oggetto: [ARMedslack] jeff Doozan's uboot > A: "Slackware ARM port" > Data: Marted? 19 Aprile 2011, 16:25 > > > --- Mar 19/4/11, Thorsten M?hlfelder > ha scritto: > > > Da: Thorsten M?hlfelder > > Oggetto: Re: [ARMedslack] jeff Doozan's uboot > > A: "Slackware ARM port" > > Data: Marted? 19 Aprile 2011, 15:32 > > Am Tuesday 19 April 2011 15:18:26 > > schrieb Davide: > > > The last cpuinfo i sent was produced by pogoplug > > system ... from slackware > > > it looks different but still is not what one > would > > expect from a dockstar: > > > root at slackware:~# cat /proc/cpuinfo > > > Processor? ? ???: Feroceon > > 88FR131 rev 1 (v5l) > > > BogoMIPS? ? ? ? : 1192.75 > > > Features? ? ? ? : swp half thumb > > fastmult edsp > > > CPU implementer : 0x56 > > > CPU architecture: 5TE > > > CPU variant? ???: 0x2 > > > CPU part? ? ? ? : 0x131 > > > CPU revision? ? : 1 > > > > > > Hardware? ? ? ? : Marvell > > SheevaPlug Reference Board > > > Revision? ? ? ? : 0000 > > > Serial? ? ? ? ? : > > 0000000000000000 > > > root at slackware:~# > > > > > > The board actually looks the same as my other > dockstar > > ... I guess it's > > > just a different SOC that make sthe difference. > > > > As I've said: you are using a wrong "arcNumber". > Doozan's > > u-boot is patched so > > that the arcNumber can be set as u-boot environment > > variable. > > Basically arcNumber is just some term used by Doozan. > In > > the Linux kernel it > > is called machine type. Have a look > > at /usr/src/linux/include/generated/mach-types.h for > a > > complete list. There > > you'll find: > > #define MACH_TYPE_DOCKSTAR? ? ? ? > > ? ???2998 > > #define MACH_TYPE_SHEEVAPLUG? ? ? > > ???2097 > > If you want your kernel to recognize the dockstar you > have > > to use 2998 as > > arcNumber in u-boot. > > > > Did not understand you the first time .... but not much > changes: > I've done a saveenv avter having set > setenv arcNumber 2998 > > and these are the other things I'm fiddling with to boot > for my setup: > setenv arcNumber 2998 ; setenv usb_root /dev/sda3 ; setenv > usb_rootfstype ext3 ; usb start > setenv bootargs console=$console root=$usb_root > rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype > ext2load usb 0:1 0x800000 uImage ; ext2load usb 0:1 > 0x1100000 uinitrd ; bootm 0x800000 0x1100000 > > But none the less once I'm up the green led stops flashing > and cpuinfo still tells me that it's not a dockstar: > > root at slackware:~# cat /proc/cpuinfo > Processor? ? ???: Feroceon 88FR131 > rev 1 (v5l) > BogoMIPS? ? ? ? : 1192.75 > Features? ? ? ? : swp half thumb > fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant? ???: 0x2 > CPU part? ? ? ? : 0x131 > CPU revision? ? : 1 > > Hardware? ? ? ? : Marvell SheevaPlug > Reference Board > Revision? ? ? ? : 0000 > Serial? ? ? ? ? : > 0000000000000000 > root at slackware:~# > > I did check beforr booting that teh environment variable > was set > Marvell>> echo $arcNumber? ? ? ? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? > ??? > 2998 > Marvell>> > and also under pogoplud environment the led works and also > cpuinfo still says that it's not a dockstar. > Are the new dockstars using sheeva's SOC ? > > Regards > David > >_______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From thenktor at gmx.de Tue Apr 19 16:57:29 2011 From: thenktor at gmx.de (Thorsten =?windows-1252?q?M=FChlfelder?=) Date: Tue, 19 Apr 2011 18:57:29 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <157005005-1303231046-cardhu_decombobulator_blackberry.rim.net-12874933-@bda282.bisx.prod.on.blackberry> References: <393604.3123.qm@web29720.mail.ird.yahoo.com> <455389.74273.qm@web29719.mail.ird.yahoo.com> <157005005-1303231046-cardhu_decombobulator_blackberry.rim.net-12874933-@bda282.bisx.prod.on.blackberry> Message-ID: <201104191857.29330.thenktor@gmx.de> Am Tuesday 19 April 2011 18:37:20 schrieb richard.lapointe at gmail.com: > Yeah, I got fooled by this. Would had replied but you had it solve before > I finished reading the thread. BTW, I have three Dockstars all with their > own Seagate Freeagent Go drives running ARMedSlack 13.37RC1 and booting > from Doozan's uboot. I also use his Rescue System. What rescue system did you use? It seems my original pogoplug system (that one the dockstar is deliverd with) does not boot anymore. So some other fallback system would be nice. -- Thorsten M?hlfelder Salix OS: www.salixos.org From richard.lapointe at gmail.com Tue Apr 19 22:48:56 2011 From: richard.lapointe at gmail.com (Rich) Date: Tue, 19 Apr 2011 18:48:56 -0400 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104191857.29330.thenktor@gmx.de> References: <393604.3123.qm@web29720.mail.ird.yahoo.com> <455389.74273.qm@web29719.mail.ird.yahoo.com> <157005005-1303231046-cardhu_decombobulator_blackberry.rim.net-12874933-@bda282.bisx.prod.on.blackberry> <201104191857.29330.thenktor@gmx.de> Message-ID: <4DAE1158.9010908@laprjns.com> I used this on all three of my Dockstars http://forum.doozan.com/read.php?4,3896 Makes for a very nice backup OS. Rich On 04/19/2011 12:57 PM, Thorsten M?hlfelder wrote: > Am Tuesday 19 April 2011 18:37:20 schrieb richard.lapointe at gmail.com: > >> Yeah, I got fooled by this. Would had replied but you had it solve before >> I finished reading the thread. BTW, I have three Dockstars all with their >> own Seagate Freeagent Go drives running ARMedSlack 13.37RC1 and booting >> from Doozan's uboot. I also use his Rescue System. >> > What rescue system did you use? It seems my original pogoplug system (that one > the dockstar is deliverd with) does not boot anymore. So some other fallback > system would be nice. > > From louigi600 at yahoo.it Wed Apr 20 10:01:10 2011 From: louigi600 at yahoo.it (Davide) Date: Wed, 20 Apr 2011 11:01:10 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <4DAE1158.9010908@laprjns.com> Message-ID: <240985.13426.qm@web29719.mail.ird.yahoo.com> Now that I've a developement environment I'll be replicating what I did with miniroot to get ap/3G/nas/router on a minimal busybox based environment. As usual I'll leave a slackwareish feeling environment to the system. Once I get it working this could be an alternative emergency rescue for those who like a slackare feel in the emerg system too :-D Unless someone comes up with a better place for it (since I no longer run my www.seicento.selfip.org site) once I finish I'll mekrr the image avalibe via rapidshare. As an alternatibe place to have this would it be a crazy thing to have a microroot armedslack ? Regards David > I used this on all three of my > Dockstars > > http://forum.doozan.com/read.php?4,3896 > > Makes for a very nice backup OS. > > Rich > > > On 04/19/2011 12:57 PM, Thorsten M?hlfelder wrote: > > Am Tuesday 19 April 2011 18:37:20 schrieb richard.lapointe at gmail.com: > >? ? > >> Yeah, I got fooled by this.? Would had > replied but you had it solve before > >> I finished reading the thread. BTW, I have three > Dockstars all with their > >> own Seagate Freeagent Go drives running ARMedSlack > 13.37RC1 and booting > >> from Doozan's uboot.? I also use his Rescue > System. > >>? ? ? > > What rescue system did you use? It seems my original > pogoplug system (that one > > the dockstar is deliverd with) does not boot anymore. > So some other fallback > > system would be nice. > > From thenktor at gmx.de Wed Apr 20 11:21:34 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Wed, 20 Apr 2011 13:21:34 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <240985.13426.qm@web29719.mail.ird.yahoo.com> References: <240985.13426.qm@web29719.mail.ird.yahoo.com> Message-ID: <201104201321.34816.thenktor@gmx.de> Am Wednesday 20 April 2011 12:01:10 schrieb Davide: > Now that I've a developement environment I'll be replicating what I did > with miniroot to get ap/3G/nas/router on a minimal busybox based > environment. So you have a Slackware system with busybox instead of the GNU tools? How much space saves this? > As an alternatibe place to have this would it be a crazy > thing to have a microroot armedslack ? The bigges NAND partition on the Dockstar is about 220 MB and could be used by a rescue/fallback root partition if no USB drive is connected. UBIFS would be a good choice for it. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Wed Apr 20 12:08:00 2011 From: louigi600 at yahoo.it (Davide) Date: Wed, 20 Apr 2011 13:08:00 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <201104201321.34816.thenktor@gmx.de> Message-ID: <549547.28934.qm@web29708.mail.ird.yahoo.com> > > Now that I've a developement environment I'll be > replicating what I did > > with miniroot to get ap/3G/nas/router on a minimal > busybox based > > environment. > > So you have a Slackware system with busybox instead of the > GNU tools? How much > space saves this? I'd stripp all that is not needed. Last time I built a similar emergency system I had, if I remember correctly: busybox, wireless tools, dropbera, vncviewer, dresktop, tinyX, fluxbox and limited hotplug/usb functionality in something like 15Mb. I think that's still avalible on freshmeat/sourceforge ... look for clash ... amongst the downloads there should be a small iso images. I had a look it's still avalible: http://sourceforge.net/projects/bclash/files/iso_images/2/ It has been unmaintained since then ans version 3 remains unfixed. BTW: the stuff I wrote at the time I had evidently less experience might be full of stuff I myself would find infuriating right now :-D This time I'll be aiming at making the AP/3G/nas/router fit in a smaller footprint. The idea would be to have: busybox, wireless tools, udev, usb utils, dropbear, nand utilities and possibly webserver and some web oriented scripting language. Web stuff aside it could be a nice small rescue system. My current armedslack miniroot AP/3G/nas/router fits in the 229Mb data mtd partition. I'm targeting the 32Mb root mtd partition for the reduced busybox setup. But in 32Mb I may not be able to get the web scripting language ... I'll see what I can manage. My last intel based surap (SUper Router Access Point) setup was less the 100Mb (if I remember correctly) and had apache and php. At worse it will be again more or less the same size. > > > As an alternatibe place to have this would it be a > crazy > > thing to have a microroot armedslack ? > > The bigges NAND partition on the Dockstar is about 220 MB > and could be used by > a rescue/fallback root partition if no USB drive is > connected. > UBIFS would be a good choice for it. I've never used ubifs ... my current setup uses jffs2 on the 229 Mb data mtd partition. jffs2 did a little compression magic and I was able to fit some 400Mb of data in the 229Mb partition. But once the system is created one can rearrange it for a different filesystem with just a small administrative effort. root at hp:~/dockstar# ls -l rootfs_ro.jffs2* -rw-r--r-- 1 root root 207506392 2011-03-29 15:53 rootfs_ro.jffs2 -rw-r--r-- 1 root root 217841664 2011-03-30 09:44 rootfs_ro.jffs2.sum root at hp:~/dockstar# du -ms rootfs_ro 471 rootfs_ro root at hp:~/dockstar# Regards David From thenktor at gmx.de Thu Apr 21 10:03:10 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Thu, 21 Apr 2011 12:03:10 +0200 Subject: [ARMedslack] Kernel kirkwood-2.6.38.2: CONFIG_N_HDLC In-Reply-To: <20110409153308.32c8d98f@pinkfloyd.tm-net> References: <201104071746.06306.thenktor@gmx.de> <20110409153308.32c8d98f@pinkfloyd.tm-net> Message-ID: <20110421120310.0de6e3d0@pinkfloyd.tm-net> Am Sat, 9 Apr 2011 15:33:08 +0200 schrieb Thorsten M?hlfelder : > Am Thu, 7 Apr 2011 19:39:16 +0100 (BST) > schrieb Stuart Winter : > > > I'll add the kernel option before the 13.37 release - either as a > > kernel rebuild, or a kernel update - which ever comes first. > > Thanks! > Just noticed: pppoe uses about 11 % CPU with downstram fully loaded > (16 MBit/s). > With synchronous mode pppoe only uses 5 % CPU on my dockstar. Sadly the connection is not really stable. The download rate fluctuates and opening web pages in the browser is slow. In the syslog are some errors: Apr 21 10:57:22 dreamtheater pppd[2911]: Protocol-Reject for unsupported protocol 0xfc7a Apr 21 10:57:27 dreamtheater pppd[2911]: Protocol-Reject for unsupported protocol 0xdb Apr 21 10:58:43 dreamtheater pppoe[2912]: read (syncReadFromPPP): Session 649: Input/output error So I'm back to asynchronous mode now. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Thu Apr 21 10:12:44 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Apr 2011 11:12:44 +0100 (BST) Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <549547.28934.qm@web29708.mail.ird.yahoo.com> Message-ID: <192269.73397.qm@web29710.mail.ird.yahoo.com> This is a mix ov a few I built myself and some gotten from current. This is waht I'll be working with and should fit in a compressed jffs2 image 64Mb big. root at slackware:/usr/src/surap_packages# du -ms * | sort -n 1 busybox-1.18.4-arm-1.tgz 1 dropbear-0.53.1-arm-1.tgz 1 hostapd-0.7.3-arm-1.tgz 1 iptables-1.4.10-arm-1.tgz 1 iw-0.9.20-arm-1.tgz 1 ppp-2.4.5-arm-1.tgz 1 udev-165-arm-2.tgz 1 usb_modeswitch-1.1.6-arm-1.tgz 1 wireless-tools-29-arm-2.tgz 2 httpd-2.2.17-arm-2.tgz 2 kernel-firmware-2.6.38.3-noarch-1.tgz 5 glibc-solibs-2.13-arm-1.tgz 8 kernel_kirkwood-2.6.38.3-arm-1.tgz 10 php-5.3.5-arm-1.tgz 15 kernel-modules-kirkwood-2.6.38.3_kirkwood-arm-1.tgz root at slackware:/usr/src/surap_packages# du -ms . 43 . root at slackware:/usr/src/surap_packages# Since booting from jffs2 image does not require initrd ... and maybe one can do without documentation .... I'll see if I can fit that in a 32Mb image. From thenktor at gmx.de Thu Apr 21 10:17:13 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Thu, 21 Apr 2011 12:17:13 +0200 Subject: [ARMedslack] jeff Doozan's uboot In-Reply-To: <192269.73397.qm@web29710.mail.ird.yahoo.com> References: <549547.28934.qm@web29708.mail.ird.yahoo.com> <192269.73397.qm@web29710.mail.ird.yahoo.com> Message-ID: <20110421121713.2d1cc8de@pinkfloyd.tm-net> Am Thu, 21 Apr 2011 11:12:44 +0100 (BST) schrieb Davide : > This is a mix ov a few I built myself and some gotten from current. > This is waht I'll be working with and should fit in a compressed > jffs2 image 64Mb big. root at slackware:/usr/src/surap_packages# du -ms > * | sort -n 1 busybox-1.18.4-arm-1.tgz > 1 dropbear-0.53.1-arm-1.tgz > 1 hostapd-0.7.3-arm-1.tgz > 1 iptables-1.4.10-arm-1.tgz > 1 iw-0.9.20-arm-1.tgz > 1 ppp-2.4.5-arm-1.tgz > 1 udev-165-arm-2.tgz > 1 usb_modeswitch-1.1.6-arm-1.tgz > 1 wireless-tools-29-arm-2.tgz > 2 httpd-2.2.17-arm-2.tgz > 2 kernel-firmware-2.6.38.3-noarch-1.tgz > 5 glibc-solibs-2.13-arm-1.tgz > 8 kernel_kirkwood-2.6.38.3-arm-1.tgz > 10 php-5.3.5-arm-1.tgz > 15 kernel-modules-kirkwood-2.6.38.3_kirkwood-arm-1.tgz > root at slackware:/usr/src/surap_packages# du -ms . > 43 . > root at slackware:/usr/src/surap_packages# > > > Since booting from jffs2 image does not require initrd ... and maybe > one can do without documentation .... I'll see if I can fit that in a > 32Mb image. Build a custom kernel with few modules ;) -- Thorsten M?hlfelder Salix OS: www.salixos.org From pino.otto at gmail.com Thu Apr 21 11:24:12 2011 From: pino.otto at gmail.com (Giovanni) Date: Thu, 21 Apr 2011 13:24:12 +0200 Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) Message-ID: Do you know whether it is possible to install and run Slackware ARM on this small computer? http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 This is the hardware: CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) Memory: 32MB = 32MB total PCI clock at 33M and currently it supports SnakeOS: http://code.google.com/p/snake-os/ Best regards, giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: From rw at rlworkman.net Thu Apr 21 15:37:20 2011 From: rw at rlworkman.net (Robby Workman) Date: Thu, 21 Apr 2011 10:37:20 -0500 Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: References: Message-ID: <20110421103720.46070226@liberty.rlwhome.lan> On Thu, 21 Apr 2011 13:24:12 +0200 Giovanni wrote: > Do you know whether it is possible to install and run Slackware ARM > on this small computer? > > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 > > This is the hardware: > > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) Memory: 32MB = 32MB > total PCI clock at 33M I don't know, but I don't think you'll be happy with it regardless. The transfer speeds are going to be terribly slow - bottlenecking due to the usb2 speeds *and* the general wimpiness of the hardware. -RW From m-lists at biscuit.org.uk Thu Apr 21 15:49:04 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Apr 2011 16:49:04 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: <20110421103720.46070226@liberty.rlwhome.lan> References: <20110421103720.46070226@liberty.rlwhome.lan> Message-ID: > I don't know, but I don't think you'll be happy with it regardless. > The transfer speeds are going to be terribly slow - bottlenecking > due to the usb2 speeds *and* the general wimpiness of the hardware. Yeah having built the distribution on 287MHZ RiscPCs for a couple of years with 256MB RAM... I don't know how I kept going. I guess because there wasn't any better or faster supported arm hardware at the time, so I didn't have anything to wish I could have ;-) I wouldn't bother with it. Some devices use lower speed ARM CPUs but their usage (and software) is tuned to the device to match the usage with the device's specs. Slackware ARM is a generic distribution built to run on the widest range of products possible, at the expense of speed in some areas (which IMO can easily be re-gained by recompiling glibc and some other critical libraries; but that's another topic :) ). From pino.otto at gmail.com Thu Apr 21 15:59:32 2011 From: pino.otto at gmail.com (Giovanni) Date: Thu, 21 Apr 2011 17:59:32 +0200 Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: References: <20110421103720.46070226@liberty.rlwhome.lan> Message-ID: Do you mean that I can install and run Slackware ARM on the NS-K330? best regards giovanni On Thu, Apr 21, 2011 at 5:49 PM, Stuart Winter wrote: > > > I don't know, but I don't think you'll be happy with it regardless. > > The transfer speeds are going to be terribly slow - bottlenecking > > due to the usb2 speeds *and* the general wimpiness of the hardware. > > Yeah having built the distribution on 287MHZ RiscPCs for a couple of years > with 256MB RAM... I don't know how I kept going. I guess because there > wasn't any better or faster supported arm hardware at the time, so I > didn't have anything to wish I could have ;-) > > I wouldn't bother with it. Some devices use lower speed ARM CPUs but their > usage (and software) is tuned to the device to match the usage with the > device's specs. Slackware ARM is a generic distribution built to run > on the widest range of products possible, at the expense of speed in some > areas (which IMO can easily be re-gained by recompiling glibc and some > other critical libraries; but that's another topic :) ). > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Apr 21 16:12:12 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Apr 2011 17:12:12 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: References: <20110421103720.46070226@liberty.rlwhome.lan> Message-ID: You would have to install it either manually using a script, or try and use the mini root filesystem (probably the easiest route). You could not install using the slackware installer because the installer wouldn't even fit into RAM! It may work though but as usual you'd have get a kernel, figure out the boot loader etc.. On Thu, 21 Apr 2011, Giovanni wrote: > Do you mean that I can install and run Slackware ARM on the NS-K330? > > best regards > giovanni > > > On Thu, Apr 21, 2011 at 5:49 PM, Stuart Winter wrote: > > > > > > I don't know, but I don't think you'll be happy with it regardless. > > > The transfer speeds are going to be terribly slow - bottlenecking > > > due to the usb2 speeds *and* the general wimpiness of the hardware. > > > > Yeah having built the distribution on 287MHZ RiscPCs for a couple of years > > with 256MB RAM... I don't know how I kept going. I guess because there > > wasn't any better or faster supported arm hardware at the time, so I > > didn't have anything to wish I could have ;-) > > > > I wouldn't bother with it. Some devices use lower speed ARM CPUs but their > > usage (and software) is tuned to the device to match the usage with the > > device's specs. Slackware ARM is a generic distribution built to run > > on the widest range of products possible, at the expense of speed in some > > areas (which IMO can easily be re-gained by recompiling glibc and some > > other critical libraries; but that's another topic :) ). > > > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > -- Stuart Winter Slackware ARM: www.armedslack.org From pino.otto at gmail.com Thu Apr 21 16:18:48 2011 From: pino.otto at gmail.com (Giovanni) Date: Thu, 21 Apr 2011 18:18:48 +0200 Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: References: <20110421103720.46070226@liberty.rlwhome.lan> Message-ID: OK, thanks. When I have one NS-K330, I will try and let you know. best regards, giovanni On Thu, Apr 21, 2011 at 6:12 PM, Stuart Winter wrote: > > You would have to install it either manually using a script, or try and > use the mini root filesystem (probably the easiest route). > You could not install using the slackware installer because the installer > wouldn't even fit into RAM! > > It may work though but as usual you'd have get a kernel, figure out the > boot loader etc.. > > On Thu, 21 Apr 2011, Giovanni wrote: > > > Do you mean that I can install and run Slackware ARM on the NS-K330? > > > > best regards > > giovanni > > > > > > On Thu, Apr 21, 2011 at 5:49 PM, Stuart Winter >wrote: > > > > > > > > > I don't know, but I don't think you'll be happy with it regardless. > > > > The transfer speeds are going to be terribly slow - bottlenecking > > > > due to the usb2 speeds *and* the general wimpiness of the hardware. > > > > > > Yeah having built the distribution on 287MHZ RiscPCs for a couple of > years > > > with 256MB RAM... I don't know how I kept going. I guess because there > > > wasn't any better or faster supported arm hardware at the time, so I > > > didn't have anything to wish I could have ;-) > > > > > > I wouldn't bother with it. Some devices use lower speed ARM CPUs but > their > > > usage (and software) is tuned to the device to match the usage with the > > > device's specs. Slackware ARM is a generic distribution built to run > > > on the widest range of products possible, at the expense of speed in > some > > > areas (which IMO can easily be re-gained by recompiling glibc and some > > > other critical libraries; but that's another topic :) ). > > > > > > > > > _______________________________________________ > > > ARMedslack mailing list > > > ARMedslack at lists.armedslack.org > > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Apr 22 05:53:43 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Apr 2011 06:53:43 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: Message-ID: <198061.94886.qm@web29707.mail.ird.yahoo.com> If you considet that you can get a dockstar for 50 Euro in Italy or possibbly less it you look world wide ... this little wimpy nas had better cost no more then 25 Euro or I'd just buy a dockstar instead. I know that it's infuriating that the prices went up from 36 euro to 52 euro but for what you get it's still a nice price .... I mean is the sheeva plug not 99 Euro (or USD I forget right now) ? whichever you can get a seagate GoFlexNET for 75 Euro. Wait I have it ... you want a gumstix and spend no less then 150 USD. Or is it that you want to play with an old sharp Zaurus (I've 3 of them do you want one ?) or some other hand-held device and spend even more ? Or would you like a Toschiba with one of those dual core arm BASED CPU ? (the best price I saw around for that was something like 225 Euro) Apart from all that is it really worth the effort fro such a wimpy piece of hardware ? Regards David --- Gio 21/4/11, Giovanni ha scritto: Da: Giovanni Oggetto: [ARMedslack] Slackware ARM on Small NAS (NS-K330) A: "Slackware ARM port" Data: Gioved? 21 Aprile 2011, 13:24 Do you know whether it is possible to install and run Slackware ARM on this small computer? http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 This is the hardware: CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) Memory: 32MB = 32MB total PCI clock at 33M and currently it supports SnakeOS: http://code.google.com/p/snake-os/ Best regards, giovanni -----Segue allegato----- _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Apr 22 08:14:53 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 22 Apr 2011 09:14:53 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: <198061.94886.qm@web29707.mail.ird.yahoo.com> References: <198061.94886.qm@web29707.mail.ird.yahoo.com> Message-ID: Davide -- can you please reply properly to the threads? I'm not sure what your mail client is doing here, but it's not prefixing the Subject line with "Re:" for a start, so it looks as if you're starting a new thread each time. Can you check the settings on your mail client, or perhaps choose a different reply method please. On Fri, 22 Apr 2011, Davide wrote: > If you considet that you can get a dockstar for 50 Euro in Italy or possibbly less it you look world wide ... this little wimpy nas had better cost no more then 25 Euro or I'd just buy a dockstar instead. I know that it's infuriating that the prices went up from 36 euro to 52 euro but for what you get it's still a nice price .... I mean is the sheeva plug not 99 Euro (or USD I forget right now) ? whichever you can get a seagate GoFlexNET for 75 Euro. > Wait I have it ... you want a gumstix and spend no less then 150 USD. > Or is it that you want to play with an old sharp Zaurus (I've 3 of them do you want one ?) or some other hand-held device and spend even more ? > Or would you like a Toschiba with one of those dual core arm BASED CPU ? (the best price I saw around for that was something like 225 Euro) > > Apart from all that is it really worth the effort fro such a wimpy piece of hardware ? > > Regards > David > > --- Gio 21/4/11, Giovanni ha scritto: > > Da: Giovanni > Oggetto: [ARMedslack] Slackware ARM on Small NAS (NS-K330) > A: "Slackware ARM port" > Data: Gioved? 21 Aprile 2011, 13:24 > > Do you know whether it is possible to install and run Slackware ARM on this small computer? > > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 > > > This is the hardware: > > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) > Memory: 32MB = 32MB total > PCI clock at 33M > > > and currently it supports SnakeOS: > > http://code.google.com/p/snake-os/ > > Best regards, > giovanni > > > > -----Segue allegato----- > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Fri Apr 22 08:32:33 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Apr 2011 09:32:33 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: Message-ID: <508436.80493.qm@web29718.mail.ird.yahoo.com> I was told that reply made a mess by some other user. I'll fix it manually just tell me what fields I should leave and where. This is what my client would normaly do as a reply: "Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)" What's good in that and what's bad in that ? Regards David --- Ven 22/4/11, Stuart Winter ha scritto: > Da: Stuart Winter > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330) > A: "Slackware ARM port" > Data: Venerd? 22 Aprile 2011, 10:14 > > Davide -- can you please reply properly to the threads? > I'm not sure what your mail client is doing here, but it's > not prefixing > the Subject line with "Re:" for a start, so it looks as if > you're starting > a new thread each time. > > Can you check the settings on your mail client, or perhaps > choose a > different reply method please. > > On Fri, 22 Apr 2011, Davide wrote: > > > If you considet that you can get a dockstar for 50 > Euro in Italy or possibbly less it you look world wide ... > this little wimpy nas had better cost no more then 25 Euro > or I'd just buy a dockstar instead. I know that it's > infuriating that the prices went up from 36 euro to 52 euro > but for what you get it's still a nice price .... I mean is > the sheeva plug not 99 Euro (or USD I forget right now) ? > whichever you can get a seagate GoFlexNET for 75 Euro. > > Wait I have it ... you want a gumstix and spend no > less then 150 USD. > > Or is it that you want to play with an old sharp > Zaurus (I've 3 of them do you want one ?) or some other > hand-held device and spend even more ? > > Or would you like a Toschiba with one of those dual > core arm BASED CPU ? (the best price I saw around for that > was something like 225 Euro) > > > > Apart from all that is it really worth the effort fro > such a wimpy piece of hardware ? > > > > Regards > > David > > > > --- Gio 21/4/11, Giovanni > ha scritto: > > > > Da: Giovanni > > Oggetto: [ARMedslack] Slackware ARM on Small NAS > (NS-K330) > > A: "Slackware ARM port" > > Data: Gioved? 21 Aprile 2011, 13:24 > > > > Do you know whether it is possible to install and run > Slackware ARM on this small computer? > > > > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 > > > > > > This is the hardware: > > > > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) > > Memory: 32MB = 32MB total > > PCI clock at 33M > > > > > > and currently it supports SnakeOS: > > > > http://code.google.com/p/snake-os/ > > > > Best regards, > > giovanni > > > > > > > > -----Segue allegato----- > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > -----Segue allegato----- > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Fri Apr 22 08:36:18 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Fri, 22 Apr 2011 10:36:18 +0200 Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: <508436.80493.qm@web29718.mail.ird.yahoo.com> References: <508436.80493.qm@web29718.mail.ird.yahoo.com> Message-ID: <20110422103618.3232112d@pinkfloyd.tm-net> Am Fri, 22 Apr 2011 09:32:33 +0100 (BST) schrieb Davide : > > I was told that reply made a mess by some other user. What I've meant was: Don't use the reply button for new threads and change the subject only because this generates a mess in the thread view ;-) > I'll fix it manually just tell me what fields I should leave and > where. This is what my client would normaly do as a reply: > "Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)" > > What's good in that and what's bad in that ? That's fine. -- Thorsten M?hlfelder Salix OS: www.salixos.org From m-lists at biscuit.org.uk Fri Apr 22 09:03:24 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 22 Apr 2011 10:03:24 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: <508436.80493.qm@web29718.mail.ird.yahoo.com> References: <508436.80493.qm@web29718.mail.ird.yahoo.com> Message-ID: Yep that works -- but normally your mail client should do it for you. You can probably configure it to prefix any reply with "Re:". It'll save wear and tear on your fingers and keyboard! ;) On Fri, 22 Apr 2011, Davide wrote: > > I was told that reply made a mess by some other user. > > I'll fix it manually just tell me what fields I should leave and where. > This is what my client would normaly do as a reply: > "Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)" > > What's good in that and what's bad in that ? > > Regards > David > --- Ven 22/4/11, Stuart Winter ha scritto: > > > Da: Stuart Winter > > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330) > > A: "Slackware ARM port" > > Data: Venerd? 22 Aprile 2011, 10:14 > > > > Davide -- can you please reply properly to the threads? > > I'm not sure what your mail client is doing here, but it's > > not prefixing > > the Subject line with "Re:" for a start, so it looks as if > > you're starting > > a new thread each time. > > > > Can you check the settings on your mail client, or perhaps > > choose a > > different reply method please. > > > > On Fri, 22 Apr 2011, Davide wrote: > > > > > If you considet that you can get a dockstar for 50 > > Euro in Italy or possibbly less it you look world wide ... > > this little wimpy nas had better cost no more then 25 Euro > > or I'd just buy a dockstar instead. I know that it's > > infuriating that the prices went up from 36 euro to 52 euro > > but for what you get it's still a nice price .... I mean is > > the sheeva plug not 99 Euro (or USD I forget right now) ? > > whichever you can get a seagate GoFlexNET for 75 Euro. > > > Wait I have it ... you want a gumstix and spend no > > less then 150 USD. > > > Or is it that you want to play with an old sharp > > Zaurus (I've 3 of them do you want one ?) or some other > > hand-held device and spend even more ? > > > Or would you like a Toschiba with one of those dual > > core arm BASED CPU ? (the best price I saw around for that > > was something like 225 Euro) > > > > > > Apart from all that is it really worth the effort fro > > such a wimpy piece of hardware ? > > > > > > Regards > > > David > > > > > > --- Gio 21/4/11, Giovanni > > ha scritto: > > > > > > Da: Giovanni > > > Oggetto: [ARMedslack] Slackware ARM on Small NAS > > (NS-K330) > > > A: "Slackware ARM port" > > > Data: Gioved? 21 Aprile 2011, 13:24 > > > > > > Do you know whether it is possible to install and run > > Slackware ARM on this small computer? > > > > > > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320 > > > > > > > > > This is the hardware: > > > > > > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) > > > Memory: 32MB = 32MB total > > > PCI clock at 33M > > > > > > > > > and currently it supports SnakeOS: > > > > > > http://code.google.com/p/snake-os/ > > > > > > Best regards, > > > giovanni > > > > > > > > > > > > -----Segue allegato----- > > > > > > _______________________________________________ > > > ARMedslack mailing list > > > ARMedslack at lists.armedslack.org > > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > > > -- > > Stuart Winter > > Slackware ARM: www.armedslack.org > > -----Segue allegato----- > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Fri Apr 22 09:45:45 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Apr 2011 10:45:45 +0100 (BST) Subject: [ARMedslack] micro root rescue system Message-ID: <652402.23698.qm@web29718.mail.ird.yahoo.com> Sorry for starting a new thread on something that was started elsewhere .... but maybe the shoot-off needs better attention with a new thread. >> This is a mix of a few I built myself and some gotten from current. >> This is what I'll be working with and should fit in a compressed >> jffs2 image 64Mb big. >> root at slackware:/usr/src/surap_packages# du -ms * | sort -n >> 1 ? busybox-1.18.4-arm-1.tgz >> 1? ? dropbear-0.53.1-arm-1.tgz >> 1 ? hostapd-0.7.3-arm-1.tgz >> 1? ? iptables-1.4.10-arm-1.tgz >> 1 ???iw-0.9.20-arm-1.tgz >> 1 ???ppp-2.4.5-arm-1.tgz >> 1 ???udev-165-arm-2.tgz >> 1? ? usb_modeswitch-1.1.6-arm-1.tgz >> 1? ? wireless-tools-29-arm-2.tgz >> 2? ? httpd-2.2.17-arm-2.tgz >> 2? ? kernel-firmware-2.6.38.3-noarch-1.tgz >> 5? ? glibc-solibs-2.13-arm-1.tgz >> 8? ? kernel_kirkwood-2.6.38.3-arm-1.tgz >> 10?? php-5.3.5-arm-1.tgz >> 15 kernel-modules-kirkwood-2.6.38.3_kirkwood-arm-1.tgz >> root at slackware:/usr/src/surap_packages# du -ms . >> 43? ? ? . >> root at slackware:/usr/src/surap_packages# >> >> Since booting from jffs2 image does not require initrd ... and maybe >> one can do without documentation .... I'll see if I can fit that in a >> 32Mb image. >> > Build a custom kernel with few modules ;) I will strip all unnecessary modules for a rescue system, remove initrd, strip documentation and carve down as much as possible ... if it won't fit I'll consider thttpd and some lighter web scripting language. Maybe web stuff is not really necessary for a rescue system anyway. Now I've a question. there are 2 ways to do this: 1) repackage the single packages and append some suffix to distinguish them from the standard packages, possibly modify the build scripts for them so that future maintenance will be easier, 2) just shove everything needed somewhere and remove all that is not needed and then build the jffs2 image. Now if this micro root system is just going to be my personal AP/3g/NAS/router/rescue the second way will take much less effort, on the other hand if you like the idea of having an armedslack micro root system that will be more then just a rescue system and possibly fit in a 32Mb compressed image; well then we should go about the first way. I say we because I'm just a user and even if I do most of the dirty work I'll need assistance from the ARMedslack team to do some of the required actions if this is of any interest to ARMedslack community. I've no reservation in sharing my work as I consider all my work GPL + it's mainly just administration so the question really is: Does armedslack want a smart micro root system ? Best regards David Rao From louigi600 at yahoo.it Fri Apr 22 13:23:41 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Apr 2011 14:23:41 +0100 (BST) Subject: [ARMedslack] kernel setup linux-2.6.38.3 Message-ID: <189756.8110.qm@web29702.mail.ird.yahoo.com> While going about recompiling kernel for micro root I noticed a few things that one can do without at least for kirkwood: Fusion MPT device support (this is a hardware RAID SCSI controller ... I doubt anyone will ever have one connected to an ARM based embedde system even if a working pcie slot. ) IEEE 1394 (FireWire) support (The kirkwood SOC does not have firewire in it so unless you have a usb2firewire adapter, which would not make much sense anyway, or a pci* slot where to place one in you wont need this. Those who have a kirkwood based system with working pcie slot and a pcie firewire card can recompile kernel ;-) ) Regards David From m-lists at biscuit.org.uk Sat Apr 23 08:09:46 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 23 Apr 2011 09:09:46 +0100 (BST) Subject: [ARMedslack] kernel setup linux-2.6.38.3 In-Reply-To: <189756.8110.qm@web29702.mail.ird.yahoo.com> References: <189756.8110.qm@web29702.mail.ird.yahoo.com> Message-ID: > Fusion MPT device support > (this is a hardware RAID SCSI controller ... I doubt anyone will ever > have one connected to an ARM based embedde system even if a working > pcie slot. > ) > > IEEE 1394 (FireWire) support There are many other things which are compiled as modules but aren't needed. One of the reasons (apart from it takes time and there's no reward) that there are unnecessary modules being built is that some other modules which *are* needed and can be used, sometimes depend upon others which cannot. Without knowing what the dependencies are, they won't be removed from the config. However, since they *are* modules, the only slight niggle I have is that the modules consume extra disc space. My thoughts are that if anybody cares enough they can review them and delete the modules they don't need: more over if someone's building an embedded system, they'd rebuild the kernel with a tuned config file rather than the kitchen sink config that comes with armedslack. From louigi600 at yahoo.it Sun Apr 24 15:28:36 2011 From: louigi600 at yahoo.it (Davide) Date: Sun, 24 Apr 2011 16:28:36 +0100 (BST) Subject: [ARMedslack] kernel setup linux-2.6.38.3 In-Reply-To: Message-ID: <539093.84616.qm@web29712.mail.ird.yahoo.com> > > Fusion MPT device support > >???(this is a hardware RAID SCSI > controller ... I doubt anyone will ever > >? ???have one connected to an ARM > based embedde system even if a working > >? ???pcie slot. > >???) > > > > IEEE 1394 (FireWire) support > > There are many other things which are compiled as modules > but aren't > needed. One of the reasons (apart from it takes time and > there's no > reward) that there are unnecessary modules being built is > that some > other modules which *are* needed and can be used, sometimes > depend upon > others which cannot.? Without knowing what the > dependencies are, they > won't be removed from the config. Cannot think of anything that requires the fusion MPT module and I'm not sure that anything that is not firewire will possibbly never need anything from the firewire stack appart from firewire2* adapter. But don't get me wrong I was just reporting that as far as I know some things could possibly be never needed on a kirkwood based system > However, since they *are* modules, the only slight niggle I > have > is that the modules consume extra disc space. > My thoughts are that if anybody cares enough they can > review them and > delete the modules they don't need: more over if someone's > building an > embedded system, they'd rebuild the kernel with a tuned > config file rather > than the kitchen sink config that comes with armedslack. But then again you're right a module is just a module: what the hell if you're stuck with small space it's up to you to get rid of what you don't need. I guess that this applies also to the micro root system. Regards David From atelszewski at gmail.com Tue Apr 26 08:16:08 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 26 Apr 2011 10:16:08 +0200 Subject: [ARMedslack] setup support for installing on NFS Message-ID: <4DB67F48.1070303@gmail.com> Hi, First of all, I'm not sure, if this should be posted here, but I guess if it shouldn't, then someone forwards this message to appropriate people;) Last time I was trying to install ARMed Slack on my ARM board, but I wanted it to be installed on NFS share. My point is that, it is much easier to develop embedded system using NFS for its rootfs. Finally I managed to do it, but I think there should be better way to do so. The problem is that, setup expects the existence of at least one partition of type Linux. So, do you think, is the setup program worth extending to support installation on NFS or at least not to refuse installing, when there's no partition available? My installation procedure looked like this: - mounted remote NFS on /mnt, - used SD/MMC so the setup finally didn't complain about lack of partition, - in TARGET menu I selected 'Continue' without setting any target partition. Any suggestions welcome;) BTW, I'm using ARMed Slack in my thesis, and in near future I'll give you some example what it can do (not robust, but gives some view). -- Pozdrawiam, Best regards, Andrzej Telszewski From m-lists at biscuit.org.uk Tue Apr 26 09:03:23 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 26 Apr 2011 10:03:23 +0100 (BST) Subject: [ARMedslack] setup support for installing on NFS In-Reply-To: <4DB67F48.1070303@gmail.com> References: <4DB67F48.1070303@gmail.com> Message-ID: > Last time I was trying to install ARMed Slack on my ARM board, but I wanted it > to be installed on NFS share. My point is that, it is much easier to develop > embedded system using NFS for its rootfs. Finally I managed to do it, but I > think there should be better way to do so. I agree -- this would be good, and as you say- it needs adjustment in the installer in order to accomplish it. > My installation procedure looked like this: > - mounted remote NFS on /mnt, > - used SD/MMC so the setup finally didn't complain about lack of partition, > - in TARGET menu I selected 'Continue' without setting any target partition. What else did you do in order to boot over nfs? I might end up doing this myself soon, and if there's anything I can do (eg additional kernel modules or something) before releasing 13.37, I'd like to do it. > BTW, I'm using ARMed Slack in my thesis, and in near future I'll give you some > example what it can do (not robust, but gives some view). Sounds good! -- Stuart Winter Slackware ARM: www.armedslack.org From atelszewski at gmail.com Tue Apr 26 09:15:14 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 26 Apr 2011 11:15:14 +0200 Subject: [ARMedslack] setup support for installing on NFS In-Reply-To: References: <4DB67F48.1070303@gmail.com> Message-ID: <4DB68D22.5000506@gmail.com> On 04/26/2011 11:03 AM, Stuart Winter wrote: > What else did you do in order to boot over nfs? > I might end up doing this myself soon, and if there's anything I can do > (eg additional kernel modules or something) > before releasing 13.37, I'd like to do it. Would you like me to post the complete mini tutorial here? Basically it consists of setting up NFS server and configuring U-Boot. -- Pozdrawiam, Best regards, Andrzej Telszewski From m-lists at biscuit.org.uk Tue Apr 26 11:07:20 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 26 Apr 2011 12:07:20 +0100 (BST) Subject: [ARMedslack] setup support for installing on NFS In-Reply-To: <4DB68D22.5000506@gmail.com> References: <4DB67F48.1070303@gmail.com> <4DB68D22.5000506@gmail.com> Message-ID: > Would you like me to post the complete mini tutorial here? Basically it > consists of setting up NFS server and configuring U-Boot. Yes please! -- Stuart Winter Slackware ARM: www.armedslack.org From jawkins at armedslack.org Tue Apr 26 12:17:00 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Tue, 26 Apr 2011 13:17:00 +0100 (BST) Subject: [ARMedslack] setup support for installing on NFS In-Reply-To: <4DB67F48.1070303@gmail.com> References: <4DB67F48.1070303@gmail.com> Message-ID: On Tue, 26 Apr 2011, Andrzej Telszewski wrote: > My installation procedure looked like this: > - mounted remote NFS on /mnt, > - used SD/MMC so the setup finally didn't complain about lack of partition, > - in TARGET menu I selected 'Continue' without setting any target partition. > > Any suggestions welcome;) I did an NFS root install a while back. According to my notes I did the following to trick the installer into not requiring a target partition: mount 192.168.1.1:/home/jawkins/devel/armlinux/guruplug-rootfs /mnt -o nolock { sleep 1; touch /var/log/setup/tmp/SeTnative; } & setup Bit of a hack, but it did the job :) Cheers, Jim From atelszewski at gmail.com Tue Apr 26 12:16:56 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 26 Apr 2011 14:16:56 +0200 Subject: [ARMedslack] A step by step guide to ARMed Slack on NFS root;) Message-ID: <4DB6B7B8.7080209@gmail.com> Hi, The guide is here;) Directories/locations: a) ARMed Slack packages series: /home/soft/cross/armedslack/armedslack-13.1/slackware b) installer (unpacked initrd): /home/soft/cross/bf-210/rootfs-installer c) initrd: /home/soft/cross/armedslack/armedslack-13.1/slackware/isolinux/uinitrd-kirkwood.img d) kernel common to both installer and installed system: /home/soft/cross/bf-210/rootfs/boot/uImage IP addresses: 10.7.11.0 - subnet address 255.255.255.0 - subnet mask 10.7.11.1 - gateway 10.7.11.2 - server/host 10.7.11.10 - board/target A. Host ------- 1. Installer preparation $ cd /home/soft/cross/bf-210/rootfs-installer $ dd if=/home/soft/cross/armedslack/armedslack-13.1/isolinux/uinitrd-kirkwood.img bs=64 skip=1 | gzip -dc | cpio -div 2. NFS server /etc/exports: /home/soft/cross/bf-210/rootfs-installer 10.7.11.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check) /home/soft/cross/armedslack/armedslack-13.1/slackware 10.7.11.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check) /home/soft/cross/bf-210/rootfs 10.7.11.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check) $ sh /etc/rc.d/rc.rpc start $ sh /etc/rc.d/rc.nfsd start (probably the permissions in exports could be fine grained). 3. Kernel Prepare and compile your kernel and copy it to: /home/soft/cross/bf-210/rootfs/boot/uImage The target kernel should have at least the followings compiled-in: CONFIG_IP_PNP CONFIG_NFS_FS CONFIG_ROOT_NFS B. Target --------- 1. My U-Boot environment This is environment I use to boot installed system: boff> printenv bootdelay=3 baudrate=115200 ethaddr=00:17:09:00:04:11 loadaddr=0x21000000 gatewayip=10.7.11.1 netmask=255.255.255.0 bootcmd=nfs; bootm rootpath=/home/soft/cross/bf-210/rootfs bootfile=/home/soft/cross/bf-210/rootfs/boot/uImage ipaddr=10.7.11.10 serverip=10.7.11.2 bootargs=mem=32M console=ttyS0,115200n8 rootdelay=1 ro root=/dev/nfs nfsroot=10.7.11.2:/home/soft/cross/bf-210/rootfs ip=10.7.11.10:10.7.11.2:10.7.11.1:255.255.255.0::eth0: stdin=serial stdout=serial stderr=serial Environment size: 478/508 bytes Be aware, that nfsroot and ip are part of the bootargs environment variable (they might seem to separate because of e-mail's line breaking). For the installation, the following should be changed: rootpath should point to /home/soft/cross/bf-210/rootfs-installer bootrgs - ro flag should be changed to rw flag After changes, you should reload bootargs environment variable, e.g.: setenv bootargs mem=32M console=ttyS0,115200n8 rootdelay=1 ro root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::eth0: I guess the options in bootargs are self-explanatory, if not, refer to Documentation/filesystems/nfs/nfsroot.txt Now you can issue 'boot' command. When you are at the installer prompt, mount the NFS location the system is going to be installed to: $ rpc.portmap $ rpc.statd $ mount -t nfs -o vers=3 10.7.11.2:/home/soft/cross/bf-210/rootfs /mnt Remember, that at this time, you need at least one partition of type Linux. Run 'setup' and do the thing you have done for at least one billion times already;) But first, in TARGET submenu just hit 'Continue' without selecting any target partition. After installation is complete, change the U-Boot environment to its previous state so it can boot freshly installed system. Before loading the just installed system, it is worth to do some setup on the HOST: - in /home/soft/cross/bf-210/rootfs/etc/fstab add the line for the rootfs: 10.7.11.2:/home/soft/cross/bf-210/rootfs / nfs noauto 0 0 - in /home/soft/cross/bf-210/rootfs/etc/securetty and /home/soft/cross/bf-210/rootfs/etc/inittab: configure the serial console if you use one Now you can 'boot'. I know that there are some things that can be done better (especially when it comes to the NFS configuration parameters), but this just works and I needed it very quickly. Any questions/comments are welcome. -- Pozdrawiam, Best regards, Andrzej Telszewski From atelszewski at gmail.com Tue Apr 26 12:22:23 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 26 Apr 2011 14:22:23 +0200 Subject: [ARMedslack] setup support for installing on NFS In-Reply-To: References: <4DB67F48.1070303@gmail.com> Message-ID: <4DB6B8FF.7020509@gmail.com> On 04/26/2011 02:17 PM, Jim Hawkins wrote: > I did an NFS root install a while back. According to my notes I did the > following to trick the installer into not requiring a target partition: > > mount 192.168.1.1:/home/jawkins/devel/armlinux/guruplug-rootfs /mnt -o nolock > { sleep 1; touch /var/log/setup/tmp/SeTnative; }& setup > > Bit of a hack, but it did the job :) > Yep, any hack is good;) But if there are so many hackers for that particular feature, I guess it should be included in the next release of the installer;) -- Pozdrawiam, Best regards, Andrzej Telszewski From louigi600 at yahoo.it Fri Apr 29 08:06:44 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 29 Apr 2011 09:06:44 +0100 (BST) Subject: [ARMedslack] qemu-network-tun.sh modified script Message-ID: <920274.16512.qm@web29716.mail.ird.yahoo.com> If anyone else finds this handy this works with dhcp client on both host and guest and also gets rid of all rc.local requirements. On the guest os you will need to config interface once system is up (static or via dhcp) Needs fixing for static ip reconfiguration/rerouting on host system after bridge creation. I apologize for my non standard indentation ... #!/bin/sh echo 1 > /proc/sys/net/ipv4/ip_forward echo 1024 > /proc/sys/dev/rtc/max-user-freq if [ $(ifconfig |grep "Link encap" |grep -c "^br0") -lt 1 ] then if [ $(ps -eo pid,cmd |grep -v grep |grep -c dhcpcd) -ge 1 ] then RESTART_NET="dhcpcd -t 10 br0" killall dhcpcd else RESTART_NET="to be fixed for static networking ifconfig and route" ifconfig eth0 0.0.0.0 down fi brctl addbr br0 brctl stp br0 off brctl setfd br0 1 brctl addif br0 eth0 $RESTART_NET fi /sbin/ifconfig $1 0.0.0.0 promisc up /sbin/brctl addif br0 $1 sleep 1 brctl show From unixjohn1969 at gmail.com Fri Apr 29 08:23:31 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 29 Apr 2011 04:23:31 -0400 Subject: [ARMedslack] qemu-network-tun.sh modified script In-Reply-To: <920274.16512.qm@web29716.mail.ird.yahoo.com> References: <920274.16512.qm@web29716.mail.ird.yahoo.com> Message-ID: <4DBA7583.2000400@gmail.com> On 04/29/2011 04:06 AM, Davide wrote: > If anyone else finds this handy this works with dhcp client on both host and guest and also gets rid of all rc.local requirements. > On the guest os you will need to config interface once system is up (static or via dhcp) > Needs fixing for static ip reconfiguration/rerouting on host system after bridge creation. > > I apologize for my non standard indentation ... Also if anyone cares, I wrote a script like that over a year ago to lanuch a private network for many VMs (all Linux distros - many versions) to compile software for a company I was at. It is configured a private network so some assembly is required. But I made most of it configurable up top so it could be on a public adapter. I developed it on Slack (of course) then deployed it to a Suse production box. I had set up NFS on the host with the source code. The source would get copied to its own branch for the machine it was compiling for, fire up the VM, compile over NFS, create package on NFS host (rpm/tgz/txz/deb/etc), then die, rinse and repeat. #!/bin/sh # Start/stop qemu's private network # Revised: 12/16/2009 JJO ### BEGIN INIT INFO # Provides: qemunet # Required-Start: $network # Required-Stop: $network # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start the qemu private network ### END INIT INFO ETHIP=10.10.10.1 GATEWAY= ETHBC=10.10.10.255 BRIDGE=br0 ETH=dummy0 TAP=tap0 # A little SuSE sanity check [ -f /etc/SuSE-release ] && /sbin/rmmod dummy0 >/dev/null 2>&1 # Start the qemu private network qemunet_start() { # Make sure the qemu private network isnt already running PROBLEM=FALSE for IF in $ETH $TAP $BRIDGE; do /sbin/ifconfig | grep $IF >/dev/null 2>&1 [ $? = 0 ] && PROBLEM=TRUE done if [ $PROBLEM = TRUE ]; then echo "All or part of the qemu private network is already running!" echo "Cowardly refusing to start it again! BYE!" exit 1 fi echo "Starting the qemu private network..." # Make sure the kernel module is loaded /sbin/lsmod | grep dummy >/dev/null 2>&1 [ $? = 1 ] && /sbin/modprobe dummy # First take interface down, then bring it up with IP 0.0.0.0 /sbin/ifconfig $ETH down /sbin/ifconfig $ETH 0.0.0.0 promisc up # Bring up the tap device (name specified as first argument, by QEMU) /usr/sbin/openvpn --mktun --dev $TAP /sbin/ifconfig $TAP 0.0.0.0 promisc up # create the bridge between eth0 and the tap device /sbin/brctl addbr $BRIDGE /sbin/brctl addif $BRIDGE $ETH /sbin/brctl addif $BRIDGE $TAP # only a single bridge so loops are not possible, turn off spanning tree protocol /sbin/brctl stp $BRIDGE off # Bring up the bridge with ETHIP and add the default route /sbin/ifconfig br0 $ETHIP netmask 255.255.255.0 broadcast $ETHBC [ -n "$GATEWAY" ] && /sbin/route add default gw $GATEWAY } # Stop the qemu private network qemunet_stop() { echo "Stopping the qemu private network..." # Bring down interface and br0 /sbin/ifconfig $ETH down /sbin/ifconfig $BRIDGE down /sbin/rmmod dummy # Delete the bridge /sbin/brctl delbr $BRIDGE # delete the tap device /usr/sbin/openvpn --rmtun --dev $TAP } # Restart the qemu private network qemunet_restart() { qemunet_stop sleep 1 qemunet_start } # Check if the qemu private network is up and running qemunet_status() { echo -n "Checking the qemu private network: " # Check the qemu private inetwork for IF in $ETH $TAP $BRIDGE; do /sbin/ifconfig | grep $IF >/dev/null 2>&1 if [ $? = 1 ]; then echo -n "$IF is down" else echo -n "$IF is up" fi if [ $IF = $BRIDGE ]; then echo "." else echo -n ", " fi done } case "$1" in 'start') qemunet_start ;; 'stop') qemunet_stop ;; 'restart') qemunet_restart ;; 'status') qemunet_status ;; *) echo "usage $0 start|stop|restart|status" esac -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From louigi600 at yahoo.it Sat Apr 30 05:40:52 2011 From: louigi600 at yahoo.it (Davide) Date: Sat, 30 Apr 2011 06:40:52 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: Message-ID: <212840.62864.qm@web29708.mail.ird.yahoo.com> I'm interested in the recompiling glibc thing to regain speed on specific hardware: has this been discussed in the ML previously ? --- Gio 21/4/11, Stuart Winter ha scritto: > Da: Stuart Winter > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330) > A: "Slackware ARM port" > Data: Gioved? 21 Aprile 2011, 17:49 > > > I don't know, but I don't think you'll be happy with > it regardless. > > The transfer speeds are going to be terribly slow - > bottlenecking > > due to the usb2 speeds *and* the general wimpiness of > the hardware. > > Yeah having built the distribution on 287MHZ RiscPCs for a > couple of years > with 256MB RAM... I don't know how I kept going.? I > guess because there > wasn't any better or faster supported arm hardware at the > time, so I > didn't have anything to wish I could have ;-) > > I wouldn't bother with it. Some devices use lower speed ARM > CPUs but their > usage (and software) is tuned to the device to match the > usage with the > device's specs.? Slackware ARM is a generic > distribution built to run > on the widest range of products possible, at the expense of > speed in some > areas (which IMO can easily be re-gained by recompiling > glibc and some > other critical libraries; but that's another topic :) ). > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From m-lists at biscuit.org.uk Sat Apr 30 07:46:23 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 30 Apr 2011 08:46:23 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: <212840.62864.qm@web29708.mail.ird.yahoo.com> References: <212840.62864.qm@web29708.mail.ird.yahoo.com> Message-ID: I think it has but I don't recall anybody having done it. What hardware? I'm quite interested in it because I'm still thinking about building armedslack for armv5te (it's armv4 at the moment). We need some valid test cases. On Sat, 30 Apr 2011, Davide wrote: > I'm interested in the recompiling glibc thing to regain speed on specific hardware: has this been discussed in the ML previously ? > > --- Gio 21/4/11, Stuart Winter ha scritto: > > > Da: Stuart Winter > > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330) > > A: "Slackware ARM port" > > Data: Gioved? 21 Aprile 2011, 17:49 > > > > > I don't know, but I don't think you'll be happy with > > it regardless. > > > The transfer speeds are going to be terribly slow - > > bottlenecking > > > due to the usb2 speeds *and* the general wimpiness of > > the hardware. > > > > Yeah having built the distribution on 287MHZ RiscPCs for a > > couple of years > > with 256MB RAM... I don't know how I kept going.? I > > guess because there > > wasn't any better or faster supported arm hardware at the > > time, so I > > didn't have anything to wish I could have ;-) > > > > I wouldn't bother with it. Some devices use lower speed ARM > > CPUs but their > > usage (and software) is tuned to the device to match the > > usage with the > > device's specs.? Slackware ARM is a generic > > distribution built to run > > on the widest range of products possible, at the expense of > > speed in some > > areas (which IMO can easily be re-gained by recompiling > > glibc and some > > other critical libraries; but that's another topic :) ). > > > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Sat Apr 30 14:52:58 2011 From: louigi600 at yahoo.it (Davide) Date: Sat, 30 Apr 2011 15:52:58 +0100 (BST) Subject: [ARMedslack] Slackware ARM on Small NAS (NS-K330) In-Reply-To: Message-ID: <510150.81618.qm@web29719.mail.ird.yahoo.com> I wanted to get all I can out of my dockstar if it works well I might even do that on my zauruses (C 760/860/1000). The zauri should all be ARMv5 as husky boxer are PXA255 and Akita is PXA270. While the dockstar I'm not sure but I think it's ARMv5 too. It would be the first time I look into rebuilding glibc in order to get better performance and actually I don't recall ever doing it at all so if I did I just followed the build scripts to build it. Any help is appreciated for this task. Regards David > I think it has but I don't recall anybody having done it. > > What hardware? > > I'm quite interested in it because I'm still thinking about > building > armedslack for armv5te (it's armv4 at the moment). > We need some valid test cases. > > On Sat, 30 Apr 2011, Davide wrote: > > > I'm interested in the recompiling glibc thing to > regain speed on specific hardware: has this been discussed > in the ML previously ? > > > > --- Gio 21/4/11, Stuart Winter > ha scritto: > > > > > Da: Stuart Winter > > > Oggetto: Re: [ARMedslack] Slackware ARM on Small > NAS (NS-K330) > > > A: "Slackware ARM port" > > > Data: Gioved? 21 Aprile 2011, 17:49 > > > > > > > I don't know, but I don't think you'll be > happy with > > > it regardless. > > > > The transfer speeds are going to be terribly > slow - > > > bottlenecking > > > > due to the usb2 speeds *and* the general > wimpiness of > > > the hardware. > > > > > > Yeah having built the distribution on 287MHZ > RiscPCs for a > > > couple of years > > > with 256MB RAM... I don't know how I kept > going.? I > > > guess because there > > > wasn't any better or faster supported arm > hardware at the > > > time, so I > > > didn't have anything to wish I could have ;-) > > > > > > I wouldn't bother with it. Some devices use lower > speed ARM > > > CPUs but their > > > usage (and software) is tuned to the device to > match the > > > usage with the > > > device's specs.? Slackware ARM is a generic > > > distribution built to run > > > on the widest range of products possible, at the > expense of > > > speed in some > > > areas (which IMO can easily be re-gained by > recompiling > > > glibc and some > > > other critical libraries; but that's another > topic :) ). > > > > > > > > > _______________________________________________ > > > ARMedslack mailing list > > > ARMedslack at lists.armedslack.org > > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > -----Segue allegato----- > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack >