Slacko RC

[Jades]

Any thoughts on what I can check to see what's the matter with Slacko and my Netgear WN111v2? It's wierd that on this distro I'm getting performance not much quicker than dialup whereas on all of the versions of Lupu the performance has been close to that of XP. I suspect it's possibly something to do with the drivers or the newer kernel version.

I had been comparing it to Lupu 528, which was a little unfair as that version was optomised for i686+ systems but even Lupu 525 is considerably quicker online than Slacko. The good wireless performance had been the reason why I decided to use Puppy rather than one of the more mainstream distros.

Other than the disappointing wireless performance, Slacko has run well on the Pentium D machine and seems to be running well on the K6 once I installed the i486 version of FFMPEG. Even Sea Monkey is starting to grow on me.

[Jades]

Double post. Damned touchpad!

[Lobster]

Lobster,
Any more and it's 10mins simmer and then seafood sauce.

For those requiring their mind to be suchifed (to be made into raw fish)
Here is the new YAP 2.1 for Slacko
. . . now to set up a shrine for helpless sardines . . .

http://www.murga-linux.com/puppy/viewto ... 702#574702

[rcrsn51]

What I noticed is, that the step in the boot process where it says "Looking for Puppy files ..." seems to take more time now on my computer and there are red dots appearing. Was there a change somewhere? Can anyone point out (link?) what has been changed and where?

There has definitely been a change in recent Puppies. Do you have any devices like printers turned on during bootup?

Also, please post your GRUB menu.lst entry. There may be ways to optimize it.

[emil]

rcrsn51
I think I found the relevant blog entry.

I am on a machine with 11 usb and card slots
my grub entry for slacko is

Code: Select all

title slacko(on /dev/sda3)
  root (hd0,2)
  kernel /slacko/vmlinuz psubdir=slacko pfix=ram ro vga=normal
  initrd /slacko/initrd.gz

emil

[rcrsn51]

@emil: Try this change:

Code: Select all

title slacko(on /dev/sda3)
  root (hd0,2)
  kernel /slacko/vmlinuz psubdir=slacko pfix=ram ro vga=normal pdev1=sda3
  initrd /slacko/initrd.gz

[gcmartin]

On command line it asks for a password = there is none so I press Enter. ... .

Change your script to

Code: Select all

#!/bin/bash
mount.cifs //192.168.1.101/DadE /mnt/network/STUDY/DadE -o username=guest,guest

This will work your script. You may be a little more universal to use

Code: Select all

mount -t cifs -o username=root,password=woofwoof  //192.168.1.101/DadE /mnt/network/STUDY/DadE

I have found this to work on all PUP distros, used thus far, trying to use folders from Windows, Macs, and Linux PCs on the LAN. Its because some of the distro are implemented with subsystems that require the mount command to use the "password=" approach. So, by using the parm your script should work on most distro where you use it.

Finally, if you want your Pup to run your script every time you boot, then post back for Slacko directions to do this.

Hope this helps

[rcrsn51]

You may be a little more universal to use

Code: Select all

mount -o username=root,password=woofwoof  //192.168.1.../resource /mnt/network/STUDY

???

Please explain. Why would you login to a Windows machine using the credentials of a Puppy user?

[gcmartin]

Please explain. Why would you login to a Windows machine using the credentials of a Puppy user?

Management and tracking on the internal LAN at the sharing source.

@rcrsn51 PM me with this if you like.

[Jades]

What I noticed is, that the step in the boot process where it says "Looking for Puppy files ..." seems to take more time now on my computer and there are red dots appearing. Was there a change somewhere?

I don't have the thread address to hand but I think that Barry added an extra delay because some systems were completing the search process before attached USB storage had finished initialising and were consequently failing to find the saves and boot.

[gcmartin]

The FLASH issue that was raised: I see what's occurring.

My observation

1. Slacko PAE boots to a text window for Video selection
2. Slacko proceeds to desktop
3. Something in Slacko sees a active LAN connections and request
4. FLASH installation
5. Something delays FirstRUN but, it pops to the desktop
6. Flash is installed and FirstRUN changes are completed.

