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@centos.org [mailto:centos-bounces@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@centos.org [mailto:centos-bounces@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@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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@centos.org [mailto:centos-bounces@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@centos.org [mailto:centos-bounces@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@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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@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@centos.org [mailto:centos-bounces@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@centos.org [mailto:centos-bounces@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@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Newer Broadcom gigabit controllers ? not using the standard tg3 module ? If that's the case Dell support should give you both driver disks ... except if Dell doesn't support RHEL 4 on such box .... :o) Contact Dell Support to see if they have a OS install howto for RHEL 4 on your server model ...
On Tue, 2006-07-18 at 19:15 +0200, Horchler, Joerg wrote:
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(
Horchler, Joerg wrote:
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.
why can you not just ask Dell for an updated driver disk ?
the other real option is to install the module manually, the driver will work fine, even if its built for RHEL 4.0 ( work with CentOS 4.3 - but only if instmod'd manually, anaconda wont even bother testing / trying if the kernel version is different, and hence the issue ).
Also, can you stop top posting ? that really messes up things.
- K
Karanbir Singh schrieb:
Also, can you stop top posting ? that really messes up things.
- K
Stripping the quotation is the most important part. There is no need to get the conversation again with each new posting (just filling my mailbox and archives with redundant data). Mail client and archives do threading. Not using richtext in Outbreak is another issue, along with setting the reply prefix to international/english standard "Re: " (prevends the topic to become "uglyfied").
Regards
Alexander
-
Alexander Dalloz -
Fabian Arrotin -
Horchler, Joerg -
Karanbir Singh