SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Recently I was trying to get a SCSI adapter with SYM53C8XX chipset running on Slackware 10.2, but no luck. I have a Kernel 2.6.16 configured specifically for including the Symbios driver Version 2, as instructed on various sites. But the driver doesn't load, it just gave a message "sym0: giving up ..." or similar in the output of dmesg.
It can't be the card, because on my Windoze box, the card works fine. I'm just wondering if it's possible to use it on Linux.
In my Slackware box, my boot drive is a SATA drive, and I'm also having USB drives using the SCSI subsystem. Does this impose any problems?
Nope, that shouldn't pose any problem at all. And I've used a symbios controller
successfully with Slack from versions 8 to 10.2. Admittedly not with a 2.6 kernel,
but I can't imagine that 2.6 should be that broken.
Yeah, I thought of these problems as well. Indeed, the bus isn't terminated properly; I was trying to recover data from an old hard drive, I probably still have the terminators, somewhere ... On Windows, this was no problem, however.
While being on SuSE Linux 10.1 for a while, I had the strange problem, that the Linux kernel froze when nothing was connected to the adapter. But it didn't seem to load the driver either. Back then, I didn't know that the driver reported as "sym0" to the log.
Back on Slackware I noticed that it doesn't matter if anything is connected to the card. The driver exits right away.
The connected SCSI drive has ID #2, and despite the sym0 driver exits immediately after being intialized, the SCSI numbers assigned to other devices had changed; so it DID recognize the drive.
I have one SATA drive, which gets SCSI ID #1, the external drive on the Symbios card that has SCSI ID #2, and an external USB Flash card reader that gets assigned #3 when the external SCSI drive is connected, and #2 otherwise.
Another strange occurrence: Despite the mainboard having no current whatsoever, after I had plugged in the card once, the machine did have a power failure while booting and rebooted. So, could it be a PCI problem? Perhaps the old card doesn't mix well with my mainboard? This mainboard is from 2004, while the one in my Windows box is a couple of years older (from 2001).
Last edited by byte weaver; 09-04-2006 at 05:37 AM.
From that description it may be just about anything ;} from tolerances in
power to insufficient power over to timing issues on the PCI bus.
But on the subject of "old HDDs" .... you are aware that the two controllers
use a different low-level format? It's been a while since I last tried that,
maybe as long as 97, but back then I was trying to hook up an HDD I had initialised
on a Symbios, and the adaptec couldn't handle it at all. I had to low-level the
drive before I could use it with the 2940U2W.