Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. ATB David Il Domenica 17 Novembre 2013 3:04, openpand...@free.fr openpand...@free.fr ha scritto: Thanks ! I appreciate. - Mail original - De: Stuart Winter m-li...@biscuit.org.uk À: Slackware ARM port armedslack@lists.armedslack.org Envoyé: Dimanche 17 Novembre 2013 00:00:26 Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 'These are _not_ just warnings; ldconfig ignores the library content, so output/target/etc/ld.so.cache is left unpopulated, meaning that the target device will not boot successfully due to missing libraries (the libraries are on the file-system, just the ld.so.cache does not list them).' He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] USB host on the Allwinner SOC's
I compiled the new kernel last night but the usb host is behaving just like in the older kernel :( At this point I suspect that it's never going to get fixed on the freely available kernel ... it's a sad but common thing in the linux ARM world. Regards David Il Mercoledì 30 Ottobre 2013 11:51, Davide louigi...@yahoo.it ha scritto: Today I noticed that the linux-sunxi kernel has been updated in the usb host section. Hopefully this will get all those dongles that work on the stock android kernel functional on the linux-sunxi kernel too (currently only some keyboard, mice and mass storage seem to work right). I'll compile it and test it asap. If it works I'll update the image builder with a new kernel with propper usb host capabilities. ATBDavid ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Setting up Slackware ARM 14.0 on the OLinuXino A10S from scratch
Today I noticed that the linux-sunxi kernel has been updated in the usb host section. Hopefully this will get all those dongles that work on the stock android kernel functional on the linux-sunxi kernel too. I'll compile it and test it asap. If it works I'll update the image builder with a new kernel with propper usb host capabilities. ATB David Il Lunedì 21 Ottobre 2013 15:54, Davide louigi...@yahoo.it ha scritto: The A10s should be amongs the supported devices that my image builder targets, did you haveto do it a different way because it failed ? Regards David Da: Michael Balcos michael.bal...@gmail.com A: armedslack@lists.armedslack.org Inviato: Lunedì 21 Ottobre 2013 3:54 Oggetto: [ARMedslack] Setting up Slackware ARM 14.0 on the OLinuXino A10S from scratch I got Slackware ARM 14.0 to work on the OLinuXino A10S. If you're interested, here is the documentation: http://www.malaya-digital.org/setting-up-slackware-arm-14-0-on-the-olinuxino-a10s-from-scratch/ :) -- Michael Balcos http://blog.malaya-digital.org/ http://www.balcos.net/ ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] USB host on the Allwinner SOC's
Today I noticed that the linux-sunxi kernel has been updated in the usb host section. Hopefully this will get all those dongles that work on the stock android kernel functional on the linux-sunxi kernel too (currently only some keyboard, mice and mass storage seem to work right). I'll compile it and test it asap. If it works I'll update the image builder with a new kernel with propper usb host capabilities. ATBDavid___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Setting up Slackware ARM 14.0 on the OLinuXino A10S from scratch
This is where I started out on the Axx soc http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I started taking note of things as I got the thing ... and it takes you trought to creating manually a custom image on the uSD. At some point (in the wrapping up section) I've a link to the image builder that does all the figity steps in a nice neat script still leaving you tons of flexibility. ftp://ftp.slackware.org.uk/slackwarearm/people/louigi600/ Be warned that I've not yet fixed the image builder to make ext4 root there are pros and cons in doing this on a flash device ... after all I'm beginning to appreciate more the pros and accept the cons. You might want to change the formatting in the script to best suit what you prefer. Regards David Da: Michael Balcos michael.bal...@gmail.com A: Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Martedì 22 Ottobre 2013 2:21 Oggetto: Re: [ARMedslack] Setting up Slackware ARM 14.0 on the OLinuXino A10S from scratch Hi Davide, I havenapos;t tried your image builder yet. Could you point me to your documentation? :) Iapos;ll give it a shot. On Mon, Oct 21, 2013 at 9:54 PM, Davide louigi...@yahoo.it wrote: The A10s should be amongs the supported devices that my image builder targets, did you haveto do it a different way because it failed ? Regards David Da: Michael Balcos michael.bal...@gmail.com A: armedslack@lists.armedslack.org Inviato: Lunedì 21 Ottobre 2013 3:54 Oggetto: [ARMedslack] Setting up Slackware ARM 14.0 on the OLinuXino A10S from scratch I got Slackware ARM 14.0 to work on the OLinuXino A10S. If youapos;re interested, here is the documentation: http://www.malaya-digital.org/setting-up-slackware-arm-14-0-on-the-olinuxino-a10s-from-scratch/ :) -- Michael Balcos http://blog.malaya-digital.org/ http://www.balcos.net/ ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Michael Balcos http://blog.malaya-digital.org/ http://www.balcos.net/ ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
Ok I grabbed the boot stuff from rasbian (2013-09-10) and used the slackware arm miniroot in a freshlu formatted and partitioned SD it boots (minor issue complaining about root being already mounted rw ... probabbly need to add ro to cmdline or edit the fstab). ATB David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
Where can I get more details on how the PI boots ? Does the GPU get properly initialized right away ? can I see the kenel booting on the HDMI output ? or do I need a serial console for that ? So all the other files are not necessary for booting ? COPYING.linux and LICENCE.broadcom are probabbly there for the boot code ... I'm sure I can omit them safely. But what about fixup.dat , fixup_cd.dat and start_cd.elf ? I don't really want to do the install thing as I generally prefer to start from a miniroot and add what I need rather then answring a lot of questions, tinkering with tagfiles or installing everything. On a PC with 1Tb of mass storage installing everything just to going fast is ok ... but on slower hardware with slower flash storage I really prefer the miniroot way. Regards David Da: stan...@stanleygarvey.com stan...@stanleygarvey.com A: stan...@stanleygarvey.com; Slackware ARM port armedslack@lists.armedslack.org Inviato: Mercoledì 25 Settembre 2013 20:58 Oggetto: Re: [ARMedslack] A quick primer for the PI The pi requires a fat filesystem to boot from. That partition is normally mountesd on /boot and should contain a kernel - default kernel.img, start.elf, bootcode.bin, cmdline.txt and optionally a config.txt which is used to overide defaut settings. --Original Message-- From: stan...@stanleygarvey.com Sender: ARMedslack To: Davide To: Slackware ARM port ReplyTo: stan...@stanleygarvey.com ReplyTo: Slackware ARM port Subject: Re: [ARMedslack] A quick primer for the PI Sent: 25 Sep 2013 16:59 Try the installer image. The gpu boots the system. At work now so can' explain further at he moment. Regards Stanley Sent from my BlackBerry smartphone from Virgin Media -Original Message- From: Davide louigi...@yahoo.it Sender: ARMedslack armedslack-boun...@lists.armedslack.orgDate: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM portarmedslack@lists.armedslack.org Reply-To: Davide louigi...@yahoo.it, Slackware ARM port armedslack@lists.armedslack.org Subject: [ARMedslack] A quick primer for the PI ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack Sent from my BlackBerry smartphone from Virgin Media ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
Hum ... I tried with both HDM plugged and unplugged ... made no difference. After having failed I fiddled with the config.txt ... this is what it look like stripped from comments: root@darkstar:/mnt/floppy# grep -vE ^ *$|^# config.txt hdmi_safe=1 hdmi_force_hotplug=1 hdmi_drive=2 hdmi_mode=4 disable_overscan=1 kernel=zImage-raspberrypi-3.10.3 root@darkstar:/mnt/floppy# and this is the last content of the boot partition: root@darkstar:/mnt/floppy# ls -l total 49665 -rwxr-xr-x 1 root root 18693 Sep 26 10:18 COPYING.linux* -rwxr-xr-x 1 root root 1447 Sep 26 10:18 LICENCE.broadcom* -rwxr-xr-x 1 root root 1536531 Aug 1 03:23 System.map-raspberrypi-3.10.3* -rwxr-xr-x 1 root root 1258940 Sep 26 10:18 System.map-raspberrypi-3.2.27* -rwxr-xr-x 1 root root 16536 Jul 7 2012 bootcode.bin* -rwxr-xr-x 1 root root 208 Sep 26 11:14 cmdline.txt* -rwxr-xr-x 1 root root 68928 Sep 26 11:05 config-raspberrypi-3.10.3* -rwxr-xr-x 1 root root 75124 Sep 26 10:18 config-raspberrypi-3.2.27* -rwxr-xr-x 1 root root 29619 Sep 26 11:49 config.txt* -rwxr-xr-x 1 root root 39558430 Sep 26 10:18 initrd-raspberrypi.img* -rwxr-xr-x 1 root root 275235 Jun 17 2012 loader.bin* -rwxr-xr-x 1 root root 2053296 Aug 1 2012 start.elf* -rwxr-xr-x 1 root root 3233208 Aug 1 03:23 zImage-raspberrypi-3.10.3* -rwxr-xr-x 1 root root 2727800 Sep 26 10:18 zImage-raspberrypi-3.2.27* root@darkstar:/mnt/floppy# I'm puzzled ! David Da: dowe...@netscape.net dowe...@netscape.net A: louigi...@yahoo.it; stan...@stanleygarvey.com; armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 14:58 Oggetto: Re: [ARMedslack] A quick primer for the PI I recognise that behaviour, I encountered the same kind of behaviour. In my case it was because the bootloader code/GPU was trying to initialise the HDMI interface, and I run the pi headless. I fixed that by adding the line: hdmi_safe=1 to config.txt I'm using a later level of GPU firmware than you are, but I think that line was supported on the version you're using. The files I use to boot to the installer are available here http://www.dowelld.net/?p=49 the txt file explains how I use them. Thanks Dave -Original Message- From: Davide louigi...@yahoo.it To: stanley garvey stan...@stanleygarvey.com; dowelld dowe...@netscape.net; armedslack armedslack@lists.armedslack.org Sent: Thu, Sep 26, 2013 1:38 pm Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David Da: stanley garvey stan...@stanleygarvey.com A: dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org; Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 Davide louigi...@yahoo.it wrote: I got a friend to lend me a PI for a week ... I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) I'm supposing that the first partition (the dos one) is where this stuff should be put ? The content in there looks about right: root@darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2 97664
Re: [ARMedslack] A quick primer for the PI
No I formatted the filesystem myself and copied files into it. The firs lot of boot loader stuff was gotten out of http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip , unzipp created loop device with off set on the image first partition ... mounted it and copied files over. root@darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux swap slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux root@darkstar:/tmp# echo $((32 * 512)) 16384 root@darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root@darkstar:/tmp# modprobe vfat root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root@darkstar:/tmp# ls /mnt/floppy/ COPYING.linux* config-raspberrypi-3.2.27* start.elf* LICENCE.broadcom* config.txt* start_cd.elf* System.map-raspberrypi-3.2.27* fixup.dat* zImage-raspberrypi-3.2.27* bootcode.bin* fixup_cd.dat* cmdline.txt* initrd-raspberrypi.img* root@darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David Da: stan...@stanleygarvey.com stan...@stanleygarvey.com A: Davide louigi...@yahoo.it; dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 14:52 Oggetto: Re: [ARMedslack] A quick primer for the PI Did you dd the image onto the card? What suze of card? Try the installer image at stanleygarvey.com Regards, Stanley Sent from my BlackBerry smartphone from Virgin Media From: Davide louigi...@yahoo.it Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garveystan...@stanleygarvey.com; dowe...@netscape.netdowe...@netscape.net; armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ReplyTo: Davide louigi...@yahoo.it Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David Da: stanley garvey stan...@stanleygarvey.com A: dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org; Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 Davide louigi...@yahoo.it wrote: I got a friend to lend me a PI for a week ... I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) I'm supposing that the first partition (the dos one) is where this stuff should be put ? The content in there looks about right: root@darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c
[ARMedslack] A quick primer for the PI
I got a friend to lend me a PI for a week ... I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) I'm supposing that the first partition (the dos one) is where this stuff should be put ? The content in there looks about right: root@darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux swap slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux root@darkstar:/tmp# echo $((32 * 512)) 16384 root@darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root@darkstar:/tmp# modprobe vfat root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root@darkstar:/tmp# ls /mnt/floppy/ COPYING.linux* config-raspberrypi-3.2.27* start.elf* LICENCE.broadcom* config.txt* start_cd.elf* System.map-raspberrypi-3.2.27* fixup.dat* zImage-raspberrypi-3.2.27* bootcode.bin* fixup_cd.dat* cmdline.txt* initrd-raspberrypi.img* root@darkstar:/tmp# I plan to play a little with a miniroot so I won't need an 8Gb SD :) ATB David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Kernel for Allwinner A1X
It appears that the usb driver in the linux-sunxi kernel is bust (at least on A1X based devices) and I don't think that there is any chance of them fixing it any time soon. I even downloaded the 3.0 stable version sources hoping that at least their stable version (as opposed to the 3.4 developement kernel) still had working usb correctly, but it had the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb devices work properly while some that work correctly on the stock android kernel just don't work with their kernel). Anyone tried using vanilla kernels on Allwinner SOC based systems ? Anyone know what's going to work and what's not going to work if I try compiling a kernel from kernel.org ? touch screen is not important because that's not working well enough to be functional anyway. I don't have any Allwiner machines, but I did add some Allwinner SoC configs into the Linux 3.10 kernels. If there are any patches, I could apply them to Linux 3.10. I think we'll be using Linux 3.10 for the Slackware 14.1 release. I did try Linux 3.11 but it was quite broken. I'm gonna try building 3.10.12 without any patches at all just to see what's going to work and what's not. ATB David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Skype on ARM linux
I'll begin my stating that I do not consider Android as having much to do with ARM linux. This this in mind what are the alternatives, if any, for having skype on ARM linux ? Is there some other instant messaging client (chat and video capable) that is knows to work well on ARM linux ? I read somewhere that pidgin supports video chat as of version 2.6: anyone tried video chatting with it ? will it work on Slackware ARM without chasing dependencies till you're driven nuts ? ATB David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Kernel for Allwinner A1X
It appears that the usb driver in the linux-sunxi kernel is bust (at least on A1X based devices) and I don't think that there is any chance of them fixing it any time soon. I even downloaded the 3.0 stable version sources hoping that at least their stable version (as opposed to the 3.4 developement kernel) still had working usb correctly, but it had the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb devices work properly while some that work correctly on the stock android kernel just don't work with their kernel). Anyone tried using vanilla kernels on Allwinner SOC based systems ? Anyone know what's going to work and what's not going to work if I try compiling a kernel from kernel.org ? touch screen is not important because that's not working well enough to be functional anyway. ATB David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hardware advice, plug and laptop.
Hi ! I would like to buy a plug-like computer (small form, not especially wall-charger type) and also an ARM laptop. It's for a very common usage, internet, video chat, etc. Can you guys recommend me some products/websites ? A lot depends on what you want out of your plug like computer ,,, if you want video output of some sort probably a Raspberry PI or a Olimex A13 (https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware) might be the sort of thing you want, but if it's to be used a sort of appliance (no need for video output) maybe some member of the plug family could be well suited. For the arm laptop, I don't know if you can get laptop sized ARM portables, but you might get lucky if you can get a netbook leftover that is arm based. Choose one that is know to be able to run custom images unless you are happy to use android. In some countries netbooks have been discontinued, in favor of the tablets, dew to poor demand. You might get lucky if you co to some hyperstore and find some ARM netbook leftover. For the arm laptop, I think that IBM have e new line of ARM powered laptops one thing you really want to make sure is that whatever you choose is know to be able to run custom images without going mad with issues in the boot loader. If it uses u-boot as boot loader there's a good chance that you can easily run custom linux images. ATB David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] A little rc.inet1 tweek
I've found that after ethernet module is loaded the link status in not reliable
until the interface has been brought up for at least a few seconds.
I often use my laptops both in presence and absence of DHCP servers. I found
the default way that the script detects the link status unreliable so I make
this change to my rc.inetd (Maybe someone else likes it too ;-) ):
--- rc.inet1 2013-08-17 21:44:25.040707457 +0200
+++ rc.inet1_new 2013-08-17 21:44:06.020603342 +0200
@@ -160,8 +160,25 @@
#fi
(end commented out)
# 10 seconds should be a reasonable default DHCP timeout. 30 was too
much.
- echo /etc/rc.d/rc.inet1: /sbin/dhcpcd -t ${DHCP_TIMEOUT[$i]:-10}
${DHCP_OPTIONS} ${1} | $LOGGER
- /sbin/dhcpcd -t ${DHCP_TIMEOUT[$i]:-10} ${DHCP_OPTIONS} ${1}
+ ifconfig ${1} up
+ STOP=$(expr $(/usr/bin/date +%s) + 5)
+ echo -n Waiting for link .
+ while [ $(/usr/bin/date +%s) -le $STOP ]; do
+ echo -n .
+ [ $(cat /sys/class/net/${1}/carrier 2 /dev/null) = 1 ] break
+ sleep 0.5
+ done
+ CONNSTATUS=$(cat /sys/class/net/${1}/carrier 2 /dev/null)
+ ifconfig ${1} down
+ if [ $CONNSTATUS -eq 1 ]; then
+ echo ${1} is uplinked
+ echo Polling for DHCP server on interface ${1}:
+ echo /etc/rc.d/rc.inet1: /sbin/dhcpcd -t ${DHCP_TIMEOUT[$i]:-10}
${DHCP_OPTIONS} ${1} | $LOGGER
+ /sbin/dhcpcd -t ${DHCP_TIMEOUT[$i]:-10} ${DHCP_OPTIONS} ${1}
+ else
+ echo ${1} is not linked
+ echo /etc/rc.d/rc.inet1: interface ${1} is not linked |$LOGGER
+ fi
else # bring up interface using a static IP address
if [ ! ${IPADDR[$i]} = ]; then # skip unconfigured interfaces
# Determine broadcast address from the IP address and netmask:___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Package auto? downgrade
I have release 13.37 according to /etc/slackware-version. I have recenly discovered that my mutt package has been downgraded, and I don't understand how/why. mutt in 13.37 was last touched in 2010. However, armedslack-13.1 has armedslack-13.1/slackware/n/mutt-1.4.2.3-arm-1 Where is slackpkg configured to download from? I suspect that you're some how downloading from the wrong tree, or the mirror you're using has mixed up content. The only uncommented line in mirrors is: ftp://mirror.inode.at/slackwarearm/armedslack-13.1/ so indeed it looks inconsistent I certainly didn't intentionally change anything to my mutt install, so what might have caused it to be downgraded? As far as I know slackpkg should not automatically do any sort of automatic package dependencies (unless you use a modified version that also rewuires using a repo with managed deps) or other automatic actions that are not specifically passed via command line (like upgrade or reinstall). Are yo sure you did not accidentally reinstall a package series and accidentally checked mutt for reinstall ? Is your system exposed to internet for long periods ? If I were you I'd check the package content to match perfectly (ie some hash check not just size) with what should be distributed with the package having an unjustified package version on your system could mean your system has been hacked. If your system has been hacked you might have other compromised bins so you should do your checks from a known good rescue system (ie your hash binary might have been hacked to report good hashes for the other bins that have been compromised). Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Package auto? downgrade
I have release 13.37 according to /etc/slackware-version. I have recenly discovered that my mutt package has been downgraded, and I don't understand how/why. mutt in 13.37 was last touched in 2010. However, armedslack-13.1 has armedslack-13.1/slackware/n/mutt-1.4.2.3-arm-1 Where is slackpkg configured to download from? I suspect that you're some how downloading from the wrong tree, or the mirror you're using has mixed up content. The only uncommented line in mirrors is: ftp://mirror.inode.at/slackwarearm/armedslack-13.1/ so indeed it looks inconsistent I certainly didn't intentionally change anything to my mutt install, so what might have caused it to be downgraded? As far as I know slackpkg should not automatically do any sort of automatic package dependencies (unless you use a modified version that also rewuires using a repo with managed deps) or other automatic actions that are not specifically passed via command line (like upgrade or reinstall). Are yo sure you did not accidentally reinstall a package series and accidentally checked mutt for reinstall ? No I am not sure :-) I remember at some I tried to upgraded to 13.37, but changed my mind. So maybe a few packages got upgraded, including mutt, and later reverted... I don't use slackpkg often :-) So I don't master it and I am a bit scared of loosing my data when trying to upgrade cleanly Once you start to upgrade your system, however it's being done, you should go all the way, failing to do so can leave you with a mess in the libraries that can be challenging to fix. Ba backup before starting is the correct way to revert if you change your mind. Is your system exposed to internet for long periods ? yes. If I were you I'd check the package content to match perfectly (ie some hash check not just size) with what should be distributed with the package having an unjustified package version on your system could mean your system has been hacked. If your system has been hacked you might have other compromised bins so you should do your checks from a known good rescue system (ie your hash binary might have been hacked to report good hashes for the other bins that have been compromised). That's a possibility indeed, but I am more inclined to thinking that I did something wrong several months ago and have now forgotten :-( Just wanted to warn you just in case, sometimes people tend to underestimate the the possibility of their system being hacked. I've won bets with people that consider security breach as a very remote possibility. Is there a way I can just install the new mutt without upgrading the whole system? slackpkg remove mutt slackpkg install mutt or alternatively : removepkg mutt-. download the desigred package and then installpkg mutt-.. As Stuart said this will work only if no library deps get broken, but if that is your case a reinstall will be much easier. Thanks, You're welcome David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Current status of arm ports eabihf
Sorry mixing html and standard indentation on yahoo means a lot of manual editing. Taking the ordinary slackware miniroot to one with compiler is really just a matter of installing some packages (in the d and l series ). I often do that on a live system just after having gotten networking and slackpkg working. If you look at the build script you can add what ever packages you need and build your own custom miniroot. But be aware that slackpkg (and possibly some other packages) will setup things on the host detected architecture so even if you install packages to e different root some configuration is done wrong , like for example slackpkg only having the x86 mirrors in the mirror list. Nothing you can't put right by hand but something you mignht want to know befor you start off. ATB David Da: Nigel Sollars nsoll...@gmail.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Domenica 28 Luglio 2013 21:33 Oggetto: Re: [ARMedslack] Current status of arm ports eabihf On Sun, Jul 28, 2013 at 4:17 PM, Ottavio Caruso ottavio2006-usenet2...@yahoo.com wrote: On Jul 28, 2013 8:56 PM, Nigel Sollars nsoll...@gmail.com wrote: Hi, Ive been away for a while, just thought id ask what the current state of a 32bit hf port is. I think the hf port is Eric's pet project but I could be wrong. I was looking at the blog actually, seems like the right direction. Be cool to see how the trimslice is working out. One question I have is, is the Linaro toolchain used in the slackport?. I'd like to see that but I suspect it needs cross compiling on a Ubuntu host. Not that it wouldn't be technical possible to cross compile on a Slackware host or any host, but... You could be right, Here is what I was hoping, is that a very simple ( mini ) root would be available ( and I mean mini ) with a working native compiler. I want to test the latter 3.10 released kernels as the Arm branch is very active with some nice fixes. For Embedded the most important is core support for better GPIO control. Ive gotten all the hardware working on the Panda, Wifi BT etc etc etc. But most probably not overly optimal. Nige Nige -- “Science is a differential equation. Religion is a boundary condition.” Alan Turing ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- “Science is a differential equation. Religion is a boundary condition.” Alan Turing ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd)
I haven't got a a20 (or earlier) device to play with (yet), but I am forwarding this email to arm-netbook. I hope this will raise interest of having Slackware on the Allwinner. I am preparing a generic armv6 and onwards Linux 3.10 kernel (the separate 'kirkwood' and 'versatile' kernels will remain as is because the armv5 support has not been consolidated). Initially I'll make sure that the existing 'Tegra' works since that's what I'm using as the main build machine, but I have also added support for Allwinner: [*] Allwinner A1X SOCs Of course, there will be plenty of other drivers and so on that would be required which someone can furnish me with at a later date once I push out the kernels. Supporting Allwinner SOC would really probabbly require a 3.0 or a 3.4 kernel from the linux-sunxi branch (https://github.com/linux-sunxi/linux-sunxi) as many patches have not made it to kernel.org, or searching around for the patches to apply to vanilla kernel (that will will be probabbly conceived for ither a 3.0 or a 3.4 kernel anyway). But if you come up with something to test I can see if it works on my XZPAD700. ATB David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd)
I got round to syncing my new image builder: http://ftp.slackware.org.uk/slackwarearm/people/louigi600/ Touchscreen is still not working on my device ... but if your touchscreen is on the usb bus chances are that it will work. Have fun David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Sabato 20 Luglio 2013 7:50 Oggetto: Re: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) My new image builder for the xzpad700 (as soon as I've time to sync it) will prepare images for all the hardware that the fedora currently supports (including the new A20 socs). as a matter of fact I\m using their bootloader and their kernels until I get round to building my own kernel. Incidently my image builder will let you deploy any distro root filesystem tarball ... but you might need a bit of manual for non slackware root tarballs. Regards David Da: Ottavio Caruso ottavio2006-usenet2...@yahoo.com A: ARMedslack@lists.armedslack.org Inviato: Venerdì 19 Luglio 2013 21:15 Oggetto: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. -- Forwarded message -- From: Antony Antony ant...@phenome.org Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: arm-netb...@lists.phcomp.co.uk this is an interesting news item, though my prefeence is a debian. -antony -- Forwarded message -- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede hdego...@redhat.com To: linux-su...@googlegroups.com, Fedora ARM a...@lists.fedoraproject.org, Development discussions related to Fedora de...@lists.fedoraproject.org Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), or at least no battery backup for it, resulting in the date + time being wrong. -If the date is of by more then a couple of months, yum update won't work because certificate validation fails for the https connection yum tries to make. So if yum fails to get its repodata first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20
Re: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd)
My new image builder for the xzpad700 (as soon as I've time to sync it) will prepare images for all the hardware that the fedora currently supports (including the new A20 socs). as a matter of fact I\m using their bootloader and their kernels until I get round to building my own kernel. Incidently my image builder will let you deploy any distro root filesystem tarball ... but you might need a bit of manual for non slackware root tarballs. Regards David Da: Ottavio Caruso ottavio2006-usenet2...@yahoo.com A: ARMedslack@lists.armedslack.org Inviato: Venerdì 19 Luglio 2013 21:15 Oggetto: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. -- Forwarded message -- From: Antony Antony ant...@phenome.org Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: arm-netb...@lists.phcomp.co.uk this is an interesting news item, though my prefeence is a debian. -antony -- Forwarded message -- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede hdego...@redhat.com To: linux-su...@googlegroups.com, Fedora ARM a...@lists.fedoraproject.org, Development discussions related to Fedora de...@lists.fedoraproject.org Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), or at least no battery backup for it, resulting in the date + time being wrong. -If the date is of by more then a couple of months, yum update won't work because certificate validation fails for the https connection yum tries to make. So if yum fails to get its repodata first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README - Quickstart guide 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run mount and if the card shows up in the output umount its partitions 3) Write the img file to the card, ie as root do: xzcat Fedora-19-a10-armhfp-r1.img.xz /dev/mmcblk0 sync 4) The card is not yet ready for use! Since the A10 u-boot is board specific, the image comes without any uboot install, follow the next
Re: [ARMedslack] Kernel 2.10 and raspberry pi
just been to kernel.org to see if the raspberry pi is supported. I see no support for the device in any kernel previous to 3.10.1 which includes support for the BCM2835. I find this odd. I would have thought that patches would have been submitted and merged in the the kernel tree. We still got super H Dreamcast code in there so why no Raspberry pi? Work is still being done on 3.6.11 at raspberry pi github. Work stopped last year on 3.2.27, so why are the patches not in kernel.org? I don't get this. I could post this to Raspberry pi, however my feeling is that I will not get a definitive answer. Perhaps I am misunderstanding how the process works. Please enlighten me. Welcome to linux ARM kernel developement :-). There are patches that have never made it to main kernel on almost all the ARM hardware I've worked on (not sure if the dockstar stuff made it all to main kernel but all the zauri, the AC100 and the whole Allwinner soc family are far from that ). Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] armedslack on android phone?
Stuart: what do you think about adding it to the list along with the AC100, Pandora and Pi ? How's about the 3rd party device support page is moved on to the ARM section of docs.slackware.com, and I change the link on http://arm.slackware.com to point to it. I don't think I need to be the custodian of the support matrix. If you want to go ahead and create the page on docs.slackware.com, go ahead and let me know once it's done. That's exactly what I was trying to say. Different story if you want me to add it to the non officially supported platforms section on the http://arm.slackware.com/supportedplatforms/ page. I've Slackware ARM booting on a AL-A13-RT713 board that came inside a tablet (XZPAD700) and I've documented my doings from hacking the info out of it to creating a MicroSD image for booting the Slackware miniroot and it's already all on http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I've also a tarball that contains all that is necessary to create bootable slackware miniroot for almost any A1x device that is currently supported by linux-sunxi, but I've no place to share it with anybody that may be intrested. David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] armedslack on android phone?
If the phone is an A1x based SOC there's chance that you can get started really quickly by reusing info on how I got Slackware arm on my XZPAD700 tables (that is a A13 based SOC). There's still work to do like the touchscreen and figuring out what kind of X server will work (probably a frame-buffer one) but it's booting and the frambuffer console is working. The documentation has not yet made it to the non officially supported platform list but I've documented my doings on http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet. I've also a self sufficient image builder that I've tarballed into 63Mb but have no place to put the image on. This new image builder replaces the script I've put on docs.slackware.com and feautres dialog menus for choosing things like target soc,kernel,partition sizes and root image tarball. Stuart: what do you think about adding it to the list along with the AC100, Pandora and Pi ? Ciao David Da: Brian L Gorecki gore...@fastguys.net A: 'Slackware ARM port' armedslack@lists.armedslack.org Inviato: Sabato 13 Luglio 2013 15:30 Oggetto: Re: [ARMedslack] armedslack on android phone? The most straight forward answer would be no, the arm architecture used in that phone isn’t supported ‘out of the box’. However, with some work, kernel builds and patience probably can be done. See http://arm.slackware.com/supportedplatforms/ for a starting point. I’ve had the same thoughts for an old Motorola Q I have but so far haven’t deemed it worth the effort. From:ARMedslack [mailto:armedslack-boun...@lists.armedslack.org] On Behalf Of Dennis Sent: Friday, July 12, 2013 1:39 PM To: armedslack@lists.armedslack.org Subject: [ARMedslack] armedslack on android phone? Hello all I have a motorola bionic phone with android JB. With it I have a webdock, which is basically a hdmi monitor with a usb mouse and keyboard. I use this fairly often and what I really miss is running linux as android is a modified version and just doesn't have the same look, feel, and functionality as a full linux system. I run slackware 14 on my home system, and when I found out slackware had this group I joined up. So far it looks like the rasp pi and simular computers are the target. Just wondering if anyone has ventured into the android phone area? I'm not sure if a dual boot would be possible? Or if it would have to run under the android shell as other linux distro's do. I haven't done much programming for a long time, but I do continue to use and play around with my linux machine at home. Been a slackware fan since 1992 or so and after trying some of the other distro's I found I prefer slackware still. Dual boot would be prefered, and I have found that the drivers for the phone are available thru android open source so just maybe this would be workable. I'm also looking to get a small computer like one of usb sticks I've seen to put the web on the TV, and am looking for any advice as to which would be the best for slackware/android combo. thanks Dennis ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] miniroot 14 and current: vi is broken
Well actually on my live slackware 14 (x86) vi is a link to elvis Although both are installed, by default vi is linked to elvis (and it's not something I did manually). looking at the sizes I cannot but agree that on the miniroot vim is just eating up space (just guessing that the arm packages will me more or less the same size) and on top of that there's 120Mb of dependencies to use it ! Since (if selected) elvis is installed first (due to being in series 'a'), it sets up a symlink in the doinst.sh script. If vim is installed, its doinst.sh script checks for the presence of the 'vi' symlink, and if not present, will symlink 'vi' to 'vim'. root@pepa:~/ac/source/a/elvis# head -n2 /var/log/scripts/elvis-2.2-arm-2 ( cd usr/bin ; rm -rf vi ) ( cd usr/bin ; ln -sf elvis vi ) root@pepa:~/ac/source/a/elvis# I noticed that vi in the miniroot slackware ARM 14 is still vim and lacking libs to make it functional. Elvis is not installed in the miniroot. Ok you can put it right pretty fast but it can be annoying if on the target device there is no means to get an extra package in apart from manipulating the flash. Ciao David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Exagerate XZPDA700
I got the kernel loading from uSD but then kernel panic because uboot passes wrong root device to kernel. http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I discovered that I cannot have the serial console if I boot feom uSD so I need some other means of manipulating the u-boot environment from the image before writing it to uSD, or in any case on the uSD before I try to boot. Anyone have an idea hot to fix that ? Having a better look at the u-boot environment it appears that it fetches variables from text files present in the boot partition so it's fixed. Last night I was able to boot and get to a login prompt. I had no usb keyboard so all I was able to do was turn it off again. I'll clean up the wiki page asap. Ciao David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Exagerate XZPDA700
I got the kernel loading from uSD but then kernel panic because uboot passes wrong root device to kernel. http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I discovered that I cannot have the serial console if I boot feom uSD so I need some other means of manipulating the u-boot environment from the image before writing it to uSD, or in any case on the uSD before I try to boot. Anyone have an idea hot to fix that ? Regards David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Exagerate XZPDA700
I downloaded the rescue image from http://www.hamletcom.com/docs/XZPAD700_microsd_restore_B.zip and I found some evidence that the device uses u-boot. I'm not sure if the u-boot image I found in the rescue image is part of the image that gets restored into the device or if the rescue image itself has a boot loader in it that gets loaded into ram as if it was a second stage boot loader. Anyway the rescue image appears as a bootable image: root@darkstar:/tmp/XZPAD700_microsd_restore_B# file XZPAD700_MicroSD_restore_B_20121122.img XZPAD700_MicroSD_restore_B_20121122.img: x86 boot sector; partition 1: ID=0xb, active, starthead 0, startsector 798949, 202522 sectors, code offset 0x0 root@darkstar:/tmp/XZPAD700_microsd_restore_B# root@darkstar:/tmp/XZPAD700_microsd_restore_B# fdisk -l XZPAD700_MicroSD_restore_B_20121122.img Disk XZPAD700_MicroSD_restore_B_20121122.img: 513 MB, 513802240 bytes 1 heads, 63 sectors/track, 15928 cylinders, total 1003520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System XZPAD700_MicroSD_restore_B_20121122.img1 * 798949 1001470 101261 b W95 FAT32 root@darkstar:/tmp/XZPAD700_microsd_restore_B# But I've not been able to mount it as a loop device with all my efforts to calculate the offset of that first partition is shown by fdisk. I even wrote the image to a microsd as documented but I was unable to mount that first partition anyway. Anyone have any idea how to mount that partition ? I then started examining the rescue image with strings and found a few interesting things: ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c --cpu=Cortex-A8.no_neon -O0 -I. -I./../../../config -I./../../../boot1/include -I./../../../boot1/include/interinc -I. -I./.svn -I./.svn/prop-base -I./.svn/props -I./.svn/text-base -I./.svn/tmp -I./.svn/tmp/prop-base -I./.svn/tmp/props -I./.svn/tmp/text-base -I ./Board -I./Board/.svn -I./Board/.svn/prop-base -I./Board/.svn/props -I./Board/.svn/text-base -I./Board/.svn/tmp -I./Board/fel_detect -I./Board/fel_detect/.svn -I./Board/power_ctrl -I./Board/power_ctrl/.svn -I./BootOS -I./BootOS/.svn -I./BootOS/.svn/prop-base -I./BootOS/.svn/pro ps -I./BootOS/.svn/text-base -I./BootOS/.svn/tmp -I./Common -I./Common/.svn -I./Common/.svn/prop-base -I./Common/.svn/props -I./Common/.svn/text-base -I./Common/.svn/tmp -I./Common/Picture -I./Common/Picture/.svn -I./Common/script_patch -I./Common/script_patch/.svn -I./Common/se rvice -I./Common/service/.svn -I./Common/ui -I./Common/ui/.svn -I./Common/ui/display_interface -I./config -I./config/.svn -I./config/.svn/prop-base -I./config/.svn/props -I./config/.svn/text-base -I./config/.svn/tmp -I./Include -I./Include/.svn -I./Include/.svn/prop-base -I./Inc lude/.svn/props -I./Include/.svn/text-base -I./Include/.svn/tmp -I./part_info -I./part_info/.svn -I./part_info/.svn/prop-base -I./part_info/.svn/props -I./part_info/.svn/text-base -I./part_info/.svn/tmp -I./usb_device -I./usb_device/.svn -I./usb_device/.svn/prop-base -I./usb_dev ice/.svn/props -I./usb_device/.svn/text-base -I./usb_device/.svn/tmp eGon2_common.o c_int.o format_transformed.o ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c --cpu=Cortex-A8.no_neon -O0 -I. -I./../../boot1/include -I./../../boot1/include/cfgs _int.o ARM Assembler, RVCT4.0 [Build 400] armasm --debug --keep --cpu=Cortex-A8.no_neon -I. -I./../../boot1/include -I./../../boot1/include/cfgs ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c --cpu=Cortex-A8.no_neon -O0 -I. -I./../../../config -I./../../../boot1/include -I. -I./.svn -I./.svn/prop-base -I./.svn/props -I./.svn/text-base -I./.svn/tmp -I./.svn/tmp/prop-base -I./.svn/tmp/props -I./.svn/tmp/text-base -I./config -I./config/.svn -I./config/ .svn/prop-base -I./config/.svn/props -I./config/.svn/text-base -I./config/.svn/tmp -I./de_bsp -I./de_bsp/.svn -I./de_bsp/.svn/prop-base -I./de_bsp/.svn/props -I./de_bsp/.svn/text-base -I./de_bsp/.svn/tmp -I./de_bsp/de -I./de_bsp/de/.svn -I./de_bsp/de/ebios -I./de_bsp/iep -I./de_bsp/iep/.svn -I./de_bsp/lcd -I./de_bsp/lcd/.svn -I./OSAL -I./OSAL/.svn -I./OSAL/.svn/prop-base -I./OSAL/.svn/props -I./OSAL/.svn/text-base -I./OSAL/.svn/tmp eGon2_common.o cleanflushcachebyregion.o format_transformed.o ARM C/C++ Compiler, RVCT4.0 [Build 400] armcc --debug -c --cpu=Cortex-A8.no_neon -O0 -I. -I./../../boot1/include -I./../../boot1/include/cfgs cleanflushcachebyway.o ARM Assembler, RVCT4.0 [Build 400] armasm --debug --keep --cpu=Cortex-A8.no_neon -I. -I./../../boot1/include -I./../../boot1/include/cfgs img_name = c:\linux\u-boot.bin U-Boot 2011.09-rc1-dirty (Nov 22 2012 - 14:25:29) Allwinner Technology U-Boot 2011.09-rc1-dirty (Nov 22 2012 - 14:25:29) Allwinner Technology
Re: [ARMedslack] Exagerate XZPDA700
I got tempted with one of these. Integrated BGN wifi 1 usb client/host port qith support for external usb devices (is ethernet/3G ) 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is reserved for boot/rescure/emergency restore) 7 screen 800x480 px single core cortex A8 (not tegra) 1/2Gb ram micro SD slot with support for 32Gb cards 3 axis accelerometer Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still tempted to try have Slackware on this one too. The user-land will probably only require just xkbd but I doubt the kernel that comes with the device has proper frame-buffer console so I'll need to figure out what sort of kernel to put on that thing. Hello! Where did you find out about the thing to begin with? Google doesn't know a thing about it, and wanted to tell me about a completely useless contraption used for playing bad music. Ooops ... XZPAD700 I have one ... I got in in hypermarket Carrefour in offer 69 Euro. I'm sure it's a re branded Chinese thing but for that price I can stick up with it. I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap. Ok here's some info on the device (I've not yet rooted the device but I got is as root so I guess this one is not locked) : I did a bit of search on distributor's site and it appears that if you press and hold the power button while booting it's able to recover from a factory rescue image placed in a microSD. I'm not sure if this will allow you to load a different kernel (probabbly not) but I'm pretty sure the microSD can be packed to look like a rescue image but have a custom userland instead. I've downloaded the rescue image to see if I can figure out how it's assembled. Ciao David root@darkstar:~/ac100/devel/android-sdk-linux_x86/platform-tools# ./adb shell ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Prompts and Slackware (general not necessarily ARM related)
Hello! It's possible. But not unlikely. The other question is when was the Kernel site hacked? It was ages ago - in 2001! Unlikely 2001 back then we only had 2.4 stable kernels more like 2010 Chances are that your installation has installed something dodgy, or you may even have some faulty RAM modules. Also unlikly as I seen it on different distributions (even enterprise ones at work) , on different hardware and in virtual machines (belonging to a vmware infrastructure system), on my scripts and on system scripts. Well whatever ... might not be connected to that but surely it's an odd thing. David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Prompts and Slackware (general not necessarily ARM related)
Hello! Earlier today I had my Slackware (on Intel) system uninstall system. Its installer removal program told me that I'd need to log out and log back in before there would be any changes seen. Well I did that. On logging back in I saw that the process had eaten the prompt. It replaced the user name@machine name that's been a mainstay of Linux since I first started using the OS many years earlier, with just the shell name. Which is of course Bash. I don't suppose all of you have any ideas for recovering things, outside of reinstalling the works? In that eventually I made sure I had downloaded a fresh DVD image of Slackware, and of the version that the system is currently running. And I'm making plans for backing up everything important that I put on the system since it was installed about two years ago December. I also asked on a list that I fellow I know runs where everyone runs everything else, and advice is rarely Slackware friendly. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. I haven't used slackware on intel for some time but I'm not aware of a system uninstall utility, unless you mean uninstalling a single package. Hello! It was the installer for QNX a Posix based Real Time OS who claims to be running on a lot of business based systems. I sometimes try to build images for applications that are slightly above the norm. You're close enough Stuart, it was the installer mechanism for that product who crashed things. Earlier I did find the original profile saved as profile.backup and copied it back, and noted that it was setup as an empty file when the thing was removed. I also did restore the etc area and noted the presence of profile.new as well. Mine was the backup named file. I'm beginning to think that since kernel.org was hacked that things just are not the same I'm seeing more and more often segmentation fault and memory fault in bash scriprs. Now it's odd that a script that executes only internal or userland commands exibits a segmentation fault that as far as I recall means that a program is accessing memory that is not pertinent to that program. Should not bash and the GNU userland (shippet with stable distributions) be immune to this sort of problem ? Ciao David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Exagerate XZPDA700
I got tempted with one of these. Integrated BGN wifi 1 usb client/host port qith support for external usb devices (is ethernet/3G ) 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is reserved for boot/rescure/emergency restore) 7 screen 800x480 px single core cortex A8 (not tegra) 1/2Gb ram micro SD slot with support for 32Gb cards 3 axis accelerometer Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still tempted to try have Slackware on this one too. The user-land will probably only require just xkbd but I doubt the kernel that comes with the device has proper frame-buffer console so I'll need to figure out what sort of kernel to put on that thing. Hello! Where did you find out about the thing to begin with? Google doesn't know a thing about it, and wanted to tell me about a completely useless contraption used for playing bad music. Ooops ... XZPAD700 I have one ... I got in in hypermarket Carrefour in offer 69 Euro. I'm sure it's a re branded Chinese thing but for that price I can stick up with it. I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap. Ciao David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Exagerate XZPDA700
I got tempted with one of these. Integrated BGN wifi 1 usb client/host port qith support for external usb devices (is ethernet/3G ) 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is reserved for boot/rescure/emergency restore) 7 screen 800x480 px single core cortex A8 (not tegra) 1/2Gb ram micro SD slot with support for 32Gb cards 3 axis accelerometer Ok android 4 is not as bad as the 2.1 that came with the AC100 but I'm still tempted to try have Slackware on this one too. The user-land will probably only require just xkbd but I doubt the kernel that comes with the device has proper frame-buffer console so I'll need to figure out what sort of kernel to put on that thing.___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Toshiba AC100
http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az It was just a quick cut and paste with minor changes. I'll work on it to make it better and all comments are welcome. Would a separate ARM section be a good idea? It'd make content easier to find although it may break up the structure of the site a little bit. Eric suggested that that would be a good place to start from so I took his advice but if we gather up all the ARM specific stuff together it would be nice too. Well whatever ... I'll be a good lamb and follow the flock :-D Ciao David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Toshiba AC100
I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been taken down thus braking the link for the information on how to get slackware arme on the AC100. I'm trying to get the info from the wetpaint crew (at least the text I wrote) to see if I can have it hosted somewhere else. Regards David Hello! I just asked Google about our interested problem and as it happens Google told me about the Wikipedia entries on it. That location has at its bottom of page an external link, that link is here: http://ac100.grandou.net/ that Wiki has a surprise there. It contains your text carefully collected from the mistake that Wetpaint claims they blocked. (The mistake was theirs, not yours.) I believe it is the text you were thinking of. Intresting but I can't see to find my text I probabbly need to have a better look but even the search form over there is not helping me. Have you a link directly to the text ? Stuart: if thext is where Greg says maybe the link in the supported platforms should be updated (as it's currently broken). Regards David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Toshiba AC100
I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been taken down thus braking the link for the information on how to get slackware arme on the AC100. I'm trying to get the info from the wetpaint crew (at least the text I wrote) to see if I can have it hosted somewhere else. Regards David Hello! I just asked Google about our interested problem and as it happens Google told me about the Wikipedia entries on it. That location has at its bottom of page an external link, that link is here: http://ac100.grandou.net/ that Wiki has a surprise there. It contains your text carefully collected from the mistake that Wetpaint claims they blocked. (The mistake was theirs, not yours.) I believe it is the text you were thinking of. Intresting but I can't see to find my text I probabbly need to have a better look but even the search form over there is not helping me. Have you a link directly to the text ? Stuart: if thext is where Greg says maybe the link in the supported platforms should be updated (as it's currently broken). Regards David Hello! It's down at the bottom of the pages on the new site. I promptly selected the link and brought it up, and shoehorned it into the Tiny URL maker. Here: http://tinyurl.com/m3qffon and that's yours. They state that after importing the (possibly) obsolete information it will be deleted. There's probably something wrong with me or with my browser or some other dumb thing ... but I recognize a menu that's resembles remotely what used to be on tosh-ac100 ... but I looked on every element of the menu and could not recognise my armedslack (it was not slackware arm at the time) howto ... well if you can see the text save it somewhere. I'm not interested in the layout ... just the text. I'll fix it up and find another place to host it. Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Toshiba AC100
I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been taken down thus braking the link for the information on how to get slackware arme on the AC100. I'm trying to get the info from the wetpaint crew (at least the text I wrote) to see if I can have it hosted somewhere else. Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] tigervnc for slackware arm
It's not a typo I'm looking for TIGERvnc client not tightvnc client. I run a desktop across 2 screens on my work pc (tigervnc x0vncserver shares your live desktop) and the tightvnc client seems to crash when I try to connect to it, this does not happen if I use the tigervnc client. Regards David Da: Richard Lapointe richard.lapoi...@gmail.com A: Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Sabato 18 Maggio 2013 14:26 Oggetto: Re: [ARMedslack] tigervnc for slackware arm Here one that I built but never tested. http://dl.dropboxusercontent.com/u/90881870/tightvnc-1.3.10-arm-1rl.txz It was built on a d\Dockstar running slackwarearm 14.0 I have close to five hundred arm (armv5tel) packages that were built natively on a Dockstar / Pogoplug using Salix slkbuild packaging system (http://slkbuild.sourceforge.net/) and Salix's source repo ( http://salix.enialis.net/x86_64/14.0/source/). Rich Lapointe (laprjns) On 05/17/2013 01:53 PM, Davide wrote: Can't seem to get tightvnc client to interoperate with the x0vncserver running on my desktop. I can find tigervnc package for x86 slackware ... anyone have an idea if there's an ARM tigervnc package ? Regards David ar ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] tigervnc for slackware arm
Can't seem to get tightvnc client to interoperate with the x0vncserver running on my desktop. I can find tigervnc package for x86 slackware ... anyone have an idea if there's an ARM tigervnc package ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] getting SATA working on seagate goflex net
I came across that yesterday while trying to check if I had the right arcnumber
... it would be really handy to have a list of the devices and their correct
archnumber somewhere ;-)
I tried setting 3089 as archnumber but the slackware kernel no longer boots if
I do that.
This can probably be fixed if I rebuild the kernel (not sure if patching is
needed too) ... but since my work on ClashNG there are 2 new members in my
family so if I can avoid time consuming stuff that would be really good.
Can I borrow a kernel from somewhere else that is known to work well if I use
it on a slackware arm 14 userland (and has support for all features of the
goflex net )?
Regards
David
Da: Richard Lapointe richard.lapoi...@gmail.com
A: Davide louigi...@yahoo.it; Slackware ARM port
armedslack@lists.armedslack.org
Inviato: Martedì 23 Aprile 2013 0:42
Oggetto: Re: [ARMedslack] getting SATA working on seagate goflex net
Maybe this will help
http://forum.doozan.com/read.php?2,12045,12045#msg-12045
Rich Lapointe
On 04/22/2013 08:49 AM, Davide wrote:
I decided it was time to pull out the goflexnet and hook up two 2.5 sata
drives on it.
I've slackware arm 14 running on it but I can't seem to see
anything like a sata bus detected on my goflex net.
Do I need to do something on uboot ro enable sata before the
kernel is started ?
I've also fixed the rootfs not being passed correctly via
kernel command line:
fw_setenv usb_scan 'usb start; setenv usb_boot_dev none; for
dev in $usb_dev_list; do test $dev -eq 0 setenv
devname /dev/sda ; test $dev -eq 1 setenv devname
/dev/sdb ; test $dev -eq 2 setenv devname /dev/sdc
; test $dev -eq 3 setenv devname /dev/sdd ; echo
$devname ; for part in $usb_part_list; do echo $dev $part ; if
ext2ls usb ${dev}:$part /etc ; then setenv root_fs
root=${devname}$part ; setenv rootfstype rootfs=ext2 ; fi ; if
ext2load usb ${dev}:$part 0x80 /boot/uImage 10 ; then
setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir /boot ;
fi ; if ext2load usb ${dev}:$part 0x80 /uImage 10 ; then
setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir ; fi ;
done; done; if test $usb_boot_dev = none ; then echo No
USB bootable device found ; else echo USB device
$usb_boot_dev is bootable ; setenv bootargs $console
$mtdparts $root_fs ro $rootfstype ; echo $bootargs ; sleep 1;
ext2load usb $usb_boot_dev 0x80 $usb_boot_dir/uImage
setenv usb_boot_address 0x80 ; ext2load usb
$usb_boot_dev 0x110 $usb_boot_dir/uinitrd
setenv usb_boot_address 0x80 0x110 ; bootm
$usb_boot_address ; fi;'
fw_setenv bootcmd 'run usb_scan; run set_flash_bootargs; run
boot_flash_kernel'
but that does not seem to help detecting anything connected to
the sata ports.
Is the arch number correct ?
arcNumber=2097
Also I can't find where the leds are controlled ... there are
a total of 8 monochromatic and one bicolr lets on this thing
but I can only find this:
root@slackware:/sys/class/leds# ls
plug:green:health@ plug:red:misc@
root@slackware:/sys/class/leds#
what's up with the 8 white leds ?
Reegards
David
___
ARMedslack mailing list ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack ___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] getting SATA working on seagate goflex net
I decided it was time to pull out the goflexnet and hook up two 2.5 sata
drives on it.
I've slackware arm 14 running on it but I can't seem to see anything like a
sata bus detected on my goflex net.
Do I need to do something on uboot ro enable sata before the kernel is started ?
I've also fixed the rootfs not being passed correctly via kernel command line:
fw_setenv usb_scan 'usb start; setenv usb_boot_dev none; for dev in
$usb_dev_list; do test $dev -eq 0 setenv devname /dev/sda ; test $dev -eq 1
setenv devname /dev/sdb ; test $dev -eq 2 setenv devname /dev/sdc ; test
$dev -eq 3 setenv devname /dev/sdd ; echo $devname ; for part in
$usb_part_list; do echo $dev $part ; if ext2ls usb ${dev}:$part /etc ; then
setenv root_fs root=${devname}$part ; setenv rootfstype rootfs=ext2 ; fi ; if
ext2load usb ${dev}:$part 0x80 /boot/uImage 10 ; then setenv usb_boot_dev
$dev:$part ; setenv usb_boot_dir /boot ; fi ; if ext2load usb ${dev}:$part
0x80 /uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir
; fi ; done; done; if test $usb_boot_dev = none ; then echo No USB
bootable device found ; else echo USB device $usb_boot_dev is bootable ;
setenv bootargs $console $mtdparts $root_fs ro $rootfstype ; echo $bootargs ;
sleep 1; ext2load usb $usb_boot_dev 0x80
$usb_boot_dir/uImage setenv usb_boot_address 0x80 ; ext2load usb
$usb_boot_dev 0x110 $usb_boot_dir/uinitrd setenv usb_boot_address
0x80 0x110 ; bootm $usb_boot_address ; fi;'
fw_setenv bootcmd 'run usb_scan; run set_flash_bootargs; run boot_flash_kernel'
but that does not seem to help detecting anything connected to the sata ports.
Is the arch number correct ?
arcNumber=2097
Also I can't find where the leds are controlled ... there are a total of 8
monochromatic and one bicolr lets on this thing but I can only find this:
root@slackware:/sys/class/leds# ls
plug:green:health@ plug:red:misc@
root@slackware:/sys/class/leds#
what's up with the 8 white leds ?
Reegards
David
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] slackwarearm on seagate dosckstar
Ok ... just wish to thank you all for the help. I now have slackware arm 14 up and running on my dockstar and have moved my attention to compiling mediatomb on it. David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 18 Aprile 2013 13:42 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Yeah ... I realized just after having sent the first mail ... I was probably typing something wrong without realizing and slackpkg was telling me there was nothing to install because it was already installed :-D Sorry for making a noise about my dyslexic typing on the keyboard lol. David Da: Richard Lapointe richard.lapoi...@gmail.com A: armedslack@lists.armedslack.org Inviato: Giovedì 18 Aprile 2013 12:39 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be missing from the slackware arm 14 repo ... I forgot where I got it from on 13.37 but on my old armedslack 13.37 it's installed: u-boot-tools-2010.12rc1-arm-1 It's in the repo root@pogo-161:/home/rich# slapt-get --se U-boot u-boot-tools-2012.04.01-arm-1 [inst=yes]: u-boot-tools (Tools for systems using the Das U-Boot Linux Loader) Rich Lapointe ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] slackwarearm on seagate dosckstar
The old uboot image instalelt over 2 years ago on my dockstar was a Jeff Doozan image with a modified environment ... and it still boots 2.6 kernels that I was using at the time (not sure if I ever got round to diddling with 3.x kernels on my dockstar but I'll check asap). Did Doozan's uboot images brake somwhere along the kernel developement line from 2.6.38 to 3.4 ? This is a live clashNG environment running from internal flash on my dockstar: root@surap:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Seagate FreeAgent DockStar Revision : Serial : root@surap:~# uname -a Linux surap 2.6.38.3-kirkwood #2 PREEMPT Fri Apr 15 22:36:21 BST 2011 armv5tel GNU/Linux root@surap:~# And this is a live armedslack 13.37 running from that same dockstar and booting from a usb stick: root@slackware:~# cat /etc/slackware-version Slackware 13.37.0 root@slackware:~# uname -a Linux slackware 2.6.38.7-kirkwood #1 PREEMPT Thu May 26 08:29:19 BST 2011 armv5tel Feroceon 88FR131x root@slackware:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Seagate FreeAgent DockStar Revision : Serial : root@slackware:~# df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/sda2 7483 3463 4020 47% / root@slackware:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100 root@slackware:~# So I'm pretty much sure that the u-boot setup is ok ... just happens that for some reason I'm unable to boot the new 3.4 kirkwood kernel. Yeah I got a couple of DKU-5 compatible cables from an ebay user (I forgot the details since it was 2 years ago) and i recall that for something like 5 Euro I had them both shipped to my door. Doing enbedded stuff without at least a serial cable suitable for the target platform is difficult to say the least ... at some stage I plan to start using jtag too ;) Da: Richard Lapointe richard.lapoi...@gmail.com A: Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 18 Aprile 2013 3:32 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS. All three are running Slackwarearm 14.0 I also use these for my serial connection. http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0_nkw=USB+2.0+to+TTL+UART_sacat=0_from=R40 root@pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root@pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x80 0x10 0x40; bootm 0x80; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x170 /rescueme 1 || fatload usb 0:1 0x170 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data ubifsmount rootfs ubifsload 0x80 /boot/uImage ubifsload 0x110 /boot/uInitrd; then bootm 0x80 0x110; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 ext2load usb $usb 0x80 /boot/uImage 1; then usb_scan_done=1; echo Found bootable drive on usb $usb; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev
Re: [ARMedslack] slackwarearm on seagate dosckstar
Ok I had a read on Jeffs uboot page and: Kernel 3.2.y introduced a default setting for the kernel that affects kirkwood machines in particular, because of an unintended u-boot behavior with regard to the Level2Cache and decompression of the kernel image. Call it a latent bug in u-boot, a regression in the kernel, or whatever... the defconfig kirkwood kernel build of 3.2.y (and by extension, higher versions) will fail to boot in most/many cases. So I updated the uboot image with the install script (I did it by hand the first time around and I;ll savemyself the trouble if possible) and nor the kernel gets loaded properly. I still have an issue concerning that the root filesystem on the usb stick is ext2 while the slackware arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix that by remaking my usb stick image or by repackaging the initrd with the correct fstype ... maybe I just need to recheck how I pass boot parameters to kernel from uboot when I detect a valid usb stick ! Regards David Da: Davide louigi...@yahoo.it A: Richard Lapointe richard.lapoi...@gmail.com; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 18 Aprile 2013 8:48 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar The old uboot image instalelt over 2 years ago on my dockstar was a Jeff Doozan image with a modified environment ... and it still boots 2.6 kernels that I was using at the time (not sure if I ever got round to diddling with 3.x kernels on my dockstar but I'll check asap). Did Doozan's uboot images brake somwhere along the kernel developement line from 2.6.38 to 3.4 ? This is a live clashNG environment running from internal flash on my dockstar: root@surap:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Seagate FreeAgent DockStar Revision : Serial : root@surap:~# uname -a Linux surap 2.6.38.3-kirkwood #2 PREEMPT Fri Apr 15 22:36:21 BST 2011 armv5tel GNU/Linux root@surap:~# And this is a live armedslack 13.37 running from that same dockstar and booting from a usb stick: root@slackware:~# cat /etc/slackware-version Slackware 13.37.0 root@slackware:~# uname -a Linux slackware 2.6.38.7-kirkwood #1 PREEMPT Thu May 26 08:29:19 BST 2011 armv5tel Feroceon 88FR131x root@slackware:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1192.75 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Seagate FreeAgent DockStar Revision : Serial : root@slackware:~# df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/sda2 7483 3463 4020 47% / root@slackware:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100 root@slackware:~# So I'm pretty much sure that the u-boot setup is ok ... just happens that for some reason I'm unable to boot the new 3.4 kirkwood kernel. Yeah I got a couple of DKU-5 compatible cables from an ebay user (I forgot the details since it was 2 years ago) and i recall that for something like 5 Euro I had them both shipped to my door. Doing enbedded stuff without at least a serial cable suitable for the target platform is difficult to say the least ... at some stage I plan to start using jtag too ;) Da: Richard Lapointe richard.lapoi...@gmail.com A: Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 18 Aprile 2013 3:32 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS. All three are running Slackwarearm 14.0 I also use these for my serial connection. http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0_nkw=USB+2.0+to+TTL+UART_sacat=0_from=R40 root@pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root@pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial
Re: [ARMedslack] slackwarearm on seagate dosckstar
One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be missing from the slackware arm 14 repo ... I forgot where I got it from on 13.37 but on my old armedslack 13.37 it's installed: u-boot-tools-2010.12rc1-arm-1 ooops ... maybe something wrong with me ... it's installed probabbly on the miniroot ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] slackwarearm on seagate dosckstar
I'ts been a while since I last fiddled with the seagate dockstar ... I puklled it back out wanting to involve it on media streaming via DLNA. I fiddled with a slackwarearm 14 miniroot image on a versatile emulated machine untill I thaught I had all the bits and pieces needed to boot from the dockstar ... but when I put the image on usb stick this is all I'm getting: Loading file /boot/uImage from usb device 0:1 (usbda1) 2343448 bytes read Loading file /boot/uinitrd from usb device 0:1 (usbda1) 7314743 bytes read USB device 0:1 is bootable ## Booting kernel from Legacy Image at 0080 ... Image Name: Linux-3.8.7-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2343384 Bytes = 2.2 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: Slackware ARM for kirkwood platf Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7314679 Bytes = 7 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. And that's it ... nothing more on the serial console and nothing on the network actually it does not even appear to mount the root filesystem as the last mount seems to be coherent with the last time I mounted it on my PC Do I need to recompile the kernel (I'm using the kirkwood uImage) or is there something else wrong ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] slackwarearm on seagate dosckstar
I'ts been a while since I last fiddled with the seagate dockstar ... I puklled it back out wanting to involve it on media streaming via DLNA. I fiddled with a slackwarearm 14 miniroot image on a versatile emulated machine untill I thaught I had all the bits and pieces needed to boot from the dockstar ... but when I put the image on usb stick this is all I'm getting: Loading file /boot/uImage from usb device 0:1 (usbda1) 2343448 bytes read Loading file /boot/uinitrd from usb device 0:1 (usbda1) 7314743 bytes read USB device 0:1 is bootable ## Booting kernel from Legacy Image at 0080 ... Image Name: Linux-3.8.7-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2343384 Bytes = 2.2 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: Slackware ARM for kirkwood platf Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7314679 Bytes = 7 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. And that's it ... nothing more on the serial console and nothing on the network actually it does not even appear to mount the root filesystem as the last mount seems to be coherent with the last time I mounted it on my PC Do I need to recompile the kernel (I'm using the kirkwood uImage) or is there something else wrong ? Hello! Probably. But we need more information. How did you collect the information that you've shown us? How is your system (if that term can be applied) configured? Including how did you connect its serial console? Seial via a modified DKU-5 cable and use minicom to manage that. The console is connected right and I can use it if I boot into the old image I burned into the internal flash but that old system is too crippled to do the streaming stuff I have one here, about all I did was pop off its housing and study the internals. My other problems were along the lines of setting the boot blocks to boot from an attached USB key. The custom uboot scripts I'm using can boot ok from a USB stick provided you put the images in the right place so uboot can find them ... and as you can see they are found and loaded. I even tested that all was ok by booting from a clashNG image on the usb stick too and it boots ok. Currently I'm running my activities on a plain black pogoplug. Who has an 8Gig key attached, and one of those portable external drives attached sized 80 Gig and formatted as FAT32. I originally had plans to, do stuff with either via the USB ports but not as if either were wearing drives with stuff on them, but doing something specific. I still want to, ah, target my Dock Star but the difficult part is to workout how to attach that serial console and without damaging things. Buy a DKU-5 compatible cell Phone cable it has the required voltage serial port interface for the dockstar (and may more devices) ... you will just need to tut off the phone plug and wire up an old 2.5 hdu conenctor to the cable so that you can plug it into the dockstar. I think I mention how I did that on the clashNG project If you want a readymade woking image for the dockstar have a look at bclash on sourceforge ... it's unmaintained over the last 2 years but it still boots from my onboard flash on the dockstar. Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] slackwarearm on seagate dosckstar
Uncompressing Linux... done, booting the kernel.
And that's it ... nothing more on the serial console and nothing on the
network actually it does not even appear to mount the root
filesystem as the last mount seems to be coherent with the last time I
mounted it on my PC Do I need to recompile the kernel (I'm using the
kirkwood uImage) or is there something else wrong ?
This usually happens when the kernel +initrd does not fit into the
allocated memory locations. Make sure you have the u-boot memory settings
correctly set:
Marvell tftpboot 0x0110 %SLACKTREE%/uinitrd-kirkwood.img
Marvell tftpboot 0x0080 %SLACKTREE%/uImage-kirkwood
Marvell setenv bootargs console=ttyS0,115200 nodhcp kbd=uk
root=/dev/ram rw
Marvell bootm 0x0080 0x0110
I haven't tried the latest Kirkwood kernel on a Plug machine, but I know
it does work on the OpenRD client. I added the 'earlyprintk' debugging to
the Tegra20 kernel which'd show you what was wrong, but I don't think this
is available in the kirkwood implementation (although I'll have a look
again later).
O possibly the sizes matched what i was using 2 years back ... might nit fit
the new images
I've lost familiarity with uboot command line
I load them from usb with something that looks like this:
${dev}
$part
${usb_boot_dir}
get populated somewhere along the execution of the script
ext2load usb ${dev}:$part 0x80 ${usb_boot_dir} /uImage
ext2load usb ${dev}:$usb_dev_part 0x110 ${usb_boot_dir}/uinitrd
setenv usb_boot_address 0x80 0x110
bootm $usb_boot_address
but they do look as if they are ok
The images got into /boot when by installing the packages from the versatile
virtual machine (I then manually linked with the correct names my uboot looks
for)
root@darkstar:/mnt/floppy/boot# ls
System.map@ config-kirkwood-3.4.11 uImage-kirkwood-3.4.11
uinitrd-kirkwood-3.4.11
System.map-kirkwood-3.4.11 uImage@ uinitrd@
root@darkstar:/mnt/floppy/boot# md5sum uinitrd-kirkwood-3.4.11
uImage-kirkwood-3.4.11
0ff11c800fa6745b04676787596246de uinitrd-kirkwood-3.4.11
0c5e9a376a92e49863e2989875564a12 uImage-kirkwood-3.4.11
root@darkstar:/mnt/floppy/boot#
so I'm supposing that it's not an issue on how they got into the image.
anyway just incase anyone is intrested on the script I'm using for booting from
usb stick if present (and correctly setup) or from internal flash here's a dump
of printenv:
Marvell printenv
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200
bootdelay=3
baudrate=115200
console=console=ttyS0,115200
mtdids=nand0=orion_nand
partition=nand0,2
led_init=green blinking
led_exit=green off
led_error=orange blinking
ethact=egiga0
arcNumber=2998
usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part}
usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part}
usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part}
usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part}
usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part}
usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part}
usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part}
set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro
${root_fstype}
mtdparts=mtdparts=orion_nand:1M(u-boot),4M@1M(uImage),32M@5M(rootfs),219M@37M(data)
root_fs=root=/dev/mtdblock2
root_fstype=rootfstype=jffs2
bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel
ethaddr=00:10:75:1A:21:B7
usb_part_list=4 3 2 1
usb_dev_list=6 5 4 3 2 1 0
usb_dev_part=0
usb_scan=usb start; setenv usb_boot_dev none; for dev in $usb_dev_list; do for
part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv
usb_boot_dir; ext2ls usb ${dev}:$part /boot setenv usb_boot_dir /boot; if
ext2load usb ${dev}:$part 0x80 ${usb_boot_dir}
/uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv
usb_boot_address 0x80; setenv root_fstype rootfstype=ext2; run
usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part
0x110 ${usb_boot_dir}/uinitrd; setenv usb_boot_address
0x80 0x110; fi; done; done; if test $usb_boot_dev = none; then echo
No USB bootable device found; else echo USB device
${usb_boot_dev}:$usb_dev_part is bootable; bootm $usb_boot_address; fi;
flash_root_fstype=rootfstype=jffs2
flash_kernel_size=0x30
flash_kernel_load_addr=0x640
set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro
${flash_root_fstype}
boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest
$flash_kernel_size; bootm $flash_kernel_load_addr
flash_root_fs=root=/dev/mtdblock2
flash_kernel_offest=0x10
stdin=serial
stdout=serial
stderr=serial
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] miniroot 14 and current: vi is broken
Well actually on my live slackware 14 (x86) vi is a link to elvis Although both are installed, by default vi is linked to elvis (and it's not something I did manually). PACKAGE NAME: vim-7.3.645-i486-1 COMPRESSED PACKAGE SIZE: 5.2M UNCOMPRESSED PACKAGE SIZE: 24M PACKAGE LOCATION: /var/log/mount/slackware/ap/vim-7.3.645-i486-1.txz PACKAGE NAME: elvis-2.2_0-i486-2 COMPRESSED PACKAGE SIZE: 655.0K UNCOMPRESSED PACKAGE SIZE: 2.6M PACKAGE LOCATION: /var/log/mount/slackware/a/elvis-2.2_0-i486-2.txz looking at the sizes I cannot but agree that on the miniroot vim is just eating up space (just guessing that the arm packages will me more or less the same size) and on top of that there's 120Mb of dependencies to use it ! I remover the unused dependencies and added in elvis saving some 120Mb of disk space on the miniroot. Bye David Da: Stuart Winter m-li...@biscuit.org.uk A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Lunedì 15 Aprile 2013 17:52 Oggetto: Re: [ARMedslack] miniroot 14 and current: vi is broken On Mon, 15 Apr 2013, Davide wrote: I noticed that in the miniroot, both current and 14, vi is broken looking for libperl and libpython . I know most of you will like to use nano ... but I'm an old fart and I still like vi !!! Hmm. I'm going to replace vim with elvis as this works without bundling additional packages. -- Stuart Winter Slackware ARM: http://arm.slackware.com ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] miniroot 14 and current: vi is broken
I noticed that in the miniroot, both current and 14, vi is broken looking for libperl and libpython . I know most of you will like to use nano ... but I'm an old fart and I still like vi !!! It can be fixed by installing a few packages: perl-5.16.1-arm-1.tgz python-2.7.3-arm-2.tgz ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Merry Christmas
Merry Christmas and happy new year to everybody. David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Updating to 14.0 with kernel 2.6.38
I'm thinking of updating to 14.0 on my AC100 (that unfortunately still runs on ubuntu based kernel ... that I learn is actually a fork of chromeos kernel) ... Will things like udev break un kernel 2.6.28 ? Anyone think of anything else I should watcout for ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Updating to 14.0 with kernel 2.6.38
Ok it appears that a new package is mandatory for udev to do it's work. Actually I think it's mandatory for modprobe which in turn is mandatory for udev. Manually installing kmod package put things right. If I'd listened to slackpkg man page better by doing first slackpkg install-new probably things would have worked better. Sorry for making a racket ... and hope this can save trouble to other people updating. David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Venerdì 7 Dicembre 2012 15:09 Oggetto: Re: [ARMedslack] Updating to 14.0 with kernel 2.6.38 The odd thing is that I actually was already 14.0 but from a previous current. Indeed I had a few problems with udev and gnutls. It also took forever to get a login prompt (and not sure if CTRL^D/C helped killing something that was not working). Udev stopped working properly and I hadto load manually usb networking interface. I'm sure I;ll have more trouble ahead for this. While doing slackpkg upgrade n gnutl came before wget and then wget stopped working ... this stopped slackpkg from downloading anything Thankgod scp still worked and I was able to get the new whet installed to go on with the upgrade process. As soon as I'm done with the upgrading I'll try posting the udev error messages and see if anyone can help me put it right. Regards David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Venerdì 7 Dicembre 2012 12:36 Oggetto: [ARMedslack] Updating to 14.0 with kernel 2.6.38 I'm thinking of updating to 14.0 on my AC100 (that unfortunately still runs on ubuntu based kernel ... that I learn is actually a fork of chromeos kernel) ... Will things like udev break un kernel 2.6.28 ? Anyone think of anything else I should watcout for ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] fltk
Forgot the important thing: thanks a million Stuart. I'd been trying to compile 1.1.6 that just did not build on my ARM netbook. Thanks David Da: Stuart Winter m-li...@biscuit.org.uk A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Venerdì 23 Novembre 2012 11:47 Oggetto: Re: [ARMedslack] fltk slackbuilds.org has a few versions of fltk - perhaps you can compile it? http://slackbuilds.org/repository/14.0/libraries/fltk/ I'm in the giving mood ;-) http://armed.slackware.com/misc/ It got me thinking that it'd be great to have a set of the most commonly requested packages from SBo provided as binary for Slackware ARM 14.0, since compiling on most of the systems won't be ideal. I'm not sure how that'd work though (I'm not going to do it). ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] New Samsung Chromebook
Does anybody know which ARM processor it has and if it can potentially run Slackware ARM in a proper and easy way? Olof Johansson has just posted a way to install an alternative Linux distro on the new Chromebook: ttps://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ He has succeded with Suse just using the Suse root filesystem and the Chrome OS stock kernel. It looks like a complicated procedure (at least for me) and the catch is that it will boot from the Chrome partition, but I understand that he and other developers are working on booting from an external storage altogether. If anybody has any ideas on this subject they will do me a great favour. I have a limited budget. I was saving money to buy the new Genesi device which hasn't come yet but this little gem is tempting me now. Can't be much more difficult then any other arm platform: get a kernel that works for the hardware, get the tools to manipulate the kernel image so that the boot loader on the hardware will liad it (may need to package the initrd in there too), setup your initrd to look for whereever you plan to put the real root filesystem (that will contain whatever distro uou prefer) find a way of writing your boot image to the hardware (and root image if not on a removable media), cross your fingers and boot. Ciao David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware 14.0 is released
Thanks for all the effort you've been putting into ARM slackware port over the years. David Da: Stuart Winter mo...@slackware.com A: Slackware ARM mailing list armedslack@lists.armedslack.org Inviato: Venerdì 28 Settembre 2012 23:53 Oggetto: [ARMedslack] Slackware 14.0 is released Hi! Slackware x86, x86_64 and ARM v14.0 is released today. Instead of pasting the same content as the web site, you can read it here instead :-) http://www.armedslack.org/ Happy release day and have a good weekend upgrading Stuart.! -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] QEMU support - does anybody care about it?
I still find qemu useful when I want to test something out amd that qould be emulating ARM from x86 hardware. I know arm hardware is cheap nowadays ... but qemu is cheaper and no need to wait for shipping ;) Da: Stuart Winter mo...@slackware.com A: Slackware ARM mailing list armedslack@lists.armedslack.org Inviato: Venerdì 31 Agosto 2012 16:09 Oggetto: [ARMedslack] QEMU support - does anybody care about it? Hi I am thinking about removing the QEMU packages from -current. I only added these years ago because my real ARM hardware died and I needed a stop gap. The thing is that QEMU is *so slow* that I cannot imagine it being useful at all, apart from a 10 minute novelty for x86 users. It takes time to test whether the installation works, and takes time to build the Versatile kernel. Is anybody going to miss it if I drop the packages and install docs? -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
Last Saturday I did an update yo current again but I still can't get
libflashplayer to load on firefox.
Maybe I'm missing something else that's not showing as error when firefox
loads plugins.
Can you give me the output of ls /var/log/pasckages on the system where
you got libflashplayer to work ?
It's a full installation minus kdei.
I've got to finish up some other packages before reinstalling my dev box
again, then I'll try and see if it still works -- I suspect it does.
I'm guessing that your system is missing a feature that this library
wants
to use.
I suspect that too but the thing that's
bothering me on this thought is that I can't get firefox to tell me that
it cannot load the library and maybe give me a hint as to why.
Maybe
it's a several level nested library dep. and that's the reason it's not
showing ... but my slack installations install all the suggested
packages in the l section just to avoid this sort of problem.
I forgot if I did something different on my AC100 but I can fix that with
slackpkg install l.
Since I could not get any responce from firefox i tryed strace ... so here is a
grep of flash form the putput of strace:
lstat64(/usr/lib/firefox-13.0.1/plugins/libflashplayer.so,
{st_mode=S_IFLNK|0777, st_size=31, ...}) = 0
readlink(/usr/lib/firefox-13.0.1/plugins/libflashplayer.so,
../../plugins/libflashplayer.so..., 4095) = 31
lstat64(/usr/lib/plugins/libflashplayer.so, {st_mode=S_IFREG|0755,
st_size=8016428, ...}) = 0
stat64(/usr/lib/plugins/libflashplayer.so, {st_mode=S_IFREG|0755,
st_size=8016428, ...}) = 0that does not look bad to me ... but maybe I'm
mistaken ?
Now here's a grep of opens that return -1 :
openat(AT_FDCWD, /usr/lib/firefox-13.0.1/distribution/bundles,
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/usr/lib/charset.alias, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or directory)
open(/usr/lib/locale/locale-archive, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open(/usr/share/locale/en_US/LC_MESSAGES/messages.mo, O_RDONLY) = -1 ENOENT
(No such file or directory)
open(/usr/share/locale/en/LC_MESSAGES/messages.mo, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/share/locale/en_US/LC_MESSAGES/gtk20.mo, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/share/locale/en/LC_MESSAGES/gtk20.mo, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/share/locale/en_US/LC_MESSAGES/libc.mo, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/share/locale/en/LC_MESSAGES/libc.mo, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/share/locale/en_US/LC_MESSAGES/gtk20-properties.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/usr/share/locale/en/LC_MESSAGES/gtk20-properties.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/lib/tls/v7l/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open(/lib/tls/v7l/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/tls/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/tls/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/v7l/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/v7l/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/lib/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
open(/usr/lib/tls/v7l/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
open(/usr/lib/tls/v7l/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open(/usr/lib/tls/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open(/usr/lib/tls/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/usr/lib/v7l/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open(/usr/lib/v7l/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/usr/lib/vfp/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/usr/lib/libgnomeui-2.so.0, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
open(/usr/lib/firefox-13.0.1/updates/0/update.status, O_RDONLY|O_LARGEFILE) =
-1 ENOENT (No such file or directory)
open(/usr/lib/gconv/gconv-modules.cache, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/root/.Xdefaults, O_RDONLY) = -1 ENOENT (No such file or directory)
open(/root/.Xdefaults-slackware, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/root/.Xdefaults, O_RDONLY) = -1 ENOENT (No such file or directory)
open(/root/.Xdefaults-slackware, O_RDONLY) = -1 ENOENT (No such file or
directory)
Re: [ARMedslack] libflashplayer
What else could it be ? Dunno but you can try with the new -current updates once I push them out this week. Last Saturday I did an update yo current again but I still can't get libflashplayer to load on firefox. Maybe I'm missing something else that's not showing as error when firefox loads plugins. Can you give me the output of ls /var/log/pasckages on the system where you got libflashplayer to work ? Ciao David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
It is a can of worms. It is closed source and lets hope it's finished. Adobe don't fully support it and have publicly said so. I think it's much worse then a can of worms. I really don't understand why people use flash for things that do not need flash: why the hell should one use flash for authentication on a web site (on some sites if you don't have flash you cannot even see the box for typing the authentication) ! I feel pledged into using flash :-D If it wasn't that sometimes it's handy to watch video documentation (like for opening up a device without braking it) I'd have been happy to use swfdec for basic flash support. I tryed gnash but I was unable to deal with the dependencies for compiling it. Yes, Adobe has officially end-of-lifed Flash Player on Android: http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html Android really has only uses a modified linux kernel and has nothing else in common with any other linux distribution so when Adobe supported flash on mobile devices it never meant that Adobe supported flash on ARM linux devices. Cheers David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
It is a can of worms. It is closed source and lets hope it's finished. Adobe don't fully support it and have publicly said so. Yes, Adobe has officially end-of-lifed Flash Player on Android: http://blogs.adobe.com/flashplayer/2012/06/flash-player-and-android-update.html Not only on Android, but on Linux in general: http://tech.slashdot.org/story/12/02/22/1323204/adobe-makes-flash-on-gnulinux-chrome-only Adobe Flash will only be available as part of Google Chrome/Chromium. Can chrome/chromium run on armedslack and not loose the flash support ? A while back I attempted using chrome/chromium on x86 slackware but my experience was limiten in the ['could not compile' ... 'very bad user experience'] range, I seriously doubt that even now it could be any better then that on ARM but maybe I'm wrong ? Ciao David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
available in source code I don't see why people can assume one can just drop libflashplayer.so for Android and expect it to work and even if it did you'd open a can of worms. It does work - I tested it. I suspect it doesn't work for Davide because the library is compiled for a CPU higher than his own. This is what I ran it on: root@pepa:~/ac/source/kde# cat /proc/cpuinfo Processor : ARMv7 Processor rev 0 (v7l) processor : 0 BogoMIPS : 1987.37 processor : 1 BogoMIPS : 1993.93 Features : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x1 CPU part : 0xc09 CPU revision : 0 Hardware : trimslice Revision : Serial : root@pepa:~/ac/source/kde# That's odd: AC100 is a TEGRA2 (Tegra 250 T20) CORTEX-A9 based that only lacks NEON instruntions. Unless the library uses NEON instruntions (that I assume is not the sace or the android it came from would not run on any TEGRA2 based device) the most sensible guass I can make is that I need to enable some kernel options that were left off. Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
available in source code I don't see why people can assume one can just drop libflashplayer.so for Android and expect it to work and even if it did you'd open a can of worms. It does work - I tested it. I suspect it doesn't work for Davide because the library is compiled for a CPU higher than his own. This is what I ran it on: root@pepa:~/ac/source/kde# cat /proc/cpuinfo Processor : ARMv7 Processor rev 0 (v7l) processor : 0 BogoMIPS : 1987.37 processor : 1 BogoMIPS : 1993.93 Features : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x1 CPU part : 0xc09 CPU revision : 0 Hardware : trimslice Revision : Serial : root@pepa:~/ac/source/kde# That's odd: AC100 is a TEGRA2 (Tegra 250 T20) CORTEX-A9 based that only lacks NEON instruntions. Unless the library uses NEON instruntions (that I assume is not the sace or the android it came from would not run on any TEGRA2 based device) the most sensible guass I can make is that I need to enable some kernel options that were left off. I think I can exclude any kernel options as my cpuinfo only differs from that in Bogomibs and Hardware section ... BogoMIPS : 1992.29 ... BogoMIPS : 1992.29 ... Hardware : Toshiba AC100/ Dynabook AZ The rest is exactly the same. What else could it be ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
I've dropped this into /usr/lib/mozilla/plugins: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so And firefox about:plugins now says: === Shockwave Flash File: libflashplayer.so Version: Shockwave Flash 10.1 r120 MIME Type Description Suffixes application/x-shockwave-flash Shockwave Flash swf application/futuresplash FutureSplash Player spl === I did the same after upgrading to the mesa package below and now firefox no longer complains about not being able to load libflashplayer.so but none the less the plugin is not detected (I recently updated to current). I can watch a video on youtube x11vnc but I don't have a working native X at the moment as x/xf86-video-xgi-1.6.0-arm-3.tgz doesn't work with the new version of X and won't build yet. Give it a go. This package is built on the new -current so I don't know if it'll work on the one that's public at the moment (although I would imagine it will) http://armed.slackware.com/test/mesa-8.0.3-arm-2.tgz The src is here: http://armed.slackware.com/test/src/ All I've changed is: Added ./configure options: --with-gallium-drivers= nouveau r600 r300 svga --enable-gles1 --enable-gles2 --enable-openvg --enable-gallium-egl and removed --disable-egl Maybe the version of libflashplayer.so is incompatible with firefox 13 or maybe there is some other issue with the mesa package on current. What were you running on when you got things to work ? Regards David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
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@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
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] libflashplayer
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@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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] libflashplayer
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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!___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi
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.___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi
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=2t=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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Tegra kernel
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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@pepa:~/ac/source/k/configs# grep AC100 config-tegra root@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 ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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@pepa:~/ac/source/k/configs# grep AC100 config-tegra root@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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Tegra kernel
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello and questions about getting Slackware on the Raspberry Pi
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 galen...@gmail.com A: ArmedSlack armedslack@lists.armedslack.org 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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check!
I'd bet on ro missing on cmdline. -- Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: What does this output? cat /proc/cmdline If this is the case, go into u-boot and do: printenv and match the values found in /proc/cmdline and you should be able to identify which u-boot variable needs altering. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] sendmail problem
Looks like you've no resolver configured. Is your /etc/resolv.conf i empty ? Also google might regect mail coming directly from your host ... you might like to configure your ISP mail relay as SMART HOST in sendmail.mc ... and subsequently make clean , make all in the sendmail config directory. Regards David Da: Giovanni pino.o...@gmail.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Mercoledì 15 Febbraio 2012 17:37 Oggetto: [ARMedslack] sendmail problem I installed the mini root fs of slackware ARM 13.37 on the pandaboard and then the full installation (all packages, except KDE). The installation of all the packages is OK. But I found a problem when I try to send an email, by using the sendmail. sendmail is up and running: root 15973 0.0 0.4 7912 2020 ? Ss Feb06 0:02 sendmail: accepting connections smmsp 15976 0.0 0.3 7284 1532 ? Ss Feb06 0:00 sendmail: Queue runner@00:25:00 for /var/spool/clientmqueue if I try to send a mail with the command: echo prova | mail -s test pino.o...@gmail.com I get the following error in the file /var/log/maillog: Feb 7 06:24:43 slackware sendmail[22802]: e176OhJw022802: from=root, size=216, class=0, nrcpts=1, msgid=22070624.e176OhJw022802@slackware.localdomain, relay=root@localhost Feb 7 06:24:44 slackware sm-mta[22803]: e176OhFi022803: from=root@slackware.localdomain, size=467, class=0, nrcpts=1, msgid=22070624.e176OhJw022802@slackware.localdomain, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Feb 7 06:24:44 slackware sendmail[22802]: e176OhJw022802: to=pino.o...@gmail.com, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30216, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (e176OhFi022803 Message accepted for delivery) Feb 7 06:24:44 slackware sm-mta[22805]: STARTTLS=client, relay=gmail-smtp-in.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-SHA, bits=128/128 Feb 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: to=pino.o...@gmail.com, ctladdr=root@slackware.localdomain (0/0), delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=120467, relay=gmail-smtp-in.l.google.com. [173.194.65.26], dsn=5.0.0, stat=Service unavailable Feb 7 06:24:45 slackware sm-mta[22805]: e176OhFi022803: e176OjFi022805: DSN: Service unavailable Feb 7 06:24:46 slackware sm-mta[22805]: e176OjFi022805: to=root@slackware.localdomain, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=31686, dsn=2.0.0, stat=Sent Is there any special configuration to do, in order to get the sendmail working on Slackware ARM? Best regards, giovanni ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] How to install full Slackware from mini root file system
Generally I do this by hand by installing what I require as I find missing functionality. But as a starting guide you might want to get networking working and slackpkg working: n/dhcpcd-5.2.11-i486-1.txz n/ethtool-2.6.36-i486-1.txz n/inetd-1.79s-i486-8.txz n/iptables-1.4.10-i486-1.txz n/iputils-s20101006-i486-1.txz n/iw-0.9.20-i486-1.txz n/links-2.3pre1-i486-1.txz n/network-scripts-13.0-noarch-3.txz n/nmap-5.51-i486-1.txz n/openssh-5.8p1-i486-1.txz n/wget-1.12-i486-1.txz n/wireless-tools-29-i486-6.txz n/wpa_supplicant-0.7.3-i486-3.txz ap/slackpkg-2.82.0-noarch-5.tgz Then setup slackpkg to point to the repository you wish, and run slackpkg update ... from there getting the rest will be very easy and fast when you need it: slackpkg install package base name or even get prompted for a wole set of packages slackpkg install n Have fun Davide Da: Giovanni pino.o...@gmail.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Lunedì 13 Febbraio 2012 10:27 Oggetto: [ARMedslack] How to install full Slackware from mini root file system I have installed Slackware ARM 13.37 on a pandaboard successfully. Now I would like to install the full version (all packages), starting from the working minimal installation. I already downloaded the slackware ARM tree via rsync directly on the pandaboard. What is the suggested way to install all the packages? Best regards, giovanni ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug
I may be mixing up memories from Zaurus and dockstar. But I remember that on one of these if one forgot to erase the flash partition where the kernel was about to be written next boot would fail. But I may be putting you of with this. Sorry for any inconvinience. Da: Jim Hammack hamm...@gotslack.org A: armedslack@lists.armedslack.org Inviato: Giovedì 9 Febbraio 2012 16:20 Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug Davide, I'm not sure what you mean by erasing the partition. I am using these commands taken from INSTALL_KIRKWOOD.TXT: setenv arcNumber 2659 setenv mainlineLinux yes setenv ipaddr 192.168.2.1 setenv serverip 192.168.2.7 saveenv reset usb start tftpboot 0x0110 armedslack-13.37/uinitrd-kirkwood.img tftpboot 0x0080 armedslack-13.37/uImage-kirkwood setenv bootargs console=ttyS0,115200 nodhcp kbd=us root=/dev/ram rw bootm 0x0080 0x0110 *** install armedslack and reboot *** setenv bootargs_console console=ttyS0,115200 setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4' setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset' setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x0110 /uinitrd-kirkwood;ext2load usb 0:1 0x0080 /uImage-kirkwood;bootm 0x0080 0x0110' setenv ethaddr F0:AD:4E:00:E5:BD setenv eth1addr F0:AD:4E:00:E5:BE saveenv reset Thanks, Jim On 02/09/2012 02:38 AM, Davide wrote: If you can boot the image via tftp but subsequently not from flash then maybe it war not flashed correctly. Are you erasing partition before writing kernel to it ? Da: Jim Hammack hamm...@gotslack.org A: armedslack@lists.armedslack.org Inviato: Giovedì 9 Febbraio 2012 3:36 Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug Brennan, Thanks for the suggestion, but I downloaded the files again and made sure they were binary transfers, and still no luck. I also downloaded armedslack-current (I had the original armedslack-13.37 that I used on my sheevaplug) but still no change. I'm confused because the kernel boots after the initial tftpboot and I can install software, configure the system, etc., but when I try to reboot the system hangs. Jim On 02/06/2012 08:32 PM, Brennan Newman wrote: Jim, I had this same issue and it was driving me crazy, it is a simple fix (at least for me). Simply re-download the kernel images and make sure that you are transferring it over in binary. I had used Filezilla to get my install and it was set to transfer all files in ascii by default which according to many people in the world today mangles binary files pretty badly. Hope this helps. Brennan On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack hamm...@gotslack.org wrote: I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XX) by following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but have been unable to get the system to boot. I believe it is due to a problem with my u-boot which I scrambled earlier. I have been able to find only one version of u-boot that will run on this machine (the guruplug version from http://www.armedslack.org/maint_kirkwooduboot loads but hangs after a 'reset'). This one works: Marvell version U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57) Marvell-DreamPlug armv5tel-softfloat-linux-gnueabi-gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) 4.4.4 GNU ld (GNU Binutils) 2.20.1.20100303 I am following Stuart's instructions with two exceptions: 1. I am using dream-2.6.38.4-uImage (renamed uImage-kirkwood) from with-linux instead of uImage-kirkwood from the distribution due to a known problem with uImage-kirkwood on the Dreamplug. (http://lists.armedslack.org/2011-August/000978.html) 2. I am using a fat16 boot partition rather that the ext2 partition Stuart uses in his documentation, so I have changed all references to ext2load to fatload in the bootcmd The system loads uinitrd-kirkwood okay, then loads uImage-kirkwood (which is really dream-2.6.38.4-uImage), but hangs after: Uncompressing Linux... done, booting the kernel. I don't think this is the problem, but does anyone see any problems with my u-boot variables? Also, I've read that newer
Re: [ARMedslack] Cant get -current 3.1.5 to boot
Have not yet fiddled with new 3.x.x kernels yet but experience forced me to be carefull wneb copying .config's across releases. Using 2.6.38.1 config on 2.6.38.x was possible but using 2.6.38.x confin on 2.6.39.x would produce unexpected results. (38 and 39 ar just examples coz I've forgotten the names of each number) Da: John O'Donnell unixjohn1...@gmail.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Domenica 1 Gennaio 2012 9:29 Oggetto: [ARMedslack] Cant get -current 3.1.5 to boot I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before attempting to compile the guruplug UAP drivers I tried to boot and had no luck. Hung at: -- ## Booting kernel from Legacy Image at 0080 ... Image Name: Linux-3.1.5-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2090424 Bytes = 2 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: Slackware ARM Initial RAM disk f Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5811263 Bytes = 5.5 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. I compiled up the modules and my own uImage with the .config that comes with the armedslack kernel source and the same thing happens. I set it back to 3.1.2 and it boots fine. John Oh yeah - Happy New Year ;-) === Never ask a geek why, just nod your head and slowly back away.=== ++==+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1...@gmail.com | ++==+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Compiling mame fro ARM
Way back in 2006 I had a working xmame for my Z that even if a little slowly it worked. Since then xmame has been dropped and original mame now builds on unix. I've built mame0143 on my x86 linux pc but I've had no luck on ARM. The old xmame sources build but produce a binary that complains about endianness while I was unable to compile normal mame on ARM. I tryed fiddling with CFLAGS to force little endian but it did no better. I've totally forgotten whatever I did way back in 2006. Anyone have any idea ? Regards David___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Video playback on AC100
I'll try ... I'm already using ununtu kernel sources to get a working kernel. I'll surf around ubuntu forums and what more on this then. Nowadays video card modules are in xorg not (only) in kernel modules. Grep your /var/log/Xorg.0.log for not found. root@slackware:~# grep -i not found /var/log/Xorg.0.log root@slackware:~# If I start attempting to show a video nothing shows up on the X0msgs but I get about 1 frame every 2 seconds. I also haveto use -ao null or I get complains about: [AO OSS] Can't set auduo device /dev/dsp ro s16le output OK I have it now ... not sure why it defaults to OSS while my kernel has alsa so this got just the audio part working on the headphones: mplayer -ao alsa -vo null whatever video Aha another thing got much better framerate: mplayer -ao alsa -vo fbdev whatever video this produces no window around the video output, a horrible info box on the bottom and leaves s mess after video is finished but has acceptable framerate ! Maybe I can set some better defaults in ~/.mplayer/config and not haveto remember this stuff every time :-) This is even better as framerate is ok but it leaves no mess and no info box: mplayer -ao alsa -vo x11 whatever video Xine does no better on video playback as it crashes shortly after starting: root@slackware:~# xine This is xine (X11 gui) - a free video player v0.99.5. (c) 2000-2007 The xine Team. X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 62 (X_CopyArea) Serial number of failed request: 4558 Current serial number in output stream: 4563 root@slackware:~# Not sure if this is because I'm missing some requisite but the output is not much help in debugging. I'll stick to mplayer -ao alsa -vo x11 whatever video for the moment :-D___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Video playback on AC100
The other day I installed mplayer on my AC100 ... but the video playback was desparately slow. I'm not sure if it's the Framebuffer X or some other issue .. Just guessing: most likely some proprietary video card binary blob that doesn't come with Slackware but comes with the default OS (Android I think). See if you can get it from horror Ubuntu. Because they are part of Linaro they usually can licence blobs that other distros can't (it's sad though...). I'll try ... I'm already using ununtu kernel sources to get a working kernel. I'll surf around ubuntu forums and what more on this then. Another thing I just compiled latest ubuntu 2.6.38-100.1 that states working audio in the headphones but I can't see to get any oudio out of the damn thing anyway Ciao Davide___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Fwd: Re: iOmega iConnect
I know I'm not the right Dave :-D I thought that google would have the answer for this bit apparently there's no correct answer: I got this as an intresting hit form Jeff Doozan's forum There is no common arcNumber: - iomega uses 1682 - OpenWRT uses 2870 - Debian asm/mach-types.h does not list any reference to the iconnect. So it is really unsupported. None of the kirkwood arcNumbers listed in Debian results in a functional network. In OpenWRT is a patch that made the GBit network working (arcNumber=2870). But the OpenWRT kernel is not able to read or write the flash correctly. My guess is that it depends on the kernel you are using. Regards David Da: Greg Lim sunsm...@gmail.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Domenica 25 Settembre 2011 22:27 Oggetto: Re: [ARMedslack] Fwd: Re: iOmega iConnect Dave, I finally got around to unboxing my iConnect. I can boot into the ArmedSlack installer, but I have no ethernet. I'm guessing that I have the wrong arcNumber. Can you tell us what the correct arcNumber is for the iConnect running on the ArmedSlack 13.37 kernel so that ethernet works? Here's what I've tried: 2870 - doesn't boot. added by someone Matrin Michlmayr on May 2010. 1682 - boots. no ethernet once booted into the install system, but ifconfig appears to show the correct ethernet addresses of both the wireless and 1GB-wired interfaces. 2097 - sheevaplug - interface missing. can't bring up 2678 - sheevaplug - esata - interface missing. can't bring up -Greg Lim On Wed, Jul 20, 2011 at 11:42 AM, Dave Dowell dowe...@netscape.net wrote: Hello again, OK I've started putting some information about this up now. http://www.dowelld.net/viewtopic.php?f=1t=3 Thanks Dave Original Message Subject: Re: [ARMedslack] iOmega iConnect Date: Fri, 01 Jul 2011 21:49:04 +0100 From: Dave Dowell dowe...@netscape.net To: armedslack@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 dowe...@netscape.net 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
Re: [ARMedslack] Flash Plugin for ARM
Some info got lost somewhere: You said that it would not run on my cpu because my cpu is armv5 while the library could be compiled for armv7 and I replied that that's not correct as the ac100 has an armv7 instruction set capable cpu: maybe the armedslack userland makes that binary unusable for some other reason. Da: Stuart Winter m-li...@biscuit.org.uk A: armedslack@lists.armedslack.org Inviato: Mercoledì 14 Settembre 2011 15:10 Oggetto: Re: [ARMedslack] Flash Plugin for ARM On Wed, 14 Sep 2011, Davide wrote: That's not correct: AC100 has a tegra2 which is cortex-A9 based (ARMv7). Bust be a library issue then. I'm not sure what you mean here -- I said it's probably compiled for armv7 which is what you say the CPU is. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Flash Plugin for ARM
It's possible to hack libflashplugin.so out of android apk (just rename the .apk in .zip). This way you can have flash support on armedslack. Fetch the android flash plugin from here: http://androidadvices.com/wp-content/uploads/2011/03/Adobe-Flash-10.2.zip This way you don't need to be in TI's grace to get it. Ok it won't play recent youtube videos but it's better then nothing at all or attempting to build gnash. Regards David Da: Ottavio pr0f3ss0r1...@yahoo.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Martedì 6 Settembre 2011 15:49 Oggetto: Re: [ARMedslack] Flash Plugin for ARM On 6 September 2011 11:41, Davide louigi...@yahoo.it wrote: Is anyone aware of easier ways of getting flash plugin for linux on ARM ? How about gnash or any of the opensource alternatives ? I have seen on the power developer website a screenshot of a user with a Genesi machine with Gnash installed and playing Youtube: http://www.gnashdev.org/images/IMGP2573.JPG -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Flash Plugin for ARM
I remember that I specifically disabled old ABI support on my kernel build. Not sure if android bins are eabi or old abi. Mayby someone can try this out on an old abi enabled kernel ? Da: Davide louigi...@yahoo.it A: Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org; Slackware ARM port armedslack@lists.armedslack.org Inviato: Martedì 13 Settembre 2011 13:21 Oggetto: Re: [ARMedslack] Flash Plugin for ARM False allarm ... the one for android does not work on armedslack. Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Martedì 13 Settembre 2011 13:14 Oggetto: Re: [ARMedslack] Flash Plugin for ARM It's possible to hack libflashplugin.so out of android apk (just rename the .apk in .zip). This way you can have flash support on armedslack. Fetch the android flash plugin from here: http://androidadvices.com/wp-content/uploads/2011/03/Adobe-Flash-10.2.zip This way you don't need to be in TI's grace to get it. Ok it won't play recent youtube videos but it's better then nothing at all or attempting to build gnash. Regards David Da: Ottavio pr0f3ss0r1...@yahoo.com A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Martedì 6 Settembre 2011 15:49 Oggetto: Re: [ARMedslack] Flash Plugin for ARM On 6 September 2011 11:41, Davide louigi...@yahoo.it wrote: Is anyone aware of easier ways of getting flash plugin for linux on ARM ? How about gnash or any of the opensource alternatives ? I have seen on the power developer website a screenshot of a user with a Genesi machine with Gnash installed and playing Youtube: http://www.gnashdev.org/images/IMGP2573.JPG -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] xlock problem
This happens on my AC100 running armedslack 13.37 (updated a few days ago). Any idea how to fix this ? Not yet. Are you running it locally or via VNC ? I can't replicate this on -current running X on the console (locally - video, kb, mouse). xlock asks for a key, locks and then asks for the password to unlock. Yea I know that's the way it should be and with root it works ... but with non privileged user the only password that is working is just hitting ENTER. Any other text (including the correct password) does not work. I'm suspecting I've an issue somewhere on my system as for root it's working fine. This works for a non-root user. Unfortunately my 13.37 machine is headless so I can't test. What version were you trying to reproduce this on ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Flash Plugin for ARM
While looking for Flash plugin for ARM linux I found this: http://www.ti.com/tool/adobeflash-a8 Not sure if there is an easier way to get Flash plugin on ARM linux. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] R: R: Armedslack on the AC100
I should read messages from the top down :-D Ok I'll be installing that later. Thanks David --- Dom 4/9/11, Stuart Winter m-li...@biscuit.org.uk ha scritto: Da: Stuart Winter m-li...@biscuit.org.uk Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Domenica 4 settembre 2011, 21:49 root@wizbit:~/ac/source/xap/mozilla-thunderbird# grep fbdev_drv /var/log/packages/* /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.la /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.so ftp://ftp.armedslack.org/armedslack/armedslack-current/slackware/x/xf86-video-fbdev-0.4.2-arm-2.tgz ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] R: R: Armedslack on the AC100
On I made sure the correct window manager was coming op beause I realized that it was an xterm startup attempt that made it all crash (probabbly twm was started up or even worse just X with a term). Using fluchbos alone got X and window manager up and running but still cannot start any sort of terminal though. So I've still an issue as to why there are no ptys in /dev. Anu ideas how to fix this ? Regards David --- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto: Da: Davide louigi...@yahoo.it Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Lunedì 5 settembre 2011, 10:02 Ok I installed that and a few other bits I missed out while compleating the miniroot. Still cannot get gui to start up. Tjis time I get an error complaining that there are not enough ptys. Well actually there are none in /dev ! And in any case ls /dev only fills 1/2 a screen of stuff which looks like a lot of other files are missing to. Udev seems to be running though ? Any ideas ? Regards David --- Dom 4/9/11, Stuart Winter m-li...@biscuit.org.uk ha scritto: Da: Stuart Winter m-li...@biscuit.org.uk Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Domenica 4 settembre 2011, 21:49 root@wizbit:~/ac/source/xap/mozilla-thunderbird# grep fbdev_drv /var/log/packages/* /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.la /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.so ftp://ftp.armedslack.org/armedslack/armedslack-current/slackware/x/xf86-video-fbdev-0.4.2-arm-2.tgz ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] R: R: Armedslack on the AC100
Ok maybe I've worked out the cause: looks like devpts needs to be mounted. mkdir /dev/pts mount -n -o mode=0620,gid=5 -t devpts devpts /dev/pts Mounting it manually gets xterm going. Actyally I grepped the mount out of rc.udev so I'll try to figure out why it's not workin. The other odd thing is that before mounting manually I can grep devpts out of /proc/mounts. I wonder if it's normal ot if it's a resedue from initrd ? Well whatever ... it looks like the check_mounted function at the top of rc.udev is using /proc/mouns to detect if something is mounted ... but the content in it seems wrong. To temporarely work around the problem I commented the check and blind make and mount /dev/pts in rc.udev. Regards David --- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto: Da: Davide louigi...@yahoo.it Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Lunedì 5 settembre 2011, 11:26 I had a look at how ubuntu on the AC100 is working: the terminals are associated to /dev/pts/? instead of /dev/ptyp? Can I do the same ? Regards David --- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto: Da: Davide louigi...@yahoo.it Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Lunedì 5 settembre 2011, 10:17 On I made sure the correct window manager was coming op beause I realized that it was an xterm startup attempt that made it all crash (probabbly twm was started up or even worse just X with a term). Using fluchbos alone got X and window manager up and running but still cannot start any sort of terminal though. So I've still an issue as to why there are no ptys in /dev. Anu ideas how to fix this ? Regards David --- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto: Da: Davide louigi...@yahoo.it Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Lunedì 5 settembre 2011, 10:02 Ok I installed that and a few other bits I missed out while compleating the miniroot. Still cannot get gui to start up. Tjis time I get an error complaining that there are not enough ptys. Well actually there are none in /dev ! And in any case ls /dev only fills 1/2 a screen of stuff which looks like a lot of other files are missing to. Udev seems to be running though ? Any ideas ? Regards David --- Dom 4/9/11, Stuart Winter m-li...@biscuit.org.uk ha scritto: Da: Stuart Winter m-li...@biscuit.org.uk Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Domenica 4 settembre 2011, 21:49 root@wizbit:~/ac/source/xap/mozilla-thunderbird# grep fbdev_drv /var/log/packages/* /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.la /var/log/packages/xf86-video-fbdev-0.4.2-arm-2:usr/lib/xorg/modules/drivers/fbdev_drv.so ftp://ftp.armedslack.org/armedslack/armedslack-current/slackware/x/xf86-video-fbdev-0.4.2-arm-2.tgz ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Armedslack on the AC100
I got round to doing some testing with an ubuntu kernel (2.6.38.1). With this kernel I was able to get the basics working chrooted. There are still some issues with kernel even with all the AC100 specific pathes applied: no sound, keyboard/touchpad often reset and sometimes crash in a way that will require a reboot to get things working again. Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] R: Logitech Squeezebox Touch
Put this in a google search bar: Logitech Squeezebox Touch hack ... did not look at the content but it looks like there are communities for this hardware. Regards David --- Gio 1/9/11, Thorsten Mühlfelder thenk...@gmail.com ha scritto: Da: Thorsten Mühlfelder thenk...@gmail.com Oggetto: [ARMedslack] Logitech Squeezebox Touch A: armedslack@lists.armedslack.org Data: Giovedì 1 settembre 2011, 18:14 Hi, I wonder if there is any information how to change the OS on a Logitech Squeezebox Touch?According to this blog it's an ARM based device running Linux:http://blog.sarine.nl/2010/09/30/squishybox-a-better-squeezebox-touch-experience/ https://github.com/DaveDavenport/squishybox/wiki/SqueezeBox-Touch GreetingsThorsten -Segue allegato- ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] R: Armedslack on the AC100
Although CONFIG_KEXEC is set on the ubuntu 2.6.38 kernel I was unable to boot any other kernel. I then tryed to manipulate the initrd so that I could boot armedslack and that worked. If anyone is intrested I've a image ready to be nvflashed to partition 5 that boots armedslack from /dev/mmcblk0p7 (the onboard big partition). Regards David --- Dom 4/9/11, Davide louigi...@yahoo.it ha scritto: Da: Davide louigi...@yahoo.it Oggetto: [ARMedslack] Armedslack on the AC100 A: Slackware ARM port armedslack@lists.armedslack.org Data: Domenica 4 settembre 2011, 10:48 I got round to doing some testing with an ubuntu kernel (2.6.38.1). With this kernel I was able to get the basics working chrooted. There are still some issues with kernel even with all the AC100 specific pathes applied: no sound, keyboard/touchpad often reset and sometimes crash in a way that will require a reboot to get things working again. Regards David -Segue allegato- ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
