Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a 1.5 T external Firewire drive (Newegg ministack v3) connected using a ieee1394b cable. I don't always have it turned on, but turn it on first before booting if I want to back things up. I dual boot Windows XP SP3 as well as Ubuntu 12.04LTS but recently reinstalled Slackware 14. I had a broken Slackware 13.37 setup.
Here's where it gets weird: sometime ago, Windows and Ubuntu stopped recognizing the presence of the Firewire drive. It was though it wasn't plugged in or turned on. I tried a different port, same result. I have an old ieee1394a camera, still recognized by both. I checked dmesg, checked lspci, lsmod, forced module loading of the firewire modules in Ubuntu, still as though it wasn't there. No hardware detection under Windows either, although it used to be reliably detected. Of course Ubuntu and Windows get "updated" regularly, so the software on both could have gotten simultaneously hosed by some update, but how likely is that? So I assumed that the PCI firewire card or drive had failed.
But Slackware 14 finds it and mounts it as though nothing is wrong.
So aside from the obvious conclusion, (Slackware rules) what the devil is going on?
Here's fdisk -l; essentially identical to Ubuntu's report except for the presence of sdf.
Code:
bash-4.2# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf539481b
Device Boot Start End Blocks Id System
/dev/sda1 * 63 204796619 102398278+ 7 HPFS/NTFS/exFAT
/dev/sda2 204797952 208795647 1998848 82 Linux swap
/dev/sda3 208797694 625141759 208172033 5 Extended
/dev/sda5 208797696 625141759 208172032 83 Linux
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0x003f of partition table 5 will be corrected by w(rite)
Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004eed3
Device Boot Start End Blocks Id System
/dev/sdc1 256 3999999 1999872 82 Linux swap
/dev/sdc2 4000254 625161983 310580865 5 Extended
/dev/sdc5 ? 8145150 1065125948 528490399+ 3f Unknown
Disk /dev/sdb: 250 MB, 250640384 bytes
64 heads, 32 sectors/track, 239 cylinders, total 489532 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x19cb014e
Device Boot Start End Blocks Id System
/dev/sdb4 * 32 489471 244720 6 FAT16
Disk /dev/sdd: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sde: 300.1 GB, 300090728448 bytes
255 heads, 63 sectors/track, 36483 cylinders, total 586114704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x25241fff
Device Boot Start End Blocks Id System
/dev/sde1 * 63 122881184 61440561 7 HPFS/NTFS/exFAT
/dev/sde2 122881185 125949599 1534207+ 83 Linux
/dev/sde3 125949600 586099394 230074897+ 83 Linux
Disk /dev/sdf: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5d5bd477
Device Boot Start End Blocks Id System
/dev/sdf1 2048 2930276351 1465137152 83 Linux
Here's lspci"
Code:
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 05)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 05)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 05)
00:1f.2 USB controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 05)
00:1f.4 USB controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4600] (rev a3)
02:01.0 Modem: Agere Systems Venus Modem (V90, 56KFlex)
02:02.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01)
02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
02:04.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 15)
02:05.0 RAID bus controller: Promise Technology, Inc. PDC20271 (FastTrak TX2000) (rev 02)
02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
02:08.0 Ethernet controller: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
02:09.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
03:08.0 USB controller: NEC Corporation USB (rev 41)
03:08.1 USB controller: NEC Corporation USB (rev 41)
03:08.2 USB controller: NEC Corporation USB 2.0 (rev 02)
03:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
I would backup all the data on the drive before anything else. It's great that Slackware recognizes the drive, but if Window$ and other distros don't then I wouldn't trust it.
I would backup all the data on the drive before anything else. It's great that Slackware recognizes the drive, but if Window$ and other distros don't then I wouldn't trust it.
That's quite a good advice, but before beeing pessimistic I would check if there is a more simple explanation for this issue.
You could check if the Ubuntu-kernel has the module for the firewire device available. In Slackware execute
Code:
lspci -k | grep -iA3 fire
this will show you which module is loaded for the firewiredevice. Afterwards you can check in Ubuntu if the module is present. As an example on my system (Slackware64-14.0)
Code:
zgrep -i fire /proc/config.gz
# IEEE 1394 (FireWire) support
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
CONFIG_FIREWIRE_NOSY=m
CONFIG_ATM_FIRESTREAM=m
CONFIG_ADAPTEC_STARFIRE=m
# Supported FireWire (IEEE 1394) Adapters
CONFIG_DVB_FIREDTV=m
CONFIG_DVB_FIREDTV_INPUT=y
CONFIG_SND_USB_6FIRE=m
CONFIG_SND_FIREWIRE=y
CONFIG_SND_FIREWIRE_LIB=m
CONFIG_SND_FIREWIRE_SPEAKERS=m
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
as you can see firewire is available in Slackware's kernel, as you already said. But please use the modulename instead of "fire".
Thank you for your response. H_TexMex_H, I'm guessing the PCI card/motherboard, not the drive, as the drive and enclosure are new and infrequently used, whereas the mobo is 10+ years old. Having said that, it is a backup drive, and the data is being backed up elsewhere as this one has been unusable for a while.
Markus,
The Ubuntu output for Slackware and Ubuntu was identical for lspci -k:
insmod: error inserting 'firewire-core.ko': -1 Unknown symbol in module
even though uname -r gives 3.2.0-34-generic
I did this instead of /proc/config.gz
cat /usr/src/linux-headers-3.2.0-34-generic/.config | grep -iA3 fire
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_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
--
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_NICSTAR=m
--
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_NET_VENDOR_ALTEON=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
--
# Supported FireWire (IEEE 1394) Adapters
#
CONFIG_DVB_FIREDTV=m
CONFIG_DVB_FIREDTV_INPUT=y
#
# Supported Earthsoft PT1 Adapters
--
CONFIG_SND_USB_6FIRE=m
CONFIG_SND_FIREWIRE=y
CONFIG_SND_FIREWIRE_LIB=m
CONFIG_SND_FIREWIRE_SPEAKERS=m
CONFIG_SND_ISIGHT=m
CONFIG_SND_PCMCIA=y
CONFIG_SND_VXPOCKET=m
--
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
And why the heck is firefox reporting that I'm posting from Windows 7? Oi! Got to change browsers again. Or distros, as firefox didn't do that under Slackware.
Last edited by mostlyharmless; 12-02-2012 at 04:13 PM.
HTex: There's no drive showing in /dev, under sdd or anything else, such as /disk/by-uuid
Under Slackware it gets assigned sdf and shows up fine.
Markus, I'm pretty convinced that it's the mobo and the FireWire card. I've deferred investigation of the hardware for now as I have other backups and am probably needing a new computer anyway. I guess I could try plugging the thing in with one of its USB ports. It's just weird that Slackware picked it up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.