Siduction Forum

Siduction Forum => Software - Support => Topic started by: mylo on 2013/09/22, 10:53:01

Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/22, 10:53:01
Hi all,

I made an install of firestarter, however the system cannot be used. I made a d-u after (around 800 packs), however everything went smooth. The windows appear incomplete, buttons and sections of the windows appear when hoovering with the mouse. The application launcher is missing (I will try zo post a snapshot if I can). What can aI do besides another install?
Title: RE: Fresh install from firestarter: Problems with incomplete
Post by: absolut on 2013/09/22, 11:25:57
Quote
What can aI do besides another install?

provide more info... you did not mention what window manager you are using...

if it is kde, try this : log out, move ~/.kde to ΒΈ/.kde_bak and log in again
Title: RE: Fresh install from firestarter: Problems with incomplete
Post by: spacepenguin on 2013/09/22, 13:43:05
If it's KDE try to use another window decoration than oxygen and try to disable the kwin effects.
Title: Fresh install from firestarter: Problems with incomplete win
Post by: der_bud on 2013/09/22, 15:29:37
mylo, someone in chat had exactly these symptoms several days ago on irc, fresh install of firestarter + big DU = same kde symptoms like you described.

In the end it was problems with correct nvidia driver and kernel-modules surviving that big dist-upgrade, because driver-names changed several times since firestarter-release.

As I have no nvidia myself I do not remember the exact solution, but it was similar to what is written for nvidia in the siduction-manual, but kind of translating the driver names from manual to the names they really have today, having the correct sources, not forgetting to unload the "faulty" module and so on.
Title: Fresh install from firestarter: Problems with incomplete win
Post by: michaa7 on 2013/09/22, 15:42:28
If this is true (I don't doubt it) I would

- save away /var/cache/apt/archives to a seperate partition (to avoid d/l 700 mb again)
- reinstall firestarter (I would *not* keep an installation which was messed up in its early hours of existence)
- after reinstall as the first action: mount <seperate archives partition) /var/cache/apt/archives
- d-u (including update to the newest kernel!)
- and only then I would install nividia (to avoid this nameing conflicts)
(I'd recommend to keep this seperate archives partition and mount it by making an appropriate entry in /etc/fstab)
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/22, 17:19:34
I did a reinstall, still no d-u'ing, everything seems to be proper.
How do i find out, what graphics driver has beeninstalled (nvidia 304 or 325 or nouveau)?

EDIT: dpkg -l shows no nvidia or nouveau.

So do I first d-u and then install 304-legaxy-xx and vdpau?
Or is an other sequence necessary?
Title: Fresh install from firestarter: Problems with incomplete win
Post by: dibl on 2013/09/22, 18:26:05
Yes, d-u first before you do anything with video drivers.

Are you sure you don't have the xserver-xorg-video-nouveau driver installed?

Do:

lspci | grep VGA

This will show the PCI bus address, for example it could be 05:00.0

Take the PCI bus address of your card, and put it in this command:

lspci -ks 05:00.0 | grep Kernel

the output will tell the driver in use.  (One of the bash / awk / sed gurus could make a script out of that ....).
Title: Fresh install from firestarter: Problems with incomplete win
Post by: absolut on 2013/09/22, 18:28:46
1) what window manager are you using?
2) please paste /var/log/Xorg.0.log
3) please paste output of dpkg -l | grep xserver
4) i'd first dist-upgrade, then install nvidia, then reboot

EDIT: fast hack of the things above...
lspci -ks $(lspci | awk '/VGA/ {print $1}') | grep Kernel
Title: Fresh install from firestarter: Problems with incomplete win
Post by: dibl on 2013/09/22, 18:38:31
Quote from: "absolut"

EDIT: fast hack of the things above...
lspci -ks $(lspci | awk '/VGA/ {print $1}') | grep Kernel


Nice -- I can only dream of such skills!   :P

Thanks absolut!
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/22, 22:07:46
# lspci -ks 01:00.0 | grep Kernel
       Kernel driver in use: nouveau


