Quantum Ultrium LTO4 tape drive not recognized

[bekks]

Quantum Ultrium LTO4 tape drive not recognized, lsscsi doesnt show it, nor there are entries besides sg* for that device. The device is connected through an SAS controller.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-28-generic 2.6.35-28.49
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices: **** List of CAPTURE Hardware Devices ****
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe7e8000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Mar 30 21:19:44 2011
HibernationDevice: RESUME=UUID=f3246e80-9667-4860-aabb-5b5aeb20dca4
IwConfig: Error: [Errno 2] No such file or directory
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7549
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=396764b3-54ed-41fc-86f9-6a3db2f20c23 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.ISO-8859-15
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.5
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
dmi.bios.date: 12/02/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V8.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 785GTM-E45 (MS-7549)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.8:bd12/02/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7549:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785GTM-E45(MS-7549):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7549
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

[bekks (bekks)]

Dear submitter,

please add these attachments as single files:

1) uname -a > uname-a.log
2) cat /proc/version_signature > version.log
3) dmesg > dmesg.log
4) sudo lspci -vnvn > lspci-vnvn.log

[northalpha (northalpha)]

As requested

[penalvch (penalvch)]

Eduard Warkentin, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Charles McColm (chaslinux)]

So I have the Quantum Ultrium LTO 3 and I'm able to access it using mt tools (erasing a cartridge right now). Using 12.04. I noticed Eduard reported it as /dev/sg. My device is recognized/accessible as /dev/st0 (not sg).

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]