ZaZu

Each MDK version I've installed has installed two kernels, I think thats normal

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?

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

I've thought about this all day. My modem is external, and self configures with my provider. I then hook up with an ethernet card. (It's a toshiba) Who is your provider, and did they supply the modem?

<{POST_SNAPBACK}>

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

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!

"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..

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

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

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"

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...

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?"

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?

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

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 :

Mandrake Linux release 10.0 (official) for i586

Kernel 2.6.3-7mdk on a i686 / ttyl

localhost login:

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

Kernel panic: no init found

try passing init= option to kernel

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?

My NIC's driver is not listed by Mandrake 10.0 so I can't choose it but it is in the modules,drivers folder, how do I add it to the list so I can tell Mandrake to use it ?

Its called "idt77252.o.gz" the NIC is listed as idt77252...even though its a 3Com ADSL PCI lan/rfc1483 aka 3cp3617...I think the "idt77" etc is the controller chip

[moved from Software by spinynorman]

edit: Finally figured out the "module" is not included in the "Community" distibution

EDIT #2: Turns out theres no Linux drivers for my NIC (a 3Com ADSL PCI Adapter lan/rfc 1483 aka 3Com 3cp3617 ) :o

Mandrake 10.0 Community installed just fine on my 3rd hard drive (hdd) its got 14 GB to roam around in,

arranged as:

/boot - 100MB

/ - 4GB

/swap - 500MB

/home - 4GB

/usr - 4GB

/var - 1.6GB

I put the bootloader (Lilo) in hdd1(/boot)

My system spec's are:

Windows XP w/sp1 (all current updates)

AMD Athlon (Thunderbird) 1G - overclocked to 1.2G

Iwill KK266-R w/1GB ram

ATI All-In-Wonder 128 Pro (agp)

Seagate - 120GB - C: (NTFS)

Seagate - 75GB - G: (NTFS)

Quantum - 14GB -disk 2 (no drive letter)

Asus - CRW-4012a cd-rw drive - H:

The problem is in Control Center my nic is listed as "module:unknown"

its a 3com ADSL PCI modem lan/rfc1483(WinXP) adapter

however in Control Center its listed as: idt77252 atm adapter

I used Control Center install to search for a module and found the idt77252 is listed in

kernal- 2.4.25.2 mdk-1-1 mdk (and 4 other 2.4.25's) and kernal-2.6.3.4 mdk-1-1 mdk (and 3 other 2.6.3.4's)

Do I need to install one of these kernal's? I think I must have one already installed

Obviously I need that idt77252 module, how do I get it? how do I install it?

Please be verbose I'm very new to Linux and have no experience using the command line

Thanks in advance - ZaZu

I don't know how it works with Win98,but with WinXP I booted with the WinXP

disk,and when asked choose "r" for the recovery console typed "1" to chose drive c:, pressed "enter" because I don't use a password

then typed "fixboot" then "y" when asked to confirm

then typed "fixmbr" and again "y"to confirm then typed "exit" and rebooted

Thats what worked to restore the WinXP bootloader