Installing 11.3 hangs at 82%

Hi,

I’ve been trying to install Opensuse 11.3 from the Kde live cd, but the installation hangs when I’m almost done. Right at the beginning the installation is interrupted right with text that among other things says:

Bug: unable to handle kernel paging request at ffffc90010b8000

After a while though, the installation picks up and continues by itself. I’m then able to complete the necessary steps and I reboot the system so that it can complete the installation.

After reboot there is a new text message that says that the bios does not support EEC memory or something to that effect and then continues with the installation. When it has completed 82% of the autoconfiguration the installation just stops and stays that way.

I’ve had no problem installing previous releases, from 10.2 up to 11.2, on the same machine.

I’ve checked md5 sum and also checked the media before proceeding with the installation.

Upon reboot after the first installation step, I also tried the failsafe mode but got the same result.

Any advice?

So you should have a grub menu to boot from?
If you have try adding 3 to the boot line, like this:
http://public.bay.livefilestore.com/y1phdSlIu0YoBuz194VhjYxYLVFt6ZB1SqN7MTU-WZoaG2ux-TBNywQ6MD0-TW-jgnK3Y2heZOcwN4ooSXeWqHAAQ/2%20Edit%20the%20Boot%20line.png?psid=1

See if it will proceed from there

Hi Caf4926,

Yes, I have a grub menu. I added 3 and then pressed enter, but it still stopped at 82% and just stayed like that.

press ESC as soon as you boot to watch the process perhaps you can see where it hangs.

Or just try the install from the beginning again.

Hi Gogalthorp!

I pressed esc and I can see that everything begins good until it says ‘starting udevd’. Then it presents a lot of info, too much for me to write it down in time before it disappears (I don’t know how to save it and print it here). Here are the sentences that contained the word ‘error’ that I managed to write down:


Loading drivers; configuring devices    7.435064] sr1 CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00

Bug: unable to handle kernel paging request at ffffc90010cb8000

... <snip a lot of text which seems ok: at the end it says>...

sr1: cdrom error, command get config 46 00 00 00 00 00 00 00 20  00
sr: Sense key hardware error [current]
sr: Add. Sense: No additional sense information


After a while, the system comes to live by itself and continues with the installation. Any idea?

I’ve tried to re-install it two times but it ends with the same result, I.e. the installation freezes at 82%.

I just discovered that when the installation freezes at 82%, I can still use Ctrl+Alt F1 through F12.

When I press Ctrl+Alt F8 there is some information about the installation. Among other things it says:


From /var/log/Xorg.0.log

(WW) warning, (EE) error, (II) Information, (NI) not implemented, (??) unknown

(EE) Failed to load module "fglrx" (module does not exist, 0)
(II) [KMS] Kernel modesetting enabled.
(EE) No input driver/identifier specified (ignoring)

In Ctrl+Alt F1, I can read information about the start-up. The output ends with “starting up Yast-installer” or something to that effect. No error messages here except that it is “waiting for eth0 DHCP” and “Setting up service (localfs) network… failed” which I figure is normal since I access the net through a mobile broadband.

Ctrl+Alt F2 brings me a prompt which I can interact with. I don’t use the prompt that much so I don’t know what I could do from here. I used ls -l and found that there are several directories installed, e.g. bin, boot, dev, clicboot, etc, lib, home, root.

I also managed to open up /var/log/Xorg.0.log.

Suggestions? Any advice on what I could try would be much appreciated!

Fglrx is the ATI driver for Radeon and Fire GL cards. If you do have a ATI card, try the parameter “nomodeset” in the grub menu. ATI graphic cards driver problems are often source of suboptimal install.

Hi Stakanov!
I tried nomodeset but it still freezes at 82%.:dont-know:

Hello Brama-Vihara.
Ok, what about asking you if you did eliminate the most frequent troublemaker? Try to install with ACPI disabled. I say this because recently I installed on a machine with Asrock mainboard and had an ACPI/HPET problem blocking the install always at 90%. It can help but must not. Just try. Otherwise, this is a fresh install I suppose. If the problem is the availability during install of the ATI driver rpm, there should be a possibility to indicate something like “third party driver” as a supplemental installation source during the process. You could charge the appropriate flgrx driver on usb and install it from there.
Did you do the “self-check” on the CD? Do you have ECC-ram on that machine? Did you try to put the values of Ram-timing in safe default values and to deactivate ECC, if you have it and it is switched on, during the install?
I think it could be helpful to have an idea about the hardware asset that your machine has.
And how did you fill the ram-banks? Dual-channel? Same producer?

It would not try to load fglrx on a new install it would use the radeon driver. So I’m guessing this is an upgrade and there is an old xorg.conf file setting around that loaded the fglrx driver and now the driver is not there.

So need more info from the OP about exactly what he is doing.

Thanks for the tips Stakanov. Plenty to try out.

Indeed, I have an Asrock mainboard. I checked my bios setup and every option under ACPI was disabled. I also tried the boot option acpi=off with no effect.

Ok, how do I do this? How do I indicate “third party driver” as a supplemental installation source during installation? I’m not so technical so I’d need some specific steps to follow to pull this off.

Did you do the “self-check” on the CD?

Yes, and it reported no problems.

Do you have ECC-ram on that machine?

Did you try to put the values of Ram-timing in safe default values and to deactivate ECC, if you have it and it is switched on, during the install?

I don’t know. How do I check? I have 1024 MB DDR2 667MHz PC-5300 CL5. During installation I get a message that says that the bios does not support EEC memory. It delays the installation process and then continues with the installation. I’ve looked in the BIOS setup for ECC-ram but couldn’t find ECC or EEC mentioned anywhere.

And how did you fill the ram-banks? Dual-channel? Same producer?

Singel-chanel memory mode in one memory slot.

I think it could be helpful to have an idea about the hardware asset that your machine has.

AMD Athlon 64bit 3500+
V-Data 1024MB DDR2 667MHz PC-5300 CL5
Samsung 200GB SATA2
ATI Radeon X300SE
Asrock AM2 K8T890CF DDR2 SATA2 LAN

If it’s of any help, here’s the output from lspci


00:00.0 Host bridge: VIA Technologies, Inc. K8T890CF Host Bridge
        Subsystem: ASRock Incorporation Device 0351
        Flags: bus master, medium devsel, latency 32
        Capabilities: [50] Power Management version 2
        Capabilities: [60] HyperTransport: Slave or Primary Interface
        Capabilities: [58] #00 [0000]

00:00.1 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge
        Subsystem: ASRock Incorporation Device 1351
        Flags: bus master, medium devsel, latency 0


00:00.5 PIC: VIA Technologies, Inc. VT3351 I/O APIC Interrupt Controller (prog-if 20 [IO(X)-APIC])
        Subsystem: ASRock Incorporation Device 5351
        Flags: bus master, fast devsel, latency 0


00:01.0 PCI bridge: VIA Technologies, Inc. [K8T890 North / VT8237 South] PCI Bridge (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Capabilities: [70] Power Management version 2

00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
        I/O behind bridge: 0000e000-0000efff
        Memory behind bridge: fea00000-feafffff
        Prefetchable memory behind bridge: 00000000f0000000-00000000f7ffffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [68] Power Management version 2
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [180] Root Complex Link <?>
        Kernel driver in use: pcieport-driver

00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
        Prefetchable memory behind bridge: 00000000eff00000-00000000efffffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [68] Power Management version 2
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [180] Root Complex Link <?>
        Kernel driver in use: pcieport-driver

00:03.1 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        Prefetchable memory behind bridge: 00000000efe00000-00000000efefffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [68] Power Management version 2
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [180] Root Complex Link <?>
        Kernel driver in use: pcieport-driver

00:03.2 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: fe900000-fe9fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [68] Power Management version 2
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel <?>
        Kernel driver in use: pcieport-driver

00:03.3 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: fe800000-fe8fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [68] Power Management version 2
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [180] Root Complex Link <?>
        Kernel driver in use: pcieport-driver

00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
        Subsystem: ASRock Incorporation Device 0591
        Flags: bus master, medium devsel, latency 32, IRQ 21
        I/O ports at bc00 [size=8]
        I/O ports at b880 [size=4]
        I/O ports at b800 [size=8]
        I/O ports at b480 [size=4]
        I/O ports at b400 [size=16]
        I/O ports at b000 [size=256]
        Capabilities: [c0] Power Management version 2
        Kernel driver in use: sata_via

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) (prog-if 8a [Master SecP PriP])
        Subsystem: ASRock Incorporation K7VT2/K7VT6 motherboard
        Flags: bus master, medium devsel, latency 32
        [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
        [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
        [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
        [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
        I/O ports at fc00 [size=16]
        Capabilities: [c0] Power Management version 2
        Kernel driver in use: pata_via

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
        Subsystem: ASRock Incorporation K7VT6
        Flags: bus master, medium devsel, latency 32, IRQ 20
        I/O ports at a480 [size=32]
        Capabilities: [80] Power Management version 2
        Kernel driver in use: uhci_hcd

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
        Subsystem: ASRock Incorporation K7VT6
        Flags: bus master, medium devsel, latency 32, IRQ 22
        I/O ports at a800 [size=32]
        Capabilities: [80] Power Management version 2
        Kernel driver in use: uhci_hcd

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
        Subsystem: ASRock Incorporation K7VT6
        Flags: bus master, medium devsel, latency 32, IRQ 21
        I/O ports at a880 [size=32]
        Capabilities: [80] Power Management version 2
        Kernel driver in use: uhci_hcd

00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
        Subsystem: ASRock Incorporation K7VT6
        Flags: bus master, medium devsel, latency 32, IRQ 23
        I/O ports at ac00 [size=32]
        Capabilities: [80] Power Management version 2
        Kernel driver in use: uhci_hcd

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
        Subsystem: ASRock Incorporation K7VT6 motherboard
        Flags: bus master, medium devsel, latency 32, IRQ 21
        Memory at fe7ffc00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2
        Kernel driver in use: ehci_hcd

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
        Subsystem: ASRock Incorporation Device 3337
        Flags: medium devsel
        Capabilities: [c0] Power Management version 2

00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
        Subsystem: VIA Technologies, Inc. Device 337e
        Flags: bus master, medium devsel, latency 32
        Capabilities: [58] HyperTransport: Interrupt Discovery and Configuration

00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge
        Flags: bus master, fast devsel, latency 0

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
        Flags: fast devsel
        Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
        Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
        Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
        Flags: fast devsel
        Capabilities: [f0] Secure device <?>
        Kernel driver in use: k8temp

02:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: ASRock Incorporation Motherboard (one of many)
        Flags: bus master, fast devsel, latency 0, IRQ 40
        Memory at fe8fe000 (32-bit, non-prefetchable) [size=8]
        Expansion ROM at fe8e0000 [disabled] [size=64]
        Capabilities: [68] Power Management version 2
        Capabilities: [50] Express Legacy Endpoint, MSI 01
        Kernel driver in use: ahci

02:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 AHCI Controller (rev 02) (prog-if 85 [Master SecO PriO])
        Subsystem: ASRock Incorporation Motherboard (one of many)
        Flags: bus master, fast devsel, latency 0, IRQ 41
        I/O ports at cc00 [size=8]
        I/O ports at c880 [size=4]
        I/O ports at c800 [size=8]
        I/O ports at c480 [size=4]
        I/O ports at c400 [size=16]
        Capabilities: [68] Power Management version 2
        Kernel driver in use: pata_jmicron

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
        Subsystem: ASRock Incorporation Motherboard (one of many)
        Flags: bus master, fast devsel, latency 0, IRQ 36
        I/O ports at d800 [size=256]
        Memory at fe9ff000 (64-bit, non-prefetchable) [size=4]
        Expansion ROM at fe9c0000 [disabled] [size=128]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Vital Product Data
        Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
        Capabilities: [60] Express Endpoint, MSI 00
        Capabilities: [84] Vendor Specific Information <?>
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [12c] Virtual Channel <?>
        Capabilities: [148] Device Serial Number 1a-00-00-00-10-ec-81-68
        Capabilities: [154] Power Budgeting <?>
        Kernel driver in use: r8169

06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller])
        Subsystem: ATI Technologies Inc Device 1b60
        Flags: bus master, fast devsel, latency 0, IRQ 24
        Memory at f0000000 (32-bit, prefetchable) [size=128]
        I/O ports at e000 [size=256]
        Memory at feae0000 (32-bit, non-prefetchable) [size=64]
        Expansion ROM at feac0000 [disabled] [size=128]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Advanced Error Reporting

06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
        Subsystem: ATI Technologies Inc Device 1b61
        Flags: bus master, fast devsel, latency 0
        Memory at feaf0000 (32-bit, non-prefetchable) [size=64]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Express Endpoint, MSI 00

80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
        Subsystem: ASRock Incorporation Device 0888
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at febfc000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [100] Virtual Channel <?>
        Kernel driver in use: HDA Intel


Thanks for taking your time![/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]

On 2010-08-05 18:36, Brahma-Vihara wrote:
>
> gogalthorp;2200976 Wrote:
>> press ESC as soon as you boot to watch the process perhaps you can see
>> where it hangs.
>
> Hi Gogalthorp!
>
> I pressed esc and I can see that everything begins good until it says
> ‘starting udevd’. Then it presents a lot of info, too much for me to
> write it down in time before it disappears (I don’t know how to save it
> and print it here). Here are the sentences that contained the word
> ‘error’ that I managed to write down:

They are saved to a file in /var/log/messages, I think. But the file is in fact in memory (it is a
live system from DVD), so it disappears when you power off.

If you could mount an usb disk, or a partition where you can write, it would be copy that file there.

> Code:
> --------------------
>
> Loading drivers; configuring devices 7.435064] sr1 CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
>
> Bug: unable to handle kernel paging request at ffffc90010cb8000

I don’t like that one…

> … <snip a lot of text which seems ok: at the end it says>…
>
> sr1: cdrom error, command get config 46 00 00 00 00 00 00 00 20 00
> sr: Sense key hardware error [current]
> sr: Add. Sense: No additional sense information
>
>
> --------------------
>
>
> After a while, the system comes to live by itself and continues with
> the installation. Any idea?

Those are kernel booting messages, and I assume the system boots, as you can issue commands on VT-2.

The messages could be important, or maybe not. Hard to say.

The last message is the one you can read by the ctrl-alt-f1 you did, and I thing what you see there
is normal. There are several consoles or virtual terminals, try ctrl-alt-F1…F12. One is the
graphical terminal, the one I assume is hanged. What does it display? There will be three or four in
which you can type commands, like the VT-2. A typical command to issue is “top”, which will show the
processes that are currently running and give you a clue. Perhaps one is at 100% cpu.

The directories you see there are not the ones being installed, but those of the live system. A “df”
or a “mount” will show you the available filesystems.

Try the rest of the terminals, some of them are logs outputs of several subsystems. One is from
yast, I think.

It is also possible to install in text mode. You might not like it, but it is a possibility.

And it may be that you simply can not run 11.3. I would try to run the lives of gnome and/or kde. I
don’t like what you say about the paging request failed or the EEC memory not being handled.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))

I am looking at your specs. There are two boards with the Via Chipset K8T890CF. The first is the AM2V890-VSTA, the other is the ALIVESATA2-GLAN. One of the two should be your case. Could you tell me which one is the right one so I can go a bit through the specs to understand what you have on your board? Thanks.

I haven’t tried to install 11.3 on my 11.2 system through an upgrade, but rather to install the system with a live-cd on another partition which I formated during the installation.

What info would be of help?

I have the later one! I found this article with the specs of the board:
[OCWORKBENCH.COM] ASRock ALIVESATA2-GLAN AM2 board (VIA K8T890CF) Review Intro 1/5]([OCWORKBENCH.COM] ASRock ALIVESATA2-GLAN AM2 board (VIA K8T890CF) Review Intro 1/5)

That info is to a certain extend of help. I am not sure if it is possible to do this, actually I have the feeling that this may be the reason the install fails. I know that it should be possible to run two different distributions on the same PC with dual boot (in this case probably a /boot would be best) and there you would be able to share swap and /home. But I am by no means sure that you can install two subsequent versions of the same distribution on the very same PC. Do you have a /boot partition or do you write to the MBR?
Maybe Caf4926 might know if this is possible. I am by no means sure. Never had the idea, I virtualize if I want to try out.

Hi Carlos!

I managed to copy several log files including ‘messages’. The strange thing is that when I open the file it is empty, even though the size of the file is 259.3 KiB. The other files I can open.

> Code:
> Loading drivers; configuring devices 7.435064] sr1 CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
>
> Bug: unable to handle kernel paging request at ffffc90010cb8000

I don’t like that one…

Me neither :slight_smile:

> … <snip a lot of text which seems ok: at the end it says>…
>
> sr1: cdrom error, command get config 46 00 00 00 00 00 00 00 20 00
> sr: Sense key hardware error [current]
> sr: Add. Sense: No additional sense information
>
> --------------------
>
> After a while, the system comes to live by itself and continues with
> the installation. Any idea?

Those are kernel booting messages, … <snip>

The last message is the one you can read by the ctrl-alt-f1 you did, and I thing what you see there is normal. There are several consoles or virtual terminals, try ctrl-alt-F1…F12.

I went through F1-F12. Only F1, F2, F7, F8 and F10 are active. The others are totally blank.

One is the graphical terminal, the one I assume is hanged. What does it display?

There are two progress bars displaying the post-installation configuration. When the system freezes, the first one is at 23% and the second one at 82%.

There will be three or four in which you can type commands, like the VT-2. A typical command to issue is “top”, which will show the processes that are currently running and give you a clue. Perhaps one is at 100% cpu.

I can only typ commands in VT-2, the other terminals are either displaying information or totally blank/non-responsive.

The output from top gave me no hints (on the other hand I don’t know what to look for). None of the processes used 100%, rather the oposite. The ‘top’ command showed 1% in usage and the rest more or less 0%. top also showed that there are 89 sleeping tasks and 1 running.

The directories you see there are not the ones being installed, but those of the live system. A “df” or a “mount” will show you the available filesystems.

Here’s the output (by hand) from df:


Filesystem         1K-blocks        Used        Available          Use       Mounted on
/dev/sda8         8309420          2925992   4961324           38%      /
devtmpfs          509488            220         509268             1%       /dev
tmpfs               510928           8084        502844             2%       /dev/shm
/dev/sda7...................(my home partition)...............      96%     /home
/dev/sda1...................(my windows partion)..............     89%    /windows/C

Try the rest of the terminals, some of them are logs outputs of several subsystems. One is from yast, I think.

I believe this is terminal F8. Here’s part of the output which I wrote down by hand


From /var/log/Xorg.0.log

(WW) warning, (EE) error, (II) Information, (NI) not implemented, (??) unknown

(EE) Failed to load module "fglrx" (module does not exist, 0)
(II) [KMS] Kernel modesetting enabled.
(EE) No input driver/identifier specified (ignoring)

It is also possible to install in text mode. You might not like it, but it is a possibility.

I’m willing to try. How do I start the installation in text mode?

Thanks!
PS. Ctrl+Alt+F10 shows information about eth0/dhcp trying to connect to the internet. I have mobile broadband so I think it’s nothing unusual.

I managed to copy some log files to my home partition. Some of info from (e.g. /var/log/Xorg.0.log) can’t be posted because they’re too long.

Here’s the output from:
kdm.log


********************************************************************************
Note that your system uses syslog. All of kdm's internally generated messages
(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to which
file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
********************************************************************************


X.Org X Server 1.8.0
Release Date: 2010-04-02
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 x86_64
Kernel command line: initrd=initrd,10240768.spl ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent quiet preloadlog=/dev/null vga=0x317
Build Date: 05 July 2010  09:27:36PM
 
Current version of pixman: 0.18.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 29 23:20:39 2010
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "fglrx" (module does not exist, 0)
(II) [KMS] drm report modesetting isn't supported.
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] This chipset requires a kernel module version of 1.17.0,
[dri] but the kernel reports a version of 2.3.0.[dri] If using legacy modesetting, upgrade your kernel.
[dri] If using kernel modesetting, make sure your module is
[dri] loaded prior to starting X, and that this driver was built
[dri] with support for KMS.
[dri] Disabling DRI.
NTSC PAL 
  XRANDR name: VGA-0
  Connector: VGA
  CRT1: INTERNAL_DAC1
  DDC reg: 0x60
  XRANDR name: DVI-0
  Connector: DVI-I
  CRT2: INTERNAL_DAC2
  DFP1: INTERNAL_TMDS1
  DDC reg: 0x64
  XRANDR name: S-video
  Connector: S-video
  TV1: INTERNAL_DAC2
  DDC reg: 0x0
finished output detect: 0
finished output detect: 1
finished output detect: 2
finished all detect
Entering TV Save
Save TV timing tables
saveTimingTables: reading timing tables
TV Save done
disable FP1
disable primary dac
disable FP1
disable TV
disable FP1
init memmap
init common
init crtc1
init pll1
freq: 108000000
best_freq: 108000000
best_feedback_div: 16
best_frac_feedback_div: 0
best_ref_div: 2
best_post_div: 2
restore memmap
restore common
restore crtc1
restore pll1
finished PLL1
set RMX
set FP1
enable FP1
disable primary dac
disable TV
(EE) No input driver/identifier specified (ignoring)
(EE) No input driver/identifier specified (ignoring)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Duplicate shape name ""
>                   Using last definition
> Warning:          Multiple doodads named ""
>                   Using first definition
> Warning:          Multiple doodads named ""
>                   Using first definition
> Warning:          Multiple doodads named ""
>                   Using first definition
> Warning:          Multiple doodads named ""
>                   Using first definition
> Warning:          Multiple doodads named ""
>                   Using first definition
> Warning:          Multiple doodads named ""
>                   Using first definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server