Dear Forum,
 
Yesterday, I've realized that i didn't move boot package in the good place, i.e the tftboot directory !! This explain why modules like sd_mod.ko or scsci_mod.ko were not loaded, because I worked always with the Boel 2.4.25 !!
 
Then , i have made the same processus with SystemImager 3.5.2.
Even so, I have always complaint like Undefined:Disk0, BUT, some modules are loaded, like SD_MOD and SCSCI_MOD.
 
I try to built my own Kernel from Front-end, with the script SI_mkbootpackage, and i got some progress !. Now, I have a message like : Kernel Panic : Unable to mount root fs. I don't want to play with mk_bookpackage now.
 
On the other hand, i will patche the 2.4.25 or/and the 2.6.9 Boel Kernel to apply libata and Sata_sil from Jeff Garzik. I play around with 2.4.25 and 2.4.25-libata16.patch from Garzik at home yesterday evening and i think it will be ok. May be l will have some trouble with 2.4.25 kernel and libata patch, because libata patch for this kernel don't work very well with SIL3114.
 
Tell you about this morning.
 
Cheers
 
Jerome Lefevre
> From: Lefevre Jerome;  Sunday, January 23, 2005 6:14 PM
> >
> >
> >Please see Config Kernel below. I think I must to ''power on'' some
> setting
> >in order to detect my Sata device. However, i test the standard boot
> >package without make change and reboot my node. There is always a bad
> issue
> >with undefined DISK0 !!
>
> Yes, the key is to get the disk recognized by the SIS kernel.
>
> >So, i run this command :
> >
> >./si_mkbootpackage.sh --verbose --kernel /boot/vmlinuz-2.6.5-1.358smp
> >--new-flavor fedora --fs ext2 --modules-dir /lib/modules/2.6.5-1.358smp
> >And i obtain a new boot package Fedora, with initrd.img, kernel and
> >binary_boel.tar.gz. I rename Fedora as Standard afer backup the
> standard
> >diectory and reboot my node.
> >
> >Same issue !!
>
> Once the client dumps into the shell, are you able to find the disks by
> hand?  If so, what is/are the device names?
>
> >If I go up on my console screen i see always this message :
> >
> ><<
> >autodetect_hardware_and_load_modules
> >Detecting hardware: spurious 8259A interrupt IRQ 7
> >ide_scsi
> >Loading sd-mod ...
> >Assuming sd-mod is compiled into the kernel, not needed, or already
> loaded
>
> This means an attempt was made to load "sd-mod", but it failed.  As
> stated, this could be because:
> a) No such module is available
> b) No hardware needing the device is present
> c) The module is already loaded.
>
> >Any idea ??
>
> I noticed this in the included config:
>
>   # CONFIG_BLK_DEV_IDE_SATA is not set
>   # CONFIG_SCSI_SATA is not set
>
> I don't know if enabling these is sufficient or not.  I know there is an
> existing SATA patch, from Garzik I think, but it has problems with the
> busybox in the SIS included w/ OSCAR.
>
> --
> David N. Lombard
>  
> My comments represent my opinions, not those of Intel Corporation.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at
http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Oscar-users mailing list
>
[email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-users
>

Reply via email to