Bugs item #930165, was opened at 2004-04-05 19:10 Message generated for change (Comment added) made by muratd2000 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=930165&group_id=259
Category: Autoinstall Kernel Group: v3.2.0 Status: Open Resolution: None Priority: 5 Submitted By: MD (muratd2000) Assigned to: dann frazier (dannf) >Summary: parted crashes due to "illegal instruction" Initial Comment: BACKGROUND: ============ I am using BOEL, busybox, etc. from systemimager-i386boot-standard-3.2.0-4.noarch.rpm The target boot station is a VIA EPIA x86 based system, which has been running plain vanilla Redhat 9 for quite some time. Because this class of VIA EPIA motherboard is PXE enabled, I am interested in being able to load a full system image on it via SIS. PROOF I GOT SIS SETUP RIGHT: ============================== I got the CD based boot working on another class of VIA EPIA machine with a slightly different x86 processor. However, this specific machine, after it boots, gets through PXE, Syslinux, etc. and gets BOEL running, stops after encountering an "illegal instruction" in /sbin/parted. The process stops at that point and drops into the busybox "#" prompt. HYPOTHESIS: I suspect/hope it should be possible to build BOEL/busybox with a more generic set of switches. ** I did not have any problem installing the same RH9 binary distribution across any of my VIA EPIA machines ** - so this should not be a "different architecture" problem. I am hoping for a new systemimager-i386boot-standard rpm with BOEL/Busybox that is more x86 generic. ---------------------------------------------------------------------- >Comment By: MD (muratd2000) Date: 2004-04-06 16:02 Message: Logged In: YES user_id=738665 Update on 4-6-04: Because the target machine is already running RH9, I downloaded systemimager-3.2.0-4.src.rpm (and the e2fsprogs-devel RPM it needs) and rebuilt the whole shebang on the target platform itself, hoping that this would yield a BOEL with properly built utilities. I then replaced the boel_binaries.tar.gz file on the distribution server with the newly built one. And it WORKED! (yea!). So now I can PXE load my system images from a central server to any of these VIA EPIA machines with built-in PXE netboot capability. So, I am over this hurdle and can achieve my immediate goal with systemInstaller. Why I experienced this poblem with the default binary distribution which was meant to work on any vanilla x386 target is still unknown. Apparently there are some non-plainVanilla optimizations enabled in the generation of these binaries, leading to "illegal instruction" exceptions on some x386 machines like some (but not all) VIA EPIA motherboards. I will leave investigation to hardcore developers. Best, M ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=930165&group_id=259 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
