> I've just compile a new 2.4.0-test12 kernel on my Qube 3. After the make
> was successfully finished I compressed the produced /usr/src/linux/vmlinux
> by 'gzip -f -9 < vmlinux > vmlinux.gz' and moved it to /boot along with
> /usr/src/linux/System.map.
>
> I monitored the booting process via serial cable, and unfortunately it
> stopped with the folowing message:
>
> First stage kernel: Decompressing - done
> Second stage kernel: Decompressing - done
The second stage kernel failed to run (duh!). Why is a different question.
As we have not tested 2.4.x for Qube3, it is entirely possible that the 2.4.x
boot mechanism is slightly different from the 2.2.x mechanism.
> Shou I apply any patches to the standard linux source code in order to get
> it running on a Qube 3?
is it possible that the 2.4.x kernels have a broken serial console, and thus
don't display properly? Try letting it boot, and ping the machine after a few
minutes - to see if it is really up. Of course, we've not tested 2.4., so
various devices will not or may not work:
national dp83815 ethernet may work
LCD/buttons will not work
Watchdog and thermal sensor will not work
_______________________________________________
cobalt-developers mailing list
[EMAIL PROTECTED]
http://list.cobalt.com/mailman/listinfo/cobalt-developers
