Jump to content

dude67

OTW
  • Posts

    1155
  • Joined

  • Last visited

Posts posted by dude67

  1. I'm not sure why it doesn't start the wicd daemon on boot? As a temp fix/hack you could add the line
    /etc/rc.d/init.d/wicd start

    to your /etc/rc.d/rc.local file. Let me know if that works for you?

    Thanks Greg, I did that and will let you know if it works.

  2. and then

    strace -o /home/dude67/wicddebug "python /opt/wicd/tray.py"

    The dump file ~wicddebug may get exhessively large, but it will contain ample information about your problem.

    OK, I've got strace already installed, but I get this:

    [root@localhost dude67]# strace -o /home/dude67/wicddebug "python /opt/wicd/tray.py"
     strace: python /opt/wicd/tray.py: command not found

    Is there something wrong with the /opt/wicd/tray.py file as it states something like "dapper" and "edgy". They suggest to have something to do with ubuntu. Anyway, this is how the file looks:

       #!/usr/bin/python
      import os,sys
      if __name__ == '__main__':
    	   os.chdir(os.path.dirname(os.path.normpath(os.path.join(os.getcwd(),sys.argv[0]))))
      import gtk
      if gtk.gtk_version[0] >= 2 and gtk.gtk_version[1] >= 10:
    	   import edgy
      else:
    	   import dapper

    I've gone through the (bloody long) system logs but haven't really figured out what the problem was. I did some hw changes and disabled the WLAN AP in the combined ADSL modem/WLAN AP and connected an extra Linksys WLAN AP into the modem by eth cable. It has been working for a week or so and has not dropped my connection once (knock on wood).

     

    I started to use wicd again today, so we'll soon know if these problems will be over or if they continue.

     

    I've therefore got a few questions:

     

    1)

    I still don't get wicd to start automatically, or it doesn't start properly as I always need to (re)start the service as I mentioned earlier

    # service wicd start
    								 Stopping any running daemons...
    								 Starting wicd daemon...
    								 /opt/wicd
    								 wicd daemon: pid 20101
    								 #

    What's with that; perhaps I should add the /opt/wicd/gui.py to the Autostart also as I did with the tray.py?

    2)

    And this autostart of tray.py does not work either.

    In a terminal as root do
    ln -s /opt/wicd/tray.py ~/.kde/Autostart/tray.py

    if you want it in your tray at startup.

    If I type it (/opt/wicd/tray.py) in Konsole as root it works, but that leaves the Konsole open with root privileges. If I exit it, it will also exit the tray. Any ideas how to fix it?

     

    Maybe it would autostart OK if the gui.py would start first (in autostart), eh?

     

    I also took Greg's advice and use "wext" as my WPA Supplicant driver. Works so far...

  3. OK, I've ran into a problem with this one (Scorpius: http://www.ione.com.tw/2005/products/media/htm/sc-p20.htm).

     

    Does anyone know how to make Grub respond to this USB/wireless KB/mouse thingy? I have (on my family room PC) a dual boot system with MDV Spring and WinXP Home. I've got Grub and there Mandriva Spring as a first choice. But I cannot choose Windows from Grub as it doesn't respond to the keybord at all.

     

    The initial boot (BIOS) does not respond to this thing (IOne Scorpius), but when I press DEL on my other KB and enter the BIOS settings I can make BIOS choises with Scorpius without any problems. I tried to find a setting which would allow the USB kb (or anything even sligthly resembling that choice), but couldn't.

     

    Currently I have two choices:

    1) to keep another kb always onsight (I hate that option)

    2) to always first boot to Linux and there reboot (from KDE) to windows (takes time to do that).

     

    I'm not particulary keen on either of the choices, so I'm asking the good folks here in MUB: does anyone know any remedy?

     

    - Edit -

    This is the HW setup:

    System # 2

    Display card: Club 3D radeon X700 Pro 256 MB PCI-e (ATI)

    Processor: Intel P4 HT 3.0 GHz

    Motherboard: ABIT AG8V 3rd eye

    Memory: 1024 Mb 400MHz DDR

    System: Dual boot with WinXP Home & Madriva 2007.0 Free

  4. I'll see what I can find in the messages. It's just that I'm not really sure what I'm looking for, but I will have a look and post back.

     

    I guess I could be looking for the parts where the system has restarted and trace back from there...

  5. When it crashes do you still have a working keyboard, so you could open another terminal? Also is it crashing with both the madwifi and ndiswrapper modules? Have you created the symlink for the tray.py?

     

    After you have started the wicd daemon and the gui.py, you can start the tray with

    /opt/wicd/tray.py

    When the system crashes it's not responding to anything! It does not respond to any keystroke nor to the mouse. My only option was to reboot with the reboot button in my PC (or pressing the power button for several seconds).

     

    I have done what you instructed here earlier - no other symlinks or anything else.

  6. When I said I got wicd to work, well, perhaps I spoke too soon. It seems to crash easily; I've now crashed the system three times and had to make hard boot (turn off the power) to recover from the crash.

     

    I'm trying to get some info about the crash, if anyone's interested. Where would be the best place to see what happened here?

  7. I'm glad it works for you, and thanks for testing it with Mandriva! :)

    Well, I'm still new to this, but as far as I can tell, it's working.

    The only thing is that I'm having trouble either with my PCI cards or with the WLAN AP (it's a combination of ADSL modem and a wireless AP). The connection has started to act up again lately and I'm not sure what's causing the problems. It worked for a long time w/o any problems, but now it keeps dropping me all the time. I need to configure the network over and over again to get it to come up again.

     

    I'm hoping that with wicd I can get more controls over the connection. But how can I tell if wicd is running? There's no icon in my system tray. If I say (as root) 'service wicd start', it doesn't give me any info. Just a new line in Konsole.

      [root@localhost dude67]#
    		 [root@localhost dude67]# service wicd status
    		 [root@localhost dude67]#

    But when I want to make sure it's running I do this:

    [root@localhost dude67]# service wicd start
    		 Stopping any running daemons...
    		 Starting wicd daemon...
    		 /opt/wicd
    		 wicd daemon: pid 14320
    		 [root@localhost dude67]#

    But, as I said, when it gets really bad, nothing else works than reconfiguring the network again (by RMB clicking the netapplet icon on my system tray) with the exact same parameters I'm running it always... I tried also ndiswrapper with Win drivers, but the same thing happened. By default I'm using madwifi.

     

    In a terminal as root do
    ln -s /opt/wicd/tray.py ~/.kde/Autostart/tray.py

    if you want it in your tray at startup.

     

    What wireless card do you have? Now that I know it works, I'll make an rpm. When Mandriva 2008 is released I'll install it with Xfce 4.4.1 on my laptop, and give wicd a try.

    I hava a Planet wireless PCI card which uses Atheros chipset and should work with madwifi or ndiswrapper. I'm getting sick of this system when it keeps dropping me, but at the moment I don't have a choice but to work with WLAN.

     

    This may be a little off-topic, but instead of wifi/wlan I may look into LAN that operates through regular electrical wiring. Something like this: http://www.dlink.com/products/?pid=533&sec=0

    Does anyone have any experience with these gadgets in Mandriva (or any other linux system)?

  8. Hey, thanks Greg2. I got it working!

     

    I was having hard time getting it running, but as root I had to do this to get it operating.

    [root@localhost dude67]# service wicd start
      Stopping any running daemons...
      Starting wicd daemon...
      /opt/wicd
      wicd daemon: pid 7407
      [root@localhost dude67]# /opt/wicd/gui.py
      attempting to connect daemon...
      success
      starting...

    I'm still not certain how to make sure it restarts when I reboot, but I'll know soon enough.

  9. Thanks Adam. I was googling around to find any info about the release date, but there was none available (at least couldn't find any updated).

     

    I realize the fact dexter11 commented and was merely asking if anyone has more info (Adam of course has inside info). I know how things go when you are working on a deadline. I work in a project environment myself and was not trying to add to the pressure. :unsure:

     

    I'm checking in regularly to Mdv download site for the 2008 release - I can hardly wait... B)

     

    Keep up the good work, guys. :thumbs:

  10. I'm also using Atheros chipset and have experienced some problems with it.

     

    Have you installed the madwifi module or the windows drivers with ndiswrapper?

     

    I'm currently using madwifi with my atheros chipsets and it's operating quite well. I too am sometimes faced with the problems you have described here and frankly I don't know the definite answer to your question.

     

    What I suggest is that you check that you have all the appropriate repos set up and see if there are any updates (in the non-free repos) for the madwifi module.

     

    I have many times just reconfigured my wireless connection to enable the wireless card in my PC. I most often just right-click the connection icon on the panel when it goes off-line and choose "configure network" (or something like that...). I go through the wireless settings and the system goes on-line again...

     

    I don't know what the reason for that is, but it usually does the trick for me.

     

    If there is a cure for this, I would also like to hear about it!

  11. Thanks.. This was the first thing I did when I wanted to install GTKPOD. It said package not found.

     

    Will rebuilding all my repos solve this? If so, how can I do that?

    Just make sure you have contrib repos configured. It's in there.

     

    	   [root@localhost dude67]# urpmi gtkpod
    
    	   ftp://mandrake.cict.fr/Mandrakelinux/official/2007.1/i586/media/contrib/release/gtkpod-0.99.9-0.20070207.1mdv2007.1.i586.rpm
       installing gtkpod-0.99.9-0.20070207.1mdv2007.1.i586.rpm from /var/cache/urpmi/rpms
       Preparing...					 #############################################
    		 1/1: gtkpod				#############################################
    
    	 [root@localhost dude67]#

    Have you set up your repos with easy-urpmi? (top of page here)

  12. Hi, dude67.

    For the xorg issue (and valid workarounds) please check THIS thread at the Archlinux forums. I do not really have a clue about the actual workaround, but it *might* be an "xorg" package group, or re-inserting an xorg dummy package. I will post back whenever this is implemented (which should be not more than 48 hours).

     

    scarecrow, I should perhaps have read this posting before I did my re-installation of Arch tonight. It may have helped at one point...

     

    As you know I cannot connect to internet without madwifi and madwifi wasn't in the installtion cd. So there was no updating the sources.

     

    For madwifi, I had brought the latest files with me in a USB flash. But there was another problem: I couldn't find a way to mount the USB flash memory... In the end I just tried installing Xorg, but wasn't able to do that either (as the Archlinux forum posting said). I couldn't start any wm.

     

    I couldn't install pretty much anything and was not even sure if I was doing the right things... I guess I would have needed more time with it, but that's the luxury I didn't have with this.

     

    So I'm afraid this time this distro will have to be waiting for "better times" as I finally took out the Xubuntu CD and installed it again. I'm going to take some time tomorrow to familiarize myself with it and hopefully I can install madwifi from USB. At least I saw that Xubuntu recognized the 4 GB USB flash I had inserted.

     

    Thank you all for your patience and help! :thumbs:

×
×
  • Create New...