Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][tlug] Detect firewire drive
- Date: Tue, 14 Nov 2006 21:52:45 +0900
- From: Darren Cook <darren@example.com>
- Subject: [tlug] Detect firewire drive
- User-agent: Thunderbird 1.5.0.8 (X11/20061107)
My recent rant against FC5 didn't get any responses to the seed problem that triggered the rant. So I thought I'd ask again, calmly and without emotion ('cos the cursed ***** thing still doesn't ***** work). I have a firewire DVD writer. As it is triggering the FC5 udev bug I plugged it into my server which is still running FC4. I switched it on and rebooted. Burnt my backup DVD. All is hunky dory. Now, though I switched it off, that server hasn't been rebooted. But when I switch the drive back on it is not detected. Well, it almost is, as I get this in the log: kernel: ieee1394: Error parsing configrom for node 0-00:1023 I tried everything I know, which only amounts to two things: 1. echo "scsi add-single-device 0 0 0 0" >/proc/scsi/scsi 2. kudzu The scsi command did nothing as expected; I think it was something that only worked back on FC3, or maybe never worked. After kudzu I got: ieee1394.agent[22471]: ... no drivers for IEEE1394 product 0x/0x/0x This all looks like an unsupported or broken device, but then why does it get detected okay if I do a reboot? Is there some "service nantoka restart" command, or similar magic, I can run? Darren
- Follow-Ups:
- Re: [tlug] Detect firewire drive
- From: Joe Larabell
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] FTTH providers
- Next by Date: Re: [tlug] Detect firewire drive
- Previous by thread: Re: [tlug] Sun Java GPLv2
- Next by thread: Re: [tlug] Detect firewire drive
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links