From frmrick at aapt.net.au Tue Jun 12 04:40:02 2012 From: frmrick at aapt.net.au (Rick Miles) Date: Tue, 12 Jun 2012 14:40:02 +1000 Subject: [ARMedslack] nfs and qemu install Message-ID: <1339476002.2573.17.camel@rick.miles.home> I've used nfs before for fileshares on our lan so I'm not a stranger there but I'm not so sure whats going on with a system, on qemu as an nfs client. I rsynced current last night Normally have dhcp via modem but changed to static ip configured with netconfig. Workstation 192.168.1.2 and gateway 192.168.1.1. Nobody else on lan so 192.168.1 3 and 4 are not assigned to anyone. As far as I know I can use rc.local-additions settings as is. I have edited /etc/exports as per qemu-install.txt. The one thing I am not clear on is what ip I assign the qemu machine do I give it 192.168.1.1 for a gateway and use 192.168.1.2 for the server? Should I give gemu machine a diffeent ip? I haven't bridged anything but a modem and that was a very long time ago. Qemu-install.txt just says Choose '3 - Install from NFS (Network Filesystem)' Enter the IP address: 192.168.1.1 Enter the directory: /export/armedslack/armedslack-current/slackware My path is different, thats all. I've tried for a couple hours using diffferent ip settings and can not get an nfs mount. Dropped out of setup and tried cli line and after making an entry to /etc/fstab but nfs but i just time out. I'm not quite sure what I should search for on the net and what I have found has not enlightened me. My qemu-1.0.1 install is from a slackbuild and I have run the debian raspberry pi build successfully on it. Host system is salix-13.37. Perhaps someone can give me a heads up on this -------------- next part -------------- An HTML attachment was scrubbed... URL: From frmrick at aapt.net.au Wed Jun 13 08:59:25 2012 From: frmrick at aapt.net.au (Rick Miles) Date: Wed, 13 Jun 2012 18:59:25 +1000 Subject: [ARMedslack] nfs and qemu install In-Reply-To: <1339476002.2573.17.camel@rick.miles.home> References: <1339476002.2573.17.camel@rick.miles.home> Message-ID: <1339577965.11443.26.camel@rick.miles.home> On Tue, 2012-06-12 at 14:40 +1000, Rick Miles wrote: > I've used nfs before for fileshares on our lan so I'm not a stranger > there but I'm not so sure whats going on with a system, on qemu as an > nfs client. I rsynced current last night > > Normally have dhcp via modem but changed to static ip configured with > netconfig. Workstation 192.168.1.2 and gateway 192.168.1.1. Nobody > else on lan so 192.168.1 3 and 4 are not assigned to anyone. As far as > I know I can use rc.local-additions settings as is. I have > edited /etc/exports as per qemu-install.txt. The one thing I am not > clear on is what ip I assign the qemu machine do I give it 192.168.1.1 > for a gateway and use 192.168.1.2 for the server? Should I give gemu > machine a diffeent ip? I haven't bridged anything but a modem and that > was a very long time ago. > > Qemu-install.txt just says > Choose '3 - Install from NFS (Network Filesystem)' > > Enter the IP address: 192.168.1.1 > Enter the > directory: /export/armedslack/armedslack-current/slackware > > My path is different, thats all. I've tried for a couple hours using > diffferent ip settings and can not get an nfs mount. Dropped out of > setup and tried cli line and after making an entry to /etc/fstab but > nfs but i just time out. > > I'm not quite sure what I should search for on the net and what I have > found has not enlightened me. My qemu-1.0.1 install is from a > slackbuild and I have run the debian raspberry pi build successfully > on it. Host system is salix-13.37. > > Perhaps someone can give me a heads up on this I'll sort the above out later.... right now I have armedslack-current installed in qemu using this work around: 1) Set up an armhost directory with utilities, kernel image and initrd as per the INSTALL_QEMU.TXT instructions. 2) Format an sdcard with three partitions, First partition will be root filesystem second swap and third is used for the slackware directory from armedslack-current. With two hard drives onboard the sdcard will be seen as /dev/sdc The largest card I had was 8gb. I gave sdc1 ~5.2gb, sdc3 ~1.76gb and the balance was sdc2 for swap. To get the /slackware directory to fit in sda3 I deleted the contents of package series I would not be installing, that is, e, kde, kdei and t. 3) Format the partitions ext4, swap, ext4, mount sdc3 and copy armedslack-current/slackware into the third partition 4) Create a harddisk.img using the command # dd if=/dev/sdc of=/your-path/armhost/harddisk.img bs=1M Note that my sdcard in a card reader on my box is /dev/sdc. 5) Once image has been created cd into armhost and start the install by running the command ./installer_launch. 6) After logging in as root and before running setup, create a directory to mount the partition containing /slackware and mount it. The installer will see the partition as sda3. # mkdir sda3 # mount /dev/sda3 sda3 Note that you can not use /mnt in the root filesystem. 7) Run setup and when prompted for source media select 6. Install from pre-mounted directory. When prompted for a source directory I enter the path as per step 6 above, i.e. /sda3/slackware. 8) The rest of the install is standard slackware. Follow the prompts. 9) When the installation was finished I shut down, edited the ROOTFSDEV variable in the disk_launch script from sda2 to sda1, saved the script and then ran the script to boot into armedslack-current on qemu. Maybe now I'll figure out what I was doing wrong with the NFS install :^! or maybe I'll see if I cam get my wireless dongle working first since I plan on eventually running this on a raspberrypi :<) Cheers From stanley at stanleygarvey.com Thu Jun 14 18:12:24 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 14 Jun 2012 19:12:24 +0100 Subject: [ARMedslack] nfs and qemu install In-Reply-To: <1339577965.11443.26.camel@rick.miles.home> References: <1339476002.2573.17.camel@rick.miles.home> <1339577965.11443.26.camel@rick.miles.home> Message-ID: <20120614181224.9DC51D051826C@bmail02.one.com> On Jun 13, 2012 09:59 "Rick Miles" wrote: > On Tue, 2012-06-12 at 14:40 +1000, Rick Miles wrote: > > > > Qemu-install.txt just says > > Choose '3 - Install from NFS (Network Filesystem)' > > > I plan on eventually running this on a raspberrypi :<) > > Cheers > > Hi, > the Qemu-install.txt is quite old and you may save yourself some > headaches by using VDE. > see: > alien.slackbook.org/dokuwiki/doku.php?id=slackware:vde > This is how I Installed armed slack on qemu. > compile and install vde > use a script like this to set up networking: (As root) > > #!/bin/bash > modprobe tun > echo "1" > /proc/sys/net/ipv4/ip_forward > iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE > vde_switch -tap tap0 -daemon > chmod -R a+rwx /var/run/vde.ctl > ifconfig tap0 192.168.2.1 broadcast 192.168.2.255 netmask > 255.255.255.0 > > This give me a subnet 192.168.2.?? for virtual machines, My router is > 192.168.0.1 and my host machine is on 192.168.0.3. here is the host > routing table after executing the above script (man route) > > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.2.0 * 255.255.255.0 U 0 0 0 tap0 > localnet * 255.255.255.0 U 0 0 0 eth0 > loopback * 255.0.0.0 U 0 0 0 lo > default 192.168.0.1 0.0.0.0 UG 1 0 0 eth0 > > To install armedslack on qemu I do this: > make a directory for your VM, and in that directory make some subdirs, > HardDrive, CDROM, Images. > create a raw disk image in HardDrive using dd. > copy needed initrd's to images and create an iso of the armedslack > distro with mkisofs (no need to be bootable). > then run an install script like this one: > > #!/bin/bash > # install armed slack > qemu-system-arm -M versatilepb -m 256 -kernel Images/zImage-versatile > -hda HardDrive/harddisk.img -cdrom CDROM/armedslack.iso -initrd > Images/initrd-versatile.img -append "root=/dev/ram rw" > > Now sit back and install, the installer will find the cdrom and > install the packages from it. > to run the installed VM use a script like this one.( adjusting per > your needs :)) > > #!/bin/bash > # Start armed slack > qemu-system-arm -M versatilepb -m 256 -net vde,vlan=0 -net > nic,vlan=0,macaddr=52:54:41:53:13:37 -kernel Images/zImage-versatile > -hda HardDrive/harddisk.img -cdrom CDROM/armedslack.iso -localtime > -usb -no-reboot -initrd Images/initrd-versatile.gz -append > "root=/dev/sda2 rootfs=ext4" > > After configuring the network with netconf ( I like static ips for my > VM's ) the VM's routing table looks like this: > > ___________________________________ > Destination Gateway Genmask Flags Metric Ref Use Iface > localnet * 255.255.255.0 U 0 0 0 eth0 > loopback * 255.0.0.0 U 0 0 0 lo > default 192.168.2.1 0.0.0.0 UG 1 0 0 eth0 > > Good luck getting it to work on a slackberry pi, I have done just > that. you will need to compile a stock Raspberry pi kernel, (good luck > on back porting 2.6.37 to broadcom chip, would be cool though, let me > know if you do.) > get your .config from a running kernel, arch is good. > copy your /root from qemu to your sd card (boot needs to be empty) > linux partion and your uncompresseed kernel to the boot vfat partion > as kernel.img, don't forget to copy the kernel modules to /lib/module, > edit your fstab and cmdline.txt, phew! reboot and voila! > > Minor niggles: ntpd wont set the clock, however ntpdate will, you go > figure? rootfs always loads as rw, perhaps a quirk of the pi boot > loader? > if you need alpha audio modprobe snd-bbcm2835 > X will require building xf86-video-fbdev, and you will need to get an > xorg.conf from a running pi. > > all the best. > Stanley > > > I hope that helps > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rickmiles at turtlespond.net Thu Jun 14 19:24:25 2012 From: rickmiles at turtlespond.net (Rick Miles) Date: Fri, 15 Jun 2012 05:24:25 +1000 Subject: [ARMedslack] nfs and qemu install In-Reply-To: <20120614181224.9DC51D051826C@bmail02.one.com> References: <1339476002.2573.17.camel@rick.miles.home> <1339577965.11443.26.camel@rick.miles.home> <20120614181224.9DC51D051826C@bmail02.one.com> Message-ID: <1339701865.2518.14.camel@rick.miles.home> On Thu, 2012-06-14 at 19:12 +0100, stanley garvey wrote: > On Jun 13, 2012 09:59 "Rick Miles" wrote: > > > On Tue, 2012-06-12 at 14:40 +1000, Rick Miles wrote: > > > > > > > > Qemu-install.txt just says > > > Choose '3 - Install from NFS (Network Filesystem)' > > > > I plan on eventually running this on a raspberrypi :<) > > > > Cheers > > > > Hi, > > the Qemu-install.txt is quite old and you may save yourself some > > headaches by using VDE. > > see: > > alien.slackbook.org/dokuwiki/doku.php?id=slackware:vde > > This is how I Installed armed slack on qemu. > > compile and install vde > > use a script like this to set up networking: (As root) > > Thank you very much for this. I have my weekend project now. This is all new stuff for me. I've been lazy on linux for a long time > > > > Good luck getting it to work on a slackberry pi, I have done just > > that. you will need to compile a stock Raspberry pi kernel, (good > > luck on back porting 2.6.37 to broadcom chip, would be cool though, > > let me know if you do.) > > get your .config from a running kernel, arch is good. > > copy your /root from qemu to your sd card (boot needs to be empty) > > linux partion and your uncompresseed kernel to the boot vfat partion > > as kernel.img, don't forget to copy the kernel modules > > to /lib/module, edit your fstab and cmdline.txt, phew! reboot and > > voila! > > I had armed slack from raspberrypi.org/phpBB3/viewtopic.php?f=56&t=6132&hilit=armedslack running on a pi but fried the pi on a dodgy usb hub trying to use wifi dongle, keyboard and mouse. I have a backordered pi due the last week of June. I hope to get my hands a little dirtier then. > > Minor niggles: ntpd wont set the clock, however ntpdate will, you go > > figure? rootfs always loads as rw, perhaps a quirk of the pi boot > > loader? > > if you need alpha audio modprobe snd-bbcm2835 > > X will require building xf86-video-fbdev, and you will need to get > > an xorg.conf from a running pi. > > Thanks for the heads up, When I don't know what should be working its nice to know what isn't. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- Cheers Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: turtle_signature.png Type: image/png Size: 608 bytes Desc: not available URL: From m-lists at biscuit.org.uk Thu Jun 14 20:59:21 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 14 Jun 2012 21:59:21 +0100 (BST) Subject: [ARMedslack] nfs and qemu install In-Reply-To: <1339701865.2518.14.camel@rick.miles.home> References: <1339476002.2573.17.camel@rick.miles.home> <1339577965.11443.26.camel@rick.miles.home> <20120614181224.9DC51D051826C@bmail02.one.com> <1339701865.2518.14.camel@rick.miles.home> Message-ID: > > > X will require building xf86-video-fbdev, and you will need to get > > > an xorg.conf from a running pi. I'm not sure why people say this -- this package is in Slackware ARM and always has been. From stanley at stanleygarvey.com Fri Jun 15 13:01:43 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 15 Jun 2012 14:01:43 +0100 Subject: [ARMedslack] nfs and qemu install In-Reply-To: References: <1339701865.2518.14.camel@rick.miles.home> Message-ID: <20120615130143.339F41A64459B@bmail02.one.com> On Jun 14, 2012 21:59 "Stuart Winter" wrote: > > > > X will require building xf86-video-fbdev, and you will need to > > > > get > > > > an xorg.conf from a running pi. > > I'm not sure why people say this -- this package is in Slackware ARM > and > always has been. > My mistake. I should have said X needs xf86-video-fbdev and requires > an xorg.conf from a running pi. > Reason,I was looking at source/ x/X11/build/package-blacklist on a x86 > dvd. > > # We don't want this one, as it causes failure of X with no xorg.conf > xf86-video-fbdev > > Off topic. > Nice to see people want armed slack on a Raspberry pi, I don't use > Debian, Arch is better. I don't get apt-get and I don't want my dep's > solved by a pacman. The Rpi is an educational computer. The kids will > be getting one each for Christmas and I want them running slackware. > > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jun 15 14:53:33 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 15 Jun 2012 15:53:33 +0100 (BST) Subject: [ARMedslack] nfs and qemu install In-Reply-To: <20120615130143.339F41A64459B@bmail02.one.com> References: <1339701865.2518.14.camel@rick.miles.home> <20120615130143.339F41A64459B@bmail02.one.com> Message-ID: > My mistake. I should have said X needs xf86-video-fbdev and requires > an xorg.conf from a running pi. > Reason,I was looking at source/ x/X11/build/package-blacklist on a x86 > dvd. Ah good. You're the third person to say this so I was wondering if there was a problem with a mirror service or something. > Nice to see people want armed slack on a Raspberry pi, I don't use > Debian, Arch is better. I don't get apt-get and I don't want my dep's > solved by a pacman. The Rpi is an educational computer. The kids will > be getting one each for Christmas and I want them running slackware. Hopefully there might be in-tree support for it by then. I'm not sure how the lack of using an initrd is going to work in the current setup though. I'm still thinking that I might leave this one to the community, as it's nice to see some discussion around the RPi & Slackware ARM (albeit on linuxquestions.org), and I can only provide support for a small range of devices anyway. -- Stuart Winter Slackware ARM: www.armedslack.org From bratsinot at gmail.com Sun Jun 17 16:18:09 2012 From: bratsinot at gmail.com (=?UTF-8?B?QnJhdFNpbm90IGFrYSDQmtGD0YDRiNCw0LzQsdCw0Lk=?=) Date: Sun, 17 Jun 2012 20:18:09 +0400 Subject: [ARMedslack] tgz Message-ID: Why tgz, not txz? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bratsinot at gmail.com Sun Jun 17 16:17:32 2012 From: bratsinot at gmail.com (=?UTF-8?B?QnJhdFNpbm90IGFrYSDQmtGD0YDRiNCw0LzQsdCw0Lk=?=) Date: Sun, 17 Jun 2012 20:17:32 +0400 Subject: [ARMedslack] little-endian Message-ID: Why are you using little-endian? Will ever be big-endian? -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sun Jun 17 17:39:16 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 17 Jun 2012 18:39:16 +0100 (BST) Subject: [ARMedslack] tgz In-Reply-To: References: Message-ID: On Sun, 17 Jun 2012, BratSinot aka ????????? wrote: > Why tgz, not txz? LZMA uses more memory to decompress, and (IIRC) takes longer to decompress. Neither is desireable slow ARM hardware that often have as little as 128MB RAM. Also the primary driver behind the adoption of LZMA on Slackware x86 was due to the increasing size of Slackware and the number of CDs required per release - which is not an issue for Slackware ARM. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Sun Jun 17 17:40:01 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 17 Jun 2012 18:40:01 +0100 (BST) Subject: [ARMedslack] little-endian In-Reply-To: References: Message-ID: On Sun, 17 Jun 2012, BratSinot aka ????????? wrote: > Why are you using little-endian? Because the consumer hardware is little endian. >Will ever be big-endian? No as it's an entire different distribution and would require another port. -- Stuart Winter Slackware ARM: www.armedslack.org From stanley at stanleygarvey.com Mon Jun 18 22:56:07 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 18 Jun 2012 23:56:07 +0100 Subject: [ARMedslack] nfs and qemu install In-Reply-To: References: <20120615130143.339F41A64459B@bmail02.one.com> Message-ID: <20120618225607.3457ADDA10D91@bmail06.one.com> On Jun 15, 2012 15:53 "Stuart Winter" wrote: > > My mistake. I should have said X needs xf86-video-fbdev and requires > > an xorg.conf from a running pi. > > Reason,I was looking at source/ x/X11/build/package-blacklist on a > > x86 > > dvd. > > Ah good. You're the third person to say this so I was wondering if > there > was a problem with a mirror service or something. > Having had some time to look at the Rpi this weekend , Armed Slack & X > works fine without an xorg.config. > > Hopefully there might be in-tree support for it by then. I'm not sure > how > the lack of using an initrd is going to work in the current setup > though. > > I don't think a conventional installer will ever work due to the way > the Rpi boots, all distros I have seen are pre-installed images. There > is is one for armed Slack but I can't be sure of its provinence, I'll > do it my self thank you! Also It has done a major hatchet job on rc.S > as the root file sytem is always mounted rw. > > I'm still thinking that I might leave this one to the community, > Yes, if I were thinking of re-building the packages, would simply > building then native on the Rpi optimise the code or do you have any > tips regarding gcc flags? > and I can only provide support for a small range of > devices anyway. > Agreed. > Thanks for making it possible to run Slackware on Rpi. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From galen.dp at gmail.com Tue Jun 19 23:24:47 2012 From: galen.dp at gmail.com (Doug Peterson) Date: Tue, 19 Jun 2012 17:24:47 -0600 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi Message-ID: Hello all. My name is Doug Peterson. I am a long time Slackware user. I received my Raspberry Pi this last week and am now working on getting ArmedSlack working on it. I was wondering if there is anyway to install ArmedSlack onto an SD card from my Slackware laptop? I would like to be able to download the ArmedSlack files, install them directly to the SD card and then move the SD card to the Pi for use. I have read the install docs on the website, but I am thinking that, at least for the Pi, a way to directly create the system from a Slackware box would be fun. -Doug From louigi600 at yahoo.it Wed Jun 20 06:45:01 2012 From: louigi600 at yahoo.it (Davide) Date: Wed, 20 Jun 2012 07:45:01 +0100 (BST) Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: References: Message-ID: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> I've no idea whether the installer works directly on that platform, but you can get the miniroot working as long as you have a working kernel for the hardware. Look at the bottomb section in the supported platforms ... there is a paragraph on "unofficially supported platforms". Look at them to get an idea as to how to go about getting slackware on the PI. Look at the mailing list archives as recently I recall someone else wrote they were working on getting slackware on the PI. Regards David ________________________________ Da: Doug Peterson A: ArmedSlack Inviato: Mercoled? 20 Giugno 2012 1:24 Oggetto: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi Hello all. My name is Doug Peterson.? I am a long time Slackware user. I received my Raspberry Pi this last week and am now working on getting ArmedSlack working on it. I was wondering if there is anyway to install ArmedSlack onto an SD card from my Slackware laptop? I would like to be able to download the ArmedSlack files, install them directly to the SD card and then move the SD card to the Pi for use. I have read the install docs on the website, but I am thinking that, at least for the Pi, a way to directly create the system from a Slackware box would be fun. -Doug _______________________________________________ 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 Wed Jun 20 08:07:08 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Jun 2012 09:07:08 +0100 (BST) Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: > I've no idea whether the installer works directly on that platform, but you can get the miniroot working as long as you have a working kernel for the hardware. > Look at the bottomb section in the supported platforms ... there is a paragraph on "unofficially supported platforms". Look at them to get an idea as to how to go about getting slackware on the PI. > Look at the mailing list archives as recently I recall someone else wrote they were working on getting slackware on the PI. http://www.raspberrypi.org/phpBB3/viewtopic.php?f=56&t=6132&start=25 There are some howtos and notes on that thread - although it's unofficial. Jawkins will receive his RPi soon so we (or I) might have a look at doing something official, since he won't use his RPi anyway ;-) But tbh I'm not sure whether I want to support this device officially (in-tree) because the RPi doesn't support initrds which means potentially a big change to how I build the kernels and modules packages; it needs a pre-made image rather than being setup via the installer (as the installer is an initrd, albeit a large one). I have briefly pondered a script to RPI-ify the 'miniroot', and include some instructions. I'm not sure how I'd handle the kernels yet - but if support isn't in the vanilla kernel, I'd most likely keep the RPi out of tree until it's supported without requiring patches. From bratsinot at gmail.com Wed Jun 20 09:23:06 2012 From: bratsinot at gmail.com (BratSinot) Date: Wed, 20 Jun 2012 13:23:06 +0400 Subject: [ARMedslack] Armedslack-current QEMU Message-ID: If you installing with kernel from 13.37 everything works. But, if you use the current kernel, QEMU writes: > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle 0x0 cmd 0x0 value 0xf0f0f0f0) > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle 0x0 cmd 0x0 value 0xf0) -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Wed Jun 20 09:38:37 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Jun 2012 10:38:37 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: > If you installing with kernel from 13.37 everything works. But, if you use > the current kernel, QEMU writes: > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle > 0x0 cmd 0x0 value 0xf0f0f0f0) > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle > 0x0 cmd 0x0 value 0xf0) with which kernel? 3.4.2? I must say that I didn't test QEMU - I only ever test QEMU before a release, as I no longer use it. I will have a look at it at some point. -- Stuart Winter Slackware ARM: www.armedslack.org From anthony.debeus at gmail.com Wed Jun 20 15:27:56 2012 From: anthony.debeus at gmail.com (A de Beus) Date: Wed, 20 Jun 2012 08:27:56 -0700 Subject: [ARMedslack] Slack on Pi Message-ID: <9FF23B0D-A448-4CB9-B44E-F2E35C954FBE@gmail.com> Doug, I suppose you've read the thread in Linuxquestions.org? Just checking: http://www.linuxquestions.org/questions/slackware-14/armedslack-and-raspberry-pi-915172/ My Pi is finally shipping so hopefully I'll have a crack at it too. From tylernt at gmail.com Wed Jun 20 16:36:31 2012 From: tylernt at gmail.com (Tyler T) Date: Wed, 20 Jun 2012 10:36:31 -0600 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: > But tbh I'm not sure whether I want to support this device officially > (in-tree) because the RPi doesn't support initrds which means potentially > a big change to how I build the kernels and modules packages; In my experiments with ARMedSlack on a Seagate DockStar, I remember using a mkboot utility to combine a kernel+initrd into a single blob that u-Boot could boot. I don't remember the exact syntax and I remember a gotcha or two (such as, the kernel had to be uncompressed) but I did eventually get it to work. Perhaps such a combined blob (two actually, one for the kernel+installer and one for the kernel+initrd) could be included in the distro for use on the RPi without any changes to the rest of the ARMedSlack distro? It appears that U-Boot was recently ported to RPi. From robby at rlworkman.net Wed Jun 20 17:36:58 2012 From: robby at rlworkman.net (Robby Workman) Date: Wed, 20 Jun 2012 12:36:58 -0500 Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: <20120620123658.1f95ea0b@liberty.rlwhome.lan> On Wed, 20 Jun 2012 10:38:37 +0100 (BST) Stuart Winter wrote: > > > If you installing with kernel from 13.37 everything works. But, if > > you use the current kernel, QEMU writes: > > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, > > > wcycle > > 0x0 cmd 0x0 value 0xf0f0f0f0) > > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, > > > wcycle > > 0x0 cmd 0x0 value 0xf0) > > with which kernel? 3.4.2? I must say that I didn't test QEMU - I only > ever test QEMU before a release, as I no longer use it. > > I will have a look at it at some point. I'm not getting that at all here, but 3.4.2 definitely won't boot (for other reasons). mount: mounting /dev/sda2 on /mnt failed: No such device or address ERROR: No /sbin/init found... blah blah .. # ls -lh /dev/sd* brw-rw---- 1 root disk 8, 0 Jan 1 1970 /dev/sda brw-rw---- 1 root disk 8, 1 Jan 1 1970 /dev/sda1 brw-rw---- 1 root disk 8, 2 Jun 1 2012 /dev/sda2 # mount -o ro /dev/sda2 /mnt mount: mounting /dev/sda2 on /mnt failed: No such device or address Soo.... no idea really. I notice that devtmpfs is not enabled in the kernel, but I don't think that should matter (since the devices are present by other means); however, it's probably worth enabling just in case. Recent udev requires devtmpfs anyway. -RW From m-lists at biscuit.org.uk Wed Jun 20 19:29:03 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Jun 2012 20:29:03 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: <20120620123658.1f95ea0b@liberty.rlwhome.lan> References: <20120620123658.1f95ea0b@liberty.rlwhome.lan> Message-ID: > Soo.... no idea really. I notice that devtmpfs is not enabled in > the kernel, but I don't think that should matter (since the devices > are present by other means ); Yes udev puts them there. > however, it's probably worth enabling > just in case. Recent udev requires devtmpfs anyway. It should be configured since it is in the x86 kernels, so I've added it to the kernel configs. I've set 3.4.3 building now and I'll probably look at the QEMU problem on Friday. From m-lists at biscuit.org.uk Wed Jun 20 19:53:00 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Jun 2012 20:53:00 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: > If you installing with kernel from 13.37 everything works. But, if you use > the current kernel, QEMU writes: > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle > 0x0 cmd 0x0 value 0xf0f0f0f0) > > pflash_write: Unimplemented flash cmd sequence (offset 00000000, wcycle > 0x0 cmd 0x0 value 0xf0) This is a QEMU message rather than a Linux kernel message. http://lists.gnu.org/archive/html/qemu-devel/2012-03/msg04050.html I suspect Linux 3.4 has made some changes that aren't compatible with the version of QEMU you're running. However, they may also just be debug info rather than the cause of any problem. I'll upgrade my installation of QEMU to the latest release and try on Friday. -- Stuart Winter Slackware ARM: www.armedslack.org From stanley at stanleygarvey.com Thu Jun 21 00:42:49 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 21 Jun 2012 01:42:49 +0100 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <20120621004250.2939D6E5EB587@bmail04.one.com> On Jun 20, 2012 09:07 "Stuart Winter" wrote: I have an 8gb img Get it via: rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . This is the whole armed slack for an 8 GB sd sandisk card sans KDE. Sorry it's not zipped, it is very late. instructions: dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card (most likley sdc) check with mount! don't wipe your hard drive. see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry For a listing os the other files.\good night :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Thu Jun 21 00:47:53 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 21 Jun 2012 01:47:53 +0100 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <20120621004250.2939D6E5EB587@bmail04.one.com> References: <20120621004250.2939D6E5EB587@bmail04.one.com> Message-ID: <20120621004753.693EFB9DDD1F0@bmail02.one.com> On Jun 21, 2012 01:42 "stanley garvey" wrote: > On Jun 20, 2012 09:07 "Stuart Winter" wrote: > I have an 8gb img > Get it via: > rsync -avz --delete rsync.stanleygarvey.co.uk::SlackBerry/Image . > This is the whole armed slack for an 8 GB sd sandisk card sans KDE. > Sorry it's not zipped, it is very late. instructions: > dd bs=1M if=Slacberry_8GB.img of=/dev/your_sd_card > (most likley sdc) check with mount! don't wipe your hard drive. > see rsync -avz rsync.stanleygarvey.co.uk::SlackBerry > For a listing os the other files.\good night :) > root is root password is root > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Jun 21 06:45:28 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 07:45:28 +0100 (BST) Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340261128.12041.YahooMailNeo@web29704.mail.ird.yahoo.com> >> But tbh I'm not sure whether I want to support this device officially >> (in-tree) because the RPi doesn't support initrds which means potentially >> a big change to how I build the kernels and modules packages; >In my experiments with ARMedSlack on a Seagate DockStar, I remember >using a mkboot utility to combine a kernel+initrd into a single blob >that u-Boot could boot. I don't remember the exact syntax and I >remember a gotcha or two (such as, the kernel had to be uncompressed) >but I did eventually get it to work. >Perhaps such a combined blob (two actually, one for the >kernel+installer and one for the kernel+initrd) could be included in >the distro for use on the RPi without any changes to the rest of the >ARMedSlack distro? It appears that U-Boot was recently ported to RPi. On my dockstar I use uImage and uinitrd so there's no need to bundle things in a single blob. -------------- next part -------------- An HTML attachment was scrubbed... URL: From frmrick at aapt.net.au Thu Jun 21 07:05:46 2012 From: frmrick at aapt.net.au (Rick Miles) Date: Thu, 21 Jun 2012 17:05:46 +1000 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340262346.2459.3.camel@rick.miles.home> On Wed, 2012-06-20 at 07:45 +0100, Davide wrote: > I've no idea whether the installer works directly on that platform, > but you can get the miniroot working as long as you have a working > kernel for the hardware. > Look at the bottomb section in the supported platforms ... there is a > paragraph on "unofficially supported platforms". Look at them to get > an idea as to how to go about getting slackware on the PI. > Look at the mailing list archives as recently I recall someone else > wrote they were working on getting slackware on the PI. > > > Regards > David > > It has been done, sort of, here http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=6103 I had this running until my pi died and I was quite impressed. I'm looking forward to my next pi but this time I hope to put it together myself if I can eat enough fish :^) From louigi600 at yahoo.it Thu Jun 21 07:20:56 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 08:20:56 +0100 (BST) Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <1340262346.2459.3.camel@rick.miles.home> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340262346.2459.3.camel@rick.miles.home> Message-ID: <1340263256.65915.YahooMailNeo@web29703.mail.ird.yahoo.com> >> I've no idea whether the installer works directly on that platform, >> but you can get the miniroot working as long as you have a working >> kernel for the hardware. >> Look at the bottomb section in the supported platforms ... there is a >> paragraph on "unofficially supported platforms". Look at them to get >> an idea as to how to go about getting slackware on the PI. >> Look at the mailing list archives as recently I recall someone else >> wrote they were working on getting slackware on the PI. >> Regards >> David >> >It has been done, sort of, here >http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=6103 > >I had this running until my pi died and I was quite impressed. I'm >looking forward to my next pi but this time I hope to put it together >myself if I can eat enough fish :^) What exactly do you eman by "until my pi died" ? Did your RPI hardware fail ? or did you have some data faliure ? I had in mind to buy one at some time ... but if you had a hardware faliure in shuch a short time that's putting me off ! Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From frmrick at aapt.net.au Thu Jun 21 07:43:48 2012 From: frmrick at aapt.net.au (Rick Miles) Date: Thu, 21 Jun 2012 17:43:48 +1000 Subject: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi In-Reply-To: <1340263256.65915.YahooMailNeo@web29703.mail.ird.yahoo.com> References: <1340174701.37382.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340262346.2459.3.camel@rick.miles.home> <1340263256.65915.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: <1340264628.2459.17.camel@rick.miles.home> On Thu, 2012-06-21 at 08:20 +0100, Davide wrote: > > >> I've no idea whether the installer works directly on that platform, > >> but you can get the miniroot working as long as you have a working > >> kernel for the hardware. > >> Look at the bottomb section in the supported platforms ... there is > a > >> paragraph on "unofficially supported platforms". Look at them to > get > >> an idea as to how to go about getting slackware on the PI. > >> Look at the mailing list archives as recently I recall someone else > >> wrote they were working on getting slackware on the PI. > >> Regards > >> David > >> > >It has been done, sort of, here > >http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=6103 > > > >I had this running until my pi died and I was quite impressed. I'm > >looking forward to my next pi but this time I hope to put it together > >myself if I can eat enough fish :^) > > What exactly do you eman by "until my pi died" ? > Did your RPI hardware fail ? or did you have some data faliure ? > > I had in mind to buy one at some time ... but if you had a hardware > faliure in shuch a short time that's putting me off ! The you have to be careful with what you use for a power supply and what you use in the way of a powered usb hub. You should not have power into the pi's two usb ports from a powered usb hub, you should be certain of what your wall wart is supplying, not too little, not too much. There has been enough discussion about this on the pi forum. the elinux website has some very good info and also a list of good hubs, power supplies and periphials. I'm not quite sure what fried my pi, either a dodgy soniq usb hub, an arc between connectors when plugging the hdmi into a monitor while the pi was booting or both. The neither would have been an issue with a normal pc. You just have to treat the pi a little nicer. I'm really looking forward to getting my hands dirty with the next one. From louigi600 at yahoo.it Thu Jun 21 08:14:53 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 09:14:53 +0100 (BST) Subject: [ARMedslack] Tegra kernel Message-ID: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> AC100 uses tegra chipset. I wonder how much work would it take to add the other bits and pieces to the armedslack kegra kernel to make it usable on the AC100. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Jun 21 08:40:14 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Jun 2012 09:40:14 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: On Thu, 21 Jun 2012, Davide wrote: > AC100 uses tegra chipset. I wonder how much work would it take to add > the other bits and pieces to the armedslack kegra kernel to make it > usable on the AC100. root at pepa:~/ac/source/k/configs# grep AC100 config-tegra root at pepa:~/ac/source/k/configs# I checked in menuconfig and couldn't see it there either. If the support for the AC100 is provided by a patch it will need to wait until the support is mainstream, but if it's already in there and is an option I can't see, let me know and I'll see if it can be added in. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Thu Jun 21 09:09:15 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 10:09:15 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> >> AC100 uses tegra chipset. I wonder how much work would it take to add >> the other bits and pieces to the armedslack kegra kernel to make it >> usable on the AC100. > >root at pepa:~/ac/source/k/configs# grep AC100 config-tegra >root at pepa:~/ac/source/k/configs# > >I checked in menuconfig and couldn't see it there either.? If the support >for the AC100 is provided by a patch it will need to wait until the >support is mainstream, but if it's already in there and is an option I >can't see, let me know and I'll see if it can be added in. As far as I know there are several patches that have not yet made it to mainstream kernel, maybe some did make it as there was talk way back in 2.6.38 that some patches were scheduled to go mainstream in 3.1. The odd thing is that 3.1 is marked End Of Life ... I've no idea if anything made ir trough to 3.4. In the guide I wrote for putting armedslack on AC100 I used the ubuntu AC100 tuned kernel to save me all the patch work on vanilla kernel ... last time I looked into patching the mainsteam kernel release i wanted with the required patches for Zaurus I nearly became insane. I'm not sire that I want to to that again. I had a look at the tegra2 SOC specs and it's supposed to gave integrated grafix card: "The second generation Tegra SoC has a dual-core ARM Cortex-A9 CPU (lacking ARMs advanced SIMD extension, marketed as NEON), an ultra low power (ULP) GeForce GPU with 4 pixel shaders + 4 vertex shaders,[13] a 32-bit single-channel memory controller with either LPDDR2 at 600?MHz or DDR2 at 667?MHz, a 32KB/32KB L1 cache per core and a shared 1MB L2 cache.[14] There is also a version of the SoC supporting 3D displays; this SoC uses a higher clocked CPU and GPU." So maybe the only mandatory things neaded for booting are keyboard and internal flash drive (can do temporarely without sound, webcam, and wifi if tey're not working from mainstream). But I'm pretty much sure that since ubuntu is currently using 3.1.10-1.2 patches are for the 3.1 kernel series and they will all need mending to be applied to 3.4 (and possibly stinn not work anyway). Anyone else out there using armedslack tegra based devices ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Jun 21 09:53:21 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 10:53:21 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> Message-ID: <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> >>> AC100 uses tegra chipset. I wonder how much work would it take to add >>> the other bits and pieces to the armedslack kegra kernel to make it >>> usable on the AC100. >>root at pepa:~/ac/source/k/configs# grep AC100 config-tegra >>root at pepa:~/ac/source/k/configs# >>I checked in menuconfig and couldn't see it there either.? If the support >>for the AC100 is provided by a patch it will need to wait until the >>support is mainstream, but if it's already in there and is an option I >>can't see, let me know and I'll see if it can be added in. >As far as I know there are several patches that have not yet made it to mainstream kernel, maybe some did make it as there was talk way back in 2.6.38 that some patches were scheduled to go mainstream in 3.1. >The odd thing is that 3.1 is marked End Of Life ... I've no idea if anything made ir trough to 3.4. >In the guide I wrote for putting armedslack on AC100 I used the ubuntu AC100 tuned kernel to save me all the patch work on vanilla kernel ... last time I looked into patching the mainsteam kernel release i wanted with the >required patches for Zaurus I nearly became insane. I'm not sire that I want to to that again. >I had a look at the tegra2 SOC specs and it's supposed to gave integrated grafix card: >"The second generation Tegra SoC has a dual-core ARM Cortex-A9 CPU (lacking ARMs advanced SIMD extension, marketed as NEON), an ultra low power (ULP) GeForce GPU with 4 pixel shaders + 4 vertex >shaders,[13] a 32-bit single-channel memory controller with either LPDDR2 at 600?MHz or DDR2 at 667?MHz, a 32KB/32KB L1 cache per core and a shared 1MB L2 cache.[14] There is also a version of the SoC >supporting 3D displays; this SoC uses a higher clocked CPU and GPU." >So maybe the only mandatory things neaded for booting are keyboard and internal flash drive (can do temporarely without sound, webcam, and wifi if tey're not working from mainstream). >But I'm pretty much sure that since ubuntu is currently using 3.1.10-1.2 patches are for the 3.1 kernel series and they will all need mending to be applied to 3.4 (and possibly stinn not work anyway). >Anyone else out there using armedslack tegra based devices ? Looking at teh config I think this would need to be enabled fro the AC100/dynabook AZ # CONFIG_MACH_PAZ00 is not set This looks like :http://cateee.net/lkddb/web-lkddb/MACH_PAZ00.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Jun 21 10:04:11 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 21 Jun 2012 11:04:11 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> >Looking at teh config I think this would need to be enabled fro the AC100/dynabook AZ > ># CONFIG_MACH_PAZ00 is not set > >This looks like : http://cateee.net/lkddb/web-lkddb/MACH_PAZ00.html > Might also be necessary to enable some grafix hardware like: CONFIG_FB_NVIDIA And here are some other bits and pieces that might be necessary: CONFIG_MMC_SDHCI_TEGRA -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Jun 21 10:54:21 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Jun 2012 11:54:21 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: > Might also be necessary to enable some grafix hardware like: > CONFIG_FB_NVIDIA This depends on CONFIG_PCI which isn't for Tegras. > And here are some other bits and pieces that might be necessary: > CONFIG_MMC_SDHCI_TEGRA I've added this as a module to the initrd and the installer. Once I push out the 3.4.2 kernels you can have a look at them and see if they're useful. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Thu Jun 21 13:07:24 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Jun 2012 14:07:24 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340281430.26544.YahooMailNeo@web29704.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340281430.26544.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: > But are you using the serial console on your tegra device or an ordinary console ? Yes it uses serial. The graphics support isn't in the mainline kernel yet I don't think. > Will the kernel you've build the screen on the AC100 ? Will the screen work, if that's what you're asking - no idea; depends what support is required in the kernel in order for the screen to work. I wouldn't have thought it'd work since there's nothing in the kernel (that I know of) that'd provide support for the AC100's screen - but I might be wrong since I don't know the details. > I'll update you if I find out any usefull info. I need to check the QEMU thing before I push anything out to the tree, but the kernels have almost finished so I'll bung one up for you to look at once it's done in an hour or so. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Thu Jun 21 19:00:03 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Jun 2012 20:00:03 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: > > And here are some other bits and pieces that might be necessary: > > CONFIG_MMC_SDHCI_TEGRA This one won't build as a module and I can't compile it into the kernel as I build the main MMC support as a module (which I'm not changing). Hopefully the kernel will build with AC100 support though so at least you'll be able to see if the kernel's useful for that device. From louigi600 at yahoo.it Fri Jun 22 06:37:19 2012 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Jun 2012 07:37:19 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340347039.50830.YahooMailNeo@web29705.mail.ird.yahoo.com> Yeah I had a build faliure too >>> And here are some other bits and pieces that might be necessary: >>> CONFIG_MMC_SDHCI_TEGRA >This one won't build as a module and I can't compile it into the kernel as >I build the main MMC support as a module (which I'm not changing). Yeah I had a build faliure too. >Hopefully the kernel will build with AC100 support though so at least >you'll be able to see if the kernel's useful for that device. When I'll have a bit mote rime I'll look better at the options in my current kernel. But sinthe the AC100 serial port is not easily accessible (if it has one at all) I think that if I can't get the video working it's not going to be much use. Well if everything works then I might be able to plug in? the ethernet usb dongle and hope that networking comes up correctly and try access with ssh just to check out that the kernel is working. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jun 22 08:25:40 2012 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Jun 2012 09:25:40 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340347039.50830.YahooMailNeo@web29705.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340347039.50830.YahooMailNeo@web29705.mail.ird.yahoo.com> Message-ID: <1340353540.98550.YahooMailNeo@web29702.mail.ird.yahoo.com> >When I'll have a bit mote rime I'll look better at the options in my current kernel. >But sinthe the AC100 serial port is not easily accessible (if it has one at all) I think that if I can't get the video working it's not going to be much use. >Well if everything works then I might be able to plug in? the ethernet usb dongle and hope that networking comes up correctly and try access with ssh just to check out that the kernel is working. I found instructions on howto get a serial port on the AC100 that would work as a serial console. http://ac100.grandou.net/serial_port_modification Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jun 22 08:29:42 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 22 Jun 2012 09:29:42 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: The problem seems to be because : [ 12.186250] sym53c8xx 0000:00:0d.0: BAR 0: can't reserve [io 0x44000000-0x440000ff] [ 12.348049] smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre [ 12.374710] eth0: SMC91C11xFD (rev 1) at d1024000 IRQ 25 [nowait] The SCSI driver isn't initialising the card properly or something like that, so sd_mod isn't being loaded by udev since there are no disks. Compare the dmesg output from the kernel in 13.37: [ 16.344200] sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 27 [ 16.356532] sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking [ 16.379719] sym0: SCSI BUS has been reset. [ 16.386938] scsi0 : sym-2.2.3 [ 19.414393] sym0: unknown interrupt(s) ignored, ISTAT=0x5 DSTAT=0x80 SIST=0x0 [ 19.425751] scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK 1.1. PQ: 0 ANSI: 5 [ 19.440427] scsi target0:0:0: tagged command queuing enabled, command queue depth 16. [ 19.455265] scsi target0:0:0: Beginning Domain Validation I don't know how to fix that yet. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Fri Jun 22 08:39:12 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 22 Jun 2012 09:39:12 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: > I don't know how to fix that yet. http://www.spinics.net/lists/arm-kernel/msg177442.html I'll try with some of the suggestions here. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Fri Jun 22 13:39:48 2012 From: louigi600 at yahoo.it (Davide) Date: Fri, 22 Jun 2012 14:39:48 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> >> > And here are some other bits and pieces that might be necessary: >> > CONFIG_MMC_SDHCI_TEGRA > >This one won't build as a module and I can't compile it into the kernel as >I build the main MMC support as a module (which I'm not changing). I've been fiddling with 3.4.3 but all the builds I'm doing fail complaining about some rtl8167 firmware file not having a way to build it. I tryed removing all the unecessary rtl drivers from the build but still I get the same error. I'll try using 3.4.2 and see if it's something on the ARM port broken on 3.4.3 of maybe just the mere fact that I copied config from 3.4.2 ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jun 22 13:56:32 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 22 Jun 2012 14:56:32 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: > I've been fiddling with 3.4.3 but all the builds I'm doing fail complaining about some rtl8167 firmware file not having a way to build it. > I tryed removing all the unecessary rtl drivers from the build but still I get the same error. > > I'll try using 3.4.2 and see if it's something on the ARM port broken on 3.4.3 of maybe just the mere fact that I copied config from 3.4.2 ? You're missing the firmware, that's why. This is my 3.4.3 config: http://www.slackware.com/~mozes/dl/config-tegra ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/firmware/rtl_nic.tar.xz You need to unpack it as it does in kernel.Slackbuild: tar xvvf $CWD/sources/firmware/rtl_nic.tar.xz -C firmware/ -- Stuart Winter Slackware ARM: www.armedslack.org From pr0f3ss0r1492 at yahoo.com Sat Jun 23 10:13:00 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Sat, 23 Jun 2012 11:13:00 +0100 Subject: [ARMedslack] Linaro and Slackware/Armedslack Message-ID: Hello people, I apologise for the naive question. I had been wanting to ask this for some time but I wanted to make sure I got it right. What prevents Slackware/Armedslack from cooperating with Linaro? Is it money, technical issues, politics? It seems to me that the only open-source(-ish) alternatives to Windows 8 and Apple Ipad on ARM are Android and Ubuntu. I don't find it very exciting. Or maybe I got it all wrong as usual. Regards -- Ottavio Caruso From m-lists at biscuit.org.uk Sun Jun 24 08:43:02 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 24 Jun 2012 09:43:02 +0100 (BST) Subject: [ARMedslack] Linaro and Slackware/Armedslack In-Reply-To: References: Message-ID: > What prevents Slackware/Armedslack from cooperating with Linaro? Is it > money, technical issues, politics? The linaro web site puts it perfectly: "Linaro is not a Linux distribution. The organization provides great software and tools for distributions to pull from (including OEMs who want to develop an in-house Linux). Linaro's aim is to provide a common software and tools foundation for the industry to use - making it easier and quicker to develop Linux-based products. Linaro's software focus is on areas that interact directly with the silicon such as multimedia, graphics, power management, kernel and boot. Distributions such as Android, Debian, Fedora, OpenSUSE, Tizen and Ubuntu provide the full user experience whereas Linaro enhances the upstream projects directly and provides useful components to any downstream distributions that wish to leverage the work done by Linaro." > It seems to me that the only open-source(-ish) alternatives to Windows > 8 and Apple Ipad on ARM are Android and Ubuntu. I don't find it very > exciting. Thre are ARM ports for most of the distributions - Fedora, Debian, ArchLinux, SuSE etc. The reason the focus on ARM is with Ubuntu and Android is because their respective owners have contracts and agreements with the hardware vendors (e.g. Samsung). From m-lists at biscuit.org.uk Mon Jun 25 08:33:04 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 25 Jun 2012 09:33:04 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: The fbdev driver probably needs rebuilding. I won't be pushing out any updates to -current for probably 2-3 weeks from now, so you'll need to see if you can fix it by recompiling the fbdev driver. On Mon, 25 Jun 2012, Davide wrote: > Unfortunately I was unable to do anything over this weekend. > Have you any idea how to work around the X issue I had after updating to current ? > > > Ciao > David > > > >I'll try that tomorrow probabbly. > > > > >I've another issue right now that makes my AC100 pretty much useless: > >I upgraded to current? with the suggested procedure in the slackpkg man page: > >slackpkg update > >slackpkg install-new > >slackpkg upgrade-all > >#At this point I blacklisted some packages I built > > >slackpkg clean-system > > > > >Now when I start X I get this error > >[??? 45.254] (EE) module ABI major version (8) doesn't match the server's version (12) > >[??? 45.254] (II) UnloadModule: "fbdev" > >[??? 45.254] (II) Unloading fbdev > >[??? 45.254] (EE) Failed to load module > "fbdev" (module requirement mismatch, 0) > >[??? 45.255] (EE) No drivers available. > >[??? 45.255] > >Fatal server error: > > > > > >I can roll back as I saved everything but I did the upgrade to use firefox13 and try to fix all the flash issues ... if I can I would avoid rolling back. > > > > >What can I do to fix this ? > > > > >Regards > >David -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Mon Jun 25 08:43:20 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 25 Jun 2012 09:43:20 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: <1340613800.32916.YahooMailNeo@web29704.mail.ird.yahoo.com> >The fbdev driver probably needs rebuilding. >I won't be pushing out any updates to -current for probably 2-3 weeks from >now, so you'll need to see if you can fix it by recompiling the fbdev >driver. Yea that thing about version 8 and 12 looked like build incompatibility of some sort .... but I was not sure. Can you help me out a bit more on how I'd go about rebuilding fbdev driver ? Last time I compiled X stuff was way back @ xf86 4.4 ... things have changed a lot since then. Will it be enough just to download the fbdev source package and build just that or will I need to download a lot more ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Jun 25 08:52:53 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 25 Jun 2012 09:52:53 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> Message-ID: <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> BTW: can I bug you trough any instant messangers (like skype, facebook, gtalk, icq or anytning that is supported by IMO) ? I promis to limit myself to only be slightly more annoying thet via email :-D Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jun 25 09:12:49 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 25 Jun 2012 10:12:49 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: Try this: http://armed.slackware.com/test/xf86-video-fbdev-0.4.2-arm-4.tgz > BTW: can I bug you trough any instant messangers (like skype, facebook, > gtalk, icq or anytning that is supported by IMO) ? I'm on #armedslack on freenode - responsiveness varies according to busyness of other things. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Mon Jun 25 12:28:45 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 25 Jun 2012 13:28:45 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> Message-ID: <1340627325.64010.YahooMailNeo@web29705.mail.ird.yahoo.com> >Try this: >http://armed.slackware.com/test/xf86-video-fbdev-0.4.2-arm-4.tgz Thanks X now starts but I have no mouse/keyboard response. Looking at the Xorg log it looks like there are more version mismatches on the input (evidev). I did remove and re-install the server? and input drivers too: Now I get that server is version 16 while the input drivers are version 11. This is the driver that's making the errors show on the log: evdev_drv.so for all input devices. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jun 25 14:10:04 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 25 Jun 2012 15:10:04 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: <1340627325.64010.YahooMailNeo@web29705.mail.ird.yahoo.com> References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340627325.64010.YahooMailNeo@web29705.mail.ird.yahoo.com> Message-ID: > This is the driver that's making the errors show on the log: > evdev_drv.so Try this: http://armed.slackware.com/test/xf86-input-evdev-2.7.0-arm-1.tgz This had failed a build and hadn't been updated since 2011. hopefully this one will work! From louigi600 at yahoo.it Mon Jun 25 14:27:25 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 25 Jun 2012 15:27:25 +0100 (BST) Subject: [ARMedslack] Tegra kernel In-Reply-To: References: <1340266493.13853.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340269755.7087.YahooMailNeo@web29701.mail.ird.yahoo.com> <1340272401.45302.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340273051.57122.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340372388.67902.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340378487.93228.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340608272.24717.YahooMailNeo@web29703.mail.ird.yahoo.com> <1340614373.35821.YahooMailNeo@web29704.mail.ird.yahoo.com> <1340627325.64010.YahooMailNeo@web29705.mail.ird.yahoo.com> Message-ID: <1340634445.27647.YahooMailNeo@web29705.mail.ird.yahoo.com> >> This is the driver that's making the errors show on the log: >> evdev_drv.so >Try this: >http://armed.slackware.com/test/xf86-input-evdev-2.7.0-arm-1.tgz Thanks man ... now my X is starting again. Now I can play with firefox13. >This had failed a build and hadn't been updated since 2011.? hopefully >this one will work! -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Wed Jun 27 07:46:01 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 27 Jun 2012 08:46:01 +0100 (BST) Subject: [ARMedslack] Armedslack-current QEMU In-Reply-To: References: Message-ID: > http://www.spinics.net/lists/arm-kernel/msg177442.html > > I'll try with some of the suggestions here. Thanks to Jim Hawkins for patching the Versatile kernel. The -current tree isn't in a state in which it can be publically consumed, so I've put the new packages and kernels here: http://armed.slackware.com/fixes/versatile/ The layout is the same as the -current tree, so you can download the files from the URL above, remove the copies in your -current tree and drop the new versions in place. The patch is also in the 'k' directory - in case anybody comes across this thread and wants to get Versatile working again in QEMU. Also whilst doing a test installation on QEMU I wondered why I'd not enabled DHCP by default in the supplied 'installer_launch' script. QEMU has a built-in DHCP server and since the script sets up QEMU using NAT, it makes sense to use DHCP. I've adjusted the script: -append "nic=auto:eth0:dhcp root=/dev/ram rw" The new version of the script will be uploaded at some point. The only thing about using DHCP from inside QEMU is that when mouting your x86 NFS server, you need to refer to it by IP Address rather than any canonical name. e.g. 192.168.1.1 Cheers s. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Wed Jun 27 14:34:35 2012 From: louigi600 at yahoo.it (Davide) Date: Wed, 27 Jun 2012 15:34:35 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: Message-ID: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Has anyone got a working version of libflashplayer.so for armedslack ? I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so but I was unable to get it to work. I also tryed this: http://ac100.wikispaces.com/file/view/libflashplayer.so/284969210/libflashplayer.so but it's still a no go . Are thse binaty incompatible or is it just a matter of fixing some library dependencies ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Wed Jun 27 18:10:53 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 27 Jun 2012 19:10:53 +0100 Subject: [ARMedslack] libflashplayer In-Reply-To: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: On 27 June 2012 15:34, Davide wrote: > Has anyone got a working version of libflashplayer.so for armedslack ? There's no official flash player for Linux on ARM. You can try to google around but you would probably find either pirated of obsolete versions. -- Ottavio Caruso From thenktor at gmail.com Wed Jun 27 18:56:44 2012 From: thenktor at gmail.com (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Wed, 27 Jun 2012 20:56:44 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: <20120627205644.13f1070d@pinkfloyd.tm-net> Am Wed, 27 Jun 2012 19:10:53 +0100 schrieb Ottavio Caruso : > On 27 June 2012 15:34, Davide wrote: > > Has anyone got a working version of libflashplayer.so for > > armedslack ? > > There's no official flash player for Linux on ARM. You can try to > google around but you would probably find either pirated of obsolete > versions. Various Android Browser are shipping a Flash plugin. AFAIK the latest Firefox for Android (version 14.x) has one, too. Maybe you can find something in their source/app/ML/chat... :-/ -- Thorsten M?hlfelder Salix OS: www.salixos.org From pr0f3ss0r1492 at yahoo.com Wed Jun 27 19:10:00 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 27 Jun 2012 19:10:00 +0000 Subject: [ARMedslack] libflashplayer In-Reply-To: <20120627205644.13f1070d@pinkfloyd.tm-net> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <20120627205644.13f1070d@pinkfloyd.tm-net> Message-ID: On 27 June 2012 18:56, Thorsten M?hlfelder wrote: > Various Android Browser are shipping a Flash plugin. AFAIK the latest > Firefox for Android (version 14.x) has one, too. Maybe you can find > something in their source/app/ML/chat... :-/ I strongly doubt that at the moment you can take random pieces from the Android userspace and just transplant it into any Linux distro, but I'd be pleased to be proven wrong. -- Ottavio Caruso From thenktor at gmail.com Wed Jun 27 19:32:28 2012 From: thenktor at gmail.com (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Wed, 27 Jun 2012 21:32:28 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <20120627205644.13f1070d@pinkfloyd.tm-net> Message-ID: <20120627213228.6f5a3202@pinkfloyd.tm-net> Am Wed, 27 Jun 2012 19:10:00 +0000 schrieb Ottavio Caruso : > On 27 June 2012 18:56, Thorsten M?hlfelder wrote: > > Various Android Browser are shipping a Flash plugin. AFAIK the > > latest Firefox for Android (version 14.x) has one, too. Maybe you > > can find something in their source/app/ML/chat... :-/ > > > I strongly doubt that at the moment you can take random pieces from > the Android userspace and just transplant it into any Linux distro, > but I'd be pleased to be proven wrong. > Well, that's right. Precompiled probably won't work. No idea what C library Android uses. -- Thorsten M?hlfelder Salix OS: www.salixos.org From pr0f3ss0r1492 at yahoo.com Wed Jun 27 20:20:54 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 27 Jun 2012 21:20:54 +0100 Subject: [ARMedslack] Gecko-mediaplayer, was Re: libflashplayer Message-ID: On 27 June 2012 20:32, Thorsten M?hlfelder wrote: > > Well, that's right. Precompiled probably won't work. No idea what C > library Android uses. However I am curious to know if FlashVideoReplacer and gecko-mediaplayer work on your systems, If so, at least one could watch Youtube and similar sites without flash altogether. This would save me the time to update my qemu install and test it on there. -- Ottavio From m-lists at biscuit.org.uk Wed Jun 27 20:58:15 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 27 Jun 2012 21:58:15 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: > I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so > but I was unable to get it to work. Did you see why it broke? LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open shared object file: No such file or directory] root at pepa:~# ldd /usr/lib/mozilla/plugins/libflashplayer.so | fgrep not libGLESv2.so => not found Finding/compiling that module doesn't guarantee whatsoever that the player would work, but you never know! From axjslack at gmail.com Thu Jun 28 03:56:53 2012 From: axjslack at gmail.com (Alexjan Carraturo) Date: Thu, 28 Jun 2012 05:56:53 +0200 Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: 2012/6/27 Stuart Winter : >> I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so >> but I was unable to get it to work. > > Did you see why it broke? > > LoadPlugin: failed to initialize shared library > /usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open > shared object file: No such file or directory] > > > root at pepa:~# ldd /usr/lib/mozilla/plugins/libflashplayer.so | fgrep not > ? ? ? ?libGLESv2.so => not found > > > Finding/compiling that module doesn't guarantee whatsoever that the player > would work, but you never know! Seems that the flashplayer version that you are trying to use is compiled in order to work with an accelerated graphic hardware. In a lot of recent arm SoC is present 3D hardware (for example Mali from ARM), and, with the driver that commonly it's GPL released are given libraries modified for that hardware (as libGLESv2) that usually are closed. The libglesv2, derives from Mesa, and there (without hardware acceleration), available second in terms of MIT license (http://www.mesa3d.org/). Often, however, things compiled for hardware accelerated version does not work well with the "software only". In slackware 13.37 is present a compiled version of mesa, but, AFAIK it's compiled with this option ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --mandir=/usr/man \ --docdir=/usr/doc/mesa-$VERSION \ --enable-xcb \ --disable-gallium \ --build=$ARCH-slackware-linux-gnueabi In order to have libgles you have to compile with this option --enable-gles1 --enable-gles2 This just in theory. I've never actually tried. I tried the precompiled version of debian, but with poor performance. bye Alexjan -- Alexjan Carraturo -- Twitter/Facebook/Identica/flickr: axjslack Personal site: http://axjslack.wordpress.com -- From louigi600 at yahoo.it Thu Jun 28 08:01:41 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 28 Jun 2012 09:01:41 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> >> I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so >> but I was unable to get it to work. >Did you see why it broke? >LoadPlugin: failed to initialize shared library >/usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open >shared object file: No such file or directory] >root at pepa:~# ldd /usr/lib/mozilla/plugins/libflashplayer.so | fgrep not >? ? ? ? libGLESv2.so => not found >Finding/compiling that module doesn't guarantee whatsoever that the player >would work, but you never know! I noticed that ldd was missing some stuff and tryed to fulfill the missing deps: could not find the libGLES on slackware so I first attempted to use fedora18 ARM port that forced me to install other dependencies too. After all the dependency fulfillment ldd told me it could find all the libs neaded ... but it was still a no go .... maybe some further dependencies that I missed or binary incompatibility ..... I did a little fiddling to try to figure out where the "LoadPlugin: failed to initialize shared library" message was coming from as I was unable to reproduce it in ani log, trought strace nor in the jsconsole. After some attempts I notced that the message comes out if you start firefox from a terminal and yoy subsequently open the add-ons tool. I'll try to build libGLESv2.so from sources minimizing the need for further dependencies and see if I get anywhere. Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jun 29 07:39:33 2012 From: louigi600 at yahoo.it (Davide) Date: Fri, 29 Jun 2012 08:39:33 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> >>LoadPlugin: failed to initialize shared library >>/usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open >>shared object file: No such file or directory] >>root at pepa:~# ldd /usr/lib/mozilla/plugins/libflashplayer.so | fgrep not >>? ? ? ? libGLESv2.so => not found >>Finding/compiling that module doesn't guarantee whatsoever that the player >>would work, but you never know! >I noticed that ldd was missing some stuff and tryed to fulfill the missing deps: could not find the libGLES on slackware so I first attempted to use fedora18 ARM port that forced me to install other dependencies too. >After all the dependency fulfillment ldd told me it could find all the libs neaded ... but it was still a no go .... maybe some further dependencies that I missed or binary incompatibility ..... >I did a little fiddling to try to figure out where the "LoadPlugin: failed to initialize shared library" message was coming from as I was unable to reproduce it in ani log, trought strace nor in the jsconsole. >After some attempts I notced that the message comes out if you start firefox from a terminal and yoy subsequently open the add-ons tool. >I'll try to build libGLESv2.so from sources minimizing the need for further dependencies and see if I get anywhere. It appears that libGLES* get built from the X mesa sources (at least fedora does it from a mesa 8.1 snapshot {20120603}and some patches aplied). I'm not familiar at all with the way redhat/fedora build their packages from sources so i was unable to figure out how to buil libGLES. Looking back at waht I have on my sistem I notice that I have the mesa-8.0.3 package installed but it does not contain libGLES*. I wonder if that is because libGLES crept in some version abter 8.0.3 and before 8.1 or because it's spefifically not built in the slackware package ? Looking at teh armedslack mesa source package I see it has GLES includes Mesa-8.0.3/include/GLES2/ Mesa-8.0.3/include/GLES2/gl2platform.h Mesa-8.0.3/include/GLES2/gl2.h Mesa-8.0.3/include/GLES2/gl2ext.h Mesa-8.0.3/include/GLES/ Mesa-8.0.3/include/GLES/glplatform.h Mesa-8.0.3/include/GLES/gl.h Mesa-8.0.3/include/GLES/glext.h Mesa-8.0.3/include/GLES/egl.h anyone know hot to build libGLES* from the armedslack source package ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jun 29 13:22:39 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 29 Jun 2012 14:22:39 +0100 (BST) Subject: [ARMedslack] libflashplayer In-Reply-To: <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> References: <1340807675.5052.YahooMailNeo@web29702.mail.ird.yahoo.com> <1340870501.32820.YahooMailNeo@web29706.mail.ird.yahoo.com> <1340955573.86863.YahooMailNeo@web29706.mail.ird.yahoo.com> Message-ID: > anyone know hot to build libGLES* from the armedslack source package ? I've dropped this into /usr/lib/mozilla/plugins: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so And firefox about:plugins now says: === Shockwave Flash File: libflashplayer.so Version: Shockwave Flash 10.1 r120 MIME Type Description Suffixes application/x-shockwave-flash Shockwave Flash swf application/futuresplash FutureSplash Player spl === I can watch a video on youtube x11vnc but I don't have a working native X at the moment as x/xf86-video-xgi-1.6.0-arm-3.tgz doesn't work with the new version of X and won't build yet. Give it a go. This package is built on the new -current so I don't know if it'll work on the one that's public at the moment (although I would imagine it will) http://armed.slackware.com/test/mesa-8.0.3-arm-2.tgz The src is here: http://armed.slackware.com/test/src/ All I've changed is: Added ./configure options: --with-gallium-drivers=" nouveau r600 r300 svga" --enable-gles1 --enable-gles2 --enable-openvg --enable-gallium-egl and removed --disable-egl From thierry.merle at free.fr Fri Jun 29 21:00:05 2012 From: thierry.merle at free.fr (Thierry Merle) Date: Fri, 29 Jun 2012 23:00:05 +0200 Subject: [ARMedslack] armedslack on android Message-ID: <4FEE1755.9010709@free.fr> Hi all, I managed to put armedslack on my Android ICS device, using a miniroot image. My aim is to put Armedslack on Android media center (Melee A2000, I don't have it yet), that will be an Armedslack NAS/email server at the same time. The method is quite simple: 1/ create a disk image containing miniroot, on the sdcard (or whatever, I feel safe on a sdcard) 2/ mount that disk image as a loop device in /local/data/armedslack for example 3/ chroot /local/data/armedslack You need root access, and loop device support on your Android device due to the loop mount/chroot commands. 1/ Disk image creation: Inspired from this [1] link Download slack-13.37-miniroot_01May11.tar.xz dd if=/dev/zero of=/path/to/c.img bs=516096c count=1000 #creates a 500MB image fdisk -u -C1000 -S63 -H16 /path/to/c.img perform commands o, n, a, p,w to add a linux primary partitioan and write (follow the [1] link for explanations) losetup -o32256 /dev/loop0 /path/to/c.img mke2fs -b1024 /dev/loop0 mount -text2 /dev/loop0 /mnt/wherever cd /mnt/wherever tar -Jxvf /where/is/slack-13.37-miniroot_01May11.tar.xz cd #get out of the mountpoint umount /dev/loop0 losetup -d /dev/loop0 dd if=/path/to/c.img of=root.img bs=32256 skip=1 #extract the ext2 partition since busybox mount does not support the offset option adb push root.img /mnt/external_sd/ #or whatever, the aim is to have root.img on your sdcard2/ mount this image as a loop device on the Android device 2/ Now on the Android device: open a shell (download Android terminal emulator, or use adb shell) cd /mnt/external_sd mkdir armedslack su mount -o loop root.img armedslack/ 3/ you need to mount some special filesystems before chroot (inspired from this [2] link): mount -t devpts devpts armedslack/dev/pts mount -t proc proc armedslack/proc mount -t sysfs sysfs armedslack/sys chroot armedslack /bin/bash . /etc/profile #in order to load environment with correct bin path /etc/rc.d/rc.S #will initialize the armedslack system as init would do. An error on filesystem check occurs (of cours rootfs is mounted rw), not fatal. /etc/rc.d/rc.M #perform multi-user initializations, ssh server for example Note: that all occurs with /system in ro mode, so should be harmless for the Android system, after a reboot. I don't have a clean method to quit the chroot armedslack (finding out processes launched in armedslack is not easy) but rebooting restores the initial state. The only side effect is system time: I get a shift that changes the Android time; I guess this is in the /etc/rc.d/rc.S script. Running ntpdate solves the issue. You can run a vnc server (like tightvnc) and use the android-vnc app to get an Armedslack graphic interface on your Android device, ... but I guess this setup is the same as for headless targets. Unfortunately the Android linux kernel does not include nfsd (my aim), but there are solutions for nfs in userspace, need to try... Regards, Thierry [1] http://wiki.osdev.org/Loopback_Device#Creating_an_image [2] http://technoreview.net/2011/10/installing-ubuntu-on-android-with-chroot.html