From unixjohn1969 at gmail.com Thu Oct 7 22:58:26 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 07 Oct 2010 18:58:26 -0400 Subject: [ARMedslack] Trying armedslack-current In-Reply-To: References: Message-ID: <4CAE5092.5060909@gmail.com> To make a long story . . . long . . . I got my recompiled u-boot to recognize the micro SD card slot and boot off of it. So instead of running my GuruPlug from a USB dongle with a 4 GB SD card I bought an 8gb micro to run the system. So I am re-installing and testing with the latest stuff! I can boot from USB and now the micro SD onboard. The patch to u-boot changed the way in which the onboard device sorted out LUN access and now it shows up properly and now I can boot off the onboard micro SD card as there are really 2 devices there with only one physically present. http://plugcomputer.org/plugforum/index.php?topic=1642.30 I run X windows from the Guru to my main Linux machine as display :2. :1 is for my second X display for World of Warcraft. :0 is my Slack KDE desktop. I only have a single core CPU on my desktop. I wanted to offload my Bittorrents off to the GuruPlug that also runs my wifi network for my android phone and occasionally other friends laptops, etc. It had been helping ALOT and working GREAT with 13.1 armedslack running Ktorrent remote NFSed to my main system saving all the data. So I run the entire KDE desktop from the Guru every day displaying on my desktop PC. I cannot run either of the dual gigabit ports on the GuruPlug because of the known overheating/rebooting issues. (BAD BAD MARVELL!) I have to plug in a USB/ethernet to get me network access. It's sad, but it works. I so wish Marvell could fix the overheating issue so I could remove all this dangling crap! http://mrlinux.homelinux.com/guruplug/myguru.jpg I ran into an issue with the kernel in -current. It seems the guru kernel patches to include the wireless AP functionality are missing. I cannot bring up the uap8xxx driver. Reference: http://lists.debian.org/debian-arm/2010/05/msg00081.html root at guruslack:/mnt/memory/usr/src/linux# modprobe uap8xxx FATAL: Module uap8xxx not found. root at guruslack:/mnt/memory/usr/src/linux# uname -a Linux guruslack 2.6.35-kirkwood #2 PREEMPT Wed Aug 4 17:01:31 BST 2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell GuruPlug Reference Board GNU/Linux yet in 13.1 it is working fine. root at guruslack:~# modinfo uap8xxx filename: /lib/modules/2.6.33.5-kirkwood/kernel/drivers/net/wireless/libertas_uap/uap8xxx.ko.gz license: GPL version: 26146 author: Marvell International Ltd. description: M-UAP Driver srcversion: A1CB6539A717ACCA9F3C0E8 alias: sdio:c*v02DFd9104* depends: mmc_core vermagic: 2.6.33.5-kirkwood preempt mod_unload modversions ARMv5 parm: helper_name:Helper name (charp) parm: fw_name:Firmware name (charp) root at guruslack:~# uname -a Linux guruslack 2.6.33.5-kirkwood #2 PREEMPT Thu May 27 14:47:11 BST 2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell GuruPlug Reference Board GNU/Linux -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Fri Oct 8 07:19:09 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 8 Oct 2010 08:19:09 +0100 (BST) Subject: [ARMedslack] Trying armedslack-current In-Reply-To: <4CAE5092.5060909@gmail.com> References: <4CAE5092.5060909@gmail.com> Message-ID: > out LUN access and now it shows up properly and now I can boot off the > onboard micro SD card as there are really 2 devices there with only one > physically present. > > http://plugcomputer.org/plugforum/index.php?topic=1642.30 Is it worth taking this u-boot and putting it on ftp.armedslack.org then? I have a guruplug u-boot that I took from a Debian developer's page. If we take this one, do the Slackware ARM Kirkwood installation instructions still apply? > for my second X display for World of Warcraft. :0 is my Slack KDE desktop. I > only have a single core CPU on my desktop. That's a good idea. I hadn't thought of that before. I usually run X11 VNC on the ARM boxes and VNC in to test x11 stuff. Although I plan on using the openrd as a desktop machine soon, since it has video and audio working (we just need some x.org updates first, to get a decent screen resolution). > I cannot run either of the dual gigabit ports on the GuruPlug because of > the known overheating/rebooting issues. (BAD BAD MARVELL!) I have to I know Jim on this list has received his guruplug a week ago, and they've added a whopping fan to it which makes itself known in the room. Perhaps you shoud send yours back for a swap. > FATAL: Module uap8xxx not found. > root at guruslack:/mnt/memory/usr/src/linux# uname -a > Linux guruslack 2.6.35-kirkwood #2 PREEMPT Wed Aug 4 17:01:31 BST 2010 > armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell GuruPlug Reference Board > GNU/Linux > > yet in 13.1 it is working fine. There were a number of patches to the 13.1 kernel: armedslack-13.1/source/k/sources/patches/esata_sheevaplug_and_guruplug-patchset but as far as I knew, all of the guru plug stuff was merged into the upstream kernel: At present, I don't apply *any* patches to the -current kernel (which is waiting to be pushed out after Slackware x86 has been) The module does not exist in the source tree. root at wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' root at wizbit:/usr/src/linux-2.6.36rc7# I checked the Debian linux-base package which is at 2.6.36rc6 and there are no guruplug patches in it. I remember talking with a Guru owner who needed some firmware for the onboard bluetooth stuff, but I don't recall anything mentioned about the network drivers. If there are any patches, I can add them into the next kernel build; if someone tells me where they are. -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Fri Oct 8 08:20:29 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 08 Oct 2010 04:20:29 -0400 Subject: [ARMedslack] Trying armedslack-current In-Reply-To: References: <4CAE5092.5060909@gmail.com> Message-ID: <4CAED44D.6020002@gmail.com> On 10/08/2010 03:19 AM, Stuart Winter wrote: > >> out LUN access and now it shows up properly and now I can boot off the >> onboard micro SD card as there are really 2 devices there with only one >> physically present. >> >> http://plugcomputer.org/plugforum/index.php?topic=1642.30 > > Is it worth taking this u-boot and putting it on ftp.armedslack.org then? > I have a guruplug u-boot that I took from a Debian developer's page. > > If we take this one, do the Slackware ARM Kirkwood installation > instructions still apply? Same instructions apply as a USB drive. It is a VERY clean patch, probably worth adding. I changed the version name and the prompt from Marvell to GuruPlug. I changed nothing else. >> for my second X display for World of Warcraft. :0 is my Slack KDE desktop. I >> only have a single core CPU on my desktop. > > That's a good idea. I hadn't thought of that before. I usually run > X11 VNC on the ARM boxes and VNC in to test x11 stuff. > Although I plan on using the openrd as a desktop machine soon, since it > has video and audio working (we just need some x.org updates first, to get > a decent screen resolution). Doesn't KDE have a sound server? I am planning on trying it out from the guru to my desktop after I get all this smoothed out with the -current tree. I Just got it all back up and running on -current but with the 13.1 version kernel install (kernel / modules / source) totally booting off the micro SD card. It is bittorrenting as I type again and running very smoothly. It is quite nice. Seems a bit more sluggish but then I was doing alot of package changes while trying to shuffle bittorrents. I made sure to buy a fast rated micro SD card. I have always run multiple X servers for many reasons. While working for the Dept of Defense, I had my windoze laptop (assigned to me - UGH!) that I could not change. But they gave us VMware!!! So alas it ran nothing but VMware . . . with Slackware in full screen all day long with an X console for my HP/ux PA Risc developement system, one for the Sun Sparc box, etc. etc. etc... I just use the GuruPlug in the same fashion. >> I cannot run either of the dual gigabit ports on the GuruPlug because of >> the known overheating/rebooting issues. (BAD BAD MARVELL!) I have to > > I know Jim on this list has received his guruplug a week ago, and they've > added a whopping fan to it which makes itself known in the room. > Perhaps you shoud send yours back for a swap. Oh I have been following the forums and been in contact with Global Scale and know all about that little 20mm x 20mm x 6mm fan they added that is apparently quite noisy. I guess I should have said "BAD BAD GLOBAL SCALE!" > There were a number of patches to the 13.1 kernel: > armedslack-13.1/source/k/sources/patches/esata_sheevaplug_and_guruplug-patchset > but as far as I knew, all of the guru plug stuff was merged into > the upstream kernel: > > At present, I don't apply *any* patches to the -current kernel > (which is waiting to be pushed out after Slackware x86 has been) > > The module does not exist in the source tree. > root at wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' > root at wizbit:/usr/src/linux-2.6.36rc7# > > I checked the Debian linux-base package which is at 2.6.36rc6 and > there are no guruplug patches in it. > > I remember talking with a Guru owner who needed some firmware for the > onboard bluetooth stuff, but I don't recall anything mentioned about the > network drivers. If there are any patches, I can add them into the next > kernel build; if someone tells me where they are. > It is mentioned several times in the forums that for the GuruPlug you need to copy the binary /usr/bin/uaputl from a shipped guruplug. I had to do the same as well with the /lib/firmware/mrvl files. I added them to http://juanisan.homeip.net/guruplug as well as my /etc/rc.d/rc.uap and /etc/rc.d/rc.dhcpd The GuruPlug is weird in that you have to start UAP and restart again once to get it fully functioning upon booting. The debian install does the same thing. But once done like that on boot it functions flawlessly. From what I follow, there apparently are NO sources available to this uaputl program and I am VERY dubious of this. I have also read that there are NO access controls and that you DONT have to be root to change the SSID or any other access point configurations with this utility and the way it talks to the kernel driver. I dont like it but it is what I have to use. Just be aware of all this and decide what you want to include. While typing this, Ktorrent Sig 11'ed. I have had issues with Ktorrent crashing, but usually not when left alone. In 13.1 sometimes it would work flawlessly. Open a torrent, start downloading, open another, etc.. And work to completion. Sometimes I would boot the plug and open a torrent, crash with sig 11, restart, it recovers and starts downloading, open another, crash sig 11, restart, downloads to completion. it only crashed on an open. few days later reboot the plug and it doesnt crash at all... A few days later, just crashes on an open and repeat the cycle. This is the first time (with -current) it crashed while downloading unattended. Keeping an eye on this. When it crashes I get the KDE dialog box telling me why it crashed and if I want to restart the application. I just click "restart" then "close". I NEED all of this to get my fix of Top Gear, Torchwood, Dr. Who and Spooks afterall!!!! :-P Go GuruPlug! GO! -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From jawkins at armedslack.org Fri Oct 8 08:40:37 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Fri, 8 Oct 2010 09:40:37 +0100 (BST) Subject: [ARMedslack] Trying armedslack-current In-Reply-To: <4CAED44D.6020002@gmail.com> References: <4CAE5092.5060909@gmail.com> <4CAED44D.6020002@gmail.com> Message-ID: On Fri, 8 Oct 2010, John O'Donnell wrote: > On 10/08/2010 03:19 AM, Stuart Winter wrote: > > I know Jim on this list has received his guruplug a week ago, and they've > > added a whopping fan to it which makes itself known in the room. > > Perhaps you shoud send yours back for a swap. > > Oh I have been following the forums and been in contact with Global Scale and > know all about that little 20mm x 20mm x 6mm fan they added that is apparently > quite noisy. I guess I should have said "BAD BAD GLOBAL SCALE!" It sounds like a hair dryer. > From what I follow, there apparently are NO sources available to this uaputl > program and I am VERY dubious of this. I have also read that there are NO > access controls and that you DONT have to be root to change the SSID or any > other access point configurations with this utility and the way it talks to > the kernel driver. I dont like it but it is what I have to use. I've not looked at it, but source is available from the bottom of this page: http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_WiFi_Access_Point Cheers, Jim From unixjohn1969 at gmail.com Fri Oct 8 08:50:26 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 08 Oct 2010 04:50:26 -0400 Subject: [ARMedslack] Trying armedslack-current In-Reply-To: References: <4CAE5092.5060909@gmail.com> <4CAED44D.6020002@gmail.com> Message-ID: <4CAEDB52.7060107@gmail.com> On 10/08/2010 04:40 AM, Jim Hawkins wrote: > On Fri, 8 Oct 2010, John O'Donnell wrote: > >> On 10/08/2010 03:19 AM, Stuart Winter wrote: >>> I know Jim on this list has received his guruplug a week ago, and they've >>> added a whopping fan to it which makes itself known in the room. >>> Perhaps you shoud send yours back for a swap. >> >> Oh I have been following the forums and been in contact with Global Scale and >> know all about that little 20mm x 20mm x 6mm fan they added that is apparently >> quite noisy. I guess I should have said "BAD BAD GLOBAL SCALE!" > > It sounds like a hair dryer. YUCK! Yeah I was googling alot last night about a replacement fan that might be quieter but not alot in that extremely small form factor. Still looking. And waiting for Global Scale to let me know when and how to get my plug fixed. They just keep telling me they will contact me. >> From what I follow, there apparently are NO sources available to this uaputl >> program and I am VERY dubious of this. I have also read that there are NO >> access controls and that you DONT have to be root to change the SSID or any >> other access point configurations with this utility and the way it talks to >> the kernel driver. I dont like it but it is what I have to use. > > I've not looked at it, but source is available from the bottom of this > page: > > http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_WiFi_Access_Point > > Cheers, > > Jim This is what I have been looking for for a LOOOOONG TIME!!!! Thank you!!!! Now I want to look at it and see what kind of security it has, etc.. and compile my own and make sure this works! THANKS! Johnny O -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From claudio.cavalera at gmail.com Fri Oct 8 08:55:39 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 8 Oct 2010 10:55:39 +0200 Subject: [ARMedslack] Trying armedslack-current In-Reply-To: <4CAEDB52.7060107@gmail.com> References: <4CAE5092.5060909@gmail.com> <4CAED44D.6020002@gmail.com> <4CAEDB52.7060107@gmail.com> Message-ID: Hi guys, I admit I haven't read the whole discussion, but wouldn't it better to sponsor Seagate Dockstar a little bit more inside slackware for arm? What are the advantages of GuruPlug vs Dockstar? Ciao, Claudio PS: googling dockstar site:armedslack.org -> no results From m-lists at biscuit.org.uk Fri Oct 8 09:34:35 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 8 Oct 2010 10:34:35 +0100 (BST) Subject: [ARMedslack] Trying armedslack-current In-Reply-To: References: <4CAE5092.5060909@gmail.com> <4CAED44D.6020002@gmail.com> <4CAEDB52.7060107@gmail.com> Message-ID: Hi Claudio > I admit I haven't read the whole discussion, but wouldn't it better to > sponsor Seagate Dockstar a little bit more inside slackware for arm? > What are the advantages of GuruPlug vs Dockstar? http://forums.slimdevices.com/showthread.php?t=79954 "Dockstar is essentially a Sheevaplug with 128MB RAM, no real-time clock, and an added 4-port usb hub (comparison)" My personal opinion is that you might as well buy a SheevaPlug. I really see no point in buying a device with such a limited amount of RAM, has no real time clock *and* requires dismantling in order to work with it. It's cheap, but limited. As far as I know, from reading this list, is that Slackware ARM works on the dockstar already. If someone wants to write some documentation that I can put on the web site, then I'll happily put it there; but for the very limited time I have to spend on Slackware, I'd rather spend it on more beefy devices. When developing Slackware ARM, this is how I determine where to spend my time: The thing with ARM devices is that they're geared for a specific job, and it doesn't mean they're worth while putting a full OS such as Slackware on it. If you have a device such as the Sheeva or OpenRD, then they're suplied in order to be a general purpose device -so they have more onboard hardware, graphics, video, more RAM, eSATA and so on. From jawkins at armedslack.org Fri Oct 8 09:37:14 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Fri, 8 Oct 2010 10:37:14 +0100 (BST) Subject: [ARMedslack] Trying armedslack-current In-Reply-To: References: <4CAE5092.5060909@gmail.com> Message-ID: On Fri, 8 Oct 2010, Stuart Winter wrote: > There were a number of patches to the 13.1 kernel: > armedslack-13.1/source/k/sources/patches/esata_sheevaplug_and_guruplug-patchset > but as far as I knew, all of the guru plug stuff was merged into > the upstream kernel: > > At present, I don't apply *any* patches to the -current kernel > (which is waiting to be pushed out after Slackware x86 has been) > > The module does not exist in the source tree. > root at wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' > root at wizbit:/usr/src/linux-2.6.36rc7# This comes from the libertas patch in that patchset. It doesn't look like it's been merged into the mainline kernel. Cheers, Jim From unixjohn1969 at gmail.com Tue Oct 12 06:12:52 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 12 Oct 2010 02:12:52 -0400 Subject: [ARMedslack] Ktorrent keeps crashing with sig 11 Message-ID: <4CB3FC64.1020607@gmail.com> I am not sure why this is happening. What can I provide to help? I disabled all the plugins to try to speed up processing and reduce the likelihood of them producing a problem. It has helped with the sluggishness alot! But I leave it unattended and it still crashes once in a while. This is from -current on my guruplug running from the micro SD with that uboot I compiled up. BUT using 2.6.33.5-kirkwood from 13.1 because of the missing Access Point module in -current. It doesn't happen alot. But it does happen enough to be a concern. Thanks in advance, Johnny O -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Tue Oct 12 14:23:08 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 12 Oct 2010 15:23:08 +0100 (BST) Subject: [ARMedslack] Ktorrent keeps crashing with sig 11 In-Reply-To: <4CB3FC64.1020607@gmail.com> References: <4CB3FC64.1020607@gmail.com> Message-ID: > is from -current on my guruplug running from the micro SD with that uboot I > compiled up. BUT using 2.6.33.5-kirkwood from 13.1 because of the missing > Access Point module in -current. > > It doesn't happen alot. But it does happen enough to be a concern. There is a Ktorrent 4.0.3 which I have built and will put into the -current when I next push it out. Whether it'll resolve the issue, I don't know, but this is in the changelog: Changes in 4.0.3: - Fix bug causing wrong encoding to be used when the default save location of a group is read (244873) - Fix crash in QueueManagerWidget when moving torrents in the queue - When renaming files in a torrent prevent duplicate names (244624) - Fix crash on exit when cleaning up UPnP requests - Fix crash due to uncaught exception when a tor directory cannot be removed (247979) -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Tue Oct 19 12:31:13 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 19 Oct 2010 13:31:13 +0100 (BST) Subject: [ARMedslack] Cross toolchain problem Message-ID: Hi Since the gcc and glibc updates last week, using the x-build script ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build I can't get glibc to build (not sure if anything further in the chain will also not build) on x86_64, and on i486 the build breaks at binutils. Can anybody who knows more about toolchains have a go at building on x86_64 & i486 and see if they can fix it? I have tried on slackware-current for both archs. Thanks s. -- Stuart Winter Slackware ARM: www.armedslack.org From vitaly.v.ch at chernookiy.com Tue Oct 19 12:57:17 2010 From: vitaly.v.ch at chernookiy.com (Vitaly V. Ch) Date: Tue, 19 Oct 2010 15:57:17 +0300 Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: Hi! Can You send here build log? \\wbr Vitaly Chernooky On Tue, Oct 19, 2010 at 3:31 PM, Stuart Winter wrote: > > Hi > > Since the gcc and glibc updates last week, using the x-build script > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build > > I can't get glibc to build (not sure if anything further in the chain will > also not build) on x86_64, and on i486 the build breaks at binutils. > > Can anybody who knows more about toolchains have a go at building on > x86_64 & i486 and see if they can fix it? > I have tried on slackware-current for both archs. > > Thanks > s. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- \\wbr Vitaly From m-lists at biscuit.org.uk Tue Oct 19 13:02:27 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 19 Oct 2010 14:02:27 +0100 (BST) Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: Oh yes that'd be useful ;) my distro scripts filter all those out.. http://stash.armedslack.org/i486_build.log.xz http://stash.armedslack.org/x86_64_build.log.xz On Tue, 19 Oct 2010, Vitaly V. Ch wrote: > Hi! > > Can You send here build log? > > \\wbr Vitaly Chernooky > > On Tue, Oct 19, 2010 at 3:31 PM, Stuart Winter wrote: > > > > Hi > > > > Since the gcc and glibc updates last week, using the x-build script > > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build > > > > I can't get glibc to build (not sure if anything further in the chain will > > also not build) on x86_64, and on i486 the build breaks at binutils. > > > > Can anybody who knows more about toolchains have a go at building on > > x86_64 & i486 and see if they can fix it? > > I have tried on slackware-current for both archs. > > > > Thanks > > s. > > > > -- > > Stuart Winter > > Slackware ARM: www.armedslack.org > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > > -- Stuart Winter Slackware ARM: www.armedslack.org From vitaly.v.ch at chernookiy.com Tue Oct 19 13:10:25 2010 From: vitaly.v.ch at chernookiy.com (Vitaly V. Ch) Date: Tue, 19 Oct 2010 16:10:25 +0300 Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: I few days ago try to compile cross toolchain for AVR and found out then gcc 4.5.1 have few bugs which does not allow it. The root of problem was than gcc does not refuse to compile for unsupported target cpu. Also There are patches for AVR target. On Tue, Oct 19, 2010 at 3:31 PM, Stuart Winter wrote: > > Hi > > Since the gcc and glibc updates last week, using the x-build script > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build > > I can't get glibc to build (not sure if anything further in the chain will > also not build) on x86_64, and on i486 the build breaks at binutils. > > Can anybody who knows more about toolchains have a go at building on > x86_64 & i486 and see if they can fix it? > I have tried on slackware-current for both archs. > > Thanks > s. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- \\wbr Vitaly Chernooky From vitaly.v.ch at chernookiy.com Tue Oct 19 13:23:04 2010 From: vitaly.v.ch at chernookiy.com (Vitaly V. Ch) Date: Tue, 19 Oct 2010 16:23:04 +0300 Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: Hm, It's not same problem :(( On Tue, Oct 19, 2010 at 4:02 PM, Stuart Winter wrote: > > Oh yes that'd be useful ;) > my distro scripts filter all those out.. > > http://stash.armedslack.org/i486_build.log.xz > http://stash.armedslack.org/x86_64_build.log.xz > > On Tue, 19 Oct 2010, Vitaly V. Ch wrote: > >> Hi! >> >> Can You send here build log? >> >> \\wbr Vitaly Chernooky >> >> On Tue, Oct 19, 2010 at 3:31 PM, Stuart Winter wrote: >> > >> > Hi >> > >> > Since the gcc and glibc updates last week, using the x-build script >> > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build >> > >> > I can't get glibc to build (not sure if anything further in the chain will >> > also not build) on x86_64, and on i486 the build breaks at binutils. >> > >> > Can anybody who knows more about toolchains have a go at building on >> > x86_64 & i486 and see if they can fix it? >> > I have tried on slackware-current for both archs. >> > >> > Thanks >> > s. >> > >> > -- >> > Stuart Winter >> > Slackware ARM: www.armedslack.org >> > _______________________________________________ >> > ARMedslack mailing list >> > ARMedslack at lists.armedslack.org >> > http://lists.armedslack.org/mailman/listinfo/armedslack >> > >> >> >> >> > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- \\wbr Vitaly From m-lists at biscuit.org.uk Wed Oct 20 17:16:59 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Oct 2010 18:16:59 +0100 (BST) Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: Yeah I didn't think it'd be. I've been looking on the web myself since last week and can't find many problems with glibc 2.12 and an ARM toolchain - although it may be that we're just ahead of the curve -- usually everyone experiences the same problems. I suppose I *could* try stripping the glibc configure options down a bit to see if I can build a more bland one... *Actually* I wonder if it's because of the linux kernel headers.... I will try with the older versions and see what happens. On Tue, 19 Oct 2010, Vitaly V. Ch wrote: > Hm, It's not same problem :(( > > On Tue, Oct 19, 2010 at 4:02 PM, Stuart Winter wrote: > > > > Oh yes that'd be useful ;) > > my distro scripts filter all those out.. > > > > http://stash.armedslack.org/i486_build.log.xz > > http://stash.armedslack.org/x86_64_build.log.xz > > > > On Tue, 19 Oct 2010, Vitaly V. Ch wrote: > > > >> Hi! > >> > >> Can You send here build log? > >> > >> \\wbr Vitaly Chernooky > >> > >> On Tue, Oct 19, 2010 at 3:31 PM, Stuart Winter wrote: > >> > > >> > Hi > >> > > >> > Since the gcc and glibc updates last week, using the x-build script > >> > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/x-build > >> > > >> > I can't get glibc to build (not sure if anything further in the chain will > >> > also not build) on x86_64, and on i486 the build breaks at binutils. > >> > > >> > Can anybody who knows more about toolchains have a go at building on > >> > x86_64 & i486 and see if they can fix it? > >> > I have tried on slackware-current for both archs. > >> > > >> > Thanks > >> > s. > >> > > >> > -- > >> > Stuart Winter > >> > Slackware ARM: www.armedslack.org > >> > _______________________________________________ > >> > ARMedslack mailing list > >> > ARMedslack at lists.armedslack.org > >> > http://lists.armedslack.org/mailman/listinfo/armedslack > >> > > >> > >> > >> > >> > > > > -- > > Stuart Winter > > Slackware ARM: www.armedslack.org > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > > -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Wed Oct 20 17:53:21 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 20 Oct 2010 18:53:21 +0100 (BST) Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: > *Actually* I wonder if it's because of the linux kernel headers.... > I will try with the older versions and see what happens. No that didn't work. Same problem. Although it felt good to clutch at the straw for a few minutes ;-) From m-lists at biscuit.org.uk Thu Oct 21 20:41:00 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Oct 2010 21:41:00 +0100 (BST) Subject: [ARMedslack] Cross toolchain problem In-Reply-To: References: Message-ID: > Although it felt good to clutch at the straw for a few minutes ;-) I'm quite good at this straw clutching thing actually. I've solved the problem for x86_64, and now have a different problem for i486, but it's probably pretty simple. I'll upload the stuff when I push armedslack-13.1 tomorrow. From niels.horn at gmail.com Sat Oct 23 12:31:11 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 23 Oct 2010 10:31:11 -0200 Subject: [ARMedslack] Slackpkg does not pick up Firefox / Thunderbird updates Message-ID: Hi, This probably happens because the packages have an ARCH setting of "armv5t" and SlackPkg looks for "arm". Should I report this to PiterPunk? It seems to be a specific ARMedslack issue. Regards, Niels Horn Rio de Janeiro, RJ Brasil site: www.nielshorn.net e-mail: niels.horn at gmail.com From m-lists at biscuit.org.uk Sat Oct 23 18:48:43 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 23 Oct 2010 19:48:43 +0100 (BST) Subject: [ARMedslack] Slackpkg does not pick up Firefox / Thunderbird updates In-Reply-To: References: Message-ID: > This probably happens because the packages have an ARCH setting of > "armv5t" and SlackPkg looks for "arm". > > Should I report this to PiterPunk? It seems to be a specific ARMedslack issue. Yes slackpkg should handle it - unless these packages have their armv4 compatability returned (it was removed from the code), then I will continue to give them the arch value they have now. I guess he could just match on "arm*". I'm not sure if there are any downsides to this, but given that we only have one ARM port now (rather than the oldabi), I don't see any problems here. From niels.horn at gmail.com Sat Oct 23 19:45:54 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 23 Oct 2010 17:45:54 -0200 Subject: [ARMedslack] Slackpkg does not pick up Firefox / Thunderbird updates In-Reply-To: References: Message-ID: On Sat, Oct 23, 2010 at 4:48 PM, Stuart Winter wrote: > >> This probably happens because the packages have an ARCH setting of >> "armv5t" and SlackPkg looks for "arm". >> >> Should I report this to PiterPunk? It seems to be a specific ARMedslack issue. > > Yes slackpkg should handle it - unless these packages have their armv4 > compatability returned (it was removed from the code), then I will > continue to give them the arch value they have now. > > I guess he could just match on "arm*". ?I'm not sure if there are any > downsides to this, but given that we only have one ARM port now (rather > than the oldabi), I don't see any problems here. OK, I'll write to PiterPunk. It might be a simple change in the configuration file, or might need a patch. I'll investigate this a bit more, to save him some work ;) Niels From niels.horn at gmail.com Sun Oct 24 00:09:33 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 23 Oct 2010 22:09:33 -0200 Subject: [ARMedslack] Slackpkg does not pick up Firefox / Thunderbird updates In-Reply-To: References: Message-ID: On Sat, Oct 23, 2010 at 5:45 PM, Niels Horn wrote: > On Sat, Oct 23, 2010 at 4:48 PM, Stuart Winter wrote: >> >>> This probably happens because the packages have an ARCH setting of >>> "armv5t" and SlackPkg looks for "arm". >>> >>> Should I report this to PiterPunk? It seems to be a specific ARMedslack issue. >> >> Yes slackpkg should handle it - unless these packages have their armv4 >> compatability returned (it was removed from the code), then I will >> continue to give them the arch value they have now. >> >> I guess he could just match on "arm*". ?I'm not sure if there are any >> downsides to this, but given that we only have one ARM port now (rather >> than the oldabi), I don't see any problems here. > > OK, I'll write to PiterPunk. It might be a simple change in the > configuration file, or might need a patch. > I'll investigate this a bit more, to save him some work ;) > > Niels > OK, I patched /usr/libexec/slackpkg/core-functions.sh and this works fine: --- core-functions.sh_orig 2010-05-01 20:10:33.000000000 -0300 +++ core-functions.sh 2010-10-23 22:02:55.799755000 -0200 @@ -122,7 +122,7 @@ PKGMAIN=${PKGMAIN:-slackware} ;; arm*) - ARCH=arm[el]* + ARCH=arm[v5t]* SLACKKEY=${SLACKKEY:-"ARMedslack Security (ARMedslack Linux Project Security) "} PKGMAIN=${PKGMAIN:-slackware} ;; (to avoid problems with line-breaking etc, also attached as a file...) I could not find any "armel" packages, so this should be safe. I'll send the patch to PiterPunk as well. Regards, Niels -------------- next part -------------- A non-text attachment was scrubbed... Name: armv5t.patch Type: text/x-diff Size: 376 bytes Desc: not available URL: From m-lists at biscuit.org.uk Sun Oct 24 08:14:10 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 24 Oct 2010 09:14:10 +0100 (BST) Subject: [ARMedslack] Slackpkg does not pick up Firefox / Thunderbird updates In-Reply-To: References: Message-ID: > + ARCH=arm[v5t]* [..] > I could not find any "armel" packages, so this should be safe. Thanks - I'll upgrade when PP has applied the patch. There won't be any packages with the arch "armel". From mozes at slackware.com Sun Oct 24 08:38:23 2010 From: mozes at slackware.com (Stuart Winter) Date: Sun, 24 Oct 2010 01:38:23 -0700 (PDT) Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug Message-ID: Hi On Slackware-current, the udev rules in INSTALL_KIRKWOOD.TXT no longer work: /dev/{openrd,sheevaplug} symlinks don't get created, so I use ttyUSB0 instead. I've had a look at udevadm info -a -p /sys/class/tty/ttyUSB0 and the attributes are the same as in the rules files. Does anybody know what needs changing? -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From niels.horn at gmail.com Sun Oct 24 14:06:05 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 24 Oct 2010 12:06:05 -0200 Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug In-Reply-To: References: Message-ID: On Sun, Oct 24, 2010 at 6:38 AM, Stuart Winter wrote: > > Hi > > On Slackware-current, the udev rules in INSTALL_KIRKWOOD.TXT > no longer work: > /dev/{openrd,sheevaplug} symlinks don't get created, so I use ttyUSB0 > instead. > > I've had a look at > udevadm info -a -p /sys/class/tty/ttyUSB0 > and the attributes are the same as in the rules files. > > Does anybody know what needs changing? > > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org Actually, I don't think it's that "current". I've had this for a while already and got used to connecting to /dev/ttyUSB0 - on my Slackware 13.1 stable box. I never really looked into it, as it works just fine for me using ttyUSB0 and thought it was something I messed up on my Slackware box. Interesting... :) Niels From niels.horn at gmail.com Sun Oct 24 14:18:37 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 24 Oct 2010 12:18:37 -0200 Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug In-Reply-To: References: Message-ID: On Sun, Oct 24, 2010 at 12:06 PM, Niels Horn wrote: > On Sun, Oct 24, 2010 at 6:38 AM, Stuart Winter wrote: >> >> Hi >> >> On Slackware-current, the udev rules in INSTALL_KIRKWOOD.TXT >> no longer work: >> /dev/{openrd,sheevaplug} symlinks don't get created, so I use ttyUSB0 >> instead. >> >> I've had a look at >> udevadm info -a -p /sys/class/tty/ttyUSB0 >> and the attributes are the same as in the rules files. >> >> Does anybody know what needs changing? >> >> >> -- >> Stuart Winter >> www.slackware.com/~mozes >> Slackware for ARM: www.armedslack.org > > Actually, I don't think it's that "current". I've had this for a while > already and got used to connecting to /dev/ttyUSB0 - on my Slackware > 13.1 stable box. > I never really looked into it, as it works just fine for me using > ttyUSB0 and thought it was something I messed up on my Slackware box. > > Interesting... :) > > Niels > hmmmm... might have found something... please confirm if this works for you as well... It seems that the "SYMLINK+=" rule needs to come after the one that creates the ttyUSB0 device, which is /lib/udev/rules.d/60-persistent-serial.rules So I simply renamed the rule to 61-marvell-kirkwood.rules and that worked :D Now I have the /dev/sheevaplug symlink again! Niels From m-lists at biscuit.org.uk Tue Oct 26 20:22:17 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 26 Oct 2010 21:22:17 +0100 (BST) Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug In-Reply-To: References: Message-ID: > It seems that the "SYMLINK+=" rule needs to come after the one that > creates the ttyUSB0 device, which is > /lib/udev/rules.d/60-persistent-serial.rules > So I simply renamed the rule to 61-marvell-kirkwood.rules and that worked :D > > Now I have the /dev/sheevaplug symlink again! Hmm. In -current, it's named 70-persistent-serial.rules so I decided to name mine 100-marvell-kirkwood.rules, but this doesn't make the symlink. I looked for some more debug but didn't find any. I'll have to start udev in debug mode or verbose mode later on. -- Stuart Winter Slackware ARM: www.armedslack.org From niels.horn at gmail.com Tue Oct 26 20:32:25 2010 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 26 Oct 2010 18:32:25 -0200 Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug In-Reply-To: References: Message-ID: On Tue, Oct 26, 2010 at 6:22 PM, Stuart Winter wrote: > >> It seems that the "SYMLINK+=" rule needs to come after the one that >> creates the ttyUSB0 device, which is >> /lib/udev/rules.d/60-persistent-serial.rules >> So I simply renamed the rule to 61-marvell-kirkwood.rules and that worked :D >> >> Now I have the /dev/sheevaplug symlink again! > > Hmm. ?In -current, it's named 70-persistent-serial.rules so I decided to > name mine 100-marvell-kirkwood.rules, but this doesn't make the symlink. > > I looked for some more debug but didn't find any. > I'll have to start udev in debug mode or verbose mode later on. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Did you try 99-marvell-kirkwood.rules, or 71-.... ? It might do a simple alpha-sort... The udev man page says that all rules are sorted, independent of their location... Niels From m-lists at biscuit.org.uk Tue Oct 26 20:43:17 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 26 Oct 2010 21:43:17 +0100 (BST) Subject: [ARMedslack] Slackware-current & udev rules for openrd/sheevaplug In-Reply-To: References: Message-ID: > > Did you try 99-marvell-kirkwood.rules, or 71-.... ? > It might do a simple alpha-sort... root at kato:~# ls -la /dev/sheevaplug lrwxrwxrwx 1 root root 7 2010-10-26 21:20 /dev/sheevaplug -> ttyUSB0 You genius! :) I renamed it 99- From mozes at slackware.com Wed Oct 27 17:16:14 2010 From: mozes at slackware.com (Stuart Winter) Date: Wed, 27 Oct 2010 10:16:14 -0700 (PDT) Subject: [ARMedslack] #armedslack IRC channel on freenode Message-ID: Hi Robby's setup an #armedslack channel on the irc.freenode.net IRC service -- there had been some discussions about armedslack on #slackware, but it was being lost in the noise. Hopefully this might be useful -- I leave myself logged into IRC 24/7 and check it every day or so so might see you around if you drop in! s. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From niels.horn at gmail.com Wed Oct 27 18:04:38 2010 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 27 Oct 2010 16:04:38 -0200 Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: References: Message-ID: On Wed, Oct 27, 2010 at 3:16 PM, Stuart Winter wrote: > > Hi > > Robby's setup an #armedslack channel on the irc.freenode.net IRC service > -- there had been some discussions about armedslack on #slackware, but it > was being lost in the noise. > Hopefully this might be useful -- I leave myself logged into IRC 24/7 and > check it every day or so so might see you around if you drop in! > > s. > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org Great initiative! I'll be there (already am) most of the time, except when off-line for downtime etc... Niels From unixjohn1969 at gmail.com Thu Oct 28 08:40:52 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 28 Oct 2010 04:40:52 -0400 Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: References: Message-ID: <4CC93714.1080603@gmail.com> On 10/27/2010 02:04 PM, Niels Horn wrote: > On Wed, Oct 27, 2010 at 3:16 PM, Stuart Winter wrote: >> >> Hi >> >> Robby's setup an #armedslack channel on the irc.freenode.net IRC service >> -- there had been some discussions about armedslack on #slackware, but it >> was being lost in the noise. >> Hopefully this might be useful -- I leave myself logged into IRC 24/7 and >> check it every day or so so might see you around if you drop in! >> >> s. >> >> -- >> Stuart Winter >> www.slackware.com/~mozes >> Slackware for ARM: www.armedslack.org > > Great initiative! > > I'll be there (already am) most of the time, except when off-line for > downtime etc... > > Niels I will try to be also. Juanisan -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From claudio.cavalera at gmail.com Thu Oct 28 08:44:41 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 28 Oct 2010 10:44:41 +0200 Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: <4CC93714.1080603@gmail.com> References: <4CC93714.1080603@gmail.com> Message-ID: Me too with nickname Lalloso! :-) On Thu, Oct 28, 2010 at 10:40 AM, John O'Donnell wrote: > On 10/27/2010 02:04 PM, Niels Horn wrote: >> >> On Wed, Oct 27, 2010 at 3:16 PM, Stuart Winter >> ?wrote: >>> >>> Hi >>> >>> Robby's setup an #armedslack channel on the irc.freenode.net IRC service >>> -- there had been some discussions about armedslack on #slackware, but it >>> was being lost in the noise. >>> Hopefully this might be useful -- I leave myself logged into IRC 24/7 and >>> check it every day or so so might see you around if you drop in! >>> >>> s. >>> >>> -- >>> Stuart Winter >>> www.slackware.com/~mozes >>> Slackware for ARM: www.armedslack.org >> >> Great initiative! >> >> I'll be there (already am) most of the time, except when off-line for >> downtime etc... >> >> Niels > > I will try to be also. > Juanisan > > -- > === Never ask a geek why, just nod your head and slowly back away.=== > +================================+==================================+ > | ?John O'Donnell ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| > | ?(Sr. Systems Engineer, ? ? ? ?| ? ?http://juanisan.homeip.net ? ?| > | ?Net Admin, Programmer, etc.) ?| ?E-Mail: unixjohn1969 at gmail.com ?| > +================================+==================================+ > No man is useless who has a friend, and if we are loved we are > indispensable. ?-- Robert Louis Stevenson > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack >