On Jun 8, 2015, at 7:01 AM, Martin Michlmayr wrote:
> * Rick Thomas [2015-06-07 19:39]:
>> I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
>> if that’s any help. The VT100-style curses stuff makes it a bit
>> hard to interpret…
>
> From the log it looks like you didn't fin
* Rick Thomas [2015-06-07 19:39]:
> I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
> if that’s any help. The VT100-style curses stuff makes it a bit
> hard to interpret…
>From the log it looks like you didn't finish the installation. These
are the last messages in the log:
On Jun 7, 2015, at 7:39 PM, Rick Thomas wrote:
>
> On Jun 6, 2015, at 10:55 AM, Martin Michlmayr wrote:
>
>> * Rodrigo Valiña Gutiérrez [2015-05-18 13:42]:
>>> The relevant part of /var/log/installer/syslog seems to be this:
>> ...
>>> May 17 15:19:13 base-installer: info: could not determin
* Rodrigo Valiña Gutiérrez [2015-05-18 13:42]:
> The relevant part of /var/log/installer/syslog seems to be this:
...
> May 17 15:19:13 base-installer: info: could not determine kernel flavour
The installer is fixed now and you can install Debian on the
SheevaPlug (and other plug variants) again.
>> But now the installer fails in the "Install the base system" step,
>> saying: "No installable kernel was found in the defined APT sources"...
>> when the last time I tested with changed machid and original uImage it
>> worked with the same sources.
>
>What does /var/log/syslog say when this happ
* Rodrigo Valiña Gutiérrez [2015-05-17 16:09]:
> But now the installer fails in the "Install the base system" step,
> saying: "No installable kernel was found in the defined APT sources"...
> when the last time I tested with changed machid and original uImage it
> worked with the same sources.
Wh
>Does this boot?
>
>This is how I prepare the image:
>
>wget
>http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb
>wget
>http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sh
I am not an expert...
The workaround just worked, but I don't know whether "0692
Marvell RD-88F6281 Reference Board"
is a valid machid for the sheevaplug, instead of the 'original' 0831.
At the beggining it worked, but now I have a problem: the sheevaplug
ethernet subsystem does not work
* Martin Michlmayr [2015-05-16 21:37]:
> So the best solution now is to append the device tree blob (DTB) to
> the kernel in the installer. This way, the kernel will find the
> correct device tree and can boot (and everything else will work since
> flash-kernel already appends the DTB on the Shee
* Rick Thomas [2015-05-16 17:47]:
> > - In u-boot:
> >
> > setenv machid 0692
> > saveenv
This is not the correct solution.
The problem is that there are different ways to boot on ARM machines.
The old way was for the boot loader to pass a machine ID to the kernel
which would tell the kerne
On May 16, 2015, at 10:33 AM, Rodrigo Valiña Gutiérrez
wrote:
> I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
>
> I solved it temporarily by doing the following:
>
> - In u-boot:
>
> setenv machid 0692
> saveenv
>
> - Then install normally. The 'make the system bo
I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
I solved it temporarily by doing the following:
- In u-boot:
setenv machid 0692
saveenv
- Then install normally. The 'make the system bootable' phase will fail
because flash-kernel fails:
/var/log/installer/syslog:
Ma
12 matches
Mail list logo