I can see that the FLASH installation would be obliterated if a user completed FirstRUN with changes, for, FirstRUN would restart the desktop. If desktop restart is done BEFORE FLASH installs, then the ability to use the automated method of FLASH installation would disappear from desktop and view.

OptionsMaybe, it there is a LAN connection, a button on FirstRUN could trigger a FLASH installation after FirstRUN completes.
There are other methods, too, some already present in the system which could be used instead.

Work-around for me has been

1. Cancel the FLASH request.
2. Complete FirstRUN,
3. then use QuickSET or PPM to add Flash (and other functionality) to the system.

Reasoning is that I know, from the past, that the traditional methods in the system have worked.

Hope this helps

[emil]

@rcrsn51, thanks, that worked
it is faster, it stops after the white dots and then there is a red
pausing
shocked me first, but all went well

@jades, thanks for info, i found it, this change was in April

[bigpup]

01micko,

Thanks for your hard work to produce Slacko.
It is starting to look very good and definitely is what Puppy needs to support the newer hardware.

A little understanding is needed by all who post to this topic.
SLACKO is still in testing and development mode.

YOU WILL FIND THINGS THAT DO NOT WORK!

Your ideas are great and very much needed!!

Slacko is not perfect, yet. So please a little understanding of the facts and a little less attitude.

I have a Nvidia driver problem. I know Slacko is not finished. I told 01micko the problem and he says it is not being seen by him, but he will look into it. That tells me the problem may be something I did or did not do. So, I will make sure I did not do something wrong. Troubleshooting 101

[01micko]

Just a note about nvidia,

This may affect bigpup, Tasgarth et al.

I have not compiled the 173xxx version of the driver for the PAE (RC++ k2.6.39.4) version. Do we need it?

I will not compile the nvidia-96xxx version for that kernel as old machines are generally not compatible with PAE, my lappy and brookdale are 2 such machines. They are both circa 2005, both intel.

[bigpup]

I have a Dell computer, made in 2007, that needs the Nvidia 173XXX driver.

Again the question. What do you support?

[01micko]

I have a Dell computer, made in 2007, that needs the Nvidia 173XXX driver.

Again the question. What do you support?

By support if you mean kernel I think it's clear that the main version is the 2.6.37.6 version which has the full suite of nvidia drivers.

The ++ versions are the more experimental versions.

2.6.37.6 (main version) has had extensive testing and has proven very stable.

In saying all that I support my work!

I'll consider compiling nvidia-173xxx for 2.6.39.4.

IIRC bigpup, you had a request for certain minor version of that driver. Heads up please? TIA

EDIT: I have these sources on file
NVIDIA-Linux-x86-173.14.28-pkg1.run
NVIDIA-Linux-x86-173.14.30-pkg1.run

[bigpup]

On Dell computer made in 2007.

Not sure if I need the PAE version of the kernel. Do not think so.
I am using the RC++ version on this machine, but got it for my newer computer.

The Nvidia driver I used in Lucid Puppy was 173.14.25.
In earlier testing of Slacko had problems getting 173.14.28 to work.

I was testing Slacko on my newer computer more than this one, so let me do some video driver testing with the other version of Slacko and I will get back with results.

[rjbrewer]

On Dell computer made in 2007.

Not sure if I need the PAE version of the kernel. Do not think so.
I am using the RC++ version on this machine, but got it for my newer computer.

PAE is for running more than 3Gb ram on 32bit os.

According to Linus Torvalds It "really,really sucks".

[grump]

On command line it asks for a password = there is none so I press Enter. ... .

Change your script to

Code: Select all

#!/bin/bash
mount.cifs //192.168.1.101/DadE /mnt/network/STUDY/DadE -o username=guest,guest

This will work your script. You may be a little more universal to use

Code: Select all

mount -t cifs -o username=root,password=woofwoof  //192.168.1.101/DadE /mnt/network/STUDY/DadE

I have found this to work on all PUP distros, used thus far, trying to use folders from Windows, Macs, and Linux PCs on the LAN....

I've tried both these methods, and some variations from the console and get asked for a password every time.

I now have a link to pnethood on the desktop and for the time being will use that, but will return to this puzzle from time to time. Thanks everyone for your advice.

[rcrsn51]

@grump: Are you typing a space after the comma in the above commands? If so, you will still be asked for a password.