Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here

beesea

Members
  • Content count

    219
  • Joined

  • Last visited

Community Reputation

0 Neutral

About beesea

  • Rank
    frequent
  1. gentoo-dev-sources are my favorite. You might wanna check out ck-sources too, they're pretty nice
  2. disabling supermount

    magicdev auto mounts cdroms, but i think its a gnome app. anyways, check to see if magicdev if running
  3. disabling supermount

    Actually, hotplug support is probably already in the kernel. Just make sure that you have the hotplug service enabled. Go to mandrake control center -> system -> services
  4. Xine or mplayer?

    totem (it uses a xine backend)
  5. No Graphical Interface

    Try typing "startx" when you log in and tell us what happens
  6. Firefox

    2 words: adblock extension
  7. magicdev for xfce

    Actually, in this case I think it might be. Gnome and kde have there own respective applications for auto-mounting cd's (in gnome's case its called magicdev). In order for these apps to work correctly, the fstab entry for a cdrom should normal (ie not setup for supermount). After checking my own /etc/fstab, which I haven't touched, this seems to be true. This means that WMs/DEs other than kde or gnome won't auto mount cdroms. Frederick, I think the way to get magicdev for xfce working is to have it start when xfce starts. Alternatively, you could edit your fstab to change your cdrom to use supermount. If you're feeling extra adventurous, you could try automatic mounting with something like ivman
  8. booting past hardware detection...

    I think if you disable the harddrake service you should be ok
  9. I don't think anything done here is kernel-specific so it should work for a 2.4 kernel, but I'm not completely sure
  10. If you're having issues with a particular part of my guide I'd be glad to help, just let me know what the problem is.
  11. nope, i use 128-bit encryption myself
  12. Intro I had a terrible experience finding info on how to set up ndiswrapper to work with my WMP54G card, but after a few days I finally figured it out and decided to post about it. Hopefully someone will find this useful. YMMV, but it should work with any card supported by ndiswrapper Procedure You're going to need to add two lines to /etc/modprobe.conf. Here are the lines I added: alias wlan0 ndiswrapper install ndiswrapper /sbin/modprobe --ignore-install ndiswrapper && { loadndisdriver 14e4 4320 /etc/ndiswrapper/bcmwl5.sys /etc/ndiswrapper/bcmwl5.inf; } The part that gave me the most headaches is the area between the curly braces. As you can see loadndisdriver takes four arguments: # loadndisdriver --help Usage: loadndisdriver [OPTIONS] pci_vendor pci_device windowsdriver.sys windowsdriver.inf Here's how I got the arguments: First, you'll need the windows driver for your card so grab the .sys and the .inf files from your card's CD (or where ever the drivers are). For my card they were called bcmwl5.sys and bcmwl5.inf. It doesn't really matter where you put these files. I put them in /etc/ndiswrapper. These are the last two arguments to loadndisdriver. To find pci_vendor and pci_device you need to run the lspci command. Here's what mine looks like: # lspci 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24) 00:0e.0 Multimedia video controller: Zoran Corporation ZR36120 (rev 03) 00:0f.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03) <=== My wireless card 00:10.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) Notice the numbers at the beginning of the line for your card (00:0f.0 for mine), and then run lspci -n: # lspci -n 00:00.0 Class 0600: 8086:7190 (rev 02) 00:01.0 Class 0604: 8086:7191 (rev 02) 00:07.0 Class 0601: 8086:7110 (rev 02) 00:07.1 Class 0101: 8086:7111 (rev 01) 00:07.2 Class 0c03: 8086:7112 (rev 01) 00:07.3 Class 0680: 8086:7113 (rev 02) 00:0d.0 Class 0200: 10b7:9055 (rev 24) 00:0e.0 Class 0400: 11de:6120 (rev 03) 00:0f.0 Class 0280: 14e4:4320 (rev 03) <=== My wireless card 00:10.0 Class 0401: 12eb:0001 (rev 02) 01:00.0 Class 0300: 10de:002d (rev 15) Match up the numbers you found earlier to locate your card. The numbers i'm looking for in my example are 14e4:4320. 14e4 is pci_vendor argument of loadndisdriver and 4320 is the pci_device argument To test this out install the ndiswrapper module: # modprobe ndiswrapper If there were no error messages, so far so good. If the command "iwconfig" (part of the wireless-tools package) recognizes wlan0 and doesn't say "no wireless extensions" then everything installed correctly. Now you can use iwconfig to setup the access point, essid, etc. See the man page for iwconfig for more info. Here's how I would start my internet manually: iwconfig wlan0 mode Managed iwconfig wlan0 key restricted XXXXXXXX iwconfig wlan0 essid ZZZZ dhcpcd wlan0 Just replace the X's with your key if you use WEP (you do use WEP, right? :D) and replace the Z's with the name of your access point. Now you're probably going to want to start all this up automatically. You need to create a file called /etc/sysconfig/network-scripts/ifcfg-wlan0 and put this in it: DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=yes ESSID=YOUR_ESSID MODE=Managed KEY="YOUR_KEY" Have a look at the /etc/sysconfig/network-scripts/ifup-wireless script to see what variables you can put in this file. Now all you have to do is reboot and see if your internet comes up. Conclusion I hope that someone can find this useful. Of course is anything here is wrong or if there's an easier way, then by all means do tell!
  13. rc-update add alsasound boot just in case you still haven't figured it out
  14. So, since Gnome 2.6 will be out the 31 March...

    Oops, my mistake :P
  15. So, since Gnome 2.6 will be out the 31 March...

    The way I understand it final edition is only supposed to have bugs fixes and security updates, so 2.6 won't be in final since its not already in CE
×