From louigi600 at yahoo.it Fri Jul 1 06:05:41 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 1 Jul 2011 07:05:41 +0100 (BST) Subject: [ARMedslack] R: Open Pandora In-Reply-To: <4E091369.80102@ohdoughnut.com> Message-ID: <1309500341.74274.YahooMailClassic@web29708.mail.ird.yahoo.com> Nice but the price ... for crying out loud you can but 2 Toshiba a100 netbooks for that price ! --- Mar 28/6/11, Geoff Walton ha scritto: > Da: Geoff Walton > Oggetto: [ARMedslack] Open Pandora > A: "Slackware ARM port" > Data: Marted? 28 giugno 2011, 01:34 > Has anyone tried to do armedslack on > the Open Pandora handheld? > > It looks like a pretty fun toy but I would want Slackware > on it. http://www.openpandora.org/ > > > -----Segue allegato----- > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From louigi600 at yahoo.it Fri Jul 1 06:32:18 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 1 Jul 2011 07:32:18 +0100 (BST) Subject: [ARMedslack] R: R: R: R: R: micro root rescue system Message-ID: <1309501938.52494.YahooMailClassic@web29701.mail.ird.yahoo.com> Ok I did a little cleaning and I managed to add X, fluxbox, rdesktop, vncviewer, links and a package manager in practically the same footprint. There is also wiki, svn, package repository and x86 port. Have fun david --- Lun 23/5/11, Davide ha scritto: > Da: Davide > Oggetto: R: [ARMedslack] R: R: R: R: micro root rescue system > A: "Slackware ARM port" > Data: Luned? 23 maggio 2011, 10:24 > Ok since armedslack does not want a > microroot system I put it up as part of my clash progect as > clash New Generation (clashNG). > You can see it bothe on freshmeat and sourceforge: > http://freshmeat.net/projects/clash > https://sourceforge.net/projects/bclash/ > > It still need a lot of documentation but I put up a wiki on > sourceforge that I hope helps and with a bit of luck I can > get others to help make better and more accurate > documentation: > http://sourceforge.net/apps/trac/bclash/wiki > > I know that Pat does not like other distros to say that > they are Slackware based thta's whi it's not so evident that > a lot of work on this arm clashNG comes right out of > armedslack. If anybody feels about this just tell me the > correct level of evidence and I'll show it up. > > Regards > David > > --- Ven 6/5/11, Davide > ha scritto: > > > Da: Davide > > Oggetto: [ARMedslack] R:? R:? R:? > R:? micro root rescue system > > A: "Slackware ARM port" > > Data: Venerd? 6 maggio 2011, 09:19 > > I put the image on diet and now it > > fits in 32 Mb (without summery on the jffs2 image): > > > > root at hp:/mnt/hd/usr/src# du -ks > rootfs_surap_busybox.jffs2 > > > > 31892???rootfs_surap_busybox.jffs2 > > root at hp:/mnt/hd/usr/src# > > > > This is what's in the system: > > root at hp:/mnt/hd/usr/src/surap_packages# du -ms * |sort > -n > > 1? ? ???apr-util-1.3.10-arm-1.tgz > > 1? ? ???at-3.1.12-arm-1.tgz > > 1? ? ???busybox-1.18.4-arm-1.tgz > > 1? ? ???dnsmasq-2.52-arm-1.tgz > > 1? ? ???dropbear-0.53.1-arm-1.tgz > > 1? ? ???hostapd-0.7.3-arm-1.tgz > > 1? ? ???iptables-1.4.10-arm-1.tgz > > 1? ? ???iw-0.9.20-arm-1.tgz > > 1? ? ???ppp-2.4.5-arm-1.tgz > > 1? ? ???sqlite-3.7.3-arm-1.tgz > > 1? ? ???udev-165-arm-2.tgz > > 1? ? > > ???usb_modeswitch-1.1.6-arm-1.tgz > > 1? ? > > ???wireless-tools-29-arm-2.tgz > > 2? ? > > ???kernel-firmware-2.6.38.3-noarch-1.tgz > > 3? ? ???php-5.3.6-arm-1.tgz > > 5? ? ???microroot_libs-arm-1.tgz > > 12? ? ? > > kernel_2.6.38.3-microkirkwood-arm-1.tgz > > > > I've not got around to get all the pppd helping > stuff, > > master mode upun wifi gongle plugin ... etc stuff > working > > but the base system is working and could be used as a > > slackware like rescue system. > > > > The busybox build is pretty much a complete buld and > has > > nearly everything enebled including nand utilities.? > > > > > Anyone intrested ? > > > > --- Gio 5/5/11, Davide > > ha scritto: > > > > > Da: Davide > > > Oggetto: [ARMedslack] R:? R:? R:? micro > > root rescue system > > > A: "Slackware ARM port" > > > Data: Gioved? 5 maggio 2011, 10:15 > > > Busybox has an internal micro web > > > server > > > root at surap:~# busybox httpd --help > > > BusyBox v1.18.4 (2011-04-20 14:04:26 BST) > multi-call > > > binary. > > > > > > Usage: httpd [-ifv[v]] [-c CONFFILE] [-p > [IP:]PORT] > > [-u > > > USER[:GRP]] [-r REALM] [-h HOME] > > > or httpd -d/-e/-m STRING > > > > > > Listen for incoming HTTP requests > > > > > > Options: > > > ? ? ? ? -i? ? ? ? > > > ? ? ? Inetd mode > > > ? ? ? ? -f? ? ? ? > > > ? ? ? Don't daemonize > > > ? ? ? ? -v[v]? ? ? > > > ? ???Verbose > > > ? ? ? ? -p [IP:]PORT? ? Bind > > > to IP:PORT (default *:80) > > > ? ? ? ? -u > > > USER[:GRP]???Set uid/gid after binding to > > > port > > > ? ? ? ? -r REALM? ? ? > > > ? Authentication Realm for Basic Authentication > > > ? ? ? ? -h HOME? ? ? > > > ???Home directory (default .) > > > ? ? ? ? -c FILE? ? ? > > > ???Configuration file (default > > > {/etc,HOME}/httpd.conf) > > > ? ? ? ? -m STRING? ? > > > ???MD5 crypt STRING > > > ? ? ? ? -e STRING? ? > > > ???HTML encode STRING > > > ? ? ? ? -d STRING? ? > > > ???URL decode STRING > > > > > > I'll be getting rid of apache in the microroot > system > > > > > > --- Mer 4/5/11, Davide > > > ha scritto: > > > > > > > Da: Davide > > > > Oggetto: [ARMedslack] R:? R:? micro root > > > rescue system > > > > A: "Slackware ARM port" > > > > Data: Mercoled? 4 maggio 2011, 00:57 > > > > Ok I've the first working image with > > > > all the basics working. > > > > > > > > This is what's in the image: > > > > root at hp:/mnt/hd/usr/src/surap_packages# ls > > > > at-3.1.12-arm-1.tgz? ? ? ? ? > > > > ? iptables-1.4.10-arm-1.tgz > > > > busybox-1.18.4-arm-1.tgz? ? > > > > ???iw-0.9.20-arm-1.tgz > > > > dnsmasq-2.52-arm-1.tgz? ? ? > > > > ???kernel-firmware-2.6.38.3-noarch-1.tgz > > > > dropbear-0.53.1-arm-1.tgz? ? ? > > > > kernel_2.6.38.3-microkirkwood-arm-1.tgz > > > > php-5.3.5-arm-1.tgz? ? ? ? ? > > > > ? glibc-solibs-2.13-arm-1.tgz? > > > > ppp-2.4.5-arm-1.tgz? ? ? ? ? > > > > ? hostapd-0.7.3-arm-1.tgz? ? ? > > > > udev-165-arm-2.tgz? ? ? ? ? > > > > ???httpd-2.2.17-arm-2.tgz? ? > > > > ??? > > > > usb_modeswitch-1.1.6-arm-1.tgz > > > wireless-tools-29-arm-2.tgz > > > > root at hp:/mnt/hd/usr/src/surap_packages# > > > > and a few other required libs picked > manually > > > > > > > > The compressed and unsummed jffs2 is 41Mb > big > > > > > > > > root at hp:/mnt/hd/usr/src/surap_packages# du > -ms > > > > ../surap_busybox.jffs2 > > > > 41? ? ? ../surap_busybox.jffs2 > > > > root at hp:/mnt/hd/usr/src/surap_packages# > > > > > > > > usb_modeswitch will not work because it > needs > > tclsh > > > and I > > > > don't want to add it unless it's really > > necessary. > > > I'll try > > > > working around the problem with pure busybox > ash > > > scripting > > > > ... if that's not possible I'll write a > small c > > > program to > > > > help out ash. > > > > > > > > Regards > > > > David > > > > > > > > --- Mar 3/5/11, Davide > > > > ha scritto: > > > > > > > > > Da: Davide > > > > > Oggetto: [ARMedslack] R:? micro root > > rescue > > > > system > > > > > A: "Slackware ARM port" > > > > > Data: Marted? 3 maggio 2011, 08:43 > > > > > I struck another little problem while > > > > > trying to keep things as much slackware > as > > > possible: > > > > > busybox default shell (the most > complete > > one) > > > seems to > > > > have > > > > > no support for arrays. Slackware's > > > > /etc/rc.d/rc.inet1.conf > > > > > is all array config file. > > > > > > > > > > In order to at least keep the same > > parameter > > > names > > > > with no > > > > > array index I moved to making > > > ifcfg. > > > > whose > > > > > contents would be the unindexed > variables > > for > > > each > > > > > interface. Now this is a bit redhatish > but I > > was > > > > unable to > > > > > think of any other slackware like > solution > > with > > > no > > > > arrays. > > > > > > > > > > Anyone have any idea ? > > > > > > > > > > Regards > > > > > David > > > > > > > > > > --- Ven 22/4/11, Davide > > > > > ha scritto: > > > > > > > > > > > Da: Davide > > > > > > Oggetto: [ARMedslack] micro root > > rescue > > > system > > > > > > A: "Slackware ARM port" > > > > > > Data: Venerd? 22 Aprile 2011, > 11:45 > > > > > > Sorry for starting a new thread > on > > > > > > something that was started > elsewhere > > .... > > > but > > > > maybe > > > > > the > > > > > > shoot-off needs better attention > with a > > new > > > > thread. > > > > > > > > > > > > >> This is a mix of a few I > > built > > > myself > > > > and > > > > > some > > > > > > gotten from current. > > > > > > >> This is what I'll be > working > > with > > > and > > > > should > > > > > fit > > > > > > in a compressed > > > > > > >> jffs2 image 64Mb big. > > > > > > >> > > > root at slackware:/usr/src/surap_packages# > > > > du > > > > > -ms * | > > > > > > sort -n > > > > > > >> 1 ? > busybox-1.18.4-arm-1.tgz > > > > > > >> 1? ? > > dropbear-0.53.1-arm-1.tgz > > > > > > >> 1 ? > hostapd-0.7.3-arm-1.tgz > > > > > > >> 1? ? > > iptables-1.4.10-arm-1.tgz > > > > > > >> 1 > ???iw-0.9.20-arm-1.tgz > > > > > > >> 1 > ???ppp-2.4.5-arm-1.tgz > > > > > > >> 1 > ???udev-165-arm-2.tgz > > > > > > >> 1? ? > > > usb_modeswitch-1.1.6-arm-1.tgz > > > > > > >> 1? ? > > wireless-tools-29-arm-2.tgz > > > > > > >> 2? ? > httpd-2.2.17-arm-2.tgz > > > > > > >> 2? ? > > > > kernel-firmware-2.6.38.3-noarch-1.tgz > > > > > > >> 5? ? > > glibc-solibs-2.13-arm-1.tgz > > > > > > >> 8? ? > > > > kernel_kirkwood-2.6.38.3-arm-1.tgz > > > > > > >> 10?? > php-5.3.5-arm-1.tgz > > > > > > >> > > > > > > > > > > > > > > > > > > > > > 15???kernel-modules-kirkwood-2.6.38.3_kirkwood-arm-1.tgz > > > > > > >> > > > root at slackware:/usr/src/surap_packages# > > > > du > > > > > -ms . > > > > > > >> 43? ? ? . > > > > > > >> > > > root at slackware:/usr/src/surap_packages# > > > > > > >> > > > > > > >> Since booting from jffs2 > image > > does > > > not > > > > > require > > > > > > initrd ... and maybe > > > > > > >> one can do without > > documentation > > > .... > > > > I'll > > > > > see if > > > > > > I can fit that in a > > > > > > >> 32Mb image. > > > > > > >> > > > > > > > Build a custom kernel with > few > > modules > > > ;) > > > > > > > > > > > > I will strip all unnecessary > modules > > for a > > > > rescue > > > > > system, > > > > > > remove initrd, strip documentation > and > > carve > > > down > > > > as > > > > > much as > > > > > > possible ... if it won't fit I'll > > consider > > > thttpd > > > > and > > > > > some > > > > > > lighter web scripting language. > Maybe > > web > > > stuff > > > > is > > > > > not > > > > > > really necessary for a rescue > system > > > anyway. > > > > > > > > > > > > Now I've a question. > > > > > > there are 2 ways to do this: > > > > > > 1) repackage the single packages > and > > append > > > some > > > > > suffix to > > > > > > distinguish them from the > standard > > > packages, > > > > possibly > > > > > modify > > > > > > the build scripts for them so > that > > future > > > > maintenance > > > > > will > > > > > > be easier, > > > > > > > > > > > > 2) just shove everything needed > > somewhere > > > and > > > > remove > > > > > all > > > > > > that is not needed and then build > the > > jffs2 > > > > image. > > > > > > > > > > > > Now if this micro root system is > just > > going > > > to be > > > > my > > > > > > personal AP/3g/NAS/router/rescue > the > > second > > > way > > > > will > > > > > take > > > > > > much less effort, on the other > hand if > > you > > > like > > > > the > > > > > idea of > > > > > > having an armedslack micro root > system > > that > > > will > > > > be > > > > > more > > > > > > then just a rescue system and > possibly > > fit > > > in a > > > > 32Mb > > > > > > compressed image; well then we > should > > go > > > about > > > > the > > > > > first > > > > > > way. > > > > > > I say we because I'm just a user > and > > even if > > > I do > > > > most > > > > > of > > > > > > the dirty work I'll need > assistance > > from > > > the > > > > > ARMedslack team > > > > > > to do some of the required actions > if > > this > > > is of > > > > any > > > > > > interest to ARMedslack community. > > > > > > > > > > > > > I've no reservation in sharing my > work > > as I > > > > consider > > > > > all my > > > > > > work GPL + it's mainly just > > administration > > > so > > > > the > > > > > question > > > > > > really is: Does armedslack want a > > smart > > > micro > > > > root > > > > > system ? > > > > > > > > > > > > Best regards > > > > > > David Rao > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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 > > > > > > > > > > _______________________________________________ > > > > 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 > > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > From dowelld at netscape.net Fri Jul 1 09:18:09 2011 From: dowelld at netscape.net (Dave Dowell) Date: Fri, 01 Jul 2011 10:18:09 +0100 Subject: [ARMedslack] iOmega iConnect Message-ID: <4E0D90D1.8050801@netscape.net> Hello everyone, I've installed ARMedslack onto one of these now. http://go.iomega.com/en/products/network-storage-desktop/wireless-data-station/network-hard-drive-iconnect/ *Specification* * Desktop, compact form factor * Marvell 6281 CPU at 1.0GHz with 256MB RAM * 1 x RJ45 10/100/1000Mbps (GbE) Ethernet port LAN standards: IEEE 802.3, IEEE 802.3u * Wireless (802.11b/g/n) * 4 x USB 2.0 ports (to connect external HDD, printers) * AC Voltage 100-240 VAC * Power consumption -- 5 Watts * Documentation localized for 18 languages, including; English, German, Spanish, French, Italian, Brazilian Portuguese, Chinese Simplified, and Russian It doesn't mention the onboard flash memory there, but it also has 512MB of flash built in. It's a Marvell Orion board inside, complete with the header for a TTL to USB serial console. The console can be rigged like this http://doip.org/iconnect_console I've recompiled the kernel to include the following options: (Could these be added into the standard ARMedslack kernel config please ?) > CONFIG_RT2800PCI=m > CONFIG_RT2800PCI_RT33XX=y > CONFIG_RT2800PCI_RT35XX=y However it probably only requires the first of them. This has made the onboard Ralink wireless adapter available. I'm trying to hack the mapower architecture code changes into the kernel code to get the pretty LEDs working, but have had varying degrees of success with that so far, I think I've got the code in and working, however I've yet to figure out how to control the LEDs. So I'm hacking away at the default (flash) image (debian 5) to try and figure out how they've done it. It looks like they're controlling it with a closed source binary atm. The Sheeva Plug install instructions work for the install. Anyway, other than that it works well, and it's a cheap device :-) Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From sunsmoke at gmail.com Fri Jul 1 19:19:46 2011 From: sunsmoke at gmail.com (Greg Lim) Date: Fri, 1 Jul 2011 15:19:46 -0400 Subject: [ARMedslack] iOmega iConnect In-Reply-To: <4E0D90D1.8050801@netscape.net> References: <4E0D90D1.8050801@netscape.net> Message-ID: <565BEF19-B474-45B8-8EDB-8EE0319D7D8D@gmail.com> Dave, this is great work. You've inspired me to purchase one of these. -Greg Lim Sent from my VT102 On Jul 1, 2011, at 5:18 AM, Dave Dowell wrote: > Hello everyone, > > I've installed ARMedslack onto one of these now. > http://go.iomega.com/en/products/network-storage-desktop/wireless-data-station/network-hard-drive-iconnect/ > > Specification > Desktop, compact form factor > Marvell 6281 CPU at 1.0GHz with 256MB RAM > 1 x RJ45 10/100/1000Mbps (GbE) Ethernet port > LAN standards: IEEE 802.3, IEEE 802.3u > Wireless (802.11b/g/n) > 4 x USB 2.0 ports (to connect external HDD, printers) > AC Voltage 100-240 VAC > Power consumption ? 5 Watts > Documentation localized for 18 languages, including; English, German, Spanish, French, Italian, Brazilian Portuguese, Chinese Simplified, and Russian > It doesn't mention the onboard flash memory there, but it also has 512MB of flash built in. > > It's a Marvell Orion board inside, complete with the header for a TTL to USB serial console. > The console can be rigged like this http://doip.org/iconnect_console > > I've recompiled the kernel to include the following options: (Could these be added into the standard ARMedslack kernel config please ?) > > CONFIG_RT2800PCI=m > > CONFIG_RT2800PCI_RT33XX=y > > CONFIG_RT2800PCI_RT35XX=y > > However it probably only requires the first of them. This has made the onboard Ralink wireless adapter available. > > I'm trying to hack the mapower architecture code changes into the kernel code to get the pretty LEDs working, but have had varying degrees of success with that so far, I think I've got the code in and working, however I've yet to figure out how to control the LEDs. So I'm hacking away at the default (flash) image (debian 5) to try and figure out how they've done it. It looks like they're controlling it with a closed source binary atm. > > The Sheeva Plug install instructions work for the install. > > Anyway, other than that it works well, and it's a cheap device :-) > > Thanks > Dave > > _______________________________________________ > 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 Fri Jul 1 20:49:04 2011 From: dowelld at netscape.net (Dave Dowell) Date: Fri, 01 Jul 2011 21:49:04 +0100 Subject: [ARMedslack] iOmega iConnect In-Reply-To: <565BEF19-B474-45B8-8EDB-8EE0319D7D8D@gmail.com> References: <4E0D90D1.8050801@netscape.net> <565BEF19-B474-45B8-8EDB-8EE0319D7D8D@gmail.com> Message-ID: <4E0E32C0.3050508@netscape.net> I was right about the kernel code for making the leds work, I have managed to get it working. It creates an object for each led in /sys/class/leds and each led contains a brightness object which can be manipulated to change turn the leds on and off... now I just have to work out how to automate that with udev. The same code also includes the objects for the onboard button, but I'll be buggered if I know where to start with that one yet. I can see it has been found and that the interrupts are being detected when it's pressed though :-) I'll knock up a page with some information / downloadable files and put up for this, once I've moved this all forward a bit. Thanks Dave On 01/07/2011 20:19, Greg Lim wrote: > Dave, this is great work. You've inspired me to purchase one of these. > > -Greg Lim > > Sent from my VT102 > > On Jul 1, 2011, at 5:18 AM, Dave Dowell > wrote: > >> Hello everyone, >> >> I've installed ARMedslack onto one of these now. >> http://go.iomega.com/en/products/network-storage-desktop/wireless-data-station/network-hard-drive-iconnect/ >> >> *Specification* >> >> * Desktop, compact form factor >> * Marvell 6281 CPU at 1.0GHz with 256MB RAM >> * 1 x RJ45 10/100/1000Mbps (GbE) Ethernet port >> LAN standards: IEEE 802.3, IEEE 802.3u >> * Wireless (802.11b/g/n) >> * 4 x USB 2.0 ports (to connect external HDD, printers) >> * AC Voltage 100-240 VAC >> * Power consumption ? 5 Watts >> * Documentation localized for 18 languages, including; English, >> German, Spanish, French, Italian, Brazilian Portuguese, Chinese >> Simplified, and Russian >> >> It doesn't mention the onboard flash memory there, but it also has >> 512MB of flash built in. >> >> It's a Marvell Orion board inside, complete with the header for a TTL >> to USB serial console. >> The console can be rigged like this http://doip.org/iconnect_console >> >> I've recompiled the kernel to include the following options: (Could >> these be added into the standard ARMedslack kernel config please ?) >> > CONFIG_RT2800PCI=m >> > CONFIG_RT2800PCI_RT33XX=y >> > CONFIG_RT2800PCI_RT35XX=y >> >> However it probably only requires the first of them. This has made >> the onboard Ralink wireless adapter available. >> >> I'm trying to hack the mapower architecture code changes into the >> kernel code to get the pretty LEDs working, but have had varying >> degrees of success with that so far, I think I've got the code in and >> working, however I've yet to figure out how to control the LEDs. So >> I'm hacking away at the default (flash) image (debian 5) to try and >> figure out how they've done it. It looks like they're controlling it >> with a closed source binary atm. >> >> The Sheeva Plug install instructions work for the install. >> >> Anyway, other than that it works well, and it's a cheap device :-) >> >> Thanks >> Dave >> >> _______________________________________________ >> 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 louigi600 at yahoo.it Thu Jul 14 13:06:01 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 14 Jul 2011 14:06:01 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 Message-ID: <1310648761.79071.YahooMailClassic@web29712.mail.ird.yahoo.com> My last day at the old work the work mate gave me a Toshiba AC100 as a present (one of those nvidia tegra dual core arm based netbooks with android): how do I put armedslack in this thing ? Regards David From thenktor at gmx.de Thu Jul 14 13:30:14 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 14 Jul 2011 15:30:14 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310648761.79071.YahooMailClassic@web29712.mail.ird.yahoo.com> References: <1310648761.79071.YahooMailClassic@web29712.mail.ird.yahoo.com> Message-ID: <201107141530.14616.thenktor@gmx.de> Am Thursday 14 July 2011 15:06:01 schrieb Davide: > My last day at the old work the work mate gave me a Toshiba AC100 as a > present (one of those nvidia tegra dual core arm based netbooks with > android): how do I put armedslack in this thing ? You can search the ML archive for this message and ask Manfred: > > I wonder If anyone has tried ARMed Slack on a Toshiba AC100 netbook? > > Hi Thorsten, > > at the very moment I've started porting FluxFlux to ARMed Slack using the > ac100 as dev machine. > > I'm at a very early stage, but I think this netbook is a very good start > to be prepared for the release of tegra 4. > > Regards, > > Manfred aka Quax -- Thorsten M?hlfelder Salix OS: www.salixos.org From manfred.mueller at lin2go.com Thu Jul 14 14:42:16 2011 From: manfred.mueller at lin2go.com (=?utf-8?Q?Manfred_M=C3=BCller?=) Date: Thu, 14 Jul 2011 16:42:16 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <201107141530.14616.thenktor@gmx.de> References: <1310648761.79071.YahooMailClassic@web29712.mail.ird.yahoo.com> <201107141530.14616.thenktor@gmx.de> Message-ID: <1310654536369510500@lin2go.com> An embedded and charset-unspecified text was scrubbed... Name: not available URL: From louigi600 at yahoo.it Thu Jul 14 15:15:35 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 14 Jul 2011 16:15:35 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310654536369510500@lin2go.com> Message-ID: <1310656535.84820.YahooMailClassic@web29720.mail.ird.yahoo.com> Hum well I can do with the ordinary fluxbox as long as the touchpad works. I could even accept to run on it a framebuffer kdrive as xserver as long as I can have an ordinary linux distribution on it (possibly slackware or slackware based). The real questions are: do I haveto stick with the original bootloader whatever it is or has someone ported uboot or something else to it or do I haveto work with kexecboot ? do I haveto stick with the origina kernel to get all the onboard devices working or can a vanilla kernel be configured to handle all the devices on this thing ? will the armedslack binaries run on the ac100 or do they need to be compiled specially for this specific arm processor ? Regards David --- Gio 14/7/11, Manfred M?ller ha scritto: > Da: Manfred M?ller > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: "Slackware ARM port" > Data: Gioved? 14 luglio 2011, 16:42 > Hi list, > > > You can search the ML archive for this message and ask > Manfred: > > although I still own this littele thing I gave up on > porting ARMedslack to it > because I have to finish the tablet version of FluxFlux > first... > > @Thorsten: > > ot: was it really needed to reinvent the wheel with Salt > instead of improving the legacy LLS? > > Regards, Manfred > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Thu Jul 14 15:26:54 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 14 Jul 2011 17:26:54 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310654536369510500@lin2go.com> References: <1310648761.79071.YahooMailClassic@web29712.mail.ird.yahoo.com> <201107141530.14616.thenktor@gmx.de> <1310654536369510500@lin2go.com> Message-ID: <201107141726.54839.thenktor@gmx.de> Am Thursday 14 July 2011 16:42:16 schrieb Manfred M?ller: > @Thorsten: > > ot: was it really needed to reinvent the wheel with Salt instead of > improving the legacy LLS? I'm not a Linux Live user, so you have to ask this question on our ML ;-) -- Thorsten M?hlfelder Salix OS: www.salixos.org From dowelld at netscape.net Thu Jul 14 15:29:59 2011 From: dowelld at netscape.net (Dave Dowell) Date: Thu, 14 Jul 2011 16:29:59 +0100 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310656535.84820.YahooMailClassic@web29720.mail.ird.yahoo.com> References: <1310656535.84820.YahooMailClassic@web29720.mail.ird.yahoo.com> Message-ID: <4E1F0B77.1000701@netscape.net> Here's a page which covers the bootloader http://tosh-ac100.wetpaint.com/page/Ubuntu Thanks Dave On 14/07/2011 16:15, Davide wrote: > Hum well I can do with the ordinary fluxbox as long as the touchpad works. > I could even accept to run on it a framebuffer kdrive as xserver as long as I can have an ordinary linux distribution on it (possibly slackware or slackware based). > > The real questions are: > do I haveto stick with the original bootloader whatever it is or has someone ported uboot or something else to it or do I haveto work with kexecboot ? > > do I haveto stick with the origina kernel to get all the onboard devices working or can a vanilla kernel be configured to handle all the devices on this thing ? > > will the armedslack binaries run on the ac100 or do they need to be compiled specially for this specific arm processor ? > > Regards > David > > --- Gio 14/7/11, Manfred M?ller ha scritto: > >> Da: Manfred M?ller >> Oggetto: Re: [ARMedslack] Got a toshiba AC100 >> A: "Slackware ARM port" >> Data: Gioved? 14 luglio 2011, 16:42 >> Hi list, >> >>> You can search the ML archive for this message and ask >> Manfred: >> >> although I still own this littele thing I gave up on >> porting ARMedslack to it >> because I have to finish the tablet version of FluxFlux >> first... >> >> @Thorsten: >> >> ot: was it really needed to reinvent the wheel with Salt >> instead of improving the legacy LLS? >> >> Regards, Manfred >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From thenktor at gmx.de Thu Jul 14 15:50:09 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 14 Jul 2011 17:50:09 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <4E1F0B77.1000701@netscape.net> References: <1310656535.84820.YahooMailClassic@web29720.mail.ird.yahoo.com> <4E1F0B77.1000701@netscape.net> Message-ID: <201107141750.09635.thenktor@gmx.de> Am Thursday 14 July 2011 17:29:59 schrieb Dave Dowell: > Here's a page which covers the bootloader > http://tosh-ac100.wetpaint.com/page/Ubuntu And there also is a kernel available and a rootfs (which probably can be exchanged with the ARMed Slack one): http://ac100.gudinna.com/ > > On 14/07/2011 16:15, Davide wrote: > > Hum well I can do with the ordinary fluxbox as long as the touchpad > > works. I could even accept to run on it a framebuffer kdrive as xserver > > as long as I can have an ordinary linux distribution on it (possibly > > slackware or slackware based). > > > > The real questions are: > > do I haveto stick with the original bootloader whatever it is or has > > someone ported uboot or something else to it or do I haveto work with > > kexecboot ? > > > > do I haveto stick with the origina kernel to get all the onboard devices > > working or can a vanilla kernel be configured to handle all the devices > > on this thing ? > > > > will the armedslack binaries run on the ac100 or do they need to be > > compiled specially for this specific arm processor ? > > > > Regards > > David > > > > --- Gio 14/7/11, Manfred M?ller ha scritto: > >> Da: Manfred M?ller > >> Oggetto: Re: [ARMedslack] Got a toshiba AC100 > >> A: "Slackware ARM port" > >> Data: Gioved? 14 luglio 2011, 16:42 > >> Hi list, > >> > >>> You can search the ML archive for this message and ask > >> > >> Manfred: > >> > >> although I still own this littele thing I gave up on > >> porting ARMedslack to it > >> because I have to finish the tablet version of FluxFlux > >> first... > >> > >> @Thorsten: > >> > >> ot: was it really needed to reinvent the wheel with Salt > >> instead of improving the legacy LLS? > >> > >> Regards, Manfred > >> _______________________________________________ > >> 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 > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Thu Jul 14 18:00:30 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 14 Jul 2011 19:00:30 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <4E1F0B77.1000701@netscape.net> Message-ID: <1310666430.459.YahooMailClassic@web29713.mail.ird.yahoo.com> Thanks Dave ... nice wiki lots of info. Will need a good deal of reading. Ubuntu is not ma fabourit but maybe I can use the info to get another distro running. David --- Gio 14/7/11, Dave Dowell ha scritto: > Da: Dave Dowell > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: armedslack at lists.armedslack.org > Data: Gioved? 14 luglio 2011, 17:29 > Here's a page which covers the > bootloader > http://tosh-ac100.wetpaint.com/page/Ubuntu > > Thanks > Dave > > On 14/07/2011 16:15, Davide wrote: > > Hum well I can do with the ordinary fluxbox as long as > the touchpad works. > > I could even accept to run on it a framebuffer kdrive > as xserver as long as I can have an ordinary linux > distribution on it (possibly slackware or slackware based). > > > > The real questions are: > > do I haveto stick with the original bootloader > whatever it is or has someone ported uboot or something else > to it or do I haveto work with kexecboot ? > > > > do I haveto stick with the origina kernel to get all > the onboard devices working or can a vanilla kernel be > configured to handle all the devices on this thing ? > > > > will the armedslack binaries run on the ac100 or do > they need to be compiled specially for this specific arm > processor ? > > > > Regards > > David > > > > --- Gio 14/7/11, Manfred M?ller? > ha scritto: > > > >> Da: Manfred M?ller > >> Oggetto: Re: [ARMedslack] Got a toshiba AC100 > >> A: "Slackware ARM port" > >> Data: Gioved? 14 luglio 2011, 16:42 > >> Hi list, > >> > >>> You can search the ML archive for this message > and ask > >> Manfred: > >> > >> although I still own this littele thing I gave up > on > >> porting ARMedslack to it > >> because I have to finish the tablet version of > FluxFlux > >> first... > >> > >> @Thorsten: > >> > >> ot: was it really needed to reinvent the wheel > with Salt > >> instead of improving the legacy LLS? > >> > >> Regards, Manfred > >> _______________________________________________ > >> 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 > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From louigi600 at yahoo.it Thu Jul 14 18:07:31 2011 From: louigi600 at yahoo.it (Davide) Date: Thu, 14 Jul 2011 19:07:31 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <201107141750.09635.thenktor@gmx.de> Message-ID: <1310666851.13601.YahooMailClassic@web29703.mail.ird.yahoo.com> Armedslack current I thinks needs 2.6.32 or udev will need to be downgraded ... the libs should be ok as if I remember right they require 2.6.26 or better. But that's not the major issue right now ;-) I'm worried about binary compatibility as "armedslack binaries will run on almost any arm platform" but that does not mean they will run on every arm platform. David --- Gio 14/7/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: "Slackware ARM port" > Data: Gioved? 14 luglio 2011, 17:50 > Am Thursday 14 July 2011 17:29:59 > schrieb Dave Dowell: > > Here's a page which covers the bootloader > > http://tosh-ac100.wetpaint.com/page/Ubuntu > > And there also is a kernel available and a rootfs (which > probably can be > exchanged with the ARMed Slack one): > http://ac100.gudinna.com/ > > > > > > On 14/07/2011 16:15, Davide wrote: > > > Hum well I can do with the ordinary fluxbox as > long as the touchpad > > > works. I could even accept to run on it a > framebuffer kdrive as xserver > > > as long as I can have an ordinary linux > distribution on it (possibly > > > slackware or slackware based). > > > > > > The real questions are: > > > do I haveto stick with the original bootloader > whatever it is or has > > > someone ported uboot or something else to it or > do I haveto work with > > > kexecboot ? > > > > > > do I haveto stick with the origina kernel to get > all the onboard devices > > > working or can a vanilla kernel be configured to > handle all the devices > > > on this thing ? > > > > > > will the armedslack binaries run on the ac100 or > do they need to be > > > compiled specially for this specific arm > processor ? > > > > > > Regards > > > David > > > > > > --- Gio 14/7/11, Manfred M?ller? > ha scritto: > > >> Da: Manfred M?ller > > >> Oggetto: Re: [ARMedslack] Got a toshiba > AC100 > > >> A: "Slackware ARM port" > > >> Data: Gioved? 14 luglio 2011, 16:42 > > >> Hi list, > > >> > > >>> You can search the ML archive for this > message and ask > > >> > > >> Manfred: > > >> > > >> although I still own this littele thing I > gave up on > > >> porting ARMedslack to it > > >> because I have to finish the tablet version > of FluxFlux > > >> first... > > >> > > >> @Thorsten: > > >> > > >> ot: was it really needed to reinvent the > wheel with Salt > > >> instead of improving the legacy LLS? > > >> > > >> Regards, Manfred > > >> > _______________________________________________ > > >> 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 > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Thu Jul 14 18:34:30 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Thu, 14 Jul 2011 20:34:30 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310666851.13601.YahooMailClassic@web29703.mail.ird.yahoo.com> References: <201107141750.09635.thenktor@gmx.de> <1310666851.13601.YahooMailClassic@web29703.mail.ird.yahoo.com> Message-ID: <20110714203430.42cc0a47@pinkfloyd.tm-net> Am Thu, 14 Jul 2011 19:07:31 +0100 (BST) schrieb Davide : > I'm worried about binary compatibility as "armedslack > binaries will run on almost any arm platform" but that does not mean > they will run on every arm platform. They are built for armv4 and the Tegra should be at least armv6 so they should run without problems. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Fri Jul 15 07:21:53 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 15 Jul 2011 08:21:53 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <20110714203430.42cc0a47@pinkfloyd.tm-net> Message-ID: <1310714513.23670.YahooMailClassic@web29705.mail.ird.yahoo.com> Ok I followed instructions from http://ac100.gudinna.com/README/ to get ubuntoo 10.10 working off the SD. I then mixed up an armedslack miniroot 13.1 (any higher would hit the udev kernel version requirement issue) with the kernel modules from ubuntu 10.10 for ac100 in an attempt to get a base system booting off the SD. All looked right while starting to boot until I hit a kernel panic: attempting to kill init Anyone have any ideas how to fix this or what's actually causing it ? Having got as far as that I suppose the root got mounted. Init being the first binary to be executed I guess it's having some trouble: could it be something wrong with the console ? I got very few messages on console while kernel was starting so I suppose ither kernel has been configured to be very quiet or the console is not where I'm looking. Could init kill itself if it finds nowhere to spraun getty for console ? Regards David --- Gio 14/7/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: armedslack at lists.armedslack.org > Data: Gioved? 14 luglio 2011, 20:34 > Am Thu, 14 Jul 2011 19:07:31 +0100 > (BST) > schrieb Davide : > > > I'm worried about binary compatibility as "armedslack > > binaries will run on almost any arm platform" but that > does not mean > > they will run on every arm platform. > > They are built for armv4 and the Tegra should be at least > armv6 so they > should run without problems. > > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Fri Jul 15 08:14:27 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 15 Jul 2011 10:14:27 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310714513.23670.YahooMailClassic@web29705.mail.ird.yahoo.com> References: <1310714513.23670.YahooMailClassic@web29705.mail.ird.yahoo.com> Message-ID: <201107151014.27711.thenktor@gmx.de> Am Friday 15 July 2011 09:21:53 schrieb Davide: > Ok I followed instructions from http://ac100.gudinna.com/README/ to get > ubuntoo 10.10 working off the SD. > > I then mixed up an armedslack miniroot 13.1 (any higher would hit the udev > kernel version requirement issue) with the kernel modules from ubuntu 10.10 > for ac100 in an attempt to get a base system booting off the SD. > > All looked right while starting to boot until I hit a kernel panic: > attempting to kill init Could you make some photos of the interesting error messages? If you do, don't attach them to the mail. Instead upload them to an image hoster. -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Fri Jul 15 09:23:06 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 15 Jul 2011 10:23:06 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <201107151014.27711.thenktor@gmx.de> Message-ID: <1310721786.14478.YahooMailClassic@web29702.mail.ird.yahoo.com> To reduce possible faliures to a minimum I did the same with clashNG. Maybe I did not look well enough the first time but this time I got for sure another intresting message before init killing itself: Kernel too old Don't think a picture is necessary for that. Now I'm not 100% sure that I also had this on slackware 13.1 miniroot but since I use slackware 13.1 to build clashNG I'm strongly suspecting that I had the same message but did not notice it since it wan not on the last line. Damn .... Anyone know what boot loader is on the AC100 ... maybe it's possible to have more then one kernel lingering around ? Anyone know how to build kernel for the ac100 that will run armedslack ? Regards David --- Ven 15/7/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: "Slackware ARM port" > Data: Venerd? 15 luglio 2011, 10:14 > Am Friday 15 July 2011 09:21:53 > schrieb Davide: > > Ok I followed instructions from http://ac100.gudinna.com/README/ to get > > ubuntoo 10.10 working off the SD. > > > > I then mixed up an armedslack miniroot 13.1 (any > higher would hit the udev > > kernel version requirement issue) with the kernel > modules from ubuntu 10.10 > > for ac100 in an attempt to get a base system booting > off the SD. > > > > All looked right while starting to boot until I hit a > kernel panic: > > attempting to kill init > > Could you make some photos of the interesting error > messages? If you do, don't > attach them to the mail. Instead upload them to an image > hoster. > > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thenktor at gmx.de Fri Jul 15 09:49:26 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 15 Jul 2011 11:49:26 +0200 Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <1310721786.14478.YahooMailClassic@web29702.mail.ird.yahoo.com> References: <1310721786.14478.YahooMailClassic@web29702.mail.ird.yahoo.com> Message-ID: <201107151149.26676.thenktor@gmx.de> Take a look here: http://people.canonical.com/~ogra/tegra/2.6.37/ and https://launchpad.net/~ac100/+archive/ppa Perhaps you'll find a working kernel there. Otherwise you should find newer kernel sources there and the config of the 2.6.29 kernel here: http://ac100.gudinna.com/kernel/config.txt You could use Codesourcery's toolchain to cross compile this kernel then. Make sure you are using the EABI toolchain. You also could compile the kernel on a Dockstar or some other ARMed Slack system. Am Friday 15 July 2011 11:23:06 schrieb Davide: > To reduce possible faliures to a minimum I did the same with clashNG. > Maybe I did not look well enough the first time but this time I got for > sure another intresting message before init killing itself: Kernel too old > > Don't think a picture is necessary for that. > > Now I'm not 100% sure that I also had this on slackware 13.1 miniroot but > since I use slackware 13.1 to build clashNG I'm strongly suspecting that I > had the same message but did not notice it since it wan not on the last > line. > > Damn .... > > Anyone know what boot loader is on the AC100 ... maybe it's possible to > have more then one kernel lingering around ? Anyone know how to build > kernel for the ac100 that will run armedslack ? > > Regards > David > > --- Ven 15/7/11, Thorsten M?hlfelder ha scritto: > > Da: Thorsten M?hlfelder > > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > > A: "Slackware ARM port" > > Data: Venerd? 15 luglio 2011, 10:14 > > Am Friday 15 July 2011 09:21:53 > > > > schrieb Davide: > > > Ok I followed instructions from http://ac100.gudinna.com/README/ to get > > > ubuntoo 10.10 working off the SD. > > > > > > I then mixed up an armedslack miniroot 13.1 (any > > > > higher would hit the udev > > > > > kernel version requirement issue) with the kernel > > > > modules from ubuntu 10.10 > > > > > for ac100 in an attempt to get a base system booting > > > > off the SD. > > > > > All looked right while starting to boot until I hit a > > > > kernel panic: > > > attempting to kill init > > > > Could you make some photos of the interesting error > > messages? If you do, don't > > attach them to the mail. Instead upload them to an image > > hoster. > > > > > > -- > > Thorsten M?hlfelder > > Salix OS: www.salixos.org > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- Thorsten M?hlfelder Salix OS: www.salixos.org From louigi600 at yahoo.it Fri Jul 15 10:06:16 2011 From: louigi600 at yahoo.it (Davide) Date: Fri, 15 Jul 2011 11:06:16 +0100 (BST) Subject: [ARMedslack] Got a toshiba AC100 In-Reply-To: <201107151149.26676.thenktor@gmx.de> Message-ID: <1310724376.31480.YahooMailClassic@web29708.mail.ird.yahoo.com> Thanks ... good info. Can I have 2 kernels without having to hook up and reflash the original kernel ? If I flash the new kernel into partition 5 I guess that the original andriod will stop working correctly. Since currently I guess it's the only thing that will make all onboard peripherals work correctly it's something I don't want to do untill the open source kernel starts supporting everything. Regards David --- Ven 15/7/11, Thorsten M?hlfelder ha scritto: > Da: Thorsten M?hlfelder > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: "Slackware ARM port" > Data: Venerd? 15 luglio 2011, 11:49 > Take a look here: > http://people.canonical.com/~ogra/tegra/2.6.37/ > and > https://launchpad.net/~ac100/+archive/ppa > > Perhaps you'll find a working kernel there. Otherwise you > should find newer > kernel sources there and the config of the 2.6.29 kernel > here: > http://ac100.gudinna.com/kernel/config.txt > > You could use Codesourcery's toolchain to cross compile > this kernel then. Make > sure you are using the EABI toolchain. > You also could compile the kernel on a Dockstar or some > other ARMed Slack > system. > > > Am Friday 15 July 2011 11:23:06 schrieb Davide: > > To reduce possible faliures to a minimum I did the > same with clashNG. > > Maybe I did not look well enough the first time but > this time I got for > > sure another intresting message before init killing > itself: Kernel too old > > > > Don't think a picture is necessary for that. > > > > Now I'm not 100% sure that I also had this on > slackware 13.1 miniroot but > > since I use slackware 13.1 to build clashNG I'm > strongly suspecting that I > > had the same message but did not notice it since it > wan not on the last > > line. > > > > Damn .... > > > > Anyone know what boot loader is on the AC100 ... maybe > it's possible to > > have more then one kernel lingering around ? Anyone > know how to build > > kernel for the ac100 that will run armedslack ? > > > > Regards > > David > > > > --- Ven 15/7/11, Thorsten M?hlfelder > ha scritto: > > > Da: Thorsten M?hlfelder > > > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > > > A: "Slackware ARM port" > > > Data: Venerd? 15 luglio 2011, 10:14 > > > Am Friday 15 July 2011 09:21:53 > > > > > > schrieb Davide: > > > > Ok I followed instructions from http://ac100.gudinna.com/README/ to get > > > > ubuntoo 10.10 working off the SD. > > > > > > > > I then mixed up an armedslack miniroot 13.1 > (any > > > > > > higher would hit the udev > > > > > > > kernel version requirement issue) with the > kernel > > > > > > modules from ubuntu 10.10 > > > > > > > for ac100 in an attempt to get a base system > booting > > > > > > off the SD. > > > > > > > All looked right while starting to boot > until I hit a > > > > > > kernel panic: > > > > attempting to kill init > > > > > > Could you make some photos of the interesting > error > > > messages? If you do, don't > > > attach them to the mail. Instead upload them to > an image > > > hoster. > > > > > > > > > -- > > > Thorsten M?hlfelder > > > Salix OS: www.salixos.org > > > _______________________________________________ > > > ARMedslack mailing list > > > ARMedslack at lists.armedslack.org > > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- > Thorsten M?hlfelder > Salix OS: www.salixos.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From rworkman at slackbuilds.org Tue Jul 19 00:21:44 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 18 Jul 2011 19:21:44 -0500 Subject: [ARMedslack] Mailing list maintenance / move Message-ID: <20110718192144.25ba1aa0@liberty.rlwhome.lan> The SlackBuilds and ArmedSlack mailing lists will likely be unreachable for a (hopefully) short period of time within the next 24-48 hours; I'll be moving them over to a new (more stable) host. We'll still be available on IRC if needed [1] [1] SlackBuilds: #slackbuilds on freenode ArmedSlack: #armedslack on freenode -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dowelld at netscape.net Wed Jul 20 15:42:07 2011 From: dowelld at netscape.net (Dave Dowell) Date: Wed, 20 Jul 2011 16:42:07 +0100 Subject: [ARMedslack] Fwd: Re: iOmega iConnect Message-ID: <4E26F74F.7060000@netscape.net> Hello again, OK I've started putting some information about this up now. http://www.dowelld.net/viewtopic.php?f=1&t=3 Thanks Dave -------- Original Message -------- Subject: Re: [ARMedslack] iOmega iConnect Date: Fri, 01 Jul 2011 21:49:04 +0100 From: Dave Dowell To: armedslack at lists.armedslack.org I was right about the kernel code for making the leds work, I have managed to get it working. It creates an object for each led in /sys/class/leds and each led contains a brightness object which can be manipulated to change turn the leds on and off... now I just have to work out how to automate that with udev. The same code also includes the objects for the onboard button, but I'll be buggered if I know where to start with that one yet. I can see it has been found and that the interrupts are being detected when it's pressed though :-) I'll knock up a page with some information / downloadable files and put up for this, once I've moved this all forward a bit. Thanks Dave On 01/07/2011 20:19, Greg Lim wrote: > Dave, this is great work. You've inspired me to purchase one of these. > > -Greg Lim > > Sent from my VT102 > > On Jul 1, 2011, at 5:18 AM, Dave Dowell > wrote: > >> Hello everyone, >> >> I've installed ARMedslack onto one of these now. >> http://go.iomega.com/en/products/network-storage-desktop/wireless-data-station/network-hard-drive-iconnect/ >> >> *Specification* >> >> * Desktop, compact form factor >> * Marvell 6281 CPU at 1.0GHz with 256MB RAM >> * 1 x RJ45 10/100/1000Mbps (GbE) Ethernet port >> LAN standards: IEEE 802.3, IEEE 802.3u >> * Wireless (802.11b/g/n) >> * 4 x USB 2.0 ports (to connect external HDD, printers) >> * AC Voltage 100-240 VAC >> * Power consumption ? 5 Watts >> * Documentation localized for 18 languages, including; English, >> German, Spanish, French, Italian, Brazilian Portuguese, Chinese >> Simplified, and Russian >> >> It doesn't mention the onboard flash memory there, but it also has >> 512MB of flash built in. >> >> It's a Marvell Orion board inside, complete with the header for a TTL >> to USB serial console. >> The console can be rigged like this http://doip.org/iconnect_console >> >> I've recompiled the kernel to include the following options: (Could >> these be added into the standard ARMedslack kernel config please ?) >> > CONFIG_RT2800PCI=m >> > CONFIG_RT2800PCI_RT33XX=y >> > CONFIG_RT2800PCI_RT35XX=y >> >> However it probably only requires the first of them. This has made >> the onboard Ralink wireless adapter available. >> >> I'm trying to hack the mapower architecture code changes into the >> kernel code to get the pretty LEDs working, but have had varying >> degrees of success with that so far, I think I've got the code in and >> working, however I've yet to figure out how to control the LEDs. So >> I'm hacking away at the default (flash) image (debian 5) to try and >> figure out how they've done it. It looks like they're controlling it >> with a closed source binary atm. >> >> The Sheeva Plug install instructions work for the install. >> >> Anyway, other than that it works well, and it's a cheap device :-) >> >> Thanks >> Dave >> >> _______________________________________________ >> 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: