**** BEGIN LOGGING AT Mon Apr 08 02:59:58 2013
**** BEGIN LOGGING AT Mon Apr 08 11:28:15 2013
**** BEGIN LOGGING AT Mon Apr 08 11:59:37 2013
Apr 08 16:23:39 <mjrosenb> on the dreamplug, does the vfat/fat16 partition need to be marked bootable?
Apr 08 16:38:33 <Tootoot222> nope
Apr 08 16:38:53 <Tootoot222> you manually list what partition to read from
Apr 08 16:39:01 <Tootoot222> so the bootable flag doesn't do anything
Apr 08 16:39:15 <mjrosenb> where do I manually list the partition to read from?
Apr 08 16:40:03 * mjrosenb is not very clear on the dreamplug's boot process
Apr 08 20:15:51 <mjrosenb> ok, so if I have a system with partitions |/dev/sdb1            2048      206847      102400   83  Linux|  |/dev/sdb2          206848     6498303     3145728   83  Linux| and |/dev/sdb3   *     6498304     7743487      622592    b  W95 FAT32|
Apr 08 20:16:33 <mjrosenb> presumably, the last partition is the one that it loads some data (uboot?) from before it loads the OS from /dev/sdb2.  correct?
Apr 08 20:39:06 <Tootoot222> mjrosenb: it's set up in a list of commands in uboot
Apr 08 20:39:31 <Tootoot222> if you plug in the jtag board and pause it at the boot process you can list/change the command
Apr 08 20:39:51 <Tootoot222> if you don't have the jtag board, it's set up to read from a static numbered partition by default
Apr 08 20:40:14 <Tootoot222> so whatever the old one was (like sdb2), then just make your boot partition sdb2 again and it will be ok
Apr 08 20:40:17 <mjrosenb> so without a jtag, I need to replace this sdcard with another one that has the image located at /dev/sda3 (called sdb3 here because it is a different machine)
Apr 08 20:40:40 <Tootoot222> yes, and it has to be fat(32 i assume)
Apr 08 20:41:17 <mjrosenb> and this uboot image just contains a kernel, or does it contain a kernel and initrd?
Apr 08 20:43:11 <Tootoot222> uboot is the bootloader (much the same as grub)
Apr 08 20:43:30 <Tootoot222> but yeah on that partition you only need a uImage kernel at the minimum
Apr 08 20:43:36 <Tootoot222> it'll try to load an initrd if one exists afaik
Apr 08 20:47:06 <mjrosenb> Tootoot222: do you happen to have a wheezy system?
Apr 08 20:51:48 * mjrosenb seems to have broken something either in udev, or before udev that renders udev ineffective
Apr 08 20:51:59 <mjrosenb> and I don't have another similar system to test with.
Apr 08 20:52:10 <Tootoot222> did you delete everything out of /dev ?
Apr 08 20:52:28 <Tootoot222> i don't have a wheezy system per say but i'm not bad with debian
Apr 08 20:52:32 <mjrosenb> no, should I?
Apr 08 20:52:48 <Tootoot222> no, but if you delete everything from /dev it usually breaks things =p
Apr 08 20:52:57 <Tootoot222> what seems to be the problem you're having? it won't boot up?
Apr 08 20:53:28 <mjrosenb> it boots up, but /dev is missing most of its files (/dev/{tty,console,urandom})
Apr 08 20:53:33 <mjrosenb> so sshd isn't starting
Apr 08 20:53:51 <mjrosenb> so I've been manually creating these files in /etc/rc.local
Apr 08 20:53:57 <mjrosenb> then launching sshd from there
Apr 08 20:54:05 <mjrosenb> but it is not working very well.
Apr 08 20:54:45 <mjrosenb> I'm hoping to find a stable solution that will at least allow me to poke the system directly, rather than logging from /etc/rc.local, and walking across the room to pull the sd card out of the machine.
Apr 08 20:56:58 <mjrosenb> this time, it apparently hung executing chown -v root:tty /dev/{console,ptmx,tty}
Apr 08 20:57:18 <mjrosenb> or maybe that was the last thing that got synched to the disk before it got powered off.
Apr 08 21:00:54 <Tootoot222> did you compile your own kernel?
Apr 08 21:01:00 <Tootoot222> or where did you get your kernel from?
Apr 08 21:01:25 <mjrosenb> no, I just got a new one from apt-get update after changing squeeze to wheezy in /etc/apt/sources.list
Apr 08 22:09:10 <mjrosenb> is the location of hard coded into uboot, or the kernel image?
**** ENDING LOGGING AT Tue Apr 09 02:59:58 2013