Hi, Nathan! Trying to kill the keyboard, Nathan Meyers ([EMAIL PROTECTED]) produced 5,1K in 116 lines: > Turns > out that the driver doesn't like to share interrupts, whereas normal behavior > for PCI devices is to all share a single interrupt. For interrupt-sharing both hardware and software have to support that feature, which is not a 'given' in either of them. > Feb 3 17:13:36 morse kernel: [059] 0 fdc-io.c (fdc_probe) - Type i82078-1 or >5Volt i82078SL FDC found. We find something we think is the card ... > Feb 3 17:14:08 morse kernel: [061] 0 ftape-ctl.c (ftape_activate_drive) - No >tape drive found. ... but not the Max. Hmmm ... -Wolfgang
- Trying (& failing) to use ftape + bpck + 2.2 on D... Nathan Meyers
- Re: Trying (& failing) to use ftape + bpck +... Joan Carles Soler
- Re: Trying (& failing) to use ftape + bpck +... Nathan Meyers
- Re: Trying (& failing) to use ftape + bp... Wolfgang Weisselberg
- Re: Trying (& failing) to use ftape ... Nathan Meyers
- Re: Trying (& failing) to use ft... Nathan Meyers
- Re: Trying (& failing) to u... Nathan Meyers
- Re: Trying (& failing) ... Wolfgang Weisselberg
- Re: Trying (& faili... Nathan Meyers
- Re: Trying (& faili... Jochen Hoenicke
- Re: Trying (& faili... Nathan Meyers
- ftape+bpck-fdc : Seagat... C. Tsotras
- ftape driver memory corrupt... Nathan Meyers
