After 12.3 upgrade, no graphics, part 2

English Install/Boot/Login
#1

opensuse 12.3
gnome 3.6
ati hd 3200

I upgraded another system that failed to start with hardware acceleration like the system did in Part 1 of this adventure.

Unfortunately, the same solution does not work as I cannot seem to hit ESC often enough the prevent the animation. Another difference is that it does boot in Failsafe mode, although with no acceleration.

I tried to edit the Boot Loader to modify the startup parameters to disable the boot animation. The Boot Loader, via YAST, does not load. It hangs on the “Read Partitioning” bit forever. I waited 2 hours which I feel was a sufficient time to the process.

Where are the boot loader configuration file(s) so that I can modify them directly?

#2

Probably best to change it via Yast

#3

That is what I meant by Boot Loader.

Yast::System::Boot Loader takes a very long time to discover the disk partitions, up to 10 minutes. When I select “Edit” a loader option doing nothing obvious, it hangs forever, unless it crashes the whole computer after a while.

Since the usual user-friendly tools have turned hostile, where are the boot loader configuration files?

#4

Where are the boot loader configuration file(s) so that I can modify them directly?

For grub2, read the following guide:

openSUSE 12.3: Chapter 10. The Boot Loader GRUB2

10.2.2. The File /etc/default/grub¶](http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/grub2.html#grub2.etc_default_grub) More general options of GRUB2 belong here, such as the time the menu is displayed, or the default OS to boot. To list all available options, see the output of the following command:

grep “export GRUB_DEFAULT” -A50 /usr/sbin/grub2-mkconfig | grep GRUB_ In addition to already defined variables, the user may introduce their own variables, and use them later in the scripts found in the /etc/grub.d directory.
After you edit /etc/default/grub, run grub2-mkconfig -o /boot/grub2/grub.cfg to update the main configuration file.

#5

long discovery may indicate that you have a floppy disk active in BIOS but no drive. Check the BIOS and if it indicates a floppy disable it.

#6

Yes, as it turns out. Even though there was a floppy device connected, 12.3 seems to find it too exotic to know what to do with it.

After disabling the floppy interface in the BIOS, Yast::System::Boot Loader started much more quickly. More usefully, I could edit the boot option to remove the unwanted options.

Now that the system can boot without the animated logo, the X system starts correctly as well. It is an adequate workaround.

#7

On 04/01/2013 03:56 AM, jimoe666 pecked at the keyboard and wrote:
> gogalthorp;2543276 Wrote:
>> long discovery may indicate that you have a floppy disk active in BIOS
>> but no drive. Check the BIOS and if it indicates a floppy disable it.
> Yes, as it turns out. Even though there was a floppy device connected,
> 12.3 seems to find it too exotic to know what to do with it.

More likely it was looking for a floppy disk to actually be in the drive
and had to time-out first. I would guess that if a disk was in the drive
the process would have gone quicker.

Ken

#8

I had thought so also. Having a non-bootable disk in the drive made no difference.

#9

I don’t have a floppy but others report the floppy drivers may be broken.