Date: Tue, 01 Dec 1998 23:44:17 -0600 From: Scott Honey <shoney@symmetricsolutions.com> To: Mike Smith <mike@smith.net.au>, freebsd-hackers@FreeBSD.ORG Subject: Re: vpo0 driver not displaying or functioning correctly Message-ID: <3664D3B1.775483A8@symmetricsolutions.com> References: <199812020446.UAA02650@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------E5574D95B003BF1628879FC3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Smith wrote: > > The README document for ppbus and LINT configuration file don't > > tell youto rem out these devices and also doesn't tell you to remove the > > disable. > > It doesn't tell you to remove the other devices because you don't have > to. It doesn't tell you to remove the 'disable' because it's assumed > that anyone actually paying attention will have noticed it already. If you can get it to work without disabling the other devices I would liketo see it. Because without disabling the other devices you get these messages when you boot: Dec 1 20:21:04 synth /kernel: ppc: parallel port found at 0x378 Dec 1 20:21:04 synth /kernel: ppc0 at 0x378 irq 7 on isa Dec 1 20:21:04 synth /kernel: ppc0: SMC Dec 1 20:21:04 synth /kernel: FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode Dec 1 20:21:04 synth /kernel: nlpt0: <generic printer> on ppbus 0 Dec 1 20:21:04 synth /kernel: nlpt0: Interrupt-driven port Dec 1 20:21:04 synth /kernel: ppi0: <generic parallel i/o> on ppbus 0 Dec 1 20:21:04 synth /kernel: lppps0: <Pulse per second Timing Interface> on ppbus 0 Dec 1 20:21:04 synth /kernel: plip0: <PLIP network interface> on ppbus 0 It doesn't even say that the vpo driver is loading and when you try to mount the scsi device (sd0) it tells you that the Device is not configured. The ppbus does not detected the zip drive or If it does detect it, it doesn't configure any devices nodes for it. When I remove the other 4 devices and leave just the controllers and no devices for ppbus the boot messages are as follows: Dec 1 20:29:34 synth /kernel: ppc: parallel port found at 0x378 Dec 1 20:29:34 synth /kernel: ppc0 at 0x378 irq 7 on isa Dec 1 20:29:34 synth /kernel: ppc0: SMC Dec 1 20:29:34 synth /kernel: FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode Dec 1 20:29:34 synth /kernel: vpo0: <Iomega VPIO Parallel to SCSI interface> on ppbus 0 Dec 1 20:29:34 synth /kernel: vpo0: EPP 1.9 mode Wow, its finally being detected, gee if the ppbus is suppose to detected the Zip drive with all the other devices configured, than why doesn't it want to work. Either give me a logical reason why its not working in my case or check it out for yourself. Do you even have a parallel zip drive? One other thing: People come to these mailing lists to get help, not a attitude when we do something wrong. ---------------------------------------------------------------- Scott Honey CEO of Symmetric Solutions, Inc MCSE and Computer Programmer shoney@symmetricsolutions.com http://www.symmetricsolutions.com ---------------------------------------------------------------- --------------E5574D95B003BF1628879FC3 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <HTML> Mike Smith wrote: <BLOCKQUOTE TYPE=CITE>> The README document for ppbus and LINT configuration file don't <BR>> tell youto rem out these devices and also doesn't tell you to remove the <BR>> disable. <P>It doesn't tell you to remove the other devices because you don't have <BR>to. It doesn't tell you to remove the 'disable' because it's assumed <BR>that anyone actually paying attention will have noticed it already.</BLOCKQUOTE> If you can get it to work without disabling the other devices I would liketo see it. Because without disabling the other devices you get these messages <BR>when you boot: <P>Dec 1 20:21:04 synth /kernel: ppc: parallel port found at 0x378 <BR>Dec 1 20:21:04 synth /kernel: ppc0 at 0x378 irq 7 on isa <BR>Dec 1 20:21:04 synth /kernel: ppc0: SMC <BR>Dec 1 20:21:04 synth /kernel: FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode <BR>Dec 1 20:21:04 synth /kernel: nlpt0: <generic printer> on ppbus 0 <BR>Dec 1 20:21:04 synth /kernel: nlpt0: Interrupt-driven port <BR>Dec 1 20:21:04 synth /kernel: ppi0: <generic parallel i/o> on ppbus 0 <BR>Dec 1 20:21:04 synth /kernel: lppps0: <Pulse per second Timing Interface> on ppbus 0 <BR>Dec 1 20:21:04 synth /kernel: plip0: <PLIP network interface> on ppbus 0 <P>It doesn't even say that the vpo driver is loading and when you try to mount the scsi device (sd0) it tells you that the Device is not configured. The ppbus does not detected the zip drive or If it does detect it, it doesn't configure any devices nodes for it. When I remove the other 4 devices and leave just the controllers and no devices for ppbus the boot messages are as follows: <P>Dec 1 20:29:34 synth /kernel: ppc: parallel port found at 0x378 <BR>Dec 1 20:29:34 synth /kernel: ppc0 at 0x378 irq 7 on isa <BR>Dec 1 20:29:34 synth /kernel: ppc0: SMC <BR>Dec 1 20:29:34 synth /kernel: FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode <BR>Dec 1 20:29:34 synth /kernel: vpo0: <Iomega VPIO Parallel to SCSI interface> on ppbus 0 <BR>Dec 1 20:29:34 synth /kernel: vpo0: EPP 1.9 mode <P>Wow, its finally being detected, gee if the ppbus is suppose to detected the Zip drive with all the other <BR>devices configured, than why doesn't it want to work. Either give me a logical reason why its not <BR>working in my case or check it out for yourself. Do you even have a parallel zip drive? <P>One other thing: People come to these mailing lists to get help, not a attitude when we do something wrong. <P>---------------------------------------------------------------- <BR>Scott Honey <BR>CEO of Symmetric Solutions, Inc <BR>MCSE and Computer Programmer <BR><A HREF="mailto:shoney@symmetricsolutions.com">shoney@symmetricsolutions.com</A> <BR><A HREF="http://www.symmetricsolutions.com">http://www.symmetricsolutions.com</A>; <BR>---------------------------------------------------------------- </HTML> --------------E5574D95B003BF1628879FC3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3664D3B1.775483A8>