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

ZaZu

Members
  • Content count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ZaZu

  • Rank
    New Here
  • Birthday 06/29/49

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Location
    @Home
  1. Two kernels by default

    Each MDK version I've installed has installed two kernels, I think thats normal
  2. Could someone that knows programming tell me what they are on about here: http://seclists.org/lists/linux-kernel/2004/Aug/0893.html I think they are saying there was(is?) a problem with ADSL modems using the idt77252 chipset and that that is the fix for it Is it likley that the "fix" if thats what it is is available?, where should I look for it?
  3. I'm only installing MDK to "check out this Linux I keep hearing about" its not important enough that I'd buy another ADSL modem from Bellsouth The ADSL modem has worked great under Windows over the past 3 years
  4. My ADSL modem is an internal PCI card it aparently has an intergral ethernet capability as I do not have a seperate ethernet card Bellsouth supplied the ADSL modem which is PPPOE it is a discontinued 3Com model 3cp3617 which uses a idt77252 chipset so MDK lists it as an idt77252 @nocturnes I've done all that its useless since the ADSL card is not being activated by MDK because the driver/module (idt77252.ko.gz) is not installed The driver/module is in the /lib/modules/~/drivers/atm folder I found this :http://seclists.org/lists/linux-kernel/2004/Aug/0893.html I' m not sure what to make of it, but it looks like their trying to solve or have solved the problem I'm having
  5. I'm done....I've done all I can think of to get MDK to load the driver for my ADSL card , even removed the card to see if MDK could be made to rediscover it as a ADSL modem not an ethernet card ...didn't work I guess me and Linux wasn't meant to be .... I'm done it beat me... No I'm not gonna buy another ADSL modem that MDK might support to replace the perfectly good one I already have PEACE!
  6. "Mandy" has not mis-identified the driver it is looking in the /lib/modules/~/drivers/net folder for a driver thats in the /lib/modules/~/drivers/atm folder The "let me choose a driver" bar that your refering to is the one that presents a list of ethernet drivers I need a atm driver edit: Do I need an ADSL modem for broadband or could I use an ethernet card just as well? re-edit: Just found the answer : Q. What are the requirements for ADSL modems compatible with AceDSL® service? A. G.DMT, RFC 1483 SNAP Bridge, LLC-Mux, VPI-0, VCI-35, Alcatel DSLAM compatible. I suppose that answer is universial..
  7. The card shows up correctly in MCC as idt77252 but is listed was "module: unknown" The module (idt77252.ko.gz) is in the /lib/modules/~/drivers/atm folder MDK only lists whats in the /lib/modules/~/drivers/net when asking what driver to use for the card I need to get MDK to offer the contents of /lib/modules/~/drivers/atm as the choice because the card is a ADSL modem not an ethernet NIC
  8. The correct driver is in the ATM modules folder ,MCC>Hardware>NIC only looks in the NET folder I need to figure out how to get MDK to look in the ATM folder where the ATM driver is
  9. Its looking at the list of drivers I think in the net folder,its where it looks when your setting up a NIC but my NIC needs a ATM module I don't know enough about MDK to know if I can "symlink"
  10. Is there anyway I could get MDK to look in the ATM modules folder for the ADSL driver? cause thats where it is MDK is looking in the NET folder, I put the driver in that folder then rebooted still nada.. I don't suppose theres something like in Windows where you choose where it looks and what for? Damn this is frustrating...
  11. Even if you make the driver theres no guaranty MDK will use it , my ADSL NIC's driver is in the ATM modules folder where it belongs and MDK won't even look for it there! So I can't use my ADSL with MDK...at least Windows would ask "where should I look,and for what?"
  12. When installing MDK10.0 I saw a notice that said that the free download version does not include some drivers for ADSL modems, I've been unsucsessful in getting MDK to install the driver/module for my NIC its a 3Com ADSL PCI lan/rfc1483 adapter aka 3Com 3cp3617, MDK lists it as idt77252 There is a idt77252.ko.gz in the modules section but I can't install it After unzipping it I tried insmod which says there are unknown symbols in it the output from dmesg says: idt77252: Unknown symbol atm_pcr_goal idt77252: Unknown symbol suni_init idt77252: Unknown symbol atm_dev_deregister idt77252: Unknown symbol atm_dev_register idt77252: Unknown symbol atm_charge modprobe just says module not found Could this module be corrupt? Could the module I need be on the commercial version?
  13. Thanks MadDOG, but it was so f$!&ed up I had to reinstall MDK 10.0....I'm not giving up though,I will get MDK to work with my ADSL no matter how many times I have to "break" it
  14. Been banging away at MDK 10.0 trying to get it to use my ADSL modem (it can see it and has the driver ) I must have told MDK that I don't want a graphical login cause now it presents me with : I can login but I don't know enough about command line usage to get to KDE or GNOME could someone tell me what I should type in to fix this? When I use my boot floppy it stops at
  15. I copied idt77252.ko.gz into my temp dir so as not to risk damaging the original "insmod" returns: [root@localhost tmp]# insmod idt77252.ko.gz insmod: error inserting 'idt77252.ko.gz': -1 Invalid module format and after I un'gzip' it [root@localhost tmp]# insmod idt77252.ko insmod: error inserting 'idt77252.ko': -1 Unknown symbol in module "modprobe" can't even see it: [root@localhost net]# modprobe idt77252.ko.gz FATAL: Module idt77252.ko.gz not found. [root@localhost tmp]# modprobe idt77252.ko FATAL: Module idt77252.ko not found. I'm thinking this module is corrupt,or am I doing something wrong?
×