[ARMedslack] Armedslack on a dockstar :-)
Hello, I'm new to this list! I've been using slackware on x86 since 7.1 and I tend to install it on every machine I touch. Recently I'm being in touch with the Seagate Dockstar which is a promising device based on Kirkwood Soc: http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device/ I've found this info on how to install armedslack on it: http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 I hope I'll succeed :-) Just one general question on armedslack: is it suggested to use slackbuilds.org scripts to compile and install software which is not officially in slackware or is it better to compile and install by hand ? Bye, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Armedslack on a dockstar :-)
On Wed, Sep 15, 2010 at 5:22 PM, Jim Hawkins wrote: > On Wed, 15 Sep 2010, Stuart Winter wrote: > >> I don't see anything about the "Dockstar" in the "kirkwood >> implementations" in the Kernel armedslack ships. There might be support >> in linux 2.6.36, in which case I'll add it in when I next update the >> kernel. > > Someone just posted a patch for the DockStar to the armlinux mailing list. > Doesn't really have much device specific stuff in it - configures the GPIO > pins for LEDs and USB power enable. You can probably get away with using a > different Kirkwood kernel as Thorsten has found. What is USB power enable? Thanks, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello
On Fri, Sep 17, 2010 at 12:55 AM, Richard Lapointe wrote: > I subscribed to this list at the end of August, but have been having trouble > getting my email so I just subscribed again with my alternate gmail account. > > Just wanted to tell you that I've got armedslack running on my dockstar. > Once I got my serial line working, it was quite easy. I first follow the > direction from here: > http://plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot , but only > through installing the uboot. After that I followed the instructions for > 13.1 from here: > ftp://ftp.armedslack.org/armedslack/armedslack-13.1/INSTALL_KIRKWOOD.TXT. I > actually installed current first, so they both worked. > > Rich Lapointe Great! I guess it's not possible to achieve that without a serial cable, is it? So you did not patched the kernel to have LEDs working and USB power did you? Thanks, Claudio ___ 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] #armedslack IRC channel on freenode
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: 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
Re: [ARMedslack] A few questions on kirkwood initrd
Hello, I'm the cause of this thread's revival. I aim to be the first armed slacker without the serial cable. :-) I've patched the uboot with these commands on the dockstar: cd /tmp wget http://plugapps.com/os/pogoplug/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh (it's the uboot from doozan: http://jeff.doozan.com/debian/uboot/ ) I've set up a netconsole like suggested here http://forum.doozan.com/read.php?3,14 and it's working so and so. The problem is that when I load the stuff from the tftpboot, but when I bootm the last thing I see on my netcat session is: Starting kernel... then I would expect my dockstar to be online in order to ssh in it and run setup, but it does not reply to ping. :-( I've tried the commands from Stuart as well as the commands from the original poster: setenv arcNumber 2097 setenv mainlineLinux yes usb start tftpboot 0x180 armedslack-13.1/uinitrd-kirkwood.img tftpboot 0x600 armedslack-13.1/uImage-kirkwood setenv bootargs console=ttyS0,115200 kbd=it nic=auto:eth0:dhcp root=/dev/ram rw bootm 0x600 0x180 The original poster also said something about an "uncompressed kernel" to be used with dockstar. http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 Could be this the reason of my problem? Thanks, Claudio On Sun, Nov 7, 2010 at 21:49, Stuart Winter wrote: > >> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp >> root=/dev/ram rw;bootm 0x0080 0x0110;reset > > Obviously best to take out "nodhcp", although it still worked with it in: > > setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp root=/dev/ram > rw;bootm 0x0080 0x0110;reset > > > -- > 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] Armedslack on a dockstar :-)
Thorsten, could you please provide some guidelines to put armed slack on the dockstar? I've explained where I'm stuck at, in the other thread on this ML. Thanks a lot, Claudio 2010/9/15 Thorsten Mühlfelder : > The Dockstar works fine with the Armed Slack kernel. See my message from > 29.08.2010: > >> OK, I've received my Seagate Freeagent Dockstar. I've flashed a new >> U-Boot loader to it. A description can be found here: >> http://www.plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot >> http://plugapps.com/os/pogoplug/uboot/ >> >> The board boots fine when the kirkwood kernel is used, that comes with >> the mini rootfs. Here is the cpuinfo: >> >> 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 : Marvell SheevaPlug Reference Board >> Revision : >> Serial : > > I've installed the new U-Boot. Make sure the kernel is called uImage and the > initrd is called uInitrd. > > > Am Wednesday 15 September 2010 11:15:11 schrieb Stuart Winter: >> > Recently I'm being in touch with the Seagate Dockstar which is a >> > promising device based on Kirkwood Soc: >> > http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device >> >/ >> >> This looks like an interesting device. >> >> You'll probably need to build a new >> kernel to begin with patched with support for the Dockstar, because I >> don't see anything about the "Dockstar" in the "kirkwood implementations" >> in the Kernel armedslack ships. There might be support in linux 2.6.36, >> in which case I'll add it in when I next update the kernel. >> >> Let us know how you get on with it. Good luck! :) >> ___ >> ARMedslack mailing list >> ARMedslack@lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack > > > > -- > > Dipl.-Ing. (FH) Thorsten Mühlfelder > Hard- und Softwareentwicklung > ___ > 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 on a dockstar :-)
RM Linux Kernel Image (uncompressed) Data Size:2096716 Bytes = 2 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0180 ... Image Name: Slackware ARM Installer Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:14698980 Bytes = 14 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... On Fri, Nov 12, 2010 at 14:23, Claudio Cavalera wrote: > Thorsten, > could you please provide some guidelines to put armed slack on the dockstar? > I've explained where I'm stuck at, in the other thread on this ML. > Thanks a lot, > Claudio > > 2010/9/15 Thorsten Mühlfelder : >> The Dockstar works fine with the Armed Slack kernel. See my message from >> 29.08.2010: >> >>> OK, I've received my Seagate Freeagent Dockstar. I've flashed a new >>> U-Boot loader to it. A description can be found here: >>> http://www.plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot >>> http://plugapps.com/os/pogoplug/uboot/ >>> >>> The board boots fine when the kirkwood kernel is used, that comes with >>> the mini rootfs. Here is the cpuinfo: >>> >>> 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 : Marvell SheevaPlug Reference Board >>> Revision : >>> Serial : >> >> I've installed the new U-Boot. Make sure the kernel is called uImage and the >> initrd is called uInitrd. >> >> >> Am Wednesday 15 September 2010 11:15:11 schrieb Stuart Winter: >>> > Recently I'm being in touch with the Seagate Dockstar which is a >>> > promising device based on Kirkwood Soc: >>> > http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device >>> >/ >>> >>> This looks like an interesting device. >>> >>> You'll probably need to build a new >>> kernel to begin with patched with support for the Dockstar, because I >>> don't see anything about the "Dockstar" in the "kirkwood implementations" >>> in the Kernel armedslack ships. There might be support in linux 2.6.36, >>> in which case I'll add it in when I next update the kernel. >>> >>> Let us know how you get on with it. Good luck! :) >>> ___ >>> ARMedslack mailing list >>> ARMedslack@lists.armedslack.org >>> http://lists.armedslack.org/mailman/listinfo/armedslack >> >> >> >> -- >> >> Dipl.-Ing. (FH) Thorsten Mühlfelder >> Hard- und Softwareentwicklung >> ___ >> 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] Hello
Thx for your answer Richard! I've ccopied the ML because I think this stuff could be also useful to someone else. Are you also on the #armedslack IRC Channel on freenode? I really would like to install Slackware on my dockstar. I don't have made the serial cable yet :-) I'm sorry you have bricked your dockstar with the rescue system, is it broken or is it because of your mistake? (where have you bought your other dockstars? I can't find them anywhere in Europe anymore). Anyway could you please help me identify the proper sequence of commands ? It shouldn't be so long after one has done the tftp and NFS configuration part on a slackware server. I've summarized this one at the moment. My goal is to have the dockstar booting and getting an IP address from the DHCP router as it already does when it starts with pogoplug. This way I should be able to start the slackware installer by doing ssh into the dockstar and without the serial cable. If we can achieve this goal we could write a guide to share on armedslack also (if we double check the procedure). Here is what I'm doing, I'm missing something near the end, maybe the line with the dhcp part (so please read at least the last line :-) Unplug your internet. You don't want to accidentally stealth update the firmware Unplug your USB drives and boot to PogoPlug OS Log in via SSH as root, the default password is stxadmin, this may have changed if you registered with PogoPlug Remount the file system read and write with: mount / -rw -o remount edit or create /etc/hosts to add these lines: 127.0.0.1 service.pogoplug.com 127.0.0.1 pm1.pogoplug.com 127.0.0.1 pm2.pogoplug.com 127.0.0.1 service.cloudengines.com 127.0.0.1 upgrade.pogoplug.com save the file! Remount the file system back to read only: mount / -r -o remount Reboot: /sbin/reboot Install the new uboot version by Jeff Doozan: cd /tmp wget http://plugapps.com/os/pogoplug/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh activate netconsole as explained here: http://forum.doozan.com/read.php?3,14,14 -bash-3.2# /usr/sbin/fw_setenv serverip 192.168.1.38 -bash-3.2# /usr/sbin/fw_setenv ipaddr 192.168.1.229 -bash-3.2# /usr/sbin/fw_setenv if_netconsole 'ping $serverip' -bash-3.2# /usr/sbin/fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;' -bash-3.2# /usr/sbin/fw_setenv preboot 'run if_netconsole start_netconsole' then on your linux pc 192.168.1.38: nc -l -u -p & nc -u 192.168.1.229 # run killall -9 nc after you've finished to kill the background nc process; if you have problems I suggest run nc in foreground in two separate sessions (e.g. two shells or two screen sessions) Then enter the uboot prompt by pressing ENTER just after a reboot of the dockstar Marvell>>tftpboot 0x0110 armedslack-13.1/uinitrd-kirkwood.img Marvell>>tftpboot 0x0080 armedslack-13.1/uImage-kirkwood setenv bootargs console=ttyS0,115200 kbd=it nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x0080 0x0110;reset Thanks, Claudio On Sun, Nov 14, 2010 at 17:54, Rich wrote: > Hi Claudio, > Yes, I still read the armed slack mail list. Regarding getting armed slack > installed on my Dockstar, I first tried doing what Thorsten did, loading the > mini root file system onto a usb drive and renaming the kernel and uinitrd > to uImage, but it just resulted in getting the "Starting kernel" message and > continual reboots. So then yes I used those commands, following the armed > slack INSTALL_KIRKWOOD.TXT instructions and was able get armed slack running > on my Dockstar. I had it running for over a month, but just last week I > managed to semi-brick it installing Jeff Doozan Rescue System. Now all I > can do is boot into uboot. > I too would like to be able to install without a serial cable since I have > two more Dockstars that I want to get up and running. > Regards > Rich Lapointe > > On 11/13/2010 03:07 PM, Claudio Cavalera wrote: >> >> Hi Richard, >> do you still read the armed slack mailing list? could you please help >> me out a bit with my dockstar? >> Have you run this commands to install your dockstar? >> Thx, >> Claudio >> >> >> 4.4 Booting the installer >> - >> >> Now download the Kernel and Slackware ARM installer via TFTP: >> >> Marvell>> tftpboot 0x0110 armedslack-13.1/uinitrd-kirkwood.img >> Marvell>> tftpboot 0x0080 armedslack-13.1/uImage-kirkwood >> Marvell>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk >> root=/dev/ram rw >> Marvell>> bootm 0x0080 0x0110 >> >> Note: >>
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Tue, Dec 7, 2010 at 21:44, Christophe Lyon wrote: > I must mention that I don't have a serial cable; I have actived > uboot's netconsole, which is helpful... but not enough. > You are stuck at the same point as me. If you read my emails you could find some parameters to pass at the kernel command line in order to have DHCP and network and therefore avoid serial cable. Not wokring for me though. :-( Please let us know if you succeed. Thanks, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Thu, Dec 9, 2010 at 13:02, Stuart Winter wrote: > >> kernel command line in order to have DHCP and network and therefore >> avoid serial cable. Not wokring for me though. :-( >> Please let us know if you succeed. > > Did you check your DHCP logs? does the device request an IP? My DHCP server is the ADSL router. It is a switch. :-/ > /me suggests getting a serial cable :) > At least then we can figure out where the boot process is failing - it > might be a simple fix. I have a serial cable but I can't bear debian works without it. :-) Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
2010/12/9 Thorsten Mühlfelder : > Am Thursday 09 December 2010 14:48:25 schrieb Stuart Winter: >> > I have a serial cable but I can't bear debian works without it. :-) >> >> Hang on a minute. So you've got a serial cable... >> use it, figure out where the boot process stops (if at all). >> Then once we know what the problem is, it can most likely be fixed or >> worked around. > > Within 90 % a serial cable to RS232 connector won't work with the Dockstar. > You need a TTL to RS232 level converter. > Search for it on ebay and you'll find some cheap TTL to USB interfaces from > China. I already have the right serial cable with the right connector. But I'm too lazy to open the dockstar. :-) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Thu, Dec 9, 2010 at 21:02, Christophe Lyon wrote: >> >> I already have the right serial cable with the right connector. But >> I'm too lazy to open the dockstar. :-) > > Too bad! > I misread your initial post and thought you actually succeeded in > booting Slackware :-( Maybe I've booted it but it did not get an IP Address. Serial cable is for whimps. :-) Which parameters do you use at bootm= ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Fri, Dec 10, 2010 at 13:09, Christophe Lyon wrote: >> Maybe I've booted it but it did not get an IP Address. Serial cable is >> for whimps. :-) >> Which parameters do you use at bootm= ? > > As I said, I used Jeff Doozan's script to update my uboot, which also > sets to boot parameters. I have also used that script to update/patch my uboot but just for that. I then activated the netconsole and used uboot interactively with a couple of nc sessions. You should be able to do this if you read well within my old emails at this list. I think we are using completely different approaches. I was using a tftp server with tftpboot commands at uboot prompt. Regards, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Fri, Dec 10, 2010 at 16:58, Stuart Winter wrote: > Actually - what driver does the dockstar use for its ethernet? > I assume it's mv643xx_eth -- if not, then that's your problem ;-) > I can't imagine it'd be anything other than that though. I have it when I run lsmod in the debian mv643xx_eth Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Sat, Jan 15, 2011 at 10:40, Stuart Winter wrote: >> I got the chance to run a quick test last night so I loaded the >> installer and kernel onto a usb thumb drive ext2 partition, renamed them >> to uImage and uInitrd and booted with the existing doozan uboot and boot >> lines. As seen in the pastebin boot log, it booted normally until it >> stuck waiting for a keyboard entry. Since I was using a serial cable I >> was able to hit enter allowing the boot process to continue. Obviously >> I would not have able to continue if I did not have the serial cable. >> After logging in I check to see if the network interface was up and >> found that it was not. I assumed then that ssh was not running. After >> that I started the install process, using ftp install option. I didn't >> have enough time to complete the install but I have no doubt that it >> would have worked. So I would think the following three things need be >> addressed to allow the installer to work without the need for a serial >> cable: 1) Eliminate the need for a keyboard selection entry (may be a >> time out) 2) Start up dhcpd 3) Start up ssh > > These things are already taken care of, when you specify the > correct boot parameters. > > What is the boot line you used in u-boot? From what I've understood Richard has used the bootline which is included in the patched Uboot from Jeff Doozan (e.g. plug the usb key and let the uboot boot the kernel and installer automagically). Instead with the serial cable (or with a netconsole activated in the uboot) it is possible by pressing enter during the startup to interrupt the boot process and type the commands to the uboot interactively. I have the feeling, but I might be wrong, that Richard has not done this. Come on guys, we are almost there! :-) Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Wed, Jan 26, 2011 at 02:11, Rich wrote: > Well, i think its good news because you confirmed that the installer can be > started and you seem to have gone through a complete installation. Now I > think you hit the next problem. I'm sorry I have not had time to look into this yet; However I think it's good news, I hope we can make this procedure official somehow. Is it possible to host the jeff uboot on armedslack.org without breaking any license? If you backup the full USB with dd and put it on another one, would it boot ? Thanks, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Wed, Jan 26, 2011 at 10:37, Stuart Winter wrote: > > He's not managed to get the OS installed. > Stuart what do you mean? Cristophe wrote: "Thanks for this procedure. I have tried it but... The installer started, and the installation seemed to be OK, but when I reboot, the netconsole only shows "Starting kernel" and I am not able to ssh into the dockstar anymore :-( At configuration time, I have asked for DHCP, so I think it's OK." Isn't he talking about the reboot at the end of installation? Thanks, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Wed, Jan 26, 2011 at 11:56, Stuart Winter wrote: > >> > He's not managed to get the OS installed. >> > >> >> Stuart what do you mean? >> >> Cristophe wrote: >> "Thanks for this procedure. I have tried it but... The installer >> started, and the installation seemed to be OK, but when I reboot, the > > [..] >> Isn't he talking about the reboot at the end of installation? > > > I think you're right! I misread that. > > Forget what I said - do what Richard said :-) Now I expect full official support by armed slack and the patched uboot available too! :-) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Wed, Jan 26, 2011 at 12:11, Stuart Winter wrote: > >> > Forget what I said - do what Richard said :-) >> >> Now I expect full official support by armed slack and the patched >> uboot available too! :-) > > I expect to win the lottery too, but it ain't happened yet. Just joking. :-) > What does "official support" mean? You should put a dockstar on a wishlist so that we can buy it to you and then you could test and mantain armedslack on it! :-) > All that I can see is that the INSTALL_KIRKWOOD doc needs a couple of > extra points to make the installation work: > - fsck config > - starting NTP on boot This is what I mean, provide full instructions to install on a dockstar. > Can you actually upgradepkg the kernel packages and reboot into the new > kernel without modifying any u-boot config? I don't know but I think yes, in debian for sure I've already apt-get upgraded the kernel. However this is a test for Richard and Cristophe. > If you give me all the u-boot stuff, I can put the u-boot binaies on the > ftp site and link to them from the "device maintenance" page on the web > site. > I'm not sure where I'd put the modifying of the u-boot environment/rescue > thing. The rescue thing is not necessary and I would avoid it. It's just a matter of the uboot. *Maybe* we could have a page on armedslack web site like this one: http://jeff.doozan.com/debian/uboot/ and hosting an adjusted script like this http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh which pulls out things from the armedslack website instead of doozan.com We should inform doozan though. :-) the fw_printenv stuff I don't think is really needed, if we could patch the uboot to have the special bootline needed for the dockstar... I agree, it's a lot of work anyway but dockstars are nice! :-) Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Thu, Jan 27, 2011 at 01:01, Rich wrote: > On 01/26/2011 03:39 AM, Claudio Cavalera wrote: >> >> Is it possible to host the jeff uboot on armedslack.org without >> breaking any license? >> > > Why would you need to do this?. Just get it off of Jeff site Maybe it's better to be on our own concerning stuff to be downloaded, but I'm not sure. Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Hello
On Sun, Mar 13, 2011 at 07:13, Davide wrote: > Hi, > my name is David and I'm new here so please forgive me if I ask odd questions > in odd places. > > I'm wondering if the seagate dockstar is amongst the fully supported devices ? Hello! If you look in the ML archive you should find lot of information about armed slack on the dockstar. I'm not sure it's officially supported, there was some plan to build a semi-automatic installer script like the one at jeff.doozan.com for debian but we are always short on time. I think the kernel needs some patches in any case if you want the led to work meaningfully, see for example at: http://dev.shyd.de/2011/01/seagate-dockstar-debian-squeeze/ Ciao, Claudio ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Improving USB audio sound quality on the Dockstar
On 05/05/2011, Andrzej Telszewski wrote: > On 05/05/2011 10:32 AM, Thorsten Mühlfelder wrote: >> Hi, >> >> I'm using a high quality USB audio device (Burr-Brown Japan PCM2702) with >> my >> Dockstar. I've configured mpd to use the hardware interface without dmix >> because dmix seems to be broken on the ARM platform. >> >> But there is one problem left: sometimes clicks and pops can be heard. >> They >> appear randomly up to 2 times a minute. My impression is that hard disk >> data >> transfer causes them, because using "hdparm -t" makes the situation worse. >> On >> the Dockstar all USB devices are connected via hub to the same USB >> controller: >> # 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 0bc2:2120 Seagate RSS LLC >> Bus 001 Device 005: ID 08bb:2702 Texas Instruments Japan Speakers >> >> Is it possible to give the USB audio data transfers a higher priority? >> > > Hi, > > You might try 'chrt', but you need to find the process(es) ID(s) > responsible for all the audio stuff. Eventually, check here: > > http://subversion.ffado.org/wiki/IrqPriorities > > but it's rather about real-time Linux. > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > ___ > 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
