In my message of 18/5 with Subject of "SUSE 9.1 - BAH!" I mentioned that I was having big problems with getting Suse 9.1 to co-operate with my modem/modems (either internal or external - but as I have replaced my internals with externals my comments below only refer to external modems). Since that message of 18/5 I've been doing some testing and have found this (summarised): (a) during the installation of 9.1, at the point where the modem is first configured, is then tested for connectivity with the ISP and then the YOU update is allowed to be done - at this point the modem works perfectly. I get a consistent thruput of 4.4 - 5.9 Kb/s (apart from the occasional drop, of course). However, once the REST of the Suse installation is completed, the modem almost stops working with thruput between 0 and 800+ b/s (not Kb/s but b/s) coupled with periods of total inactivity lasting minutes. My testing has shown that it is NOT the YOU update that causes the modem problem but the completion of the installation- meaning that something gets installed that causes the problem. Configuring the modem during the installation, allowing it to dial the ISP - but not letting YOU to update - and then completing the installation does not solve the modem problem; (b) doing a full install of anything OTHER than KDE-related applications does NOT cause problems with the modem. If, for example, one installs the GNOME Desktop and not KDE then the modem works perfectly after the full installation. In one test I only installed the "Minimum graphical system (without KDE)" - and got the FVWM 'desktop' - and things worked fine but then I added GAMES (which are KDE) to this system. Immediately the modem stopped working correctly; (c) C Hamel and I have been corresponding privately and he mentioned earlier tonight that he found a "funny" about the KDE application "k3b". As a test I re-installed Suse 9.1 with KDE Desktop, Multimedia, Games, plus a couple of other things I normally insall, BUT I deliberately omitted installing k3b. After the full installation the modem was behaving almost normally with thruput again back to 4.4 - 5.9 Kb/s but with quite a number of slowdowns and stops. This degradation in performance could have been caused by the fact that in our part of the world at that time the Net is used pretty heavily. I will be retesting this during the day time (later today) to see if the performance is still below par. In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b. I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf? (I got my Suse 9.1 on 13 May but haven't been able to use the darn thing because of the problem with the modem - and I'm getting p***** off :-(.) Cheers. -- I am not young enough to know everything.
Hi, On Monday 31 May 2004 17:40, Basil Chupin wrote: [...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious (I guess you realised this) - on the other hand it appears you did take a systematic approach.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
I have forwarded it to one of our modem guys. Greetings from Bremen hartmut
On Monday 31 May 2004 10:51, Hartmut Meyer wrote:
Hi,
On Monday 31 May 2004 17:40, Basil Chupin wrote:
[...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious (I guess you realised this) - on the other hand it appears you did take a systematic approach.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
I have forwarded it to one of our modem guys.
Greetings from Bremen hartmut I wish to point out that the modem problem runs across versions. I am currently using v9 (FTP installed), and was using 9.1 for a short time. This was something not specifically mentioned in Basil's post, succinct though it was. :-) -- ...CH SuSE 9 Works Linux user# 313696 Linux box# 199365
C Hamel wrote:
On Monday 31 May 2004 10:51, Hartmut Meyer wrote:
Hi,
On Monday 31 May 2004 17:40, Basil Chupin wrote:
[...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious (I guess you realised this) - on the other hand it appears you did take a systematic approach.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
I have forwarded it to one of our modem guys.
Greetings from Bremen hartmut
I wish to point out that the modem problem runs across versions. I am currently using v9 (FTP installed), and was using 9.1 for a short time. This was something not specifically mentioned in Basil's post, succinct though it was. :-)
WHOA there, CH! :-) The modem problem for me has only come up in Suse 9.1 (Pro, BTW). I have had absolutely no problems with either internal (Conecant chipset, both HCF and SHF) or external modems in versions of Suse prior to v9.1. It is only with 9.1 that my problems began. (Correctly me if I'm wrong but I thought you said that you are now firing on all 5 1/2 cylinders using version 9.0 but that it was 9.1 that is causing you much grief? Did I misunderstand you?) Cheers. -- I am not young enough to know everything.
On Monday 31 May 2004 12:02, Basil Chupin wrote:
C Hamel wrote:
On Monday 31 May 2004 10:51, Hartmut Meyer wrote:
Hi,
On Monday 31 May 2004 17:40, Basil Chupin wrote:
[...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious (I guess you realised this) - on the other hand it appears you did take a systematic approach.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
I have forwarded it to one of our modem guys.
Greetings from Bremen hartmut
I wish to point out that the modem problem runs across versions. I am currently using v9 (FTP installed), and was using 9.1 for a short time. This was something not specifically mentioned in Basil's post, succinct though it was. :-)
WHOA there, CH! :-)
The modem problem for me has only come up in Suse 9.1 (Pro, BTW). I have had absolutely no problems with either internal (Conecant chipset, both HCF and SHF) or external modems in versions of Suse prior to v9.1. It is only with 9.1 that my problems began.
(Correctly me if I'm wrong but I thought you said that you are now firing on all 5 1/2 cylinders using version 9.0 but that it was 9.1 that is causing you much grief? Did I misunderstand you?)
Cheers.
-- I am not young enough to know everything. The problems are on both platforms, but the difference is that 9.1 completely breaks. SuSE 9 allows one to dial in, but won't stay connected for more than two or three minutes. The k3b problem I pointed to is in v9, and you also experienced it in v9.1. -- ...CH SuSE 9 Works Linux user# 313696 Linux box# 199365
Hartmut Meyer wrote:
Hi,
On Monday 31 May 2004 17:40, Basil Chupin wrote:
[...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious (I guess you realised this) - on the other hand it appears you did take a systematic approach.
Devious is not the word. It's worse. And yes, I've installed and re-installed now about 20 times now using different options. Of course, there is always something one misses or does wrong but I have tried to be as scientific about it as I can. (Years of being a Sysop of Bulletin Board Systems [BBSs] where "I have no problems in connecting to other BBS except yours" or "I can stay connected to other BBSs for hours except yours" was the "complaint of the day".)
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
I have forwarded it to one of our modem guys.
Thank you. Greatly appreciated.
Greetings from Bremen hartmut
Cheers. -- I am not young enough to know everything.
On Monday 31 May 2004 17.51, Hartmut Meyer wrote:
Hi,
On Monday 31 May 2004 17:40, Basil Chupin wrote:
[...]
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
To be honst, this sounds devious
I think you mean dubious, and I would agree. In my opinion it is almost certainly a kernel problem. I think it's time for a kernel update for 9.1. The kernels in projects/kotd intended for SLES 9 work infinitely much better than the kernel in 9.1.
On Monday 31 May 2004 11:40 am, Basil Chupin wrote:
In my message of 18/5 with Subject of "SUSE 9.1 - BAH!" I mentioned that I was having big problems with getting Suse 9.1 to co-operate with my modem/modems (either internal or external - but as I have replaced my internals with externals my comments below only refer to external modems).
Since that message of 18/5 I've been doing some testing and have found this (summarised):
(a) during the installation of 9.1, at the point where the modem is first configured, is then tested for connectivity with the ISP and then the YOU update is allowed to be done - at this point the modem works perfectly. I get a consistent thruput of 4.4 - 5.9 Kb/s (apart from the occasional drop, of course).
However, once the REST of the Suse installation is completed, the modem almost stops working with thruput between 0 and 800+ b/s (not Kb/s but b/s) coupled with periods of total inactivity lasting minutes.
My testing has shown that it is NOT the YOU update that causes the modem problem but the completion of the installation- meaning that something gets installed that causes the problem.
Configuring the modem during the installation, allowing it to dial the ISP - but not letting YOU to update - and then completing the installation does not solve the modem problem;
(b) doing a full install of anything OTHER than KDE-related applications does NOT cause problems with the modem.
If, for example, one installs the GNOME Desktop and not KDE then the modem works perfectly after the full installation.
In one test I only installed the "Minimum graphical system (without KDE)" - and got the FVWM 'desktop' - and things worked fine but then I added GAMES (which are KDE) to this system. Immediately the modem stopped working correctly;
(c) C Hamel and I have been corresponding privately and he mentioned earlier tonight that he found a "funny" about the KDE application "k3b".
As a test I re-installed Suse 9.1 with KDE Desktop, Multimedia, Games, plus a couple of other things I normally insall, BUT I deliberately omitted installing k3b.
After the full installation the modem was behaving almost normally with thruput again back to 4.4 - 5.9 Kb/s but with quite a number of slowdowns and stops. This degradation in performance could have been caused by the fact that in our part of the world at that time the Net is used pretty heavily. I will be retesting this during the day time (later today) to see if the performance is still below par.
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
(I got my Suse 9.1 on 13 May but haven't been able to use the darn thing because of the problem with the modem - and I'm getting p***** off :-(.)
I don't recall seeing anything in the above that mentions what you are using for a modem setup (kppp, kinternet, or ??? Not familiar with all of them because I've always used pppd) -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/31/04 12:07 + +----------------------------------------------------------------------------+ "Pray for the success of atheism."
On Monday 31 May 2004 11:08, Bruce Marshall wrote:
On Monday 31 May 2004 11:40 am, Basil Chupin wrote:
In my message of 18/5 with Subject of "SUSE 9.1 - BAH!" I mentioned that I was having big problems with getting Suse 9.1 to co-operate with my modem/modems (either internal or external - but as I have replaced my internals with externals my comments below only refer to external modems).
Since that message of 18/5 I've been doing some testing and have found this (summarised):
(a) during the installation of 9.1, at the point where the modem is first configured, is then tested for connectivity with the ISP and then the YOU update is allowed to be done - at this point the modem works perfectly. I get a consistent thruput of 4.4 - 5.9 Kb/s (apart from the occasional drop, of course).
However, once the REST of the Suse installation is completed, the modem almost stops working with thruput between 0 and 800+ b/s (not Kb/s but b/s) coupled with periods of total inactivity lasting minutes.
My testing has shown that it is NOT the YOU update that causes the modem problem but the completion of the installation- meaning that something gets installed that causes the problem.
Configuring the modem during the installation, allowing it to dial the ISP - but not letting YOU to update - and then completing the installation does not solve the modem problem;
(b) doing a full install of anything OTHER than KDE-related applications does NOT cause problems with the modem.
If, for example, one installs the GNOME Desktop and not KDE then the modem works perfectly after the full installation.
In one test I only installed the "Minimum graphical system (without KDE)" - and got the FVWM 'desktop' - and things worked fine but then I added GAMES (which are KDE) to this system. Immediately the modem stopped working correctly;
(c) C Hamel and I have been corresponding privately and he mentioned earlier tonight that he found a "funny" about the KDE application "k3b".
As a test I re-installed Suse 9.1 with KDE Desktop, Multimedia, Games, plus a couple of other things I normally insall, BUT I deliberately omitted installing k3b.
After the full installation the modem was behaving almost normally with thruput again back to 4.4 - 5.9 Kb/s but with quite a number of slowdowns and stops. This degradation in performance could have been caused by the fact that in our part of the world at that time the Net is used pretty heavily. I will be retesting this during the day time (later today) to see if the performance is still below par.
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
(I got my Suse 9.1 on 13 May but haven't been able to use the darn thing because of the problem with the modem - and I'm getting p***** off :-(.)
I don't recall seeing anything in the above that mentions what you are using for a modem setup (kppp, kinternet, or ??? Not familiar with all of them because I've always used pppd)
-- <FOOTERS TRIMMED> I have used --or attempted to use-- wvdial, kppp & kinternet. No joy using wvdial, limited success using kppp. Not certain what Basil Chupin was using. -- ...CH SuSE 9 Works Linux user# 313696 Linux box# 199365
On Monday 31 May 2004 12:32 pm, C Hamel wrote:
<FOOTERS TRIMMED> I have used --or attempted to use-- wvdial, kppp & kinternet. No joy using wvdial, limited success using kppp. Not certain what Basil Chupin was using.
There have been no problems using pppd on 9.0, and I suspect there won't be in using 9.1 also. Best to be a bit clearer about what you are using before you say "modem problem". -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/31/04 13:30 + +----------------------------------------------------------------------------+ "With clothes the new are best, with friends the old are best."
Bruce Marshall wrote:
On Monday 31 May 2004 11:40 am, Basil Chupin wrote:
In my message of 18/5 with Subject of "SUSE 9.1 - BAH!" I mentioned that I was having big problems with getting Suse 9.1 to co-operate with my modem/modems (either internal or external - but as I have replaced my internals with externals my comments below only refer to external modems).
Since that message of 18/5 I've been doing some testing and have found this (summarised):
(a) during the installation of 9.1, at the point where the modem is first configured, is then tested for connectivity with the ISP and then the YOU update is allowed to be done - at this point the modem works perfectly. I get a consistent thruput of 4.4 - 5.9 Kb/s (apart from the occasional drop, of course).
However, once the REST of the Suse installation is completed, the modem almost stops working with thruput between 0 and 800+ b/s (not Kb/s but b/s) coupled with periods of total inactivity lasting minutes.
My testing has shown that it is NOT the YOU update that causes the modem problem but the completion of the installation- meaning that something gets installed that causes the problem.
Configuring the modem during the installation, allowing it to dial the ISP - but not letting YOU to update - and then completing the installation does not solve the modem problem;
(b) doing a full install of anything OTHER than KDE-related applications does NOT cause problems with the modem.
If, for example, one installs the GNOME Desktop and not KDE then the modem works perfectly after the full installation.
In one test I only installed the "Minimum graphical system (without KDE)" - and got the FVWM 'desktop' - and things worked fine but then I added GAMES (which are KDE) to this system. Immediately the modem stopped working correctly;
(c) C Hamel and I have been corresponding privately and he mentioned earlier tonight that he found a "funny" about the KDE application "k3b".
As a test I re-installed Suse 9.1 with KDE Desktop, Multimedia, Games, plus a couple of other things I normally insall, BUT I deliberately omitted installing k3b.
After the full installation the modem was behaving almost normally with thruput again back to 4.4 - 5.9 Kb/s but with quite a number of slowdowns and stops. This degradation in performance could have been caused by the fact that in our part of the world at that time the Net is used pretty heavily. I will be retesting this during the day time (later today) to see if the performance is still below par.
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
I would pass this info onto to Suse Tech Support but I can't find their address right now. If someone knows it could they please forward this message to them on my behalf?
(I got my Suse 9.1 on 13 May but haven't been able to use the darn thing because of the problem with the modem - and I'm getting p***** off :-(.)
I don't recall seeing anything in the above that mentions what you are using for a modem setup (kppp, kinternet, or ??? Not familiar with all of them because I've always used pppd)
Ah, OK. I use Suse's current default dialer which is kinternet, but when I installed the GNOME desktop it has qinternet and I had to use that. (qinternet is the same as kinternet except for the first letter in the name :-) .) When I talk about an "install" or a "full install" I mean whatever is pre-selected in Suse to be installed as default when one selects, for example, Games or Multimedia or All of KDE and so on. The only additional apps I ever install are gftp, kernel-source, pysol, gnome games, and tvtime but for the purposes of the tests I've been doing none of these were installed. Cheers. -- I am not young enough to know everything.
Basil Chupin wrote: [The first part of my original message pruned] .....
(c) C Hamel and I have been corresponding privately and he mentioned earlier tonight that he found a "funny" about the KDE application "k3b".
As a test I re-installed Suse 9.1 with KDE Desktop, Multimedia, Games, plus a couple of other things I normally insall, BUT I deliberately omitted installing k3b.
After the full installation the modem was behaving almost normally with thruput again back to 4.4 - 5.9 Kb/s but with quite a number of slowdowns and stops. This degradation in performance could have been caused by the fact that in our part of the world at that time the Net is used pretty heavily. I will be retesting this during the day time (later today) to see if the performance is still below par.
In summary, something KDE-related is causing the problem with the modem(s) - and it may be possible that it is k3b.
[rest pruned] OK, I retested the above starting at 1327 hours East-coast-of-Australia time (0527 hours Berlin time) and the results were less than encouraging: the results were 1/3 of the way between DISASTER and WHAT I NORMALLY GET. The thruput was hovering on many occasions at the 1.4 - 2.8 Kb/s mark with the occasional peak of 4.4 Kb/s but also there were many zeros until finally the whole thing ground to a halt for a long time with total inactivity. Bottom line is that while there was a noticeable improvement from the "Can't use the modem under Suse 9.1" scenario the improvement is nothing to hold a parade about. Nevertheless, it does appear that removing k3b *may* have been of benefit <shrugs shoulders>. Cheers. -- I am not young enough to know everything.
participants (5)
-
Anders Johansson -
Basil Chupin -
Bruce Marshall -
C Hamel -
Hartmut Meyer