Jos van de Ven wrote:
>
> On Wed, Jun 30, 1999 at 03:35:48PM +0200, Peter Suetterlin wrote:
> > xander wrote
> > >
> > > > In case of the SB-driver (I'm using alsa 0.3.2) I am able to load the
> > > > driver (modprobe snd-sb16 or snd-sbawe). Only when I try to actually
> > > > play some sound, it crashes.
> > >
> > > I'd suggest not using alsa 3.2.0. I've experienced kernel crashes and
> > > memory leaks (??) with it (also uninitialized modules). This happened with
> > > 3 systems (of which 2 aren't mine and single-cpu) and 2.2.10.
> >
> > I'll watch it carefully, thanks for the warning!
> >
> > > I'm sorry for the off-topic answer; you probably have tried a config
> > > without alsa.
> >
> > No, not really OT. But yes, it's not connected to alsa (which I'm very
> > content with up to now, btw), it also happens when alsa is not loaded.
> >
> > That's why I had the ISA stuff in mind - both the SB and SCSI are ISA
> > cards. OTOH, the (onboard) serial and parallel interfaces do work...
> >
> > Peter
>
> I don't think it is ISA trouble. I don't have isa cards (in fact I do,
> but I tried to eliminate causes by taking my Gravis UltraSound MAX out
> of my computer) that can couse the trouble. I couldn't acces my SCSI
> stuff, and my computer did not boot anymore, till I switched back to
> an old SCSI driver. (Onboard AIC7880) Strange fact, but it can be related
> to my long SCSI cables. (WinNT does not work either, but I don't care)
> It all appears to be a interrupt question with GA586DX boards. I have heard
> this far more often. But a point of info request: which revision of the
> board do you have? (1, 2 or 3?) I have got rev. 3.
> Let me describe something else noticed with this board: I receive often
> the message 'recvmsg bug copied <xxxxx>' I haven't had time to investigate,
> but I remember a message I saw about this bug being related to unexpected
> interrupts. As the person who spoke about it, had got a GA586DX too, I
> expect it to be related to the board. There should be a patch around to
> check for unexpected interrupts. You should search through the archives
> of the Linux Kernel.
> And I too have got problems with the g_NCR5380, but that also happens in
> my UP board. I never got it to work, so I decided to connect my scanner to
> the same SCSI bus as my Zip, Atlas III, Plextor 20x CD-ROM, Plextor 20x2x4x
> CD-Writer, which appears to cause trouble with the SCSI support in newer
> kernels and in WinNT.
> So concluding, I think the problems is with interrupts, (you had to use
> 'noapic' to make it work, I didn't), and the problems are about many devices,
> all using interrupts (sound gives problems as soon as interrupts occur...)
>
> Greetings,
> Jos van de Ven
>
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
I can't second your experience.
I have a Gigabyte GA586DX with two P166MMX and 128MB RAM.
I don't use IDE, only SCSI devices connected to the onboard adapter.
I have sound SB16, Matrox MilII.
HD, CDROM, CDRW and DAT on AIC7xxx.
For my scanner I recently use the dtc3181 adapter with g_NCR5380 driver set
up with the correct parameters. Works ok, but the scanner is _much_ faster
when
connected to the adaptec. When I connect all of the SCSI devices of which some
are external, the cable gets too long and the box refuses to boot. But when it
boots afterwards I don't get into any trouble.
My board rev. is 3b with the apropriate BIOS. My system is SUSE 6.1 kernel
2.2.5
no specific patches, plain install. And I use IOAPIC.
Cheers
--
Joachim
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
