(old)Puppy Linux Discussion Forum

I tested Slacko 531 on a Pentium4 with intel graphics
and it selected the intel driver and booted nicely.

No problem with sound either.

________________________________________________________

I installed Right click on Slacko and it worked nicely
http://www.murga-linux.com/puppy/viewtopic.php?t=67013

But first install ghasher or gtkhash to get md5sums.

________________________________________________

I upgraded gtkhash to version 0.5.0 and checked it on slacko
http://www.murga-linux.com/puppy/viewto ... 30&t=73839

__________________________________________

Viewing the text in this forum, particularly the text in blue or hyperlinks, default fonts in Seamonkey 2.5 could stand a little tweaking. Nice color scheme, particularly the menu tree. Task bar does a cute disappearing trick when unoccupied. Uh-oh, no "mount" icon. I'm gonna miss this. I guess it was considered to be redundant?

Running 3builddistro with a vanilla Slacko build with Woof2. I'm looking for creative ideas for 5.3.2 and trying to get certain packages to work right (most notably, wbar and idesk).

Works splendidly so far, except some mess in 3builddistro. It fails to create /root/.packages for some reason.

I'd like to thank you, Mick, for all your hard work and the willingness to cooperate with other developers, as you did with the Trinity SFS and the /opt prefix fixes.

EDIT: found the problem, it was my fault. Hurray for Woof2!

WoW!

i'm running PAE 5.3.1 in a RAM based LIve media environment. This system, on a laptop, screams, its so fast.

The only change I have made is the addition of FULL SAMBA 3.61 from the Network Section of the PPM. Your tool that you include to help newbies (or even experienced Puppy users) to start immediate use is phenomenal. IN fact, the total arrangement of how you start the system as well as how you start SAMBA makes this so easy to have a Puppy which matches the experience I get OOTB from OSs from the Big 2 Ms (MACs and Microsofts). And, it shares all of my media flawlessly with entertainment devices that I have had problems with, in Linux, before now.

The RAM use is ONLY 134MB on this 4GB system with SAMBA sharing going and a user transferring a file from this laptop. This is a phenomenal feat. And after 2 days, I still haven't rebooted to save-session the current desktop. This experience is polished, its stable, its fast, and its feature-rich. This is all I could ever ask for from any distro, but, the speed of this exceeds wildest dreams.

Thanks 01Micko......THANKS!

Iguleder wrote:I'm looking for creative ideas for 5.3.2

I am using wbar with a Puppy config script
http://www.murga-linux.com/puppy/viewto ... 073#589073
and also the Should I customise tip (don't try this without accelerated graphics)
http://puppylinux.org/wikka/SlackoTips
Also updated Transmission - there was a reason Mick was using the 1.2 version but it is slow (to the point of not working for some)

Running a home-made 5.3.1 and it's amazing how fast it is.

I'll probably rebuild all the packages in my repository with a /usr prefix, so the existing packages can be easily replaced.

I really like all the small gems of this version (e.g the SFS loading feature), they make it much nicer than 5.2.x.

By the way, I have three bug reports:
- Annoying flickering in JWM's tooltips when the cursor hovers above the tray.
- Visual artifacts under 2.6.37.6; I use the i915 driver (for my Intel 3150 GPU) and I see small diagonal lines in random places. Opening an application "cleans" its area, but they appear again once something moves.
- My Synaptics touchpad support multi-touch, but two-finger scrolling is disabled by default, as in any other distro. However, flsynclient doesn't work.

Iguleder, about your bug report,

jwm.. Joe has been active but his latest has layer problems. I stuck with 508. Yes jwm is getting a bit behind, but it's tiny, the bloat with jwm is the tools!

i915 .. could be jwm, but I did find a minor bug with woof to do with glib, may be unrelated. There are numerous "tricks" you can perform on xorg, including fooling it into not reading a xorg.conf at all, but being a laptop you'd possibly need to add some "synaptics.conf" stuff in /etc/xorg.conf.d/

Synaptics .. either try the newer kernel or try flsynclient -0.7 in PPM.

First of all, I want this to be clear - this isn't a bug report, but a RFC

Since OpenGL is unsupported out-of-the-box, I was thinking - why don't we build a tiny Mesa package with just the DRI software rasterizer (e.g a CPU-based driver) so 3D stuff work out of the box?

This could be a nice addition and I don't think it's big. For new machines, OpenGL will work, while it will be slow on older machines. But the key feature here is the fact it works.

Hi all

Mick have found a few little problems

1. there is no "more" command in the bash, usually in /bin/ (was working in 530 but not in 531) (found by CatDude and Smokey01) during a scripting session on psip. (great tool for development)

2. the rox focus bug.

3. the important one. the link from the shed to you playing guitar doesn't work

everything else seems to be working great, congratulations on another great puppy

cheers

Don

Here is a bug that I reported in development and the answer was you will have to live with it.
Maybe you will have more time now to investigate. Hard to figure I am the only one this is affecting.

Problem:
1366X768 resolution
At first fresh boot of Slacko 5.3.1
I am able to select 1366X768 resolution in xorgwizard.
Personalized setting says it is 1368X768
Desktop looks like it is off to right slightly.
So, desktop looks like 1368X768.
In personalized setting, I can choose 1366X768, and it shows as that in all settings.
However, the desktop is still looking like 1368X768 is used.

My monitors native resolution is 1366X768, but it will not auto adjust to 1368X768
In fact, I do not think that is even a standard excepted resolution.
The problem seems to be that 1368X768 gets used, even after selecting 1366X768.

These pictures are after I change setting.
Frugal + save file and rebooted.
NV driver.

Hi,

thank you for slacko puppy. Works great so far on my Dell mini 9. First I had a problem with wifi (broadcom bcm4312) connecting to my router but using himem-pae iso fixed it (newer kernel I suppose).

Iguleder wrote: - Visual artifacts under 2.6.37.6; I use the i915 driver (for my Intel 3150 GPU) and I see small diagonal lines in random places. Opening an application "cleans" its area, but they appear again once something moves.

This is related to intel video drivers (xf86-video-intel). I updated to 2.17.0 and intel "fixed" it by removing the upper border edges.

Iguleder

Hmm.. interesting idea about the cut down mesa. Using mesa does solve some i915 issues.

Stripe

1) I don't know what happened there with "more". It may be the busybox upgrade in woof. You can symlink to busybox., or use "less", a more comprehensive iteration of "more", confused yet?

