[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2008-10-24 Thread Jonathan Thomas
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. 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 t

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2008-08-28 Thread Leann Ogasawara
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

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-04-16 Thread zebulous
I have played around a bit, finding that the problem also occurs on my notebook (Dell Latitude D610) using the feisty live cd of 2007-04-15. Might the problem be related to my ELSA Microlink 56k modem? Would it help if I post the notebook's log files? -- Feisty: Serial Modem Hangups in Herd 4

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-04-04 Thread Brian Murray
** Changed in: linux-source-2.6.20 (Ubuntu) Sourcepackagename: None => linux-source-2.6.20 Assignee: Brian Murray => Ubuntu Kernel Team Status: Needs Info => Confirmed -- Feisty: Serial Modem Hangups in Herd 4 and 5 https://bugs.launchpad.net/bugs/89512 You received this bug notifica

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-29 Thread zebulous
The problem persists with the 2.6.20-13-generic kernel. The exact error message (reported by wvdial) is: "The PPP daemon has died: A modem hung up the phone (exit code = 16)" I'd be happy to contribute to a solution (but unfortunately don't know how) as the problem is really annoying. It makes fe

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-25 Thread zebulous
I can confirm this bug for feisty beta. uname -a: Linux aztec 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU7Linux ** Attachment added: "dmesg.log" http://librarian.launchpad.net/6934909/G%3A%5Cdmesg.log -- Feisty: Serial Modem Hangups in Herd 4 and 5 https://launchpad.net/

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-25 Thread zebulous
... and lspci-vvnn.log ** Attachment added: "lspci-vvnn.log" http://librarian.launchpad.net/6934921/G%3A%5Clspci-vvnn.log -- Feisty: Serial Modem Hangups in Herd 4 and 5 https://launchpad.net/bugs/89512 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailm

Re: [Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-14 Thread JimmyME
Brian, I'm trying to remember... It may have been KPPP in Kubuntu Herd 4 that gave this message. Somewhere I was able to watch what the reason for the disconnects were and it was reported as exit status 16 "modem hung up". The symptoms were the same in Kubuntu Herd 4 or Ubuntu Herd 4 or 5 though

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-14 Thread Brian Murray
What reported "Exit Status 16"? Thanks again. -- Feisty: Serial Modem Hangups in Herd 4 and 5 https://launchpad.net/bugs/89512 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-12 Thread JimmyME
Hi Brian, I have Edgy (6.10 AMD64) on my system. I no longer have Feisty loaded due to the inability to use an external serial port modem without being disconnected. I just wanted to tip you off to this as a lot of people still use modems and this could be a harbinger of problems down the road w

[Bug 89512] Re: Feisty: Serial Modem Hangups in Herd 4 and 5

2007-03-05 Thread Brian Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. Please include the following additional information, if you have not already done so (please pay attention to lspci's addi