Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Errors during MDK9 install?

0 views
Skip to first unread message

SomeOne

unread,
Oct 9, 2002, 9:52:52 PM10/9/02
to
Hey all!

Just wondering what might be causing errors during my Mandrake 9 install...

PC is working - it ran Win2K server for a year without an issue. Hardware is:

-Cyrix M3 733mhz CPU
-128 PC 100 memory
-ATI all-in-wonder AGP video card (8meg)
-CMedia based PCI soundcard - 6 channel
-SMC1211TX 10/100 PCI network card
-14.4k ISA hardware modem (COM3, IRQ9)
- Gigabyte GA6VXE7+ mainboard
- PS2 keyboard/mouse
-36X CDRom
-1.44m floppy

If I boot from a DOS diskette, I can read all sectors on the CD, so the CD's are readable on this CD drive. Sector tests of the hard drive show no bad sectors. Checksums of the ISO files I downloaded match. (Can one do a checksum on the CD itself?)

Doing a text or graphical install, while it is copying the packages I will occasionally get an error "There was an error copying XXX. Do you want to continue?"

On the F3 screen it starts having issues when the following appears:

getFile libbonobo2_0-2.0.0-2mdk.i586.rpm:Installation CD1(x86)
transactions done, now trying to close still opened fd
getFile XXX:
bad package XFree86-4.2.1-3mdk.i586
opened rpm database for retry transaction of 1 package only
rpm transactions start
getFile XFree86-4.2.1-3mdk.i586:Installation CD 1 (x86)
transactions done, now trying to close still opened fd
getFile XXX:
bad package XFree86-4.2.1-3mdk.i586
opened rpm database for retry transaction of 1 package only
rpm transactions start
getFile XFree86-4.2.1-3mdk.i586:Installation CD 1 (x86)
...etc.

On the F5 screen I see:
/tmp/imm.o: init_module: No such device
/tmp/ppa.o: init_module: No such device

If I keep going and let it finish I will see a few of these errors, then on reboot I don't get anything happening after the hardware detection of the BIOS. Not even the "LI" I'm used to seeing for a bad install.

ANY help is appreciated. Thanks!

Birdy

unread,
Oct 10, 2002, 2:39:39 AM10/10/02
to
>Just wondering what might be causing errors during my Mandrake 9 install...
>Doing a text or graphical install, while it is copying the packages I will
occasionally get
>an error "There was an error copying XXX. Do you want to continue?"

Howdy - I'd had the exact same problem. Pain in the ass, made me hafta
install Redhat 8.0 until Mandrake gets in gear and fixes it. Hopefully I
won't get too tied down to Redhat 8.0 by the time they do.

I've looked all over for the cause of this problem, and kinda determined
what the common factor is. Number one on your list of hardware -

>-Cyrix M3 733mhz CPU

I have a Via Epia 800 (C3 @ 800mhz) board, you have a C3, and MOST of the
other cases I've seen have a C3. I guess we're SOL until Mandrake figures
this thing out. :(

Someone prove me wrong, please!


Birdy

unread,
Oct 10, 2002, 12:36:46 PM10/10/02
to
Found a much more useful answer than my previous "Us C3 users are SOL"

http://www.linux-mandrake.com/en/errata.php3#viac3

A quick little workaround, just for the installer.

Enjoy!


Opinator

unread,
Oct 10, 2002, 10:44:36 PM10/10/02
to
Most common reason is bad ISO files... if you downloaded from some FTP.


"SomeOne" <dont...@me.now> escribió en el mensaje
news:U35p9.514061$f05.21...@news1.calgary.shaw.ca...

SomeOne

unread,
Oct 11, 2002, 9:53:03 AM10/11/02
to
Thanks for the info!

I'll give it a go and see what happens!

P.s. Sorry for the busted time on my previous posts everyone. Forgot to set it back after testing some software.

"Birdy" <nospamo...@bradeeoh.no.way.com> wrote in message news:uqbb4ui...@corp.supernews.com...

SomeOne

unread,
Oct 11, 2002, 1:25:25 PM10/11/02
to
Ok...

It's definately a compatibility issue with the Cyrix C3 processor.

The information at that link got me installed without any errors. A couple of comments for those who aren't sure what to do...

- To make the indicated diskette from DOS:
rawrite -d a -f /images/alternat/cdrom_im.19_
- I could not format my partitions with the Reiser file system, so I chose the ext3
- You will be prompted for the root password a fair ways into the installation.

The install completed fine, but still did not work.

During boot the terminal displayed a fair number of errors. It appears that the filesystem is mounted read only. Even after logging in as root I'm getting read only errors. I just tried to save a text file from VI and no go. Unfortunately, I can't scroll backwards through the terminal screen to see where the errors started occurring.

BLECH!

For some reason I didn't get an IP until after the install completed and the PC rebooted. I couldn't get the updates during the install, or test my printer (which is on an IP print server)

...at this point I'm wondering whether I should try another distro, or maybe just load OpenBSD and forgo Linux.

"Birdy" <nospamo...@bradeeoh.no.way.com> wrote in message news:uqbb4ui...@corp.supernews.com...

Peter T. Breuer

unread,
Oct 11, 2002, 3:20:40 PM10/11/02
to
SomeOne <dont...@me.now> wrote:
> It's definately a compatibility issue with the Cyrix C3 processor.

With what? Make sure you install a kernel that nothing more than plain
i386 instructions in.

> The information at that link got me installed without any errors. A couple of comments for those who aren't sure what to do...

> - To make the indicated diskette from DOS:
> rawrite -d a -f /images/alternat/cdrom_im.19_

?? well, whatever turns you on!

> - I could not format my partitions with the Reiser file system, so I
> chose the ext3

There's no need (or purpose) in doing so ...

> The install completed fine, but still did not work.

> During boot the terminal displayed a fair number of errors. It
> appears that the filesystem is mounted read only. Even after logging in
> as root I'm getting read only errors. I just tried to save a text file

There's no surprise in that. It's readonly! Being root or god
makes no difference. Remount it rw, but first fix the fs erros that
caused it to be mounted ro.

> terminal screen to see where the errors started occurring.

No need to. dmesg.

> ...at this point I'm wondering whether I should try another distro, or maybe just load OpenBSD and forgo Linux.

Well, what's a "C3"? If it's not up to i586 instuctions, you need a
different install kernel.

Peter

SomeOne

unread,
Oct 11, 2002, 4:22:18 PM10/11/02
to
> > It's definately a compatibility issue with the Cyrix C3 processor.
>
> With what? Make sure you install a kernel that nothing more than plain
> i386 instructions in.

But a C3 is a Socket 370 processor that should be compatible with at least a Celeron or P3 level processor - the key word here being "should".

> > The information at that link got me installed without any errors. A couple of comments for those who aren't sure what to do...
>
> > - To make the indicated diskette from DOS:
> > rawrite -d a -f /images/alternat/cdrom_im.19_
>
> ?? well, whatever turns you on!

The filenames in DOS do not match with those in the intsructions... Definately confusing for a newbie.

> > - I could not format my partitions with the Reiser file system, so I
> > chose the ext3
>
> There's no need (or purpose) in doing so ...

And if I *WANT* to use the Reiser journaling filesystem, then what? From what I hear it's faster and more robust than ext3.

> > During boot the terminal displayed a fair number of errors. It
> > appears that the filesystem is mounted read only. Even after logging in
> > as root I'm getting read only errors. I just tried to save a text file
>
> There's no surprise in that. It's readonly! Being root or god
> makes no difference. Remount it rw, but first fix the fs erros that
> caused it to be mounted ro.

I would expect a brand new install to work the first boot after the installation. WHY would it stay read only? I haven't done anything to it yet!

> > terminal screen to see where the errors started occurring.
>
> No need to. dmesg.

What is a "dmesg" ??? How do I do this while the system is booting? Or is this a log file I should read after logging in? Where would I find it?

SomeOne

unread,
Oct 15, 2002, 3:58:19 PM10/15/02
to
Just an update... Had more time to try more installs...

At this point, the instructions on Mandrakes site work for installing
Mandrake 9 on a C3 based machine. I haven't gotten a full install
working due to other issues... The image file you need on the CD is
called "cdrom_im.19_" - this installs without errors. (You can't use
the Reiser file system)

- During the install, on disc 3, the machine will just lock solid.
Can't even CAD to restart. I have to use the reset or power button. I
can log into the box at this point, but X is not configured. I'm
guessing that this is something to do with the XFree install/config as
the machine freezes just after I choose XFree 4.0.1.

- I save my packages choices to a floppy halfway through the
installation. Next time I try to install and load this back in, the
installer just keeps asking for a disk with the file on it. The
auto_inst.cfg file is on the floppy and I can read it.

From what I've seen of KDE3, it looks pretty good... I'm considering
installing it on my main box:
- AMD Tbird @ 1.33Ghz
- 512meg DDR
- ECS mainboard (onboard Avance sound, Realtek RTL100 LAN and Promise
RAID)
- AGP Geforce 2 GTS video
- SB Live! soundcard
- USB MS Cordless optical mouse "blue"
- PS2 MS ergo keyboard
- USB Mustek Bearpaw 1200 scanner
- 40gig IBM DTLA hard drive
- Hitachi GD7500 DVD reader

...this would definately dual boot between Mandrake and WinXP.

Anyone see any issues with the hardware above?


SomeOne

unread,
Oct 15, 2002, 4:13:36 PM10/15/02
to
Just a correction...

> - During the install, on disc 3, the machine will just lock solid.
> Can't even CAD to restart. I have to use the reset or power button.
I
> can log into the box at this point, but X is not configured. I'm
> guessing that this is something to do with the XFree install/config
as
> the machine freezes just after I choose XFree 4.0.1.

... it's after I choose 4.2.3 (not 4.0.1).

- ATI All in Wonder Pro, 8meg AGP
- NEC XV15 set for 1024x768x16bit

mouse will move (gonna leave it alone for a while and see if anything
happens) but I'm pretty certain that clicking it will freeze the PC.


0 new messages