Re: serial troubles
I remember some PCI errors showing up during boot with older kernels that were eliminated in later kernel versions(2.0.32+ ?), but, of course, I can't tell whether this applies to your situation. yep. upgrading removed (PCI-related) warnings during boot and now XF86Config, e.g., recognizes the diamond s3-virge which it wasn't doing before What exacly does 'can't initialize the modem' mean? the ppp-on-dialer script was unable to pass the 'AT' command to the modem. there was txd/rxd activity but the modem was not receiving the command. I had a file permission problem with the /etc/chatscript/provider script that caused pppd to freeze when it tried to use the chatscript. What does the end of the ppp.log look like? Use plog to see this. the string being passed by the script (which i borrowed from the PPP-HOWTO included a /r -- '/rAT' -- the modem in the 486 had no problem with the return. but, both the gdc and the us robotics (on the pentium) did. i removed the 'r' and... voila. funny. had ruled out the script because it worked and had been tested. duh. thanks, ed--c -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: serial troubles
i suspected the modem too so tried a us robotics (usually have a gdc connected)...both behave the same. seems to be related to warnings at bootup re: PCI ... there is a serial USB controller on IRQ 10 that is one of the PCI devices that isn't recognized (identified by number)... i tried disabling it and manually configuring /etc/rc.boot/0setserial but still get the same behavior. i need info on this PCI bizness. i read the PCI-HowTo but found nothing there of any use the only debian cd i have is 2.0.27 (kernel) think i'll try hamm if i can find a cd...maybe PCI problems have been eliminated best--c On 2 Jul 1998, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Chea Prince [EMAIL PROTECTED] wrote: have included serial support in the kernel and on bootup shows serial devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0 /dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at IRQ 3 4. That's OK; the interrupts are only allocated when the port is actually opened. You see, you can't share interrupts at the same time between devices but 2 devices can use the same interrupt if they are not used at the same time. That's why IRQs are only allocated when used. can dialout fine from minicom but ppp script fails (can't initialize the modem). Smells like a modem problem. Maybe the modem is set to non-echo? Try using the init string from minicom in the ppp script. Mike. -- Miquel van Smoorenburg | Our vision is to speed up time, [EMAIL PROTECTED] | eventually eliminating it. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: serial troubles
Chea Prince wrote: i suspected the modem too so tried a us robotics (usually have a gdc connected)...both behave the same. seems to be related to warnings at bootup re: PCI ... there is a serial USB controller on IRQ 10 that is one of the PCI devices that isn't recognized (identified by number)... i tried disabling it and manually configuring /etc/rc.boot/0setserial but still get the same behavior. i need info on this PCI bizness. i read the PCI-HowTo but found nothing there of any use the only debian cd i have is 2.0.27 (kernel) think i'll try hamm if i can find a cd...maybe PCI problems have been eliminated best--c On 2 Jul 1998, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Chea Prince [EMAIL PROTECTED] wrote: have included serial support in the kernel and on bootup shows serial devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0 /dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at IRQ 3 4. That's OK; the interrupts are only allocated when the port is actually opened. You see, you can't share interrupts at the same time between devices but 2 devices can use the same interrupt if they are not used at the same time. That's why IRQs are only allocated when used. can dialout fine from minicom but ppp script fails (can't initialize the modem). Smells like a modem problem. Maybe the modem is set to non-echo? Try using the init string from minicom in the ppp script. Mike. -- Miquel van Smoorenburg | Our vision is to speed up time, [EMAIL PROTECTED] | eventually eliminating it. I remember some PCI errors showing up during boot with older kernels that were eliminated in later kernel versions(2.0.32+ ?), but, of course, I can't tell whether this applies to your situation. What exacly does 'can't initialize the modem' mean? I had a file permission problem with the /etc/chatscript/provider script that caused pppd to freeze when it tried to use the chatscript. What does the end of the ppp.log look like? Use plog to see this. -- Ed -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
serial troubles
have included serial support in the kernel and on bootup shows serial devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0 /dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at IRQ 3 4. can dialout fine from minicom but ppp script fails (can't initialize the modem). same scripts run fine on a 486 which reports serial devices appropriately on reading /proc/interrupts. system with the problem is a pentium 166mhz; (asus txp4 MB). thanks in advance for any assistance best--c -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: serial troubles
In article [EMAIL PROTECTED], Chea Prince [EMAIL PROTECTED] wrote: have included serial support in the kernel and on bootup shows serial devices being assigned to /dev/cua0 /dev/cua1 and /dev/ttyS0 /dev/ttyS1 but 'cat /proc/interrupts' shows no serial devices at IRQ 3 4. That's OK; the interrupts are only allocated when the port is actually opened. You see, you can't share interrupts at the same time between devices but 2 devices can use the same interrupt if they are not used at the same time. That's why IRQs are only allocated when used. can dialout fine from minicom but ppp script fails (can't initialize the modem). Smells like a modem problem. Maybe the modem is set to non-echo? Try using the init string from minicom in the ppp script. Mike. -- Miquel van Smoorenburg | Our vision is to speed up time, [EMAIL PROTECTED] | eventually eliminating it. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
