RE: [leaf-user] Bering bootable cd (Help) Problem resolved
At 10:21 3/05/2002, Luis.F.Correia wrote: Kim, I did, it was quite helpful, and was the main raison why I considered trying it out. It was written pretty clearly so I thought if it is this simple even I as an (mct) should be able to do it. :-) Guess again ;-) Well I kinda found the problem fixed although not in the clean and nice way as I want to fix it. It will require some more tweaking though. In the end my problem had nothing to do with the modules (although isofs.o is still failing during boot). My problem was that I tried to boot from /dev/cdrom which doesn't exist. I tried to create it afterwards backup root initrd but that didn't help. I noticed just now that the /dev contents is recreated each time from a file called /var/lib/lrpkg/root.dev.mk unfortunately that file is being backed up executed from the root.lrp package which is the first package on /dev/cdrom. Kinda a chicken egg problem. I resolved it temporarily by specifying /dev/hdc (which is my actual cdromdrive) in isolinux.cfg in the boot variable in the pkgpath variable. You might want to change this in your documentation because I think I won't be the only bietekwiet who might make that mistake. Kim Oppalfens have you read my documentation on how to boot Bering from a CDROM? It's available @ http://leaf.sourceforge.net/devel/jnilo/bucdrom.html Have fun! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:56 AM To: Eric Wolzak Cc: Kim Oppalfens; [EMAIL PROTECTED] Subject: Re: [leaf-user] Bering bootable cd (Help) Comments inline Try to remove or uncomment the modules. Ok I' ll try that and see what happens. Btw the new kernel was necessary to boot from flashmodule from apacer which is an idedrive. At the end of /boot/etc/modules isofs.o is trying to load. I said trying, because it is failing stating insmod: init_modules isofs.o device or resource busy Did you use your own created modules, or did you download the modules ( in that case you could have a problem due to the fact that the modules on the bering site, are from a patched kernel. I used downloaded versions, but I used the same patches for the kernel so I don't think that is the problem, especially in combination with the next comment. (read on) Afterwards I get the tempfs linuxrc Installing packages : (all my packages are the (nf!) or not found I get a kernel panic stating that I tried to kill init. It seems that your cdrom is not recognized that reason the packages are not found. If I use all the same .lrp files kernel on the flash module everything runs fine except for the above mentioned ide-probe isofs problem. Which isn't a real concern when booting from the module. I expect that you included the flash rom ide support in the kernel itself. After you boot from the ide-rom, can you mount the cdrom or at least try to insmod the modules from boot/lib one by one and try to mount the cdrom then. Perhaps a conflict betweeen the ide driver for the cdrom and the disk ( Master slave conflict ? ) Hope I have given you a few hints where you might look for a solution. After I boot all modules are loaded (according to lsmod) except for isofs.o. If i try to insmod isofs.o I get the same problem, but a mount -t iso9660 /dev/cdrom /mnt works like a charm. So I think I can conclude that there is nothing wrong with the modules, can't I? I am affraid this also rules out master/slave problems. Correction this definitely rules out master/slave since flashrom is on ide channel 0 cdrom on ide channel 1. I didn't include ideflash support in the kernel by the way, the apacer module uses the ide specifiaction and does not need anything special to work. Kim - This mail sent through Tiscali Webmail (http://webmail.tiscali.be) ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get
RE: [leaf-user] Bering bootable cd (Help) Problem resolved
At 23:24 3/05/2002, Eric Wolzak wrote: Your absolutetely right, and that is where it should go and will fix my problem, I only have create a /dev/cdrom link to /dev/hdc and I am set. Sorry for not checking first but I assumed because the file started out with root it would be backed up in root. My bad for not verifying before bothering the list. Damn I hate to be wrong ;-) although I don't mind telling someone else he is right. Kim Hello Kim Others Well I kinda found the problem fixed although not in the clean and nice way as I want to fix it. It will require some more tweaking though. In the end my problem had nothing to do with the modules (although isofs.o is still failing during boot). My problem was that I tried to boot from /dev/cdrom which doesn't exist. I tried to create it afterwards backup root initrd but that didn't help. I noticed just now that the /dev contents is recreated each time from a file called /var/lib/lrpkg/root.dev.mk unfortunately that file is being backed up executed from the root.lrp package I have no actuall image booted at hand but root.dev.mk is backed up with initrd on bering. look in /var/lib/lrpkg/initrd.list here var/lib/lrpkg/root.dev.mk should be listed. and is there for backed up with initrd = at the boot device. Eric Wolzak which is the first package on /dev/cdrom. Kinda a chicken egg problem. I resolved it temporarily by specifying /dev/hdc (which is my actual cdromdrive) in isolinux.cfg in the boot variable in the pkgpath variable. You might want to change this in your documentation because I think I won't be the only bietekwiet who might make that mistake. Kim Oppalfens have you read my documentation on how to boot Bering from a CDROM? It's available @ http://leaf.sourceforge.net/devel/jnilo/bucdrom.html Have fun! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 6:56 AM To: Eric Wolzak Cc: Kim Oppalfens; [EMAIL PROTECTED] Subject: Re: [leaf-user] Bering bootable cd (Help) Comments inline Try to remove or uncomment the modules. Ok I' ll try that and see what happens. Btw the new kernel was necessary to boot from flashmodule from apacer which is an idedrive. At the end of /boot/etc/modules isofs.o is trying to load. I said trying, because it is failing stating insmod: init_modules isofs.o device or resource busy Did you use your own created modules, or did you download the modules ( in that case you could have a problem due to the fact that the modules on the bering site, are from a patched kernel. I used downloaded versions, but I used the same patches for the kernel so I don't think that is the problem, especially in combination with the next comment. (read on) Afterwards I get the tempfs linuxrc Installing packages : (all my packages are the (nf!) or not found I get a kernel panic stating that I tried to kill init. It seems that your cdrom is not recognized that reason the packages are not found. If I use all the same .lrp files kernel on the flash module everything runs fine except for the above mentioned ide-probe isofs problem. Which isn't a real concern when booting from the module. I expect that you included the flash rom ide support in the kernel itself. After you boot from the ide-rom, can you mount the cdrom or at least try to insmod the modules from boot/lib one by one and try to mount the cdrom then. Perhaps a conflict betweeen the ide driver for the cdrom and the disk ( Master slave conflict ? ) Hope I have given you a few hints where you might look for a solution. After I boot all modules are loaded (according to lsmod) except for isofs.o. If i try to insmod isofs.o I get the same problem, but a mount -t iso9660 /dev/cdrom /mnt works like a charm. So I think I can conclude that there is nothing wrong with the modules, can't I? I am affraid this also rules out master/slave problems. Correction this definitely rules out master/slave since flashrom is on ide channel 0 cdrom on ide channel 1. I didn't include ideflash support in the kernel by the way, the apacer module uses the ide specifiaction and does not need anything special to work. Kim - This mail sent through Tiscali Webmail (http://webmail.tiscali.be) ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] leaf-user mailing list: [EMAIL PROTECTED]
