**** BEGIN LOGGING AT Mon Oct 18 02:59:57 2010 Oct 18 03:15:49 Majost: you compiled it yourself right? Oct 18 03:16:36 the maintainers are silly Oct 18 03:16:46 the left the offset for the guruplug at 0x4000 Oct 18 03:16:50 40000* Oct 18 03:16:55 which is the default for other boards Oct 18 03:17:27 but 0x40000 = 250kb Oct 18 03:17:39 and the uboot size for the guruplug is now 370kb Oct 18 03:17:45 so when you save the environment Oct 18 03:17:55 it overwrites some of the uboot binary Oct 18 03:17:59 thus the brick Oct 18 03:18:01 if you edit the file Oct 18 03:18:04 uh Oct 18 03:18:30 u-boot-marvell.git/include/configs/guruplug.h Oct 18 03:18:35 on lines 75 and 76 Oct 18 03:18:41 change 0x40000 to 0xa0000 Oct 18 03:19:12 it will match up with the current sheevaplug sizes (thus letting you continue to use the burning tools for the sheevaplug, such as the sheevaplug_installer_v1.0 on your guruplug) Oct 18 03:20:48 i've also found that if you try to use the sheevaplug installer on a guruplug to update/burn environment varibles, it sometimes doesn't write properly Oct 18 03:21:05 (the error being "readenv() failed" or like) Oct 18 03:21:38 if you change sheevaplug_installer_v1.0/uboot/openocd/config/board/sheevaplug.cfg Oct 18 03:21:51 line 120 (and maybe) line 109 Oct 18 03:22:03 change oob_softecc_kw to oob_softecc at the end of the lines Oct 18 03:22:36 it doesn't seem to matter for burning the uboot binary itself, but when you try to write the environment it has troubles Oct 18 03:23:01 because they are different devices Oct 18 03:23:30 tinker-f595: they're the same board Oct 18 03:23:32 you need to make sure you edit all the correct configuration files Oct 18 03:23:34 the version numbers are the same Oct 18 03:23:46 (between sheeva and guru) Oct 18 03:23:46 no they are not the same Oct 18 03:23:55 I have both and they are not the same board Oct 18 03:24:16 they have different mach types Oct 18 03:24:31 and the gpios are a bit different Oct 18 03:52:32 damn Oct 18 03:52:35 I missed him Oct 18 03:52:36 heh Oct 18 04:03:45 I seem to have the issue with flipflip's version of uboot too though Oct 18 04:03:57 which has the patch tootoot mentioned Oct 18 04:04:04 actually Oct 18 04:04:06 take that back Oct 18 04:04:10 its a different issue Oct 18 05:57:52 do I need to use the mainlineLinux option for the latest git version of u-boot? Oct 18 05:58:01 I am using the stock kernel though Oct 18 06:02:29 Majost: you use what you need for the kernel Oct 18 06:05:16 the stock kernel doesn't seem to need anything (to my knowledge_ Oct 18 06:06:17 by stock kernel I assume you mean the one that shipped with it Oct 18 06:06:24 correct Oct 18 06:06:42 yes having MinalineLinux unset is correct for that Oct 18 06:06:48 whoops Oct 18 06:07:13 mainlineLinux unset is correct Oct 18 06:10:03 hrmm Oct 18 06:10:19 yeah... it hangs at: done, booting the kernel. Oct 18 06:11:07 actually, I think I have an idea why now Oct 18 06:11:16 Load Address: 00008000 Oct 18 06:11:17 Entry Point: 00008000 Oct 18 06:12:50 I applied the flipflip patch to set the uboot offset Oct 18 06:13:19 so I probably need to reflash the kernel at the same offset Oct 18 06:15:44 seems like the address is not correct Oct 18 06:18:34 Majost: take a look around http://plugcomputer.org/plugwiki/index.php?title=Main_Page. well I am going to sleep Oct 18 06:19:41 or look at http://computingplugs.com/index.php/Main_Page **** BEGIN LOGGING AT Mon Oct 18 12:30:01 2010 Oct 18 16:13:00 http://seclists.org/fulldisclosure/2010/Oct/257 instantroot(tm) :-( **** ENDING LOGGING AT Tue Oct 19 02:59:57 2010