Anyone has Debian 3.0 R2 ?

After getting my xserver, I try to log on into kde, in the middle of starting up the screen blacks out then goes back to the log-in screen.

After searching the internet for answers, I try with out GLcore and Dri, but then instead of blacking out I get static that scroll upward. Note this only happens with kde, I’m able to use gnome just fine so it must be something with the kde2 build. Anyone know how to fix this with out internet ?

I was running Testing for some time, only recently upgraded to Unstable. kde has always worked for me just fine. the information you provice here isn’t quite enough to figure out what is the problem, but probably something in the kde startup script that doesn’t go as it should, thats why it throws you back in login. maybe something missing, maybe something broken.

you mention kde2, is that really so? that is quite old version…

what you could do is to launch x without any login manager, (just do xinit in console), or from login manager just choose the option of doing failsafe, or what it’s called… so that you end up with just single xterm window.
then try to run kde manually with “startkde”, so you see will see all the messages what is happening, and let me know what are the last errors you get.

.b

Ok, will do.

Here’s part of the log, hope it’s enough

Total Memory: 256 64Kb banks (16M)
(–) VESA(0): Virtual size is 800x600 (pitch 800)
() VESA(0): Default mode “800x600”
(
) VESA(0): Using “Shadow Framebuffer”
(II) Loading sub module “shadow”
(II) LoadModule: “shadow”
(II) Loading /usr/X11R6/lib/modules/libshadow.a
(II) Module shadow: vendor=“The XFree86 Project”
compiled for 4.1.0.1, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.1
(II) Loading sub module “fb”
(II) LoadModule: “fb”
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor=“The XFree86 Project”
compiled for 4.1.0.1, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.1
(II) do I need RAC? No, I don’t.
(II) resource ranges after preInit:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MXB
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B]E
[6] -1 0 0xf7ffc000 - 0xf7ffffff (0x4000) MXB
[7] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MXB
[8] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[9] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[10] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[11] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[12] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[13] -1 0 0x0000ff00 - 0x0000ff7f (0x80) IX[B]E
[14] -1 0 0x0000fff0 - 0x0000ffff (0x10) IX[B]E
[15] -1 0 0x00007800 - 0x000078ff (0x100) IXB
[16] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[17] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
virtual address = 0x40262000 - physical address = 0xf0000000 - size = 16777216
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
() Option “dpms”
(
) VESA(0): DPMS enabled
(WW) VESA(0): Option “UseFBDev” is not used
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
PEXExtensionInit: Couldn’t open default PEX font file Roman_M
(II) Keyboard “Generic Keyboard” handled by legacy driver
() Option “Protocol” “PS/2”
(
) Configured Mouse: Protocol: “PS/2”
() Option “CorePointer”
(
) Configured Mouse: Core Pointer
() Option “Device” “/dev/psaux”
(==) Configured Mouse: Buttons: 3
(
) Option “Emulate3Buttons” “true”
() Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(
) Option “ZAxisMapping” “4 5”
() Configured Mouse: ZAxisMapping: buttons 4 and 5
(
) Option “Protocol” “ImPS/2”
() Generic Mouse: Protocol: “ImPS/2”
(
) Option “SendCoreEvents” “true”
() Generic Mouse: always reports core events
(
) Option “Device” “/dev/input/mice”
(EE) xf86OpenSerial: Cannot open device /dev/input/mice
No such device.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device “Generic Mouse”
(II) UnloadModule: “mouse”
(II) XINPUT: Adding extended input device “Configured Mouse” (type: MOUSE)
SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0
SetKbdSettings - Succeeded

:slight_smile:

well this happens to be your xserver log, but I understood your X is actually running just fine, its kde that doesnt work… so I wanted to see the log “startkde” command outputs.

anyway, now that I see this log, I am wondering a bit your mouse setup. there is missing /dev/input/mice, and “Generic Mouse” doesnt load… but thats alright I guess since the other mouse, “Configured Mouse” loads. :slight_smile:

anyways, if you can drop me the startkde output too… thanks.

.b

There is no startkde log, there’s a kdm.log however, is that the one ?

no, there is no startkde log, but if you start kde by typing that “startkde” in xterm window, you get the printout in there. thats what I need :slight_smile:

if you ever use irc, get into the freenode network and just open a query on me… nickname ‘basse’. maybe conversation goes faster :slight_smile:

.b

It blacks out on kdestart and send me to the login screen again, not able to see anything that is printed out.

and you started kde with command “startkde” ?

.b

Yup, xinit brings me into X and then type startkde, starts up like kde should, then looks at right in the middle of setting up, it blanks out, I think it’s when it looks at the screen or something, display, whatever, you know, those kde icons during start up.

Never happens in Gnome.

but it then kills your whole X?

.b

Yes, but sometimes it sends me back to the debian login screen.

maybe you could do this:

startkde &>/tmp/kde.log

and then you end up having log file in your tmp dir… try it.

.b

Here it is.

DCOPServer up and running.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
KLauncher: Exiting on signal 1
kdeinit: sending SIGTERM to children.
kdeinit: Exit.

shit doesnt really tell anything. something has IO error and that’s it.

well, as we have no real clues what is it that brings the problem, my suggestion is simply to upgrade KDE, there are more recent (much nicer) versions out anyway.

.b

What good is linux if it doesn’t work ?

It does say broken pipe and xbin can’t be found.