[Pardus-devel] Calisan and Kurulan Differences

[Rajeev J Sebastian]

Hello Emre,

Thanks for your response. I shall try with 2007.1 as soon as I can,
but I doubt it will work, because another person also has the same
problem with 2007.1 (i.e., erratic freezing/locking of the system).

On 3/26/07, Emre Erenoglu <erenoglu at gmail.com> wrote:
> Hi Rajeev,
>
> First of all, I suggest you to use the newest 2007.1 version. It's just
> released.
> http://www.pardus.org.tr/eng/download.html
>
> Coming to differences:
> Calisan = Which runs from CD (i.e. livecd)
> Kurulan = Which installs (use this for installation on your hard disk)
>
> Can there be a problem in your BIOS, especially for ACPI? Can you update to
> the latest version? I didn't really understand your problem. Is it due to
> kernel or the display driver? Can you actually install Pardus using kurulan
> or not? If you can, do you face the problem after installation, at system
> boot up?

The reason I ask about differences is because of the symptoms:

Installer works fine, and Calisan works fine. I get X with splash
screen etc, no problem. I can work without any locking/freezing at
all.

Kurulan on the other hand doesnt work (by kurulan, I mean the
installed OS, not the YALI Installer).

I did see some differences between Calisan and Kurulan as far as GRUB
were concerned; in Calisan, video=vesafb:off ... and with Kurulan
(installed OS), it was video=vesafb:nomtrr.........

Anyway, after installation of Kurulan, the system boots, but freezes a
little while later. So, I used the runlevel 1, removed the "quiet"
option from GRUB, removed the "splash" option from GRUB, finally, made
"video=vesafb:off" in GRUB. With these settings, I can see the bootup
process. It freezes right after the init has completed and the login
starts. If I retain runlevel 3, along with removal of other options
from GRUB, then I can see that the moment X/KDM starts, the system
freezes.

>From Googling, this seems to be related to display driver ... the
system has a Intel 945/950GM card (iirc).

> Can you boot if you manually rename xorg.conf and reboot:
>
> /etc/X11/> sudo mv xorg.conf xorg.conf.rajeev
> /etc/X11/> sudo reboot
>
> Normally, zorg script shall detect your card and show you the desktop. If
> not, please try editing your xorg.conf yourself (if you know about it a
> bit).

Yes coming to this one .... I did edit xorg.conf, to use the vesa
driver instead of i810

Surprisingly, it had two Device sections, the first using i810, and
the second was nothing.

That didnt work.

Next, I tried to manually start X, to see whether KDM was at fault. I
got some wierd errors like

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
 _XSERVTransOpen: transport open failed for inet6/darkstar:0
 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6


So, following some forums online, I tried to configure -nolisten inet6
... didn't work though.


I do not have the laptop on me handy, but I can get access to it
again. Seems like other distro's have faced the same problem, so I
will provide as much info on this as possible.

Regards
Rajeev J Sebastian