(old)Puppy Linux Discussion Forum

@NewCrest - in my earlier test with 2.16, it still have the same performance problem as 2.15CE. I'm sure the bloat in my compiled NTFS is due to my own foresight ...

@MU - Thanks, I tried, but still the same

@Rest of 2.14R team - Thanks !

(there's a service pack that's been "nearly ready" for more than a month..)

I know how that goes. I've given myself an ultimatum to get all my "almost done" stuff finished by Sunday. My original plan was to have it all done by mid October. Last October that is.

Speaking of which, part if that stuff involves adding a boot.msg type deal to USB installs. Then when booting from USB you get the ability to add boot options ans such, just like with live-cd. It's pretty simple; mainly needs a tweak to the install scripts so they copy in a template syslinux.cfg file then append the final line to it (rather than creating the whole file on the fly). That way the same file can be used when setting up syslinux, extlinux, and isolinux, without having to modify code in a dozen places when you want to change some minor detail.

I should have it all togeather for 3.01 and 2.14 tonight, and maybe 2.14R (assuming there's a difference in the relevant scripts; haven't looked yet).

In case you're interested in the syslinux modifications I mentioned above, I just uploaded them here:
http://www.murga-linux.com/puppy/viewto ... 777#172777

Something to be aware of if you use it: my version uses f2.msg rather than f2.

Also, if you don't use it, I should let you know that as far as I can tell you didn't modify the remaster script nor the mulitisession scripts to take in account for the f2 file you added.
/etc/rc.d/rc.shutdown
/usr/sbin/pupremaster.sh
/usr/sbin/savesession-dvd

It's an easy fix, just use find to locate where it copies the boot.msg file, and add a line for f2. All three of the scripts are about the same.


One other thing about 2.14R that I took a while to realize: I like the GTK theme, but it's hard to tell at a glance if a check box is checked or unchecked. It took forever before I realized why Seamonkey wouldn't just shut up when I tried checking my email

Pizzasgood wrote:I like the GTK theme, but it's hard to tell at a glance if a check box is checked or unchecked.

Yeah, I know what you mean. It took Dougal and me quite some time to decide on a good GTK theme. It seems every one had some bad trait, e.g., while testing, there always seemed to be an app where the foreground colour and background colour were nearly the same making text hard to read. This one turned out to be the best compromise...

I do wish there was some way of changing the check boxes to use a check mark though :-/

Hi guys

Just wanted to stop by and say thanks for bringing out a thoroughly tested puppy. Im looking forward to the updated drivers/NTFS support. The first CE alpha will not be going out without these enhancements.

Keep up the good work!!! Woof Woof

Hi there, how is the progress going? Were looking to start the development of the CE edition based on this soon and release an alpha.

I found another bug the other day that I was going to mention, but then I forgot what it was... I noticed it again today though, so here it is:

In the /usr/sbin/puppyinstaller script, it gives you the option to mount an iso to get the pup_xxx.sfs file. This uses a loop device. Since it wasn't specified which, it will generally grab /dev/loop2. That's a problem later, because the part that mounts pup_xxx.sfs (line 1417) is hardcoded to use /dev/loop2. This would also be a problem if the user had something else mounted (like an old pup_save.2fs file). Changing: to: would let it use any loop device while still explicitly using losetup to mount it.



While working on Pebble over the weekend, I figured out what broke my Pizzapup install and fixed it. So I'm mostly done with 2.14R for the time being. It's been fun, but I'm not quite ready to scrap my old install just yet.

Keep up the good work

Hi Dougal,
Love hotpup and pfix=blacklist. I've just done full install to my harddrive (twice) and FYI it won't recognize usb flash drives in any way: hotpup, mut, pmount, or command line. I've tried 5 different drives of various types and sizes. Works fine from liveCD however. It's also the first puppy edition that's recognized my mrv8k wireless card.

jrb wrote:It's also the first puppy edition that's recognized my mrv8k wireless card.

The wifi drivers in Pup214R were updated, and we included the mrv8k driver (for Marvell Libertas Wifi chipsets).
This driver has been available as an additional package for Puppy for a long time now, from -
http://dotpups.de/dotpups/Wifi/
but you're the first person to report anything about it.

Does it work? Can you make a wifi connection?

If you want to use WEP encryption, you will probably need to load the wifi WEP module, like this - and maybe also these encryption modules - But the mrv8k driver does not support WPA encryption.

Sorry tempestuous.
Sadly the mrv8k doesn't find my network. I have this machine wired in and when I saw mrv8k wireless indicated I assumed it was correct without trying it. When I scan it doesn't pick up my unencrypted network, which my laptop does. This is a trendnet tew421pc wireless card which I have only used with ndiswrapper.

More info on my harddrive install. I formatted the drive and then did full install. On the 1st boot I get full usb drive function. On 2nd, 3rd, etc. it disappears. Strangely enough after all this, I uninstalled Seamonkey and installed Opera9.5b-staticqt and then remastered the CD (had to manually replace pup_0R.sfs with pup_214R.sfs in pupremaster.sh) and the new CD is fully functional including usb drives.

I also noticed the detection and loading of the native mrv8k driver, great as I have been using ndiswrapper forever now. but it didn't work. the log indicates that it failed to load a firmware file.

I have located the firmware files in the zdrv file and plan to copy them into the appropriate location in my save file. But I haven't had a chance to try this yet. My puppy computer is very busy most of the time so I don't often have a chance to test new things. Thanks for a great puppy.

Puppy PC: Dell PIII 450 MHz cpu, 512 MB ram, 160GB hd. Backup Storage, Firewall, Router, Mail service etc. for a 5 PC network.

Inspried by joe roberts, I am attaching the /var/log/message.

Hi,

Using teenpup which is based on 214 I get no problems. I can connect with my Toshiba portage 4010 laptop (orinoco_cs) and my mainframe
(rt2500).

With 214R, again I have no trouble connecting with mainframe.

With laptop the orinoco_cs driver is not loaded at boot. If I load it with modprobe I still can't get wireless.

I have tried the drivers from teenpup with the same result.

Anyone know of a procedure I can use to remedy the situation ?

Regards Tony.

Joe, I would be very interested in how you got puppy to run all of the network services you have, would be useful for the cybercafe

>Joe, I would be very interested in how you got puppy to run all of the network services you have, would be useful for the cybercafe

Ecomoney:
My setup is quite primitive, serves only 5 lightly used PCs, and not secure at all. I guess that’s why its performance is acceptable. Everything I use I found in this forum so the credit belongs to others here.

The setup is a DSL modem on eth0 for internet access. Local LAN is on wlan0 in Ad-Hoc mode. The 5 PCs connect to wlan0 rather than an access point appliance. The printer has its own wifi card (otherwise it would be installed on this PC too).

Router functionality consists of enabling packet forwarding and NAT in the kernel. The default route sends every packet not intended for a local LAN IP to the DSL modem which itself forwards them out to the internet.

The Backup Storage consists of a cron job that runs rsync against the home directory of each of the client PCs several times a day. I does not delete backup files so its not a mirror. The client PCs run rsync as a daemon so they share the work of determining the bits that update the backup.

Samba is configured to publicly share the whole 160GB FAT32 drive to the local LAN only (rejects anything from eth0). Puppy’s 1GB of files and swap are not shared.

Firewall is iptables with only a few rules, these I have picked up from several examples in the forums. I often fiddle with the rules as some program or other doesn’t work as expected. Because we don’t provide ANY services or access from the internet into the LAN (this is why it works for me) it can be kept very simple.

Mail services consists of the standard UNIX mail program providing POP3/SMTP to the LAN from local storage. Incoming mail is provided by “yahoopops

joe-roberts wrote:the log indicates that it failed to load a firmware file.

OK, that could be the problem. I provided "standard" firmware for the mrv8k driver, but maybe it's necessary to install the vendor-specifice firmware.

jrb and joe-roberts, please install this dotpet, and copy the Windows driver for your device somewhere convenient ... let's say /root/my-applications
The Windows driver may consist of several files, I think it's the .sys file we want.
Now run this command to extract the firmware from the Windows sys file - Now shift the extracted firmware files from /root/my-applications into /lib/firmware, and reboot.
Look at the output of dmesg to see how the mrv8k module loaded, and report what it says if there are further problems.

tony,
Yes, the orinoco driver in Pup214R was updated.
Please load the driver and configure your wifi connection using manual commands, following this procedure -
http://www.murga-linux.com/puppy/viewtopic.php?t=22469

This way you should be able to identify at what point the process fails, and you can report your results if you need further help.

As a start, you should do this to see how the orinoco driver loaded then do this to see if a network interface has been created

Thank you Dougal and others who came up with the HotPup daemon. I installed this on my Puppy 2.17.1 and worked very well.

I really love seeing this feature in our favorite Puppy .

Thanks again.

Hi tempestuous,

Thank you for coming back, I had already worked through the measures that you prescribed. but it led me to type in the cardmgr command.

I was then surprised to find that I had wireless. Had to think back to what I had done.

It seems that the card manager was not starting automatically at boot. Something that it did with teenpup.

Regards Tony.

Pizzasgood wrote:In case you're interested in the syslinux modifications I mentioned above, I just uploaded them here:
http://www.murga-linux.com/puppy/viewto ... 777#172777

I remember you asked people to test this for you and wasn't sure if there's a point in it, but I guess we should probably add it. I'll implement it today.

One other thing about 2.14R that I took a while to realize: I like the GTK theme, but it's hard to tell at a glance if a check box is checked or unchecked.

Yes, that's a pretty annoying thing about that gtk-engine.
I've also got a package with the smooth engines and a bunch of themes -- I should post it in case people want to use them (I left it out by default since it's big and slow).