dpkg -l | grep xserver
ii  x11-xserver-utils                                    7.7~3                               amd64        X server utilities
ii  xserver-common                                       2:1.12.4-6                          all          common files used by various X servers
ii  xserver-xorg                                         1:7.7+3                             amd64        X.Org X server
ii  xserver-xorg-core                                    2:1.12.4-6                          amd64        Xorg X server - core server
ii  xserver-xorg-input-all                               1:7.7+3                             amd64        X.Org X server -- input driver metapackage
ii  xserver-xorg-input-evdev                             1:2.7.0-1+b1                        amd64        X.Org X server -- evdev input driver
ii  xserver-xorg-input-mouse                             1:1.7.2-3                           amd64        X.Org X server -- mouse input driver
ii  xserver-xorg-input-synaptics                         1.6.2-2                             amd64        Synaptics TouchPad driver for X.Org server
ii  xserver-xorg-input-vmmouse                           1:12.9.0-1                          amd64        X.Org X server -- VMMouse input driver to use with VMWare
ii  xserver-xorg-video-ati                               1:6.14.4-8                          amd64        X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev                             1:0.4.2-4+b3                        amd64        X.Org X server -- fbdev display driver
ii  xserver-xorg-video-intel                             2:2.19.0-6                          amd64        X.Org X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-mach64                            6.9.1-2                             amd64        X.Org X server -- ATI Mach64 display driver
ii  xserver-xorg-video-mga                               1:1.5.0-3                           amd64        X.Org X server -- MGA display driver
ii  xserver-xorg-video-nouveau                           1:1.0.1-5                           amd64        X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-qxl                               0.0.17-2+b1                         amd64        X.Org X server -- QXL display driver
ii  xserver-xorg-video-r128                              6.8.2-1                             amd64        X.Org X server -- ATI r128 display driver
ii  xserver-xorg-video-radeon                            1:6.14.4-8                          amd64        X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa                              1:2.3.1-1+b1                        amd64        X.Org X server -- VESA display driver
ii  xserver-xorg-video-vmware                            1:12.0.2-1+b1                       amd64        X.Org X server -- VMware display driver
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/22, 22:13:18
Quote from: "absolut"1) what window manager are you using?
2) please paste /var/log/Xorg.0.log
3) please paste output of dpkg -l | grep xserver
4) i'd first dist-upgrade, then install nvidia, then reboot

EDIT: fast hack of the things above...
lspci -ks $(lspci | awk '/VGA/ {print $1}') | grep Kernel

1) KDE
3) see below
2) http://paste.siduction.org/20130922202121
Title: Fresh install from firestarter: Problems with incomplete win
Post by: absolut on 2013/09/22, 23:01:02
nouveau is being loaded, it seems...

but the following line
[   481.024] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.9-3.towo-siduction-amd64 root=UUID=dc98e50b-f960-4ce9-9ec4-866fef79c8bf ro quiet 3 says that you do not boot into graphical environment, only into init 3... why?

at this point in time, i would go for a dist-upgrade and see what happens... then you can think about nvidia-glx driver
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/24, 21:59:36
Ok, I go for the d-u on this install again and then I follow:

apt-get install policy nvidia-legacy-304xx-driver  apt-cache policy nvidia-vdpau-driver

as per http://forum.siduction.org/index.php?topic=3801&postdays=0&postorder=asc&start=15

Is that ok?
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/24, 22:08:00
Wow the firestarter really has an own life as a vulcano. I am deeply impressed. I set the terminal to an unlimited no. of lines in order to be able to scroll back and review the d-u -s request.

Suddenly a mixture of init 5 and 3 appears (mouse indicator stays visible, while texe mode talks abou nouveau...
Title: Fresh install from firestarter: Problems with incomplete win
Post by: absolut on 2013/09/24, 23:12:09
random guess: maybe it is the xserver-xorg transition kicking our butts here?
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/25, 06:42:17
Have to check tonight...however it was before the d-u.
Title: Fresh install from firestarter: Problems with incomplete win
Post by: mylo on 2013/09/25, 22:17:23
Hi,

I checked the update now and have the problems again with the grizzling windows.

I installed firestarter from scratch and made the d-u after.
Everything ran fine except the result:

Please see

paste.siduction.org/20130925200444

paste.siduction.org/20130925200530

for grep on dpkg regarding xserver and nouveau.

My questions:

1) Can I proceeed on installing nvidia then (304xx nd vdpau)?
Does that skip the grizz windows?

2) Is it possible to install firestarter from scratch and come to a working inst with an nvidia card (or does this major upgrade kill any trial in any case)?
Why is the iso not updated to clear the upgarde path regarding nvidia (to skipping renaming prob). Do the experts want to stay alone?

3) What else can i do except a distro change??

I use sid now so long but cannot get running my box since two weeks now.
Really frustrating.