[ARMedslack] Anyone weigh in on Dreamplug install for 14.0?
slackware at langfinger.org
Wed Oct 3 17:57:41 UTC 2012
i also built my own 3.4.11 kernel now (took 6+ hours... ;)), with the
# CONFIG_MTD_NAND_ORION is not set
This leads to the following:
- Dreamplug machine id (0xdde) set: Lockup after the "Uncompressing..."
- Guruplug machine id (0xa63) set: System boots (because of MTD
I also checked the sources from the u-boot version that i use and the
bugfix for the CONFIG_ARM_PATCH_PHYS_VIRT problem is included in this
version. I made sure that the system really hangs (and not that there is
just no output over the serial line) by changing the bootargs variable
setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp
and then booting the kernel. The system boots up and gets an address if
i use the Guruplug machine id, but it doesn't get an address using the
Dreamplug machine id. So, still no idea what's causing the lockup. Seems
like using the Guruplug machid and compiling a custom kernel is still
the only way to get the Dreamplug booting...
> Thanks Michael, you've confirmed a lot of what I've been discovering!
> I have now built my own 3.4.11 with MTD disabled as a workaround (I
> had to disable PHYS_VIRT in my case as I have not upgraded U-Boot
> and that does indeed boot into the 14.0 installer successfully.
> When I switch to using the Dreamplug board number / FDT config I also
> see the same lockup right after the "Uncompressing...done" message -
> it's interesting that upgrading U-Boot did not fix that for you (but
> have you checked CONFIG_SERIAL_OF_PLATFORM as per , I believe the
> Slackware install kernel has that set to N). Let me know if you find
> anything interesting in the U-Boot sources - I have now procured what
> appears to be the original U-Boot image from another source (thanks
> Jim!) so I feel a little more secure about blowing my current U-Boot
> image away with a new one!
> Cheers, Innes.
More information about the ARMedslack