Re: [ARMedslack] Trying armedslack-current
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. > r...@wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' > r...@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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Trying armedslack-current
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. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Trying armedslack-current
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Trying armedslack-current
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 LONG 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: 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
Re: [ARMedslack] Trying armedslack-current
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Trying armedslack-current
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. r...@wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' r...@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
Re: [ARMedslack] Trying armedslack-current
> 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. > r...@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. r...@wizbit:/usr/src/linux-2.6.36rc7# find . -iname '*uap8xxx*' r...@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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack