Civileme (and everyone),
I would love to know what dmesg says... That CD problem is NOT a common report, and
they have a lot of trouble fixing what they cannot duplicate.
I beg to differ - I had posted the problem here a couple weeks ago, and this was
followed by two other people reporting
Submitted 29-Jun-00 by Bob Puff@NLE:
I was getting a ton of "conf.modules is more recent than ..."
messages. I found someone's suggestion of simply changing the
date/time on the referenced file, and it went away. But why was this
check done? It filled my logs with TONS of these messages.
OH!! My bad - you're the one corresponding with Civilme on UDMA66, yes?
Me thinks you're in good hands, Mike
I am sorry...I should havce changed the subject line...I was responding to
someone with a laptopbut I am getting desperate here...LOL
Jim
Hey Jim,
I'm not an 'expert', but
I am sorry...I should havce changed the subject line...I was responding to
someone with a laptopbut I am getting desperate here...LOL
Jim
Hey Jim,
I'm not an 'expert', but I just read your message and it seems that
you're not real happy. It sounds like somebody dropped the ball as far
My experience with loading Linux on my IBM Thinkpad went ok except for getting
the sound card (YamahaOPL3) to work properly. I tries Slackware7, All RedHat
versions and Mandrake 6.0, 6.5, and 7.0. None of these worked with my sound
card because there was always a conflict and would lock up the
I've reported this to "bugs" but don't expect any response from there...
I successfully installed 7.1 on my desktop with some issues; but none like
trying to install 7.1 on my Tecra500CDT where the install process proceeds quite
nicely through the first CD...
Then... the prompt to change CDs...
Pierre Fortin wrote:
I've reported this to "bugs" but don't expect any response from there...
I successfully installed 7.1 on my desktop with some issues; but none like
trying to install 7.1 on my Tecra500CDT where the install process proceeds quite
nicely through the first CD...
Then...
I was getting ready to re-install 6.1; but I'll give this a try... the gotcha
is that I have to babysit this install; at least I can enlist the help of my
stapler again... sigh
The down side of what I've done so far is that every attempt was not given an OK
or Cancel, so the system was not
"Jim P." wrote:
CDROMS are a big problem for 7.1. I have been dealing with a simular issue
for a month...still no help...I have been begging mdk support and all the
lists for help, and ya know what...most of the time no one even
respondsI have found red hat 6.2 to be a viable option
Civileme wrote:
Do the first CD in GRAPHICAL install and when it calls for the second, click OK
The installation will complete without installing anything from the second CD.
"OK" just gives the same dialog; only Cancel is valid here.
The install proceeds; but suffers from a MAJOR flaw
Pierre Fortin wrote:
Civileme wrote:
Do the first CD in GRAPHICAL install and when it calls for the second, click OK
The installation will complete without installing anything from the second CD.
"OK" just gives the same dialog; only Cancel is valid here.
The install proceeds; but
Civileme wrote:
Actually, nw that you have that much of the install, login as root and use Kpackage
to
draw the rest from the ext disk.
I would love to know what dmesg says... That CD problem is NOT a common report, and
they have a lot of trouble fixing what they cannot duplicate.
The
12 matches
Mail list logo