From louigi600 at yahoo.it Sun Jul 1 07:42:14 2012 From: louigi600 at yahoo.it (Davide) Date: Sun, 1 Jul 2012 08:42:14 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> >I've dropped this into /usr/lib/mozilla/plugins: >? http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so >And firefox about:plugins now says: >=== >Shockwave Flash ?> ? File: libflashplayer.so ?> ? Version: ?> ? Shockwave Flash 10.1 r120 >MIME Type? ? ? Description? ? Suffixes >application/x-shockwave-flash? Shockwave Flash? ? ? ? swf >application/futuresplash? ? ? ? FutureSplash Player? ? spl >=== I did the same after upgrading to the mesa package below and now firefox no longer complains about not being able to load libflashplayer.so but none the less the plugin is not detected (I recently updated to current). >I can watch a video on youtube? x11vnc but I don't have a working native >X at the moment as x/xf86-video-xgi-1.6.0-arm-3.tgz doesn't work with the new version of X >and won't build yet. >Give it a go.? This package is built on the new -current so I don't know >if it'll work on the one that's public at the moment (although I would >imagine it will) >? http://armed.slackware.com/test/mesa-8.0.3-arm-2.tgz >The src is here: >? http://armed.slackware.com/test/src/ >All I've changed is: > Added ./configure options: > --with-gallium-drivers=" nouveau r600 r300 svga" >? --enable-gles1 --enable-gles2 --enable-openvg --enable-gallium-egl >and removed --disable-egl Maybe the version of libflashplayer.so is incompatible with firefox 13 or maybe there is some other issue with the mesa package on current. What were you running on when you got things to work ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Sun Jul 1 10:25:13 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Sun, 1 Jul 2012 11:25:13 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: On 1 July 2012 08:42, Davide wrote: > Maybe the version of libflashplayer.so is incompatible with firefox 13 or > maybe there is some other issue with the mesa package on current. Am I missing something? While modern Android OS may share the same kernel with a traditional Linux distro, its runtime library is not binary compatible with the GNU libraries. As the flash plugin is not available in source code I don't see why people can assume one can just drop libflashplayer.so for Android and expect it to work and even if it did you'd open a can of worms. The only realistic solution (which I'm not going to try at the moment) is to run some sort of Android SDK emulator. But if I have missed the point please correct me where I'm wrong. -- Ottavio From m-lists at biscuit.org.uk Sun Jul 1 12:58:41 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 1 Jul 2012 13:58:41 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: > available in source code I don't see why people can assume one can > just drop libflashplayer.so for Android and expect it to work and even > if it did you'd open a can of worms. It does work - I tested it. I suspect it doesn't work for Davide because the library is compiled for a CPU higher than his own. This is what I ran it on: root at pepa:~/ac/source/kde# cat /proc/cpuinfo Processor : ARMv7 Processor rev 0 (v7l) processor : 0 BogoMIPS : 1987.37 processor : 1 BogoMIPS : 1993.93 Features : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x1 CPU part : 0xc09 CPU revision : 0 Hardware : trimslice Revision : 0000 Serial : 0000000000000000 root at pepa:~/ac/source/kde# From stanley at stanleygarvey.com Mon Jul 2 00:55:34 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 02 Jul 2012 01:55:34 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: References: Message-ID: <20120702005534.C9198A9C41998@bmail04.one.com> On Jul 1, 2012 13:58 "Stuart Winter" wrote: > > available in source code I don't see why people can assume one can > > just drop libflashplayer.so for Android and expect it to work and > > even > > if it did you'd open a can of worms. > > > > > It is a can of worms. It is closed source and lets hope it's > > > finished. Adobe don't fully support it and have publicly said so. > > > > It does work - I tested it. I suspect it doesn't work for Davide > because > the library is compiled for a CPU higher than his own. This is what I > ran > it on: > > >I am a pragmatist, if it works use it. Still hoping the web goes > >HTML5, MP4, OGG. > Steve Jobs may have had a point. > > > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Jul 2 06:59:24 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 2 Jul 2012 07:59:24 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> >> available in source code I don't see why people can assume one can >> just drop libflashplayer.so for Android and expect it to work and even >> if it did you'd open a can of worms. >It does work - I tested it.? I suspect it doesn't work for Davide because >the library is compiled for a CPU higher than his own.? This is what I ran >it on: >root at pepa:~/ac/source/kde# cat /proc/cpuinfo >Processor? ? ? : ARMv7 Processor rev 0 (v7l) >processor? ? ? : 0 >BogoMIPS? ? ? ? : 1987.37 >processor? ? ? : 1 >BogoMIPS? ? ? ? : 1993.93 >Features? ? ? ? : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 >tls >CPU implementer : 0x41 >CPU architecture: 7 >CPU variant? ? : 0x1 >CPU part? ? ? ? : 0xc09 >CPU revision? ? : 0 >Hardware? ? ? ? : trimslice >Revision? ? ? ? : 0000 >Serial? ? ? ? ? : 0000000000000000 >root at pepa:~/ac/source/kde# ? That's odd: AC100 is a TEGRA2 (Tegra 250 T20) CORTEX-A9 based that only lacks NEON instruntions. Unless the library uses NEON instruntions (that I assume is not the sace or the android it came from would not run on any TEGRA2 based device) the most sensible guass I can make is that I need to enable some kernel options that were left off. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Jul 2 07:32:05 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 2 Jul 2012 08:32:05 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> >>> available in source code I don't see why people can assume one can >>> just drop libflashplayer.so for Android and expect it to work and even >>> if it did you'd open a can of worms. >>It does work - I tested it.? I suspect it doesn't work for Davide because >>the library is compiled for a CPU higher than his own.? This is what I ran >>it on: >>root at pepa:~/ac/source/kde# cat /proc/cpuinfo >>Processor? ? ? : ARMv7 Processor rev 0 (v7l) >>processor? ? ? : 0 >>BogoMIPS? ? ? ? : 1987.37 >>processor? ? ? : 1 >>BogoMIPS? ? ? ? : 1993.93 >>Features? ? ? ? : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 >>tls >>CPU implementer : 0x41 >>CPU architecture: 7 >>CPU variant? ? : 0x1 >>CPU part? ? ? ? : 0xc09 >>CPU revision? ? : 0 >>Hardware? ? ? ? : trimslice >>Revision? ? ? ? : 0000 >>Serial? ? ? ? ? : 0000000000000000 >>root at pepa:~/ac/source/kde# ? >That's odd: AC100 is a TEGRA2 (Tegra 250 T20) CORTEX-A9 based that only lacks NEON instruntions. >Unless the library uses NEON instruntions (that I assume is not the sace or the android it came from would not run on any TEGRA2 based device) the most sensible guass I can make is that I need to enable some kernel >options that were left off. I think I can exclude any kernel options as my cpuinfo only differs from that in Bogomibs and Hardware section ... BogoMIPS? ? ? ? : 1992.29 ... BogoMIPS? ? ? ? : 1992.29 ... Hardware? ? ? ? : Toshiba AC100/ Dynabook AZ The rest is exactly the same. What else could it be ? Regards David _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From unixjohn1969 at gmail.com Mon Jul 2 07:15:28 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Mon, 02 Jul 2012 03:15:28 -0400 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: <4FF14A90.4040901@gmail.com> On 07/01/2012 06:25 AM, Ottavio Caruso wrote: > On 1 July 2012 08:42, Davide wrote: >> Maybe the version of libflashplayer.so is incompatible with firefox 13 or >> maybe there is some other issue with the mesa package on current. > > Am I missing something? While modern Android OS may share the same > kernel with a traditional Linux distro, its runtime library is not > binary compatible with the GNU libraries. As the flash plugin is not > available in source code I don't see why people can assume one can > just drop libflashplayer.so for Android and expect it to work and even > if it did you'd open a can of worms. The android system does not use glibc. It uses a system called Bionic. It is essentially glibc trimmed down. So if it works on Bionic it should work on glibc. http://en.wikipedia.org/wiki/Bionic_%28software%29 Hope this helps. John -- === 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 m-lists at biscuit.org.uk Mon Jul 2 09:51:03 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 2 Jul 2012 10:51:03 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: > What else could it be ? Dunno but you can try with the new -current updates once I push them out this week. From pr0f3ss0r1492 at yahoo.com Wed Jul 4 11:24:16 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 4 Jul 2012 12:24:16 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: <20120702005534.C9198A9C41998@bmail04.one.com> References: <20120702005534.C9198A9C41998@bmail04.one.com> Message-ID: On 2 July 2012 01:55, stanley garvey wrote: >> It is a can of worms. It is closed source and lets hope it's finished. >> Adobe don't fully support it and have publicly said so. Yes, Adobe has officially end-of-lifed Flash Player on Android: http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html -- Ottavio From thenktor at gmail.com Wed Jul 4 11:57:05 2012 From: thenktor at gmail.com (=?ISO-8859-1?Q?Thorsten_M=FChlfelder?=) Date: Wed, 4 Jul 2012 13:57:05 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <20120702005534.C9198A9C41998@bmail04.one.com> Message-ID: 2012/7/4 Ottavio Caruso : > On 2 July 2012 01:55, stanley garvey wrote: > >>> It is a can of worms. It is closed source and lets hope it's finished. >>> Adobe don't fully support it and have publicly said so. > > Yes, Adobe has officially end-of-lifed Flash Player on Android: > > http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html Not only on Android, but on Linux in general: http://tech.slashdot.org/story/12/02/22/1323204/adobe-makes-flash-on-gnulinux-chrome-only Adobe Flash will only be available as part of Google Chrome/Chromium. Thorsten From louigi600 at yahoo.it Wed Jul 4 13:51:29 2012 From: louigi600 at yahoo.it (Davide) Date: Wed, 4 Jul 2012 14:51:29 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <20120702005534.C9198A9C41998@bmail04.one.com> Message-ID: <1341409889.6777.YahooMailNeo@web29703.mail.ird.yahoo.com> >>> It is a can of worms. It is closed source and lets hope it's finished. >>> Adobe don't fully support it and have publicly said so. I think it's much worse then a can of worms. I really don't understand why people use flash for things that do not need flash: why the hell should one use flash for authentication on a web site (on some sites if you don't have flash you cannot even see the box for typing the authentication) ! I feel pledged into using flash :-D If it wasn't that sometimes it's handy to watch video documentation (like for opening up a device without braking it) I'd have been happy to use swfdec for basic flash support. I tryed gnash but I was unable to deal with the dependencies for compiling it. >Yes, Adobe has officially end-of-lifed Flash Player on Android: >http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html Android really has only uses a modified linux kernel and has nothing else in common with any other linux distribution so when Adobe supported flash on mobile devices it never meant that Adobe supported flash on ARM linux devices. Cheers David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Wed Jul 4 14:03:02 2012 From: louigi600 at yahoo.it (Davide) Date: Wed, 4 Jul 2012 15:03:02 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <20120702005534.C9198A9C41998@bmail04.one.com> Message-ID: <1341410582.92674.YahooMailNeo@web29703.mail.ird.yahoo.com> ________________________________ >>>> It is a can of worms. It is closed source and lets hope it's finished. >>>> Adobe don't fully support it and have publicly said so. >> >> Yes, Adobe has officially end-of-lifed Flash Player on Android: >> >> http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html >Not only on Android, but on Linux in general: >http://tech.slashdot.org/story/12/02/22/1323204/adobe-makes-flash-on-gnulinux-chrome-only >Adobe Flash will only be available as part of Google Chrome/Chromium. Can chrome/chromium run on armedslack and not loose the flash support ? A while back I attempted using chrome/chromium on x86 slackware but my experience was limiten in the ['could not compile' ... 'very bad user experience'] range, I seriously doubt that even now it could be any better then that on ARM.... but maybe I'm wrong ? Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Wed Jul 4 14:11:15 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 4 Jul 2012 15:11:15 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: <1341410582.92674.YahooMailNeo@web29703.mail.ird.yahoo.com> References: <20120702005534.C9198A9C41998@bmail04.one.com> <1341410582.92674.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: On 4 July 2012 15:03, Davide wrote: > Can chrome/chromium run on armedslack and not loose the flash support ? I am not aware of Chrome/Chromium running on ARM at all. The problem is in the hardware, not the software. Adobe will pay their developers to develop on 'certified' architectures' only, that is the chip manufacturer will have to pay money for it: ===quote=== To ensure that the Flash Player provides the best possible experience for users, our partner program requires certification of each Flash Player implementation. Certification includes extensive testing to ensure web content works as expected, and that the Flash Player provides a good user experience. Certified devices typically include the Flash Player pre-loaded at the factory or as part of a system update. ==unquote=== -- Ottavio From oldtopman at guy-family.com Wed Jul 4 15:03:22 2012 From: oldtopman at guy-family.com (Old Man) Date: Wed, 4 Jul 2012 09:03:22 -0600 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <20120702005534.C9198A9C41998@bmail04.one.com> <1341410582.92674.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: Chrome on ARM is just an android package: https://www.google.com/intl/en/chrome/browser/mobile/android.html#utm_campaign=en&utm_source=en-ha-na-us-bk&utm_medium=ha At this point you'd be writing an android emulator. Not that it's a bad idea though, just a difficult one. On Jul 4, 2012, at 8:11 AM, Ottavio Caruso wrote: > On 4 July 2012 15:03, Davide wrote: >> Can chrome/chromium run on armedslack and not loose the flash support ? > > I am not aware of Chrome/Chromium running on ARM at all. > > The problem is in the hardware, not the software. Adobe will pay their > developers to develop on 'certified' architectures' only, that is the > chip manufacturer will have to pay money for it: > > ===quote=== > > To ensure that the Flash Player provides the best possible experience > for users, our partner program requires certification of each Flash > Player implementation. Certification includes extensive testing to > ensure web content works as expected, and that the Flash Player > provides a good user experience. Certified devices typically include > the Flash Player pre-loaded at the factory or as part of a system > update. > > ==unquote=== > > -- > Ottavio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From thenktor at gmail.com Wed Jul 4 17:42:40 2012 From: thenktor at gmail.com (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Wed, 4 Jul 2012 19:42:40 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <20120702005534.C9198A9C41998@bmail04.one.com> <1341410582.92674.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: <20120704194240.23a46314@pinkfloyd.tm-net> Am Wed, 4 Jul 2012 09:03:22 -0600 schrieb Old Man : > Chrome on ARM is just an android package: > https://www.google.com/intl/en/chrome/browser/mobile/android.html#utm_campaign=en&utm_source=en-ha-na-us-bk&utm_medium=ha No, it should be possible to build "real" chromium on ARMed Slack and run it in X. -- Thorsten M?hlfelder Salix OS: www.salixos.org From thenktor at gmail.com Wed Jul 4 17:47:09 2012 From: thenktor at gmail.com (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Wed, 4 Jul 2012 19:47:09 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: <1341409889.6777.YahooMailNeo@web29703.mail.ird.yahoo.com> References: <20120702005534.C9198A9C41998@bmail04.one.com> <1341409889.6777.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: <20120704194709.5f878127@pinkfloyd.tm-net> Am Wed, 4 Jul 2012 14:51:29 +0100 (BST) schrieb Davide : > why the hell should one use flash for authentication on a web site > (on some sites if you don't have flash you cannot even see the box > for typing the authentication) ! I've never seen that and actually it's kind of funny nowadays. I guess the webmaster does not want to have many users? :-D The mobile phone/tablet market is growing every day and neither iOS nor recent Android is meant to run flash. -- Thorsten M?hlfelder Salix OS: www.salixos.org From stanley at stanleygarvey.com Wed Jul 4 23:01:44 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 05 Jul 2012 00:01:44 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: <20120704194709.5f878127@pinkfloyd.tm-net> References: <1341409889.6777.YahooMailNeo@web29703.mail.ird.yahoo.com> <20120704194709.5f878127@pinkfloyd.tm-net> Message-ID: <20120704230145.2899736D9D36@bmail06.one.com> On Jul 4, 2012 18:47 "Thorsten M?hlfelder" wrote: > Am Wed, 4 Jul 2012 14:51:29 +0100 (BST) > schrieb Davide : > > > why the hell should one use flash for authentication on a web site > > (on some sites if you don't have flash you cannot even see the box > > for typing the authentication) ! > > I've never seen that and actually it's kind of funny nowadays. I guess > the webmaster does not want to have many users? :-D > The mobile phone/tablet market is growing every day and neither iOS > nor > recent Android is meant to run flash. > > > Flash is already dead. Its hulking corpse seemingly animated only by > > the inertia of its ubiquitous web presence. In a diverse client > > environment Adobe has lost their way. The Web works just fine with > > out flash. It's now down to content providers to provide content > > that does not require a proprietary plugin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sorin at spit-ct.ro Tue Jul 10 18:55:56 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Tue, 10 Jul 2012 21:55:56 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update Message-ID: <4FFC7ABC.60604@spit-ct.ro> Hello, On slackware-current I can not compile the kernel on my raspberry Pi anymore. Until and including Mon Jun 18 08:07:25 UTC 2012 changes in the slackware-current repository I recompiled the kernel several times with succes. With the changes that were made on Thu Jul 5 07:56:34 UTC 2012 in the repository I get an error at the end of the compilation: Inconsistent kallsyms data This is a bug - please report about it Try make KALLSYMS_EXTRA_PASS=1 as a workaround make: *** [vmlinux] Error 1 I tried to add KALLSYMS_EXTRA_PASS=1 but with no luck. Thanks in advance, Sorin Mitrica From gregg.drwho8 at gmail.com Tue Jul 10 18:58:37 2012 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 10 Jul 2012 14:58:37 -0400 Subject: [ARMedslack] Seagate Dockstar device questions Message-ID: Hello! Before I start doing something with this device and probably ruin it I have a question. Is this device completely supported by the ARM Slackware port? ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From brennan.newman at gmail.com Tue Jul 10 19:06:10 2012 From: brennan.newman at gmail.com (Brennan Newman) Date: Tue, 10 Jul 2012 14:06:10 -0500 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: In my experience, yes. You may have to update the uboot in it so it will boot off USB device. That is what I had to do to get my dockstar running On Jul 10, 2012 1:58 PM, "Gregg Levine" wrote: > Hello! > Before I start doing something with this device and probably ruin it I > have a question. > > Is this device completely supported by the ARM Slackware port? > > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Tue Jul 10 19:13:00 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Tue, 10 Jul 2012 20:13:00 +0100 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: On 10 July 2012 19:58, Gregg Levine wrote: > Is this device completely supported by the ARM Slackware port? I guess Stuart would say: "it's not a case of "porting" - it's just adding support". -- Ottavio From m-lists at biscuit.org.uk Tue Jul 10 19:50:01 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 10 Jul 2012 20:50:01 +0100 (BST) Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: > > Is this device completely supported by the ARM Slackware port? > > I guess Stuart would say: "it's not a case of "porting" - it's just > adding support". Not to answer *that* question I wouldn't. The dockstar is supported in the way that a kernel is supplied that runs on that device. Much to my disgust, someone on this list used one of those pointless devices ;-) See- http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org -- Stuart Winter Slackware ARM: www.armedslack.org From tylernt at gmail.com Tue Jul 10 19:00:58 2012 From: tylernt at gmail.com (Tyler T) Date: Tue, 10 Jul 2012 13:00:58 -0600 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: The Dockstar has an identical processor ("Kirkwood") to the SheevaPlug, which is supported. It takes some extra effort to "hack" the bootloader on the Dockstar, but once I had that sorted, running Slackware on my Dockstar was no problem. On Tue, Jul 10, 2012 at 12:58 PM, Gregg Levine wrote: > Hello! > Before I start doing something with this device and probably ruin it I > have a question. > > Is this device completely supported by the ARM Slackware port? > From m-lists at biscuit.org.uk Tue Jul 10 19:52:59 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 10 Jul 2012 20:52:59 +0100 (BST) Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFC7ABC.60604@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> Message-ID: > Until and including > Mon Jun 18 08:07:25 UTC 2012 changes in the slackware-current repository I If you're using -current you need to keep up to date -- this date is of an old batch. The latest batch has a toolchain upgrade and lots of other changes. From gregg.drwho8 at gmail.com Tue Jul 10 19:52:23 2012 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 10 Jul 2012 15:52:23 -0400 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: On Tue, Jul 10, 2012 at 3:50 PM, Stuart Winter wrote: > >> > Is this device completely supported by the ARM Slackware port? >> >> I guess Stuart would say: "it's not a case of "porting" - it's just >> adding support". > > Not to answer *that* question I wouldn't. > > The dockstar is supported in the way that a kernel is supplied that runs > on that device. > > Much to my disgust, someone on this list used one of those pointless > devices ;-) > See- > http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org > Hello! Okay, what about them bothers you? ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From brennan.newman at gmail.com Tue Jul 10 20:00:49 2012 From: brennan.newman at gmail.com (Brennan Newman) Date: Tue, 10 Jul 2012 15:00:49 -0500 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: No hardware clock, have to use ntp to sync the time. This is a problem if it is not connected to the "internet" On Tue, Jul 10, 2012 at 2:52 PM, Gregg Levine wrote: > On Tue, Jul 10, 2012 at 3:50 PM, Stuart Winter > wrote: > > > >> > Is this device completely supported by the ARM Slackware port? > >> > >> I guess Stuart would say: "it's not a case of "porting" - it's just > >> adding support". > > > > Not to answer *that* question I wouldn't. > > > > The dockstar is supported in the way that a kernel is supplied that runs > > on that device. > > > > Much to my disgust, someone on this list used one of those pointless > > devices ;-) > > See- > > > http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org > > > > Hello! > Okay, what about them bothers you? > > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > 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 Tue Jul 10 20:09:26 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 10 Jul 2012 21:09:26 +0100 (BST) Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: > Hello! > Okay, what about them bothers you? I always think about using the machines as either 'desktops' or build machines, so anything that is of low spec doesn't interest me at all - especially when there are better machines out there. The dockstar has no RTC and only 128MB RAM. IMO if you were going to spend any money on a Kirkwood machine, buy a SheevaPlug. More costly but it's *supposed* to be developed on so it's completely open (rather than sold as an appliance for a particular application and having to be hacked) and has 512MB RAM. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Tue Jul 10 20:28:15 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 10 Jul 2012 21:28:15 +0100 (BST) Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: References: <4FFC7ABC.60604@spit-ct.ro> Message-ID: > > Until and including > > Mon Jun 18 08:07:25 UTC 2012 changes in the slackware-current repository I > > If you're using -current you need to keep up to date -- this date is of an > old batch. > > The latest batch has a toolchain upgrade and lots of other changes. Aha I misread your post! This is common for Fedora, apparently: http://lists.fedoraproject.org/pipermail/arm/2012-March/003001.html Have a dig around and see whether there's a fix for it that Fedora have applied to their kernels. I must say that I've never come across this before when building the kernels for Slackware ARM. -- Stuart Winter Slackware ARM: www.armedslack.org From dhm at mersenne.com Tue Jul 10 20:16:34 2012 From: dhm at mersenne.com (David Madden) Date: Tue, 10 Jul 2012 13:16:34 -0700 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: <4FFC8DA2.5060300@mersenne.com> On 7/10/2012 13:09, Stuart Winter wrote: > so anything that is of low spec doesn't interest me at all - > especially when there are better machines out there. The Dockstar is such a cute form factor, though. Especially when you put one of the 2.5" drives in it. But you're right, only 128MB is painful. (Although I did have one running MySQL, Postgresql, Lighttpd, PHP, Gallery, Wordpress, git and Davical! But I recently moved all that stuff over to a GuruPlug because the image processing for Gallery was just painfully slow.) -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 From m-lists at biscuit.org.uk Tue Jul 10 20:54:02 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 10 Jul 2012 21:54:02 +0100 (BST) Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: References: <4FFC7ABC.60604@spit-ct.ro> Message-ID: > > > > The latest batch has a toolchain upgrade and lots of other changes. > > Aha I misread your post! > > This is common for Fedora, apparently: > > http://lists.fedoraproject.org/pipermail/arm/2012-March/003001.html > > Have a dig around and see whether there's a fix for it that Fedora have > applied to their kernels. I must say that I've never come across this > before when building the kernels for Slackware ARM. The previous gcc packages are here in case they turn out to be useful: http://armed.slackware.com/armedslack-current/reversions/d/gcc-4.7.1-1/ You should be able to downgrade to those and re-try the kernels. The gcc packages in the latest batch (Jul 5th) do have some new patches. There will be a gcc rebuild again in the next batch with the latest batch of upstream patches and bug fixes. -- Stuart Winter Slackware ARM: www.armedslack.org From gregg.drwho8 at gmail.com Tue Jul 10 20:57:49 2012 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 10 Jul 2012 16:57:49 -0400 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: <4FFC8DA2.5060300@mersenne.com> References: <4FFC8DA2.5060300@mersenne.com> Message-ID: On Tue, Jul 10, 2012 at 4:16 PM, David Madden wrote: > On 7/10/2012 13:09, Stuart Winter wrote: >> so anything that is of low spec doesn't interest me at all - >> especially when there are better machines out there. > > The Dockstar is such a cute form factor, though. Especially when you > put one of the 2.5" drives in it. But you're right, only 128MB is > painful. (Although I did have one running MySQL, Postgresql, Lighttpd, > PHP, Gallery, Wordpress, git and Davical! But I recently moved all that > stuff over to a GuruPlug because the image processing for Gallery was > just painfully slow.) > > -- > Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 > - Small Business, Startup and Intellectual Property Law - > 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack Hello! I agree folks. Really. I've already got a black Pogoplug here doing all of that with two drives attached. I originally wanted to track down of them (the Seagate Dockstar) about a year or so earlier, when there was talk of stuffing one of the others on it, OpenWRT in fact. That also included the serial port on the device which has its pins the front. Someone else had gotten the thing to talk to a screen via one those VGA to USB translation devices as well. But for me that platform is perfect for exploring the world of running Linux on non-Intel platforms. Oh and thank you Stuart for creating this port. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From richard.lapointe at gmail.com Tue Jul 10 21:39:31 2012 From: richard.lapointe at gmail.com (Rich) Date: Tue, 10 Jul 2012 17:39:31 -0400 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: Message-ID: <4FFCA113.2080104@laprjns.com> On 07/10/2012 03:50 PM, Stuart Winter wrote: >>> Is this device completely supported by the ARM Slackware port? >> I guess Stuart would say: "it's not a case of "porting" - it's just >> adding support". > Not to answer *that* question I wouldn't. > > The dockstar is supported in the way that a kernel is supplied that runs > on that device. > > Much to my disgust, someone on this list used one of those pointless > devices ;-) > See- > http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org Well you would be really discussed with me. I've got three Dockstars all running ARMedSlack 13.37. And to make it worst, I've got two Pogoplugs E02 running current. On all of these devices I loaded Jeff Doozan uboot, so no real problem with hacking the boot loader. Rich Lapointe From gregg.drwho8 at gmail.com Wed Jul 11 03:46:57 2012 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 10 Jul 2012 23:46:57 -0400 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: <4FFCA113.2080104@laprjns.com> References: <4FFCA113.2080104@laprjns.com> Message-ID: On Tue, Jul 10, 2012 at 5:39 PM, Rich wrote: > On 07/10/2012 03:50 PM, Stuart Winter wrote: >>>> >>>> Is this device completely supported by the ARM Slackware port? >>> >>> I guess Stuart would say: "it's not a case of "porting" - it's just >>> adding support". >> >> Not to answer *that* question I wouldn't. >> >> The dockstar is supported in the way that a kernel is supplied that runs >> on that device. >> >> Much to my disgust, someone on this list used one of those pointless >> devices ;-) >> See- >> >> http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org > > > Well you would be really discussed with me. I've got three Dockstars all > running ARMedSlack 13.37. And to make it worst, I've got two Pogoplugs E02 > running current. On all of these devices I loaded Jeff Doozan uboot, so no > real problem with hacking the boot loader. > > Rich Lapointe > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack Hello! Rich is this the article that you followed? http://projects.doozan.com/debian/ Granted he is talking about that cluster of Penguins in back of our group and slightly to the left of the router community. But for my efforts that one makes sense. I'm leaning towards putting a Slackware-13.37 system on it, but, ah, what space requirements should I take into consideration? ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From sorin at spit-ct.ro Wed Jul 11 05:21:59 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Wed, 11 Jul 2012 08:21:59 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: References: <4FFC7ABC.60604@spit-ct.ro> Message-ID: <4FFD0D77.9040200@spit-ct.ro> On 10.07.2012 23:54, Stuart Winter wrote: >>> The latest batch has a toolchain upgrade and lots of other changes. >> Aha I misread your post! >> >> This is common for Fedora, apparently: >> >> http://lists.fedoraproject.org/pipermail/arm/2012-March/003001.html >> >> Have a dig around and see whether there's a fix for it that Fedora have >> applied to their kernels. I must say that I've never come across this >> before when building the kernels for Slackware ARM. > The previous gcc packages are here in case they turn out to be useful: > http://armed.slackware.com/armedslack-current/reversions/d/gcc-4.7.1-1/ > > You should be able to downgrade to those and re-try the kernels. The gcc > packages in the latest batch (Jul 5th) do have some new patches. > There will be a gcc rebuild again in the next batch with the latest batch > of upstream patches and bug fixes. > Thanks ! I`ll let you know if it works in several hours when the compilation ends. From sorin at spit-ct.ro Wed Jul 11 05:31:07 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Wed, 11 Jul 2012 08:31:07 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFD0D77.9040200@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> Message-ID: <4FFD0F9B.5040204@spit-ct.ro> On 11.07.2012 08:21, Sorin Mitrica wrote: > On 10.07.2012 23:54, Stuart Winter wrote: >>>> The latest batch has a toolchain upgrade and lots of other changes. >>> Aha I misread your post! >>> >>> This is common for Fedora, apparently: >>> >>> http://lists.fedoraproject.org/pipermail/arm/2012-March/003001.html >>> >>> Have a dig around and see whether there's a fix for it that Fedora have >>> applied to their kernels. I must say that I've never come across >>> this >>> before when building the kernels for Slackware ARM. >> The previous gcc packages are here in case they turn out to be useful: >> http://armed.slackware.com/armedslack-current/reversions/d/gcc-4.7.1-1/ >> >> You should be able to downgrade to those and re-try the kernels. The >> gcc >> packages in the latest batch (Jul 5th) do have some new patches. >> There will be a gcc rebuild again in the next batch with the latest >> batch >> of upstream patches and bug fixes. >> > Thanks ! I`ll let you know if it works in several hours when the > compilation ends. > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Those reversions are actuallty the latest gcc packages in -current. Kernel compilation on the Pi worked with gcc-4.7.0, with 4.7.1 it gives me that error. From dhm at mersenne.com Wed Jul 11 04:00:12 2012 From: dhm at mersenne.com (David Madden) Date: Tue, 10 Jul 2012 21:00:12 -0700 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: <4FFCA113.2080104@laprjns.com> Message-ID: <4FFCFA4C.2030306@mersenne.com> On 7/10/2012 20:46, Gregg Levine wrote: > what space requirements should > I take into consideration? I spent a fair amount of time trying to put together a tiny system that would fit into the Flash on a Dockstar, but ended up with a more conventional installation (system on USB disk). More recently, I built a GuruPlug system to take over the Dockstar's duties, and was able to fit Linux-3.4.4, Apache, PHP, MySQL, PostgreSQL, and a fair amount of other stuff into the 507MB flash, with ... let's see ... almost 100MB left. (This is using a UBI compressed filesystem.) For the GuruPlug install, I started with Arch Linux, rather than Slackware. I'm not up on the politics of the various distros, but it seemed like Arch made it easier to pick & choose individual packages. I plan to rebuild the Dockstar after the GuruPlug has a few weeks to get the bugs shaken out, and I'll probably try to fit an Arch Linux installation into the 128MB flash. I doubt I can fit a complete LAMP setup, but I really only need NFS, CUPS and maybe a basic web server. You should make sure you can access the TTL-level serial port on the Dockstar before you get too fancy with it! -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 From m-lists at biscuit.org.uk Wed Jul 11 07:27:52 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 11 Jul 2012 08:27:52 +0100 (BST) Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFD0F9B.5040204@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> Message-ID: > Those reversions are actuallty the latest gcc packages in -current. Kernel > compilation on the Pi worked with gcc-4.7.0, with 4.7.1 it gives me that > error. Hehe. It all made sense yesterday in my lack of sleep induced alternate reality. So I have a newer gcc build on the dev boxes than the packages on the FTP site and I got confused about what "-current" was where. Given that I've compiled 3 kernels with that toolchain, I'd go down the patch route if I were you. I'll have some newer gcc packages nearer the end of the week that I can upload for test if you want, but to be honest I doubt they'll help. From axjslack at gmail.com Wed Jul 11 07:41:24 2012 From: axjslack at gmail.com (Alexjan Carraturo) Date: Wed, 11 Jul 2012 09:41:24 +0200 Subject: [ARMedslack] Cross Compiling Message-ID: Hi to all my name it's Alexjan, and I use Gnu/Linux O.S. on some evalution board with ARM Cpu (especially Cortex-A9). I have tried the Armedslack and seems to be a very interesting product. Works good, but for some thing may be needed some optimization (for example KDE). I see that there is a tool to compile "native" the packages, but now I'm wondering if there is the possibility to have (or realize) a Cross Compiler specifically that it's able to work with Slackbuilds of armedslack. I say that because I can access to a very powerful compiling workstation, and for me would be very useful to automatize the compilation process. For the moment I'm trying to follow the "procedure" on the README that is in the /source directory of Armedslack, but the download of source directory it's very slow. Thanks in advance for any advice and sorry for disturbing with my noising question. Bye Alexjan. -- Alexjan Carraturo -- Twitter/Facebook/Identica/flickr: axjslack Personal site: http://axjslack.wordpress.com -- From m-lists at biscuit.org.uk Wed Jul 11 08:42:51 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 11 Jul 2012 09:42:51 +0100 (BST) Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: > I have tried the Armedslack and seems to be a very interesting > product. Works good, but for some thing may be needed some > optimization (for example KDE). What optimisations are you hoping to add? The only way to optimise KDE that I know of are to turn off the "must have lots of graphical loviness" which used to be an possible in KDE3 but I haven't seen it in KDE4. > I see that there is a tool to compile "native" the packages, but now > I'm wondering if there is the possibility to have (or realize) a Cross > Compiler specifically that it's able to work with Slackbuilds of > armedslack. ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/ You need to run the 'x-build' script there run distcc on your x86 machine using commands from the 'rc.local-addition' script, and then use part of the 'dbuild' script on your ARM machine So do do a build of an armedslack package all I do is cd source/a/bash dbuild Obviously you have to have read the instructions first and configured everything. Have a look through the mail archives for this list as you're not the first to ask. From axjslack at gmail.com Wed Jul 11 09:00:16 2012 From: axjslack at gmail.com (Alexjan Carraturo) Date: Wed, 11 Jul 2012 11:00:16 +0200 Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: 2012/7/11 Stuart Winter : > >> I have tried the Armedslack and seems to be a very interesting >> product. Works good, but for some thing may be needed some >> optimization (for example KDE). > > What optimisations are you hoping to add? > > The only way to optimise KDE that I know of are to turn off the "must have > lots of graphical loviness" which used to be an possible in KDE3 but I > haven't seen it in KDE4. > There are a lot of possible optimization. >> I see that there is a tool to compile "native" the packages, but now >> I'm wondering if there is the possibility to have (or realize) a Cross >> Compiler specifically that it's able to work with Slackbuilds of >> armedslack. > > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/ > > You need to run the 'x-build' script there > run distcc on your x86 machine using commands from the 'rc.local-addition' > script, and then use part of the 'dbuild' script on your ARM machine > > So do do a build of an armedslack package all I do is > > cd source/a/bash > dbuild > > Obviously you have to have read the instructions first and configured > everything. > Ok. This instruction are very interesting, even if are talking about a thing that is different from what I'm looking for. Anyway I'll try to use it to implement what I really need. > Have a look through the mail archives for this list as you're not the > first to ask. > > > I did a manual search (looking on the archive of the last months), but I was unable to find. Thanks Alexjan. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- Alexjan Carraturo -- Twitter/Facebook/Identica/flickr: axjslack Personal site: http://axjslack.wordpress.com -- From panych.y at gmail.com Wed Jul 11 09:00:42 2012 From: panych.y at gmail.com (Yaroslav Panych) Date: Wed, 11 Jul 2012 12:00:42 +0300 Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: Hi 2012/7/11 Alexjan Carraturo : > I see that there is a tool to compile "native" the packages, but now > I'm wondering if there is the possibility to have (or realize) a Cross > Compiler specifically that it's able to work with Slackbuilds of > armedslack. Yes, it is possible to Cross Compile Armedslack, and I believe Armedslack-team does ti for most packages, but there is some problem: some software packages no suitable to be cross-compiled, and it is required to change Makefiles manually, so crosscompilation can fail. I am not Armedslack user yet, so I can only recommend you to read here http://www.armedslack.org/doku.php?id=faqs (follow sublinks, probably it can give you some answers. regards, Yaroslav From m-lists at biscuit.org.uk Wed Jul 11 09:06:53 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 11 Jul 2012 10:06:53 +0100 (BST) Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: > > lots of graphical loviness" which used to be an possible in KDE3 but I > > haven't seen it in KDE4. > > > > There are a lot of possible optimization. Are there any that can be applied to the packages in Slackware ARM? Not KDE application specific tweaks, but compilation flags. > > > > Ok. This instruction are very interesting, even if are talking about a > thing that is different from what I'm looking for. Anyway I'll try to > use it to implement what I really need. If you want to do proper cross compiling then no, but if you wanted to use the armedslack build scripts it'd not be that hard since you could install slackkit on an x86 and use a cross compiler, but you'll need to figure that out. From axjslack at gmail.com Wed Jul 11 09:15:54 2012 From: axjslack at gmail.com (Alexjan Carraturo) Date: Wed, 11 Jul 2012 11:15:54 +0200 Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: 2012/7/11 Stuart Winter : >> > lots of graphical loviness" which used to be an possible in KDE3 but I >> > haven't seen it in KDE4. >> > >> >> There are a lot of possible optimization. > > Are there any that can be applied to the packages in Slackware ARM? Not > KDE application specific tweaks, but compilation flags. > Yes, there are. I don't know if are usable on Slackware ARM port ( I still don't test anything, but In other distribution, e.g. Fedora, Debian works with good result. >> > >> >> Ok. This instruction are very interesting, even if are talking about a >> thing that is different from what I'm looking for. Anyway I'll try to >> use it to implement what I really need. > > If you want to do proper cross compiling then no, but if you wanted to use > the armedslack build scripts it'd not be that hard since you could > install slackkit on an x86 and use a cross compiler, but you'll need to figure that out. > Ok, this is what I'm talking about. Now I'm doing a "feasibility study", considering various part of Armedslack project, to evaluate if it's possibile to do a port for a specific SoC. Thanks for informations Alexjan. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- Alexjan Carraturo -- Twitter/Facebook/Identica/flickr: axjslack Personal site: http://axjslack.wordpress.com -- From axjslack at gmail.com Wed Jul 11 09:22:16 2012 From: axjslack at gmail.com (Alexjan Carraturo) Date: Wed, 11 Jul 2012 11:22:16 +0200 Subject: [ARMedslack] Cross Compiling In-Reply-To: References: Message-ID: 2012/7/11 Yaroslav Panych : > Hi > > 2012/7/11 Alexjan Carraturo : >> I see that there is a tool to compile "native" the packages, but now >> I'm wondering if there is the possibility to have (or realize) a Cross >> Compiler specifically that it's able to work with Slackbuilds of >> armedslack. > > Yes, it is possible to Cross Compile Armedslack, and I believe > Armedslack-team does ti for most packages, but there is some problem: > some software packages no suitable to be cross-compiled, and it is > required to change Makefiles manually, so crosscompilation can fail. > I am not Armedslack user yet, so I can only recommend you to read here > http://www.armedslack.org/doku.php?id=faqs (follow sublinks, probably > it can give you some answers. > > regards, Yaroslav Thanks for the link.... there give a complete answer about my question (that is quite similar to Stuart's answer). Sorry for disturbing, I would have to read there before. Thank you and bye Alexjan -- Alexjan Carraturo -- Twitter/Facebook/Identica/flickr: axjslack Personal site: http://axjslack.wordpress.com -- From louigi600 at yahoo.it Wed Jul 11 10:45:21 2012 From: louigi600 at yahoo.it (Davide) Date: Wed, 11 Jul 2012 11:45:21 +0100 (BST) Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: <4FFCFA4C.2030306@mersenne.com> References: <4FFCA113.2080104@laprjns.com> <4FFCFA4C.2030306@mersenne.com> Message-ID: <1342003521.19096.YahooMailNeo@web29704.mail.ird.yahoo.com> I had a slimmed version of the mini root working on the dockstar (that initially ran on an external usb flashdisk untill I slimmed it enough to fit in the docstar) ... but I subsequently spent a lot of time on an old project I had back 2004 (Clash). Currently my dosckstar runs on that but if you need new kernel feautres the project has been dormant since I changed job, so you might like to look for a kernel elsewhere. Anyway, being a slackware enthusiast, I did my best to leave a slackware feeling to ClashNG while keeping things in a fairly small footprint. All the work I did is on sourceforge (bclash.sourceforge.net) Regards David ________________________________ Da: David Madden A: Slackware ARM port Inviato: Mercoled? 11 Luglio 2012 5:00 Oggetto: Re: [ARMedslack] Seagate Dockstar device questions On 7/10/2012 20:46, Gregg Levine wrote: > what space requirements should > I take into consideration? I spent a fair amount of time trying to put together a tiny system that would fit into the Flash on a Dockstar, but ended up with a more conventional installation (system on USB disk).? More recently, I built a GuruPlug system to take over the Dockstar's duties, and was able to fit Linux-3.4.4, Apache, PHP, MySQL, PostgreSQL, and a fair amount of other stuff into the 507MB flash, with ... let's see ... almost 100MB left.? (This is using a UBI compressed filesystem.) For the GuruPlug install, I started with Arch Linux, rather than Slackware.? I'm not up on the politics of the various distros, but it seemed like Arch made it easier to pick & choose individual packages. I plan to rebuild the Dockstar after the GuruPlug has a few weeks to get the bugs shaken out, and I'll probably try to fit an Arch Linux installation into the 128MB flash.? I doubt I can fit a complete LAMP setup, but I really only need NFS, CUPS and maybe a basic web server. You should make sure you can access the TTL-level serial port on the Dockstar before you get too fancy with it! -- Mersenne Law LLC? ?? www.mersenne.com? ?? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon? 97201 _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From sorin at spit-ct.ro Wed Jul 11 19:25:14 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Wed, 11 Jul 2012 22:25:14 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> Message-ID: <4FFDD31A.6090105@spit-ct.ro> On 11.07.2012 10:27, Stuart Winter wrote: >> Those reversions are actuallty the latest gcc packages in -current. Kernel >> compilation on the Pi worked with gcc-4.7.0, with 4.7.1 it gives me that >> error. > Hehe. It all made sense yesterday in my lack of sleep induced alternate > reality. > > So I have a newer gcc build on the dev boxes than the packages on the > FTP site and I got confused about what "-current" was where. > > Given that I've compiled 3 kernels with that toolchain, I'd go down the > patch route if I were you. I'll have some newer gcc packages nearer the > end of the week that I can upload for test if you want, but to be honest I > doubt they'll help. > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Please upload those newer gcc packages. It seems there is a bug in the toolchain. I downloaded again the sources for the kernel from the git hub, removed all packages from d/ and glibc , cleaned everything, reinstalled all the packages that I removed earlier but the error still persists. Thanks in advance, Sorin From galen.dp at gmail.com Wed Jul 11 22:22:29 2012 From: galen.dp at gmail.com (Doug Peterson) Date: Wed, 11 Jul 2012 16:22:29 -0600 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <1340264628.2459.17.camel@rick.miles.home> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340262346.2459.3.camel@rick.miles.home> <1340263256.65915.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340264628.2459.17.camel@rick.miles.home> Message-ID: Hi all, I just wanted to say thank you for all the reply's I received. I also want to apologies for not replying. The same day I first posted my questions about ArmedSlack on the Raspberry Pi, a loved one ended up in the hospital with ARDS. I have not had much time to catch up on things like this. He is now starting to do better, so I am turning back to this stuff. -Doug From galen.dp at gmail.com Wed Jul 11 22:43:33 2012 From: galen.dp at gmail.com (Doug Peterson) Date: Wed, 11 Jul 2012 16:43:33 -0600 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <20120621004250.2939D6E5EB587@bmail04.one.com> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> <20120621004250.2939D6E5EB587@bmail04.one.com> Message-ID: Thank you. I am rsyncing this now. Will give it a try. -Doug On Wed, Jun 20, 2012 at 6:42 PM, stanley garvey wrote: > On Jun 20, 2012 09:07 "Stuart Winter" wrote: > I have an 8gb img > Get it via: > rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . > This is the whole armed slack for an 8 GB sd sandisk card sans KDE. > Sorry it's not zipped, it is very late. instructions: > dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card > (most likley sdc) check with mount! don't wipe your hard drive. > see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry > For a listing os the other files.\good night :) > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From richard.lapointe at gmail.com Thu Jul 12 01:15:25 2012 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Wed, 11 Jul 2012 21:15:25 -0400 Subject: [ARMedslack] Seagate Dockstar device questions In-Reply-To: References: <4FFCA113.2080104@laprjns.com> Message-ID: <4FFE252D.7040402@laprjns.com> On 07/10/2012 11:46 PM, Gregg Levine wrote: > On Tue, Jul 10, 2012 at 5:39 PM, Rich wrote: >> On 07/10/2012 03:50 PM, Stuart Winter wrote: >>>>> Is this device completely supported by the ARM Slackware port? >>>> I guess Stuart would say: "it's not a case of "porting" - it's just >>>> adding support". >>> Not to answer *that* question I wouldn't. >>> >>> The dockstar is supported in the way that a kernel is supplied that runs >>> on that device. >>> >>> Much to my disgust, someone on this list used one of those pointless >>> devices ;-) >>> See- >>> >>> http://www.mail-archive.com/search?q=dockstar&l=armedslack%40lists.armedslack.org >> Well you would be really disgusted with me. I've got three Dockstars all >> running ARMedSlack 13.37. And to make it worst, I've got two Pogoplugs E02 >> running current. On all of these devices I loaded Jeff Doozan uboot, so no >> real problem with hacking the boot loader. >> >> Rich Lapointe >> >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! > Rich is this the article that you followed?http://projects.doozan.com/debian/ Yes, but I don't use the Debian install. I use the uboot installation instructions that are linked to in the first line of your reference link. Here the direct link. http://projects.doozan.com/uboot/. The uboot that this installs was recently updated to work with kernels 3.1 and greater. I also installed Jeff's Rescue System, http://forum.doozan.com/read.php?4,7915. I find it easier to use for installing ARMedSlack than stock firmware. > Granted he is talking about that cluster of Penguins in back of our > group and slightly to the left of he router community. But for my > efforts that one makes sense. I'm leaning towards putting a > Slackware-13.37 system on it, but, ah, what space requirements should > I take into consideration? I use USB hard drives (anywhere between 80G to 600G) with all my Dockstars and Pogoplugs, so i don't have to worry about space requirements. I recall installing on a 4 G flash drive without problems. My general partition scheme is as follows: sda1 / ext3 ( can be anywhere between 2 to 20 G) sda2 swap (i still follow the old rule of thumb of 2x ram) sda3 /home ext4 (size depends on what i planning to do with it) sda4 - logical disk to take up the reaming disk space if any In order not to have to screw with the uboot variables, the root file systems needs to be on sda1. Although most instruction indicate the the root files system need to be ext2, ext3 works fine. To install ARMedSlack I just untar the mini root file system in sda1, edit fstab to work with the partitioning scheme and add the following sym links to /boot ln -s uinitrd-kirkwood uInitrd ln -s uImage-kirkwood uImage As Stuart said your going to need to to install ntp and make the appropriate changes in ntp.conf. The network is setup to run dhcp, but I suggest that you set up a static ip so that you will not have to hunt for the ip address to ssh in after the first boot. Rich Lapointe > ----- > Gregg C Levinegregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." From m-lists at biscuit.org.uk Thu Jul 12 11:31:35 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 12 Jul 2012 12:31:35 +0100 (BST) Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFDD31A.6090105@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> <4FFDD31A.6090105@spit-ct.ro> Message-ID: > Please upload those newer gcc packages. It seems there is a bug in the > toolchain. I downloaded again the sources for the kernel from the git hub, > removed all packages from d/ and glibc , cleaned everything, reinstalled all > the packages that I removed earlier but the error still persists. http://armed.slackware.com/armedslack-current/test/d/ Try these. I only built them yesterday and have compiled just one package with them. Once I have some time, I'll give building a kernel a go. From sorin at spit-ct.ro Thu Jul 12 11:37:38 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Thu, 12 Jul 2012 14:37:38 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> <4FFDD31A.6090105@spit-ct.ro> Message-ID: <4FFEB702.2070704@spit-ct.ro> On 12-07-2012 2:31 PM, Stuart Winter wrote: >> Please upload those newer gcc packages. It seems there is a bug in the >> toolchain. I downloaded again the sources for the kernel from the git hub, >> removed all packages from d/ and glibc , cleaned everything, reinstalled all >> the packages that I removed earlier but the error still persists. > http://armed.slackware.com/armedslack-current/test/d/ > > Try these. I only built them yesterday and have compiled just one > package with them. > > Once I have some time, I'll give building a kernel a go. > > Thank you ! I`m building vmlinux now with the new gcc package. Let`s see... From stanley at stanleygarvey.com Thu Jul 12 14:34:45 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 12 Jul 2012 15:34:45 +0100 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: References: <20120621004250.2939D6E5EB587@bmail04.one.com> Message-ID: <20120712143446.4DC2CD8B0C87F@bmail-n01.one.com> On Jul 11, 2012 23:43 "Doug Peterson" wrote: > Thank you. I am rsyncing this now. Will give it a try. > > -Doug > > > On Wed, Jun 20, 2012 at 6:42 PM, stanley garvey > wrote: > > > I have an 8gb img > > Get it via: > > rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . > > This is the whole armed slack for an 8 GB sd sandisk card sans KDE. > > Sorry it's not zipped, it is very late. instructions: > > dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card > > (most likley sdc) check with mount! don't wipe your hard drive. > > see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry > > > > Thanks for trying it out Doug. > > Please replace or edit the file /etc/fstab with : > > > > /dev/mmcblk0p3 swap swap defaults 0 0 > > /dev/mmcblk0p2 / ext4 defaults 1 0 > > /dev/mmcblk0p1 /boot vfat defaults 0 0 > > #/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0 > > #/dev/fd0 /mnt/floppy auto noauto,owner 0 0 > > devpts /dev/pts devpts gid=5,mode=620 0 0 > > proc /proc proc defaults 0 0 > > tmpfs /dev/shm tmpfs defaults 0 0 > > > > I messed up and forgot to change this file in the image, oddly the > > pi boots with an incorrect /etc/fstab anyhow. > > Some Caveats. the boot will stop with an annoying message regarding > > the root file system being RW, just continue by hitting enter. You > > can hack the script /etc/rc.d/rc.S if you like, I chose not to. > > The Pi has no real time clock and starting the ntp daemon does not > > set the time, the ntpdate command will set the time example: > > ntpdate ntp.stanleygarvey.co.uk > > I have not investigated why this occurs. > > > > I did not think that there was much interest in the image and so had > > not updated it. I have a couple of slackbuilds that I will upload, > > this weekend: > > A script by Hexxeh to update the raspberry pi kernel and firmware > > also two librarys to enable the use of the hardware accelerated > > video player 'omxplayer'. > > Let me know how you get along. > > Regards > > Stanley > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sorin at spit-ct.ro Thu Jul 12 14:53:54 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Thu, 12 Jul 2012 17:53:54 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFEB702.2070704@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> <4FFDD31A.6090105@spit-ct.ro> <4FFEB702.2070704@spit-ct.ro> Message-ID: <4FFEE502.5070009@spit-ct.ro> On 12-07-2012 2:37 PM, Sorin Mitrica wrote: > On 12-07-2012 2:31 PM, Stuart Winter wrote: >>> Please upload those newer gcc packages. It seems there is a bug in the >>> toolchain. I downloaded again the sources for the kernel from the >>> git hub, >>> removed all packages from d/ and glibc , cleaned everything, >>> reinstalled all >>> the packages that I removed earlier but the error still persists. >> http://armed.slackware.com/armedslack-current/test/d/ >> >> Try these. I only built them yesterday and have compiled just one >> package with them. >> >> Once I have some time, I'll give building a kernel a go. >> >> > > Thank you ! > > I`m building vmlinux now with the new gcc package. Let`s see... > _______________________________________________ Same error, I reverted to gcc-4.5.2-arm-3.tgz from -13.37. I`ll have another run. From sorin at spit-ct.ro Fri Jul 13 06:20:19 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Fri, 13 Jul 2012 09:20:19 +0300 Subject: [ARMedslack] Error compiling kernel on raspberry pi since latest changelog update In-Reply-To: <4FFEE502.5070009@spit-ct.ro> References: <4FFC7ABC.60604@spit-ct.ro> <4FFD0D77.9040200@spit-ct.ro> <4FFD0F9B.5040204@spit-ct.ro> <4FFDD31A.6090105@spit-ct.ro> <4FFEB702.2070704@spit-ct.ro> <4FFEE502.5070009@spit-ct.ro> Message-ID: <4FFFBE23.1070204@spit-ct.ro> On 12-07-2012 5:53 PM, Sorin Mitrica wrote: > On 12-07-2012 2:37 PM, Sorin Mitrica wrote: >> On 12-07-2012 2:31 PM, Stuart Winter wrote: >>>> Please upload those newer gcc packages. It seems there is a bug in the >>>> toolchain. I downloaded again the sources for the kernel from the >>>> git hub, >>>> removed all packages from d/ and glibc , cleaned everything, >>>> reinstalled all >>>> the packages that I removed earlier but the error still persists. >>> http://armed.slackware.com/armedslack-current/test/d/ >>> >>> Try these. I only built them yesterday and have compiled just one >>> package with them. >>> >>> Once I have some time, I'll give building a kernel a go. >>> >>> >> >> Thank you ! >> >> I`m building vmlinux now with the new gcc package. Let`s see... >> _______________________________________________ > > Same error, I reverted to gcc-4.5.2-arm-3.tgz from -13.37. I`ll have > another run. > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > I even reverted to kernel-headers and glibc from 13.37 but won`t compile, same error. I`ll start from scratch with the latest current rootfs tonight and see what happens. From louigi600 at yahoo.it Mon Jul 16 05:53:30 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 16 Jul 2012 06:53:30 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: <1342418010.74921.YahooMailNeo@web29702.mail.ird.yahoo.com> >> What else could it be ? >Dunno but you can try with the new -current updates once I push them out >this week. Last Saturday I did an update yo current again but I still can't get libflashplayer to load on firefox. Maybe I'm missing something else that's not showing as error when firefox loads plugins. Can you give me the output of "ls /var/log/pasckages" on the system where you got libflashplayer to work ? Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jul 16 13:50:16 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 16 Jul 2012 14:50:16 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1342418010.74921.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> <1342418010.74921.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: > > Last Saturday I did an update yo current again but I still can't get libflashplayer to load on firefox. > Maybe I'm missing something else that's not showing as error when firefox loads plugins. > Can you give me the output of "ls /var/log/pasckages" on the system where you got libflashplayer to work ? It's a full installation minus kdei. I've got to finish up some other packages before reinstalling my dev box again, then I'll try and see if it still works -- I suspect it does. I'm guessing that your system is missing a feature that this library wants to use. From louigi600 at yahoo.it Mon Jul 16 17:42:00 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 16 Jul 2012 18:42:00 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341128534.31359.YahooMailNeo@web29701.mail.ird.yahoo.com> <1341212364.75292.YahooMailNeo@web29706.mail.ird.yahoo.com> <1341214325.40436.YahooMailNeo@web29704.mail.ird.yahoo.com> <1342418010.74921.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: <1342460520.40906.YahooMailNeo@web29705.mail.ird.yahoo.com> >>> Last Saturday I did an update yo current again but I still can't get libflashplayer to load on firefox. >>> Maybe I'm missing something else that's not showing as error when firefox loads plugins. >>> Can you give me the output of "ls /var/log/pasckages" on the system where you got libflashplayer to work ? >>It's a full installation minus kdei. >>I've got to finish up some other packages before reinstalling my dev box >>again, then I'll try and see if it still works -- I suspect it does. >>I'm guessing that your system is missing a feature that this library wants >>to use. >I suspect that too but the thing that's bothering me on this thought is that I can't get firefox to tell me that it cannot load the library >and maybe give me a hint as to why. >Maybe it's a several level nested library dep. and that's the reason it's not showing ... but my slack installations? install all the >suggested packages in the "l" section just to avoid this sort of problem. >I forgot if I did something different on my AC100 but I can fix that with "slackpkg install l". Since I could not get any responce from firefox i tryed strace ... so here is a grep of flash form the putput of strace: lstat64("/usr/lib/firefox-13.0.1/plugins/libflashplayer.so", {st_mode=S_IFLNK|0777, st_size=31, ...}) = 0 readlink("/usr/lib/firefox-13.0.1/plugins/libflashplayer.so", "../../plugins/libflashplayer.so"..., 4095) = 31 lstat64("/usr/lib/plugins/libflashplayer.so", {st_mode=S_IFREG|0755, st_size=8016428, ...}) = 0 stat64("/usr/lib/plugins/libflashplayer.so", {st_mode=S_IFREG|0755, st_size=8016428, ...}) = 0that does not look bad to me ... but maybe I'm mistaken ? Now here's a grep of opens that return -1 : openat(AT_FDCWD, "/usr/lib/firefox-13.0.1/distribution/bundles", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/charset.alias", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/messages.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/messages.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/gtk20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/gtk20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/gtk20-properties.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/gtk20-properties.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib/tls/v7l/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/tls/v7l/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/tls/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/tls/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/v7l/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/v7l/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/tls/v7l/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/tls/v7l/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/tls/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/tls/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/v7l/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/v7l/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/vfp/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/libgnomeui-2.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/firefox-13.0.1/updates/0/update.status", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/gconv/gconv-modules.cache", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/pango/pangorc", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/root/.pangorc", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/root/.icons/default/cursors/xterm", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.icons/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/default/cursors/xterm", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/pixmaps/default/cursors/xterm", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/pixmaps/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/firefox-13.0.1/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}/chrome.manifest", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/glib20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/glib20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/icon-theme.cache", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/pixmaps/icon-theme.cache", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/local/share//mime/aliases", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/local/share//mime/subclasses", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/local/share//mime/icons", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/local/share//mime/generic-icons", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/gdk-pixbuf.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/gdk-pixbuf.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.Xdefaults-slackware", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.icons/default/cursors/left_ptr", O_RDONLY) = -1 ENOENT (No such file or directory) open("/root/.icons/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/default/cursors/left_ptr", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/icons/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/pixmaps/default/cursors/left_ptr", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/pixmaps/default/index.theme", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib/libcanberra.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/libcanberra.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/lib/libcanberra.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib/libcanberra.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/root/.mozilla/firefox/yup11s77.default/prefs.js", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_LARGEFILE, 0644) = -1 EEXIST (File exists) open("/root/.mozilla/firefox/yup11s77.default/prefs.js", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_LARGEFILE, 0644) = -1 EEXIST (File exists) open("/root/.mozilla/firefox/yup11s77.default/localstore.rdf", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_LARGEFILE, 0644) = -1 EEXIST (File exists) The stuff in root's home, /usr/share/, gnome I suspect being harmless as I guess pretty much nobody uses gnome on any slackware version ... so tha leaves me with very few things missin that I've no idea if they are mandatory ro flash: /lib/libcanberra.so.0 /usr/lib/libcanberra.so.0 /lib/libcanberra.so.0 I did a 3 leven ldd search for libraries neaded by flash and I did not spot any "not found" ... so I've no clue as to what's going wrong. Anyone know if these are required for flash ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From mag-one at autistici.org Thu Jul 19 13:52:28 2012 From: mag-one at autistici.org (Gabbroral Complex) Date: Thu, 19 Jul 2012 13:52:28 +0000 Subject: [ARMedslack] d2plug Message-ID: hi, has anyone had success installing armedslack on a D2PLUG device? I'm trying to boot but the kernel hangs after the image's uncompress. please can anyone help me? tanx, m.