<?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: A bug in proliant support pack for RHEL 4?? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104441#M30783</link>
    <description>Hi Jimmy&lt;BR /&gt;&lt;BR /&gt;That didn't work - if I comment that line and restart the network I then get a message that the bnx2 device is not present. &lt;BR /&gt;&lt;BR /&gt;I then tried "modprobe bnx2" and it tells me "incorrect module format".&lt;BR /&gt;&lt;BR /&gt;depmod -a and then modprobe again just gives the same error. &lt;BR /&gt;&lt;BR /&gt;I found another thread this morning which appears to be exactly the same problem so I'll follow up in there. Looks like this is an issue with PSP on some new systems. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1113552" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1113552&lt;/A&gt;</description>
    <pubDate>Mon, 19 Nov 2007 05:03:42 GMT</pubDate>
    <dc:creator>Ben Stokes</dc:creator>
    <dc:date>2007-11-19T05:03:42Z</dc:date>
    <item>
      <title>A bug in proliant support pack for RHEL 4??</title>
      <link>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104439#M30781</link>
      <description>I have a major issue with the PSP for RHEL4. The same thing happens every time if the ILO card drivers are installed, this is what I'm doing:&lt;BR /&gt;&lt;BR /&gt;up2date -i -f kernel-devel&lt;BR /&gt;ln -s /usr/src/kernels/`uname -r` /lib/modules/`uname -r`/build&lt;BR /&gt;tar psp...blah blah&lt;BR /&gt;cd /blah/blah&lt;BR /&gt;./installxxx&lt;BR /&gt;&lt;BR /&gt;Everything is installed OK, but the next time the server is rebooted, during startup it says device eth0 has a different mac address than expecting, ignoring. Then it becomes impossible to start up eth0 because of this problem. &lt;BR /&gt;&lt;BR /&gt;It would be a quick fix to rebuild the server and just not create this symlink so that the ILO drivers are not installed, after all this is not critical for the server to run  and ILO will work perfectly without it ... but I would rather get to the bottom of this. What am I doing wrong here? Or is this a problem with the PSP and RHEL4?</description>
      <pubDate>Sun, 18 Nov 2007 16:13:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104439#M30781</guid>
      <dc:creator>Ben Stokes</dc:creator>
      <dc:date>2007-11-18T16:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: A bug in proliant support pack for RHEL 4??</title>
      <link>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104440#M30782</link>
      <description>I've not seen this particular error when installing the PSP on a RHEL4 system.&lt;BR /&gt;&lt;BR /&gt;Not know what server you have, my first thought is you are using iLO in the shared NIC port mode?&lt;BR /&gt;&lt;BR /&gt;I don't know if iLO changes the ports MAC address when in this mode.&lt;BR /&gt;&lt;BR /&gt;as a test and possible workaround in /etc/sysconfig/network-scripts/ifcfg-eth0 remark out the HWADDR line. The system will work fine without it.&lt;BR /&gt;&lt;BR /&gt;I normally remove this entry as I move drives around to different servers in my test lab.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 18 Nov 2007 20:57:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104440#M30782</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2007-11-18T20:57:53Z</dc:date>
    </item>
    <item>
      <title>Re: A bug in proliant support pack for RHEL 4??</title>
      <link>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104441#M30783</link>
      <description>Hi Jimmy&lt;BR /&gt;&lt;BR /&gt;That didn't work - if I comment that line and restart the network I then get a message that the bnx2 device is not present. &lt;BR /&gt;&lt;BR /&gt;I then tried "modprobe bnx2" and it tells me "incorrect module format".&lt;BR /&gt;&lt;BR /&gt;depmod -a and then modprobe again just gives the same error. &lt;BR /&gt;&lt;BR /&gt;I found another thread this morning which appears to be exactly the same problem so I'll follow up in there. Looks like this is an issue with PSP on some new systems. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1113552" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1113552&lt;/A&gt;</description>
      <pubDate>Mon, 19 Nov 2007 05:03:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104441#M30783</guid>
      <dc:creator>Ben Stokes</dc:creator>
      <dc:date>2007-11-19T05:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: A bug in proliant support pack for RHEL 4??</title>
      <link>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104442#M30784</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;PSP builds its own kernel and sets it up to run in /boot/grub/grub.conf&lt;BR /&gt;&lt;BR /&gt;Tehre is no reason to use it. iLo does not work with the kernel at all, it has its own mini-OS built in.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 19 Nov 2007 08:11:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/a-bug-in-proliant-support-pack-for-rhel-4/m-p/4104442#M30784</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-11-19T08:11:01Z</dc:date>
    </item>
  </channel>
</rss>

