Skip to contentSkip to conversation

Firewire Buslink dirve incorrectly detected as a LiteOn in 2.4.20

DISCUSSION MaxF 3 participants 3 messages Feb 9, 2003

lore
Share & tools
lore

MaxF

author
#0 lore raw

All kernels post 2.4.20-xx are detecting my firewire Buslink CD-RW as:

Feb  9 07:54:19 maxer kernel:   Vendor: LITE-ON   Model: LTR-48125W        Rev: VS06

Buslink model #RW4848FE

I do have however a second drive that is a Lite-On, but is not firewire.

Any ideas?

Frank

#1 lore raw
Quoted 9 lines · MaxF

All kernels post 2.4.20-xx are detecting my firewire Buslink CD-RW as:

Feb  9 07:54:19 maxer kernel:   Vendor: LITE-ON   Model: 

LTR-48125W Rev: VS06

Buslink model #RW4848FE

I do have however a second drive that is a Lite-On, but is not firewire.

Can you give some more details, like a complete description of your system configuration including this other drive that appears to tbe confusing the scsi layer.

Signature · 4 lines
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/
#2 lore raw
In reply to MaxF
Quoted 11 lines · MaxF

All kernels post 2.4.20-xx are detecting my firewire Buslink CD-RW as:

Feb  9 07:54:19 maxer kernel:   Vendor: LITE-ON   Model: 

LTR-48125W Rev: VS06

Buslink model #RW4848FE

I do have however a second drive that is a Lite-On, but is not firewire.

Any ideas?

Many of the Buslink FireWire drives have Lite-On drives inside. The output you pasted is exactly what I'd expect from a BusLink FireWire CD-RW.

Is this a change in behavior from previous kernels (i.e., did it show something different in the past?) If so, what did an older kernel show? If there's a difference, that could indeed be a bug.

Conversely, if you're merely surprised that one company manufactured the drive and a different company put the drive into a FireWire enclosure, I wouldn't consider that to be a bug in Linux.

-Barry K. Nathan <[email protected]>