**** BEGIN LOGGING AT Sun Nov 26 02:59:57 2006 Nov 26 03:46:41 03bzhou * r4553 10optware/trunk/make/nano.mk: nano: 1.2.5 -> 2.0.1, latest template **** BEGIN LOGGING AT Sun Nov 26 05:45:37 2006 **** BEGIN LOGGING AT Sun Nov 26 06:19:27 2006 Nov 26 06:35:14 03mwester * r584 10kernel/trunk/patches/2.6.19/ (77-dsmg600-cmdline.patch series): Add 77-dsmg600-cmdline.patch; fixup the default command line for the DSM-G600 Nov 26 07:32:23 03mwester * r585 10kernel/trunk/patches/2.6.19/77-dsmg600-cmdline.patch: dsmg600-setup.c: Ensure command line fixup is actually executed. Nov 26 09:14:06 03rwhitby * r79 10slugimage/trunk/slugimage: slugimage: moved microcode to SysConf partition Nov 26 09:15:37 yes, tonight's the night that the microcode moves from FIS directory to SysConf. Nov 26 09:19:00 03rwhitby * r586 10kernel/trunk/ (7 files in 2 dirs): Initial apex slugos configuration support Nov 26 09:19:24 03rwhitby * r587 10kernel/trunk/patches/2.6.19/43-nslu2-mtd-microcode.patch: Moved NLSU2 microcode from FIS directory to SysConf Nov 26 09:26:42 03rwhitby * r588 10kernel/trunk/patches/2.6.19/43-nas100d-mtd-microcode.patch: nas100d: Moved microcode to sysconf partition Nov 26 10:30:36 Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e0000 Nov 26 10:30:36 RedBoot directory 0x507e0000(0x20000) native Nov 26 10:30:36 6 RedBoot partitions found on MTD device IXP4XX-Flash.0 Nov 26 10:30:36 Creating 6 MTD partitions on "IXP4XX-Flash.0": Nov 26 10:30:36 0x00000000-0x00040000 : "RedBoot" Nov 26 10:30:36 nslu2 mac: 00:04:5a:0f:b2:c6 Nov 26 10:30:38 0x00040000-0x00060000 : "SysConf" Nov 26 10:30:40 npe: searching for firmware... Nov 26 10:30:42 npe: found at 0x1c000, IXP425/NPE-B func: 00, rev: 2.1, size: 11964, id: 01000201 Nov 26 10:30:44 npe: firmware loaded to NPE-B, func: 00, rev: 2.1, status: 80800000, crc: 14cb Nov 26 10:30:46 0x00060000-0x00080000 : "Loader" Nov 26 10:30:50 0x00080000-0x001c0000 : "Kernel" Nov 26 10:30:52 0x001c0000-0x007e0000 : "Flashdisk" Nov 26 10:30:54 0x007e0000-0x00800000 : "FIS directory" Nov 26 10:48:26 Hmm - putting microcode in SysConf on NSLU2 makes it quite difficult for the very first flash - how do you get the microcode on the device in the first placea/ Nov 26 11:05:32 03rwhitby * r589 10kernel/trunk/patches/2.6.19/ (43-nas100d-mtd-microcode.patch 43-nslu2-mtd-microcode.patch): Moved nslu2 microcode back to FIS directory, and moved NAS100d microcode to the kernel partition (as you can just append it to the kernel image in the 2MB of space). Nov 26 11:06:35 03rwhitby * r80 10slugimage/trunk/slugimage: Moved microcode back into the FIS directory Nov 26 11:50:40 * rwhitby flashes stock firmware onto NAS100d to devise a stock to slugos upgrade procedure ... Nov 26 17:16:54 03bzhou * r4554 10optware/trunk/make/py-kid.mk: py-kid: 0.9.3 -> 0.9.4; latest template; added py25- Nov 26 19:12:33 03bzhou * r4555 10optware/trunk/make/automake.mk: automake: 1.9.6 -> 1.10; latest template Nov 26 21:09:38 anyone seen this error from turnup: Nov 26 21:09:54 root@brokenslug:~$ turnup disk /dev/sda1 Nov 26 21:09:54 devio: d: input device number unknown Nov 26 21:09:54 /sbin/turnup: : device number is not valid, cannot continue. Nov 26 21:18:47 jacques: I seem to remember that error being one of the scripts using the wrong name for the target partition (in mtd) for one of the commands it does in preparation for changing flash contents to indicate the turnup preference Nov 26 21:20:15 I have a sysconfig partition Nov 26 21:20:40 not sure what other ones it would need to touch Nov 26 21:22:15 nad100d? Nov 26 21:22:21 s/nad/nas Nov 26 21:22:42 mwester, yep Nov 26 21:22:47 mwester-laptop, yep Nov 26 21:25:02 it would help if devio commands didn't look like this )*&^VP(BYN4P9&(p*o^%$#&e^^^hjbb^$cw%epo*ybM Nov 26 21:25:14 it would help a lot. Nov 26 21:26:01 hehe - I haven't had to mess with any of those yet... Nov 26 21:26:44 I don't intend to. Nov 26 21:29:57 I'm looking at the turnup script and I Don't see where it's getting that error Nov 26 21:30:31 the string "device number" does not appear in /sbin/turnup Nov 26 21:31:00 back to building up the build machine :D Nov 26 21:34:00 I tried linking /linuxrc to /boot/disk but it still booted to flash Nov 26 21:37:00 what is a uuid? Nov 26 21:37:12 disk [-i] [-s] | [mount options] Nov 26 21:39:04 it's mentioned in turnup help but not explained/defined in any way Nov 26 21:41:33 uuid is the unique id of the partition, used to locate it. Nov 26 21:42:02 Do you have "init=/linuxrc" in your command-line when booting? Nov 26 21:43:25 Also, check the module utilities in /etc/default (on the jffs2 device), it might be that a modprobe kernel-module-pata-artop is required (the dsmg600 needed that, otherwise the disk was mounted waaay too late int eh boot.) Nov 26 21:44:33 root@brokenslug:/$ cat /proc/cmdline Nov 26 21:44:33 root=/dev/mtdblock2 rootfstype=jffs2 init=/linuxrc rtc-pcf8563.probe=0,0x51 noirqdebug console=ttyS0,1152 Nov 26 21:44:33 00n8 Nov 26 21:45:27 03oleo * r4556 10optware/trunk/ (Makefile make/tor.mk): optware: tor initial import Nov 26 21:45:37 mwester-laptop, that last thing you said sounds like it might be it Nov 26 21:46:11 what's the kernel-module-pata-artop string? Nov 26 21:46:27 I mean, that's not the module's name... Nov 26 21:46:38 I commited a fix for that for the dsmg600 last night. I think it added "modprobe kernel-module-pata-artop" Nov 26 21:46:48 Should be the same on the 100d Nov 26 21:48:20 shouldn't it just be 'modprobe pata_artop' ? Nov 26 21:51:30 Er, sorry - you are correct. Nov 26 21:52:38 that had no effect that I can tell Nov 26 21:52:52 it's like the boot/disk stuff is being bypassed Nov 26 21:53:50 probably related to turnup failure Nov 26 22:00:24 /boot/disk does this: if test -n "$1" Nov 26 22:00:24 where does $1 come from Nov 26 22:00:42 # boot from the hard disk partition "$1" (which Nov 26 22:00:42 # must be given) using options from the rest of Nov 26 22:00:42 # the command line. Nov 26 22:00:55 doesn't really tell me anything useful Nov 26 22:01:02 given how? Nov 26 22:01:35 if $1 wasn't set, it would bypass all the disk boot like it is doing Nov 26 22:05:54 isn't this command: sed -n 's!^Hardware *: !!p' /proc/cpuinfo Nov 26 22:06:03 supposed to output something? Nov 26 22:06:11 /boot/disk is called from /linuxrdc Nov 26 22:06:38 Yeah that command is strange; I don't how it works. But it seems to. Nov 26 22:07:17 how can you tell? Nov 26 22:07:49 for example, how could I tell if it was working on my system? Nov 26 22:08:24 the conditionals in /etc/default/moduleutils (or something) to load the required modules seem to work when I added the correct incantations for the DSM-G600. Nov 26 22:08:29 it had no effect for me Nov 26 22:08:38 so for all I know that's not working Nov 26 22:09:31 It sure made a difference for me; I added and removed lines in a conditional I added to load modules for the dsmg600 and observed the differences (like, modules wouldn't load if I commented them out). Nov 26 22:12:34 well, I'm out of time to mess with this. Nov 26 22:21:27 if a partition doesn't have a UUID is that bad? Nov 26 22:21:44 I get a different error when I try turnup by UUID Nov 26 22:21:51 root@brokenslug:/boot$ blkid Nov 26 22:21:51 /dev/sda1: TYPE="reiserfs" Nov 26 22:21:51 /dev/sda2: UUID="3afae03d-99bf-4534-9c93-86501cac5989" TYPE="reiserfs" Nov 26 22:21:51 /dev/sda3: TYPE="swap" Nov 26 22:21:51 /dev/sda4: TYPE="reiserfs" Nov 26 22:22:10 root@brokenslug:/boot$ turnup disk 3afae03d-99bf-4534-9c93-86501cac5989 Nov 26 22:22:10 turnup disk: 3afae03d-99bf-4534-9c93-86501cac5989: block device required Nov 26 22:22:22 but /dev/sda1 is my boot partition Nov 26 22:22:58 at least I can find "block device required" in the scripts Nov 26 22:23:14 unlike "device number" Nov 26 22:23:57 device="$1" Nov 26 22:23:57 test -n "$device" -a -b "$device" || { Nov 26 22:23:57 echo "turnup disk: $device: block device required" >&2 Nov 26 22:23:57 return 1 Nov 26 22:23:57 } Nov 26 22:24:12 tho I'm not sure it's doing the right thing Nov 26 22:24:31 how does it know whether it was given a UUID or device name ? Nov 26 22:26:06 I don't know how to debug these things - how do I get the return value of test on the command line? Nov 26 22:32:49 echo $? or echo $status Nov 26 22:32:54 (depending on your shell) Nov 26 22:33:21 jacques: so what's the steps to get my nas100d to the same state yours is in so I can help you debug the scripts? Nov 26 22:55:26 rwhitby, sorry was in shower Nov 26 22:55:42 I gotta go somewhere but will try to get on from there, then I ca ntell you everything I know Nov 26 22:56:30 short version is I installed these modules (which are built by default): Nov 26 22:56:40 kernel-module-libata_2.6.19-rc5-r1.579_ixp4xxle.ipk and kernel-module-pata-artop_2.6.19-rc5-r1.579_ixp4xxle.ipk Nov 26 22:57:03 after that, on boot the lude modprobes the module and even mounts all the partitions on the disk Nov 26 22:57:05 ok, I'll put them in the disk modules scripts for nas100d Nov 26 22:57:20 I should be able to fix the turnup problems from there Nov 26 22:57:30 that would be awesome :-) Nov 26 22:57:51 just reloading debianslug now Nov 26 22:57:54 I'll still try to get online later in case there's anything I forgot Nov 26 23:39:05 jacques: ok, I'm up with you now. Nov 27 00:25:42 03rwhitby * r590 10kernel/trunk/patches/2.6.19/defconfig: Make non-user-servicable MTD partitions read-only, and expose unallocated areas. Nov 27 00:29:10 03rwhitby * r591 10kernel/trunk/patches/2.6.19/43-nas100d-mtd-microcode.patch: Moved nas100d microcode back to sysconfig partition. Nov 27 00:30:59 *sigh* Nov 27 00:31:11 * NAiL wants to have time to become a contributing factor again Nov 27 00:31:55 we all go through phases of activity and inactivity Nov 27 00:32:50 yeah, but it's bothering me ;) Nov 27 01:12:09 * rwhitby now tries flashing a slugos 4.1 rootfs on nas100d which should bring up IDE support be default ... Nov 27 01:12:51 <[g2]> rwhitby booting the g600 straight from disk was nice Nov 27 01:13:32 yeah, but for slugos that would mean putting the ide modules in the kernel, and wasting ram on the nslu2 Nov 27 01:13:47 (unless we do some sort of initramfs) Nov 27 01:13:53 <[g2]> rwhitby I thought you had all your video stored on a network drive managed by a slug no ? Nov 27 01:14:45 <[g2]> I think the common kernel is great for testing, but not so good for production Nov 27 01:15:28 [g2]: I think slugos is a good tradeoff with pivot from flash. Nov 27 01:16:08 <[g2]> I'm just about all setup with NFS Nov 27 01:16:25 <[g2]> I've got my CDs as FLACs on the NFS net now. Nov 27 01:16:27 [g2]: you're not the target slugos end-user :-) Nov 27 01:16:45 <[g2]> rwhitby heh... not for about 2 years :) Nov 27 01:17:30 I'm just wondering how debian will react when I propose that the standard ixp4xx kernel have IDE modules enabled :-) Nov 27 01:22:59 [g2]: howdy, how's trix...? Nov 27 01:23:29 <[g2]> GPSFan hey. happy t-giving Nov 27 01:23:54 <[g2]> GPSFan good. I've been playing with xmms2 the last couple days Nov 27 01:23:55 [g2]: same 2 you... enjoy your turkey? Nov 27 01:24:05 <[g2]> GPSFan yeah alot thx Nov 27 01:24:23 * GPSFan doesn't mean that xmms2 is a turkey ;>) Nov 27 01:24:26 <[g2]> ok it's been the last 24 hours, but its seems like a couple days Nov 27 01:24:54 [g2]: swell, we had goose. mmmm good... Nov 27 01:25:25 * [g2] thinks about warming up some stuffing Nov 27 01:25:59 [g2]: I've been chaseing a madwifi problem for the last few days, almost found the cause. testing now.. Nov 27 01:26:17 <[g2]> GPSFan what kinda probelm ? Nov 27 01:26:39 <[g2]> HEAD or old stuff ? Nov 27 01:27:18 it's on x86, so somewhat OT, but the driver we use on our backhaul started crashing when updated to "latest stable" 0.9.2, also does the same on latest svn. Nov 27 01:27:36 <[g2]> ah Nov 27 01:28:26 I've got a test setup that can reproduce the problem within about 30 min of pinging. got it tracked down to a small part one patch that went in at svn 1520. Nov 27 01:29:03 <[g2]> that's 9 revs past the wackelf stuff Nov 27 01:29:53 it has to do with trying to improve permormance/operation with PREEMPT and SMP kernels. Nov 27 01:30:01 the patch that is. **** ENDING LOGGING AT Mon Nov 27 02:59:57 2006