Problems installing 12.1 on a Qosmio F750 3D

English Install/Boot/Login
1

Greetings!

I’m currently attempting to install SuSE 12.1 x86_64 on a Qosmio F750 3D, but right now no matter what I do, it is rendered unsuccessful.

Initially everything looks fine, and YaST fires up when booting from the installation CD (network) or the DVD, but when it eventually attempts to install the packages, things go haywire.
As soon as YaST attempts to install the kernel, something locks up (possibly the post-installation scriptlet in the kernel RPM?), not proceeding any further. I have also tried to modify the kernel settings when starting up from the DVD, with even more awkward results: When setting “No local APIC”, the same thing occurs, and when applying safe settings, the kernel somehow locks up and goes out to lunch, and I cannot do anything besides shutting down the computer the hard way (by pressing the Power button for 4 secs).

Then I went to investigate the next problem on tty2, and checking with ps -ef | less gave me this (only the part involved in the installation):


root 5417 2869 8 09:54 tty1 00:00:04 rpm --root /mnt --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/openSUSE-12.1-12-1-1.4/suse/x86_64/kernel-xen-3.1.0-1.2.1.x86_64.rpm
root 5422 5417 0 09:54 tty1 00:00:00 /bin/sh /var/tmp/rpm-tmp.TJXbJa 1
root 5428 5422 0 09:54 tty1 00:00:00 /bin/bash -hB /usr/lib/module-init-tools/weak-modules2 --add-kernel 3.1.0-1.2-xen
root 5437 5428 0 09:54 tty1 00:00:00 /bin/bash -hB /usr/lib/module-init-tools/weak-modules2 --add-kernel 3.1.0-1.2-xen
root 5440 5437 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
root 5480 5440 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
root 6088 5480 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
root 6179 6088 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
root 6180 6179 0 09:54 tty1 00:00:00 /sbin/modprobe -C /dev/null --set-version 3.1.0-1.2-xen --ignore-install --show-depends nouveau
root 6181 6179 0 09:54 tty1 00:00:00 grep -E ^(insmod|builtin)

This happens no matter which kernel I might be choosing: As soon as the kernel is to be installed, rpm just locks up.

When I kill rpm (killall -9 rpm) I get the following details on its operation:


Subprocess failed. Error: RPM fehlgeschlagen: Free diskspace below /boot: 9442734 blocks
Scanning scripts ...
Resolve dependencies ...
Install symlinks in /lib/mkinitrd/setup ...
Install symlinks in /lib/mkinitrd/boot ...

Kernel image: /boot/vmlinuz-3.1.0-1.2-xen
Initrd image: /boot/vmlinuz-3.1.0-1.2-xen
KMS drivers: nouveau
Root device: /dev/disk/by-id/<identifier> (/dev/sda2) (mounted on / as ext4)

Plus I get the option to choose if I want to ignore this, abort altogether or repeat the operation (the latter gives me the exact same results, though).
Furthermore, clearing everything up (i. e. killing all subprocesses spawned by rpm) and repeating gives me an exactly identical result.

FYI: The processor installed is an Intel Core i7-2670QM.

Any help on this issue is greatly appreciated.

P.S.: I have installed the very same system from the very same DVD on an Inspiron mini, and it worked like a charm: No problems at all with that one.

2

On 08/14/2012 10:36 AM, Robidu wrote:
>
> Greetings!
>
> I’m currently attempting to install SuSE 12.1 x86_64 on a Qosmio F750
> 3D, but right now no matter what I do, it is rendered unsuccessful.
>
> Initially everything looks fine, and YaST fires up when booting from
> the installation CD (network) or the DVD, but when it eventually
> attempts to install the packages, things go haywire.
> As soon as YaST attempts to install the kernel, something locks up
> (possibly the post-installation scriptlet in the kernel RPM?), not
> proceeding any further. I have also tried to modify the kernel settings
> when starting up from the DVD, with even more awkward results: When
> setting “No local APIC”, the same thing occurs, and when applying safe
> settings, the kernel somehow locks up and goes out to lunch, and I
> cannot do anything besides shutting down the computer the hard way (by
> pressing the Power button for 4 secs).
>
> Then I went to investigate the next problem on tty2, and checking with
> ps -ef | less gave me this (only the part involved in the
> installation):
>
>
> Code:
> --------------------
>
> root 5417 2869 8 09:54 tty1 00:00:04 rpm --root /mnt --dbpath /var/lib/rpm -U --percent --force --nodeps – /var/cache/zypp/packages/openSUSE-12.1-12-1-1.4/suse/x86_64/kernel-xen-3.1.0-1.2.1.x86_64.rpm
> root 5422 5417 0 09:54 tty1 00:00:00 /bin/sh /var/tmp/rpm-tmp.TJXbJa 1
> root 5428 5422 0 09:54 tty1 00:00:00 /bin/bash -hB /usr/lib/module-init-tools/weak-modules2 --add-kernel 3.1.0-1.2-xen
> root 5437 5428 0 09:54 tty1 00:00:00 /bin/bash -hB /usr/lib/module-init-tools/weak-modules2 --add-kernel 3.1.0-1.2-xen
> root 5440 5437 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
> root 5480 5440 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
> root 6088 5480 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
> root 6179 6088 0 09:54 tty1 00:00:00 /bin/bash /sbin/mkinitrd -k /boot/vmlinuz-3.1.0-1.2-xen -i /boot/initrd-3.1.0-1.2-xen
> root 6180 6179 0 09:54 tty1 00:00:00 /sbin/modprobe -C /dev/null --set-version 3.1.0-1.2-xen --ignore-install --show-depends nouveau
> root 6181 6179 0 09:54 tty1 00:00:00 grep -E ^(insmod|builtin)
>
> --------------------
>
>
> This happens no matter which kernel I might be choosing: As soon as the
> kernel is to be installed, rpm just locks up.
>
> When I kill rpm (killall -9 rpm) I get the following details on its
> operation:
>
> Code:
> --------------------
>
> Subprocess failed. Error: RPM fehlgeschlagen: Free diskspace below /boot: 9442734 blocks
> Scanning scripts …
> Resolve dependencies …
> Install symlinks in /lib/mkinitrd/setup …
> Install symlinks in /lib/mkinitrd/boot …
>
> Kernel image: /boot/vmlinuz-3.1.0-1.2-xen
> Initrd image: /boot/vmlinuz-3.1.0-1.2-xen
> KMS drivers: nouveau
> Root device: /dev/disk/by-id/<identifier> (/dev/sda2) (mounted on / as ext4)
>
> --------------------
>
> Plus I get the option to choose if I want to ignore this, abort
> altogether or repeat the operation (the latter gives me the exact same
> results, though).
> Furthermore, clearing everything up (i. e. killing all subprocesses
> spawned by rpm) and repeating gives me an exactly identical result.
>
> FYI: The processor installed is an Intel Core i7-2670QM.
>
> Any help on this issue is greatly appreciated.
>
> P.S.: I have installed the very same system from the very same DVD on
> an Inspiron mini, and it worked like a charm: No problems at all with
> that one.
>
>

