Re: upgrade problems

Re: upgrade problems

[igueths]

Hi Kenny and all. The command I used to so-called fully 
upgrade the packages I had installed was apt --dselect-
upgrade. It downloaded 82.2 mb of data before dpkg 
proceeded to configure the packages. I will try apt-get -
-fix-broken --show-upgraded --dist-upgrade and see what 
happens next time my box is up. Thanks for all the 
replies (I'll let everyone know if I am successfull, I 
hope I am). 
> Hi.  I don't have any problems using modprobe with Woody.  
> You should probably let dpkg and apt manage your package data base
> instead of trying to do things manually.
> Someone suggested a list of commands to try first in another message try
> running them and see what you get.
> 
>           Kenny
> 
> 
> On Wed, Aug 14, 2002 at 02:01:49PM +0000, igueths@attbi.com wrote:
> > Hi. Ok well at least now I know that people are using 
> > Woody without the problems I have mentioned (I guess 
> > that this is a good sign for the most part). Also, I 
> > noticed that Woody has installed modutils 2.4.15, and 
> > have since not been able to load my modules manually via 
> > modprobe (don't like modules.conf too much). Can 
> > modprobe still be run manually to load modules? Or is it 
> > absolutely necessary that I create files for my various 
> > devices via /etc/modutils? I personally don't really 
> > like this method due to the fact that I have always been 
> > able to script-load my modules and I prefer it that way. 
> > I am beginning to think that I for some reason did not 
> > do a full upgrade. Isn't the package index located 
> > somewhere in /var/state/apt? Bc I was going to remove 
> > the current index and rebuild it possibly based on Cd 
> > images. And thanks for all the replies, they have been 
> > very helpfull. 
> > > Hi.  I haven't had any of the problems you are having with upgrading to 
> Woody.
> > > Everything is working fine.
> > > 
> > >           Kenny
> > > 	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> > > > Hi all. I upgraded to Woody about three days ago, and 
> > > > have since been experiencing many problems. In my 
> > > > opinion, the thing's not even close to being ready for 
> > > > stable distribution (unlike potato). Is anyone currently 
> > > > experiencing problems with modutils, where modprobe 
> > > > says "invalid line 81 in modules.conf?" Considering the 
> > > > fact that nothing has been changed in modules.conf for a 
> > > > considerably long time, because I have always been 
> > > > loading my modules manually via scripts. Also has anyone 
> > > > experienced a status 10 in fetchmail because connection 
> > > > to localhost failed? The most probable cause for this is 
> > > > an early termination by exim (This was in my syslog 
> > > > output). Another thing that has been happening to me is 
> > > > that whenever I download a file in Lynx, and go back to 
> > > > the previous page, Dectalk seases responding to 
> > > > keystrokes. This means that possibly setserial is 
> > > > attempting to change port configuration and preventing 
> > > > data from being passed to the serial device (the Dectalk 
> > > > express). Also at boot time, when I am trying to review 
> > > > the screen with the 5 and 6 keys on the numpad, they 
> > > > don't work when the hd is being probed for example. They 
> > > > only work starting at the login prompt. To fix this 
> > > > problem, I am going to get the keymap that I was using 
> > > > in potato and revert back to it. In terms of the 
> > > > problems with the packages, I am going to replace the 
> > > > Woody version with the potato version of setserial, and 
> > > > possibly getting the latest version of Exim. Or if that 
> > > > doesn't work, I'm going to use the Potato version. And 
> > > > in terms of modutils, its going to have to get scrapped 
> > > > for the earlier version as well. So far, I know of one 
> > > > person who has or is experiencing the problems mentioned 
> > > > above. Is there anyone else? I am considering submitting 
> > > > a series of bug reports when this whole thing gets 
> > > > resolved (if nobody else has done so already). Thanks in 
> > > > advance for any input!
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: upgrade problems

[Cheryl Homiak]

I never use dselect if I can help it; dselect drives me crazy!

Cheryl

Re: upgrade problems

[Steve Holmes]

My problems came up before I could have run these package managers
with any good results at all! I had no network functionality because
the net modules wouldn't load; nor any other modules from what I could
tell.  I've about concluded the only to get a compatable kernel with
debian and its modules is to compile the kernel on an existing debian
machine.  Think that might be the case? Even when I used debian's
kernel config file as a base I ran into the module unresolved symbol problems.

On Wed, Aug 14, 2002 at 01:42:32PM -0500, Kenny Hitt wrote:
> Hi.  I don't have any problems using modprobe with Woody.  
> You should probably let dpkg and apt manage your package data base
> instead of trying to do things manually.
> Someone suggested a list of commands to try first in another message try
> running them and see what you get.
> 
>           Kenny
> 
> 
> On Wed, Aug 14, 2002 at 02:01:49PM +0000, igueths@attbi.com wrote:
> > Hi. Ok well at least now I know that people are using 
> > Woody without the problems I have mentioned (I guess 
> > that this is a good sign for the most part). Also, I 
> > noticed that Woody has installed modutils 2.4.15, and 
> > have since not been able to load my modules manually via 
> > modprobe (don't like modules.conf too much). Can 
> > modprobe still be run manually to load modules? Or is it 
> > absolutely necessary that I create files for my various 
> > devices via /etc/modutils? I personally don't really 
> > like this method due to the fact that I have always been 
> > able to script-load my modules and I prefer it that way. 
> > I am beginning to think that I for some reason did not 
> > do a full upgrade. Isn't the package index located 
> > somewhere in /var/state/apt? Bc I was going to remove 
> > the current index and rebuild it possibly based on Cd 
> > images. And thanks for all the replies, they have been 
> > very helpfull. 
> > > Hi.  I haven't had any of the problems you are having with upgrading to Woody.
> > > Everything is working fine.
> > > 
> > >           Kenny
> > > 	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> > > > Hi all. I upgraded to Woody about three days ago, and 
> > > > have since been experiencing many problems. In my 
> > > > opinion, the thing's not even close to being ready for 
> > > > stable distribution (unlike potato). Is anyone currently 
> > > > experiencing problems with modutils, where modprobe 
> > > > says "invalid line 81 in modules.conf?" Considering the 
> > > > fact that nothing has been changed in modules.conf for a 
> > > > considerably long time, because I have always been 
> > > > loading my modules manually via scripts. Also has anyone 
> > > > experienced a status 10 in fetchmail because connection 
> > > > to localhost failed? The most probable cause for this is 
> > > > an early termination by exim (This was in my syslog 
> > > > output). Another thing that has been happening to me is 
> > > > that whenever I download a file in Lynx, and go back to 
> > > > the previous page, Dectalk seases responding to 
> > > > keystrokes. This means that possibly setserial is 
> > > > attempting to change port configuration and preventing 
> > > > data from being passed to the serial device (the Dectalk 
> > > > express). Also at boot time, when I am trying to review 
> > > > the screen with the 5 and 6 keys on the numpad, they 
> > > > don't work when the hd is being probed for example. They 
> > > > only work starting at the login prompt. To fix this 
> > > > problem, I am going to get the keymap that I was using 
> > > > in potato and revert back to it. In terms of the 
> > > > problems with the packages, I am going to replace the 
> > > > Woody version with the potato version of setserial, and 
> > > > possibly getting the latest version of Exim. Or if that 
> > > > doesn't work, I'm going to use the Potato version. And 
> > > > in terms of modutils, its going to have to get scrapped 
> > > > for the earlier version as well. So far, I know of one 
> > > > person who has or is experiencing the problems mentioned 
> > > > above. Is there anyone else? I am considering submitting 
> > > > a series of bug reports when this whole thing gets 
> > > > resolved (if nobody else has done so already). Thanks in 
> > > > advance for any input!
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: upgrade problems

[Kenny Hitt]

Hi.  I don't have any problems using modprobe with Woody.  
You should probably let dpkg and apt manage your package data base
instead of trying to do things manually.
Someone suggested a list of commands to try first in another message try
running them and see what you get.

          Kenny


On Wed, Aug 14, 2002 at 02:01:49PM +0000, igueths@attbi.com wrote:
> Hi. Ok well at least now I know that people are using 
> Woody without the problems I have mentioned (I guess 
> that this is a good sign for the most part). Also, I 
> noticed that Woody has installed modutils 2.4.15, and 
> have since not been able to load my modules manually via 
> modprobe (don't like modules.conf too much). Can 
> modprobe still be run manually to load modules? Or is it 
> absolutely necessary that I create files for my various 
> devices via /etc/modutils? I personally don't really 
> like this method due to the fact that I have always been 
> able to script-load my modules and I prefer it that way. 
> I am beginning to think that I for some reason did not 
> do a full upgrade. Isn't the package index located 
> somewhere in /var/state/apt? Bc I was going to remove 
> the current index and rebuild it possibly based on Cd 
> images. And thanks for all the replies, they have been 
> very helpfull. 
> > Hi.  I haven't had any of the problems you are having with upgrading to Woody.
> > Everything is working fine.
> > 
> >           Kenny
> > 	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> > > Hi all. I upgraded to Woody about three days ago, and 
> > > have since been experiencing many problems. In my 
> > > opinion, the thing's not even close to being ready for 
> > > stable distribution (unlike potato). Is anyone currently 
> > > experiencing problems with modutils, where modprobe 
> > > says "invalid line 81 in modules.conf?" Considering the 
> > > fact that nothing has been changed in modules.conf for a 
> > > considerably long time, because I have always been 
> > > loading my modules manually via scripts. Also has anyone 
> > > experienced a status 10 in fetchmail because connection 
> > > to localhost failed? The most probable cause for this is 
> > > an early termination by exim (This was in my syslog 
> > > output). Another thing that has been happening to me is 
> > > that whenever I download a file in Lynx, and go back to 
> > > the previous page, Dectalk seases responding to 
> > > keystrokes. This means that possibly setserial is 
> > > attempting to change port configuration and preventing 
> > > data from being passed to the serial device (the Dectalk 
> > > express). Also at boot time, when I am trying to review 
> > > the screen with the 5 and 6 keys on the numpad, they 
> > > don't work when the hd is being probed for example. They 
> > > only work starting at the login prompt. To fix this 
> > > problem, I am going to get the keymap that I was using 
> > > in potato and revert back to it. In terms of the 
> > > problems with the packages, I am going to replace the 
> > > Woody version with the potato version of setserial, and 
> > > possibly getting the latest version of Exim. Or if that 
> > > doesn't work, I'm going to use the Potato version. And 
> > > in terms of modutils, its going to have to get scrapped 
> > > for the earlier version as well. So far, I know of one 
> > > person who has or is experiencing the problems mentioned 
> > > above. Is there anyone else? I am considering submitting 
> > > a series of bug reports when this whole thing gets 
> > > resolved (if nobody else has done so already). Thanks in 
> > > advance for any input!
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: upgrade problems

[Steve Holmes]

A couple weeks ago, I ran into all kinds of problems with modules and
unresolved symbols and such.  This happened with every possible
comvination of speakup-enabled bootdisks and self-compiled kernels
module loads from Deb 3.0 CD's both 2.2 and 2.4.18.  I got through the
basic install but none of my modules would load so I had no network
access.  Since I could never resolve the unresolved symbols at
modprobe time, I gave up on Debian and put slackware 8.1 and had
things up and running within a couple hours.  Of course I have
experience with slackware previous versions so that was probably a
good help.  But I really wanted to give a good hard look at debian due
to its package selections and the upgrade facilities it has to offer.

On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> Hi all. I upgraded to Woody about three days ago, and 
> have since been experiencing many problems. In my 
> opinion, the thing's not even close to being ready for 
> stable distribution (unlike potato). Is anyone currently 
> experiencing problems with modutils, where modprobe 
> says "invalid line 81 in modules.conf?" Considering the 
> fact that nothing has been changed in modules.conf for a 
> considerably long time, because I have always been 
> loading my modules manually via scripts. Also has anyone 
> experienced a status 10 in fetchmail because connection 
> to localhost failed? The most probable cause for this is 
> an early termination by exim (This was in my syslog 
> output). Another thing that has been happening to me is 
> that whenever I download a file in Lynx, and go back to 
> the previous page, Dectalk seases responding to 
> keystrokes. This means that possibly setserial is 
> attempting to change port configuration and preventing 
> data from being passed to the serial device (the Dectalk 
> express). Also at boot time, when I am trying to review 
> the screen with the 5 and 6 keys on the numpad, they 
> don't work when the hd is being probed for example. They 
> only work starting at the login prompt. To fix this 
> problem, I am going to get the keymap that I was using 
> in potato and revert back to it. In terms of the 
> problems with the packages, I am going to replace the 
> Woody version with the potato version of setserial, and 
> possibly getting the latest version of Exim. Or if that 
> doesn't work, I'm going to use the Potato version. And 
> in terms of modutils, its going to have to get scrapped 
> for the earlier version as well. So far, I know of one 
> person who has or is experiencing the problems mentioned 
> above. Is there anyone else? I am considering submitting 
> a series of bug reports when this whole thing gets 
> resolved (if nobody else has done so already). Thanks in 
> advance for any input!
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: upgrade problems

[igueths]

Hi. Ok well at least now I know that people are using 
Woody without the problems I have mentioned (I guess 
that this is a good sign for the most part). Also, I 
noticed that Woody has installed modutils 2.4.15, and 
have since not been able to load my modules manually via 
modprobe (don't like modules.conf too much). Can 
modprobe still be run manually to load modules? Or is it 
absolutely necessary that I create files for my various 
devices via /etc/modutils? I personally don't really 
like this method due to the fact that I have always been 
able to script-load my modules and I prefer it that way. 
I am beginning to think that I for some reason did not 
do a full upgrade. Isn't the package index located 
somewhere in /var/state/apt? Bc I was going to remove 
the current index and rebuild it possibly based on Cd 
images. And thanks for all the replies, they have been 
very helpfull. 
> Hi.  I haven't had any of the problems you are having with upgrading to Woody.
> Everything is working fine.
> 
>           Kenny
> 	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> > Hi all. I upgraded to Woody about three days ago, and 
> > have since been experiencing many problems. In my 
> > opinion, the thing's not even close to being ready for 
> > stable distribution (unlike potato). Is anyone currently 
> > experiencing problems with modutils, where modprobe 
> > says "invalid line 81 in modules.conf?" Considering the 
> > fact that nothing has been changed in modules.conf for a 
> > considerably long time, because I have always been 
> > loading my modules manually via scripts. Also has anyone 
> > experienced a status 10 in fetchmail because connection 
> > to localhost failed? The most probable cause for this is 
> > an early termination by exim (This was in my syslog 
> > output). Another thing that has been happening to me is 
> > that whenever I download a file in Lynx, and go back to 
> > the previous page, Dectalk seases responding to 
> > keystrokes. This means that possibly setserial is 
> > attempting to change port configuration and preventing 
> > data from being passed to the serial device (the Dectalk 
> > express). Also at boot time, when I am trying to review 
> > the screen with the 5 and 6 keys on the numpad, they 
> > don't work when the hd is being probed for example. They 
> > only work starting at the login prompt. To fix this 
> > problem, I am going to get the keymap that I was using 
> > in potato and revert back to it. In terms of the 
> > problems with the packages, I am going to replace the 
> > Woody version with the potato version of setserial, and 
> > possibly getting the latest version of Exim. Or if that 
> > doesn't work, I'm going to use the Potato version. And 
> > in terms of modutils, its going to have to get scrapped 
> > for the earlier version as well. So far, I know of one 
> > person who has or is experiencing the problems mentioned 
> > above. Is there anyone else? I am considering submitting 
> > a series of bug reports when this whole thing gets 
> > resolved (if nobody else has done so already). Thanks in 
> > advance for any input!
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: upgrade problems

[Scott Howell]

Been using Woody for a long time now and have not experienced any of
those problems. Got others, but probably partly my fault along the way.
Just haven't sat down to fix them all, but this is mainly X windows
issues and X is for my wife that is.

In any case I should say that I started with Woody or as soon as I
installed Potato I immediately upgraded so perhaps there's something in
the upgrade path that created some of your issues.

Interesting though and good luck.

Re: upgrade problems

[Cheryl Homiak]

Hi.
I ran woody for months and months even before it became the stable distribution
and had none of these problems. so while i'm not sure what the problem is, I
don't think your problem is woody per se.
You might try running apt-get --fix-broken --show-upgraded dist-upgrade to make
sure you actually did a complete upgrade; also check the contents of your
/etc/apt/sources.list to make sure this is accurate.
beyond that, all I can tell you is that I am now actually running the new
testing version--I think they are calling it sarge--and still not experiencing
any of the problems you list. In fact, I even ran unstable for a while before
woody was officially released without these problems.
It seems logical when you
upgrade and have
problems to blame the new version, but the most obvious answer isn't always the
right one or at least it isn't necessarily the whole explanation.
Hope you find out what is going on there; i know it can be very frustrating!

Cheryl

Re: upgrade problems

[Kenny Hitt]

Hi.  I haven't had any of the problems you are having with upgrading to Woody.
Everything is working fine.

          Kenny
	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> Hi all. I upgraded to Woody about three days ago, and 
> have since been experiencing many problems. In my 
> opinion, the thing's not even close to being ready for 
> stable distribution (unlike potato). Is anyone currently 
> experiencing problems with modutils, where modprobe 
> says "invalid line 81 in modules.conf?" Considering the 
> fact that nothing has been changed in modules.conf for a 
> considerably long time, because I have always been 
> loading my modules manually via scripts. Also has anyone 
> experienced a status 10 in fetchmail because connection 
> to localhost failed? The most probable cause for this is 
> an early termination by exim (This was in my syslog 
> output). Another thing that has been happening to me is 
> that whenever I download a file in Lynx, and go back to 
> the previous page, Dectalk seases responding to 
> keystrokes. This means that possibly setserial is 
> attempting to change port configuration and preventing 
> data from being passed to the serial device (the Dectalk 
> express). Also at boot time, when I am trying to review 
> the screen with the 5 and 6 keys on the numpad, they 
> don't work when the hd is being probed for example. They 
> only work starting at the login prompt. To fix this 
> problem, I am going to get the keymap that I was using 
> in potato and revert back to it. In terms of the 
> problems with the packages, I am going to replace the 
> Woody version with the potato version of setserial, and 
> possibly getting the latest version of Exim. Or if that 
> doesn't work, I'm going to use the Potato version. And 
> in terms of modutils, its going to have to get scrapped 
> for the earlier version as well. So far, I know of one 
> person who has or is experiencing the problems mentioned 
> above. Is there anyone else? I am considering submitting 
> a series of bug reports when this whole thing gets 
> resolved (if nobody else has done so already). Thanks in 
> advance for any input!
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

upgrade problems

[igueths]

Hi all. I upgraded to Woody about three days ago, and 
have since been experiencing many problems. In my 
opinion, the thing's not even close to being ready for 
stable distribution (unlike potato). Is anyone currently 
experiencing problems with modutils, where modprobe 
says "invalid line 81 in modules.conf?" Considering the 
fact that nothing has been changed in modules.conf for a 
considerably long time, because I have always been 
loading my modules manually via scripts. Also has anyone 
experienced a status 10 in fetchmail because connection 
to localhost failed? The most probable cause for this is 
an early termination by exim (This was in my syslog 
output). Another thing that has been happening to me is 
that whenever I download a file in Lynx, and go back to 
the previous page, Dectalk seases responding to 
keystrokes. This means that possibly setserial is 
attempting to change port configuration and preventing 
data from being passed to the serial device (the Dectalk 
express). Also at boot time, when I am trying to review 
the screen with the 5 and 6 keys on the numpad, they 
don't work when the hd is being probed for example. They 
only work starting at the login prompt. To fix this 
problem, I am going to get the keymap that I was using 
in potato and revert back to it. In terms of the 
problems with the packages, I am going to replace the 
Woody version with the potato version of setserial, and 
possibly getting the latest version of Exim. Or if that 
doesn't work, I'm going to use the Potato version. And 
in terms of modutils, its going to have to get scrapped 
for the earlier version as well. So far, I know of one 
person who has or is experiencing the problems mentioned 
above. Is there anyone else? I am considering submitting 
a series of bug reports when this whole thing gets 
resolved (if nobody else has done so already). Thanks in 
advance for any input!