Puppy Linux Discussion Forum

[puppian]

Can someone help this guy out?

------------------------------------
I've tried Puppy in the past, and it's fun, but it won't be useful for me until it includes a VIA Velocity gigabit net driver. I know it's not included officially in the 2.4 kernel, but it's available elsewhere.

I'm attaching a source for the module, which I found at this page:
http://www.viaarena.com/default.aspx?PageID=420&OSID=1&CatID=1190&SubCatID=130

Even if you can't get hardware autodetection to work for it, just including the module will be enough for me. I can't complile it myself since my main OS is 64 bit.

Also, you might want to consider "CDRBQ" ( http://sourceforge.net/projects/cdrtoaster/ )as a CD burning frontend. It's ridiculously tiny and easy to use. I think it's tailor made for live distros. Pardon me if it's already in dotpup or whatever--I wouldn't know, since my net doesn't work in Puppy.

Thanks for considering my requests.

Brody
------------------------------------

[MU]

http://dotpups.de/diverse-tgz/velocityget.o.tgz (20 kb)

**************************************************
Build options:
VERSION 2.4.29
SMP Disabled
**************************************************

Mark

[MU]

[puppian]

Thanks so much Mark!
I hope Brody will find it useful

[shrdlu]

I am a happy Puppy user on 2 out of 3 of my computers.

Ironically, I can't get it to work reliably on a newer box I built when Tiger-direct basically was giving away SOYO mobos. The symptoms are wierd - with the 2.4 kernel, sometimes Puppy comes up and works great, but most of the time it hangs during usb initialization. With the 2.6 kernel it comes all the way up, but I can't get to the network. Same problem Brody had. The wizard tells me it sees the on-board eth0 and the via-rhine driver is loaded. Can't even ping the router. This is pretty consistent with other 2.6 distros I've worked with on this box. It looks like both usb and ethernet are trying to grab IRQ 11. Naturally, Windows works perfectly. Since I can still use Puppy, I sorta don't care if it gets fixed or not, but I was curious if anyone else had seen this wierd behavior.

Update: Punted and got things working with ndiswrapper and the win driver.