i'm trying to install the Asix AX88772 USB-Ethernet Adapter
onto a toshiba satellite 4010cds running full install puppy 412
with kernel 2.6.21.7. i have added modules asix, usbnet and mii
via bootmanager so they are loaded by default. there is an asix.ko
in /lib/modules/2.6.21.7/kernel/drivers/usb/net.

a green light on the adapter indicates that it is alive.

the info in the readme says the driver needs to be compiled
but i am uncertain about how to follow the directions given.

a previous forum thread on this adapter was inconclusive;
the original poster dropped out.

thanks, mmLast edited by mmmrr on Fri 02 May 2014, 10:57; edited 2 times in total

That's unwise - your have forcibly loaded those modules, but it's far better to allow Puppy to automatically load the modules ...
however, it then becomes a question of whether your USB-ethernet adapter's USB device ID is recognised as compatible by Puppy's asix module. To find out, first run this command

Code:

cat /proc/bus/usb/devices

Amongst the results you will see the vendor and product ID's for your device listed. Write them down, or post here.
Now run this command -

Code:

modinfo asix

This will show you all USB device ID's recognised by the module. Hopefully your device will be listed. Let us know.

I'm out of town for the next 2 weeks, so it will take some time to determine if it's possible to compile the smsc75xx module for Puppy 4.1.x
In the meantime you could try the most recent Puppy version - Slacko 5.7 - get the non-PAE version.

thanks, i'll give slacko 5.7 a go;
see how this old pentium 2, 266 cpu manages.
release note:
'Slacko has been known to run on a P3 733MHz processor with 256MB RAM. Slacko does not support old P2 or AMD K6 processors.'
cheers, mm

slacko 5.7 boots, displays,
makes internet connection via
usb/smsc75xx module.
it is too slow to be useful.
i'll see what i can find abt
compiling for the 2.6.21.7
and post here if i do anything.
cheers, mm

Further investigation reveals that the smsc75xx driver was introduced only from the 2.6.34 kernel onwards, thus it's completely absent from all early Puppies up to, and including, Lucid 5.2.8.

You could try Lucid 5.2.9 (Three-headed Dog) - it definitely contains the driver.

Alternatively, stick with Puppy 4.1.x and change to a different USB-ethernet adaptor. Try to find one that's supported by either the asix, kaweth, or pegasus drivers - these drivers are all contained in the Puppy 4.1 series.

hello temptestuous,
both pup412 and pup431 were able to see and use
the dfx-690txd ethernet adapter. however, it took
about 10 times longer to load sites than the expansion
card wireless adapter [ndiswrapper] which i've been using.

the xload display when using the ethernet connection
showed one white line with red above and no white line
and red 1/3 when using the wireless connection.

both pup412 and pup431 were able to see and use the dfx-690txd ethernet adapter. however, it took about 10 times longer to load sites than the expansion card wireless adapter [ndiswrapper] which i've been using.

Then clearly there's a problem. It sounds like the 8139too driver is not playing well with your ethernet adaptor.
You can change the driver's behaviour by passing various parameters to it as it loads. The valid parameter in this case is "media=" and you want to force it to full-duplex mode, 100Mb/s. According to Google, this value should be "media=0x230". So do this -
Open /etc/modprobe.conf in Geany, and add this line:

using the wireless card, i read yr latest post.
thanks. r-clicking the connect icon i disconnected
from the network then inserted the ethernet card and
l-clicked the connect icon. as before the card is
seen and as before i had to set ip statically because
the auto dhcp gives a 169.254xx address which the
connection wizard says is good but the browser fails
to connect. i forgot to mention that. apologies.

i was puzzled as to how to save after entering code
'options ...' so before opening a terminal, while still
in connection wizard at the window showing card seen,
button for eth0, etc. i clicked 'load module' then on
next window 'more' which gave the window where i could
click 'specify' then enter the module name plus parameters.

entered '8139too media=0x230', clicked 'load'. that made no
difference to the speed. opened terminal:

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum