Find the answer to your Linux question:
Results 1 to 5 of 5
Have been trialing Linux distros for a month or so now and am on my fifth with the Mandriva 2007. Been something of a breeze installing although as usual the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Oct 2006
    Posts
    5

    kde su login wierdness - Mandriva Free 2007


    Have been trialing Linux distros for a month or so now and am on my fifth with the Mandriva 2007. Been something of a breeze installing although as usual the USB ADSL modem was an absolute blister to configure. Like several other distros looks like being a serious competitor to MS. However hit some profoundly weird behaviour logging in as root in order to configure the computer. The kde su login as root dialog ran then I entered the password then hit the enter key. The asterisks went wild across the input box and then nothing. Decided to reboot and try again but the start up menu would just keep bringing the kde su box up again. Right-clicked on the desktop and logged out and rebooted that way. Everything looks fine again. So tried to log in again to configure the computer but the kde su cursor doesn't do anything now no matter what I key in. Also the start up menu is flickering and I can't access any programs - have to log out again via right-clicking on the desktop. Found a workaround by using the local drake (system) log on which gave me access to the configure the computer stuff (I have to access the configure the computer in order to run an internet connection for the adsl modem).

    My first thought is a virus but on a four day old Linux installation?

    Would appreciate any input whatsoever on this one.

    Also have not been able to find the anti-virus software whilst I belatedly noticed that the firewall was not running on the pppo interface. Worrying. Don't want to have to do reinstall if I can help it.

  2. #2
    Linux Guru fingal's Avatar
    Join Date
    Jul 2003
    Location
    Birmingham - UK
    Posts
    1,539
    Hello Don Quixote

    It might be a typical Mandriva bug ... possibly as the result of installing a driver for your modem, though I have no way of knowing that absolutely. If you can get to a command line, log in as root and check out /var/log ... This is just generic guidance which may show something up:

    cd /var/log
    su
    <enter_password>

    tail -50 Xorg.0.log (your Xorg log might have a different name)
    tail -50 messages
    tail -50 dmesg

    Try listing everything in that directory like so: ls -al and see if you can find anymore useful log files. The tail command can be varied, and all I've done is suggest that you get output from the last 50 lines of the log. This is arbitrary and you could list 100 or whatever.

    This is very unlikely to be a virus. On the whole, they don't happen. You might try downloading Rootkit Hunter and running it from the command line in report mode: http://www.rootkit.nl It's not too hard to use with practice and it's very useful. I prefer it to a fully versioned virus checker in fact.

    - fingal
    I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso

  3. #3
    Just Joined!
    Join Date
    Oct 2006
    Posts
    5
    Hi fingal
    Thanks for replying!

    Seems to have got worse as now the LocalDrake login isn't accepting any keying in either.
    But (this is a big but) after ending the session and logging back in again the kde su now accepts keying in.
    The following is the output from running the Xorg.0.log. There are several other logs too including an Xorg.1 and Xorg.9. This is the log after killing the first session and logging back in. I don't think the modem driver is the issue as the system was booted several times without a problem. The trouble with the USB modem (Sagem fast 800) is the latest ueagle-atm driver that seems to want to use my eth0 (network card for my lan) interface rather than bring up another (eth1) interface. It runs the pppo over eth0 which means my windows machine cant see the linux but the linux can see the windows! I have manged to get windows to see the Linux PC but then I can't establish an internet connection. Have been toying with trying to configure the Mandriva as a firewall/router and running dhcp server - currently it is manually configured with static ip address (there are only two machines with two NICs). Given the trouble this modem has caused me under Linux I am currently saving up for a router/adsl solution and that problem at least should finally disappear.
    Perhaps you can spot something 'sinister' in the following:


    Password:
    [root@localhost log]# tail -50 Xorg.0.log
    (EE) AIGLX: Screen 0 is not DRI capable
    (II) Loading local sub module "GLcore"
    (II) LoadModule: "GLcore"
    (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
    (II) Module GLcore: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) GLX: Initialized MESA-PROXY GL provider for screen 0
    (**) Option "CoreKeyboard"
    (**) Keyboard1: Core Keyboard
    (**) Option "Protocol" "standard"
    (**) Keyboard1: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard1: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard1: XkbModel: "pc105"
    (**) Option "XkbLayout" "gb"
    (**) Keyboard1: XkbLayout: "gb"
    (**) Option "XkbOptions" "compose:rwin"
    (**) Keyboard1: XkbOptions: "compose:rwin"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard1: CustomKeycodes disabled
    (**) Option "Protocol" "ExplorerPS/2"
    (**) Mouse1: Device: "/dev/mouse"
    (**) Mouse1: Protocol: "ExplorerPS/2"
    (**) Option "CorePointer"
    (**) Mouse1: Core Pointer
    (**) Option "Device" "/dev/mouse"
    (==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
    (**) Mouse1: ZAxisMapping: buttons 4 and 5
    (**) Mouse1: Buttons: 9
    (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
    (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
    (II) Mouse1: ps2EnableDataReporting: succeeded
    (II) Open ACPI successful (/var/run/acpid.socket)
    (II) APM registered successfully
    (==) MGA(0): Write-combining range (0xd4000000,0x400000)
    (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (==) MGA(0): Default visual is TrueColor
    (EE) MGA(0): Static buffer allocation failed, not initializing the DRI
    (EE) MGA(0): Need at least 9216 kB video memory at this resolution, bit depth
    (II) MGA(0): Using 255 lines for offscreen memory.
    (**) MGA(0): DPMS enabled
    (II) MGA(0): Using overlay video
    (WW) MGA(0): Direct rendering disabled
    (==) RandR enabled
    (EE) AIGLX: Screen 0 is not DRI capable
    (II) GLX: Initialized MESA-PROXY GL provider for screen 0
    (II) Mouse1: ps2EnableDataReporting: succeeded
    [root@localhost log]# tail -50 messages
    Oct 28 18:53:50 localhost mdkapplet[3541]: Connecting to ...
    Oct 28 18:54:20 localhost drakconf.real[3633]: ### Program is starting ###
    Oct 28 18:54:31 localhost mdkapplet[3541]: ### Program is exiting ###
    Oct 28 18:54:35 localhost drakconf.real[3647]: ### Program is starting ###
    Oct 28 18:54:38 localhost localedrake[3654]: ### Program is starting ###
    Oct 28 18:54:44 localhost localedrake[3654]: ### Program is exiting ###
    Oct 28 18:55:36 localhost drakconnect[3657]: ### Program is starting ###
    Oct 28 18:55:44 localhost drakconnect[3657]: Found settings for driver "ueagle-atm" in category "network::connection:dsl"
    Oct 28 18:55:45 localhost drakconnect[3657]: No kernel_module package for module "ueagle-atm" is required, skipping
    Oct 28 18:55:45 localhost drakconnect[3657]: No tools package for module "ueagle-atm" is required, skipping
    Oct 28 18:55:45 localhost drakconnect[3657]: Required firmware package for module "ueagle-atm" is already installed, skipping
    Oct 28 18:55:45 localhost drakconnect[3657]: Settings for driver "ueagle-atm" applied
    Oct 28 18:56:02 localhost drakconnect[3657]: running: /bin/rpm -q --qf %{name} ppp-pppoatm
    Oct 28 18:56:02 localhost drakconnect[3657]: modified file /etc/ppp/pap-secrets
    Oct 28 18:56:02 localhost drakconnect[3657]: modified file /etc/ppp/chap-secrets
    Oct 28 18:56:02 localhost drakconnect[3657]: modified file /etc/sysconfig/network-scripts/ifcfg-ppp0
    Oct 28 18:56:02 localhost drakconnect[3657]: modified file /etc/sysconfig/network-scripts/ifcfg-ppp0
    Oct 28 18:56:03 localhost drakconnect[3657]: changed mode of /etc/sysconfig/network-scripts/ifcfg-ppp0 to 755
    Oct 28 18:56:03 localhost drakconnect[3657]: written ppp0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-ppp0
    Oct 28 18:56:03 localhost drakconnect[3657]: running: /sbin/ifdown ppp0 daemon
    Oct 28 18:56:03 localhost drakconnect[3657]: running: /sbin/ifup ppp0 daemon
    Oct 28 18:56:03 localhost kernel: CSLIP: code copyright 1989 Regents of the University of California
    Oct 28 18:56:03 localhost kernel: PPP generic driver version 2.4.2
    Oct 28 18:56:03 localhost ifup-ppp: pppd started for ppp0 on at
    Oct 28 18:56:03 localhost pppd[3688]: Plugin pppoatm.so loaded.
    Oct 28 18:56:03 localhost pppd[3688]: PPPoATM plugin_init
    Oct 28 18:56:03 localhost pppd[3688]: PPPoATM setdevname_pppoatm - SUCCESS:0.38
    Oct 28 18:56:03 localhost pppd[3688]: pppd 2.4.3 started by root, uid 0
    Oct 28 18:56:03 localhost pppd[3688]: Using interface ppp0
    Oct 28 18:56:03 localhost pppd[3688]: Connect: ppp0 <--> 0.38
    Oct 28 18:56:03 localhost pppd[3688]: CHAP authentication succeeded
    Oct 28 18:56:04 localhost pppd[3688]: local IP address 80.47.41.24
    Oct 28 18:56:04 localhost pppd[3688]: remote IP address 212.74.111.218
    Oct 28 18:56:04 localhost pppd[3688]: primary DNS address 212.139.132.7
    Oct 28 18:56:04 localhost pppd[3688]: secondary DNS address 212.139.132.6
    Oct 28 18:56:04 localhost NET[3777]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
    Oct 28 18:56:21 localhost drakconnect[3657]: modified file /etc/modprobe.conf
    Oct 28 18:56:21 localhost drakconnect[3657]: running: dmidecode
    Oct 28 18:56:21 localhost drakconnect[3657]: to put in /etc/modules
    Oct 28 18:56:21 localhost drakconnect[3657]: modified file /etc/modules
    Oct 28 18:56:21 localhost drakconnect[3657]: to put in /etc/modprobe.preload via-agp
    Oct 28 18:56:21 localhost drakconnect[3657]: modified file /etc/modprobe.preload
    Oct 28 18:56:21 localhost drakconnect[3657]: ### Program is exiting ###
    Oct 28 18:56:38 localhost drakconf.real[3647]: modified file /etc/mcc.conf
    Oct 28 19:01:01 localhost crond[3857]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
    Oct 28 19:01:02 localhost msec: set variable SystemMenu to true in /etc/X11/gdm/gdm.conf
    Oct 28 19:01:02 localhost msec: changed mode of /var/log/wtmp from 664 to 640
    Oct 28 19:01:02 localhost msec: changed group of /var/log/wtmp from utmp to adm
    Oct 28 19:01:02 localhost msec: changed mode of /var/log/Xorg.0.log from 644 to 640
    Oct 28 19:01:02 localhost msec: changed group of /var/log/Xorg.0.log from root to adm
    [root@localhost log]#

    cheers
    Don

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Oct 2006
    Posts
    5

    forgot to mention

    I forgot to say that I didn't exactly install a driver for the usb modem. The Mandriva free version doesn't supply the firmware but otherwise supports the modem. I happened to have the ueagle-atm firmware from previous Linux installations and simply copied it over to the firmware folder.
    cheers again
    Don

  6. #5
    Linux Guru fingal's Avatar
    Join Date
    Jul 2003
    Location
    Birmingham - UK
    Posts
    1,539
    Hmmm not many clues there. I wonder what make of video card you're using, and which driver? It might be a video/display issue of some kind given the flickering you mentioned. Having said that I note the line:

    'AIGLX: Screen 0 is not DRI capable '

    and also I see that:

    '(WW) MGA(0): Direct rendering disabled'

    so for a guess you're not using any fancy video drivers. You might want to use one which enables these features if possible. If you're using an ATI card this can be a problem. In your /etc/X11 directory is a file called xorg.conf . I would check to see that the vertical and horizontal refresh rates are right for your monitor. That's all I can think of atm.

    You can configure your card in the Mandriva Control Centre.

    - fingal
    I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •