D-Link AirPlus G wireless card won't work

[Mr. Maxwell]

Got some bad news. It still did not work after nukeing the hard drive and the RAM is 2 32MB chips not 1 64MB chips, so I would have to replace both to upgrade.

I'll try cleaning the RAM.

[rjbrewer]

Actually, the 2 pieces of ram don't have to match in size.

[Mr. Maxwell]

Some good and bad news.

The good: I was able to install puppy 4.1.2 to the computer.
The bad: after the install I restarted the computer without the cd in it and I got to here:

Code: Select all

Unlazmaing Linux... done.
Booting the kernel.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

then it hung.

[rjbrewer]

Good ol' kernel panic; remember him well.

Usually meant I forgot to do something.

Did you install grub to the mbr?
Create a partition with Gparted and set boot flag?
Set disk label when creating partition?

If yes to all above insert cd, boot up, click on sda1 or where ever
the install is, and find the boot, grub , menu list and write the 3 or for
lines in the next post.

[Mr. Maxwell]

I am going to nuke the hard drive one more time and pray I can get the Live CD to boot up one more time.

[rjbrewer]

Forgot to mention;

Make a 200 to 300 mb swap partition.
Resize your existing partition to accomodate if you don't want to start over.

The smallest amount of ram on old gear that Barry used while
developing the 4.1+ series was 128.

There are a few puppy derivatives below 64 mb ram that might work.

Damn Small Linux would probably load; but it's based on a 2.4 series
kernel, which may give you some hardware (wifi) problems.

[Mr. Maxwell]

If I nuke the hard drive I am able to boot off the live cd, not sure if that is good or bad.

Does the swap partition act like virtual memory?

Reformating the hard drive as I type this. Lets see if I can get it to work.

[rjbrewer]

Yea;

virtual memory...a piece of the hard drive dedicated to compensate for a lack of ram. Slow but necessary if you have less than 300-500 megs
ram with puppy.

[tempestuous]

Mr. Maxwell,
in the interests of accurate information dissemination on the forum, it's worth mentioning that this discussion has moved way beyond your original query about a D-Link DWL-G630 wifi adaptor, and the thread topic is no longer representative of the discussion.

It's also worth noting that your original problem does not relate to the Cardbus wifi device, but to the cardbus interface, itself.

[Mr. Maxwell]

Well I just got puppy to work and now need to get the wireless working so were back on topic. When I type lsmod at the console it does not come up with the yenta_socket module as loaded. How would I go about fixing this?

Is this now considered on-topic?

[rerwin]

Mr. Maxwell,
Thanks for hanging in there to get 4.1.2 running. The absence of yenta_socket concerns me. Apparently the reworked cardbus detection does not find the O2 Micro controller. So, my previous suggestions still apply.

Use the BootManager to force loading of yenta_socket. You need a pupsave before BootManager will let you do that. Try that alone first, but if a reboot doesn't find the G630, then also force loading of ath_pci.
Richard.

[Mr. Maxwell]

The interface scanner still finds the cardbus controller but can't find the wireless card. I set the boot-loader to load yenta_socket at startup and when I restarted the computer it said

Code: Select all

Loading user-selected modules... yenta_socket

But that still did not find the card. Then I opened up the console and typed

Code: Select all

lsmod

and it did not say yenta_socket was loaded. So I typed

Code: Select all

modprobe yenta_socket

and got this error message:

Code: Select all

WARNING: Could not open '/lib/modules/2.6.25.16/kernel/drivers/pcmcia/rsrc_nonstatic.ko': No such file or directory
FATAL: Could not open '/lib/modules/2.6.25.16/kernel/drivers/pcmcia/yenta_socket.ko': No such file or directory

After that I opened the hard drive and navagated to the directory in the error message and found these four files:

i82092.ko
i82365.ko
pd6729.ko
tcic.ko

No yenta_socket.ko or rsrc_nonstatic.ko. I'm guessing I need to download these files from somewhere?

[rjbrewer]

Mr.Maxwell;

I don't have the yenta or rsrc files and have an atheros card that
works fine.
I think rerwin of tempestuous probably have the answer to this.

rjb

[Mr. Maxwell]

After doing a file search I found that this directory:

/lib/modules/2.6.25.16/initrd/kernel/drivers/pcmcia/

has these files:

rsrc_nonstatic.ko.gz
yenta_socket.ko.gz

Should I extract them to the folder they are supposed to be in?

[rjbrewer]

My card is pci, not card bus; doesn't need yenta or rscr.

I would wait for rerwin to show up as he is trying to diagnose
the loading problem for your card type.

[Mr. Maxwell]

Ok I'll stand-by.

[rjbrewer]

I found those same files.
Makes me wonder if using full install as you and I do, fails to put
the files in the correct place.

[rjbrewer]

Nope;

Exact same thing with live cd-save file.

[Mr. Maxwell]

It sounds like a bug to me.

[Mr. Maxwell]

I copyed the two compressed files to where they are supposed to be and uncompressed them. Typed 'modprobe yenta_socket' and the light on the wireless card came on.

I'll try to set up the internet.