<?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 firewire drive... in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532616#M17258</link>
    <description>All,&lt;BR /&gt;I am using an external firewire drive (maxtor). I am running rh9 with kernel 2.4.30.  I am able to load ohci1394 and sbp2 module. When I do a dmesg, I do not see any instance of sd? bieng recognize by the system.  Also did fdisk -l, no instance of firewire drive.  Any idea?  Thanks.</description>
    <pubDate>Tue, 26 Apr 2005 22:27:17 GMT</pubDate>
    <dc:creator>K.C. Chan</dc:creator>
    <dc:date>2005-04-26T22:27:17Z</dc:date>
    <item>
      <title>firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532616#M17258</link>
      <description>All,&lt;BR /&gt;I am using an external firewire drive (maxtor). I am running rh9 with kernel 2.4.30.  I am able to load ohci1394 and sbp2 module. When I do a dmesg, I do not see any instance of sd? bieng recognize by the system.  Also did fdisk -l, no instance of firewire drive.  Any idea?  Thanks.</description>
      <pubDate>Tue, 26 Apr 2005 22:27:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532616#M17258</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2005-04-26T22:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532617#M17259</link>
      <description>did you try rebooting the system once. Linux 2.4 is not so good in detecting hot plug&amp;amp;play devices. &lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Gopi</description>
      <pubDate>Wed, 27 Apr 2005 00:45:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532617#M17259</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-04-27T00:45:02Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532618#M17260</link>
      <description>If it doesn't auto detect, try the 2.6 kernel.&lt;BR /&gt;&lt;BR /&gt;Otherwise out of luck.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 27 Apr 2005 00:56:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532618#M17260</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-04-27T00:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532619#M17261</link>
      <description>What's in your boot.log? If no errors appear, listen to "uncle Steven" and upgrade your kernel.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;&lt;BR /&gt;Renarios</description>
      <pubDate>Wed, 27 Apr 2005 06:55:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532619#M17261</guid>
      <dc:creator>renarios</dc:creator>
      <dc:date>2005-04-27T06:55:56Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532620#M17262</link>
      <description>Do You have a scsi disk driver module loaded?&lt;BR /&gt;&lt;BR /&gt;I stumbled over this a few weeks ago when using an USB stick, linux also showed my the usb, but not the mass storage device until I modprobed the additional driver.</description>
      <pubDate>Wed, 27 Apr 2005 07:46:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532620#M17262</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-04-27T07:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532621#M17263</link>
      <description>Using the directions from &lt;BR /&gt;&lt;A href="http://www.linux1394.org/" target="_blank"&gt;http://www.linux1394.org/&lt;/A&gt;&lt;BR /&gt;I ran their rescan-scsi-bus.sh script before the device was mapped to a scsi device. Link to the script on this page:&lt;BR /&gt;&lt;A href="http://www.linux1394.org/sbp2.php" target="_blank"&gt;http://www.linux1394.org/sbp2.php&lt;/A&gt;&lt;BR /&gt;OK, I have attached it.&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Apr 2005 11:02:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532621#M17263</guid>
      <dc:creator>Hank Ratzesberger</dc:creator>
      <dc:date>2005-04-27T11:02:37Z</dc:date>
    </item>
    <item>
      <title>Re: firewire drive...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532622#M17264</link>
      <description>it works when I added entry into scsi dir under /proc, but why? why does one have to do this?, why can't it work when the module is loaded? It works on a redhat standard kernel, but when I roll my own (2.4.30) with proper modules loaded, it needed the extra mile just to get it to see the maxter firewire drive. Any idea?  Thanks.</description>
      <pubDate>Wed, 27 Apr 2005 22:36:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/firewire-drive/m-p/3532622#M17264</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2005-04-27T22:36:46Z</dc:date>
    </item>
  </channel>
</rss>

