Hi All, Toshiba Satellite 32 bit, has been running under OpenSUSE very nicely since 11. Tried an Upgrade to 13.2 from 13.1 KDE splash screen indicated that it failed to load the Display. In 13.1 it was a Gnome desktop. So I selected CTRL +ALT +F2 and logged in there to try again, this time with a Gnome desktop. Worse outcome. Clean shut down from the Alt F2 screen and decided to run the install with LVM btrfs and encryption to force a format of /home for the next attempt. Now I know that openSUSE has moved to systemd for this release, but is that the problem, or do I look elsewhere? I still have the isos for 13.1 so regression is an option. I am seriously apprehensive about upgrading my production machine. Thanks Andrew Greig
On 12/11/14 02:02, Andrew Greig wrote:
Toshiba Satellite 32 bit, has been running under OpenSUSE very nicely since 11. Tried an Upgrade to 13.2 from 13.1 KDE splash screen indicated that it failed to load the Display [...] Now I know that openSUSE has moved to systemd for this release, but is that the problem, or do I look elsewhere?
More likely to be a display driver issue than a systemd one. You don't say which Satellite model you have. Were you using the fglrx driver? I notice that OpenSUSE 13.2 had some issue with it. https://lizards.opensuse.org/2014/11/01/fglrx-warning-opensuse-13-2-tumblewe... Glenn -- sks-keyservers.net 0x6d656d65
On Wed, 2014-11-12 at 09:43 +1100, Glenn McIntosh wrote:
On 12/11/14 02:02, Andrew Greig wrote:
Toshiba Satellite 32 bit, has been running under OpenSUSE very nicely since 11. Tried an Upgrade to 13.2 from 13.1 KDE splash screen indicated that it failed to load the Display [...] Now I know that openSUSE has moved to systemd for this release, but is that the problem, or do I look elsewhere?
More likely to be a display driver issue than a systemd one.
You don't say which Satellite model you have. Were you using the fglrx driver? I notice that OpenSUSE 13.2 had some issue with it. https://lizards.opensuse.org/2014/11/01/fglrx-warning-opensuse-13-2-tumblewe...
Hi Glenn, Thanks for the link, that script is an impressive piece of scripting. But I failed a due diligence test as my Toshy has nvidia graphics and not amd. I found this about the nouveau driver: On some systems with NVIDIA cards, the installer may show garbage on the top part of the screen due to problems with the default nouveau driver. If you are affected by this problem, you can disable the nouveau kernel module to run the installer and then enable it again once the system is installed or upgraded. To disable the kernel module, once you boot from the installation media, select the 'Installation' entry in grub and press 'e' to edit the parameters. Then go to the line starting with 'linux' (or 'linuxefi') and add brokenmodules=nouveau at the end. Now press F10 to continue booting with the new parameter. After the system is installed, you can re-enable the nouveau module by editing /etc/modprobe.d/50-blacklist.conf and removing the entry that blacklists nouveau. Now my problem is more a "failure to launch" here is an extract from lsmod nouveau 1165639 3 yenta_socket 40215 0 pcmcia_rsrc 18030 1 yenta_socket pcmcia_core 26424 3 pcmcia,pcmcia_rsrc,yenta_socket firewire_core 65881 1 firewire_ohci crc_itu_t 12627 1 firewire_core mxm_wmi 12893 1 nouveau wmi 18689 3 toshiba_acpi,mxm_wmi,nouveau i2c_algo_bit 13197 1 nouveau drm_kms_helper 59103 1 nouveau ttm 85189 1 nouveau drm 280073 6 ttm,drm_kms_helper,nouveau video 19630 1 nouveau button 13683 1 nouveau I am running the machine without graphics but with mc fortunately. Given that the system is already installed, is there something I can do, or do I need to run another install session? Cheers Andrew
participants (2)
-
Andrew Greig -
Glenn McIntosh