**** BEGIN LOGGING AT Sat Sep 03 02:59:57 2005 Sep 03 06:24:37 hi Sep 03 06:25:38 is there anyone that can discuss/enlighten an item on the InitialisingOpenSlug wiki page? Sep 03 06:29:53 only if you ask the question first :) Sep 03 06:31:35 ok Sep 03 06:32:10 the wiki page suggests using dhcp for the slug (if you have a dchp server) instead of static ip. Sep 03 06:32:45 What is the rationale for this? I think I prefer a static address anyway (so I know its address) Sep 03 06:33:06 dhcp can give static addresses too Sep 03 06:33:36 it saves you from editing configs on the slug Sep 03 06:33:44 hmm. don't know if my router will Sep 03 06:33:48 lemme check Sep 03 06:34:24 * koen|train uses ipv6, much cleaner Sep 03 06:34:37 nope its a simple thing that does not allow reservation or so Sep 03 06:35:31 ipv6 is cool, but I'm not sure how to get to that (and whether I want to add a device or so to do ipv6/ipv4 conversion (as my isp is v4) Sep 03 06:36:28 anyway, using dhcp or not is a personal preference, not a prerequisite for using openslug Sep 03 06:36:31 anyway, is the suggestion to use dhcp on the wiki a good idea? Sep 03 06:37:03 I know this is not a prereq, but it is indicated on the wiki Sep 03 06:37:18 If you have a DHCP server on your network you should use dhcp as the boot protocol, not static (which is the default). Sep 03 06:37:27 that is what the wiki says Sep 03 06:37:45 (i'm moving to openslug in another window...) Sep 03 06:38:01 (so I am reading all this quite carefully). Sep 03 06:38:17 I felt inclined to change the wiki, but I was unsure if this was not there for a good reason Sep 03 06:51:00 OK. Made the change. If anyone can review the change that would be nice. Sep 03 06:51:00 http://www.nslu2-linux.org/wiki/OpenSlug/InitialisingOpenSlug Sep 03 07:19:39 Hm. I just did a turnup disk but when I reboot I do not reboot from the new partition but still from the flash. Sep 03 07:19:44 The wiki just says: Reboot to the new disk partition Sep 03 07:19:51 What should I do to accomplish this? Sep 03 07:20:07 type 'reboot' Sep 03 07:20:26 I did Sep 03 07:21:26 df still has /dev/mtdblock4 on / Sep 03 07:21:34 root@NSLU2:/etc# df Sep 03 07:21:34 Filesystem 1k-blocks Used Available Use% Mounted on Sep 03 07:21:34 /dev/mtdblock4 6528 5468 1060 84% / Sep 03 07:21:34 tmpfs 15340 24 15316 0% /var Sep 03 07:21:34 tmpfs 15340 0 15340 0% /media/ram Sep 03 07:21:35 /dev/sda1 155844268 102303272 53540996 66% /mnt Sep 03 07:21:51 and I still get the tmpfs although turnup said it will be disabled. Sep 03 07:22:18 Only odd thing I did was turnup to /dev/sda5 (as I did not loose all existing data that was already in /dev/sda1) Sep 03 07:30:12 try looking into /linuxrc Sep 03 07:30:50 interesting, was just looking where I could find this. Sep 03 07:30:52 It says: Sep 03 07:30:52 #!/bin/sh Sep 03 07:30:53 exec '/boot/disk' '/dev/sda5' '-t' 'ext3' '-o' 'defaults' Sep 03 07:30:53 exec /boot/flash Sep 03 07:32:32 looks like booting from disk fails Sep 03 07:32:50 sda5 exists Sep 03 07:33:00 root@NSLU2:/dev# ls -l sda5 Sep 03 07:33:00 brw-rw---- 1 root root 8, 5 Oct 3 16:08 sda5 Sep 03 07:33:15 try mounting it to /mnt Sep 03 07:33:47 should it also be rw for other ??? Sep 03 07:33:52 oops forgot return Sep 03 07:33:57 it is now mounted to /mnt Sep 03 07:34:12 looks good: Sep 03 07:34:12 root@NSLU2:/dev# cd /mnt Sep 03 07:34:12 root@NSLU2:/mnt# ls Sep 03 07:34:12 bin home lost+found proc sys var Sep 03 07:34:12 dev initrd media root tmp Sep 03 07:34:12 etc lib mnt sbin usr Sep 03 07:34:47 ls -la /mnt Sep 03 07:35:01 see if a .recovery exists Sep 03 07:35:27 no .recovery Sep 03 07:35:32 actually no . files at all Sep 03 07:35:38 weird Sep 03 07:35:46 should it be there? Sep 03 07:35:56 it shouldn't :) Sep 03 07:37:41 ok. i think i broke it Sep 03 07:38:20 i issued the cmd manually and I got: Sep 03 07:38:20 root@NSLU2:/# /boot/disk /dev/sda5 -t ext3 -o defaults Sep 03 07:38:20 boot: rootfs: mount -t ext3 -o defaults /dev/sda5 Sep 03 07:38:47 after that df does not work any more: /proc/mounts: no such file or directory Sep 03 07:39:21 rebooting, stay tuned... Sep 03 07:45:19 reboot didn't help Sep 03 07:50:16 wb ByronT Sep 03 08:03:40 apparently I've nuked by slug, away for a while to switch ip addresses and reflash Sep 03 08:13:56 back in business; instrumented /boot/disk. Let's see where it fails ... Sep 03 08:59:07 hmm, i'm now continuously stuck at amber flashing Sep 03 08:59:14 this is both the case if the disk is attached or not Sep 03 08:59:26 is there anything I can do to fix this? Sep 03 09:20:35 effem, do you have serial? Sep 03 09:27:43 no Sep 03 09:27:52 sorry for responding late, was watching thenews Sep 03 09:29:08 without serial it's a bit hard to figure out what is dying/hanging/etc. Sep 03 09:29:39 so self rescue (w/o serial) tends to be of the flash known good firmware and start over Sep 03 09:29:42 yeah I know but we didn't manage to open up the holes to put a connector Sep 03 09:29:51 i was planning to do so Sep 03 09:30:08 solder sucker is what I've used Sep 03 09:30:13 brb Sep 03 09:30:15 5 times so far Sep 03 09:30:55 going to reflash Sep 03 09:31:22 its upgrading Sep 03 09:31:47 we used sucking wire (don't know if this is the good name) but managed to open only one hole. Sep 03 09:31:59 we did install the always on mod and turbo-ed it Sep 03 09:32:09 so(l)derwick Sep 03 09:32:29 I changed/instrumented /boot/disk to write to /mnt after mounting the disk Sep 03 09:32:39 but now it doesn't come through Sep 03 09:32:40 yeah, solderwick is a PITA to use sometimes Sep 03 09:33:00 you used a sucker pump? Sep 03 09:33:11 I used the patented Percussion solder removal method ;) Sep 03 09:33:14 soldersuckers are less precise but seem to be more effective Sep 03 09:34:02 the problem I had with the slug was that it would not boot from disk even though I did a turnup Sep 03 09:34:24 so somewhere in /boot/disk something did not seem to work Sep 03 09:34:46 after doing the turnup I was still booting from flash Sep 03 09:39:25 ok. it is reflashed and I am logged in Sep 03 09:46:43 re-init-ed, and recopied the root fs. No success. Sep 03 09:47:03 odd Sep 03 09:47:09 It seems the disk is not accessed at all. It is on usb1. The partition I am using is /dev/sda5 Sep 03 09:47:33 if you mount /dev/sda5 manually? Sep 03 09:47:58 fine, no .recovery file or any other . file Sep 03 09:48:07 but the filesystem looks "ok" Sep 03 09:48:08 ? Sep 03 09:48:35 this is a brand new openslug image? Sep 03 09:48:38 the fs looks ok Sep 03 09:48:50 fsck told: /dev/sda5 was not cleanly unmounted, check forced. Sep 03 09:48:57 shouldn't matter Sep 03 09:49:12 this is the binary image loaded from the web. It is my first attemt at openslug Sep 03 09:49:18 aha, ok Sep 03 09:49:19 attempt Sep 03 09:49:52 I did follow the wiki instructions. Sep 03 09:49:56 the only thing not very clear was: Sep 03 09:49:57 Reboot to the new disk partition. Sep 03 09:50:11 but I learned later that linuxrc will take care of that Sep 03 09:50:33 There's no error output when you run turnup? Sep 03 09:51:11 nope, this is what I got: Sep 03 09:51:15 root@NSLU2:~# turnup disk -f -i /dev/sda5 -t ext3 Sep 03 09:51:15 /usr/sbin/turnup: umounting any existing mount of /dev/mtdblock4 Sep 03 09:51:15 turnup: copying root file system Sep 03 09:51:15 16920 blocks Sep 03 09:51:15 done Sep 03 09:51:16 turnup: initialising dev file system Sep 03 09:51:18 turnup: tmpfs will no longer be mounted on /var Sep 03 09:51:20 turnup: /etc/syslog.conf: changed to file buffering Sep 03 09:51:22 Old (buffer) version in /etc/syslog.conf.sav Sep 03 09:51:24 Log messages will be in /var/log/messages Sep 03 09:51:26 (sorry for the long paste) Sep 03 09:52:00 thinking of it, could it be related to the swap space or where it is? Sep 03 09:52:09 I don't think I have any swap space active Sep 03 09:52:50 or should I add a sleep to /boot/disk to give the system time to detect the hd?? Sep 03 09:52:58 try that Sep 03 09:53:12 swap shouldn't affect it Sep 03 09:54:27 ok, added a sleep 5 to /boot/disk Sep 03 09:54:34 let's see what that brings Sep 03 09:54:41 brb Sep 03 09:56:07 didn't help. I don't think there was any disk activity Sep 03 09:58:17 and you don't have serial? Sep 03 09:58:25 nope, wish I had Sep 03 10:00:18 added a few echo's that write to the disk and reboot Sep 03 10:05:29 hm. added a few echo's in /boot/disk after the disk is mounted and now I cannot get beyond the red led stage Sep 03 10:05:42 even if I remove the disk and reboot Sep 03 10:06:01 flash again then see if something has been scribbled on the disk (I saw one access) Sep 03 10:22:06 hm dumped the mount command in /boot/disk Sep 03 10:22:08 it reads: Sep 03 10:22:09 mount -t ext3 -o defaults /dev/sda5 Sep 03 10:22:21 if I do this manually it complains that /dev/sda5 is not in fstab Sep 03 10:22:26 heh, yes Sep 03 10:22:29 should turnup disk have added this? Sep 03 10:22:34 it should be mounted somewhere Sep 03 10:22:48 it is mounted in /boot/disk Sep 03 10:23:20 it says: Sep 03 10:23:21 # Mount read-write because before exec'ing init Sep 03 10:23:21 # this script creates the '.recovery' link to Sep 03 10:23:21 # detect failed boot. No file type is given to Sep 03 10:23:21 echo mount "$@" "$device" >log Sep 03 10:23:21 if mount "$@" "$device" /mnt Sep 03 10:23:35 I added the echo Sep 03 10:23:40 the mount command should be "mount -e ext3 -o defaults /dev/sda5 /mnt" Sep 03 10:23:57 ah, yeah, you forgot /mnt before the echo Sep 03 10:24:08 so it doesn't know where to mount it Sep 03 10:24:13 is it -e ext3 ? Sep 03 10:24:15 or -t Sep 03 10:24:22 t Sep 03 10:24:50 ok if I add that to log it indeed mounts Sep 03 10:30:32 hm, an echo after the mount does not succeed .... Sep 03 10:30:49 could this be due to the fact that I am using /dev/sda5 ?? (i.s.o. /dev/sda1) Sep 03 10:31:00 that shouldn't matter at all Sep 03 10:31:22 that Sep 03 10:31:25 s what I expected Sep 03 10:31:37 I'm stumped Sep 03 10:32:39 it is the mount that is failing Sep 03 10:33:07 added || echo mountfailed >/log to the script and the echo was done Sep 03 10:34:10 but mounting it manually on /mnt works? Sep 03 10:34:27 yes Sep 03 10:34:54 this is what I get from the mount in /boot/disk: Sep 03 10:34:55 mount: Mounting /dev/sda5 on /mnt failed: No such file or directory Sep 03 10:35:07 does /dev/sda5 exist? Sep 03 10:35:31 yes and so does /mnt Sep 03 10:35:31 root@NSLU2:/# ls -lsd /dev/sda /mnt Sep 03 10:35:31 0 brw-rw---- 1 root root 8, 0 Oct 3 19:23 /dev/sda Sep 03 10:35:31 0 drwxr-xr-x 2 root root 0 Oct 3 19:21 /mnt Sep 03 10:35:52 oops lets make that /dev/sda5 Sep 03 10:35:52 root@NSLU2:/# ls -lsd /dev/sda5 /mnt Sep 03 10:35:52 0 brw-rw---- 1 root root 8, 5 Oct 3 19:23 /dev/sda5 Sep 03 10:35:52 0 drwxr-xr-x 2 root root 0 Oct 3 19:21 /mnt Sep 03 10:36:00 and manually it works Sep 03 10:36:04 I am flabbergasted Sep 03 10:36:30 ok. have to quit as I have to go. more tomorrow. Sep 03 10:36:35 thanks a lot! Sep 03 10:36:37 np Sep 03 10:37:42 hi all Sep 03 10:38:05 where can I get from just the compiler and cross compiler for armbe? **** ENDING LOGGING AT Sun Sep 04 02:59:56 2005