-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can scarcely believe what I am about to put down, here, but this is exactly what happened on my SuSE Personal Edition box. I installed 9.1 & hooked up my 3Com ISDN modem, which worked pretty well except for the fact that it would only work on one channel. I used it anyhow, for a few hours w/o problems. I decided to check the updates & installed each, not selecting to remove the files when done. Roughly 18 hours later, the modem was online & I was doing my thing when suddenly there was absolutely no throughput. I was online, yes, the modem light indicating such was lighted. E-mail would not fetch, browser would not fetch. I had a backup ISDN modem & hooked that one up & dialed. It hooked up on both lines, and worked non-stop for roughly 18 hours, then quit ...while I was online, like before. I was listening to a RealPlayer feed it & suddenly stopped. E-mail & browser would not fetch, as before. Since this modem has reset capability I did the factory reset and tried dialing, again. The box wouldn't even talk to the modem ...or if it was, there was no indication. I moved the modem to my XP box & was online in roughly 3.5 seconds, as always. I sent a couple e-mails and then moved the modem back to the SuSE box for one last-ditch effort before pulling the plug on the installation ...and it worked. As I indicated to a couple people privately, I am really damned frustrated and a bit hot about it because I cannot seem to get to the bottom of the problem. SuSE 9 Pro stopped working with the same modems immediately after updates were applied ...unless and until SuSE 9 was reinstalled from scratch and NO updates applied EVER. SuSE 9.1, on the other hand, selectively works or doesn't work ONLY after the updates were applied! ANY help will be gratefully received ...whether the solutionworks, or not. I don't even know where to begin!! Thanks... - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAqtQ81rD/PgIdojIRAv3FAJ9LIG5/mrwnF1t3gt0fAUCVWc6zUACgp0CB tnoTKtklRi6w1koDs+ISeQo= =AqXv -----END PGP SIGNATURE-----
On Wednesday 19 May 2004 03:27, C Hamel wrote:
...whether the solutionworks
~ maybe a CRON job runs /etc/permissions . . . maybe, cron job removes users permission to use modem? . . . have a look at modem permissions? -- best wishes ____________ sent on Linux ____________
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 00:36, pinto wrote:
On Wednesday 19 May 2004 03:27, C Hamel wrote:
...whether the solutionworks
~ maybe a CRON job runs /etc/permissions
. . . maybe, cron job removes users permission to use modem?
. . . have a look at modem permissions?
--
best wishes
____________
sent on Linux
____________ Hadn't thought of that one. Thanks... I'll give that a look!
...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAq5AX1rD/PgIdojIRAizuAJ99QgVJbtY1AlFW+EVgNOuZvIYZjQCfVIoE wvH5UBvfxcmH8gaSakuonEE= =mQeZ -----END PGP SIGNATURE-----
On Tuesday 18 May 2004 11:27 pm, C Hamel wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I can scarcely believe what I am about to put down, here, but this is exactly what happened on my SuSE Personal Edition box.
I installed 9.1 & hooked up my 3Com ISDN modem, which worked pretty well except for the fact that it would only work on one channel. I used it anyhow, for a few hours w/o problems. I decided to check the updates & installed each, not selecting to remove the files when done.
Roughly 18 hours later, the modem was online & I was doing my thing when suddenly there was absolutely no throughput. I was online, yes, the modem light indicating such was lighted. E-mail would not fetch, browser would not fetch.
I had a backup ISDN modem & hooked that one up & dialed. It hooked up on both lines, and worked non-stop for roughly 18 hours, then quit ...while I was online, like before. I was listening to a RealPlayer feed it & suddenly stopped. E-mail & browser would not fetch, as before.
Since this modem has reset capability I did the factory reset and tried dialing, again. The box wouldn't even talk to the modem ...or if it was, there was no indication.
I moved the modem to my XP box & was online in roughly 3.5 seconds, as always. I sent a couple e-mails and then moved the modem back to the SuSE box for one last-ditch effort before pulling the plug on the installation ...and it worked.
As I indicated to a couple people privately, I am really damned frustrated and a bit hot about it because I cannot seem to get to the bottom of the problem. SuSE 9 Pro stopped working with the same modems immediately after updates were applied ...unless and until SuSE 9 was reinstalled from scratch and NO updates applied EVER. SuSE 9.1, on the other hand, selectively works or doesn't work ONLY after the updates were applied!
ANY help will be gratefully received ...whether the solutionworks, or not. I don't even know where to begin!!
Bottom posting which is a pain in the arse..... but the posting police will get you if you don't watch out.... I have been having a similar problem but may have found the problem. I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor. I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them). I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?) At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them. Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks... - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAqtQ81rD/PgIdojIRAv3FAJ9LIG5/mrwnF1t3gt0fAUCVWc6zUACgp0CB tnoTKtklRi6w1koDs+ISeQo= =AqXv -----END PGP SIGNATURE-----
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 07:27 + +----------------------------------------------------------------------------+ "When you open a new bag of cotton balls, are you supposed to throw the top one away?"
Bruce Marshall wrote:
On Tuesday 18 May 2004 11:27 pm, C Hamel wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I can scarcely believe what I am about to put down, here, but this is exactly what happened on my SuSE Personal Edition box.
I installed 9.1 & hooked up my 3Com ISDN modem, which worked pretty well except for the fact that it would only work on one channel. I used it anyhow, for a few hours w/o problems. I decided to check the updates & installed each, not selecting to remove the files when done.
Roughly 18 hours later, the modem was online & I was doing my thing when suddenly there was absolutely no throughput. I was online, yes, the modem light indicating such was lighted. E-mail would not fetch, browser would not fetch.
I had a backup ISDN modem & hooked that one up & dialed. It hooked up on both lines, and worked non-stop for roughly 18 hours, then quit ...while I was online, like before. I was listening to a RealPlayer feed it & suddenly stopped. E-mail & browser would not fetch, as before.
Since this modem has reset capability I did the factory reset and tried dialing, again. The box wouldn't even talk to the modem ...or if it was, there was no indication.
I moved the modem to my XP box & was online in roughly 3.5 seconds, as always. I sent a couple e-mails and then moved the modem back to the SuSE box for one last-ditch effort before pulling the plug on the installation ...and it worked.
As I indicated to a couple people privately, I am really damned frustrated and a bit hot about it because I cannot seem to get to the bottom of the problem. SuSE 9 Pro stopped working with the same modems immediately after updates were applied ...unless and until SuSE 9 was reinstalled from scratch and NO updates applied EVER. SuSE 9.1, on the other hand, selectively works or doesn't work ONLY after the updates were applied!
ANY help will be gratefully received ...whether the solutionworks, or not. I don't even know where to begin!!
Bottom posting which is a pain in the arse..... but the posting police will get you if you don't watch out....
I have been having a similar problem but may have found the problem.
I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor.
I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them).
I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?)
At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them.
Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks for confirming what I have exprienced (very, very close to being the same as you). See my message I sent yesterday with the Subject of SUSE 5.1 - BAH! Cheers. -- I am not young enough to know everything.
On Wednesday 19 May 2004 09:12 am, Basil Chupin wrote:
I have been having a similar problem but may have found the problem.
I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor.
I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them).
I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?)
At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them.
Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks for confirming what I have exprienced (very, very close to being the same as you). See my message I sent yesterday with the Subject of SUSE 5.1 - BAH!
Basil: Can you tell me what kernel you are running (with 9.1) and then check in /boot and see if CONFIG_PREEMPT is set. I have recompiled 2.6.6 with preempt turned off and it seems (after just a few minutes) to have solved my problem with slow modem thruput. It would seem that it could also solve your problem. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 14:17 + +----------------------------------------------------------------------------+ "If God had meant for us to go to rock concerts, he would have given us tickets."
On Wednesday 19 May 2004 09:12 am, Basil Chupin wrote:
I have been having a similar problem but may have found the problem.
I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor.
I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them).
I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?)
At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them.
Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks for confirming what I have exprienced (very, very close to being the same as you). See my message I sent yesterday with the Subject of SUSE 5.1 - BAH!
Basil:
Can you tell me what kernel you are running (with 9.1) and then check in /boot and see if CONFIG_PREEMPT is set.
I have recompiled 2.6.6 with preempt turned off and it seems (after just a few minutes) to have solved my problem with slow modem thruput. It would seem that it could also solve your problem.
-- +-------------------------------------------------------------------------- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 14:17 + +-------------------------------------------------------------------------- --+ "If God had meant for us to go to rock concerts, he would have given us tickets." Since I started the thread... <G> ...I'll respond: The kernel is the default installation kernel for 9.1 Personal. Now, a question: How dows one check
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 13:19, Bruce Marshall wrote: the preemption? Thanks! - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAq6mi1rD/PgIdojIRAmDfAJ0W1XYJA243hwM+2Ug7QFV72NdcXgCfUFa4 WBY7wVlNduYfgtHESzhU7C0= =e/YY -----END PGP SIGNATURE-----
On Wednesday 19 May 2004 20.38, C Hamel wrote:
Now, a question: How dows one check the preemption?
zcat /proc/config.gz|grep PREEMPT (special note in case you feel like giving me a 'useless use of <something>' award: I do know about zgrep, I also know that for some reason it frequently fails on files in /proc)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 13:43, Anders Johansson wrote:
zcat /proc/config.gz|grep PREEMPT Okay... ' CONFIG_PREEMPT is not set' according to that command's output. FWIW&IDC, my thread got hijacked, somehow. <LOL>
...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAq7i51rD/PgIdojIRAvUeAJ9Hd4ZOYCcZlM4ttvW2fXgDWfOySwCgj1kk pPjBKo/f0dB/2F6jLhL7cdQ= =F6sy -----END PGP SIGNATURE-----
On Wednesday 19 May 2004 02:38 pm, C Hamel wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 19 May 2004 13:19, Bruce Marshall wrote:
On Wednesday 19 May 2004 09:12 am, Basil Chupin wrote:
I have been having a similar problem but may have found the problem.
I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor.
I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them).
I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?)
At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them.
Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks for confirming what I have exprienced (very, very close to being the same as you). See my message I sent yesterday with the Subject of SUSE 5.1 - BAH!
Basil:
Can you tell me what kernel you are running (with 9.1) and then check in /boot and see if CONFIG_PREEMPT is set.
I have recompiled 2.6.6 with preempt turned off and it seems (after just a few minutes) to have solved my problem with slow modem thruput. It would seem that it could also solve your problem.
-- +------------------------------------------------------------------------ -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 14:17 + +------------------------------------------------------------------------ -- --+ "If God had meant for us to go to rock concerts, he would have given us tickets."
Since I started the thread... <G> ...I'll respond: The kernel is the default installation kernel for 9.1 Personal. Now, a question: How dows one check the preemption?
Well, since I don't have 9.1 *anything*, I still don't know what kernel *you* have. Do a: uname -r to find out what it is. You should have in /boot, a file named config-2.6.xxxxx--blah that defines the config used for the kernel. Look in this file for CONFIG-PREEMPT. However, removing preemption didn't solve my problem it appears so I am still looking at what the problem might be.
Thanks! - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAq6mi1rD/PgIdojIRAmDfAJ0W1XYJA243hwM+2Ug7QFV72NdcXgCfUFa4 WBY7wVlNduYfgtHESzhU7C0= =e/YY -----END PGP SIGNATURE-----
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 14:55 + +----------------------------------------------------------------------------+ "I live on a one-way dead-end street."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 13:57, Bruce Marshall wrote: <SNIP>
Since I started the thread... <G> ...I'll respond: The kernel is the default installation kernel for 9.1 Personal. Now, a question: How dows one check the preemption?
Well, since I don't have 9.1 *anything*, I still don't know what kernel *you* have.
Do a: uname -r to find out what it is.
You should have in /boot, a file named config-2.6.xxxxx--blah that defines the config used for the kernel. Look in this file for CONFIG-PREEMPT.
However, removing preemption didn't solve my problem it appears so I am still looking at what the problem might be.
Thanks! - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAq6mi1rD/PgIdojIRAmDfAJ0W1XYJA243hwM+2Ug7QFV72NdcXgCfUFa4 WBY7wVlNduYfgtHESzhU7C0= =e/YY -----END PGP SIGNATURE-----
-- +-------------------------------------------------------------------------- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/19/04 14:55 + +-------------------------------------------------------------------------- --+ "I live on a one-way dead-end street." So sorry... it's 2.6.4-54.5-default. :-)
...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAq7lH1rD/PgIdojIRAjKoAJ4w5p1iWIWQCUQrPhYEog38OKM7pgCgnaav Vg8Do+E04yTTJu9Gl8uv2PU= =zmiD -----END PGP SIGNATURE-----
Bruce Marshall wrote:
On Wednesday 19 May 2004 09:12 am, Basil Chupin wrote:
I have been having a similar problem but may have found the problem.
I am running 9.0 but I *was* running with kernel 2.6.6. I also was having thruput problems on a normal 56k dialup modem. Things wouldn't stop completely, but the throughput was almost non-existant... really poor.
I was yelling at my ISP (and fortunately I have a good relationship with them) and they were testing dialup response and not finding any problems... and also said that I was the only one complaining. (and I believe them).
I tried different phone numbers, and a different (but the same type) modem (USR V-everything) but nothing really changed. At one point I dialed into another ISP and things got really good for awhile, but then slowed down again. (sound familiar?)
At that point, I switched back to a 2.4.25 kernel and things have been a lot different since. Pretty good thruput. So I am thinking there are problems in the 2.6.6 kernel somewhere. NOTE: Both of these kernels are stock, vanilla kernels from kernel.org so SuSE has nothing to do with them.
Not sure how to shoot this kind of problem but I think there definitely is a problem.
Thanks for confirming what I have exprienced (very, very close to being the same as you). See my message I sent yesterday with the Subject of SUSE 5.1 - BAH!
Basil:
Can you tell me what kernel you are running (with 9.1) and then check in /boot and see if CONFIG_PREEMPT is set.
I have recompiled 2.6.6 with preempt turned off and it seems (after just a few minutes) to have solved my problem with slow modem thruput. It would seem that it could also solve your problem.
See the repsonse from C Hamel (who is the pot stirrer on this one :-) ). We are both running the stock standard 9.1 kernel (2.6.4-5). Cheers. -- I am not young enough to know everything.
participants (5)
-
Anders Johansson -
Basil Chupin -
Bruce Marshall -
C Hamel -
pinto