Re: Sarge Upgrade Brole Everything Except Terminal
----- Original Message -----
From: "Kent West" <westk@acu.edu>
To: "Leonard Chatagnier" <lenc@ruralcomm.com>
Cc: <debian-user@lists.debian.org>
Sent: Tuesday, December 21, 2004 3:59 PM
Subject: Re: Sarge Upgrade Brole Everything Except Terminal
> Leonard Chatagnier wrote:
>
> >Well, no one responded to my posting on how to get apt-get to upgrage to
> >Sarge so took matters in my own hands and installed the virtual
kernel-image
> >2.6.8-10-i686. Even so, lilo wouldn't boot it up until I ran MKINITRD
and
> >that didn't run without error. The setup didn't mention this. Is it
> >required?
> >However, my real problem is that I can only access the terminals. My
modem,
> >mouse are not recognized. Can't dial out to finish upgrade. X window
> >reports modules pex5, xie do not exist, yet the modules were installed,
then
> >uninstalled. /dev/psaux reported as nonexistant or not found. Ran
> >dpkg --configure on gdm, XFree86 which ended in error. The upgrade
> >reconfigured some things I told it use current configuration(buggy?) or
is
> >this because I have a lot of upgrading to do before sarge works right.
The
> >final error on the X window error messages was: Fatal ????? error failed
to
> >initialize core devices.
> >I'm stumped and need some help to resolve this, needing the modem first
to
> >continue with the upgrading. Please help.
> >Please copy my email address lenc@ruralcomm.com as I'm not currently
> >subscribed.
> >Many thanks.
> >Leonard
> >
> >PS-I read the postings from Dec 15-18 period and picked up some info on
> >upgrading to sarge but didn't work for me. So I searched the Deb site
for
> >the kernel-image and installed.
> >
> >
> I'm just coming into this, but it sounds like you've tried upgrading
> both your system to Sarge, and your system to a new kernel. This warning
> is a little late, but next time you might want to take these two steps
> separately.
>
I don't understand this two step thing. Please explain, maybe in a separate
reply
so not to clutter this posting any more than necessary.
> I'm not sure what you mean by "virtual kernel-image". When I do an
> "apt-cache search kernel-image-2.6.8", with my sources.list pointing at
> unstable, I see no version -10; -9 is the highest I've seen. This
> indicates to me that you're getting your kernel image from some
> non-Debian source; in such a situation, breakage is not surprising to
> me. (Of course, I might be misunderstanding something here.)
>
I'll explain. It's all debian, but not via apt-get as I've used it until no
more
upgrades would list. The virtual package was found searching/browsing
the Debian site. The URL and package name are:
http://packages.debian.org/testing/base/kernel-image-2.6.8-1-686
Package: kernel-image-2.6.8-1-686 (2.6.8-10)
Linux kernel image for version 2.6.8 on PPro/Celeron/PII/PIII/PIV
> I don't believe that you should have needed to run "mkinitrd" unless
> you've compiled your own kernel; at least I've never had to use this
> utility when I install a standard kernel image.
>
I didn't compile. I've read plenty manuals since last post and saw no
reference
to it. I came across it in my searches and it seemed aprapopo so I used it
with the -r
option. It never completed without error. But, when I rebooted after using
it,
the new kernel loaded for the first time after many failed attempts.
> What do you get when you run "uname -a"? It sounds like you've got a
> broken kernel, and a broken/unfinished apt-upgrade. I'd try fixing the
> kernel first, then worry about fixing the upgrade. Can you boot into
> your old kernel?
>
uname -r gives Linux debian 2.6.8-1-686 #1 etc. It does appear to me that
some modules are loaded and unloaded. There are some messages that appear
on the bootup screen that scroll by to fast to read and dmesg doesn't show
them.
I wish I knew what log file contained them so I could see what the problem
it, but
using locate to veiw log files hasn't picked it up yet. Everything works
fine on the old
kernel boot.
> If your modem is a real modem, you can probably recover; if it's a
> win-modem, that requires some driver, you may be looking at a world of
> hurt, at least until you've got a properly working kernel. If your modem
> is real, you should be able to set up a connection either with pppconfig
> or with wvdial; once you have a working connection, you can finish your
> upgrade.
>
I have a win modem Diamond MM SupraMax 56i Voice PCI modem and the drivers
are installed and the modem worked under Woody-bf2.4 and still does. But be
forewarned,
I will not use apt-get again until I get some help on why it hasn't already
worked for me after
many updates, upgrages and dist-upgrades using the "testing" configuration
in my sources.list.
I'm getting tired of spinning my wheels gettin nowhere using apt-get and
I've read the manual(s).
I'll be happy to send you my source.list for examination. I believe you
were the one who helped
me in previous postings(Mewbie Having Much Trouble Getting Deb 2.4.18-bf2.4
To Work) on what's required after the mirror listing.
FLASH: New info. I've discovered that my /var partition is full again and
probably prevented some
required files from downloading when I ran dpkg -i on the kernel-image.
I've made a symbolic link for
the apt-get cache in past to work around this. The install must have filled
it up again so I need to create
some more links to get a work around. I wish I could repartition and
correct this problem but I don't want
to have to reinstall everything again starting with Woody. I have plenty
room on the hard drive. Is this the
root of the problem?
Len Chatagnier
> --
> Kent West
> westk@acu.edu
>
>
Reply to: