11.2 initial install failure - question

English Install/Boot/Login
1

Hello,

I run Suse 11.0 on an IBM Thinkcentre quite nicely. However, I attempted to install 11.2 (box edition) but when I selected ‘installation’ I received the following error message.

DATA___________________Prog
:______________________7:_______2. 1
:______________________8:_______0. 1
:______________________9:____19b0.55
:______________________a:____19c7.15
0:__8bd7a._a___________b:____19bc. 5
1:______3._7___________c:____1a76.15
2:__8bd00._4___________d:____1a73.15
3:__7cb54._4___________e:____1a6a.15

err 11
ip 1a5f:_____________8c.7
>>/boot/i386/loader<<

I then click any key and I am taken to a non-gui install screen with a prompt. I have not gone beyond that screen.

Anyone have any idea why the install does not progress normally?

The machine is a p4 32mhz with 2 gig ram.

Thanks,

Mark

2

DVD or CD install
Did you do this first
http://public.bay.livefilestore.com/y1pJ4rXn0nafayHFfLo9EZ5LgLSk07iTm2dRsZNR46SIIRoMKpeAGTyuFXJOvtYN5ETgs2tQgsU_hOP6q7kNDHHIw/pic1-media%20check.png

3

Hi C.,

I ran the gamut of those options and each time I selected an option the non-gui install page appears. There is no option in the non-gui install page to check the media.

Mark

4

You didn’t tell me if you are using a DVD or CD? x86 or _64?

You should have downloaded a .iso and run a md5sum to check the .iso and post burn to CD or DVD you check that for errors too.
NEW Users - openSuse Pre-install (general) – PLEASE READ - openSUSE Forums

5

Sorry, Caf,

I said it was the boxed version and that the computer is an old P4, therefore DVD and 32 bit.

What I need to know is what does the error message mean?

The hardware should not be in issue. I have been running Suse since version 9 through 11.0 nicely on this machine and there have been no hardware changes. I have also been running Suse since v. 7.0 and never experienced this problem on many different types of machine configurations.

I cannot produce a log or memory dump as there is none produced other than the screen dump, above. Simply put the problem clearly is within the very initial stage of the install programme. I thought there might be a memory problem but a memory test shows no apparent problem.

This is the sequence of events:

(1) Hard boot with boxed DVD installed
(2) loader text message appears for an instant
(3) Graphical welcome screen appears
(4) The graphical OpenSuse installer then appears with the following options:
_____(a) boot from hard disk
_____(b) Installation
_____(c) Repair installed system
_____(d) Rescue system
_____(e) Check installation media
_____(f) Firmware test
_____(g) Memory test

When I select any of these options (a) through (g) I am presented with the screen dump which I have replicated, above in my first email.

The same sequence of events occurs whether I change the kernal settings from default to saft or to no ACPI or to no local APIC. I have also changed video mode from 1600x1200 to VGA but to no avail. The screen dump always appears.

The machine is an IBM Thinkcentre with a p 4 (HT) running at 3.2GHz (no o/c). 2 gigabytes of non-ECC memory (PC2700 (333MHz)).

As for chipsets:
____Intel 865GV chipset
____Integrated Intel Extreme Graphics 2
____I/O Controller Hub (ICH5) for PCI 2.2 bus
____AC '97 2.3 Digital controller

The IDE controller is SATA.

So, bog standard equipment which should not frustrate the loader.

I have no DVD writer so can’t burn the download on-line version as a check. I doubt there is a media problem. Translating the error message will be key. Any thoughts? It may be an exception error, too.

Thanks,

Mark

6

NEW Users - Suse-11.2 Pre-installation – PLEASE READ - openSUSE Forums

7

I realized the same issues. After the installation finished and the system rebootes, the same error window appears. When I get the Welcome Linux graphical screen, I try to log in, a short piece of music can be heard which is interrupted. After that, the login screen reappears.

What can I do?

8

You could tell us what graphics you have.
If you are using kde or gnome.
Have you tried the Failsafe boot option?