Re: Can't re-create initrd

2014-10-12 Thread Roger Heflin
. (dot) usually in these cases are whatever preferred named sub-directory that you extracted it in to start with. On Sun, Oct 12, 2014 at 2:48 PM, jd1008 wrote: > > On 10/12/2014 01:39 PM, CLOSE Dave wrote: >> >> find . | cpio -oc | xz --check=crc32 --lzma2=dict=1MiB >../initrd2.img > > So . (dot

Re: Can't re-create initrd

2014-10-12 Thread jd1008
On 10/12/2014 01:39 PM, CLOSE Dave wrote: find . | cpio -oc | xz --check=crc32 --lzma2=dict=1MiB >../initrd2.img So . (dot) is /boot/grub2 ?? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/use

Re: Can't re-create initrd

2014-10-12 Thread CLOSE Dave
I wrote: > Eventually, I want to modify the initrd. But first I want to find a > working procedure to create the revised version. So, without changing > anything, I'm trying to recreate the initrd. If I can't get an > unmodified version to work, I probably have no hope for a modified one. > > My c

Re: Can't re-create initrd

2014-10-11 Thread Roger Heflin
And the machine pxeboots successfully with the original unmodified initrd? You could get a serial crossover cable get enhanced console logging that way, I have used serial before, just not on normal home type machines. You could also make only tiny modifications of the initird (ie adding the slee

Re: Can't re-create initrd

2014-10-11 Thread CLOSE Dave
Roger Heflin wrote: > it is failing to find the root device. > > If the root device is initrd then that should be found, since you > are modifing the initrd you may add a few more commands to it. > ... > if the root device is elsewhere it is not finding that. Eventually, I want to modify the init

Re: Can't re-create initrd

2014-10-11 Thread Roger Heflin
it is failing to find the root device. If the root device is initrd then that should be found, since you are modifing the initrd you may add a few more commands to it. sleep 10 (ash should have a sleep command) and a few more echo's so you can confirm if the initrd is running or not. if the root

Re: Can't re-create initrd

2014-10-11 Thread CLOSE Dave
Roger Heflin wrote: > note step 3.4: -H newc is important. > find . | cpio -o -H newc | gzip > ../initrd.img Yes, it is. But -c means exactly the same thing. -- Dave Close, Thales Avionics, Irvine California USA. cell +1 949 394 2124, dave.cl...@us.thalesgroup.com "If a cluttered desk is a sign

Re: Can't re-create initrd

2014-10-11 Thread Roger Heflin
This page: http://www.thewireframecommunity.com/node/14 note step 3.4: -H newc is important. find . | cpio -o -H newc | gzip > ../initrd.img On Sat, Oct 11, 2014 at 3:29 PM, CLOSE Dave wrote: > Heinz Diehl wrote: > >> You could use dracut to recreate your initramfs? >> Works flawlessly (here as

Re: Can't re-create initrd

2014-10-11 Thread CLOSE Dave
Heinz Diehl wrote: > You could use dracut to recreate your initramfs? > Works flawlessly (here as a test, with an old kernel): While I am not familiar with dracut, I've looked at it a bit. I don't see a way to use it to modify an existing initrd, only to create a new one based on the running sy

Re: Can't re-create initrd

2014-10-11 Thread Heinz Diehl
On 10.10.2014, CLOSE Dave wrote: > What am I doing wrong? You could use dracut to recreate your initramfs? Works flawlessly (here as a test, with an old kernel): [root@kiera boot]# dracut -v -f initramfs-3.16.3-rc1.img I: *** Including module: i18n *** I: *** Including module: drm *** I: *** I

Can't re-create initrd

2014-10-10 Thread CLOSE Dave
I'm working on a local change to the initrd used by PXE for Fedora 20. The standard version works great for me. As an experiment, I ran these commands. # ls -l initrd.img -rw-r--r--. 1 root root 34631660 Dec 12 2013 initrd.img # mkdir newrd; cd newrd # unxz <../initrd.img | cpio -i