home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.mandriva      Somewhat decent but also getting bloated      29,919 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 29,051 of 29,919   
   Moe Trin to All   
   Re: OT: Off-Topic   
   19 Feb 13 20:01:56   
   
   From: ibuprofin@painkiller.example.tld.invalid   
      
   On Tue, 19 Feb 2013, in the Usenet newsgroup alt.os.linux.mandriva, in article   
   , TJ wrote:   
      
   >Adam wrote:   
      
   >> TJ wrote:   
      
   >>> Update on my struggles with wireless and Mageia 2: Still testing,   
   >>> but I seem to have solved my connectivity problem by blacklisting   
   >>> the driver supplied with the kernel and installing the latest   
   >>> driver from Realtek.   
      
   >> So apparently another factor (in addition to the distro) is the   
   >> wireless card/chip/adapter and therefore what driver will be needed.   
   >> I hadn't thought of trying a different driver.   
      
   This was the point I was trying to make   
      
   >> "eris" (2007 desktop) is now my test system, with a cheap but   
   >> adequate PCI WiFi card I got from eBay.  Getting wireless configured   
   >> for each distro on it (same hardware, obviously) has ranged from   
   >> trivial to "not yet".  Maybe some of them aren't using the correct   
   >> driver.   
      
   >Depends on the kernel, I think.   
      
   Basically, yes.   We had the same problems in the early days of Linux   
   trying to get Ethernet cards running. Today, it generally works with   
   no effort, but look at the Ethernet-HOWTO and see the grief we used   
   to go through.  ("Does that take the ''sundance'' or ''tulip'' or   
   ''yellowfin'' driver?")   
      
   >Mageia 1, using a 2.x kernel I believe, worked fine with my dongle   
   >using the driver and firmware available from the repositories. Mageia   
   >2, on the other hand, using a 3.x kernel, never did work right until   
   >I used the driver from the chipmaker.   
      
   Looking at the boot logs and dmesg output immediately upon booting,   
   and looking at the output of lsmod and/or 'cat /proc/modules' may let   
   you see which module each distribution is attempting to use to talk to   
   the hardware.  My question was basically "is everyone using the same   
   one?".     Maybe, maybe not.   
      
   >I've heard that some users have had mixed results with the open source   
   >firmware and drivers and Mageia 2.   
      
   I think it's more the old saw "if it works, don't fix it".   ;-)   
      
           Old guy   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca