AW: AW: AW: [CentOS] Problems with installation

Tue Jul 18 17:15:39 UTC 2006
Horchler, Joerg <joerg.horchler at coremedia.com>

I saw this too after extracting the modules. CentOS 4.3 is running a newer kernel than included in the driver disk. I then tried to install CentOS 4.2. The kernel version on this Release fits the kernel versions on driver disk. But -- CentOS 4.2 lacks support for the Broadcom Gigabit Controller of this machine. So I can't load the driver disk because network and USB are not available. 
 
Now I see two options:
Install CentOS 4.3 with an older kernel (which meens to rebuild the installation disk) or find a way to include both driver disks (megaraid_sas and bnx2) for CentOS 4.2. 
 
Or install Windows Server 2003 R2 :o(

________________________________

Von: centos-bounces at centos.org im Auftrag von Fabian Arrotin
Gesendet: Di 18.07.2006 18:39
An: CentOS mailing list
Betreff: Re: AW: AW: [CentOS] Problems with installation



Here is your problem : you're trying to use a driver disk build for RHEL
4.0 on CentOS 4.3 and not CentOS 4.0 ... Try to find a dd for RHEL 4u3
(except if the same dd contains modules for RHEL 4, 4U1, 4U2 and 4U3 but
usually they are separate driver disks ....) and then test with CentOS
4.3 ...

On Tue, 2006-07-18 at 16:41 +0200, Horchler, Joerg wrote:
> I will install CentOS 4.3 and downloaded the driver disk from Dell for
> RedHat Enterprise Linux 4:
>
> Description:  Dell PowerEdge RAID Controller 5 Device Driver for Red Hat
> Enterprise Linux 4.0, X86 & X86_64
>
> I saw a few minutes ago that the driver disk is extracted within
> /tmp/ramfs/DD-01. Therfore I know that the network is working correct. I
> will try to extract the module and insmod/modprobe it by hand to see what
> happens
>
> -----Ursprüngliche Nachricht-----
> Von: centos-bounces at centos.org [mailto:centos-bounces at centos.org] Im Auftrag
> von Fabian Arrotin
> Gesendet: Dienstag, 18. Juli 2006 16:13
> An: CentOS mailing list
> Betreff: Re: AW: [CentOS] Problems with installation
>
> 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 at centos.org [mailto:centos-bounces at centos.org] 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 at centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> > _______________________________________________
> > CentOS mailing list
> > CentOS at centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 8156 bytes
Desc: not available
URL: <http://lists.centos.org/pipermail/centos/attachments/20060718/c41ac388/attachment-0005.bin>