Re: [gentoo-amd64] initio seen, mt -f doesn't work
Hi, When I modprobe initio I get the single word 'killed' at which the whole system freezes and I have to switch off at the box. Do I need to modify the kernel? Thanks. On Fri, 2005-12-09 at 12:14 -0600, Brett Johnson wrote: On Fri, Dec 09, 2005 at 05:55:28PM +, Gavin Seddon wrote: Thanks Which modules do I need to add to 'etc/modules.autoload.d/kernel-2.6'? Gavin. Assuming that doing the 'modprobe initio' worked for you, that's all you need to put into the /etc/modules.autoload.d/kernel-2.6. It appears everything else you need (and more) is already configured properly. Brett -- Dr Gavin Seddon School of Pharmacy and Pharmaceutical Sciences University of Manchester Oxford Road, Manchester M13 9PL, U.K. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] initio seen, mt -f doesn't work
On Sun, Dec 11, 2005 at 10:32:20AM +, Gavin Seddon wrote: Hi, When I modprobe initio I get the single word 'killed' at which the whole system freezes and I have to switch off at the box. Do I need to modify the kernel? Thanks. What model initio board do you have? There are two different initio drivers, and the one called initio is for the 9100 series chipset. It's possible loading the wrong chipset could lock up the pc, or at least the console. When the console locks up, I like to go to a different terminal (pc) and see if I can ping the frozen pc. If so, then try to ssh in (assuming ssh is running) and see if I can shut it down remotely. All you should need configure in the kernel is: CONFIG_SCSI: SCSI device support CONFIG_CHR_DEV_ST: SCSI tape support And depending of the controller chipset, either: CONFIG_SCSI_INITIO: Initio 9100U(W) support CONFIG_SCSI_INIA100: Initio INI-A100U2W support This assumes you don't have an Onstream tape drive of a multi slot tape drive. If so, there are a few extra drivers needed, but that's not the issue you are having at this time. If the tape drive is external, you can try and shut off the drive before you boot the PC and then see if you can get the module to load. It's possible that there is something wrong with the SCSI bus (bad tape drive, improper termination) that is causing the driver to hang the system. You should also confirm you have proper termination on the SCSI bus. Also, you can refer to: http://www.initio.com/support/download.htm#pc. It appears the inito driver in the kernel supports most of their boards, but if you have a really old board (INI-9100/9100W), you may need to download a seperate driver. There is also a link to flash the bios, but I would only try that as a last resort. Brett -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] initio seen, mt -f doesn't work
st: Version 20050830, fixed bufsize 32768, s/g segs 256 It appears to me that the st driver is loading properly, but I did not see any sign of the SCSI driver loading in the dmesg output. This could be becuase you have the module compiled as a module, in which case you can jump to the last paragraph. If you're not sure if the driver is configured in the kernel, you can check it quickly by typing 'grep INITIO /usr/src/linux/.config' If the output says # CONFIG_SCSI_INITIO is not set, you will need to run 'genkernel --menuconfig all', navigate to the Device Drivers - SCSI device support - SCSI low-level drivers and enable Initio 9100U (W) support. With this being a tape drive, I'd probably select module as opposed to compiling into the kernel. Once the build is complete, install the new kernel and modules, and reboot. (Assuming you picked module, his step is probably optional, since all we did was add a module, but I like to reboot to be safe). Now, just run 'modprobe initio' and it should load without any errors. The last step is to check 'lsmod' and 'dmesg | tail'. You should see the scsi card loaded, and the tape drive and assigned a device name (st0). Brett -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] initio seen, mt -f doesn't work
Hi, I have a scsi tape with an initio controller. 'dmesg' sees initio 360p. But when I use mt I get ' mt -f /dev/st0 eject /dev/st0: No such device or address' Where will the tape be? Thanks. -- Dr Gavin Seddon School of Pharmacy and Pharmaceutical Sciences University of Manchester Oxford Road, Manchester M13 9PL, U.K. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] initio seen, mt -f doesn't work
On Thu, Dec 08, 2005 at 01:25:07PM +, Gavin Seddon wrote: Hi, I have a scsi tape with an initio controller. 'dmesg' sees initio 360p. But when I use mt I get ' mt -f /dev/st0 eject /dev/st0: No such device or address' Where will the tape be? Thanks. First thing I would check is the output of dmesg, you may need to reboot depending on how many messages were added since the last reboot. You should some entries where the kernel detectes the drive (by model number) and assigns it a device name (st0). As an example, look for your primary hard drive entry (hda, hde, sda etc). There should be a similar entry for st0 after it detects the tape drive. If not, that most likely means the kernel is missing some required driver(s). It sounds like you have the scsi adapter configured and loaded, do you have scsi tape support configured and loaded (if a moduled)? -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] initio seen, mt -f doesn't work
Brett Johnson wrote: As an example, look for your primary hard drive entry (hda, hde, sda etc). There should be a similar entry for st0 after it detects the tape drive. he could also post a gzip'd copy of his dmesg, or better yet.. provide a link to it. -- gentoo-amd64@gentoo.org mailing list