i don’t think i can help, but i see you have had none in three hours, so
here is something that might help, while you await a real guru:

  1. if you have not yet, please check the installation medium this way:
    http://tinyurl.com/3qde66h (yes, i read it worked great on a different
    machine…but, that might be because the other machine’s optical reader
    read it a little differently, or the part of your disk which is broken
    only applies to the machine in which it won’t boot. so, i know it may be
    prefect already–but, lets rule that out, please)

  2. this may also not help, or it might be the magic key: on the first
    green screen type nomodeset into the kernel options line, if that
    allows the install to proceed then you will probably have trouble the
    next time you try to boot, but that is also fixable…

if that does not help, then have a look here:
http://en.opensuse.org/SDB:Configuring_graphics_cards for the next thing
to try… (yes, i know it says the symptom is not normally a lockup as
you describe, but sometimes . . .)

  1. maybe there is something in one of these
    https://www.google.com/search?q=site%3Aforums.opensuse.org+intel+core+i7-2670qm

  2. hmmmm…you might see if a live CD for still in pre-release 12.2
    boots…it may be that it has a newer kernel which likes your i7
    better. fetch it here: http://software.opensuse.org/developer/

NOTE: read my sig caveat, and know i do NOT suggest or recommend you
install 12.2 as it is NOT ready for a production system…instead i’m
suggest to TRY to see if that newer kernel will boot up…if it does,
let us know and maybe someone here can give a good recommendation of how
to proceed…

–
dd http://tinyurl.com/DD-Caveat

3

O.k., I have investigated a bit further and can rule the other options out: It’s not an issue with the processor but instead with the graphics card.
The graphics card used on the Qosmio is a GT 540M, and somehow modprobe doesn’t like the nouveau kernel module.
During the installation process (when the kernel install locked up again) I attempted to probe nouveau, and modprobe promptly locked up so I had to kill it with CTRL-C.
After killing the modprobe initiated by mkinitrd I did the same thing - with an identical result.

How do I get rid of that one so that everything at least boots up properly (would brokenmodules=nouveau suffice here)?

4

Sorry for double-post - but unfortunately after a certain time one cannot edit his own posts any more… :frowning:

O.k., I have used brokenmodules on the boot prompt of the DVD, and the system has been successfully installed. An initial start displayed no unusual or erratic behavior, either.

How can I figure out what’s actually going haywire inside the nouveau module? And the other question: Are there any driver modules for the kernel 3.1.0 available from nVidia?

5

On 08/20/2012 07:06 PM, Robidu wrote:
>
> Sorry for double-post - but unfortunately after a certain time one
> cannot edit his own posts any more… :frowning:
>
> O.k., I have used brokenmodules on the boot prompt of the DVD, and the
> system has been successfully installed. An initial start displayed no
> unusual or erratic behavior, either.
>
> How can I figure out what’s actually going haywire inside the nouveau
> module? And the other question: Are there any driver modules for the
> kernel 3.1.0 available from nVidia?
>
>

i can’t tell from either post if you used my nomodeset hint (#2 on my
list)…i think if you had it would have got you to the same place as
your ‘brokenmodules’ did…

in any case if you had come back with success with nomodeset i would
have pointed you to http://tinyurl.com/37v9y7m – and since you have
success, i point you there now

it is (as far as i know) about the best and/or latest there is on
nvidia…HOWEVER! nvidia drivers change/come out/get updated
often…so, you might use google to drag the forum for more recent info

https://www.google.com/search?q=site%3Aforums.opensuse.org+nvidia+GT+540M

and

https://www.google.com/search?q=site%3Aforums.opensuse.org+nvidia+driver+released

oh, and all of this is just to keep you busy until a real guru shows up
to actually help you. (but, you might take a look at the refs)

–
dd http://tinyurl.com/DD-Caveat