2) CatDude also found a work-around for the rox bug, another oversight
http://www.murga-linux.com/puppy/viewto ... 851#585851
Hmmm... just tried that, didn't work for me , maybe that's why I left it out? (rebooted)

3) Woops, need to re-upload that clip!

bigpup
Can you please try shinobar's latest "firstrun-1.9.5" to see if this fixes that issue. I tried to use it in woof but it has some weird bug where it won't install in the woof environment but installs fine in a running pup.
EDIT: No, firstrun wont make a difference. It seems a problem of the NV driver. One other has reported the issue in an early alpha, wuwei. The nouveau driver worked better for him. I took it out because it is problematic with many older nvidias and it would always get chosen, even if it was hidden in the "drivers-alternate" directory. Nouveau driver is in PPM under "Setup". Please give it a try while I see if I can find a patched source for NV.

tekeli-li
Welcome and I hope you continue to enjoy Slacko. There is the "wl" driver for broadcom in PPM for the older kernel if you want to try it again. I guess the problem is I should include it, but it's huge and proprietary.. I perhaps should have mentioned in the release notes that for modern machines with broadcom wireless that the PAE kernel is best.

01mick0

Re: line 303 of rc.sysinit.
Given that the kernel now contains built in support for both USB core & storage, this line would appear to be redundant.

Finally many thanks for this very slick pup - SLICKO ?

Slacko 5.3.1: serial mouse still won't work.

Finally many thanks for this very slick pup - SLICKO ?

Perhaps we should start calling him 01Slicko....instead of 01micko?

Aitch

01micko wrote:The nouveau driver worked better for him. I took it out because it is problematic with many older nvidias and it would always get chosen, even if it was hidden in the "drivers-alternate" directory. Nouveau driver is in PPM under "Setup". Please give it a try while I see if I can find a patched source for NV.

The Nouveau driver is a little better with the 1366X768 resolution.
However, it is no good for visuals with everything else. Too many other problems to list.
This is an older Nvidia graphics chip and this driver does not work well with.

I am starting to think the Nvidia chip just does not support this resolution.
But, that still does not resolve the question.
Why would the NV driver offer 1368X768 resolution and seem to be using only that?

See here, from Steps >
http://wiki.debian.org/NvidiaGraphicsDrivers

Aitch

bigpup

From your screeny xrandr is telling us that your card is using 1366 x 768 @ 60Hz.

There is no update to the nv driver, actually it looks like it's an abandoned project, which is unfortunate since nouveau is still very experimental. Have you tried vesa? There is no gain in using nv because it doesn't support video acceleration at all.

I might try and patch nv myself anyway, but I doubt that it will improve your situation. I might be able to get rid of the ridiculous 1368 entry but your display still might be slightly shifted. I remember from installing drivers in windows XP that I had to adjust the monitor with the physical buttons on the monitor it's self to get the image to fit the screen.

My display is put left about 5 to 6 pixels when I use the onboard nvidia in my main machine using nv (1280 x 1024) but if I plug in my faster nvidia card it is fine. Installing the proprietary video driver (nvidia) fixes it in both instances. This happens to me in Lupu as well (and IIRC wuwei too), and in Racy all I get working is vesa.

An output of your /var/log/Xorg.0.log may be useful.

EDIT: There is no mention of the 1368 entry in the nv driver sources so there is nothing to patch. maybe it's ddcprobe?
Please run "ddcprobe" in a terminal and see if the "1368" entry is there, also do this in Lupu.

Output from Slacko 5.3.1
Lupu gives same output.

# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV34 Board - q231-0 Chip Rev
memory: 65536kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 3
id: 0249
eisa: EMA0249
serial: 10310034
manufacture: 3 2011
input: sync on green, analog signal.
screensize: 41 23
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 1280x800@60
ctiming: 1280x1280@60
dtiming: 1366x768@69
monitorname: E182HL
monitorrange: 31-83, 56-76
monitorserial: Q450C0014020
#