Re: [Cooker] kernel-2.4.18-2mdk no initrd
Juan Quintela wrote: mathias == Mathias L Bjorkman [EMAIL PROTECTED] writes: mathias it doesn't seem that kernel-2.4.18-2mdk has a initrd mathias prebuild so therefor doesn't link initrd to initrd-2.4.18-2mdk.img mathias properly. mathias Another thing that came up is it complains when mathias mounting /proc, it says its allready mounted so mathias that program fails. What is your configuration? Here it creates a initrd for sure. what is your root fs and in what is it imounted (i.e. ide, or if SCSI, what card). Later, Juan I've reported this bug three or so times, and received no reply. For me, the root fs is XFS on an ATA100 harddisk. 1.) For mkbootdisk, I would hope if 1.38M is not big enough to fit the XFS module the installer would attempt to format for a larger size (apparently this can be done). At least this way, if you fail to create the initrd when I install Mandrake Linux, the bootdisk may save me. 2.) It seems there is an error creating the initrd. For one thing it would be nice if it took a --root=/mnt option. I cannot tell what the cause is, but I see either: a.) unresolved symbols in modules loaded from initrd b.) no xfs module included in the initrd, so no ability to mount root fs anyway 3.) I have tried installing an older kernel which is known to work. Same thing happens -- creating initrd fails. Persumably, it looks in /sbin or /lib for modules, when my rescue disk puts my filesystems under /mnt. But again, I try creating this file manually, and I get the same errors as above. Like I said, this has happened before. I forgot how I fixed it last time, but I remember it took me a couple of days. Sorry, I don't have much info, maybe you can tell me where to look? I have tried creating the initrd manually since the RPM fails when it tries to do it. -- Sincerely, David Walluck [EMAIL PROTECTED]
Re: [Cooker] kernel-2.4.18-2mdk no initrd
david == David Walluck [EMAIL PROTECTED] writes: david Juan Quintela wrote: mathias == Mathias L Bjorkman [EMAIL PROTECTED] writes: mathias it doesn't seem that kernel-2.4.18-2mdk has a initrd mathias prebuild so therefor doesn't link initrd to initrd-2.4.18-2mdk.img mathias properly. mathias Another thing that came up is it complains when mathias mounting /proc, it says its allready mounted so mathias that program fails. What is your configuration? Here it creates a initrd for sure. what is your root fs and in what is it imounted (i.e. ide, or if SCSI, what card). Later, Juan david I've reported this bug three or so times, and received no reply. For david me, the root fs is XFS on an ATA100 harddisk. david 1.) For mkbootdisk, I would hope if 1.38M is not big enough to fit the david XFS module the installer would attempt to format for a larger size david (apparently this can be done). At least this way, if you fail to david create the initrd when I install Mandrake Linux, the bootdisk may save david me. known problem, no way to create a boot disk for XFS sorry, but floppyes are still 1.44MB xfs alone is: quintela$ ll /lib/modules/2.4.17-18mdk/kernel/fs/xfs*/* -rw-r--r--1 root root 1192269 Feb 14 22:20 /lib/modules/2.4.17-18mdk/kernel/fs/xfs_dmapi/xfs_dmapi.o.gz -rw-r--r--1 root root 7754 Feb 14 22:20 /lib/modules/2.4.17-18mdk/kernel/fs/xfs_support/xfs_support.o.gz -rw-r--r--1 root root 296188 Feb 14 22:20 /lib/modules/2.4.17-18mdk/kernel/fs/xfs/xfs.o.gz and that is just too much :((( david 2.) It seems there is an error creating the initrd. For one thing it david would be nice if it took a --root=/mnt option. I cannot tell what the david cause is, but I see either: I have no idea, but I have been able to boot a machine with xfs yesterday :( I don't know what is happening in your case. david a.) unresolved symbols in modules loaded from initrd Nope, if they are created in that orde: xfs_support xfs_dmapi xfs it works, tested. david b.) no xfs module included in the initrd, so no ability to mount root david fs anyway could you take a look at what is at the initrd? cp /boot/intrd-xxx /tmp/initrd.gz gunzip /tmp/initrd.gz mount -o loop /tmp/initrd /mnt/disk ls -l /mnt/disk cat /mnt/disk/linuxrc that will give me one idea of what is happening david 3.) I have tried installing an older kernel which is known to david work. Same thing happens -- creating initrd fails. Persumably, it david looks in /sbin or /lib for modules, when my rescue disk puts my david filesystems under /mnt. But again, I try creating this file manually, david and I get the same errors as above. Could you copy the exact errors for me? Here it is working fine (not in a floppy, no space for it), but in the root fs, it just works. david Like I said, this has happened before. I forgot how I fixed it last david time, but I remember it took me a couple of days. try, to remove /boot/initrdof your kernel urpme last kernel urpmi last kernel, and see if this fixes the problem, if it is not fixed, send me what errors it gives while you are installing also. david Sorry, I don't have much info, maybe you can tell me where to look? I david have tried creating the initrd manually since the RPM fails when it david tries to do it. Paste the errors tath it gives to you in a mail please? Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] kernel-2.4.18-2mdk no initrd
Juan Quintela wrote: known problem, no way to create a boot disk for XFS sorry, but floppyes are still 1.44MB xfs alone is: I thought there we ways to squeeze and extra 200k or so out of floppies? david a.) unresolved symbols in modules loaded from initrd Nope, if they are created in that orde: xfs_support xfs_dmapi xfs They aren't necessarily unresolved symbols for XFS. I'd try to get the whole output but I don't think it is logged sicne this is of course before init starts. There looks to be unresolved symbols in a whole lot of modules, though. could you take a look at what is at the initrd? cp /boot/intrd-xxx /tmp/initrd.gz gunzip /tmp/initrd.gz mount -o loop /tmp/initrd /mnt/disk ls -l /mnt/disk cat /mnt/disk/linuxrc that will give me one idea of what is happening I will get you the exact output after I sleep... so give this 8 hours or so, after all, it is Sunday ;) try, to remove /boot/initrdof your kernel urpme last kernel urpmi last kernel, and see if this fixes the problem, if it is not fixed, send me what errors it gives while you are installing also. I have tried, for example, if I remove the kernel, so I have no kernel installed, then I do the Upgrade install the install will add a kernel for me. -- Sincerely, David Walluck [EMAIL PROTECTED]
Re: [Cooker] kernel-2.4.18-2mdk no initrd
david == David Walluck [EMAIL PROTECTED] writes: david Juan Quintela wrote: known problem, no way to create a boot disk for XFS sorry, but floppyes are still 1.44MB xfs alone is: david I thought there we ways to squeeze and extra 200k or so out of floppies? no std, and no way to do it cleanly and that will work with all the floppy drives floppies :( david They aren't necessarily unresolved symbols for XFS. I'd try to get the david whole output but I don't think it is logged sicne this is of course david before init starts. There looks to be unresolved symbols in a whole david lot of modules, though. Then something is wrong in mkinitrd, since several versions, I am not able to release a kernel with unresolved symbols, they will just broke the compilation before it finishes. could you take a look at what is at the initrd? cp /boot/intrd-xxx /tmp/initrd.gz gunzip /tmp/initrd.gz mount -o loop /tmp/initrd /mnt/disk ls -l /mnt/disk cat /mnt/disk/linuxrc that will give me one idea of what is happening david I will get you the exact output after I sleep... so give this 8 hours david or so, after all, it is Sunday ;) ok, I also need to go to sleep. try, to remove /boot/initrdof your kernel urpme last kernel urpmi last kernel, and see if this fixes the problem, if it is not fixed, send me what errors it gives while you are installing also. david I have tried, for example, if I remove the kernel, so I have no kernel david installed, then I do the Upgrade install the install will add a david kernel for me. yep, but if you install it with urpmi, you can have _several_ kernels installed. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] kernel-2.4.18-2mdk no initrd
Juan Quintela wrote: Then something is wrong in mkinitrd, since several versions, I am not able to release a kernel with unresolved symbols, they will just broke the compilation before it finishes. Yes, I haven't been able to build the kernel from source, either, which can't be a good sign. Anyway, the error is unresolved symbols, which I can type out a bit by hand: ... a hundred or so unresolved symbols busybox: unresolved symbol remove_proc_entry_R29dQ busybox: unresolved symbol dm_send_namesp_event_R14e19551 busybox: unresolved symbol balance_dirty_Ra2df694 ERROR: /bin/insmod exited abnormally! Creating root device Mounting /proc filesystem mount: error 19 mounting xfs flags Freeing unused kernel memory 260k freed kernel panic: No init found. Try passing init= option to kernel could you take a look at what is at the initrd? cp /boot/intrd-xxx /tmp/initrd.gz gunzip /tmp/initrd.gz mount -o loop /tmp/initrd /mnt/disk ls -l /mnt/disk cat /mnt/disk/linuxrc that will give me one idea of what is happening david I will get you the exact output after I sleep... so give this 8 hours david or so, after all, it is Sunday ;) ok, I also need to go to sleep. I tried this. It looks like the boot kernel does not have loopback support. I'm not sure what to do, then. try, to remove /boot/initrdof your kernel urpme last kernel urpmi last kernel, and see if this fixes the problem, if it is not fixed, send me what errors it gives while you are installing also. david I have tried, for example, if I remove the kernel, so I have no kernel david installed, then I do the Upgrade install the install will add a david kernel for me. yep, but if you install it with urpmi, you can have _several_ kernels installed. I did install 2.4.17-10mdk from Beta 1. But when I tried to create an initrd it says: No module xfs_dmapi found for kernel 2.4.17-10mdk Someone said that creating a 2.4.18-2mdk kernel manually fixed the problem for them, but I don't know if they are using XFS or not. -- Sincerely, David Walluck [EMAIL PROTECTED]
Re: [Cooker] kernel-2.4.18-2mdk no initrd
Mathias L Bjorkman wrote: it doesn't seem that kernel-2418-2mdk has a initrd prebuild so therefor doesn't link initrd to initrd-2418-2mdkimg properly Another thing that came up is it complains when mounting /proc, it says its allready mounted so that program fails /MattB If you do: mkinitrd initrd-2418-2mdkimg 2418-2mdk after installation it works (as a temporary mesure) Irek
Re: [Cooker] kernel-2.4.18-2mdk no initrd
mathias == Mathias L Bjorkman [EMAIL PROTECTED] writes: mathias it doesn't seem that kernel-2.4.18-2mdk has a initrd mathias prebuild so therefor doesn't link initrd to initrd-2.4.18-2mdk.img mathias properly. mathias Another thing that came up is it complains when mathias mounting /proc, it says its allready mounted so mathias that program fails. What is your configuration? Here it creates a initrd for sure. what is your root fs and in what is it imounted (i.e. ide, or if SCSI, what card). Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
