external serial modem don't work (but does work on other linuxes)

[javi]

On Ubuntu 6.10:

When going to System -> Administration -> Networking and trying to configure an external modem (not winmodem) it simply don't work at all.

When I try to run "sudo pppconfig" it does not even recognize it.

The modem works perfectly with other Linuxes, and does not require a driver, as it is directly connected to the RS232 port. I've been using this modem for years with Linux without problem. I tryed it tonight with Suse and works perfectly.

There seems to be also more people with this problem, according to this page:

https://help.ubuntu.com/community/DialupModemHowto/HardwareModem

The modem do work well with 6.06, so this seems to be a 6.10 issue.

[Ante Karamatić (ivoks)]

I can confirm this even on dapper. While Debian's kernel (2.6.8-2-686-smp) works ok, on that same system, dapper's kernel (-28-server) doesn't recognize modem.

I'm using Hylafax, but minicom also doesn't work.

[Kyle McMartin (kyle)]

You didn't provide a dmesg. Please attach that and the output of "sudo setserial -a /dev/ttyS0" to this bug.

[Ante Karamatić (ivoks)]

2.6.8:
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
        Baud_base: 115200, close_delay: 500, divisor: 0
        closing_wait: 30000
        Flags: spd_normal skip_test

2.6.15:
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test

dmesg attached

[Carlos Diener / emonkey (emonkey)]

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/

[Ante Karamatić (ivoks)]

On hardy:

# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
 Baud_base: 115200, close_delay: 50, divisor: 0
 closing_wait: 3000
 Flags: spd_normal skip_test

Still doesn't work.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

[Sergio Zanchetta (primes2h)]

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Magnus S (magnuss)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!