Re: AW: [CentOS] Problems with installation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



If Anaconda told you that he can't find the kernel module, that should
say that you're not using the correct driver disk for the kernel you're
using during setup ...
Which version of CentOS are you trying to install ? CentOS 4.3 ? and for
which processor ? i686 or x86_64 ? Verify that you have the right driver
disk ...
If you want to see which modules are included in modules.cgz, just
explode it (gzip -d -c /media/floppy/modules.cgz | cpio -i -d) somewhere
(in /tmp for example) and compare the kernel modules version.

On Tue, 2006-07-18 at 13:28 +0200, Horchler, Joerg wrote:
> step by step :-)
> 
> I booted now with
> 
> 'linux dd=nfs:<ip>:<path> nostorage nousb ksdevice=eth0' 
> 
> nostorage to disable probing for the SAS-devices and nousb to keep my
> keyboard working. This works nearly perfect:
> 
> anaconda loads the driver disk and shows me the text of the file 'modinfo'
> within the devices list (LSI Logic megaraid_sas Driver ver v00.00.02.03).
> But when I try to load the driver I can see on the second console (alt+F2)
> that he can't find the kernel module. 
> 
> Is the installer not able to copy the contents of the disk-image into a
> specific directory? What is happening when anaconda is loading the disk? Is
> it neccessary to extract 'modules.cgz' on the driver disk first?
> 
> -----Ursprüngliche Nachricht-----
> Von: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] Im Auftrag
> von Matt Hyclak
> Gesendet: Montag, 17. Juli 2006 15:01
> An: CentOS mailing list
> Betreff: Re: [CentOS] Problems with installation
> 
> On Mon, Jul 17, 2006 at 09:26:55AM +0200, Horchler, Joerg enlightened us:
> > I'll try to install CentOS 4.3 for X86_64. 
> > 
> > Do you have an idea how I can find out which device causes the 
> > keyboard to freeze? I'm not able to watch at the consoles without 
> > input device :-( Is there a list which single devices/buses I can disable
> to probe for?
> > 
> > I tried to boot with dd=nfs:<ip>:<path> too. But at the moment the 
> > installer tries to load megaraid_sas BEFORE network is reachable :-( 
> > So I think I need noprobe the device which freezes the keyboard _and_ 
> > in addition I need to find out how to noprobe for any SAS-Device 
> > (storage controllers). Does the option scsi=noprobe exists?
> > 
> 
> You can boot with the 'nostorage' option to disable all storage controllers,
> then add the appropriate drivers in by hand after the driver disk is loaded.
> 
> Matt
> 
> --
> Matt Hyclak
> Department of Mathematics
> Department of Social Work
> Ohio University
> (740) 593-1263
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux