Puppy Linux Discussion Forum

[Aitch]

@phydiux

[raffy]

You can try "puppy PMEDIA=" (that is, blank definition) if it can't use "usbcd".

[ZorroOfMars]

Hello all,

I've an ebox2300SX and wanted to download the puppy 2.14 iso for ebox.

It seems that ftp://puppy:linux@ftp.servage.net doesn't work now.
Has anything changed in the parameters (server or login/password).

Thanks for help.

[Aitch]

Hi ZorroOfMars

I just tried & it doesn't work for me either

It used to be user=puppy; password=linux

Try pm'ing raffy

http://www.murga-linux.com/puppy/privmsg.php?mode=post&u=133

Aitch

[Taki]

all OS that I have tried so far have kernel panicked with coprocessor error.

Any chance of a step by step tutorial?

[Aitch]

@Taki

[raffy]

[Taki]

Thanks for the response.

[Taki]

puppy PMEDIA=usbstorage did the trick

I'm gonna install it to IDE Hdd.

Thanks for the help.

[Aitch]

Well done, thanks for feedback

[eehouse]

I'm trying to get an unpatched kernel (i.e. without the manufacturer's skanky mods to 2.6.18) working on my 2300-sx. The thing boots, but the ethernet driver (r6040.c) doesn't work at all. Logging says that the driver is initialized without error (r6040_init_one succeeds) but that r6040_open is never called. This is with 2.6.26 and 2.6.27-rc2, which has seen a lot of changes to the driver. The driver does work in my patched 2.6.18. so I know the hardware's ok, but that driver is so old, so different from the tip, that it can't be used with a current kernel.

Anybody had any luck working in this direction, either on Puppy or some other distro?

[Aitch]

hi eehouse

go back one page

http://www.murga-linux.com/puppy/viewtopic.php?t=21864&start=75

[eehouse]

Ok, it works now. Working with the very latest kernel sources (2.6.27-rc2) was the trick, together with a mod that may not be required for Puppy. I'm running Debian, and for reasons I don't understand the r6040 device comes up as eth3. Tweaking /etc/network/interfaces to expect eth3 puts the box online with an unpatched kernel.

Is it worth posting the .config file I'm using?

[sytze]

Photon, what you have accomplished with the support of others is what we have been looking for quite some time now. Carefully reading all the posts has helped in getting Puppy wagging it's tail in about 2 hours.

I have been looking to get something going on the Vortex86SX platform to avoid additional (OS - CE) cost. The aim however is to get a commercial system going to run Windows with rdesktop against MS Terminal Server.

The downside is that the system is too slow for a commercial solution. It takes almost 4 minutes for everything to boot up from power-up to loading X.

rdesktop is remarkably responsive considering the the a speed of booting into X - however it could do with some improvement in speed.

Photon, you mentioned that there are possibly improvements that can be made to speed things up. Would you be able to give a prognosis of what kind of improvement one could expect?

The aim of the solution is:
1. to avoid Windows CE as platform.
2. to remove as much as possible from the core Puppy OS and X as possible.
3. Boot straight into rdesktop.

Would be great if there was a console based rdesktop to avoid running X - but I did not find anything like that - should I stop looking?

I am not able to do this myself - I'm a MS windows old-timer with an aged passion for technical stuff, currently building a business.

[raffy]

In 2.13 (safepup), I've put rdesktop from pupget package. 2.14 (photonn's build) uses pet packages, and the download link is here (or get it via the package manager).

I use it in console like this: