Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Thu, Jan 27, 2011 at 01:01, Rich richard.lapoi...@gmail.com 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] ARMedSlack on Seagate Dockstar
On Thu, Jan 27, 2011 at 7:35 AM, John O'Donnell unixjohn1...@gmail.com wrote: On 01/26/2011 08:25 PM, Rich wrote: The dockstar led is controlled by uboot and armedSlack's kernel doesn't know how to control it. I'd be willing to bet it is controlled by standard kernel settings. I control my guruplug's LEDs in /sys/class/leds Take a peek In /sys/class/leds, I can only see: plug:green:health If I try: echo heartbeat /sys/class/leds/plug\:green\:health/trigger -bash: echo: write error: Invalid argument # uname -a Linux dockstar 2.6.33.5-kirkwood #2 PREEMPT Thu May 27 14:47:11 BST 2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux Christophe ___ 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 m-li...@biscuit.org.uk 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
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 :-) ___ 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 m-li...@biscuit.org.uk 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
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. What does official support mean? 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 Can you actually upgradepkg the kernel packages and reboot into the new kernel without modifying any u-boot config? 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. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
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! :-) Hah. I'd not put a Dockstar on it, that's for sure :-) On a serious note: I'm very cautious about expanding the range of official (meaning it works out of the box and I endevour to make sure the OS works on it) supported devices, due to a mixture of time and interest. My thoughts are that if someone's interested in a device then they can check whether the new packages work (usually kernels and x11 would be device specific) and let me know. 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. OK - give me a diff to the INSTALL_KIRKWOOD doc and I'll look at it. *Maybe* we could have a page on armedslack web site like this one: http://jeff.doozan.com/debian/uboot/ You mean like this? http://www.armedslack.org/maint_kirkwooduboot and hosting an adjusted script like this http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh Can't you just use nandwrite from the u-boot console? The script looks far too complicated: - can't you just use nandwrite from the u-boot console? - or use the mtd tools in linux to write it? I don't like tools which download stuff from web sites and try to automate things. My preference is to include simple, pasteable commands. (which may happen to include wget); but it's nicer to let the user see what's going on. I agree, it's a lot of work anyway but dockstars are nice! :-) Nice as paper weights, yes ;-)___ 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 2:11 AM, Rich richard.lapoi...@gmail.com 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. The installed system doesn't boot because there is no real time clock in the dockstar and hence all the files have dates of 1969. What's happen is when the system is booting it tries to check the root file system and gets an unexpected inconsistency and requires users input to do a manual fsck on the file system. If you had a serial line you would be able to type in the root password and then continue doing a fsck. Once completed, it would reboot into the system. The way around this is to a add this file to the /etc directory. ftp://laprjns.com/in/e2fsck.conf OK, I have added this file. Belongs to root, permissions 644. Apparently this configuration file tells fsck to ignore bad file dates. You should add this at the end of the install before rebooting. I would also suggest at this time you make the necessary changes to start the ntp daemon on boot up. Just do a chmod +x /etc/rc.d/rc.ntpd along with making the necessary change to /etc/ntp.conf. It should boot after this. What are exactly the necessary changes? I have only uncommented the line server pool.ntp.org When I reboot, nothing has changed :-( uboot says 'starting kernel' and then nothing more. At the same time, the dockstar usb key stop blinking. However I have noticed that e2fsck finds tons of errors like Inode 81277 was part of the orphaned inode list. IGNORED. I have repeated the whole install process (+mke2fs before) several times, and I always get this kind of errors. They are reported by both arm native e2fsck on the dockstar when my usb key is attached to it, and by my x86 desktop PC. It seems very strange to me. I can't reformat it during the install process, otherwise it will the installer given that it contains /boot, right? How long did it take for you installation? I been using an Adata 4G usb stick and it took hours to install the packages. Base on that I really not sure that this is a viable way to install armedSlack on the dockstar. I am using a noname 4GB usb key, formatted as 3.5GB ext3, 500MB swap. I did not install Qt/KDE, nor X/XAP, nor games, nor TeX. It takes about 2h. The step 'processing 1002 packages' takes about 5 minutes. As for the serial cable, here's where I got mine. http://cgi.ebay.com/NEW-Data-Cable-Nokia-6101-6102-6102i-6103-CA-42-/200353624748?pt=PDA_Accessorieshash=item2ea601b2ac It literally came on a slow boat from China :) :-) Thanks for the reference. And then, I have to do something like that, right? http://www.yourwarrantyisvoid.com/2010/07/21/seagate-dockstar-add-an-accessible-serial-port/ ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On 01/26/2011 06:11 AM, Stuart Winter wrote: Can you actually upgradepkg the kernel packages and reboot into the new kernel without modifying any u-boot config? Yes, as long as you changed the symbolic links to point to the new kernel and initrd. 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. Why not just leave there on Jeff's site and just put the link in the armedslack installation instructions I'm not sure where I'd put the modifying of the u-boot environment/rescue thing. Again, why not put it the instructions. Also you can ignore the rescue thing, it's needed. Jeff's has kind of a generic uboot with some environmental variables to boot his rescue system. If the rescue system is not installed the uboot just go on to the next thing to try and boot. Regards 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
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On 01/26/2011 08:59 AM, Stuart Winter wrote: *Maybe* we could have a page on armedslack web site like this one: http://jeff.doozan.com/debian/uboot/ You mean like this? http://www.armedslack.org/maint_kirkwooduboot and hosting an adjusted script like this http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh Can't you just use nandwrite from the u-boot console? The script looks far too complicated: - can't you just use nandwrite from the u-boot console? - or use the mtd tools in linux to write it? I don't like tools which download stuff from web sites and try to automate things. My preference is to include simple, pasteable commands. (which may happen to include wget); but it's nicer to let the user see what's going on. Both Debian and plugapps do their install by a mini root file system, not an installer like we're using. In Debian case, Jeff has created a completely automatic script, which I imagine is a lot of work to maintain. Plugapps uses instructions just i a wiki format http://plugapps.com/index.php5?title=Ten%28ish%29_steps_to_setting_up_a_Seagate_Dockstar All you need to do is copy and paste. I think that instructions is all that is needed. By the way, the uboot variables are only needed to boot the installer, they are not required once you go through an installation. Regards Rich Lapointe ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On 01/26/2011 04:41 PM, Christophe Lyon wrote: What are exactly the necessary changes? I have only uncommented the line server pool.ntp.org Edit the ntp.conf file to un-comment the server pool line like this: #server127.127.1.0# local clock #fudge127.127.1.0 stratum 10 server pool.ntp.org #server 192.168.101.1 When I reboot, nothing has changed :-( uboot says 'starting kernel' and then nothing more. You should not expect to see anything more on your netconsole once the armedSlack kernel starts to boot. Did you set up the network during in the installation?. Assuming you did need to open another terminal screen, change to root an ssh into the dockstar from there. If you set it up using dhcp then you'll have to check your router or something to see what ip it assigned to the dockstar. At the same time, the dockstar usb key stop blinking. The dockstar led is controlled by uboot and armedSlack's kernel doesn't know how to control it. However I have noticed that e2fsck finds tons of errors like Inode 81277 was part of the orphaned inode list. IGNORED. I have repeated the whole install process (+mke2fs before) several times, and I always get this kind of errors. They are reported by both arm native e2fsck on the dockstar when my usb key is attached to it, and by my x86 desktop PC. It seems very strange to me. I can't reformat it during the install process, otherwise it will the installer given that it contains /boot, right? yes, you can reformat during the install process. The installer gets loaded into ram and the usb stick is not used after loading; How long did it take for you installation? I been using an Adata 4G usb stick and it took hours to install the packages. Base on that I really not sure that this is a viable way to install armedSlack on the dockstar. I am using a noname 4GB usb key, formatted as 3.5GB ext3, 500MB swap. I did not install Qt/KDE, nor X/XAP, nor games, nor TeX. It takes about 2h. The step 'processing 1002 packages' takes about 5 minutes. Yes, about the same for me. As for the serial cable, here's where I got mine. http://cgi.ebay.com/NEW-Data-Cable-Nokia-6101-6102-6102i-6103-CA-42-/200353624748?pt=PDA_Accessorieshash=item2ea601b2ac It literally came on a slow boat from China :) :-) Thanks for the reference. And then, I have to do something like that, right? http://www.yourwarrantyisvoid.com/2010/07/21/seagate-dockstar-add-an-accessible-serial-port/ yea, or if you are not worry about looks and you don't mind having it connected all the time go to Radio shack and buy a wire wrap tool http://www.radioshack.com/product/index.jsp?productId=2103243CAWELAID=107590412 Regards Rich Lapointe ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On 01/26/2011 08:25 PM, Rich wrote: The dockstar led is controlled by uboot and armedSlack's kernel doesn't know how to control it. I'd be willing to bet it is controlled by standard kernel settings. I control my guruplug's LEDs in /sys/class/leds Take a peek -- === 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] ARMedSlack on Seagate Dockstar
OK, I've got a way of getting the installer started on my Dockstar without the use of a serial line. This method requires Jeff Doozan's uboot, first because it has uboot environments that allow to boot off a usb drive and second it installs fw_setenv and fw_print command line routines into the pogoplugs (and Dockstar) stock operating system. These are needed because there are some bootargs that need to be passed to slack installer to get the network up and a keyboard selected. Jeff's uboot environment includes a variable called usb_custum_params which can be used to pass these needed bootargs so that the installer doesn't get stuck. So here how it done: 1. SSH into the Dockstar stock operating system (pogoplug) 2. Install Jeff's uboot per these instructions http://jeff.doozan.com/debian/uboot/. After the new uboot is installed reboot into the pogoplug operating system and ssh back in. 3.Add the needed uboot environment parameters. fw_setenv usb_custom_params nic=auto:eth0:dhcp kbd=uk 4. Partition a drive with partition 1 (sda1) and format to ext2 file system. You may be able to use others types, but this is the only type I've tried. Mount the partition: mkdir /tmp/sda1 mount /dev/sda1 /mnt/sda1 5.Make a /boot directory on the new partition and copy the armedSlack installer and kernel to it mkdir /tmp/sda1/boot cd /tmp/sda1/boot wget ftp://ftp.slackware.org.uk/armedslack/armedslack-current/kernels/kirkwood/uImage-kirkwood wget ftp://ftp.slackware.org.uk/armedslack/armedslack-current/isolinux/uinitrd-kirkwood.img 6.Create some symbolic links Jeff uboot looks to boot uImage and uInitrd so do the following ln -s uImage-kirkwood uImage ln -s uinitrd-kirkwood.img uInitrd 7.Reboot! A word of warning, it took over three minutes to boot into the installer, but I think this depends on the usb device that you use. If you have questions, check the armedSlack irc channel, I'm usually log in. Regards Rich Lapointe On 01/21/2011 03:34 AM, Stuart Winter wrote: 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! :-) I was speaking to Richard on IRC and I don't think it's as simple as it seems. You wanted to do this without a serial cable: I don't think it's possible to use the proper slackware installer to install onto this device. You're going to need to set the boot parameters in order to tell the kernel where the root partition is, and stuff like that. This is done normally by setting the config in u-boot to match what partition scheme you have chosen. Of course if you follow my docs exactly then you can paste in the ones from my docs, since they will match the partition scheme (also suggested in the docs). However, if you want a custom partition scheme then you will need to be able to configure your boot loader to pass the root= parameter to the kernel. From reading the Debian stuff, my guess would be that the best way to proceed is to do something similar to what they've done: take the miniroot and write a script to set it up in the way that works best for the Doozan rescue system. You could then use slackpkg to upgrade the installation after the miniroot has been unpacked onto the device. They're not actually installing Debian using the debian installer. The easiest way is to get a serial cabl and stop faffing around ;-) ___ 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 Seagate Dockstar
On Sat, Jan 15, 2011 at 10:40, Stuart Winter m-li...@biscuit.org.uk 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
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? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
Am Tuesday 21 December 2010 03:37:12 schrieb Rich: On the initial boot, it did boot the kernel and started the system initialization scripts but then fdisk the sda1 and rebooted. The second boot did complete and I got a login prompt on the serial terminal. I wonder how it booted the second time? IIRC I had to comment out the fdisk sectionin a rc script because the Dockstar does not have an RTC and after reboot the system time is set to 1970 again which causes another fsck run (fsck is forced if umount time is later than mount time). This ends up in an endless loop. I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't configured. I edited to use dhcp USE_DHCP[0]=yes rebooted and was able to ssh into the dockstar Perhaps you remember that I've told you to do so ;-) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
Am Friday 14 January 2011 11:20:51 schrieb Stuart Winter: I wonder how it booted the second time? IIRC I had to comment out the fdisk sectionin a rc script because the Dockstar does not have an RTC and after reboot the system time is set to 1970 again which causes another fsck run (fsck is forced if umount time is later than mount time). This ends up in an endless loop. This is how to do this properly: cat EOF etc/e2fsck.conf # These options stop e2fsck from erroring/requiring manual intervention # when it encounters bad time stamps on filesystems -- which happens on # the Versatile platform because QEMU does not have RTC (real time clock) # support. # [options] accept_time_fudge = 1 broken_system_clock = 1 EOF Thanks! Looks like a much better and easier solution than editing the rc script ;-) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Tue, Dec 21, 2010 at 3:37 AM, Rich richard.lapoi...@gmail.com wrote: I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't configured. I edited to use dhcp USE_DHCP[0]=yes rebooted and was able to ssh into the dockstar Rich Lapointe Thanks! I confirm it also works for me. Christophe. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
I wasn't to sure how you got the installer running over ssh, so here's what I did. First, my dockstar is running Jeff Doozan latest uboot and Rescue System, so when I boot without any usb drives plugged in it boots into the Rescue System (http://forum.doozan.com/read.php?4,831). I connect to the dockstar via ssh (the rescue system starts dhcp). Although I do have the serial line running, I just use it to monitor what going on since I'm trying to figure out how to install armedslack without a serial line. (I've got two other dockstars waiting in the wings). Once I'm connected I do the following: Prepare a directory for change root file system 1) mkdir /tmp/armedslack 2) cd /tmp/armedslack Download the armedslack uinitrd (has the installer) and decompress it # wget ftp://ftp.armedslack.org/armedslack/armedslack-13.1/isolinux/uinitrd-kirkwood.img # dd if=uinitrd-kirkwood.img bs=64 skip=1 | gzip -dc | cpio -div Now thing get a little fuzzy for me, since I really don't have a deep knowledge of what I'm doing. I found through googling that I had to do the following mounts before I changed rooted into the installer fs. It seems to br needed to mount a usb stick and its the only way to get nano running; i don't know how to use vim . #mount /proc/ /tmp/armedslack/proc # mount /dev/ /tmp/armedslack/proc # chroot /tmp/armedslack /bin/bash #TERM=linux Now plug in a usb drive, run fdisk or cfdisk and partition the drive. Since I using Doozan uboot / needs to be on sda1. I partitioned my 4G usb stick with 3.75G sda1 for \ and sda2 as a 250M swap. OK, now run the armedslack installer. #./usr/lib/setup/setup This will resulted in running the armedslack installer. The only thing of note here is that I selected a ftp install and connect to the ftp.armedslack.org using its ip address (83.170.96.167). After successfully connecting to the repos, I then select the packages and the installer proceeds to install the packages. With my usb stick and depending on the packages selected this can take a few hours to install. I found that using my Seagate Freeagent 500GM disk loads much faster. Once everything is installed and the setup is complete (network, root password, services etc) I exit out of the installer and then add the following sym links since Doozan uboot looks for uImange and uInitrd to boot. #cd /boot # ln -s uinitrd-kickwood-2.6.35.5 uInitrd # ln -s uImage-kirkwood-2.6.35.5 uImage Then I exist out of the changed root environment and reboot the dockstar. After all this and with using the serial output to monitor the process, the kernel does boot but gets a fdisk error and stalls for 60 second and then reboots, repeating the sequence over and over. See the attached file for the boot output and fdisk error from the serial link. It seems to have something to do with the dockstar not having a real time clock and getting time stamp errors. I am able to fix this by doing the following. 1) Add the following line in rc.S right at the beginning /bin/mount -n -o remount,ro / 2) add an e2fsck,config file to /etc/. The file that i use can be found here. ftp://laprjns.com/in/e2fsck.conf Once I added these, rebooting results in going through a successful fdisk on the / fs. After completing the fdisk, it successfully reboots to the armedslack prompt. Since it's fdisk'ing and rebooting it does take a little while to come up . Also found that once I successfully booted, I then can remove both the mount line in rc.S and the e2fsck.con file and boot the system there after. I sure that there is a better way to get the installer running, but as I said my linux knowledge is limited. Regards Rich Lapointe (laprjns) On 12/21/2010 05:13 AM, Stuart Winter wrote: On Mon, 20 Dec 2010, Rich wrote: My testing indicates that it not getting an ip assign during initialization because the rc.inet1.conf file isn't configured I'm a wimp, so I've been using serial cable to observe what is happening. Since you have a serial cable, can you also try booting the installer? This is what the others have been struggling with -- why doesn't the installer get an IP? If you boot using the config lines found here: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt Take the line below this heading: -current (automatically starting DHCP and SSHd) The system should boot and get an IP from DHCP. Can you see what is happening? U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB NAND: 256 MiB In:serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Using egiga0 device host 192.168.101.22 is alive Uncompressing Linux... done, booting the kernel. [0.00] Linux version 2.6.33.5-kirkwood (r...@wizbit) (gcc version 4.4.4 (GCC) ) #2 PREEMPT Thu May 27 14:47:11 BST 2010 [0.00] CPU: Feroceon 88FR131 [56251311] revision 1
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Mon, 20 Dec 2010, Rich wrote: My testing indicates that it not getting an ip assign during initialization because the rc.inet1.conf file isn't configured I'm a wimp, so I've been using serial cable to observe what is happening. Since you have a serial cable, can you also try booting the installer? This is what the others have been struggling with -- why doesn't the installer get an IP? If you boot using the config lines found here: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt Take the line below this heading: -current (automatically starting DHCP and SSHd) The system should boot and get an IP from DHCP. Can you see what is happening? -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
My testing indicates that it not getting an ip assign during initialization because the rc.inet1.conf file isn't configured I'm a wimp, so I've been using serial cable to observe what is happening. Using a desktop with Linux (Salix OS) I partitioned a Memorex 2G USB Stick into two partitions, one (sda1) for the root file system and a second for a swap partitions. I untar'ed the mini file system on to sda1, edited fstab to have sda1 mounted / and sda2 as swap. I then added sym links for the kernel and initrd ln -s uImage-kirkwood-2.3.33.5 uImage ln -s unitrd-kirkwood02.6.33.5 uInitrd Then I plug the stick into my dockstar (using doozan uboot along with his rescue system) and booted it. I monitored the boot up process with a netconsole terminal and a serial terminal connection to the dockstar. The two file attached are the output of each of these terminals during the boot process. On the initial boot, it did boot the kernel and started the system initialization scripts but then fdisk the sda1 and rebooted. The second boot did complete and I got a login prompt on the serial terminal. The netconole terminal stop at Starting kernel.. , but did show the reboot into the second boot up and then again stop at starting kernel. Although it did boot to the login prompt, my router did not indicate that the dockstar was connected. Using the serial console, i looked in and checked ifconfig and fond that there was no ip Linux 2.6.33.5-kirkwood. Last login: Thu Jan 1 01:00:52 +0100 1970 on /dev/ttyS0. You have mail. r...@slackware:~# ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't configured. I edited to use dhcp USE_DHCP[0]=yes rebooted and was able to ssh into the dockstar Rich Lapointe On 12/10/2010 10:58 AM, Stuart Winter wrote: Does anyone know if the pre-compiled ARMedslackware kernel support netconsole? (If so, then it looks like the kernel boot crashes before netconsole is operational). It's compiled as a module, so you'd have to include it in the initrd. I've taken the latest code from kernel.SlackBuild (where the initrd's are made) and made this script: http://stash.armedslack.org/scripts/make-new-initrd.sh (This is useful for people in general, btw). This will make a new initrd for the *Operating system*, however, not the installer. There's no point in adding netconsole to the installer initrd because the installer's initrd is quite a different beast and if it's not making it as far as running the /etc/rc.d/rc.modules-arm script, then you're buggered. 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. In order to use netconsole with the installer you'd have to recompile the kernel to include netconsole and the ethernet driver into the kernel itself. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB NAND: 256 MiB In:serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Using egiga0 device host 192.168.101.22 is alive Uncompressing Linux... done, booting the kernel. [0.00] Linux version 2.6.33.5-kirkwood (r...@wizbit) (gcc version 4.4.4 (GCC) ) #2 PREEMPT Thu May 27 14:47:11 BST 2010 [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: Marvell SheevaPlug Reference Board [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [0.00] PID hash table entries: 512 (order: -1, 2048 bytes) [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Memory: 128MB = 128MB total [0.00] Memory: 117688KB available (3760K code, 559K data, 124K init, 0K highmem) [0.00] Hierarchical RCU implementation. [0.00] NR_IRQS:114 [0.00] Console: colour dummy device 80x30 [0.000179] Calibrating delay loop... 1192.75
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Fri, Dec 10, 2010 at 5:06 PM, Claudio Cavalera claudio.caval...@gmail.com wrote: I have it when I run lsmod in the debian mv643xx_eth For the record, I have also noticed that under Debian the kernel version is a bit older: r...@debian:~# uname -a Linux debian 2.6.32-5-kirkwood #1 Fri Nov 26 07:01:06 UTC 2010 armv5tel GNU/Linux The modules loaded are: r...@debian:~# lsmod Module Size Used by ipv6 253826 10 hmac2475 0 sha1_generic1717 0 mv_cesa 9262 0 aes_generic32820 1 mv_cesa ext2 55411 1 mbcache 4860 1 ext2 sd_mod 31312 3 crc_t10dif 1106 1 sd_mod usb_storage34879 2 scsi_mod 119252 2 sd_mod,usb_storage ehci_hcd 35579 0 usbcore 122203 3 usb_storage,ehci_hcd mvsdio 5318 0 nls_base5367 1 usbcore mv643xx_eth22562 0 mmc_core 50206 1 mvsdio libphy 14836 1 mv643xx_eth inet_lro5060 1 mv643xx_eth configfs 20841 0 # 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 : Christophe. ___ 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 4:58 PM, Stuart Winter m-li...@biscuit.org.uk wrote: It's compiled as a module, so you'd have to include it in the initrd. Maybe the netconsole feature would be more useful as a builtin instead of as a module in this specific case (i.e. don't get ARMedSlack booting on Dockstar and don't use a serial console), since the kernel may run into troubles before the load of the module. Christophe, I should be able to provide you a kernel with the netconsole as a builtin on Monday if you wish. Will you give it a try with ARMedSlack mini-rootfs and investigate what's going on? Regards, Cédric. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
Maybe the netconsole feature would be more useful as a builtin instead of as a module in this specific case (i.e. don't get ARMedSlack booting on Dockstar and don't use a serial console), since the kernel may run into troubles before the load of the module. This means you also need to compile the network driver into the kernel. In the kernel I only want to include drivers that really cannot be modules, so I'll keep the NIC drivers as modules. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
On Sat, Dec 11, 2010 at 11:28 AM, Stuart Winter m-li...@biscuit.org.uk wrote: This means you also need to compile the network driver into the kernel. Thanks for the advice. In the kernel I only want to include drivers that really cannot be modules, so I'll keep the NIC drivers as modules. I do agree with you, that was just a suggestion for debug purpose in this specific case. Does someone know if there is a reliable support for in-memory kernel core dump on ARM? It could be useful too. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
2010/12/11 Cédric VINCENT cedric.vinc...@gmail.com: Christophe, I should be able to provide you a kernel with the netconsole as a builtin on Monday if you wish. Will you give it a try with ARMedSlack mini-rootfs and investigate what's going on? Yes, it could be useful, thanks! ___ 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 12:30 AM, Claudio Cavalera claudio.caval...@gmail.com wrote: On Thu, Dec 9, 2010 at 21:02, Christophe Lyon christophe.l...@gmail.com 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= ? As I said, I used Jeff Doozan's script to update my uboot, which also sets to boot parameters. I have: usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x80 0 1; ext2load usb $usb_device 0x80 /boot/uImage; if ext2load usb $usb_device 0x110 /boot/uInitrd; then bootm 0x80 0x110; else bootm 0x80; fi (usb_device is set to 0:1 by usb_scan) bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset (I copied only the usb_bootcmd part, as it is the only relevant one here) I have tried to add netconsole parameters to usb_set_bootargs, with no effect. Christophe. ___ 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 christophe.l...@gmail.com 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
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. Indeed, I'd like to avoid tftp if it's not absolutely necessary... and I don't see why it would be. Does anyone know if the pre-compiled ARMedslackware kernel support netconsole? (If so, then it looks like the kernel boot crashes before netconsole is operational). Christophe. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
Does anyone know if the pre-compiled ARMedslackware kernel support netconsole? (If so, then it looks like the kernel boot crashes before netconsole is operational). It's compiled as a module, so you'd have to include it in the initrd. I've taken the latest code from kernel.SlackBuild (where the initrd's are made) and made this script: http://stash.armedslack.org/scripts/make-new-initrd.sh (This is useful for people in general, btw). This will make a new initrd for the *Operating system*, however, not the installer. There's no point in adding netconsole to the installer initrd because the installer's initrd is quite a different beast and if it's not making it as far as running the /etc/rc.d/rc.modules-arm script, then you're buggered. 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. In order to use netconsole with the installer you'd have to recompile the kernel to include netconsole and the ethernet driver into the kernel itself. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
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? /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. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
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. Then, once it's fixed, you can forget that you ever used it and pretend like everything worked first time. http://www.hypnosis101.com/amnesia.htm Easy. Let's get to it! :-) ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
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. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] ARMedSlack on Seagate Dockstar
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 :-( ___ 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 christophe.l...@gmail.com 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
