LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-09-2011, 04:28 PM   #1
yaximik
Member
 
Registered: Nov 2010
Posts: 87

Rep: Reputation: 0
Unhappy Firewire Support in RHEL55/SL55


Hi everyone,

I want to add a Lacie external drive to x64 box with SL55, but it has only Firewire interface. After searching a bit the net I could not find a working solution how to make the PCI card and the drive recogizable by the system, even if I removed Firewire from RHEL blacklist. The system does not see this piece of hardware. Does anyone has a positive experience with RHEL/SL with that issue? Similar trends search lists only quite old treads - ane recent experience?
 
Old 07-09-2011, 04:46 PM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello yaximik,

at least your kernel must support firewire. You can check this with the following command within your kernelsources
Code:
grep -i firewire .config
as an example here the output on my system
Code:
# IEEE 1394 (FireWire) support
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
CONFIG_FIREWIRE_NOSY=m
CONFIG_DVB_FIREDTV_FIREWIRE=y
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
Markus
 
Old 07-10-2011, 01:05 AM   #3
yaximik
Member
 
Registered: Nov 2010
Posts: 87

Original Poster
Rep: Reputation: 0
Thanks. The check returned nothing. I looked available repos and see that ieee1394-2.618-2.el5.x86_64 (IEEE 1394 (FireWire) support) is present but not instaleed. I tried Package Manager to install it, but failed due to missing dependency vmlinuz-2.6.18-238.12.1.el5. I used ##yum search ieee1394## and found ieee1394.x84_64, which looked promising. Then ##yum install ieee1394.x84_64##, but ended up again with the same missing dependency. Upon boot I see kernel /vmlinuz-2.6.18-194.3.1.el5, I guess it just needs the more recent one.

I searched for RHEL5/SL5 - specific repo on rpm.pbone.net and found only kernel-2.6.18-238.1.2.1.el5.x86_64 in several repositories. I guess the package contains the required vmlinuz*, but I am hesitant to mess with the entire kernel. Is there a way to extract and install only the needed vmlinuz*? Or there is nothing to worry about, just run the Package Manager to install/upgrade the whole thing?
 
Old 07-10-2011, 02:36 AM   #4
Elv13
Member
 
Registered: Apr 2006
Location: Montreal,Quebec
Distribution: Gentoo
Posts: 825

Rep: Reputation: 128Reputation: 128
Use your own kernel if you don't mind. Sometime, you have to use RHEL kernel for some proprietary hardware with precompiled drivers, but if you don't and dont care about the support contract issues it create, just go to kernel.org and roll your own, it is very easy.
 
Old 07-10-2011, 03:39 AM   #5
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello yaximik,

it is nothing which can be installed, you should check if your kernel supports firewire yet. Post the output of the above command or this one
Code:
zgrep -i firewire /proc/config.gz
If the kernel does not support firewire, you'll only have to build a new one which supports it as Elv13 stated. But you can use the sources of your old kernel and have only to change the firewire-support.

Do you have the kernel-sources installed on your system?

EDIT: I've Centos running in a virtual machine and checked this, the above command will not work, use instead the grep command within the /boot directory
Code:
grep -i firewire config-2.6*
where you use the name of the configfile instead of the "*".


Markus

Last edited by markush; 07-10-2011 at 03:45 AM. Reason: added a new command
 
1 members found this post helpful.
Old 07-10-2011, 10:37 AM   #6
yaximik
Member
 
Registered: Nov 2010
Posts: 87

Original Poster
Rep: Reputation: 0
Well, this time it shows that I should have support, correct?

[yaximik@SciLinux55 boot]$ grep -i firewire config-2.6.18-194.3.1.el5
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
# IEEE 1394 (FireWire) support

But I cannot see the disk connected by to firewire PCI card. Is there something missing or needs to be checked?
 
Old 07-10-2011, 11:55 AM   #7
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
You could use the dmesg command and check if the firewire-device is mentioned there. You could even post the whole output of dmesg as an attachment to your post in txt-format.

I'm not sure for what one has to look in order to find a firewire-device with dmesg.

Markus
 
Old 07-10-2011, 12:47 PM   #8
yaximik
Member
 
Registered: Nov 2010
Posts: 87

Original Poster
Rep: Reputation: 0
Nope.

##dmesg | grep ieee1394## or #dmesg | grep firewire## both return nothing. Attached is dmesg output.

Here is actually the whole section from /boot/config-2.6.18-194.3.1.el5

#
# Enable only one of the two stacks, unless you know what you are doing
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
Attached Files
File Type: txt dmesg.txt (23.9 KB, 7 views)

Last edited by yaximik; 07-10-2011 at 12:50 PM.
 
Old 07-10-2011, 01:27 PM   #9
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello yaximik,

the last thing you can do (if not anyone in this forum knows what's going on), you're running RHEL, which is an enterprise-distribution and you've paid for support. I think you should ask Redhat for support.

Markus
 
Old 07-10-2011, 03:45 PM   #10
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,360
Blog Entries: 55

Rep: Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547
There's talk of a PCI card but dmesg doesn't show it (as in 'lspci -v')?
 
Old 07-10-2011, 03:58 PM   #11
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello,

@unSpawn: I don't really get what you wrote, do you think the card is not available/damaged?

I have a firewire-card in my server, here is the part in dmesg
Code:
[    7.282338] firewire_ohci 0000:03:08.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    7.349855] firewire_ohci: Added fw-ohci device 0000:03:08.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11
[    7.915407] firewire_core: created device fw0: GUID 1e00000000008c00, S400
where lspci -k says
Code:
srv-zuhause:~# lspci -k | grep -i fire
03:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire-ohci
There is no device connected via firewire at my server.

Since at the OP's firewire-device does not show up in dmesg, we should look at the output of
Code:
lspci -k | grep -i fire
Maybe a kernelmodule is missing.

Markus

Last edited by markush; 07-10-2011 at 04:00 PM.
 
Old 07-10-2011, 06:03 PM   #12
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,360
Blog Entries: 55

Rep: Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547
Quote:
Originally Posted by markush View Post
I don't really get what you wrote
Yes you do and what you wrote slash suggested is evidence of that.
 
Old 07-10-2011, 10:33 PM   #13
yaximik
Member
 
Registered: Nov 2010
Posts: 87

Original Poster
Rep: Reputation: 0
Smile <SOLVED>Firewire Support in RHEL55/SL55

Wow, that was quite a rite of passage... Just like Markus implied, may be someone out there knows what the hell is going on. The problem is that I was trying to get FireWire support on my SL55 box at home, not on my RHEL55 in my office, so I was on my own with this problem, no pre-paid support. However, the problem is solved and I post the pathway here in hope someone finds it helpful. Never give up!

Since for whatever reason my current vmlinuz-2.6-194.3.1.el5 was not sufficient to install the needed ieee1394-2.6.18-2.el5.x84_64 due to a missing dependency on vmlinuz-2.6-238.12.1.el5 (as reported by both pirut and yum), and no discernible reason why the current kernel cannot support ieee1394 was identified, I had no choice but to install kernel-2.6-238.12.1.el5. I explored the previous experience on the net and found I can do this safely as long as I can boot from CD and make changes in /boot/grub/grub.conf. All I needed is to move up and down a few lines:

#quote#
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Scientific Linux SL (2.6.18-238.12.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-238.12.1.el5 ro root=/dev/VolGroup00/LogVol00 rhg
b quiet
initrd /initrd-2.6.18-238.12.1.el5.img

title Scientific Linux (2.6.18-194.3.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
initrd /initrd-2.6.18-194.3.1.el5.img

#end quote#

So I could now boot with either kernel version. What I found that *238* works just fine except that I completely lost my wireless card support. The kernel did not accept the existing MAC address of the adaptor treating it as wrong (?). Everything returned to the normal when I boot back to *194*.

I tried to reinstall linux-wlan-ng-0.2.9, where prism2_usb driver came from and was working fine with *194*, with *238* kernel. It failed miserably since no 2.6.18-238.12.1.el5-x86_64 source folder was not present in /usr/src/kernels/ (??!), only previous 2.6.18-194.3.1.el5-x86_64. I could not find *238* source anywhere in the directory tree, but the *238* kernel was installed and was working just fine. Without network access with *238* I could run yum or pirut, since repositories on the net were still needed. However, if I boot back to "194*, the vmlinuz-2.6-238.12.1.x86_64 library is still in the /boot directory, so what the heck? I tried to install ieee1394-2.6.18-2.el5.x84_64 again with *194*, and guess what? It was completed successfully this time.

However, I still could not see any references to ieee1394 either in dmesg or lspci -v outputs even after reboot. Last suggestion from the replies was to check whether the card is available/damaged. Well, this is something I needed to check from the very beginning, even before I boot to Linux for the first time. So I hit F2 upon reboot and found that all my PCI slots are disabled, so nothing shows up in any of 4 slots shown in the system configuration. I have no idea how this has happened, by factory default PCI should be "on", but it was "off". I turned it "on" and voila! - "FireWire" was displayed in slot 2.

However, reboot to "194" still did not yield ieee1394 support since dmesg sill has nothing about FireWire or ieee1394. But, lspci -v yielded something different now:

04:00.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 61) (prog-if 10 [OHCI])
Subsystem: Agere Systems FW322/323

So, I rebooted again into "238*. Voila! lspci -v indicated I got it working!

04:00.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 61) (prog-if 10 [OHCI])
Subsystem: Agere Systems FW322/323
Flags: bus master, medium devsel, latency 64, IRQ 169
Memory at fe5ff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

Indeed, connected drive was mounted on desktop and opened.

Well, now I got FireWire but lost wireless card support. Not a good trade-off... To re-compile linux-wlan-ng-0.2.9 I needed to have /lib/modules/2.6.18-238.12.1.el5/build directory (by analogy to /lib/modules/2.6.18-194.3.1.el5/build that was needed with the "194" kernel, which was successful install). /lib/modules/2.6.18-194.3.1.el5/build is actually a symbolic link to /usr/src/kernels/2.6.18-194.3.1.el5-x86_64, but as I mentioned there was nothing for *238* in /usr/src/kernels/. So I just copied this symbolic link named "build" to /lib/modules/2.6.18-238.12.1.el5/, even if it still pointed to actual *194* source. I also created in the /lib/modules/2.6.18-238.12.1.el5/ directory symbolic links "source" pointing again to /usr/src/kernels/2.6.18-194.3.1.el5-x86_64 (as it was in /lib/modules/2.6.18-194.3.1.el5/) and linux-wlan-ng pointing to to /lib/modules/2.6.18-194.3.1.el5/linux-wlan-ng. Tnis time recompile only reported that the actual source is *194* (duh!), but nevertheless completed and after configuring the driver according to README I got back my wireless network.

Whoa!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
how to find out if your kernel has support for firewire dr_zayus69 Linux - Hardware 1 03-24-2005 07:48 AM
Firewire support in RHEL 4??? jverge Red Hat 0 03-03-2005 08:52 PM
Firewire support at boot BeginnerX1 Linux - Software 3 10-26-2004 03:05 PM
Firewire support question megaspaz Linux - Laptop and Netbook 2 09-16-2003 01:58 PM
Firewire support Mandrake 9.1 davecs Linux - Hardware 1 05-28-2003 06:51 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration