:: Re: [dyne:bolic] Remastering with a…
Page principale
Supprimer ce message
Répondre à ce message
Auteur: Matt Grice
Date:  
À: dynebolic mailinglist
Sujet: Re: [dyne:bolic] Remastering with a new kernel
Hey Guy,

Many thanks for your reply! I'd managed to get that far (with the help of qemu). The weirdness of the mkinitrd step failing at random is what's phasing me.

I'm going to try it on my own pc with more memory this weekend.

Thanks for your help,

Matt

Sent from my BlackBerry® wireless device

-----Original Message-----
From: Guy <sayhi2guy@???>

Date: Fri, 07 Dec 2007 12:51:29
To:dynebolic mailinglist <dynebolic@???>
Subject: Re: [dyne:bolic] Remastering with a new kernel


Matt Grice wrote:

>Hi all,
>
>I'm currently trying to remaster a Dyne:Bolic CD with a different
>kernel. 2.6.18 has a bug which screws up my external USB HD. I've been
>trying to install 2.6.21-mm2-dyne from the dyne:bolic ftp site.
>The method I've been using is:
>
>dynesdk makesdk
>
>I then copy the .krn file into dyne...
>
>export KRN=2.6.21-mm2-dyne
>dynesdk mkkern (which goes smoothly)
>
>dynesdk mkinitrd (worked once, allowed an ISO to boot and run, but found
>no kernel modules)
>dynesdk -K mkinitrd (no error messages, always freezes)
>
>at this point, the system freezes at the output "populating the ramdisk"
>(or similar -my memory fails me... ), with no kernel messages (I had
>been tailing /var/log/messages). The system appears to lose all access
>to any discs at this point. the desktop still functions, but typing 'ls'
>into an xterm sits and hangs. trying to run a program has the same result.
>
>I'm running dyne docked on an NTFS hard drive with stacks of room on an
>AMD1700 with 512mb memory.
>
>Anyone had similar or can shed some light on to this strange behaviour?
>
>
>Matt
>
>

Hi
I haven't had all your problems but I did make an iso that wouldn't
boot. The problem was isolinux.cfg not having the right name for the
kernel. I did put the solution on the wiki under troubleshooting:

you need to edit the file /dyne/sdk/cdrom/isolinux/isolinux.cfg and
change the line kernel /dyne/linux to kernel /dyne/2618ck1d.krn (or
whatever the kernel is called) and run dynesdk mkiso again.

(from http://lab.dyne.org/TroubleShooting)

Hope this helps

Guy



_______________________________________________
dynebolic mailing list
dynebolic@???
http://lists.dyne.org/mailman/listinfo/dynebolic