> At a “higher level” than load the vesa driver, what are you trying to
> do? Just play with the 11.2 milestone5 live CD ? Are you trying to
> install from the live CD ?
I’m just “playing” with the LiveCD, not trying to installing it. Just want
to check if all of my hardware is being correctly detected and how it looks
the milestone 5, so nothing serious
> ie Does the liveCD boot to a GUI and then fail during the installation
> or Does the liveCD fail when booting the GUI ?
LiveCD boots fine, but cannot load X session and leaves me into “init 3”. As
per the above bugzilla I mentioned, it seems the “intel” kernel module is
missing from the LiveCD of Milestone 5 and cannot be loaded at all, so it
falls into init 3.
I would like to get into graphical mode using standard vga “vesa” driver, if
that is possible.
> If the latter, with root permissions, then “sax -r -m 0=vesa” is the
> nominal way of loading the vesa driver. Note that is “zero equals vesa”
> and not “Oh equals vesa”. You could try just “sax2 -m 0=vesa”
> The " -r " option removes the detection database and re-init the
> hardware database.
I am testing now with: “sax2 -m 0=vesa”. No go, but /var/log/SaX.log shows
it tries to load vesa module and fails with the message “virtual width
(3840) is too large for the hardware (max. 2048)… screen(s) found, but
none have a usable configuration”. That can be the clue…
> … If you have more than one graphic device, you could try “sax2 -m
> 1=vesa” to access the second graphic device. You could try that without
> and with " -r " (ie also try “sax2 -r -l -m 0=vesa” … )
I’m afraid I only have one embedded vga card O:-)
> You could also try to force lower levels of graphics for the vesa
> driver with " sax2 -l -m 0=vesa" (where “-l” forces a lower resolution
> - that is a lower-case “L” ).
That sounds good, let’s try!
Well, no luck, I still get the same response as above. It seems vesa driver
tries to setup a screen size larger than the one it can handle and fails.
> You could also try forcing the intel driver at a lower resolution with:
> " sax2 -l -m 0=intel "
Mmm… “intel” module is completely missing, it’s not included in this
Milestone 5 so it cannot be loaded (some developer forgot to add it while
compiling or building the milestone into the OBS, dunno :-P).
> If you type “max sax2” you can read the various sax2 options.
Yes, I will try by forcing “vesa” driver to load a lower resolution by
checking the available options. I will post here any advance
Thanks so much for the suggestions!