Re: Help PLEASE! on proper kernel config file to use serial portswith puc driver
On Fri, Aug 01, 2003 at 01:37:35AM -0400, J. Seth Henry wrote: > Stan, > Could you describe your hardware in a bit more detail. I can't imagine > why your system would hard lock, unless there is something seriously > wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5 > (COM5 and COM6 respectively) Most mainboards only have sio0/COM1 and > sio1/COM2. What is using sio2 and sio3? > > BTW - I would start from a generic kernel configuration if you don't > remember what you did. Then, make the necessary changes to the copy of > GENERIC, and go from there. Then, rebuild the kernel - it probably isn't > necessary, but it will at least return your kernel to something closer > to the baseline. > The card is a generic PCI card, it's labeled "Mercury" on the box, and has a Sun chip on it. I see it's detected as a Dolphin card, and I _assume_ that is correct. The weirdness with it being COM5 and COM6 had to do with weirdness in my kernel conf file. I suspect the problem is that I need to pass certain flags in the kernel conf, but I don't know which ones. The good news is, after having spent a couple of days fighting this, and getting to the point I was locking up the computer with it, it dawned on me that I had started out there. So I went back and found out that I probably had the IO address for the on-board CO<1 chip wrong originally. Now it seems to be working, which will let me deploy the machine! Thanks for your help on this. I still plan on putting the PCI card in another machine and trying to get it to work, but that may take a while to get to. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help PLEASE! on proper kernel config file to use serial portswith puc driver
Stan, Could you describe your hardware in a bit more detail. I can't imagine why your system would hard lock, unless there is something seriously wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5 (COM5 and COM6 respectively) Most mainboards only have sio0/COM1 and sio1/COM2. What is using sio2 and sio3? BTW - I would start from a generic kernel configuration if you don't remember what you did. Then, make the necessary changes to the copy of GENERIC, and go from there. Then, rebuild the kernel - it probably isn't necessary, but it will at least return your kernel to something closer to the baseline. Regards, Seth Henry On Thu, 2003-07-31 at 13:18, stan wrote: > On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote: > > All you need in your kernel config is 'device puc'. You already appear > > to have this in your config, as your system detected the adapter. > > > > Him > > I've made some "progress" on this ;-( > > I have created teh devices in /dev. I now have just the puc line in the > kernel config, and the ports are getting detected like this: > > puc0: port 0xfce0-0xfcff irq 11 at device 6.0 on pci0 > sio4: type 16550A > sio5: type 16550A > > That;s the good nes. The bad news is that when I do "cu -l cuaa4", the > computer locks up! No response to any keyboard input, no response to a ping > etc. I have to power cycle it to get it back :-( > > Sugestions? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help PLEASE! on proper kernel config file to use serial portswith puc driver
All you need in your kernel config is 'device puc'. You already appear to have this in your config, as your system detected the adapter. You will have to "sh MAKEDEV cuaa" (where 0 < n < NUM_PORTS) to get the device nodes in your /dev directory. Alternately, since they have sequential minor numbers, you can make them yourself. 'mknod cuaa0 c 28,128 root:wheel' 'mknod cuaa1 c 28,129 root:wheel' 'mknod cuaa2 c 28,130 root:wheel' 'mknod cuaa3 c 28,131 root:wheel' 'mknod cuaa4 c 28,131 root:wheel' 'mknod cuaa5 c 28,131 root:wheel' You can also do this for the tty nodes as well. I prefer making the nodes myself, but the MAKEDEV script will do the same thing. Good luck, Seth Henry >OK, I've spent all night complaining kernels with no luck. I've read >the man page for puc, I've read the man page for sio, I've looked at >the code for puc, I've searched d Googlee, and STILL I can't get sio >devices assigned to my PCI serial port card. > > It's detected as: > >puc0: port 0xfce0-0xfcff irq 11 at device >6.0 on pci0 >sio4: type 16550A >sio5: type 16550A > > >But I feel certain I don't have the correct syntax in my kernel conf >file for the sio ports I want to assign to this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help PLEASE! on proper kernel config file to use serial portswith puc driver
On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote: > All you need in your kernel config is 'device puc'. You already appear > to have this in your config, as your system detected the adapter. > Him I've made some "progress" on this ;-( I have created teh devices in /dev. I now have just the puc line in the kernel config, and the ports are getting detected like this: puc0: port 0xfce0-0xfcff irq 11 at device 6.0 on pci0 sio4: type 16550A sio5: type 16550A That;s the good nes. The bad news is that when I do "cu -l cuaa4", the computer locks up! No response to any keyboard input, no response to a ping etc. I have to power cycle it to get it back :-( Sugestions? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help PLEASE! on proper kernel config file to use serial portswith puc driver
On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote: > All you need in your kernel config is 'device puc'. You already appear > to have this in your config, as your system detected the adapter. > > You will have to "sh MAKEDEV cuaa" (where 0 < n < NUM_PORTS) to get > the device nodes in your /dev directory. > Thanbks so much for the help on this! I have now made the devise: crw-rw 1 uucp dialer 28, 128 Jul 21 10:50 cuaa0 crw-rw 1 uucp dialer 28, 129 Jul 29 10:59 cuaa1 crw-rw 1 uucp dialer 28, 130 Jul 17 06:22 cuaa2 crw-rw 1 uucp dialer 28, 131 Jul 17 06:22 cuaa3 crw-rw 1 uucp dialer 28, 132 Jul 31 12:17 cuaa4 crw-rw 1 uucp dialer 28, 133 Jul 31 12:17 cuaa5 crw-rw 1 uucp dialer 28, 134 Jul 31 12:17 cuaa6 crw-rw 1 uucp dialer 28, 135 Jul 31 12:17 cuaa7 crw-rw 1 uucp dialer 28, 136 Jul 31 12:16 cuaa8 crw-rw 1 uucp dialer 28, 160 Jul 17 06:22 cuaia0 crw-rw 1 uucp dialer 28, 161 Jul 17 06:22 cuaia1 crw-rw 1 uucp dialer 28, 162 Jul 17 06:22 cuaia2 crw-rw 1 uucp dialer 28, 163 Jul 17 06:22 cuaia3 crw-rw 1 uucp dialer 28, 164 Jul 31 12:17 cuaia4 crw-rw 1 uucp dialer 28, 165 Jul 31 12:17 cuaia5 crw-rw 1 uucp dialer 28, 166 Jul 31 12:17 cuaia6 crw-rw 1 uucp dialer 28, 167 Jul 31 12:17 cuaia7 crw-rw 1 uucp dialer 28, 168 Jul 31 12:16 cuaia8 crw-rw 1 uucp dialer 28, 192 Jul 17 06:22 cuala0 crw-rw 1 uucp dialer 28, 193 Jul 17 06:22 cuala1 crw-rw 1 uucp dialer 28, 194 Jul 17 06:22 cuala2 crw-rw 1 uucp dialer 28, 195 Jul 17 06:22 cuala3 crw-rw 1 uucp dialer 28, 196 Jul 31 12:17 cuala4 crw-rw 1 uucp dialer 28, 197 Jul 31 12:17 cuala5 crw-rw 1 uucp dialer 28, 198 Jul 31 12:17 cuala6 crw-rw 1 uucp dialer 28, 199 Jul 31 12:17 cuala7 crw-rw 1 uucp dialer 28, 200 Jul 31 12:16 cuala8 And here is what I have in my kernel conf file: device puc options COM_MULTIPORT # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device sio2at isa? disable port IO_COM3 irq 11 device sio3at isa? disable port IO_COM4 irq 11 device sio4at isa? disable port IO_COM3 irq 11 device sio5at isa? disable port IO_COM4 irq 11 Which is probably wrong. I must have tried 20 deifferent things since yesterday afternoon :-( And here is the output of dmesg: puc0: port 0xfce0-0xfcff irq 11 at device 6.0 on pci0 sio6: type 16550A sio7: type 16550A fxp0: port 0xfcc0-0xfcdf mem 0xfec0-0xfecf,0xfedfb000-0xfedfbfff irq 10 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:71:41:b7 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 12.0 irq 9 orm0: at iomem 0xc-0xc7fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 So, it looks to me like something is still not right. Am I understnading you to say that I don't need any (nonstandard) sio entries in my kernel config file? If that's the case, I must have a basic misunderstanding (which is certainly possible). I thought the puc driver was a "bridge" driver that allowed the sio driver(s) to be connected to serial ports on PCI based cards. Is this incorect? Again, thnaks VERY much for helping me with this! -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
