From m-lists at biscuit.org.uk Sat Jun 1 07:43:57 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 1 Jun 2013 08:43:57 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: > > There's probably something wrong with me or with my browser or some other > dumb thing ... but I recognize a menu that's resembles remotely what used > to be on tosh-ac100 ... but I looked on every element of the menu and could > not recognise my armedslack (it was not slackware arm at the time) howto > ... well if you can see the text save it somewhere. > > I'm not interested in the layout ... just the text. I'll fix it up and > find another place to host it. I changed the URL on http://arm.slackware.com/supportedplatforms/ Once you've found somewhere else to host it, let me know. From ottavio2006-usenet2012 at yahoo.com Sat Jun 1 08:53:17 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sat, 1 Jun 2013 09:53:17 +0100 Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On 1 June 2013 08:43, Stuart Winter wrote: > > I changed the URL on http://arm.slackware.com/supportedplatforms/ > Once you've found somewhere else to host it, let me know. A cached copy is here: http://web.archive.org/web/20120719012735/http://tosh-ac100.wetpaint.com/page/ARMedslack Davide, make sure you save it and move it somewhere else safe. -- Ottavio From stanley at stanleygarvey.com Sat Jun 1 19:39:40 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 01 Jun 2013 20:39:40 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> Message-ID: <20130601193940.448EB966CB2DB@bmail04.one.com> On May 30, 2013 08:34 wrote: > > > > Hi > > > > > > Since Slackware 14.1 is coming together, could all of you who > > plan on preparing and distributing support for Slackware ARM > > 14.1 for the RaspberryPi please reply to this message (on-list) with > > the > > following information. I will collate it and put it into the > > /INSTALL_RASPBERRYPI.TXT document within the release. > > > > Note that this is *only* for those of you who are supplying > > images/installers that contain the _official_ Slackware ARM packages > > which > > will be taken from > > ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1. > > > > 1. The URL of the web site containing information about your > > distribution. > > > > 2. Installation method: regular installer / pre-supplied image(s) > > > > If it's a pre-supplied image, what categories of software are > > included: > > > > Don't list every package, but a high level brief description such > > as: > > > > dev tools ('d') > > > > - Compilers and toolchain tools > > - Python, Perl > > > > X11 ('x') > > > > - X packages relevant to the Rpi > > > > KDE ('kde') > > - All of KDE > > - Base components of KDE > > > > > > 3. RPi boards / versions of boards that your distribution has been > > tested with and confirmed operational. > > > > 4. The particular reason for choosing yours over another. Some of > > the > > reasons that some people have created their own image is because > > Dave > > Spencer's work stopped at 13.37, or theirs addressed particular > > problems on certain boards. > > > > Please note that this shouldn't be a reason for the 14.1 release - > > you should treat this as new rather than a patch to someone else's > > work (even > > if that's what it started out as). > > > > > > Deadline: > > --------- > > > > I'll stop taking submissions at the release of RC1 of Slackware 14.1 > > x86. > > > > Any questions - please ask! > > > > Cheers > > Stuart. > > > > > > -- > > Stuart Winter > > > > Slackware for ARM: > > _______________________________________________ > > ARMedslack mailing list > > > > > > > Hi Stuart > Judging by the avalanche of submissions, it would look I am alone in > supporting Slackware on the RPi - ( Hello! - cue hall type reverb and > tumbleweed). > However my site gets two or three hits a day regarding slackberry, so > somebody's interested. > The issue with udev renaming eth0 to eth1 is documented on the site. I > need to fix this but given to udevs labariynthine nature I may require > a ball of string. I may be some time. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sat Jun 1 21:16:25 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 1 Jun 2013 22:16:25 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> >> I changed the URL on http://arm.slackware.com/supportedplatforms/ >> Once you've found somewhere else to host it, let me know. > >A cached copy is here: >http://web.archive.org/web/20120719012735/http://tosh-ac100.wetpaint.com/page/ARMedslack > >Davide, make sure you save it and move it somewhere else safe. Ok that works and I was able to salvage the text . This time I'll keep a copy for myself ;-) I'll see where's the safest place to save it ... possibly adding a section here http://ac100.grandou.net/installing_linux might be a good place. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Sun Jun 2 10:09:17 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Sun, 2 Jun 2013 06:09:17 -0400 (EDT) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130601193940.448EB966CB2DB@bmail04.one.com> References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> Message-ID: <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> From: stanley garvey To: Slackware ARM port ; stanley Sent: Sat, Jun 1, 2013 8:39 pm Subject: Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 On May 30, 2013 08:34 stanley at stanleygarvey.com wrote: Hi Since Slackware 14.1 is coming together, could all of you who plan on preparing and distributing support for Slackware ARM 14.1 for the RaspberryPi please reply to this message (on-list) with the following information. I will collate it and put it into the /INSTALL_RASPBERRYPI.TXT document within the release. Note that this is *only* for those of you who are supplying images/installers that contain the _official_ Slackware ARM packages which will be taken from ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1. 1. The URL of the web site containing information about your distribution. 2. Installation method: regular installer / pre-supplied image(s) If it's a pre-supplied image, what categories of software are included: Don't list every package, but a high level brief description such as: dev tools ('d') - Compilers and toolchain tools - Python, Perl X11 ('x') - X packages relevant to the Rpi KDE ('kde') - All of KDE - Base components of KDE 3. RPi boards / versions of boards that your distribution has been tested with and confirmed operational. 4. The particular reason for choosing yours over another. Some of the reasons that some people have created their own image is because Dave Spencer's work stopped at 13.37, or theirs addressed particular problems on certain boards. Please note that this shouldn't be a reason for the 14.1 release - you should treat this as new rather than a patch to someone else's work (even if that's what it started out as). Deadline: --------- I'll stop taking submissions at the release of RC1 of Slackware 14.1 x86. Any questions - please ask! Cheers Stuart. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi Stuart Judging by the avalanche of submissions, it would look I am alone in supporting Slackware on the RPi - ( Hello! - cue hall type reverb and tumbleweed). However my site gets two or three hits a day regarding slackberry, so somebody's interested. The issue with udev renaming eth0 to eth1 is documented on the site. I need to fix this but given to udevs labariynthine nature I may require a ball of string. I may be some time. Hi Stanley, I got rid of the problem of eth0 -> eth1 udev renaming on the images I create by using the slackware supported standard /etc/rc.d/rc.shutdown_local script to remove the 70-persistent-net.rules file whenever a shutdown is run. I use it for a whole load of other stuff as well, but removing it on shutdown makes the images I create portable across boxes. I'll chip in on the providing stuff where I have something to offer, but whatever I chip in will be additions to the standard slackware stuff (I prefer to keep the appliances I create as standard as possible and just add stuff to it). I can't help wondering if what we really need for all of these community supported platforms is one standard site (maybe a subdomain from slackwarearm), done like a wiki type site, where each community supported platform can have it's own section, and those who contribute can sign up to have editing/uploading permissions. I have webspace, and bandwidth I can donate to that, but I don't have the time to setup and run such a site. _______________________________________________ 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 Sun Jun 2 19:13:13 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 2 Jun 2013 20:13:13 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> Message-ID: > I can't help wondering if what we really need for all of these community > supported platforms is one standard site (maybe a subdomain from > slackwarearm), done like a wiki type site, where each community > supported platform can have it's own section, and those who contribute > can sign up to have editing/uploading permissions. I have webspace, and > bandwidth I can donate to that, but I don't have the time to setup and > run such a site. This has occurred to me as well, but so far I've kept out of suggesting any structure for the RPi support (initially to see how it'd pan out). Perhaps a better approach would be to host the RPi page on http://docs.slackware.com and link to the externally hosted downloads from there. The issue I see, going forwards, is that support is fragmented. Somebody finds that doesn't work, so instead of suggesting/supplying a fix to the author of the work they were using, they start their own version which has additional issues. Does anybody want to be the lead owner of a RPi page on docs.slackware.com (assuming we can put it on there -- I have no input in to that site so have not yet checked whether we can (although I can't imagine why not!)). Ideally there'd be a single Rpi installer and/or image available that has all of the fixes rolled up into it. In the typical model for this type of thing (given that it's a binary blob of an image/installer image), the project owner essentially becomes the gate keeper so has to be able to dedicate some time to folding requests and fixes back in to the distributed images. Thoughts? Any takers? -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Mon Jun 3 08:32:11 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 3 Jun 2013 09:32:11 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> >>> I changed the URL on http://arm.slackware.com/supportedplatforms/ >>> Once you've found somewhere else to host it, let me know. >> >>A cached copy is here: >>http://web.archive.org/web/20120719012735/http://tosh-ac100.wetpaint.com/page/ARMedslack >> >>Davide, make sure you save it and move it somewhere else safe. > >Ok that works and I was able to salvage the text . This time I'll keep a copy for myself ;-) >I'll see where's the safest place to save it ... possibly adding a section here http://ac100.grandou.net/installing_linux might be a good place. > Would http://docs.slackware.com or http://slackwiki.com be a good place to put this in ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jun 3 11:05:36 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 3 Jun 2013 12:05:36 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: > > Would http://docs.slackware.com or http://slackwiki.com be a good place > to put this in ? Regards David docs.slackware.com is the best place, IMO. alienBOB is keen to have more docs there! :-) From louigi600 at yahoo.it Mon Jun 3 16:00:03 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 3 Jun 2013 17:00:03 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> >> >> Would http://docs.slackware.com or http://slackwiki.com be a good place >> to put this in ? Regards David > >docs.slackware.com is the best place, IMO. alienBOB is keen to have more >docs there! :-) http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az It was just a quick cut and paste with minor changes. I'll work on it to make it better and all comments are welcome. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jun 3 18:12:49 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 3 Jun 2013 19:12:49 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: > http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az > > It was just a quick cut and paste with minor changes. > I'll work on it to make it better and all comments are welcome. Would a separate ARM section be a good idea? It'd make content easier to find although it may break up the structure of the site a little bit. -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Tue Jun 4 06:50:02 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 4 Jun 2013 07:50:02 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> >> http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az >> >> It was just a quick cut and paste with minor changes. >> I'll work on it to make it better and all comments are welcome. > >Would a separate ARM section be a good idea?? It'd make content easier to >find although it may break up the structure of the site a little bit. Eric suggested that that would be a good place to start from so I took his advice .... but if we gather up all the ARM specific stuff together it would be nice too. Well whatever ... I'll be a good lamb and follow the flock :-D Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Jun 4 06:56:33 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 4 Jun 2013 07:56:33 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> >>> http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az >>> >>> It was just a quick cut and paste with minor changes. >>> I'll work on it to make it better and all comments are welcome. >> >>Would a separate ARM section be a good idea?? It'd make content easier to >>find although it may break up the structure of the site a little bit. >Eric suggested that that would be a good place to start from so I took his advice .... but if we gather up all the ARM specific stuff together it would be nice too. >Well whatever ... I'll be a good lamb and follow the flock :-D Forgot to mention: maybe it would be nice to link http://ac100.grandou.net/ as a generic linux on AC100 site and my short how-to as a specific tutorial on a possible way to get Slackware ARM on the AC100. The link in? http://arm.slackware.com/supportedplatforms/ still only points to http://ac100.grandou.net/ Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Jun 4 07:56:15 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 4 Jun 2013 08:56:15 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: > > >Eric suggested that that would be a good place to start from so I took his advice .... but if we > gather up all the ARM specific stuff together it would be nice too. > >Well whatever ... I'll be a good lamb and follow the flock :-D OK. I'll think about it. A separate ARM section seems to be a good idea because there's a lot of ARM specific stuff. The rest of the site can be considered x86/64 + non-arch specific Slackware stuff. > Forgot to mention: maybe it would be nice to link http://ac100.grandou.net/ as a generic linux on AC100 site and my short how-to as a specific tutorial on a possible way to get Slackware ARM on the AC100. > The link in? http://arm.slackware.com/supportedplatforms/ still only points to http://ac100.grandou.net/ I've changed the links. -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Tue Jun 4 10:26:16 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 4 Jun 2013 11:26:16 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1370341576.68155.YahooMailNeo@web28801.mail.ir2.yahoo.com> >> >Eric suggested that that would be a good place to start from so I took his advice .... but if we >>? gather up all the ARM specific stuff together it would be nice too. >> >Well whatever ... I'll be a good lamb and follow the flock :-D >OK.? I'll think about it. A separate ARM section seems to be a good idea >because there's a lot of ARM specific stuff.? The rest of the site can be >considered x86/64 + non-arch specific Slackware stuff. >> Forgot to mention: maybe it would be nice to link http://ac100.grandou.net/ as a generic linux on AC100 site and my short how-to as a specific tutorial on a possible way to get Slackware ARM on the AC100. >> The link in? http://arm.slackware.com/supportedplatforms/ still only points to http://ac100.grandou.net/ >I've changed the links. I've also done a bit of re editing on the documentation and added a few things that might be handy .... David -------------- next part -------------- An HTML attachment was scrubbed... URL: From frmrick at aapt.net.au Wed Jun 5 21:43:39 2013 From: frmrick at aapt.net.au (Rick) Date: Thu, 06 Jun 2013 07:43:39 +1000 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> Message-ID: <51AFB10B.9030502@aapt.net.au> On 03/06/13 05:13, Stuart Winter wrote: > >> I can't help wondering if what we really need for all of these community >> supported platforms is one standard site (maybe a subdomain from >> slackwarearm), done like a wiki type site, where each community >> supported platform can have it's own section, and those who contribute >> can sign up to have editing/uploading permissions. I have webspace, and >> bandwidth I can donate to that, but I don't have the time to setup and >> run such a site. > This has occurred to me as well, but so far I've kept out of suggesting > any structure for the RPi support (initially to see how it'd pan out). > Perhaps a better approach would be to host the RPi page on > http://docs.slackware.com and link to the externally hosted downloads from > there. > > The issue I see, going forwards, is that support is fragmented. Somebody > finds that doesn't work, so instead of suggesting/supplying a fix to > the author of the work they were using, they start their own version which > has additional issues. > > Does anybody want to be the lead owner of a RPi page on docs.slackware.com > (assuming we can put it on there -- I have no input in to that site so > have not yet checked whether we can (although I can't imagine why not!)). > Ideally there'd be a single Rpi installer and/or image available that has > all of the fixes rolled up into it. In the typical model for this > type of thing (given that it's a binary blob of an image/installer > image), the project owner essentially becomes the gate keeper so has to be > able to dedicate some time to folding requests and fixes back in to the > distributed images. > > Thoughts? Any takers? > After a period of inactivity I have picked up my pi again and plan to also purchase another. Besides some play automation around home I hope to learn a bit more about arm systems.What relevant Info/discussion re Slackware Arm and Raspberrypi is currently fragmented over many different urls and what you are saying makes perfect sense. I'm probably not the person for anything too technical but I could most likely manage the wiki side of things if the learning curve is not too steep. I've contributed on other wikis in the past and could probably do what is required or at least have a go. Stuart, you can contact me off forum if you want to discuss my participation in something like what you suggest From rickmiles at turtlespond.net Wed Jun 5 22:19:33 2013 From: rickmiles at turtlespond.net (Rick Miles) Date: Thu, 06 Jun 2013 08:19:33 +1000 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> Message-ID: <51AFB975.9090007@turtlespond.net> On 03/06/13 05:13, Stuart Winter wrote: > >> I can't help wondering if what we really need for all of these community >> supported platforms is one standard site (maybe a subdomain from >> slackwarearm), done like a wiki type site, where each community >> supported platform can have it's own section, and those who contribute >> can sign up to have editing/uploading permissions. I have webspace, and >> bandwidth I can donate to that, but I don't have the time to setup and >> run such a site. > This has occurred to me as well, but so far I've kept out of suggesting > any structure for the RPi support (initially to see how it'd pan out). > Perhaps a better approach would be to host the RPi page on > http://docs.slackware.com and link to the externally hosted downloads from > there. > > The issue I see, going forwards, is that support is fragmented. Somebody > finds that doesn't work, so instead of suggesting/supplying a fix to > the author of the work they were using, they start their own version which > has additional issues. > > Does anybody want to be the lead owner of a RPi page on docs.slackware.com > (assuming we can put it on there -- I have no input in to that site so > have not yet checked whether we can (although I can't imagine why not!)). > Ideally there'd be a single Rpi installer and/or image available that has > all of the fixes rolled up into it. In the typical model for this > type of thing (given that it's a binary blob of an image/installer > image), the project owner essentially becomes the gate keeper so has to be > able to dedicate some time to folding requests and fixes back in to the > distributed images. > > Thoughts? Any takers? > After a period of inactivity I have picked up my pi again and plan to also purchase another. Besides some play automation around home I hope to learn a bit more about arm systems.What relevant Info/discussion re Slackware Arm and Raspberrypi is currently fragmented over many different urls and what you are saying makes perfect sense. I'm probably not the person for anything too technical but I could most likely manage the wiki side of things if the learning curve is not too steep. I've contributed on other wikis in the past and could probably do what is required or at least have a go. Stuart, you can contact me off forum if you want to discuss my participation in something like what you suggest -- Rick Miles turtlespond.png From m-lists at biscuit.org.uk Fri Jun 7 21:32:32 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 7 Jun 2013 22:32:32 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <51AFB10B.9030502@aapt.net.au> References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> <51AFB10B.9030502@aapt.net.au> Message-ID: Hi Rick, [..] > I'm probably not the person for anything too technical but I could most likely > manage the wiki side of things if the learning curve is not too steep. I've > contributed on other wikis in the past and could probably do what is required > or at least have a go. [..] I was referring specifically to someone owning the 'master' RPi image rather than the wiki document (since anybody can update the wiki doc). I would like to see one master image/installer that has all of the fixes in it, and then have a wiki doc on docs.slackware.com with all of the appropriate information. An ARM section has now been created and I've moved the content of the INSTALL_RASPBERRYPI.TXT file into a wiki doc (the new version of this file just has the URL to the RPi wiki doc once I push out the next updates). http://docs.slackware.com/howtos:hardware:arm Feel free to add to or modify the docs. -- Stuart Winter Slackware ARM: http://arm.slackware.com From rickmiles at turtlespond.net Fri Jun 7 21:43:20 2013 From: rickmiles at turtlespond.net (Rick Miles) Date: Sat, 08 Jun 2013 07:43:20 +1000 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> <51AFB10B.9030502@aapt.net.au> Message-ID: <51B253F8.6040106@turtlespond.net> On 08/06/13 07:32, Stuart Winter wrote: > Hi Rick, > > [..] >> I'm probably not the person for anything too technical but I could most likely >> manage the wiki side of things if the learning curve is not too steep. I've >> contributed on other wikis in the past and could probably do what is required >> or at least have a go. > [..] > > I was referring specifically to someone owning the 'master' RPi image > rather than the wiki document (since anybody can update the wiki doc). > > I would like to see one master image/installer that has all of the fixes > in it, and then have a wiki doc on docs.slackware.com with all of the > appropriate information. > > An ARM section has now been created and I've moved the content of the > INSTALL_RASPBERRYPI.TXT file into a wiki doc (the new version of this file > just has the URL to the RPi wiki doc once I push out the next updates). > > http://docs.slackware.com/howtos:hardware:arm > > Feel free to add to or modify the docs. > Maybe I will someday. Right now I've got ahau's arm6 installed on a pi with ponce's 21 May kernel, everything seems a goer but X.... tonnes of fun [as the puppy snores in the background] :^) -- Rick Miles turtlespond.png -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: turtlespond.png Type: image/png Size: 444 bytes Desc: not available URL: From m-lists at biscuit.org.uk Fri Jun 7 21:52:19 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 7 Jun 2013 22:52:19 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <4c3f9baec30c1edd25e84fb27bb198de.squirrel@webmail01.one.com> <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> <51AFB10B.9030502@aapt.net.au> Message-ID: > http://docs.slackware.com/howtos:hardware:arm It's actually: http://docs.slackware.com/howtos:hardware:arm:start -- Stuart Winter Slackware ARM: http://arm.slackware.com From stanley at stanleygarvey.com Fri Jun 7 22:18:04 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 07 Jun 2013 23:18:04 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> References: <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> Message-ID: <20130607221804.D8D331B420D3@bmail04.one.com> On Jun 2, 2013 11:09 wrote: > From: stanley garvey > To: Slackware ARM port ; stanley > > Sent: Sat, Jun 1, 2013 8:39 pm > Subject: Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 > > > On May 30, 2013 08:34 wrote: > > > > > > > Hi > > > > > > > > > Since Slackware 14.1 is coming together, could all of you who > > > plan on preparing and distributing support for Slackware ARM > > > 14.1 for the RaspberryPi please reply to this message (on-list) > > > with the > > > following information. I will collate it and put it into the > > > /INSTALL_RASPBERRYPI.TXT document within the release. > > > > > > Note that this is *only* for those of you who are supplying > > > images/installers that contain the _official_ Slackware ARM > > > packages which > > > will be taken from > > > . > > > > > > 1. The URL of the web site containing information about your > > > distribution. > > > > > > 2. Installation method: regular installer / pre-supplied image(s) > > > > > > If it's a pre-supplied image, what categories of software are > > > included: > > > > > > Don't list every package, but a high level brief description such > > > as: > > > > > > dev tools ('d') > > > > > > - Compilers and toolchain tools > > > - Python, Perl > > > > > > X11 ('x') > > > > > > - X packages relevant to the Rpi > > > > > > KDE ('kde') > > > - All of KDE > > > - Base components of KDE > > > > > > > > > 3. RPi boards / versions of boards that your distribution has been > > > tested with and confirmed operational. > > > > > > 4. The particular reason for choosing yours over another. Some of > > > the > > > reasons that some people have created their own image is because > > > Dave > > > Spencer's work stopped at 13.37, or theirs addressed particular > > > problems on certain boards. > > > > > > Please note that this shouldn't be a reason for the 14.1 release - > > > you should treat this as new rather than a patch to someone else's > > > work (even > > > if that's what it started out as). > > > > > > > > > Deadline: > > > --------- > > > > > > I'll stop taking submissions at the release of RC1 of Slackware > > > 14.1 x86. > > > > > > Any questions - please ask! > > > > > > Cheers > > > Stuart. > > > > > > > > > -- > > > Stuart Winter > > > > > > Slackware for ARM: > > > _______________________________________________ > > > ARMedslack mailing list > > > > > > > > > > > Hi Stuart > > Judging by the avalanche of submissions, it would look I am alone in > > supporting Slackware on the RPi - ( Hello! - cue hall type reverb > > and tumbleweed). > > However my site gets two or three hits a day regarding slackberry, > > so somebody's interested. > > The issue with udev renaming eth0 to eth1 is documented on the site. > > I need to fix this but given to udevs labariynthine nature I may > > require a ball of string. I may be some time. > > > > > > Hi Stanley, > > > > I got rid of the problem of eth0 -> eth1 udev renamingon the images I > create by using the slackware supported standard > /etc/rc.d/rc.shutdown_local script to remove > the70-persistent-net.rules file whenever a shutdown is run. Iuse it > for a whole load of other stuff as well, but removing it on shutdown > makes theimages I create portable across boxes. > > > > I'll chip in on the providing stuff where I have something to offer, > but whatever I chip in will be additions to the standard slackware > stuff (I prefer to keep the appliances I create as standard as > possible and just add stuff toit). > > > > I can't help wondering if what we really need for all of these > community supported platforms is one standard site (maybe a subdomain > from slackwarearm), done like a wiki type site, where each community > supported platform can have it's own section,and those who contribute > can sign up to have editing/uploading permissions. > > I have webspace, and bandwidth I can donate to that,but Idon't have > the time tosetup and run such a > site._______________________________________________ > ARMedslack mailing list > > > > Hi sorry for not getting back to you sooner. Using the shutdown script > is a great idea and would work well if you intend on using an sdcard > on more than on board. The problem I see is udev re-triggering on the > same device, same mac address. I.E on initial boot when > 70-persistent-net.rules is created. It got me stumped and stalled most > of the work on the Raspberry Pi. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Jun 7 22:43:20 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 07 Jun 2013 23:43:20 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <51AFB10B.9030502@aapt.net.au> Message-ID: <20130607224320.AEB28DD43F52D@bmail06.one.com> On Jun 7, 2013 22:32 "Stuart Winter" wrote: > Hi Rick, > > [..] > > I'm probably not the person for anything too technical but I could > > most likely > > manage the wiki side of things if the learning curve is not too > > steep. I've > > contributed on other wikis in the past and could probably do what is > > required > > or at least have a go. > [..] > > I was referring specifically to someone owning the 'master' RPi image > rather than the wiki document (since anybody can update the wiki doc). > > I would like to see one master image/installer that has all of the > fixes > in it, and then have a wiki doc on docs.slackware.com with all of the > appropriate information. > > An ARM section has now been created and I've moved the content of the > INSTALL_RASPBERRYPI.TXT file into a wiki doc (the new version of this > file > just has the URL to the RPi wiki doc once I push out the next > updates). > > > > Feel free to add to or modify the docs. > > Hi Stuart, > I could own the "master' image' if you would like. I could set aside > some hours a week to administer fixes and such. > > Q. Would I create the base image myself or do you have one in mind? If > so do you think my modified Versatile-initrd is a good starting point? > or should I start back with David Spencers installer? I would value > your views on this. > > Also, what name? I have been using Slackberry as short for > 'slackwarearm on a raspberry pi' is this appropriate? > I could register a domain for this. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sat Jun 8 07:12:08 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 8 Jun 2013 08:12:08 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130607221804.D8D331B420D3@bmail04.one.com> References: <20130601193940.448EB966CB2DB@bmail04.one.com> <8D02D90601FF72C-10E4-4D444@webmail-m226.sysops.aol.com> <20130607221804.D8D331B420D3@bmail04.one.com> Message-ID: > > I got rid of the problem of eth0 -> eth1 udev renamingon the images I > > create by using the slackware supported standard > > /etc/rc.d/rc.shutdown_local script to remove > > the70-persistent-net.rules file whenever a shutdown is run. Iuse it > > for a whole load of other stuff as well, but removing it on shutdown > > makes theimages I create portable across boxes. Check that you do not have udevd running twice. ps wwaxu --forest | grep udev may show that there are multiple udevd running, but they should be children of a single parent. This was the cause of the renaming problem in an earlier builds of Slackware (prior to 14.0 release, I think, or maybe even post 14.0) - udevd had been started independently twice in the boot sequence. This was fixed a long time ago so I'm wondering whether the installer or some packages you have are old. From m-lists at biscuit.org.uk Sat Jun 8 17:54:17 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 8 Jun 2013 18:54:17 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130607224320.AEB28DD43F52D@bmail06.one.com> References: <51AFB10B.9030502@aapt.net.au> <20130607224320.AEB28DD43F52D@bmail06.one.com> Message-ID: > Hi Stuart, > I could own the "master' image' if you would like. I could set aside > some hours a week to administer fixes and such. > > Q. Would I create the base image myself or do you have one in mind? If I have only ever considered what would be appropriate in the mini root (which was essentially everything needed to have a working OS + some every day tools I needed in order to bootstrap new architectures). Normally people tend to ship minimal roots (check Fedora etc.) and the people can then download the packages they require. This has some obvious benefits such as it's faster to download, faster to upload, easier to maintain and people can use slackpkg or whatever to install the packages they want. Ovbviously if I was doing it, there'd just be an installer so I would not have to consider what to supply ;-) I'll leave it for you to decide. > so do you think my modified Versatile-initrd is a good starting point? > or should I start back with David Spencers installer? I would value > your views on this. I have not looked at your initrd and I don't have a Rpi (if I did I'd have done the support myself). My two questions are: 1. - what are you modifying and why? For example, when I add a new architecture all I edit in the installer is the /etc/rc.d/rc.modules-arm. The generic installer is then built (actually it's the versatile one but I'm going to make it generic for Linux 3.10), and my scripts unpack it, determine what modules the versatile/generic installer has and replaces them with the versions for the particular architecture, then adds any arch-specific modules and finally wraps it up again. http://armed.slackware.com/scripts/mk-tegra.sh It's pretty ugly but it's simple. 2. - can any of your changes be merged back into the original installer? This is more of a rhetorical question ;-) > Also, what name? I have been using Slackberry as short for > 'slackwarearm on a raspberry pi' is this appropriate? > I could register a domain for this. If you were turning it into a different product which was based on Slackware, then it makes sense to give it a different name. The only reason Slackware ARM was called 'ARMedslack' was because since I didn't really know Patrick in 2002, the web site said unofficial stuff shouldn't use the Slackware name, and so respectfully I gave it a separate name. However, the OS has *always* been Slackware but on the ARM architecture - apart from porting it and making necessary or particularly (what I think are) appropriate changes, it's the same product as x86. So the short answer is that I personally prefer 'Slackware ARM on a Raspberry Pi' because you're actually taking the same product but making it installable and runable on the Rpi. Cheers s. -- Stuart Winter Slackware ARM: http://arm.slackware.com From stanley at stanleygarvey.com Sat Jun 8 21:08:16 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 08 Jun 2013 22:08:16 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130607224320.AEB28DD43F52D@bmail06.one.com> Message-ID: <20130608210816.F29178AE85310@bmail02.one.com> On Jun 8, 2013 18:54 "Stuart Winter" wrote: > > Hi Stuart, > > I could own the "master' image' if you would like. I could set aside > > some hours a week to administer fixes and such. > > > > Q. Would I create the base image myself or do you have one in mind? > > If > > I have only ever considered what would be appropriate in the mini root > (which was essentially everything needed to have a working OS + some > every > day tools I needed in order to bootstrap new architectures). > > Normally people tend to ship minimal roots (check Fedora etc.) and the > people can then download the packages they require. This has some > obvious > benefits such as it's faster to download, faster to upload, easier to > maintain and people can use slackpkg or whatever to install the > packages > they want. > > Ovbviously if I was doing it, there'd just be an installer so I would > not > have to consider what to supply ;-) > > I'll leave it for you to decide. > > > so do you think my modified Versatile-initrd is a good starting > > point? > > or should I start back with David Spencers installer? I would value > > your views on this. > > I have not looked at your initrd and I don't have a Rpi (if I did I'd > have > done the support myself). My two questions are: > > 1. - what are you modifying and why? > > For example, when I add a new architecture all I edit in the installer > is > the /etc/rc.d/rc.modules-arm. The generic installer is then built > (actually it's the versatile one but I'm going to make it generic for > Linux 3.10), and my scripts unpack it, determine what modules the > versatile/generic installer has and replaces them with the versions > for > the particular architecture, then adds any arch-specific modules and > finally wraps it up again. > > It's pretty ugly but it's simple. > > > That's basically what I have done, but by hand. There is also a > > 'raspberrypi' directory containing a simple script that should be > > ran before rebooting from the installer to remove non raspberry pi > > kenels and kernel source, modify inittab, rc.S and set the > > config.txt to boot from rootfs. - I'll look at your mk-tegra script, > > thanks > > 2. - can any of your changes be merged back into the original > installer? > This is more of a rhetorical question ;-) > > >That is more of a rhetorical question. I have changed as little as > >possible! > > > > Also, what name? I have been using Slackberry as short for > > 'slackwarearm on a raspberry pi' is this appropriate? > > I could register a domain for this. > > If you were turning it into a different product which was based > on Slackware, then it makes sense to give it a different name. > The only reason Slackware ARM was called 'ARMedslack' was because > since I > didn't really know Patrick in 2002, the web site said unofficial > stuff shouldn't use the Slackware name, and so respectfully I gave it > a separate name. However, the OS has *always* been Slackware but on > the > ARM architecture - apart from porting it and making necessary or > particularly > (what I think are) appropriate changes, it's the same product as x86. > > So the short answer is that I personally prefer 'Slackware ARM on a > Raspberry Pi' because you're actually taking the same product but > making it > installable and runable on the Rpi. > > > Okay, all my page titles start with "SlackwareArm for the raspberry > > Pi' even if pointed to by 'Slackberry' I guess an installer wouldn't > > need its own domain. > > Cheers > s. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Sun Jun 9 06:43:51 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sun, 09 Jun 2013 07:43:51 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130607221804.D8D331B420D3@bmail04.one.com> Message-ID: <20130609064351.4F347C2FF4002@bmail03.one.com> On Jun 8, 2013 08:12 "Stuart Winter" wrote: > > > I got rid of the problem of eth0 -> eth1 udev renamingon the > > > images I > > > create by using the slackware supported standard > > > /etc/rc.d/rc.shutdown_local script to remove > > > the70-persistent-net.rules file whenever a shutdown is run. Iuse > > > it > > > for a whole load of other stuff as well, but removing it on > > > shutdown > > > makes theimages I create portable across boxes. > > Check that you do not have udevd running twice. > > ps wwaxu --forest | grep udev > > may show that there are multiple udevd running, but they should be > children of a single parent. > > This was the cause of the renaming problem in an earlier builds of > Slackware (prior to 14.0 release, > I think, or maybe even post 14.0) - udevd had been started > independently > twice in the boot sequence. This was fixed a long time ago so I'm > wondering whether the installer or some packages you have are old. > > > _______________________________________________ > ARMedslack mailing list > > > > Thanks for thar Stuart. I now have a clue where to look. > root at slackberry:~# ps wwaxu --forest | grep udev > root 62 0.3 0.3 4232 1636 ? Ss 00:00 0:01 /sbin/udevd --daemon > root 625 0.0 0.2 4228 1240 ? S 00:00 0:00 \_ /sbin/udevd --daemon > root 627 0.0 0.2 4228 1164 ? S 00:00 0:00 \_ /sbin/udevd --daemon > > Cheers! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Jun 10 14:40:36 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 10 Jun 2013 15:40:36 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: References: <1369902680.57822.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1370875236.41392.YahooMailNeo@web28801.mail.ir2.yahoo.com> >> >Eric suggested that that would be a good place to start from so I took his advice .... but if we >>>? gather up all the ARM specific stuff together it would be nice too. >> >Well whatever ... I'll be a good lamb and follow the flock :-D >OK.? I'll think about it. A separate ARM section seems to be a good idea >because there's a lot of ARM specific stuff.? The rest of the site can be >considered x86/64 + non-arch specific Slackware stuff. >> Forgot to mention: maybe it would be nice to link http://ac100.grandou.net/ as a generic linux on AC100 site and my short how-to as a specific tutorial on a possible way to get Slackware ARM on the AC100. >> The link in? http://arm.slackware.com/supportedplatforms/ still only points to http://ac100.grandou.net/ >I've changed the links. I think that someone, possibly Eric, created the specific arm hardware page and moved the AC100 stuff in there: the link on http://arm.slackware.com/supportedplatforms/ needs mending again :-) Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Tue Jun 11 20:43:10 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Tue, 11 Jun 2013 21:43:10 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130608210816.F29178AE85310@bmail02.one.com> References: <20130608210816.F29178AE85310@bmail02.one.com> Message-ID: <20130611204310.D8587778563DF@bmail03.one.com> > > If you were turning it into a different product which was based > > on Slackware, then it makes sense to give it a different name. > > The only reason Slackware ARM was called 'ARMedslack' was because > > since I > > didn't really know Patrick in 2002, the web site said unofficial > > stuff shouldn't use the Slackware name, and so respectfully I gave > > it > > a separate name. However, the OS has *always* been Slackware but on > > the > > ARM architecture - apart from porting it and making necessary or > > particularly > > (what I think are) appropriate changes, it's the same product as > > x86. > > > > So the short answer is that I personally prefer 'Slackware ARM on a > > Raspberry Pi' because you're actually taking the same product but > > making it > > installable and runable on the Rpi. > > > > > Okay, all my page titles start with "SlackwareArm for the > > > raspberry Pi' even if pointed to by 'Slackberry' I guess an > > > installer wouldn't need its own domain. > > > > Cheers > > s. > > > > Hi Stuart, > > I have changed my URLs to > > stanleygarvey.com/slackwarearm_rpi/index.php and dropped the > > slackberry name, also I can report that slackware-current does not > > have the udev problem that has plagued me for the last five months, > > thanks for your help. I will make images available there, I think > > that you are too not keen on preinstalled images, however as I > > install this stuff for myself it doesn't hurt to make them available > > to others as zip files for non linux users. > > I Have looked at your mk-tegra script and it looks like I can use it > > to produce a raspberry pi installer using script built kernels and > > modules. > > As for issues with the Raspberry Pi, I don't see many, it has no > > real time clock, rc.S needs hacking to remove the annoying message, > > and inittab requires patching and that's about it. > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Jun 11 20:59:45 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 11 Jun 2013 21:59:45 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130611204310.D8587778563DF@bmail03.one.com> References: <20130608210816.F29178AE85310@bmail02.one.com> <20130611204310.D8587778563DF@bmail03.one.com> Message-ID: > > > stanleygarvey.com/slackwarearm_rpi/index.php and dropped the > > > slackberry name, also I can report that slackware-current does not OK great. "Download SlackwareArm for Raspberry Pi?." You're missing the capitalisation - ARM stands for "Advanced (or 'Acorn' if you go back further) Risc Machines" (or at least it used to in the early 90s - it's probably too cool for that now though ;-) ). [..] > > > As for issues with the Raspberry Pi, I don't see many, it has no > > > real time clock, rc.S needs hacking to remove the annoying message, > > > and inittab requires patching and that's about it. What message? is it from hwclock? Personally I just leave those kind of messages in place -it looks a bit ugly but at least it's a reminder that there is no hardware clock. What needs to be modified in inittab? http://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/source/a/sysvinit-scripts/sources/doinst.sh.openttyS0 Could the change be added into here? The less changes you have to keep adding in the better - especially when I'm already doing it for the others! -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Tue Jun 11 21:01:55 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 11 Jun 2013 22:01:55 +0100 (BST) Subject: [ARMedslack] Toshiba AC100 In-Reply-To: <1370875236.41392.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <1369983632.36172.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370028875.41867.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370121385.97540.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370248331.19272.YahooMailNeo@web28806.mail.ir2.yahoo.com> <1370275203.19494.YahooMailNeo@web28805.mail.ir2.yahoo.com> <1370328602.52939.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1370328993.49304.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1370875236.41392.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: > I think that someone, possibly Eric, created the specific arm hardware > page and moved the AC100 stuff in there: the link on > http://arm.slackware.com/supportedplatforms/ needs mending again :-) Ah yes I got a bit carried away before Eric had finalised the ARM section. I've corrected the link now. From stanley at stanleygarvey.com Wed Jun 12 14:38:47 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 12 Jun 2013 15:38:47 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130611204310.D8587778563DF@bmail03.one.com> Message-ID: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> On Jun 11, 2013 21:59 "Stuart Winter" wrote: > > > > stanleygarvey.com/slackwarearm_rpi/index.php and dropped the > > > > slackberry name, also I can report that slackware-current does > > > > not > > OK great. > "Download SlackwareArm for Raspberry Pi?." > > You're missing the capitalisation - ARM stands for "Advanced (or > 'Acorn' > if you go back further) Risc Machines" (or at least it used to in the > early 90s - it's probably too > cool for that now though ;-) ). > > > I'll Correct that ( The whole section needs some polishing and > > rewriting) > > [..] > > > > As for issues with the Raspberry Pi, I don't see many, it has no > > > > real time clock, rc.S needs hacking to remove the annoying > > > > message, > > > > and inittab requires patching and that's about it. > > What message? is it from hwclock? Personally I just leave those kind > of > messages in place -it looks a bit ugly but at least it's a reminder > that > there is no hardware clock. > > > No I meant the annoying message from rc.S about the rootFS being > > read write. The Raspberry Pi does not honor the ro flag :( > The only way round this is to use a hacked rc.S, Unless somebody has a > better idea? > > What needs to be modified in inittab? > /a/sysvinit-scripts/sources/doinst.sh.openttyS0> > > Could the change be added into here? The less changes you have to keep > adding in the better - especially when I'm already doing it for the > others! > > > yes! > The Raspberry Pi uses ttyAMA0 could i Suggest: > > > egrep -q "Versatile" /proc/cpuinfo > /dev/null 2>&1 || egrep -q > "BCM2708" /proc/cpuinfo > /dev/null 2>&1 && \ > sed -i '/^# Local serial lines:/ a\s0:12345:respawn:/sbin/agetty > 115200 ttyAMA0 vt100' etc/inittab.new || \ > sed -i '/^# Local serial lines:/ a\s0:12345:respawn:/sbin/agetty > 115200 ttyS0 vt100' etc/inittab.new > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Wed Jun 12 17:28:34 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 12 Jun 2013 18:28:34 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> References: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> Message-ID: <20130612172834.B7FE81EC4EDF4@bmail03.one.com> > > What message? is it from hwclock? Personally I just leave those kind > > of > > messages in place -it looks a bit ugly but at least it's a reminder > > that > > there is no hardware clock. > > > > > No I meant the annoying message from rc.S about the rootFS being > > > read write. The Raspberry Pi does not honor the ro flag :( > > The only way round this is to use a hacked rc.S, Unless somebody has > > a better idea? > > > > > > > Opps I'll have to retract this as I have just checked, at least on > > > the new boards (512mb) the ro option is honored, perhaps the > > > firmware changed? I will need to check on a 256mb board. Its still > > > good news. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Wed Jun 12 18:32:37 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 12 Jun 2013 19:32:37 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> Message-ID: > > > read write. The Raspberry Pi does not honor the ro flag :( > > The only way round this is to use a hacked rc.S, Unless somebody has a > > better idea? Default it into the kernel: CONFIG_CMDLINE: On some architectures (EBSA110 and CATS), there is currently no way for the boot loader to pass arguments to the kernel. For these architectures, you should supply some command-line options at build time by entering them here. As a minimum, you should specify the memory size and the root device (e.g., mem=64M root=/dev/nfs). It's in 'Boot Options > () Default kernel command string' compile it in and give it a go. I've updated the new sysvinit-scripts package with the inittab change and I'll push out the changes soon. -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Thu Jun 13 06:51:49 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 13 Jun 2013 07:51:49 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> Message-ID: <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> I got tempted with one of these. Integrated BGN wifi 1 usb client/host port qith support for external usb devices (is ethernet/3G ....) 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is reserved for boot/rescure/emergency restore) 7" screen 800x480 px single core cortex A8 (not tegra) 1/2Gb ram micro SD slot with support for 32Gb cards 3 axis accelerometer Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still tempted to try have Slackware on this one too. The user-land will probably only require just xkbd but I doubt the kernel that comes with the device has proper frame-buffer console so I'll need to figure out what sort of kernel to put on that thing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu Jun 13 07:05:04 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 13 Jun 2013 03:05:04 -0400 Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> Message-ID: On Thu, Jun 13, 2013 at 2:51 AM, Davide wrote: > I got tempted with one of these. > > Integrated BGN wifi > 1 usb client/host port qith support for external usb devices (is ethernet/3G > ....) > 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is > reserved for boot/rescure/emergency restore) > 7" screen 800x480 px > single core cortex A8 (not tegra) > 1/2Gb ram > micro SD slot with support for 32Gb cards > 3 axis accelerometer > > Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still > tempted to try have Slackware on this one too. > The user-land will probably only require just xkbd but I doubt the kernel > that comes with the device has proper frame-buffer console so I'll need to > figure out what sort of kernel to put on that thing. > Hello! Where did you find out about the thing to begin with? Google doesn't know a thing about it, and wanted to tell me about a completely useless contraption used for playing bad music. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From openpandora at free.fr Thu Jun 13 17:00:48 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Thu, 13 Jun 2013 19:00:48 +0200 (CEST) Subject: [ARMedslack] gcc 4.8.1 in -current Message-ID: <845586759.103351407.1371142848520.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! What's decided about it, as i see it's missing from the last update ? LS. From m-lists at biscuit.org.uk Thu Jun 13 17:51:56 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 13 Jun 2013 18:51:56 +0100 (BST) Subject: [ARMedslack] gcc 4.8.1 in -current In-Reply-To: <845586759.103351407.1371142848520.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <845586759.103351407.1371142848520.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: Hi LS > What's decided about it, as i see it's missing from the last update ? The current problem with 4.8.0 is the same as here - it does not produce a bootable kernel. https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847 I am going to build gcc 4.8.1 soon and see whether it can compile a bootable kernel. If it can, I'll upgrade it in the 'd' series; if not 4.8.1 will upgrade 4.8.0 in /extra. -- Stuart Winter Slackware ARM: http://arm.slackware.com From stanley at stanleygarvey.com Thu Jun 13 20:22:34 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 13 Jun 2013 21:22:34 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> Message-ID: <20130613202235.01E00BCFC1410@bmail03.one.com> On Jun 12, 2013 19:32 "Stuart Winter" wrote: > > > > read write. The Raspberry Pi does not honor the ro flag :( > > > The only way round this is to use a hacked rc.S, Unless somebody > > > has a > > > better idea? > > Default it into the kernel: > > CONFIG_CMDLINE: > > On some architectures (EBSA110 and CATS), there is currently no way > for the boot loader to pass arguments to the kernel. For these > architectures, you should supply some command-line options at build > time by entering them here. As a minimum, you should specify the > memory size and the root device (e.g., mem=64M root=/dev/nfs). > > It's in 'Boot Options > () Default kernel command string' > compile it in and give it a go. > > Solved! thanks > > I've updated the new sysvinit-scripts package with the inittab change > and > I'll push out the changes soon. > > Great, Thank you very much! I wa > We saw the good side and the bad side of cyclists today and I also got > to read a poem from the 'Black Cab poet' > Tue 11th Jun 2013 @ 7:07.58 - 1h 53m 18ss wondering if something > similar could be done for '/usr/lib/setup/armedslack-nofscheck ' to > make it more generic? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Jun 13 20:35:51 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 13 Jun 2013 21:35:51 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130613202235.01E00BCFC1410@bmail03.one.com> References: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <20130613202235.01E00BCFC1410@bmail03.one.com> Message-ID: > > We saw the good side and the bad side of cyclists today and I also got > > to read a poem from the 'Black Cab poet' Cool. How'd it go?! > > Tue 11th Jun 2013 @ 7:07.58 - 1h 53m 18ss wondering if something > > similar could be done for '/usr/lib/setup/armedslack-nofscheck ' to > > make it more generic? Ok I've changed it and will upload the new installers once I've got Linux 3.9.6 kernels built. -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Thu Jun 13 20:39:34 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 13 Jun 2013 21:39:34 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <20130613202235.01E00BCFC1410@bmail03.one.com> Message-ID: > Ok I've changed it and will upload the new installers once I've got Linux > 3.9.6 kernels built. Actually, can you test it? I just edited it and haven't tested it. It's really just cosmetic, so it should be fine: http://armed.slackware.com/tmp/armedslack-nofscheck -- Stuart Winter Slackware ARM: http://arm.slackware.com From stanley at stanleygarvey.com Thu Jun 13 20:49:48 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 13 Jun 2013 21:49:48 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130613202235.01E00BCFC1410@bmail03.one.com> Message-ID: <20130613204948.F14D627D3CF6D@bmail06.one.com> On Jun 13, 2013 21:35 "Stuart Winter" wrote: > > > We saw the good side and the bad side of cyclists today and I also > > > got > > > to read a poem from the 'Black Cab poet' > > Cool. How'd it go?! > > > whoops, don't ya just hate it when that happens? :) > > > > > Tue 11th Jun 2013 @ 7:07.58 - 1h 53m 18ss wondering if something > > > similar could be done for '/usr/lib/setup/armedslack-nofscheck ' > > > to > > > make it more generic? > > Ok I've changed it and will upload the new installers once I've got > Linux > 3.9.6 kernels built. > > >I'll test it, Thank you! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jun 14 07:12:56 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 14 Jun 2013 08:12:56 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> Message-ID: <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> >> I got tempted with one of these. >> >> Integrated BGN wifi >> 1 usb client/host port qith support for external usb devices (is ethernet/3G >> ....) >> 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is >> reserved for boot/rescure/emergency restore) >> 7" screen 800x480 px >> single core cortex A8 (not tegra) >> 1/2Gb ram >> micro SD slot with support for 32Gb cards >> 3 axis accelerometer >> >> Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still >> tempted to try have Slackware on this one too. >> The user-land will probably only require just xkbd but I doubt the kernel >> that comes with the device has proper frame-buffer console so I'll need to >> figure out what sort of kernel to put on that thing. >> > >Hello! >Where did you find out about the thing to begin with? Google doesn't >know a thing about it, and wanted to tell me about a completely >useless contraption used for playing bad music. Ooops ... XZPAD700 I have one ... I got in in hypermarket Carrefour in offer 69 Euro. I'm sure it's a re branded Chinese thing but for that price I can stick up with it. I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jun 14 13:01:01 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 14 Jun 2013 14:01:01 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> >>> I got tempted with one of these. >>> >>> Integrated BGN wifi >>> 1 usb client/host port qith support for external usb devices (is ethernet/3G >>> ....) >>> 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is >>> reserved for boot/rescure/emergency restore) >>> 7" screen 800x480 px >>> single core cortex A8 (not tegra) >>> 1/2Gb ram >>> micro SD slot with support for 32Gb cards >>> 3 axis accelerometer >>> >>> Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still >>> tempted to try have Slackware on this one too. >>> The user-land will probably only require just xkbd but I doubt the kernel >>> that comes with the device has proper frame-buffer console so I'll need to >>> figure out what sort of kernel to put on that thing. >>> >> >>Hello! >>Where did you find out about the thing to begin with? Google doesn't >>know a thing about it, and wanted to tell me about a completely >>useless contraption used for playing bad music. > >Ooops ... XZPAD700 >I have one ... I got in in hypermarket Carrefour in offer 69 Euro. >I'm sure it's a re branded Chinese thing but for that price I can stick up with it. > >I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap. Ok here's some info on the device (I've not yet rooted the device but I got is as root so I guess this one is not locked) : root at darkstar:~/ac100/devel/android-sdk-linux_x86/platform-tools# ./adb? shell * daemon not running. starting it now on port 5037 * * daemon started successfully * root at android:/ # root at android:/ # cat /proc/partitions????????????????????????????????????????? major minor? #blocks? name ?? 7??????? 0?????? 3150 loop0 ?? 7??????? 1????? 14585 loop1 ? 93??????? 0????? 16384 nanda ? 93??????? 8????? 16384 nandb ? 93?????? 16????? 32768 nandc ? 93?????? 24???? 393216 nandd ? 93?????? 32??? 1048576 nande ? 93?????? 40????? 16384 nandf ? 93?????? 48????? 32768 nandg ? 93?????? 56???? 262144 nandh ? 93?????? 64???? 131072 nandi ? 93?????? 72??? 1981440 nandj ?254??????? 0?????? 3150 dm-0 ?254??????? 1????? 14584 dm-1 root at android:/ # cat /proc/cmdline???????????????????????????????????????????? console=ttyS0,115200 rw init=/init loglevel=5 root at android:/ # ls /proc/???????????????????????????????????????????????????? 1 ... ... ... 905 asound buddyinfo bus ccmu cgroups cmdline consoles cpu cpuinfo crypto devices diskstats driver execdomains fb filesystems fs interrupts iomem ioports irq kallsyms kmsg kpagecount kpageflags loadavg locks meminfo misc modules mounts net pagetypeinfo partitions sched_debug schedstat scsi self slabinfo softirqs stat swaps sys sysrq-trigger sysvipc timer_list timer_stats tty uid_stat uptime version vmallocinfo vmstat wakelocks zoneinfo root at android:/ # ls /proc/tty/???????????????????????????????????????????????? driver drivers ldisc ldiscs root at android:/ # dmesg <6>[??? 0.000000] Initializing cgroup subsys cpuset <5>[??? 0.000000] Linux version 3.0.8+ (tom at tom-ThinkPad) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #47 PREEMPT Thu Nov 22 14:25:01 CST 2012 <4>[??? 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f <4>[??? 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache <4>[??? 0.000000] Machine: sun5i <6>[??? 0.000000] Total Detected Memory: 512MB with 2 banks <6>[??? 0.000000] Memory Reserved(in bytes): <6>[??? 0.000000]?????? LCD: 0x48000000, 0x01000000 <6>[??? 0.000000]?????? SYS: 0x43000000, 0x00010000 <6>[??? 0.000000]?????? VE : 0x44000000, 0x04000000 <4>[??? 0.000000] Memory policy: ECC disabled, Data cache writeback <7>[??? 0.000000] On node 0 totalpages: 114688 <7>[??? 0.000000] free_area_init_node: node 0, pgdat c08f8864, node_mem_map c0ab4000 <7>[??? 0.000000]?? Normal zone: 1024 pages used for memmap <7>[??? 0.000000]?? Normal zone: 0 pages reserved <7>[??? 0.000000]?? Normal zone: 113664 pages, LIFO batch:31 <7>[??? 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 <7>[??? 0.000000] pcpu-alloc: [0] 0 <4>[??? 0.000000] Built 1 zonelists in Zone order, mobility grouping on.? Total pages: 113664 <5>[??? 0.000000] Kernel command line: console=ttyS0,115200 rw init=/init loglevel=5 <6>[??? 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) <6>[??? 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) <6>[??? 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) <6>[??? 0.000000] Memory: 144MB 304MB = 448MB total <5>[??? 0.000000] Memory: 361604k/361604k available, 97148k reserved, 0K highmem <5>[??? 0.000000] Virtual kernel memory layout: <5>[??? 0.000000]???? vector? : 0xffff0000 - 0xffff1000?? (?? 4 kB) <5>[??? 0.000000]???? fixmap? : 0xfff00000 - 0xfffe0000?? ( 896 kB) <5>[??? 0.000000]???? DMA???? : 0xffc00000 - 0xffe00000?? (?? 2 MB) <5>[??? 0.000000]???? vmalloc : 0xe0800000 - 0xf0000000?? ( 248 MB) <5>[??? 0.000000]???? lowmem? : 0xc0000000 - 0xe0000000?? ( 512 MB) <5>[??? 0.000000]???? pkmap?? : 0xbfe00000 - 0xc0000000?? (?? 2 MB) <5>[??? 0.000000]???? modules : 0xbf000000 - 0xbfe00000?? (? 14 MB) <5>[??? 0.000000]?????? .init : 0xc0008000 - 0xc0032000?? ( 168 kB) <5>[??? 0.000000]?????? .text : 0xc0032000 - 0xc08048f8?? (8011 kB) <5>[??? 0.000000]?????? .data : 0xc0806000 - 0xc08ff728?? ( 998 kB) <5>[??? 0.000000]??????? .bss : 0xc08ff74c - 0xc0ab36fc?? (1744 kB) <6>[??? 0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 <6>[??? 0.000000] NR_IRQS:96 nr_irqs:96 96 <6>[??? 0.000000] timer0: Periodic Mode <4>[??? 0.000000] sw_timer_init,line:372 <6>[??? 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms <4>[??? 0.000000] aw_clksrc_init, line:339 <6>[??? 0.000000] Console: colour dummy device 80x30 <3>[??? 0.000000] ram_console: buffer?? (null), invalid size 0, datasize 4294967284 <6>[??? 0.000116] Calibrating delay loop... 1001.88 BogoMIPS (lpj=5009408) <6>[??? 0.040021] pid_max: default: 32768 minimum: 301 <6>[??? 0.040143] Mount-cache hash table entries: 512 <6>[??? 0.040459] Initializing cgroup subsys cpuacct <6>[??? 0.040483] Initializing cgroup subsys devices <6>[??? 0.040493] Initializing cgroup subsys freezer <6>[??? 0.040501] Initializing cgroup subsys blkio <6>[??? 0.040570] CPU: Testing write buffer coherency: ok <6>[??? 0.040780] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available <6>[??? 0.041298] devtmpfs: initialized <6>[??? 0.042565] print_constraints: dummy: <6>[??? 0.042722] NET: Registered protocol family 16 <6>[??? 0.043237] hw-breakpoint: debug architecture 0x4 unsupported. <4>[??? 0.043671] try to parse apb frequency from script faild! <4>[??? 0.043764] SOFTWINNER DMA Driver, (c) 2003-2004,2006 Simtec Electronics <6>[??? 0.043827] Initialize DMAC OK <6>[??? 0.048085] bio: create slab at 0 <5>[??? 0.048663] SCSI subsystem initialized <6>[??? 0.048874] usbcore: registered new interface driver usbfs <6>[??? 0.048941] usbcore: registered new interface driver hub <6>[??? 0.049073] usbcore: registered new device driver usb <6>[??? 0.049490] Advanced Linux Sound Architecture Driver Version 1.0.24. <6>[??? 0.050000] cfg80211: Calling CRDA to update world regulatory domain <4>[??? 0.050000] Init eGon pin module V2.0 <6>[??? 0.050000] Switching to clocksource aw 64bits couter <5>[??? 0.050000] FS-Cache: Loaded <6>[??? 0.050000] CacheFiles: Loaded <6>[??? 0.050000] Switched to NOHz mode on CPU #0 <4>[??? 0.050000] [usb_manager]: CONFIG_USB_SW_SUN5I_USB0_OTG <4>[??? 0.050000] [sw_hcd0]: usb host driver initialize........ <4>[??? 0.050000] [sw_hcd0]: open_usb_clock <4>[??? 0.065430] [sw_hcd0]: host_init_state = 0 <4>[??? 0.065438] [sw_hcd0]: platform is usb host <4>[??? 0.065504] [sw_hcd0]: sw_hcd_init_controller: sw_hcd_host0: USB Host mode controller at f1c13000 using PIO, IRQ 38 <6>[??? 0.065527] sw_hcd_host0 sw_hcd_host0: sw_hcd host driver <6>[??? 0.065544] sw_hcd_host0 sw_hcd_host0: new USB bus registered, assigned bus number 1 <6>[??? 0.066055] hub 1-0:1.0: USB hub found <6>[??? 0.066081] hub 1-0:1.0: 1 port detected <4>[??? 0.066109] wrn: hcd is not enable, need not start hcd <4>[??? 0.066294] [sw_hcd0]: sw_usb_host0_disable start <4>[??? 0.066306] -------sw_hcd0_soft_disconnect--------- <4>[??? 0.066318] [sw_hcd_host0]: Set USB Power OFF <4>[??? 0.066330] wrn: hcd is not enable, need not stop hcd <4>[??? 0.066359] [sw_hcd0]: close_usb_clock <4>[??? 0.066401] [sw_hcd0]: sw_usb_host0_disable end <4>[??? 0.066435] [sw_udc]: udc_init: version 20080411 <6>[??? 0.066779] NET: Registered protocol family 2 <6>[??? 0.066898] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) <6>[??? 0.067167] TCP established hash table entries: 16384 (order: 5, 131072 bytes) <6>[??? 0.067393] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) <6>[??? 0.067524] TCP: Hash tables configured (established 16384 bind 16384) <6>[??? 0.067535] TCP reno registered <6>[??? 0.067545] UDP hash table entries: 256 (order: 0, 4096 bytes) <6>[??? 0.067562] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) <6>[??? 0.067713] NET: Registered protocol family 1 <6>[??? 0.068048] RPC: Registered named UNIX socket transport module. <6>[??? 0.068060] RPC: Registered udp transport module. <6>[??? 0.068070] RPC: Registered tcp transport module. <6>[??? 0.068077] RPC: Registered tcp NFSv4.1 backchannel transport module. <6>[??? 0.068248] Trying to unpack rootfs image as initramfs... <6>[??? 0.088748] Freeing initrd memory: 172K <4>[??? 0.088869] [pm]aw_pm_init! <6>[??? 0.088884] standby_mode = 0. <3>[??? 0.088890] aw_pm_init: not support super standby. <6>[??? 0.089094] audit: initializing netlink socket (disabled) <5>[??? 0.089143] type=2000 audit(0.079:1): initialized <6>[??? 0.099245] ashmem: initialized <5>[??? 0.105165] VFS: Disk quotas dquot_6.5.2 <4>[??? 0.105332] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) <6>[??? 0.108194] NTFS driver 2.1.30 [Flags: R/W]. <6>[??? 0.108506] fuse init (API version 7.16) <6>[??? 0.109065] msgmni has been set to 706 <6>[??? 0.113615] alg: No test for stdrng (krng) <6>[??? 0.113887] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) <6>[??? 0.113904] io scheduler noop registered <6>[??? 0.113912] io scheduler deadline registered <6>[??? 0.113997] io scheduler cfq registered (default) <6>[??? 0.114649] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled <6>[??? 0.116326] brd: module loaded <6>[??? 0.118076] loop: module loaded <4>[??? 0.118092] [NAND]nand driver, init. <4>[??? 0.118103] [NAND] nand driver version: 0x2, 0x10, data: 20120610 <4>[??? 0.118111] [NAND] nand clk request start <4>[??? 0.118137] [NAND] nand clk request ok! <4>[??? 0.118183] [NAND] nand gpio_request <4>[??? 0.118224] [NAND] nand gpio_request fail <4>[??? 0.118238] NAND_RequestDMA? ok <4>[??? 0.118634] [NAND] nand driver version: 0x2 0x10 <4>[??? 0.118667] nand interrupte register ok <4>[??? 0.154567] The 0 disk name = bootloader, class name = DISK, disk size = -544396252 <4>[??? 0.154585] The 1 disk name = env, class name = DISK, disk size = -544396188 <4>[??? 0.154595] The 2 disk name = boot, class name = DISK, disk size = -544396124 <4>[??? 0.154605] The 3 disk name = system, class name = DISK, disk size = -544396060 <4>[??? 0.154614] The 4 disk name = data, class name = DISK, disk size = -544395996 <4>[??? 0.154624] The 5 disk name = misc, class name = DISK, disk size = -544395932 <4>[??? 0.154634] The 6 disk name = recovery, class name = DISK, disk size = -544395868 <4>[??? 0.154645] The 7 disk name = cache, class name = DISK, disk size = -544395804 <4>[??? 0.154655] The 8 disk name = databk, class name = DISK, disk size = -544395740 <4>[??? 0.154665] The 9 disk name = UDISK, class name = DISK, disk size = -544395676 <4>[??? 0.154675] The 9 disk size = 3962880 <4>[??? 0.154681] part total count = 10 <6>[??? 0.156030]? nanda: <6>[??? 0.157526]? nandb: unknown partition table <6>[??? 0.158975]? nandc: unknown partition table <6>[??? 0.160818]? nandd: unknown partition table <6>[??? 0.162599]? nande: unknown partition table <6>[??? 0.164028]? nandf: unknown partition table <6>[??? 0.165436]? nandg: unknown partition table <6>[??? 0.167163]? nandh: unknown partition table <6>[??? 0.168546]? nandi: unknown partition table <6>[??? 0.169737]? nandj: <6>[??? 0.169908] benn: nand probe enter <4>[??? 0.169951] [NAND]nand driver, ok. <4>[??? 0.170385] drivers/spi/spi_sunxi.c(L2114) sw spi init fetch spi0 uning configuration failed <4>[??? 0.170411] drivers/spi/spi_sunxi.c(L2005) Get spi devices number failed <4>[??? 0.170422] drivers/spi/spi_sunxi.c(L2124) register spi devices board info failed <4>[??? 0.170432] cannot find any using configuration for all spi controllers! <6>[??? 0.170455] PPP generic driver version 2.4.2 <6>[??? 0.170684] PPP Deflate Compression module registered <6>[??? 0.170695] PPP BSD Compression module registered <6>[??? 0.171698] PPP MPPE Compression module registered <6>[??? 0.171715] NET: Registered protocol family 24 <6>[??? 0.171762] PPTP driver version 0.8.5 <6>[??? 0.172107] tun: Universal TUN/TAP device driver, 1.6 <6>[??? 0.172115] tun: (C) 1999-2004 Max Krasnyansky <6>[??? 0.172391] usbcore: registered new interface driver cdc_ether <6>[??? 0.172445] usbcore: registered new interface driver cdc_eem <6>[??? 0.172501] usbcore: registered new interface driver cdc_subset <6>[??? 0.172547] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver <6>[??? 0.172613] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver <6>[??? 0.172657] Initializing USB Mass Storage driver... <6>[??? 0.172755] usbcore: registered new interface driver usb-storage <6>[??? 0.172766] USB Mass Storage support registered. <6>[??? 0.172820] usbcore: registered new interface driver ums-alauda <6>[??? 0.172869] usbcore: registered new interface driver ums-cypress <6>[??? 0.172914] usbcore: registered new interface driver ums-datafab <6>[??? 0.172959] usbcore: registered new interface driver ums_eneub6250 <6>[??? 0.173006] usbcore: registered new interface driver ums-freecom <6>[??? 0.173051] usbcore: registered new interface driver ums-isd200 <6>[??? 0.173095] usbcore: registered new interface driver ums-jumpshot <6>[??? 0.173147] usbcore: registered new interface driver ums-karma <6>[??? 0.173192] usbcore: registered new interface driver ums-onetouch <6>[??? 0.173250] usbcore: registered new interface driver ums-realtek <6>[??? 0.173304] usbcore: registered new interface driver ums-sddr09 <6>[??? 0.173352] usbcore: registered new interface driver ums-sddr55 <6>[??? 0.173398] usbcore: registered new interface driver ums-usbat <6>[??? 0.173533] usbcore: registered new interface driver usbserial <6>[??? 0.173577] USB Serial support registered for generic <6>[??? 0.173629] usbcore: registered new interface driver usbserial_generic <6>[??? 0.173638] usbserial: USB Serial Driver core <6>[??? 0.173675] USB Serial support registered for GSM modem (1-port) <6>[??? 0.173796] usbcore: registered new interface driver option <6>[??? 0.173805] option: v0.7.2:USB Driver for GSM modems <4>[??? 0.173840] ------print_msc_config----- <4>[??? 0.173849] vendor_id???????????? = 0x18d1 <4>[??? 0.173855] mass_storage_id?????? = 0x1 <4>[??? 0.173861] adb_id??????????????? = 0x2 <4>[??? 0.173867] usb_manufacturer_name = USB Developer <4>[??? 0.173874] usb_product_name????? = Android <4>[??? 0.173882] usb_serial_number???? = 20080411 <4>[??? 0.173889] msc_vendor_name?????? = USB 2.0 <4>[??? 0.173895] msc_product_name????? = USB Flash Driver <4>[??? 0.173902] msc_release?????????? = 100 <4>[??? 0.173908] luns????????????????? = 2 <4>[??? 0.173914] --------------------------- <4>[??? 0.174068] [sw_udc]: [sw_usb_udc]: binding gadget driver 'android_usb' <4>[??? 0.174083] [sw_udc]: alloc request: ep(0xc08e2428, ep0, 64), req(0xdfbe2f80) <4>[??? 0.174101] WRN:L2694(drivers/usb/sun5i_usb/udc/sw_udc.c):ERR: usb device is not active <4>[??? 0.174114] [sw_udc]: sw_udc_pullup, is_on = 0 <4>[??? 0.174124] WRN:L2729(drivers/usb/sun5i_usb/udc/sw_udc.c):ERR: usb device is not active <6>[??? 0.175360] android_usb gadget: Mass Storage Function, version: 2009/09/11 <6>[??? 0.175376] android_usb gadget: Number of LUNs=2 <6>[??? 0.175386]? lun0: LUN: removable file: (no medium) <6>[??? 0.175394]? lun1: LUN: removable file: (no medium) <4>[??? 0.175403] lun name: lun <4>[??? 0.175416] lun name: lun1 <4>[??? 0.175585] WRN:L2694(drivers/usb/sun5i_usb/udc/sw_udc.c):ERR: usb device is not active <6>[??? 0.175606] android_usb gadget: android_usb ready <6>[??? 0.175729] mousedev: PS/2 mouse device common for all mice <6>[??? 0.175979] input: sun4i-keyboard as /devices/virtual/input/input0 <4>[??? 0.176092] ==register_early_suspend = <6>[??? 0.176517] i2c /dev entries driver <4>[??? 0.176649] !!! base_Addr = 0xe08eac00 <4>[??? 0.176674] config i2c gpio with gpio_config api <4>[??? 0.176728] twi0, apb clock = 24000000 <6>[??? 0.178628] axp_mfd 0-0034: AXP (CHIP ID: 0x21) detected <4>[??? 0.179570] rtc_detect,line:197 <6>[??? 0.179581] I2C: i2c-0: AW16XX I2C adapter <4>[??? 0.179587] **********start************ <4>[??? 0.179596] 0x40 <4>[??? 0.179601] 0xf8 <4>[??? 0.179606] 0x28 <4>[??? 0.179611] 0x0 <4>[??? 0.179615] 0x0 <4>[??? 0.179620] **********end************ <4>[??? 0.179662] !!! base_Addr = 0xe08ec000 <4>[??? 0.179714] twi1, apb clock = 24000000 <6>[??? 0.179902] rtc_detect: Detected chip pcf8563 at adapter 1, address 0x51 <6>[??? 0.179973] pcf8563 1-0051: chip found, driver version 0.4.3 <4>[??? 0.183824] rtc (null): alarm rollover not handled <6>[??? 0.184033] using rtc device, pcf8563, for alarms <6>[??? 0.184072] pcf8563 1-0051: rtc core: registered pcf8563 as rtc0 <6>[??? 0.186601] I2C: i2c-1: AW16XX I2C adapter <4>[??? 0.186610] **********start************ <4>[??? 0.186617] 0x40 <4>[??? 0.186621] 0xf8 <4>[??? 0.186626] 0x58 <4>[??? 0.186631] 0x0 <4>[??? 0.186635] 0x0 <4>[??? 0.186639] **********end************ <4>[??? 0.186691] !!! base_Addr = 0xe08ee400 <4>[??? 0.186744] twi2, apb clock = 24000000 <4>[??? 0.186931] rtc_detect,line:197 <6>[??? 0.186941] I2C: i2c-2: AW16XX I2C adapter <4>[??? 0.186947] **********start************ <4>[??? 0.186953] 0x40 <4>[??? 0.186958] 0xf8 <4>[??? 0.186962] 0x58 <4>[??? 0.186967] 0x0 <4>[??? 0.186972] 0x0 <4>[??? 0.186976] **********end************ <6>[??? 0.187130] lirc_dev: IR Remote Control driver registered, major 250 <6>[??? 0.187141] IR NEC protocol handler initialized <6>[??? 0.187148] IR RC5(x) protocol handler initialized <6>[??? 0.187155] IR RC6 protocol handler initialized <6>[??? 0.187162] IR JVC protocol handler initialized <6>[??? 0.187169] IR Sony protocol handler initialized <6>[??? 0.187176] IR RC5 (streamzap) protocol handler initialized <6>[??? 0.187183] IR LIRC bridge handler initialized <6>[??? 0.187190] Linux video capture interface: v2.00 <4>[??? 0.187217] [pa_drv] start!!! <4>[??? 0.187475] [pa_drv] init end!!! <6>[??? 0.187580] print_constraints: axp20_ldo1: 1300 mV <6>[??? 0.188503] print_constraints: axp20_ldo2: 1800 <--> 3300 mV at 3000 mV <6>[??? 0.189418] print_constraints: axp20_ldo3: 700 <--> 3500 mV at 3300 mV <6>[??? 0.190356] print_constraints: axp20_ldo4: 1250 <--> 3300 mV at 3300 mV <6>[??? 0.191248] print_constraints: axp20_buck2: 700 <--> 2275 mV at 1400 mV <6>[??? 0.192144] print_constraints: axp20_buck3: 700 <--> 3500 mV at 1200 mV <6>[??? 0.192546] print_constraints: axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV <6>[??? 0.192815] input: axp20-supplyer as /devices/platform/sun5i-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input1 <4>[??? 0.200101] pmu_pekoff_time = 6000 <4>[??? 0.200111] pmu_pekoff_en = 1 <4>[??? 0.200117] pmu_peklong_time = 1500 <4>[??? 0.200123] pmu_pekon_time = 1000 <4>[??? 0.200128] pmu_pwrok_time = 64 <4>[??? 0.200134] pmu_pwrnoe_time = 2000 <4>[??? 0.200140] pmu_intotp_en = 1 <4>[??? 0.200613] [AXP]POWER20_OFF_CTL:1974-->0x42 <4>[??? 0.201086] POWER20_PEK_SET:1991-->0x9d <4>[??? 0.201558] POWER20_PEK_SET:2002-->0x9d <4>[??? 0.202030] POWER20_PEK_SET:2011-->0x9d <4>[??? 0.202503] POWER20_PEK_SET:2022-->0x9d <4>[??? 0.202974] POWER20_PEK_SET:2034-->0x9d <4>[??? 0.203446] POWER20_HOTOVER_CTL:2043-->0xad <4>[??? 0.206724] [AXP]last_rest_vol = 90, now_rest_vol = 90 <4>[??? 0.208240] [AXP]Cur_CoulombCounter?????? = 1004 <4>[??? 0.208249] [AXP]charger->rest_vol = 90 <6>[??? 0.211110] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel at redhat.com <6>[??? 0.211544] device-mapper: multipath: version 1.3.0 loaded <6>[??? 0.211559] device-mapper: multipath round-robin: version 1.0.0 loaded <6>[??? 0.211570] device-mapper: multipath queue-length: version 0.1.0 loaded <6>[??? 0.211585] device-mapper: multipath service-time: version 0.2.0 loaded <4>[??? 0.212095] [mmc_pm]: no sdio card used in configuration <4>[??? 0.212107] [mmc]: sunximmc_init <4>[??? 0.212221] [mmc]: sunxi mmc controller using config : 0x1 <4>[??? 0.212279] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0 <4>[??? 0.212592] [mmc]: mmc 0 power off !! <4>[??? 0.212679] [mmc]: mmc0 Probe: base:0xe08f0000 irq:32 dma:0 pdes:0xdf02c000, ret 0. <6>[??? 0.213374] usbcore: registered new interface driver usbhid <6>[??? 0.213383] usbhid: USB HID core driver <6>[??? 0.213864] logger: created 256K log 'log_main' <6>[??? 0.213946] logger: created 256K log 'log_events' <6>[??? 0.214017] logger: created 256K log 'log_radio' <6>[??? 0.214087] logger: created 256K log 'log_system' <4>[??? 0.214620] enter sun5i Audio codec!!! <6>[??? 0.215319] sun5i audio support initialized <4>[??? 0.215543] sun5i Audio codec successfully loaded.. <6>[??? 0.215599] ALSA device list: <6>[??? 0.215607]?? #0: sun5i-CODEC? Audio Codec <6>[??? 0.215779] Netfilter messages via NETLINK v0.30. <6>[??? 0.215867] nf_conntrack version 0.5.0 (5652 buckets, 22608 max) <6>[??? 0.216351] ctnetlink v0.93: registering with nfnetlink. <6>[??? 0.216367] NF_TPROXY: Transparent proxy support initialized, version 4.1.0 <6>[??? 0.216376] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd. <6>[??? 0.216661] IPv4 over IPv4 tunneling driver <6>[??? 0.216971] GRE over IPv4 demultiplexor driver <6>[??? 0.216981] GRE over IPv4 tunneling driver <6>[??? 0.217468] ip_tables: (C) 2000-2006 Netfilter Core Team <6>[??? 0.217629] TCP cubic registered <6>[??? 0.217639] Initializing XFRM netlink socket <6>[??? 0.218366] NET: Registered protocol family 10 <6>[??? 0.219178] ip6_tables: (C) 2000-2006 Netfilter Core Team <6>[??? 0.219346] IPv6 over IPv4 tunneling driver <6>[??? 0.220282] NET: Registered protocol family 17 <6>[??? 0.220328] NET: Registered protocol family 15 <6>[??? 0.220343] L2TP core driver, V2.0 <6>[??? 0.220359] PPPoL2TP kernel driver, V2.0 <6>[??? 0.220366] L2TP IP encapsulation support (L2TPv3) <6>[??? 0.220617] L2TP netlink interface <6>[??? 0.220654] L2TP ethernet pseudowire support (L2TPv3) <6>[??? 0.220663] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 <5>[??? 0.220694] Registering SWP/SWPB emulation handler <4>[??? 0.220961] dram_sysdev_init finished! <6>[??? 0.221956] registered taskstats version 1 <4>[??? 0.221985] [LCD] lcd_module_init <4>[??? 0.793657] regulator_init_complete: axp20_buck3: incomplete constraints, leaving on <4>[??? 0.793936] regulator_init_complete: axp20_buck2: incomplete constraints, leaving on <4>[??? 0.794206] regulator_init_complete: axp20_ldo4: incomplete constraints, leaving on <4>[??? 0.794473] regulator_init_complete: axp20_ldo3: incomplete constraints, leaving on <4>[??? 0.794740] regulator_init_complete: axp20_ldo2: incomplete constraints, leaving on <4>[??? 0.795727] [sw-ehci1]: probe, pdev->name: sw-ehci, pdev->id: 1, sw_ehci: 0xc09a957c <4>[??? 0.795758] [sw-ehci1]: open clock <4>[??? 0.815772] usb_passby en=1,passly=0 <4>[??? 0.815781] hci_port_configure en=1,config_cnt=0 <4>[??? 0.815790] [sw-ehci1]: Set USB Power ON <6>[??? 0.816539] sw-ehci sw-ehci.1: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver <6>[??? 0.816578] sw-ehci sw-ehci.1: new USB bus registered, assigned bus number 2 <6>[??? 0.816695] sw-ehci sw-ehci.1: irq 39, io mem 0xf1c14000 <6>[??? 0.830049] sw-ehci sw-ehci.1: USB 0.0 started, EHCI 1.00 <4>[??? 0.830061] ehci_irq: port change detect <6>[??? 0.830617] hub 2-0:1.0: USB hub found <6>[??? 0.830646] hub 2-0:1.0: 1 port detected <4>[??? 0.830877] [sw-ehci1]: sw_usb_disable_ehci <4>[??? 0.830891] [sw-ehci1]: remove, pdev->name: sw-ehci, pdev->id: 1, sw_ehci: 0xc09a957c <6>[??? 0.830903] sw-ehci sw-ehci.1: remove, state 1 <6>[??? 0.830921] usb usb2: USB disconnect, device number 1 <6>[??? 0.831764] sw-ehci sw-ehci.1: USB bus 2 deregistered <4>[??? 0.831781] [sw-ehci1]: Set USB Power OFF <4>[??? 0.832268] hci_port_configure en=0,config_cnt=1 <4>[??? 0.832277] usb_passby en=0,passly=1 <4>[??? 0.832284] [sw-ehci1]: close clock <4>[??? 0.832437] [sw-ohci1]: probe, pdev->name: sw-ohci, pdev->id: 1, sw_ohci: 0xc09a9694 <4>[??? 0.832451] [sw-ohci1]: open clock <4>[??? 0.852472] hci_port_configure en=1,config_cnt=0 <4>[??? 0.852481] usb_passby en=1,passly=0 <4>[??? 0.852489] [sw-ohci1]: Set USB Power ON <6>[??? 0.853231] sw-ohci sw-ohci.1: SW USB2.0 'Open' Host Controller (OHCI) Driver <6>[??? 0.853261] sw-ohci sw-ohci.1: new USB bus registered, assigned bus number 2 <6>[??? 0.853302] sw-ohci sw-ohci.1: irq 40, io mem 0xf1c14400 <6>[??? 0.914457] hub 2-0:1.0: USB hub found <6>[??? 0.914479] hub 2-0:1.0: 1 port detected <4>[??? 0.914677] [sw-ohci1]: sw_usb_disable_ohci <4>[??? 0.914688] [sw-ohci1]: remove, pdev->name: sw-ohci, pdev->id: 1, sw_ohci: 0xc09a9694 <6>[??? 0.914699] sw-ohci sw-ohci.1: remove, state 1 <6>[??? 0.914713] usb usb2: USB disconnect, device number 1 <6>[??? 0.915049] sw-ohci sw-ohci.1: USB bus 2 deregistered <4>[??? 0.915064] [sw-ohci1]: Set USB Power OFF <4>[??? 0.915549] usb_passby en=0,passly=1 <4>[??? 0.915557] hci_port_configure en=0,config_cnt=1 <4>[??? 0.915564] [sw-ohci1]: close clock <6>[??? 0.916625] pcf8563 1-0051: setting system clock to 2013-06-14 11:02:45 UTC (1371207765) <4>[??? 0.916747] Warning: unable to open an initial console. <6>[??? 0.916796] Freeing init memory: 168K <3>[??? 0.971630] init: width = 800 <3>[??? 0.971656] init: height = 480 <3>[??? 0.971667] init: s.st_size = 1536000 ... ... ... <6>[??? 1.295889] init: Created socket '/dev/socket/zygote' with mode '666', user '0', group '0' <6>[??? 1.296196] init: Created socket '/dev/socket/dnsproxyd' with mode '660', user '0', group '3003' <6>[??? 1.297621] init: Created socket '/dev/socket/netd' with mode '660', user '0', group '1000' <6>[??? 1.299364] init: Created socket '/dev/socket/dbus' with mode '660', user '1002', group '1002' <6>[??? 1.300550] init: Created socket '/dev/socket/vold' with mode '660', user '0', group '1009' <6>[??? 1.301696] init: Created socket '/dev/socket/installd' with mode '600', user '1000', group '1000' <6>[??? 1.305700] init: Created socket '/dev/socket/keystore' with mode '666', user '0', group '0' <6>[??? 1.306935] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000' <6>[??? 1.312972] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001' <4>[??? 1.367459] UMP<2>: Inserting UMP device driver. Compiled: Nov 22 2012, time: 14:25:21 <4>[??? 1.368754] UMP<2>: Using OS memory backend, allocation limit: 134217728 <4>[??? 1.368775] UMP: UMP device driver? loaded <6>[??? 1.369051] init: command 'insmod' r=0 <4>[??? 1.551696] Mali: Mali device driver? loaded <6>[??? 1.552220] init: command 'insmod' r=0 <4>[??? 1.581883] ======mma7660_init=========. <4>[??? 1.581905] ========gsensor_fetch_sysconfig_para=================== <4>[??? 1.581935] gsensor_fetch_sysconfig_para: after: gsensor_twi_addr is 0x4c, dirty_addr_buf: 0x4c. dirty_addr_buf[1]: 0xfffe <4>[??? 1.581949] gsensor_fetch_sysconfig_para: twi_id is 1. <4>[??? 1.581958] mma7660_init: after fetch_sysconfig_para:? normal_i2c: 0x4c. normal_i2c[1]: 0xfffe <6>[??? 1.582262] gsensor_detect: Detected chip mma7660 at adapter 1, address 0x4c <6>[??? 1.582449] mma7660 probe <6>[??? 1.805285] mma7660 1-004c: build time Nov? 7 2012 23:09:29 <6>[??? 1.806517] input: mma7660 as /devices/virtual/input/input2 <4>[??? 1.807486] <4>[??? 1.807495]? is_mma7660 is here <4>[??? 1.807499] <6>[??? 1.807542] add mma7660 i2c driver <6>[??? 1.807684] init: command 'insmod' r=0 <4>[??? 1.833691] dmard06: init <4>[??? 1.833712] ========gsensor_fetch_sysconfig_para================== <4>[??? 1.833747] gsensor_fetch_sysconfig_para: after: gsensor_twi_addr is 0x1c, dirty_addr_buf: 0x1c. dirty_addr_buf[1]: 0xfffe <4>[??? 1.833761] gsensor_fetch_sysconfig_para: twi_id is 1. <4>[??? 1.833775] err: gpio count < =0 ,gpio_count is: 0 <4>[??? 1.833785] dmard06_init: after fetch_sysconfig_para:? normal_i2c: 0x1c. normal_i2c[1]: 0xfffe <6>[??? 1.834178] gsensor_detect: Detected chip dmard06 at adapter 1, address 0x1c <4>[??? 1.836851] [i2c1] incomplete xfer (0x20) <4>[??? 1.837057] [i2c1] incomplete xfer (0x48) <6>[??? 1.837066] i2c Read SW_RESET = 0 <4>[??? 1.837250] [i2c1] incomplete xfer (0x20) <4>[??? 1.837514] [i2c1] incomplete xfer (0x48) <6>[??? 1.837522] i2c Read WHO_AM_I = 0 <4>[??? 1.837529] dmard06 gsensor I2C err = 0! <4>[??? 1.837563] dmard06 probe failed <4>[??? 1.837593] dmard06: probe of 1-001c failed with error -1 <6>[??? 1.837747] init: command 'insmod' r=0 <4>[??? 1.856089] ========gsensor_fetch_sysconfig_para=================== <4>[??? 1.856136] gsensor_fetch_sysconfig_para: after: gsensor_twi_addr is 0x18, dirty_addr_buf: 0x18. dirty_addr_buf[1]: 0xfffe <4>[??? 1.856151] gsensor_fetch_sysconfig_para: twi_id is 1. <4>[??? 1.856160] BMA250_init: after fetch_sysconfig_para:? normal_i2c: 0x18. normal_i2c[1]: 0xfffe <6>[??? 1.856493] gsensor_detect: Detected chip bma250 at adapter 1, address 0x18 <4>[??? 1.856969] [i2c1] incomplete xfer (0x20) <6>[??? 1.856982] Bosch Sensortec Device not found,???????????????????????????? i2c error -70 <4>[??? 1.857001] bma250: probe of 1-0018 failed with error -1 <6>[??? 1.857261] init: command 'insmod' r=0 <4>[??? 1.884726] [cedar dev]: install start!!! <4>[??? 1.886412] [cedar dev]: install end!!! <6>[??? 1.886591] init: command 'insmod' r=0 <6>[??? 1.907638] init: command 'insmod' r=0 <6>[??? 1.931194] init: command 'insmod' r=0 <6>[??? 1.951837] init: command 'insmod' r=0 <6>[??? 2.006632] [CSI]Welcome to CSI driver <6>[??? 2.006652] [CSI]csi_init <6>[??? 2.009144] [CSI]registered sub device,input_num = 0 <6>[??? 2.009193] [CSI]power on and power off camera! <6>[??? 2.618739] [CSI]V4L2 device registered as video0 <6>[??? 2.618967] init: command 'insmod' r=0 <6>[??? 2.642642] usbcore: registered new interface driver asix <6>[??? 2.642935] init: command 'insmod' r=0 <6>[??? 2.662829] usbcore: registered new interface driver qf9700 <6>[??? 2.662995] init: command 'insmod' r=0 <6>[??? 2.680584] usbcore: registered new interface driver MOSCHIP usb-ethernet driver <6>[??? 2.680799] init: command 'insmod' r=0 <6>[??? 2.700440] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver <6>[??? 2.700823] usbcore: registered new interface driver rtl8150 <6>[??? 2.701037] init: command 'insmod' r=0 <6>[??? 2.719326] ===========================ft5x_ts_init===================== <6>[??? 2.719350] ctp_fetch_sysconfig_para. <6>[??? 2.719375] ctp_fetch_sysconfig_para: after: ctp_twi_addr is 0x38, dirty_addr_buf: 0x38. dirty_addr_buf[1]: 0xfffe <6>[??? 2.719389] ctp_fetch_sysconfig_para: ctp_twi_id is 1. <6>[??? 2.719401] ctp_fetch_sysconfig_para: screen_max_x = 800. <6>[??? 2.719410] ctp_fetch_sysconfig_para: screen_max_y = 480. <6>[??? 2.719420] ctp_fetch_sysconfig_para: revert_x_flag = 0. <6>[??? 2.719429] ctp_fetch_sysconfig_para: revert_y_flag = 1. <6>[??? 2.719439] ctp_fetch_sysconfig_para: exchange_x_y_flag = 1. <6>[??? 2.719448] ft5x_ts_init: after fetch_sysconfig_para:? normal_i2c: 0x38. normal_i2c[1]: 0xfffe <6>[??? 2.719502] ctp_reset. <6>[??? 2.761507] ctp_wakeup. <4>[??? 2.765204] UMP<2>: New session opened <6>[??? 2.821381] ctp_detect: Detected chip ft5x_ts at adapter 1, address 0x38 <6>[??? 2.821840] ====ft5x_ts_probe begin=====.? <4>[??? 2.821854] Testing FT touch...... <4>[??? 2.823792] FT touch i2c transfer succeed! <6>[??? 2.824153] input: ft5x_ts as /devices/virtual/input/input3 <6>[??? 2.824436] ==register_early_suspend = ... ... ... root at android:/ # cat /proc/modules ft5x_ts 45529 0 - Live 0xbf0a6000 rtl8150 10305 0 - Live 0xbf09f000 mcs7830 7581 0 - Live 0xbf099000 qf9700 9152 0 - Live 0xbf092000 asix 24601 0 - Live 0xbf086000 sun5i_csi0 33255 0 - Live 0xbf078000 gc0308 18408 1 - Live 0xbf06f000 videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf06a000 videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf060000 cedarx 9351 0 - Live 0xbf059000 bma250 7869 0 - Live 0xbf053000 dmard06 11443 0 - Live 0xbf04c000 mma7660 7193 0 - Live 0xbf046000 mali 150828 6 - Live 0xbf014000 ump 49174 11 mali, Live 0xbf000000 1|root at android:/ # df Filesystem???????????? Size?? Used?? Free?? Blksize /dev?????????????????? 176M??? 44K?? 176M?? 4096 /mnt/asec????????????? 176M???? 0K?? 176M?? 4096 /mnt/obb?????????????? 176M???? 0K?? 176M?? 4096 /system??????????????? 377M?? 246M?? 131M?? 4096 /data???????????????? 1007M?? 251M?? 756M?? 4096 /cache???????????????? 251M???? 4M?? 247M?? 4096 /mnt/sdcard????????????? 1G??? 17M???? 1G?? 4096 /mnt/secure/asec???????? 1G??? 17M???? 1G?? 4096 /mnt/asec/com.shootbubble.bubbledexlue-1???? 3M???? 1M???? 1M?? 4096 /mnt/asec/com.wyse.pocketcloudfree-1??? 14M??? 12M???? 1M?? 4096 root at android:/ # mount rootfs / rootfs rw 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 /dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0 /dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0 /dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/dm-0 /mnt/asec/com.shootbubble.bubbledexlue-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/dm-1 /mnt/asec/com.wyse.pocketcloudfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 root at android:/ # cd /pr?? root at android:/ # cd /proc/???????????????????????????????????????????????????? root at android:/ # cd /proc/???????????????????????????????????????????????????? de??????? root at android:/ # cd /proc/devices?????????????????????????????????????????????? root at android:/ # cd /proc/devices????????????????????????????????????????????? /system/bin/sh: cd: /proc/devices - Not a directory 1|root at android:/ # cat /proc/devices Character devices: ? 1 mem ? 4 /dev/vc/0 ? 4 tty ? 4 ttyS ? 5 /dev/tty ? 5 /dev/console ? 5 /dev/ptmx ? 7 vcs ?10 misc ?13 input ?29 fb ?81 video4linux ?89 i2c 108 ppp 116 alsa 125 aw_i2c_ts 128 ptm 136 pts 150 cedar_dev 180 usb 188 ttyUSB 189 usb_device 229 ump 230 mali 248 lcd 249 pa_chrdev 250 BaseRemoteCtl 251 ttyGS 252 disp 253 bsg 254 rtc Block devices: ? 1 ramdisk 259 blkext ? 7 loop ? 8 sd ?11 sr ?65 sd ?66 sd ?67 sd ?68 sd ?69 sd ?70 sd ?71 sd ?93 nand 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 179 mmc 254 device-mapper root at android:/ # cd /proc/ root at android:/proc # cat cpuinfo Processor?????? : ARMv7 Processor rev 2 (v7l) BogoMIPS??????? : 1001.88 Features??????? : swp half thumb fastmult vfp edsp neon vfpv3 CPU implementer : 0x41 CPU architecture: 7 CPU variant???? : 0x3 CPU part??????? : 0xc08 CPU revision??? : 2 Hardware??????? : sun5i Revision??????? : a13b Serial????????? : 01c0f06339313030504d4e33162542c4 root at android:/proc # ps USER???? PID?? PPID? VSIZE? RSS???? WCHAN??? PC???????? NAME root????? 1???? 0???? 348??? 208?? c011baa4 00008658 S /init root????? 2???? 0???? 0????? 0???? c008f3c4 00000000 S kthreadd root????? 3???? 2???? 0????? 0???? c00794e0 00000000 S ksoftirqd/0 root????? 4???? 2???? 0????? 0???? c008aeb8 00000000 S kworker/0:0 root????? 5???? 2???? 0????? 0???? c008aeb8 00000000 S kworker/u:0 root????? 6???? 2???? 0????? 0???? c00beb3c 00000000 S rcu_kthread root????? 7???? 2???? 0????? 0???? c008a164 00000000 S cpuset root????? 8???? 2???? 0????? 0???? c008a164 00000000 S khelpe root????? 9???? 2???? 0????? 0???? c008a164 00000000 S netns root????? 10??? 2???? 0????? 0???? c008a164 00000000 S suspend root????? 11??? 2???? 0????? 0???? c00e51e0 00000000 S sync_supers root????? 12??? 2???? 0????? 0???? c00e5d48 00000000 S bdi-default root????? 13??? 2???? 0????? 0???? c008a164 00000000 S kintegrityd root????? 14??? 2???? 0????? 0???? c008a164 00000000 S kblockd root????? 15??? 2???? 0????? 0???? c03865c8 00000000 S khubd root????? 16??? 2???? 0????? 0???? c008a164 00000000 S cpufreq_uevent root????? 17??? 2???? 0????? 0???? c008a164 00000000 S cfg80211 root????? 18??? 2???? 0????? 0???? c008aeb8 00000000 S kworker/0:1 root????? 19??? 2???? 0????? 0???? c00800f4 00000000 D usb-hardware-sc root????? 20??? 2???? 0????? 0???? c008a164 00000000 S rpciod root????? 21??? 2???? 0????? 0???? c00de530 00000000 S kswapd0 root????? 22??? 2???? 0????? 0???? c0102040 00000000 S ksmd root????? 23??? 2???? 0????? 0???? c0142044 00000000 S fsnotify_mark root????? 24??? 2???? 0????? 0???? c008a164 00000000 S nfsiod root????? 25??? 2???? 0????? 0???? c008a164 00000000 S crypto root????? 39??? 2???? 0????? 0???? c03345fc 00000000 S nandd root????? 40??? 2???? 0????? 0???? c0333fb8 00000000 S nfmtd root????? 41??? 2???? 0????? 0???? c008aeb8 00000000 S kworker/u:1 root????? 48??? 2???? 0????? 0???? c008a164 00000000 S f_mtp root????? 49??? 2???? 0????? 0???? c03c35a8 00000000 S file-storage root????? 50??? 2???? 0????? 0???? c008a164 00000000 S kpsmoused root????? 51??? 2???? 0????? 0???? c008a164 00000000 S kmpathd root????? 52??? 2???? 0????? 0???? c008a164 00000000 S kmpath_handlerd root????? 53??? 2???? 0????? 0???? c008f0d8 00000000 D kinteractiveup root????? 54??? 2???? 0????? 0???? c008a164 00000000 S kfantasy root????? 55??? 2???? 0????? 0???? c008a164 00000000 S binder root????? 56??? 2???? 0????? 0???? c008a164 00000000 S codec_resume root????? 57??? 1???? 316??? 164?? c011baa4 00008658 S /sbin/ueventd root????? 58??? 2???? 0????? 0???? c01ddee0 00000000 S jbd2/nandd-8 root????? 59??? 2???? 0????? 0???? c008a164 00000000 S ext4-dio-unwrit root????? 62??? 2???? 0????? 0???? c012e624 00000000 S flush-93:0 root????? 66??? 2???? 0????? 0???? c01ddee0 00000000 S jbd2/nande-8 root????? 67??? 2???? 0????? 0???? c008a164 00000000 S ext4-dio-unwrit root????? 73??? 2???? 0????? 0???? c01ddee0 00000000 S jbd2/nandh-8 root????? 74??? 2???? 0????? 0???? c008a164 00000000 S ext4-dio-unwrit system??? 77??? 1???? 832??? 276?? c045c5b8 40049690 S /system/bin/servicemanager root????? 78??? 1???? 4032?? 784?? ffffffff 400dbc94 S /system/bin/vold root????? 79??? 1???? 7460?? 1020? ffffffff ffff0520 S /system/bin/netd root????? 80??? 1???? 696??? 268?? c04908c8 40046f98 S /system/bin/debuggerd system??? 81??? 1???? 34792? 5172? ffffffff 400c6690 S /system/bin/surfaceflinger root????? 82??? 1???? 148916 35276 ffffffff 400507b4 S zygote drm?????? 83??? 1???? 12444? 3920? ffffffff 40150690 S /system/bin/drmserver media???? 84??? 1???? 34524? 6784? ffffffff 4012c690 S /system/bin/mediaserver bluetooth 85??? 1???? 1336?? 584?? c011baa4 40060438 S /system/bin/dbus-daemon root????? 86??? 1???? 844??? 320?? c0534d70 4004b458 S /system/bin/installd keystore? 87??? 1???? 1736?? 540?? c04908c8 400c7f98 S /system/bin/keystore root????? 88??? 1???? 868??? 344?? c011baa4 400a6438 S /system/bin/u3gmonitor root????? 89??? 1???? 4516?? 784?? ffffffff 400aec94 S /system/bin/rild root????? 90??? 2???? 0????? 0???? c008a164 00000000 S mali-pmm-wq root????? 118?? 2???? 0????? 0???? c008a164 00000000 S 1-0038 root????? 120?? 1???? 4468?? 204?? ffffffff 0000825c S /sbin/adbd system??? 147?? 82??? 247632 48792 ffffffff 40050690 S system_server root????? 167?? 2???? 0????? 0???? c008aeb8 00000000 S kworker/u:2 system??? 214?? 82??? 164788 37696 ffffffff 400513c0 S com.android.systemui app_17??? 254?? 82??? 171520 31972 ffffffff 400513c0 S com.google.android.gsf.login app_10??? 275?? 82??? 161136 30412 ffffffff 400513c0 S android.process.media app_53??? 290?? 82??? 161800 30124 ffffffff 400513c0 S com.spartacusrex.spartacuside app_17??? 303?? 82??? 197596 39136 ffffffff 400513c0 S com.google.process.gapps radio???? 323?? 82??? 169624 31604 ffffffff 400513c0 S com.android.phone app_23??? 339?? 82??? 190600 40828 ffffffff 400513c0 S com.android.launcher app_37??? 392?? 82??? 157416 26724 ffffffff 400513c0 S com.android.smspush app_0???? 430?? 82??? 165040 33296 ffffffff 400513c0 S android.process.acore app_17??? 449?? 82??? 168360 31188 ffffffff 400513c0 S com.google.android.gms app_17??? 466?? 82??? 174600 33872 ffffffff 400513c0 S com.google.process.location app_5???? 562?? 82??? 158728 29032 ffffffff 400513c0 S com.android.providers.calendar root????? 575?? 2???? 0????? 0???? c0331300 00000000 S loop0 root????? 577?? 2???? 0????? 0???? c008a164 00000000 S kdmflush root????? 590?? 2???? 0????? 0???? c008a164 00000000 S kcryptd_io root????? 591?? 2???? 0????? 0???? c008a164 00000000 S kcryptd root????? 607?? 2???? 0????? 0???? c0331300 00000000 S loop1 root????? 608?? 2???? 0????? 0???? c008a164 00000000 S kdmflush root????? 609?? 2???? 0????? 0???? c008a164 00000000 S kcryptd_io root????? 610?? 2???? 0????? 0???? c008a164 00000000 S kcryptd app_15??? 654?? 82??? 166776 32228 ffffffff 400513c0 S com.google.android.gm app_19??? 681?? 82??? 159564 28820 ffffffff 400513c0 S com.google.android.partnersetup app_35??? 715?? 82??? 185764 34744 ffffffff 400513c0 S com.android.vending app_45??? 752?? 82??? 161176 29960 ffffffff 400513c0 S org.mozilla.firefox app_52??? 770?? 82??? 157976 27172 ffffffff 400513c0 S com.rechild.advancedtaskkiller app_4???? 790?? 82??? 161848 28896 ffffffff 400513c0 S com.android.calendar app_20??? 807?? 82??? 160264 27984 ffffffff 400513c0 S com.google.android.googlequicksearchbox app_32??? 824?? 82??? 159584 28108 ffffffff 400513c0 S com.android.quicksearchbox app_14??? 845?? 82??? 158920 28644 ffffffff 400513c0 S com.android.gallery3d system??? 871?? 82??? 178804 36200 ffffffff 400513c0 S com.android.settings root????? 895?? 120?? 776??? 416?? c003c718 4005fe74 S /system/bin/sh root????? 936?? 895?? 956??? 336?? 00000000 400a6458 R ps root at android:/proc # cd /system root at android:/system # ls app bin build.prop etc fonts framework gsensors lib media preinstall tts usr vendor xbin root at android:/system # ls / acct cache config d data default.prop dev etc init init.goldfish.rc init.rc init.sun5i.rc init.sun5i.usb.rc initlogo.rle mnt proc root sbin sdcard sys system ueventd.goldfish.rc ueventd.rc ueventd.sun5i.rc vendor root at android:/system # cd /etc root at android:/etc # ls 3g_dongle.cfg NOTICE.html.gz apns-conf.xml audio_effects.conf bluetooth camera.cfg dbus.conf dhcpcd event-log-tags fallback_fonts.xml gps.conf hosts init.goldfish.sh media_profiles.xml mkshrc permissions ppp security system_fonts.xml usb_modeswitch.d usb_modeswitch.sh vold.fstab wifi root at android:/system # cd etc root at android:/system/etc # ls 3g_dongle.cfg NOTICE.html.gz apns-conf.xml audio_effects.conf bluetooth camera.cfg dbus.conf dhcpcd event-log-tags fallback_fonts.xml gps.conf hosts init.goldfish.sh media_profiles.xml mkshrc permissions ppp security system_fonts.xml usb_modeswitch.d usb_modeswitch.sh vold.fstab wifi root at android:/system/etc # ip addr list 1: lo: mtu 16436 qdisc noqueue state UNKNOWN ??? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 ??? inet 127.0.0.1/8 scope host lo ??? inet6 ::1/128 scope host ?????? valid_lft forever preferred_lft forever 2: tunl0: mtu 1480 qdisc noop state DOWN ??? link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0: mtu 1476 qdisc noop state DOWN ??? link/gre 0.0.0.0 brd 0.0.0.0 4: sit0: mtu 1480 qdisc noop state DOWN ??? link/sit 0.0.0.0 brd 0.0.0.0 5: ip6tnl0: mtu 1452 qdisc noop state DOWN ??? link/tunnel6 :: brd :: -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Sat Jun 15 14:31:38 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 15 Jun 2013 15:31:38 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: Message-ID: <20130615143138.EBA485B79767C@bmail06.one.com> On Jun 13, 2013 21:39 "Stuart Winter" wrote: > > Ok I've changed it and will upload the new installers once I've got > > Linux > > 3.9.6 kernels built. > > Actually, can you test it? I just edited it and haven't tested it. > It's > really just cosmetic, so it should be fine: > > > > > It Should work but does not. may I suggest this line: > > if [ "$( egrep "versatile" /proc/cpuinfo || egrep "BCM2708" > /proc/cpuinfo )" !="" -a -s $FSTAB ]; then > > found to work on both Raspberry Pi and ARM-Versatile. > > Many thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Sat Jun 15 15:34:13 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 15 Jun 2013 16:34:13 +0100 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130615143138.EBA485B79767C@bmail06.one.com> References: <20130615143138.EBA485B79767C@bmail06.one.com> Message-ID: <20130615153413.9FDAE67BCBBF5@bmail06.one.com> On Jun 15, 2013 15:31 "stanley garvey" wrote: > On Jun 13, 2013 21:39 "Stuart Winter" wrote: > > > > Ok I've changed it and will upload the new installers once I've > > > got Linux > > > 3.9.6 kernels built. > > > > Actually, can you test it? I just edited it and haven't tested it. > > It's > > really just cosmetic, so it should be fine: > > > > > > > > > It Should work but does not. may I suggest this line: > > > > if [ "$( egrep "versatile" /proc/cpuinfo || egrep "BCM2708" > > /proc/cpuinfo )" !="" -a -s $FSTAB ]; then > > > > found to work on both Raspberry Pi and ARM-Versatile. > > > > Many thanks > > > > > Better still > > > > > > if [ "$( grep "versatile\|BCM2708" /proc/cpuinfo )" !="" -a -s > > $FSTAB ]; then > > > > Also tested on Raspberry Pi and QEMU ARM-Versatile, I don't know why > > the alternation is being missed in egrep. My grep is version 2.14, > > am I out of date? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Sat Jun 15 15:50:02 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Sat, 15 Jun 2013 11:50:02 -0400 Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) Message-ID: Hello! Earlier today I had my Slackware (on Intel) system uninstall system. Its installer removal program told me that I'd need to log out and log back in before there would be any changes seen. Well I did that. On logging back in I saw that the process had eaten the prompt. It replaced the @ that's been a mainstay of Linux since I first started using the OS many years earlier, with just the shell name. Which is of course Bash. I don't suppose all of you have any ideas for recovering things, outside of reinstalling the works? In that eventually I made sure I had downloaded a fresh DVD image of Slackware, and of the version that the system is currently running. And I'm making plans for backing up everything important that I put on the system since it was installed about two years ago December. I also asked on a list that I fellow I know runs where everyone runs everything else, and advice is rarely Slackware friendly. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From m-lists at biscuit.org.uk Sat Jun 15 17:38:45 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 15 Jun 2013 18:38:45 +0100 (BST) Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: <20130615153413.9FDAE67BCBBF5@bmail06.one.com> References: <20130615143138.EBA485B79767C@bmail06.one.com> <20130615153413.9FDAE67BCBBF5@bmail06.one.com> Message-ID: > > > if [ "$( grep "versatile\|BCM2708" /proc/cpuinfo )" !="" -a -s > > > $FSTAB ]; then This is incorrect usage. The '|' means 'OR', and by escaping it with '\' you're preventing grep from mapping '|' to that 'OR' meaning. Also, the ARM versatile platform has a capital V in /proc/cpuinfo, so if you tested it there, then it's matching something other than 'versatile' since you did not call grep with -i. > > > Also tested on Raspberry Pi and QEMU ARM-Versatile, I don't know why > > > the alternation is being missed in egrep. My grep is version 2.14, > > > am I out of date? If you were to test it outside of the installer, the script works as it should. Calling 'grep' from a symlink called 'egrep' simply saves you passing the -E option to grep. I suspect that the issue is because in the installer, the grep binary is called 'grep.bin' (probably legacy - I can't find any reason for it to be named this - I can only guess that we had the 'grep' functionality of busybox available in the past, and wanted to be able to use both versions) and when named as such, it doesn't respect the name it was originally called as, thus not switching on the '-E' functionality. I've changed the script to use grep -E rather than 'egrep', and it works inside the installer now. I'll upload those once I've tried Linux 3.9.6 with gcc 3.8.1 (although apparently it won't work, but I might as well give it a go). Cheers s. -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Sat Jun 15 17:47:37 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 15 Jun 2013 18:47:37 +0100 (BST) Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: Message-ID: > Earlier today I had my Slackware (on Intel) system uninstall system. What is this, exactly? I am assuming that you got some 3rd party software that installed via (typically) a shell script, and now you've uninstalled it using the same script. > It replaced the @ that's been a mainstay of > Linux since I first started using the OS many years earlier, with just > the shell name. Which is of course Bash. It's screwed up your user's profile script (~/.bash* files), or if you ran the installer as root, then it could have edited the system-wide profile script - probably either deleted something from /etc/profile.d, or maybe broken /etc/profile. mozes at kermit:~$ grep -r PS1 /etc/profile* /etc/profile:#PS1='`hostname`:`pwd`# ' /etc/profile: PS1='! $ ' /etc/profile: PS1='! ${PWD/#$HOME/~}$ ' /etc/profile: PS1='%n@%m:%~%# ' /etc/profile: PS1='$ ' /etc/profile: PS1='\u@\h:\w\$ ' /etc/profile:export PATH DISPLAY LESS TERM PS1 PS2 My /etc/profile is the standard Slackware one which checks which shell you're running, and if it's anything that isn't ksh, ash and some others, it sets PS1 to the user at machine. You might want to look at the 'etc' package (in 'a' series) for your particular Slackware release. If you unpack it and copy the 'etc/profile.new' file into /etc/profile, it'd restore the original file. However, given that I have no idea what the 'uninstall' system did, it might simply have modified your local user file. -- Stuart Winter Slackware ARM: http://arm.slackware.com From ottavio2006-usenet2012 at yahoo.com Sat Jun 15 17:51:34 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sat, 15 Jun 2013 18:51:34 +0100 Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: Message-ID: On Jun 15, 2013 4:50 PM, "Gregg Levine" wrote: > > Hello! > Earlier today I had my Slackware (on Intel) system uninstall system. > Its installer removal program told me that I'd need to log out and log > back in before there would be any changes seen. Well I did that. On > logging back in I saw that the process had eaten the prompt. > > It replaced the @ that's been a mainstay of > Linux since I first started using the OS many years earlier, with just > the shell name. Which is of course Bash. > > I don't suppose all of you have any ideas for recovering things, > outside of reinstalling the works? In that eventually I made sure I > had downloaded a fresh DVD image of Slackware, and of the version that > the system is currently running. And I'm making plans for backing up > everything important that I put on the system since it was installed > about two years ago December. I also asked on a list that I fellow I > know runs where everyone runs everything else, and advice is rarely > Slackware friendly. > ----- > 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 I haven't used slackware on intel for some time but I'm not aware of a system uninstall utility, unless you mean uninstalling a single package. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Sat Jun 15 18:19:10 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Sat, 15 Jun 2013 14:19:10 -0400 Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: Message-ID: On Sat, Jun 15, 2013 at 1:51 PM, Ottavio Caruso wrote: > > On Jun 15, 2013 4:50 PM, "Gregg Levine" wrote: >> >> Hello! >> Earlier today I had my Slackware (on Intel) system uninstall system. >> Its installer removal program told me that I'd need to log out and log >> back in before there would be any changes seen. Well I did that. On >> logging back in I saw that the process had eaten the prompt. >> >> It replaced the @ that's been a mainstay of >> Linux since I first started using the OS many years earlier, with just >> the shell name. Which is of course Bash. >> >> I don't suppose all of you have any ideas for recovering things, >> outside of reinstalling the works? In that eventually I made sure I >> had downloaded a fresh DVD image of Slackware, and of the version that >> the system is currently running. And I'm making plans for backing up >> everything important that I put on the system since it was installed >> about two years ago December. I also asked on a list that I fellow I >> know runs where everyone runs everything else, and advice is rarely >> Slackware friendly. >> ----- >> Gregg C Levine gregg.drwho8 at gmail.com >> "This signature fought the Time Wars, time and again." > I haven't used slackware on intel for some time but I'm not aware of a > system uninstall utility, unless you mean uninstalling a single package. Hello! It was the installer for QNX a Posix based Real Time OS who claims to be running on a lot of business based systems. I sometimes try to build images for applications that are slightly above the norm. You're close enough Stuart, it was the installer mechanism for that product who crashed things. Earlier I did find the original profile saved as profile.backup and copied it back, and noted that it was setup as an empty file when the thing was removed. I also did restore the etc area and noted the presence of profile.new as well. Mine was the backup named file. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Sat Jun 15 19:21:16 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Sat, 15 Jun 2013 19:21:16 +0000 Subject: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 In-Reply-To: References: <20130615143138.EBA485B79767C@bmail06.one.com> <20130615153413.9FDAE67BCBBF5@bmail06.one.com> Message-ID: <1728306297-1371324078-cardhu_decombobulator_blackberry.rim.net-236175688-@b2.c14.bise7.blackberry> Versatile / versatile. Yes that was a typo as I was working in the installer I could not cut and paste from either the QEmu or Raspberry Pi. Left machines upgrading to current. Going to leave it for tonight Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Stuart Winter Sender: "ARMedslack" Date: Sat, 15 Jun 2013 18:38:45 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1 > > > if [ "$( grep "versatile\|BCM2708" /proc/cpuinfo )" !="" -a -s > > > $FSTAB ]; then This is incorrect usage. The '|' means 'OR', and by escaping it with '\' you're preventing grep from mapping '|' to that 'OR' meaning. Also, the ARM versatile platform has a capital V in /proc/cpuinfo, so if you tested it there, then it's matching something other than 'versatile' since you did not call grep with -i. > > > Also tested on Raspberry Pi and QEMU ARM-Versatile, I don't know why > > > the alternation is being missed in egrep. My grep is version 2.14, > > > am I out of date? If you were to test it outside of the installer, the script works as it should. Calling 'grep' from a symlink called 'egrep' simply saves you passing the -E option to grep. I suspect that the issue is because in the installer, the grep binary is called 'grep.bin' (probably legacy - I can't find any reason for it to be named this - I can only guess that we had the 'grep' functionality of busybox available in the past, and wanted to be able to use both versions) and when named as such, it doesn't respect the name it was originally called as, thus not switching on the '-E' functionality. I've changed the script to use grep -E rather than 'egrep', and it works inside the installer now. I'll upload those once I've tried Linux 3.9.6 with gcc 3.8.1 (although apparently it won't work, but I might as well give it a go). Cheers s. -- Stuart Winter Slackware ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From louigi600 at yahoo.it Mon Jun 17 14:35:37 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 17 Jun 2013 15:35:37 +0100 (BST) Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: Message-ID: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> >>> Hello! >>> Earlier today I had my Slackware (on Intel) system uninstall system. >>> Its installer removal program told me that I'd need to log out and log >>> back in before there would be any changes seen. Well I did that. On >>> logging back in I saw that the process had eaten the prompt. >>> >>> It replaced the @ that's been a mainstay of >>> Linux since I first started using the OS many years earlier, with just >>> the shell name. Which is of course Bash. >>> >>> I don't suppose all of you have any ideas for recovering things, >>> outside of reinstalling the works? In that eventually I made sure I >>> had downloaded a fresh DVD image of Slackware, and of the version that >>> the system is currently running. And I'm making plans for backing up >>> everything important that I put on the system since it was installed >>> about two years ago December. I also asked on a list that I fellow I >>> know runs where everyone runs everything else, and advice is rarely >>> Slackware friendly. >>> ----- >>> Gregg C Levine gregg.drwho8 at gmail.com >>> "This signature fought the Time Wars, time and again." >> I haven't used slackware on intel for some time but I'm not aware of a >> system uninstall utility, unless you mean uninstalling a single package. > >Hello! >It was the installer for QNX a Posix based Real Time OS who claims to >be running on a lot of business based systems. I sometimes try to >build images for applications that are slightly above the norm. >You're close enough Stuart, it was the installer mechanism for that >product who crashed things. Earlier I did find the original profile >saved as profile.backup and copied it back, and noted that it was >setup as an empty file when the thing was removed. >I also did restore the etc area and noted the presence of profile.new >as well. Mine was the backup named file. I'm beginning to think that since kernel.org was hacked that things just are not the same .... I'm seeing more and more often "segmentation fault" and "memory fault" in bash scriprs. Now it's odd that a script that executes only internal or userland commands exibits a segmentation fault that as far as I recall means that a program is accessing memory that is not pertinent to that program. Should not bash and the GNU userland (shippet with stable distributions) be immune to this sort of problem ? Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Mon Jun 17 14:38:24 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Mon, 17 Jun 2013 10:38:24 -0400 Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: On Mon, Jun 17, 2013 at 10:35 AM, Davide wrote: >>>> Hello! >>>> Earlier today I had my Slackware (on Intel) system uninstall system. >>>> Its installer removal program told me that I'd need to log out and log >>>> back in before there would be any changes seen. Well I did that. On >>>> logging back in I saw that the process had eaten the prompt. >>>> >>>> It replaced the @ that's been a mainstay of >>>> Linux since I first started using the OS many years earlier, with just >>>> the shell name. Which is of course Bash. >>>> >>>> I don't suppose all of you have any ideas for recovering things, >>>> outside of reinstalling the works? In that eventually I made sure I >>>> had downloaded a fresh DVD image of Slackware, and of the version that >>>> the system is currently running. And I'm making plans for backing up >>>> everything important that I put on the system since it was installed >>>> about two years ago December. I also asked on a list that I fellow I >>>> know runs where everyone runs everything else, and advice is rarely >>>> Slackware friendly. >>>> ----- >>>> Gregg C Levine gregg.drwho8 at gmail.com >>>> "This signature fought the Time Wars, time and again." >>> I haven't used slackware on intel for some time but I'm not aware of a >>> system uninstall utility, unless you mean uninstalling a single package. >> >>Hello! >>It was the installer for QNX a Posix based Real Time OS who claims to >>be running on a lot of business based systems. I sometimes try to >>build images for applications that are slightly above the norm. > >>You're close enough Stuart, it was the installer mechanism for that >>product who crashed things. Earlier I did find the original profile >>saved as profile.backup and copied it back, and noted that it was >>setup as an empty file when the thing was removed. > >>I also did restore the etc area and noted the presence of profile.new >>as well. Mine was the backup named file. > > I'm beginning to think that since kernel.org was hacked that things just are > not the same .... > I'm seeing more and more often "segmentation fault" and "memory fault" in > bash scriprs. > Now it's odd that a script that executes only internal or userland commands > exibits a segmentation fault that as far as I recall means that a program is > accessing memory that is not pertinent to that program. > > Should not bash and the GNU userland (shippet with stable distributions) be > immune to this sort of problem ? > > Ciao > David > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! It's possible. But not unlikely. The other question is when was the Kernel site hacked? ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From m-lists at biscuit.org.uk Mon Jun 17 14:55:57 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 17 Jun 2013 15:55:57 +0100 (BST) Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: > Hello! > It's possible. But not unlikely. The other question is when was the > Kernel site hacked? It was ages ago - in 2001! Chances are that your installation has installed something dodgy, or you may even have some faulty RAM modules. From ottavio2006-usenet2012 at yahoo.com Mon Jun 17 15:14:54 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Mon, 17 Jun 2013 16:14:54 +0100 Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: Kernel.org was hacked in 2011. But I think that the segmentation faults come from dodgy Android code. Has anybody read a dmesg on an Android device? I can post one if nedeed. It's a mess! -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Jun 18 12:18:18 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 18 Jun 2013 13:18:18 +0100 (BST) Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1371557898.16247.YahooMailNeo@web28805.mail.ir2.yahoo.com> >> Hello! >> It's possible. But not unlikely. The other question is when was the >> Kernel site hacked? >It was ages ago - in 2001! Unlikely 2001 back then we only had 2.4 stable kernels? .... more like 2010 >Chances are that your installation has installed something dodgy, >or you may even have some faulty RAM modules. Also unlikly as I seen it on different distributions (even enterprise ones at work) , on different hardware and in virtual machines (belonging to a vmware infrastructure system), on my scripts and on system scripts. Well whatever ... might not be connected to that but surely it's an odd thing. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Jun 18 12:22:06 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 18 Jun 2013 13:22:06 +0100 (BST) Subject: [ARMedslack] Prompts and Slackware (general not necessarily ARM related) In-Reply-To: References: <1371479737.43868.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1371558126.87989.YahooMailNeo@web28805.mail.ir2.yahoo.com> >Kernel.org was hacked in 2011. But I think that the segmentation faults come from dodgy Android code. Has anybody read a dmesg on an Android device? >I can post one if nedeed. It's a mess! It's not from an ARM device I'm getting those errors, I actually have not noticed it there yet, they're coming from? x86 and x86_64 hardware. But this is really getting off topic. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sat Jun 22 14:20:54 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 22 Jun 2013 15:20:54 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> >>>> I got tempted with one of these. >>>> >>>> Integrated BGN wifi >>>> 1 usb client/host port qith support for external usb devices (is ethernet/3G >>>> ....) >>>> 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is >>>> reserved for boot/rescure/emergency restore) >>>> 7" screen 800x480 px >>>> single core cortex A8 (not tegra) >>>> 1/2Gb ram >>>> micro SD slot with support for 32Gb cards >>>> 3 axis accelerometer >>>> >>>> Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still >>>> tempted to try have Slackware on this one too. >>>> The user-land will probably only require just xkbd but I doubt the kernel >>>> that comes with the device has proper frame-buffer console so I'll need to >>>> figure out what sort of kernel to put on that thing. >>>> >>> >>>Hello! >>>Where did you find out about the thing to begin with? Google doesn't >>>know a thing about it, and wanted to tell me about a completely >>>useless contraption used for playing bad music. >> >>Ooops ... XZPAD700 >>I have one ... I got in in hypermarket Carrefour in offer 69 Euro. >>I'm sure it's a re branded Chinese thing but for that price I can stick up with it. >> >>I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap. >Ok here's some info on the device (I've not yet rooted the device but I got is as root so I guess this one is not locked) : I did a bit of search on distributor's site and it appears that if you press and hold the power button while booting it's able to recover from a factory rescue image placed in a microSD. I'm not sure if this will allow you to load a different kernel (probabbly not) but I'm pretty sure the microSD can be packed to look like a rescue image but have a custom userland instead. I've downloaded the rescue image to see if I can figure out how it's assembled. Ciao David >root at darkstar:~/ac100/devel/android-sdk-linux_x86/platform-tools# ./adb? shell -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Jun 25 10:18:34 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 25 Jun 2013 11:18:34 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1372155514.46356.YahooMailNeo@web28801.mail.ir2.yahoo.com> I downloaded the rescue image from http://www.hamletcom.com/docs/XZPAD700_microsd_restore_B.zip and I found some evidence that the device uses u-boot. I'm not sure if the u-boot image I found in the rescue image is part of the image that gets restored into the device or if the rescue image itself has a boot loader in it that gets loaded into ram as if it was a second stage boot loader. Anyway the rescue image appears as a bootable image: root at darkstar:/tmp/XZPAD700_microsd_restore_B# file XZPAD700_MicroSD_restore_B_20121122.img XZPAD700_MicroSD_restore_B_20121122.img: x86 boot sector; partition 1: ID=0xb, active, starthead 0, startsector 798949, 202522 sectors, code offset 0x0 root at darkstar:/tmp/XZPAD700_microsd_restore_B# root at darkstar:/tmp/XZPAD700_microsd_restore_B# fdisk -l XZPAD700_MicroSD_restore_B_20121122.img Disk XZPAD700_MicroSD_restore_B_20121122.img: 513 MB, 513802240 bytes 1 heads, 63 sectors/track, 15928 cylinders, total 1003520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 ????????????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System XZPAD700_MicroSD_restore_B_20121122.img1?? *????? 798949???? 1001470????? 101261??? b? W95 FAT32 root at darkstar:/tmp/XZPAD700_microsd_restore_B# But I've not been able to mount it as a loop device with all my efforts to calculate the offset of that first partition is shown by fdisk. I even wrote the image to a microsd as documented but I was unable to mount that first partition anyway. Anyone have any idea how to mount that partition ? I then started examining the rescue image with strings and found a few interesting things: ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c? --cpu=Cortex-A8.no_neon -O0 -I. -I./../../../config -I./../../../boot1/include -I./../../../boot1/include/interinc -I. -I./.svn -I./.svn/prop-base -I./.svn/props -I./.svn/text-base -I./.svn/tmp -I./.svn/tmp/prop-base -I./.svn/tmp/props -I./.svn/tmp/text-base -I ./Board -I./Board/.svn -I./Board/.svn/prop-base -I./Board/.svn/props -I./Board/.svn/text-base -I./Board/.svn/tmp -I./Board/fel_detect -I./Board/fel_detect/.svn -I./Board/power_ctrl -I./Board/power_ctrl/.svn -I./BootOS -I./BootOS/.svn -I./BootOS/.svn/prop-base -I./BootOS/.svn/pro ps -I./BootOS/.svn/text-base -I./BootOS/.svn/tmp -I./Common -I./Common/.svn -I./Common/.svn/prop-base -I./Common/.svn/props -I./Common/.svn/text-base -I./Common/.svn/tmp -I./Common/Picture -I./Common/Picture/.svn -I./Common/script_patch -I./Common/script_patch/.svn -I./Common/se rvice -I./Common/service/.svn -I./Common/ui -I./Common/ui/.svn -I./Common/ui/display_interface -I./config -I./config/.svn -I./config/.svn/prop-base -I./config/.svn/props -I./config/.svn/text-base -I./config/.svn/tmp -I./Include -I./Include/.svn -I./Include/.svn/prop-base -I./Inc lude/.svn/props -I./Include/.svn/text-base -I./Include/.svn/tmp -I./part_info -I./part_info/.svn -I./part_info/.svn/prop-base -I./part_info/.svn/props -I./part_info/.svn/text-base -I./part_info/.svn/tmp -I./usb_device -I./usb_device/.svn -I./usb_device/.svn/prop-base -I./usb_dev ice/.svn/props -I./usb_device/.svn/text-base -I./usb_device/.svn/tmp eGon2_common.o c_int.o format_transformed.o ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c? --cpu=Cortex-A8.no_neon -O0 -I. -I./../../boot1/include -I./../../boot1/include/cfgs _int.o ARM Assembler, RVCT4.0 [Build 400] armasm --debug --keep --cpu=Cortex-A8.no_neon? -I. -I./../../boot1/include -I./../../boot1/include/cfgs ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c? --cpu=Cortex-A8.no_neon -O0 -I. -I./../../../config -I./../../../boot1/include -I. -I./.svn -I./.svn/prop-base -I./.svn/props -I./.svn/text-base -I./.svn/tmp -I./.svn/tmp/prop-base -I./.svn/tmp/props -I./.svn/tmp/text-base -I./config -I./config/.svn -I./config/ .svn/prop-base -I./config/.svn/props -I./config/.svn/text-base -I./config/.svn/tmp -I./de_bsp -I./de_bsp/.svn -I./de_bsp/.svn/prop-base -I./de_bsp/.svn/props -I./de_bsp/.svn/text-base -I./de_bsp/.svn/tmp -I./de_bsp/de -I./de_bsp/de/.svn -I./de_bsp/de/ebios -I./de_bsp/iep -I./de_bsp/iep/.svn -I./de_bsp/lcd -I./de_bsp/lcd/.svn -I./OSAL -I./OSAL/.svn -I./OSAL/.svn/prop-base -I./OSAL/.svn/props -I./OSAL/.svn/text-base -I./OSAL/.svn/tmp eGon2_common.o cleanflushcachebyregion.o format_transformed.o ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c? --cpu=Cortex-A8.no_neon -O0 -I. -I./../../boot1/include -I./../../boot1/include/cfgs cleanflushcachebyway.o ARM Assembler, RVCT4.0 [Build 400] armasm --debug --keep --cpu=Cortex-A8.no_neon? -I. -I./../../boot1/include -I./../../boot1/include/cfgs img_name = c:\linux\u-boot.bin U-Boot 2011.09-rc1-dirty (Nov 22 2012 - 14:25:29) Allwinner Technology U-Boot 2011.09-rc1-dirty (Nov 22 2012 - 14:25:29) Allwinner Technology ???????????????????????????????????? ???????????????????????????????????????? bootcmd=nand read 50000000 boot;boota 50000000 bootdelay=1 baudrate=115200 bootdelay=3 bootcmd=run setargs boot_normal console=ttyS0,115200 nand_root=/dev/nandd mmc_root=/dev/mmcblk0p4 init=/init loglevel=8 setargs=setenv bootargs console=${console} root=${nand_root}init=${init} loglevel=${loglevel} boot_normal=nand read 50000000 boot; boota 50000000 boot_recovery=nand read 50000000 recovery; boota 50000000 boot_fastboot=fastboot bootcmd=nand read 50000000 boot;boota 50000000 bootdelay=1 baudrate=115200 bootdelay=3 bootcmd=run setargs boot_normal console=ttyS0,115200 nand_root=/dev/nandd mmc_root=/dev/mmcblk0p4 init=/init loglevel=8 setargs=setenv bootargs console=${console} root=${nand_root}init=${init} loglevel=${loglevel} boot_normal=nand read 50000000 boot; boota 50000000 boot_recovery=nand read 50000000 recovery; boota 50000000 boot_fastboot=fastboot set_default_env env_import mmc_saveenv nand_saveen Ciao David P.S.: would it be a good idea to put up a page on docs.slackware.com? on hacking attempts on the XZPAD700 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Jun 27 00:34:39 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Wed, 26 Jun 2013 20:34:39 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour Message-ID: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Has anyone got any idea about how to trun of the default behaviour of having every interface automatically assigned an IPv6 address when it comes up? So far I've hunted around and around the interwebs, and pushed "0" into all sorts of files in /proc/sys/net/ipv6/conf/*/* all to no avail. The moment I bring an interface up an inet6 LLA address is automatically assigned to it. I'm starting to wonder if Linux is an OS I really want to have anywhere near a computer of mine when it seems the designers of it decided it'd be a good idea to (by default) automatically open up a connectable address on every single nertwork interface, of every single device, without any consideration for whether an interface was protected or not. I mean I've seen many utterly ridiculous decisions in my time in this industry, but I never thought I'd see one which left nearly every single linux system (all those where ip6tables hasn't been explicitly invoked anyway) vulnerable to attack (even if only from another system on the local network). Utter madness, with seemingly no way to disable it. Any ideas/suggestions welcomed. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu Jun 27 00:46:33 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 26 Jun 2013 20:46:33 -0400 Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: On Wed, Jun 26, 2013 at 8:34 PM, wrote: > Has anyone got any idea about how to trun of the default behaviour of having > every interface automatically assigned an IPv6 address when it comes up? > > So far I've hunted around and around the interwebs, and pushed "0" into all > sorts of files in /proc/sys/net/ipv6/conf/*/* all to no avail. The moment I > bring an interface up an inet6 LLA address is automatically assigned to it. > > I'm starting to wonder if Linux is an OS I really want to have anywhere near > a computer of mine when it seems the designers of it decided it'd be a good > idea to (by default) automatically open up a connectable address on every > single nertwork interface, of every single device, without any consideration > for whether an interface was protected or not. > > I mean I've seen many utterly ridiculous decisions in my time in this > industry, but I never thought I'd see one which left nearly every single > linux system (all those where ip6tables hasn't been explicitly invoked > anyway) vulnerable to attack (even if only from another system on the local > network). Utter madness, with seemingly no way to disable it. > > Any ideas/suggestions welcomed. > > > Thanks > Dave Hello! And did you try using the rmmod command on the ipv6 module? And to prevent it being loaded all the time then add it to the blacklist for modules. Also check to see where its being loaded. In all actuality IPv6 happens to be practically right around the corner, we actually ran out of IPv4 addresses about three to six years previously. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From robby at rlworkman.net Thu Jun 27 01:05:41 2013 From: robby at rlworkman.net (Robby Workman) Date: Wed, 26 Jun 2013 20:05:41 -0500 Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: <20130626200541.40a73f68.robby@rlworkman.net> On Wed, 26 Jun 2013 20:34:39 -0400 (EDT) dowelld at netscape.net wrote: > Has anyone got any idea about how to trun of the default behaviour of > having every interface automatically assigned an IPv6 address when it > comes up? > > So far I've hunted around and around the interwebs, and pushed "0" > into all sorts of files in /proc/sys/net/ipv6/conf/*/* all to no > avail. The moment I bring an interface up an inet6 LLA address is > automatically assigned to it. > > I'm starting to wonder if Linux is an OS I really want to have > anywhere near a computer of mine when it seems the designers of it > decided it'd be a good idea to (by default) automatically open up a > connectable address on every single nertwork interface, of every > single device, without any consideration for whether an interface was > protected or not. > > I mean I've seen many utterly ridiculous decisions in my time in this > industry, but I never thought I'd see one which left nearly every > single linux system (all those where ip6tables hasn't been explicitly > invoked anyway) vulnerable to attack (even if only from another > system on the local network). Utter madness, with seemingly no way to > disable it. > > Any ideas/suggestions welcomed. If they're just link local addresses, they're not connectable at all from outside. Re the decisions, it's not linux - it's how ipv6 works: http://www.openwall.com/presentations/IPv6/ -RW From dowelld at netscape.net Thu Jun 27 08:31:05 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 27 Jun 2013 04:31:05 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: <8D04127CC9ACC26-F7C-26B44@webmail-d159.sysops.aol.com> -----Original Message----- From: Gregg Levine To: Slackware ARM port Sent: Thu, Jun 27, 2013 1:46 am Subject: Re: [ARMedslack] IPv6 Default behaviour On Wed, Jun 26, 2013 at 8:34 PM, wrote: > Has anyone got any idea about how to trun of the default behaviour of having > every interface automatically assigned an IPv6 address when it comes up? > > So far I've hunted around and around the interwebs, and pushed "0" into all > sorts of files in /proc/sys/net/ipv6/conf/*/* all to no avail. The moment I > bring an interface up an inet6 LLA address is automatically assigned to it. > > I'm starting to wonder if Linux is an OS I really want to have anywhere near > a computer of mine when it seems the designers of it decided it'd be a good > idea to (by default) automatically open up a connectable address on every > single nertwork interface, of every single device, without any consideration > for whether an interface was protected or not. > > I mean I've seen many utterly ridiculous decisions in my time in this > industry, but I never thought I'd see one which left nearly every single > linux system (all those where ip6tables hasn't been explicitly invoked > anyway) vulnerable to attack (even if only from another system on the local > network). Utter madness, with seemingly no way to disable it. > > Any ideas/suggestions welcomed. > > > Thanks > Dave Hello! And did you try using the rmmod command on the ipv6 module? And to prevent it being loaded all the time then add it to the blacklist for modules. Also check to see where its being loaded. In all actuality IPv6 happens to be practically right around the corner, we actually ran out of IPv4 addresses about three to six years previously. ----- 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 Hi Gregg, I don't want to disable IPv6, in fact I'm trying to implement it in an appliance. I just want it implemented securely. Assigning an EUI64 address to the interface automatically in the kernel is just plain daft... and IMHO dangerous. For example, thanks to the kernel team, every single Slackware system (and who knows how many other distributions) are by default connectable and therefore attackable upon install. Got an unpatched apache/ssh/email server running on your system, that's nice I'll just connect to it on the unprotected IPv6 interface which you probably don't even know exists (most normal people won't know it exists). What kind of madness is that... it's the latest kind. As implemented on every single linux system worldwide, good eh? What was wrong with the simple idea that interfaces are configured in userland? You know by users, who are at least then aware or culpable for having enabled it. I will no doubt today spend another several hours here trying to find a way close a hole which should never have been opened. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Jun 27 08:37:08 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 27 Jun 2013 04:37:08 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: <20130626200541.40a73f68.robby@rlworkman.net> References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> <20130626200541.40a73f68.robby@rlworkman.net> Message-ID: <8D04128A4CAC7B8-F7C-26B5D@webmail-d159.sysops.aol.com> -----Original Message----- From: Robby Workman To: armedslack Sent: Thu, Jun 27, 2013 2:05 am Subject: Re: [ARMedslack] IPv6 Default behaviour On Wed, 26 Jun 2013 20:34:39 -0400 (EDT) dowelld at netscape.net wrote: > Has anyone got any idea about how to trun of the default behaviour of > having every interface automatically assigned an IPv6 address when it > comes up? > > So far I've hunted around and around the interwebs, and pushed "0" > into all sorts of files in /proc/sys/net/ipv6/conf/*/* all to no > avail. The moment I bring an interface up an inet6 LLA address is > automatically assigned to it. > > I'm starting to wonder if Linux is an OS I really want to have > anywhere near a computer of mine when it seems the designers of it > decided it'd be a good idea to (by default) automatically open up a > connectable address on every single nertwork interface, of every > single device, without any consideration for whether an interface was > protected or not. > > I mean I've seen many utterly ridiculous decisions in my time in this > industry, but I never thought I'd see one which left nearly every > single linux system (all those where ip6tables hasn't been explicitly > invoked anyway) vulnerable to attack (even if only from another > system on the local network). Utter madness, with seemingly no way to > disable it. > > Any ideas/suggestions welcomed. If they're just link local addresses, they're not connectable at all from outside. Re the decisions, it's not linux - it's how ipv6 works: http://www.openwall.com/presentations/IPv6/ -RW _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Hi Robby, Sorry, I'm not reassured to know that my systems are only being placed at risk by default on the local link. If Microsoft did this with WIndows everyone would point out how stupid they were to automatically make an interface addressable without protecting it behind a firewall. I'm afraid it is linux, it's no different to the linux kernel automatically assigning an IPv4 address to every interface which has a connected cable. It could have been implemented that way, but it wasn't. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Thu Jun 27 10:08:11 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Thu, 27 Jun 2013 11:08:11 +0100 Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: On 27 June 2013 01:34, wrote: > Has anyone got any idea about how to trun of the default behaviour of having > every interface automatically assigned an IPv6 address when it comes up? Never tried it myself but have you tried adding "ipv6.disable=1" as kernel command line parameter? -- Ottavio From geoff at ohdoughnut.com Thu Jun 27 11:34:46 2013 From: geoff at ohdoughnut.com (Geoff Walton) Date: Thu, 27 Jun 2013 07:34:46 -0400 Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: Microsoft does do this with Windows, if you don't disable ipv6. Its part of the spec. On Thu, Jun 27, 2013 at 6:08 AM, Ottavio Caruso < ottavio2006-usenet2012 at yahoo.com> wrote: > On 27 June 2013 01:34, wrote: > > Has anyone got any idea about how to trun of the default behaviour of > having > > every interface automatically assigned an IPv6 address when it comes up? > > Never tried it myself but have you tried adding "ipv6.disable=1" as > kernel command line parameter? > > > > > -- > Ottavio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Jun 27 12:33:43 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 27 Jun 2013 08:33:43 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: <8D04149B22AC5C2-F7C-274FB@webmail-d159.sysops.aol.com> -----Original Message----- From: Ottavio Caruso To: Slackware ARM port Sent: Thu, Jun 27, 2013 11:08 am Subject: Re: [ARMedslack] IPv6 Default behaviour On 27 June 2013 01:34, wrote: > Has anyone got any idea about how to trun of the default behaviour of having > every interface automatically assigned an IPv6 address when it comes up? Never tried it myself but have you tried adding "ipv6.disable=1" as kernel command line parameter? -- Ottavio _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack That might disable IPv6 and I don't want to do that, as I said before I'm trying to implement it on an appliance. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Jun 27 12:48:11 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 27 Jun 2013 08:48:11 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: <8D0414BB78516B9-F7C-27612@webmail-d159.sysops.aol.com> They also put the interface they bring up behind a firewall, which prevents access to privileged ports. The Linux autoconfiguration can't be disabled, at least I can't disable it. So when my appliance starts all the services it provides are open to be attacked until the start up scripts process the ip6tables rules I've written. I can't remove the auto configured address on startup, I've tried that at various points in the startup, it just gets rejected by the kernel. Basically any linux system I start is started with an autoconfigured interface with a unique address which is opened to any other system on the local network. I have no ability to prevent or control that. I can't prevent any other system on the local network from connecting to the apache server through that interface and attempting to push malware of one form or another into it. I can't prevent some malware from a windows systems attempting to infect any files on fileshares available through that interface, I basically have just lost the ability to secure my systems at start up. Someone somewhere thought this was a good idea, all I can see are great big gaping security holes. I can understand the people who wrote IPv6 specs thinking designing their protocol so every computer could find it's neighbours, and thus make use of locally available network resources easily, writing it like that. They're not the kind of people who think about writing malware which looks for access to other systems to infect them. I can't for the life of me understand why anyone who lives/works in the real world, where unadulterated access to systems through unsecured network interfaces has proven time and time again to be a problem, would implement a system which created such unprotected interfaces in their OS. My only option seems to be to prevent any access to any service through IPv6... some replacement protocol. Thanks Dave -----Original Message----- From: Geoff Walton To: Slackware ARM port Sent: Thu, Jun 27, 2013 12:34 pm Subject: Re: [ARMedslack] IPv6 Default behaviour Microsoft does do this with Windows, if you don't disable ipv6. Its part of the spec. On Thu, Jun 27, 2013 at 6:08 AM, Ottavio Caruso wrote: On 27 June 2013 01:34, wrote: > Has anyone got any idea about how to trun of the default behaviour of having > every interface automatically assigned an IPv6 address when it comes up? Never tried it myself but have you tried adding "ipv6.disable=1" as kernel command line parameter? -- Ottavio _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Jun 27 21:31:26 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 27 Jun 2013 17:31:26 -0400 (EDT) Subject: [ARMedslack] IPv6 Default behaviour In-Reply-To: References: <8D040E53DCDA5C1-F7C-25951@webmail-d159.sysops.aol.com> Message-ID: <8D04194CF3DE2D9-F7C-2BB58@webmail-d159.sysops.aol.com> After far to many hours trying to take back control of how a computer I run interfaces with the world. Here's how to do it (at least the best fix I've managed to come up with so far. The trick to controlling IPv6 addresses assigned to network cards. (For the awkward gits amongst you (like me) who want to be in contol of the network interfaces your system runs) 1). Do not configure the eth card in rc.inet1. 2). In rc.local inject "1" into /proc/sys/net/ipv6/conf/eth?/disable_ipv6 3). Then bring the eth card UP (ifconfig eth? UP) 4). Now in another script inject "0" into /proc/sys/net/ipv6/conf/eth?/disable_ipv6 5). The kernel will automatically assign an IPv6 fe80:: LLA address to the interface. 6). Capture the automatically assigned address to a file somewhere incase you want to use it at some point. 7). Delete the address from the interface. 8). Use rc.local to assign any IPv4 addresses you want assigned. rc.local example lines: # Disable IPv6 autoconf on eth0 echo 1 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6 # Bring up the eth0 interface if [ `/sbin/ifconfig eth0 | grep UP | wc -l` -eq 0 ]; then /sbin/ifconfig eth0 up fi # Start IPv6 interfaces if [ -x /etc/rc.d/rc.ipv6 ]; then /etc/rc.d/rc.ipv6 fi rc.ipv6 example lines: # Enable IPv6 autoconf on eth0 echo 0 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6 # Store auto assigned IPv6 address and remove it from the interface SAVEIFS=$IFS IFS=$(echo -en "\n\b") for line in `ifconfig eth0 | grep inet6` ; do ADDR=`echo ${line// /_} | cut -f10 -d_` PRFX=`echo ${line// /_} | cut -f13 -d_` if [ `grep $ADDR /etc/rc.d/ipv6.addresses | wc -l` -eq 0 ]; then echo "$ADDR/$PRFX" >> /etc/rc.d/ipv6.addresses fi /sbin/ifconfig eth0 inet6 del $ADDR/$PRFX done IFS=$SAVEIFS unset SAVEIFS 9). You now finally have control over whether individual NICs run IPv6 or not, and if they do, what addresses you assign to them. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: