VIA Velocity VT6122 Gigabit LAN WORKING!

What works, and doesn't, for you. Be specific, and please include Puppy version.
Post Reply
Message
Author
Rider1
Posts: 8
Joined: Tue 03 Oct 2006, 20:10
Location: Philadelphia, PA

VIA Velocity VT6122 Gigabit LAN WORKING!

#1 Post by Rider1 »

I am posting the solution to this configuration problem in Hardware although the thread began in Beginners Help.

http://www.murga.org/%7Epuppy/viewtopic.php?t=11488

Extract the via-velocity.ko module from the all-modules-k2.6.16.7-PUP202.tar.gz package at http://www.puppyos.com/test/

Copy the module into /lib/modules/2.6.16.7/net/

To the end of /etc/rc.d/rc.local add these lines:

insmod /lib/modules/2.6.16.7/lib/crc-ccitt.ko
insmod /lib/modules/2.6.16.7/net/via-velocity.ko

Reboot the computer.

Then Run the Puppy_Network_Setup Wizard.

I found that the configuration would not save for the next boot for me,
(Running Mean Puppy 2.02)
so I took the recommendation from Tempestuous concerning
automating the network setup process and
added these lines to /etc/rc.d/rc.local (after the above lines):

rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth0

Anyway I hope this helps a9x and anyone else with this ethernet hardware.
As a newcomer to Linux, I suspect there are other more elegant solutions to this. And I do understand the frustrations.

Seeing that that the crc-ccitt.ko module ended in .ko just like the via-velocity.ko module, I ran insmod on it in a terminal.
My Computer didn't self-destruct.
Then of course I ran insmod on the via driver.
Voila! No error statements. The rest is history. Connnection!

Almost Sunrise. Good Night and Good Luck!

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#2 Post by BarryK »

I think that it would have worked after running the Network Wizard, but not
after reboot, because of the order in which the bootup scripts execute.
/etc/rc.d/rc.network executes before rc.local.
The former executes whatever was set by the Wizard, but the network chip
driver has not yet loaded.

Try this:
# depmod
...this should integrate the via driver, so at next bootup it should get recongised
and auto-loaded prior to rc.network executing.
So, you won't need anything in rc.local.

Let's see, after executing 'depmod', try this:
# modinfo via-velocity
...it should show what pci interfaces the module works with.
Then do this:
# lspci
...which will show you what pci interfaces are in your pc.
...if there is a match (the display format is different), then rc.sysinit at bootup will detect this and load the
via-velocity module.

Rider1
Posts: 8
Joined: Tue 03 Oct 2006, 20:10
Location: Philadelphia, PA

Via-Velocity Working Even Better

#3 Post by Rider1 »

Many Thanks, BarryK!

Erased Pup_Save and started over.

Copied Via-velocity.ko (from all-modules) to /lib/modules/2.6.16.7/net

Opened up a terminal . Ran #depmod . Closed terminal. Reboot.

Ran Puppy_Network_Wizard. Ethernet Recognized. Configuration saved.

Simple. Elegant. ("depmod" worked this time)

I'm Actually posting this message using the humble computer
with the Via-Velocity interface. (2.4Ghz CeleronD, Soyo SY-P4RC350 Board)

Next Challenge: 1394 Firewire Interface(PCI card) for Digital Video Capture and Editing.
Shouldn't be too tough to get running. Deciding between Kino, Avidemux, or LiVES
will be difficult. Probably will use whatever works. Will keep you posted.

Again My Appreciation To You Barry and The Puppy Linux Community.

Post Reply