I was looking forward to trying out the new 11.3 (KDE 64-bit iso) on my test rig. But when I boot from the DVD that I burned, the progress bar (just before the desktop loads) only gets half way and then the screen goes into a wonderful abstract of rainbow colours. At first I thought perhaps a bad DVD burn, but a second DVD produces the same result. Both DVDs boot OK in another PC, so I wonder if 11.3 doesn’t like the graphics card on the test rig? The card is a standard Nvidia 9600GT which Mandriva and Windows 7 are both quite happy with.
“Milestone 2 is part of the milestones where we track new releases in the open source universe and test the building of our various distribution images with them. While milestone 1 introduced various pre-release versions of free and open source projects (KDE 4.4 RC1, OpenOffice 3.2 Beta4 or VirtualBox 3.1 beta 1) into our development distribution openSUSE Factory, this milestone is characterized by final releases of those projects. We are also preparing everything to switch to GCC 4.5.0 as the default compiler. Currently our staging version of Factory already builds with it and our compiler people document/fix the most serious issues. They aim at milestone 3 for the switch.”
I was hopeful that it would be pretty stable and, as I said in my original post, it loads and runs OK on other machines. I believe the media are OK. Mobo is a Gigabyte GA-K8N Pro-SLI.
Indeed. This morning, I started up my computer and I am also experiencing the same problem. My graphics is an Nvidia GeForce 8 GTS with 512 MB of VRAM.
In the meantime, try using the text install by pressing F3 at the start of the installation.
>
> Romanator
>
> I appreciate your suggestion - but I can’t get to the LiveCD
> desktop because of the screen problem which is the subject of my
> original post …
>
I experienced the same problem yesterday. Download and made a MS2
KDE LiveCD. Ran all checks Ok. Then reboot and tried to install.
Screen comes up unreadable. Could not get to command line to install
Nvidia driver.
>
> If the screen is unreadable, press ALT + F1
>
>
I try this tomorrow and post results. I was just trying the LiveCD.
I have a MS2 DVD I made but have not tried installing it. I want to
try update from it, but have a problem with MS1 when the user tries
using the dvd’s drives, Can only access them after root accesses
them from dolphin or konsole. Wanted to try and solve that first.
A bug has been filed with Bugzilla about this problem.
When the installer starts, press F1 and run a text installation. Once the installation has finished, there a good chance, you’ll see that same anomaly.
To get out of it:
Press ALT + F1 and log in
Type su followed by the password
Type:
init 3
sax2 -r -m 0=vesa
init 5; exit
The command " init 5 " will take you to the desktop.
I am not able to hit F1 and get in text mode installation. Hitting too fast a gets into BIOS or too late I get Help in the Grub installation menu when boot from KDE Live CD.
I got through the KDE Live CD installation, but when I boot from disk, the KDE 4.4 graphic screen hangs and is black. But I can get to a console - tty2 (tty1 is hanging after “Start HAL deamon”) and:
> init 3
But sax2 is not found? Also tried> find / -name sax2 -print ; without luck. I can get back to> init 5 and run consoles (tty’s), but still not graphic desktop
I have also looked in /etc/X11 after X11-config files, but directory don’t look as it used to. But I can start Yast in text-mode!
Do you think it will give me any hope/way to get KDE 4.4 running?
Sorry - /etc/X11 looks like 11.2 directory. But I couldn’t find /etc/X11/xorg.conf. Something I have been lucky to fix X11 by finding another conf-file. New X11 have been changed.
>
> I had the same at a test installation. Just boot in save mode.
> Than install the nouveau driver reboot. Fixed.
>
I just tried in safemode to install the nvidia driver but it failed
saying it needed kernel symbols rpm. This was a boot from live cd in
safemode (F4) and text mode (F3). I wanted to try Live Cd (M2)
before I actually install over M1
where do you get the nouveau driver? Is it I think I’ll just do a
real clean install of M2 from the dvd.
I had similar problems installing from the dvd. After the first reboot, I had nothing but a black screen and a cursor. When I did ctrl > alt > F1, it said Starting YaST2 with a blinking cursor but did nothing after that. The sax2 command just hung.
When I booted into runlevel3, my user hadn’t been created and I could only log in as root. The second half of the install where the configuration takes place never happened.
I ended up installing in text mode. At least the second half of the install completed but I still ended up with a black screen and a cursor. Maybe the problem is with the nv driver.
But with the text install sax2 -r -m 0=vesa got me the gui finally.
As the OP of this thread, I am not convinced that this is simply an issue with the nv (graphics) driver. The LiveCD has booted OK for me in a second PC which uses the same Nvidia 9600GT card - but it has an Intel mobo/chipset, whereas the ‘problem’ machine has an Nvidia chipset. I reckon there is a wider Nvidia-based issue with MS2.
I think I’ll wait for MS3/final release and hope that the wizards who are working on this distro can fix the problem. I don’t have the technical savvy to undertake a text install.
>
> I had similar problems installing from the dvd. After the first
> reboot, I had nothing but a black screen and a cursor. When I did
> ctrl > alt > F1, it said Starting YaST2 with a blinking
> cursor but did nothing after that. The sax2 command just hung.
>
> When I booted into runlevel3, my user hadn’t been created and I
> could only log in as root. The second half of the install where
> the configuration takes place never happened.
>
> I ended up installing in text mode. At least the second half of
> the install completed but I still ended up with a black screen and
> a cursor. Maybe the problem is with the nv driver.
>
> But with the text install sax2 -r -m 0=vesa got me the gui
> finally.
>
Interesting. I’ll try that tomorrow, committed today. I thought the
Sax command had been removed. I had a similar problem the first time
I tried MS1 but somehow got into command line and installed the
nvidia package manually. Don’t remember what I did. Its worked fine
since. I’ll post my results
