<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: new initrd after kernel upgrade in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061705#M29840</link>
    <description>I wasn't actually compiling a new kernel, just simply downloaded the latest from RH.&lt;BR /&gt;&lt;BR /&gt;I had installed a new Qlogic driver (HP recommended)and was not using the one from RH.&lt;BR /&gt;&lt;BR /&gt;After booting the new kernel and initrd I had no new Qlogic driver. The modprobe.conf was still intact but no module loaded.&lt;BR /&gt;&lt;BR /&gt;I ended up removing the qlogic driver package and re-installing it and then setting failover which created a new initrd. Any changes made to the HBA's via sansurfer requires a new initrd.&lt;BR /&gt;&lt;BR /&gt;HBA's are QMH2462.&lt;BR /&gt;&lt;BR /&gt;Another reboot and all seems to be fine.&lt;BR /&gt;&lt;BR /&gt;Not sure if this is the recommended procedure.&lt;BR /&gt;&lt;BR /&gt;Thx.</description>
    <pubDate>Tue, 28 Aug 2007 18:57:39 GMT</pubDate>
    <dc:creator>westb</dc:creator>
    <dc:date>2007-08-28T18:57:39Z</dc:date>
    <item>
      <title>new initrd after kernel upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061701#M29836</link>
      <description>I have the Qlogic FC HBA driver setup in failover mode, confiured the HBA's with sansurfer.&lt;BR /&gt;&lt;BR /&gt;Does anyone know the correct procedure to create a new initrd with the qlogic stuff after a kernel upgrade ?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Tue, 28 Aug 2007 10:17:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061701#M29836</guid>
      <dc:creator>westb</dc:creator>
      <dc:date>2007-08-28T10:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: new initrd after kernel upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061702#M29837</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Should not have to generate a new kernel or initrd but:&lt;BR /&gt;&lt;BR /&gt;Make required changes to /etc/modprobe.conf&lt;BR /&gt;&lt;BR /&gt;cd /boot&lt;BR /&gt;mv initrd-....img to initrd-....img.orig&lt;BR /&gt;&lt;BR /&gt;mkinitrd&lt;BR /&gt;&lt;BR /&gt;mkinitrd initrd-2.6.9-42.0.3.ELsmp.img 2.6.9-42.0.3.ELsmp&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Aug 2007 10:55:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061702#M29837</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-28T10:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: new initrd after kernel upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061703#M29838</link>
      <description>My modprobe.conf file is still intact with everything I need.&lt;BR /&gt;&lt;BR /&gt;Do I have to rebuild the Qlogic driver again ? This process rebuilds initrd.</description>
      <pubDate>Tue, 28 Aug 2007 11:18:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061703#M29838</guid>
      <dc:creator>westb</dc:creator>
      <dc:date>2007-08-28T11:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: new initrd after kernel upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061704#M29839</link>
      <description>To answer the second question, I would need to know the model number of the card.&lt;BR /&gt;&lt;BR /&gt;Most Qlogic cards are auto detected by the kernel, necessitating only a change in modeprobe.conf, which the system does on its own as well.&lt;BR /&gt;&lt;BR /&gt;before compiling the kernel and doing mkinitrd, perhaps run dmesg or hwbrowser and see if the system recognizes the hardware.&lt;BR /&gt;&lt;BR /&gt;If recognized tuck this procedure away for when you need to use an emulex card, which won't auto detect and requires a ram disk rebuild in order to mount filesystems via /etc/fstab&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 28 Aug 2007 11:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061704#M29839</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-28T11:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: new initrd after kernel upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061705#M29840</link>
      <description>I wasn't actually compiling a new kernel, just simply downloaded the latest from RH.&lt;BR /&gt;&lt;BR /&gt;I had installed a new Qlogic driver (HP recommended)and was not using the one from RH.&lt;BR /&gt;&lt;BR /&gt;After booting the new kernel and initrd I had no new Qlogic driver. The modprobe.conf was still intact but no module loaded.&lt;BR /&gt;&lt;BR /&gt;I ended up removing the qlogic driver package and re-installing it and then setting failover which created a new initrd. Any changes made to the HBA's via sansurfer requires a new initrd.&lt;BR /&gt;&lt;BR /&gt;HBA's are QMH2462.&lt;BR /&gt;&lt;BR /&gt;Another reboot and all seems to be fine.&lt;BR /&gt;&lt;BR /&gt;Not sure if this is the recommended procedure.&lt;BR /&gt;&lt;BR /&gt;Thx.</description>
      <pubDate>Tue, 28 Aug 2007 18:57:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/new-initrd-after-kernel-upgrade/m-p/4061705#M29840</guid>
      <dc:creator>westb</dc:creator>
      <dc:date>2007-08-28T18:57:39Z</dc:date>
    </item>
  </channel>
</rss>

