**** BEGIN LOGGING AT Wed Mar 30 02:59:57 2011 Mar 30 04:03:10 Seems you are getting processor speed and dram speed confused Mar 30 04:03:43 tinker-f595: his bogomips was actually 400 Mar 30 04:04:12 the dram speed for the guruplug and dreamplug should be 800mhz anyway Mar 30 04:04:21 well bogomips also depends on the kernel installed...it may be a kernel bug Mar 30 04:04:38 in how bogo mips is being caclulated Mar 30 04:04:41 no, if you saw the forum post i linked Mar 30 04:04:51 somebody messaged GS and they said they had sent out messed up boards Mar 30 04:04:57 hahaha Mar 30 04:05:05 sounds like a recall Mar 30 04:05:17 the letter said it was only for a small number of boards Mar 30 04:05:18 but yea Mar 30 04:05:26 it made the dreamplug epic slow Mar 30 04:05:30 well at least they confessed Mar 30 04:05:31 even just trying to list a directory contents Mar 30 04:06:07 I remember a few times when Intel released buggy CPUs they would 1st deny it and then try and make out it was not a big deal Mar 30 04:06:47 lol Mar 30 04:32:11 I wonder how it performs in comparison to hte sheeva Mar 30 04:32:48 noidea: the messed up 400bogomips dreamplugs? Mar 30 04:32:52 or a regular one? Mar 30 04:33:03 regular one Mar 30 04:33:07 'cause you could just compare it to a guruplug in that case Mar 30 04:33:12 What happened with the messed up one Mar 30 04:33:31 they accidentally shipped a batch of dreamplugs @ 400bogomips where the normal was 1200bm Mar 30 04:33:46 (bogomips is independant of ghz, although they're oddly related here) Mar 30 04:33:52 the 400 ones were epic slow Mar 30 04:34:20 lolol Mar 30 05:07:50 Tootoot222: I would love to know why it is so slow Mar 30 05:08:23 tinker-f595: dunno, they shipped with a bad bit of hardware Mar 30 05:08:36 do they say that? Mar 30 05:08:39 it's not that slow on the actual/proper dreamplugs Mar 30 05:09:21 or is it bad software that is booting it up in a slower mode...need to look at my kirkwood HW docs to see if that is a possibility Mar 30 05:09:48 Mystery solved! Grin Mar 30 05:09:48 i just spoke with Nancy over at GTI. She says there were a few units accidentally shipped with Ubuntu 9.04 and some of those units were running at 400 MHz. New units are shipping with 1.2 GHz and Debian. I was just one of the lucky people to get a slow beast with a doggy OS. New one on it's way to me. Thanks for the help guys! Mar 30 05:09:54 http://plugcomputer.org/plugforum/index.php?topic=5765.0 Mar 30 05:09:59 third-to-bottom post there ^ Mar 30 05:30:15 Tootoot222: just looking through the arm mailing list and there was a bogomips reported bug back around january Mar 30 06:00:34 jfb_h20: kernel on things that aren't the NAND causes problems Mar 30 06:01:51 not sure why though Mar 30 06:02:01 Tootoot222: why didn't uboot fix all of those issues? :( Mar 30 06:07:55 kerio: fix what issues? Mar 30 06:08:38 the issues with uboot not actually... well, working with non-nand devices Mar 30 06:08:44 at least, not working well Mar 30 06:09:26 kerio: it works fine for me Mar 30 06:09:35 the sd works ok, i guess, but usb and esata are still ew Mar 30 06:10:00 kerio: you probably do not know the commands to use Mar 30 06:10:15 usb and sata work ok for me Mar 30 06:10:18 ...right Mar 30 06:10:27 well I am going to sleep now Mar 30 06:10:36 catch me on the weekend Mar 30 06:10:43 so the countless reports of people typing usb start and their *plug not finding shit are...? Mar 30 06:13:55 kerio: are them not using the commands correctly Mar 30 06:14:07 anyway I need to go to sleep Mar 30 06:17:22 this is what I use with my sheevaplug Mar 30 06:17:23 setenv bootcmd 'usb start; ext2load usb 0:1 0x8000000 /boot/uImage; bootm 0x8000000; reset' Mar 30 06:17:23 setenv bootargs 'console=ttyS0,115200 root=/dev/sda5 rootdelay=10 rw' Mar 30 08:32:14 Morning folks, after some tweaking around, it seems I was finally able to get Debian onto an SD card. :) Mar 30 08:33:15 hi Mar 30 08:33:29 jfb_h20: what kind of device? Mar 30 08:33:31 what I don't understand is how to put the linux kernel on NAND, but the rootfs on SD (or USB) Mar 30 08:33:35 Sheevaplug Mar 30 08:36:26 I kept having a problem when I was upgrade uboot. Finally I tried the arcNumber for the eSATA version (which I don't have) and things worked! Mar 30 08:36:58 prior to that, fatload wasn't loading the uboot.bin image properly... Mar 30 08:37:35 once uboot was upgraded, I was able to follow instructions for the debian installer w/o problems Mar 30 11:49:57 tinker-f595: and why do you need the "reset" at the end of bootcmd? Mar 30 14:11:53 kerio: incase it failed to load the kernel into that memory address, uboot will just say "bad kernel!" and move on to the next command (reset), which will make it try again Mar 30 14:12:11 it was a rethorical question Mar 30 14:12:33 he claims there's no problem with the current USB support Mar 30 14:38:55 and there is not Mar 30 14:39:37 kerio:the reset is there in case the drive is slow to spin up Mar 30 14:50:12 Or the cat was playing with the cable again... or any number of very practical reasons. :) Mar 30 15:07:41 mwester: yes it is always da Kat ;) Mar 30 15:08:03 ;) Cats are fundamentally evil. Mar 30 15:08:15 depends on the cat **** ENDING LOGGING AT Thu Mar 31 02:59:58 2011