Mailinglist Archive: opensuse (2700 mails)

< Previous Next >
Re: [SLE] screen blocks installation of 9.1
  • From: Colin Carter <colincarter@xxxxxxxxxxxxxx>
  • Date: Sun, 3 Jul 2005 02:15:51 +1000
  • Message-id: <200507030215.51441.colincarter@xxxxxxxxxxxxxx>
On Saturday 02 July 2005 02:50, Sunny wrote:
> On 7/1/05, Colin Carter <colincarter@xxxxxxxxxxxxxx> wrote:
> > Hi folks,
> > It is an AMD 64 bit processor supplied by a company called TPG,
> > but I believe that it is actually an Arima W70-K8M in disguise.
> > I tried to install SuSE 9.1 for 64 bit machines but ran into the
> > following problem.
> Have you tried to disable apm and acpi? Set apm=off acpi=off at the boot
> prompt.
> I had similar (not exactly the same) problems, with laptops, which
> fail to boot, dying on starting different services.
> Sunny

Hi again Sunny.
I tried your suggestion.
It doesn't work, but seems to get further.
I tried using F2 to change to a screen of 1280 x 768 which
gives a good image.

What I can't understand is why the SuSE programmers
almost deliberately "mess it up".

Let me explain:
On startup I get the full SuSE "Welcome in several languages" screen.
Then, as it installs, the program displays every screen perfectly.
This includes perfect text and images.
Then it reboots.
Then the program displays text and images correctly on a full screen.
Then it displays a window with the message saying that it doesn't
know the screen dimensions and says that it is 0 x 0.
THAT is just stupid, because it has been displaying perfect text and
images for an hour!
If I adjust it to 1280 x 800 (correct native, which M$ manages),
OR to VGA, OR just 'cancel' I get the same reaction:
Flashing colours and hung machine.
These young SuSE programmers ought to take some advice
from my departed father: "If it ain't broke don't fix it."
Why, if after working perfectly well for an hour, change the mode
into something else? Just what logic are they using in the code?
Leave the bloody thing alone!

Another example of poor coding with this issue:
The boot requests (via F2) the screen resolution.
It happily accepts 1280 x 768 and uses same.
Now, my logic says that the code must have placed those values
into memory, otherwise it couldn't use these values for an hour.
If, later in the program, it reads 0 x 0, then why store 0 x 0 ?
The code even 'knows' that this is wrong (it even prompts me)
so why the hell configure and store the 0 x 0. Logic says that
if the code reached this point then the current settings, as
accepted and used above, must be a better guess than values
which it has just proven to be wrong.
Or don't they teach logic in modern programming courses?

Sorry to sound off, but every time you buy something these
days you have to make immediate arrangements to have it fixed.
For example, today I bought a new leather case to carry my
nice new laptop, and I get it home only to discover that it has a
faulty clip on the shoulder carrying strap.

If anybody has any idea how to trick SuSE logic please let me
have a hint. This is becoming urgent as I am about to board
a plane for London and I will not be able to read these emails
for three weeks.


< Previous Next >