Precise Puppy 5.5 Release Candidate

Please post any bugs you have found
Message
Author
User avatar
tater
Posts: 32
Joined: Sat 29 May 2010, 18:13
Location: Michigan, USA

#211 Post by tater »

Greetings rcrsn51

I tried your solution for connecting to my samba shares without success.

I don't know if this will help, but my server is running SMS (superb mini server) based on slackware 13.37.

Here's my samba.conf

Code: Select all

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba HOWTO Collection.
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
	log file = /var/log/samba.%m
	printer = HP_Deskjet_1050_J410_series
	restrict anonymous = no
	ldap ssl = No
	max protocol = NT1
	server string = SMS
	path = /var/spool
	acl compatibility = winnt
	workgroup = WORKGROUP
	server signing = Auto
	os level = 20
	domain master = no
	public = yes
	security = share
	preferred master = no
	max log size = 50
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;    hosts allow = 192.168.10.0  127.0.0.0

[Music]
	force user = nobody
	path = /mnt/sdb1/Music/
	read only = yes

[andy]
	valid users = andy
	writeable = yes
	path = /mnt/sdb1/andy/

[Videos]
        force user = nobody
	path = /mnt/sdb1/Videos
        read only = yes



[HPDeskje]
	printable = yes
	path = /var/spool/cups/
Let me know if you want me to test anything else.

[/code]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#212 Post by rcrsn51 »

@tater: Just to clarify:

1. What version of Precise are you using?

2. Can other Puppies connect to this server?

Here are some variations to try:

Code: Select all

sec=
       none attempt to connection as a null user (no name)
       krb5 Use Kerberos version 5 authentication
       krb5i Use Kerberos authentication and packet signing
       ntlm Use NTLM password hashing (default)
       ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default)
       ntlmv2 Use NTLMv2 password hashing
       ntlmv2i Use NTLMv2 password hashing with packet signing

User avatar
tater
Posts: 32
Joined: Sat 29 May 2010, 18:13
Location: Michigan, USA

#213 Post by tater »

@rcrsn51

I'm testing precise 5.4.93 and this is not connecting to my samba shares.

I have lupu 528.005 running on two machines and both connect using pnethood without a problem. Also have a windows 7 machine on the network that connects fine.

User avatar
tater
Posts: 32
Joined: Sat 29 May 2010, 18:13
Location: Michigan, USA

#214 Post by tater »

@rcrsn51

I have to step out to run some errands.

I'll be back later, I'll try those codes you've provided and let you know my results.

Thanks for your help

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Precise 5.4.9.3 (k3.8.0)

#215 Post by peebee »

rcrsn51 wrote:Samba-login has an Options box. Enter sec=ntlm

Can someone else please test this?
YASSM works OK for me on 5.4.93 both without and with your suggested option.

My server is Slacko 5.4 running Samba 3.6.1 (from memory).

Cheers
peebee
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#216 Post by rcrsn51 »

@peebee: Thanks. It looks like this issue is specific to very new kernels and certain light-weight Samba servers.

Goku
Posts: 7
Joined: Sat 23 Feb 2013, 18:14

Virtual Box

#217 Post by Goku »

I like this distro don't see any problems but the screen size is way to off and changing the resolution is not helping the bottom and the right side is off other than that no bugs for someone who goes on the Internet and plays some games.

EDIT: I found a fix to the screen problem you go to the Terminal and then you type in XorgWizard after you then chose vesa and then your screen resoultion wanted now there are not any bugs for Virtual Box.
Last edited by Goku on Sun 24 Feb 2013, 16:27, edited 1 time in total.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#218 Post by don570 »

http://murga-linux.com/puppy/viewtopic. ... 248#687248

There is a German version of my Right click menu package.
It works for English as well 8)

______________________________________________

drblock2
Posts: 153
Joined: Mon 19 Jan 2009, 12:38

Precise 5.4.93

#219 Post by drblock2 »

@rcrsn51

Yes, adding sec=ntlm to the options in YASSM solves the problem of connecting to Puppy machines on the network!

This is unfortunately not possible from the GUI in pnethood, but I will try adding this in the script and report back.

@BarryK

Adding the missing file version.h whether via symbolic link or by simply copying the missing file to the expected location does not make it possible to compile the nvidia driver. There must be some other (additional) problem.

npierce
Posts: 858
Joined: Tue 29 Dec 2009, 01:40

alias ls='ls --color=auto'

#220 Post by npierce »

linuxcbon wrote:- Bright color in console doing ls -la /dev/ram comes from "/etc/profile" line 188 alias ls='ls --color=auto'
Yes, but this is not a bug. It isn't even unconventional behavior.

By default the ls command displays its lists in monochrome. This is so that all terminals are supported -- even antiques from the 1980s that don't support color and relics from the 1970s that would be confused by the ANSI escape sequences needed to set text colors.

But the Linux console and terminal emulators like xterm (and those it inspired, like rxvt and urxvt) support ANSI escape sequences and color. And most folks prefer the color-coded lists (as long as the colors are well chosen), so it has been common practice for distro builders to include the "alias ls='ls --color=auto'" in a bash configuration file at least since the mid-1990s.

We all know that Puppy users like to make good use of old hardware rather than consigning it to a landfill. But I'll bet not many of us connect our Puppies to monochrome terminals. And those that do probably have terminals that are younger than three decades in age and support ANSI, so would simply display the lists in monochrome without choking on escape sequences.

So removing that line from Puppies and requiring those who want colored lists to add it back to a bash configuration file, or type "ls --color" all the time, is not necessary, nor do I expect that it would be a popular change.


As to the bright yellow on white text that ls displays for devices, I totally agree with you that it is hard to read.

You can change that, as explained earlier in this thread:
In an earlier post, [url=http://www.murga-linux.com/puppy//viewtopic.php?p=686747#686747]Improving contrast for ls listing of devices[/url], npierce wrote:But if you prefer the current white background, you can simply change the background color that ls uses to list block devices and character devices.

Add this line to your ~/.bashrc file:

Code: Select all

export LS_COLORS='bd=40;33;01:cd=40;33;01'
Alternatively, you could put it in your /etc/profile.local file or in an appropriate line in your /etc/profile file.
Perhaps if Barry thinks that is an improvement, he might include it in /etc/profile. If not, it is an easy customization to make.

I chose bright yellow on black because that combination may look familiar to anyone that uses a distro that sets LS_COLORS using the dircolors utility. This is for consistency. This way, when you go to help your friend who is running another distro, you don't have to relearn the colors. Also, using black for a background won't affect users who already have black backgrounds. But you may use any colors you like by substituting other values for 40 and 33, and/or removing 01:

Foreground colors:
30 black (dark gray if bright)
31 red
32 green
33 brownish (yellow if bright)
34 blue
35 magenta
36 cyan
37 light gray (white if bright)
39 default foreground color

Background colors:
40 black
41 red
42 green
43 brownish
44 blue
45 magenta
46 cyan
47 light gray
49 default background color

My example uses 01 to make the foreground color bright. If you don't want a bright color remove the 01 and the preceding semicolon (e.g., cd=40;33).

Likewise, for the default foreground or background colors, you don't need to use 39 or 49. Instead you may simply not set a foreground or background color by omitting the number and the semicolon (e.g., cd=33).


There does exist a dircolor utility which is helpful if you would like to make a lot of changes to LS_COLORS, but it is overkill if you just want to change a couple of things. It creates a very long string of over a thousand characters for LS_COLORS, some of which just set colors that are default anyway. Better to just set the few that you want to change.

(If you decide to try dircolor, be sure that the version you get isn't newer than your version of ls ("ls --version"). If dircolors is newer it may use new codes that the older ls doesn't understand, and you will get no colors at all.)

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: alias ls='ls --color=auto'

#221 Post by BarryK »

npierce wrote:
linuxcbon wrote:- Bright color in console doing ls -la /dev/ram comes from "/etc/profile" line 188 alias ls='ls --color=auto'
Yes, but this is not a bug. It isn't even unconventional behavior.

By default the ls command displays its lists in monochrome. This is so that all terminals are supported -- even antiques from the 1980s that don't support color and relics from the 1970s that would be confused by the ANSI escape sequences needed to set text colors.

But the Linux console and terminal emulators like xterm (and those it inspired, like rxvt and urxvt) support ANSI escape sequences and color. And most folks prefer the color-coded lists (as long as the colors are well chosen), so it has been common practice for distro builders to include the "alias ls='ls --color=auto'" in a bash configuration file at least since the mid-1990s.

We all know that Puppy users like to make good use of old hardware rather than consigning it to a landfill. But I'll bet not many of us connect our Puppies to monochrome terminals. And those that do probably have terminals that are younger than three decades in age and support ANSI, so would simply display the lists in monochrome without choking on escape sequences.

So removing that line from Puppies and requiring those who want colored lists to add it back to a bash configuration file, or type "ls --color" all the time, is not necessary, nor do I expect that it would be a popular change.


As to the bright yellow on white text that ls displays for devices, I totally agree with you that it is hard to read.

You can change that, as explained earlier in this thread:
In an earlier post, [url=http://www.murga-linux.com/puppy//viewtopic.php?p=686747#686747]Improving contrast for ls listing of devices[/url], npierce wrote:But if you prefer the current white background, you can simply change the background color that ls uses to list block devices and character devices.

Add this line to your ~/.bashrc file:

Code: Select all

export LS_COLORS='bd=40;33;01:cd=40;33;01'
Alternatively, you could put it in your /etc/profile.local file or in an appropriate line in your /etc/profile file.
Perhaps if Barry thinks that is an improvement, he might include it in /etc/profile. If not, it is an easy customization to make.

I chose bright yellow on black because that combination may look familiar to anyone that uses a distro that sets LS_COLORS using the dircolors utility. This is for consistency. This way, when you go to help your friend who is running another distro, you don't have to relearn the colors. Also, using black for a background won't affect users who already have black backgrounds. But you may use any colors you like by substituting other values for 40 and 33, and/or removing 01:

Foreground colors:
30 black (dark gray if bright)
31 red
32 green
33 brownish (yellow if bright)
34 blue
35 magenta
36 cyan
37 light gray (white if bright)
39 default foreground color

Background colors:
40 black
41 red
42 green
43 brownish
44 blue
45 magenta
46 cyan
47 light gray
49 default background color

My example uses 01 to make the foreground color bright. If you don't want a bright color remove the 01 and the preceding semicolon (e.g., cd=40;33).

Likewise, for the default foreground or background colors, you don't need to use 39 or 49. Instead you may simply not set a foreground or background color by omitting the number and the semicolon (e.g., cd=33).


There does exist a dircolor utility which is helpful if you would like to make a lot of changes to LS_COLORS, but it is overkill if you just want to change a couple of things. It creates a very long string of over a thousand characters for LS_COLORS, some of which just set colors that are default anyway. Better to just set the few that you want to change.

(If you decide to try dircolor, be sure that the version you get isn't newer than your version of ls ("ls --version"). If dircolors is newer it may use new codes that the older ls doesn't understand, and you will get no colors at all.)
Thanks for the info!

I decided to do it this way, in /etc/profile:

Code: Select all

#130224 npierce: fix hard-to-read yellow in white terminal. refer: http://murga-linux.com/puppy/viewtopic.php?t=84298&start=210
#reference: refer http://blog.twistedcode.org/2008/04/lscolors-explained.html
export LS_COLORS='bd=33:cd=33'
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#222 Post by BarryK »

pemasu wrote:I test recompiled 3.8 kernel. I did add bunch of multimedia - dvb drivers. I unticked first the automatic creation button in make menuconfig ....under multimedia ( I dont remember the exact name of that tickable option )....and then I did tick manually the drivers in multimedia section. I got the missing ivtv with hauppage pvr drivers. The problem Billtoo posted.
Brcmsmac was added just by ticking it, since it was now tickable option...due to bcma.ko inclusion.

I provide here the diff comparision of those drivers I was able to add. I am sure there are some multimedia drivers which are not needed, but anyway....there were alot useful drivers left out.

Poulsbo.ko should be left out. It interferes the /kernel/drivers/gpu/drm/gma500/gma500_gfx.ko usage if and when the modesetting_drv.so ( in /usr/lib/x/drivers-alternate ) version 0.6.0 has been added and the cedarview fix pet by 01micko has been added/installed.

As aarf posted. Modesetting for intel atom with gma graphics does not work atm.
pemasu,
Would you mind sending me your .config file?

I'll do another compile of the 3.8.0 kernel.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#223 Post by BarryK »

pemasu wrote:ar5523 is a Linux kernel driver for the Atheros AR5005UG (802.11b/g) and AR5005UX (802.11a/b/g) USB wireless LAN chipsets.

Firmware is required for device operation.

modinfo ar5523
filename: /lib/modules/3.8.0/kernel/drivers/net/wireless/ath/ar5523/ar5523.ko
firmware: ar5523.bin

http://www.ubuntuupdates.org/package/xo ... x-firmware

http://ppa.launchpad.net/xorg-edgers/pp ... 00_all.deb
ar5523: Add firmware for new driver
I hope that firmware is ok.

firmware.dep need again editing and all-firmware possibly new folder for the firmware...or/if how Barry decide with this driver. It is included anyway in the build.

EDIT. Just informational note. New driver:
# modinfo wil6210
filename: /lib/modules/3.8.0/kernel/drivers/net/wireless/ath/wil6210/wil6210.ko
description: Driver for 60g WiFi WIL6210 card

http://wireless.kernel.org/en/users/Drivers/wil6210
Thanks, I have created a PET.

Hopefully I will be able to upload to ibiblio soon.
[url]https://bkhome.org/news/[/url]

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#224 Post by 01micko »

Barry,

Ibiblio seems ok here, just uploaded some sfs.

Actually you may want to link the LibreOffice-4.0.0_en-GB_xz.sfs to your sfs repo.
Puppy Linux Blog - contact me for access

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Precise Puppy 5.5beta

#225 Post by Billtoo »

I did a manual frugal install of my 5493remaster.iso to a hp desktop
pc.
VIDEO REPORT: Precise Puppy, version 5.4.93
Chip description:
VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
24
24
Modules requested to be loaded: dbe
Drivers requested to be loaded: nvidia fbdev vesa
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod glx kbd mouse ramdac record wfb
Actual rendering on monitor:
Resolution: 3840x1080 pixels (1049x292 millimeters)
Depth: 24 planes
OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GT 430/PCIe/SSE2
Version 4.3.0 NVIDIA 310.32
Direct Rendering Yes
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
303 frames in 5.0 seconds = 60.435 FPS
301 frames in 5.0 seconds = 60.002 FPS
301 frames in 5.0 seconds = 60.003 FPS

The proprietary Nvidia driver installed with no problem on this pc.
Attachments
screenshot.jpg
(23.79 KiB) Downloaded 481 times
nvidiascrn.jpg
(64.83 KiB) Downloaded 508 times
Last edited by Billtoo on Sun 24 Feb 2013, 01:25, edited 1 time in total.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#226 Post by BarryK »

mchabez wrote:
Hi everyone, I found another debdb2pupdb bug. It's in 5.4.3, I have to check yet in the 5.5beta.
Some Ubuntu packages have weird dependencies like "udev(>=", "libx11-6(>>" and so on. The root cause is that in the Ubuntu package databases, in the package dependency data, sometimes the dependent package name and version requirement has no space between them.

To check which packages are affected, run this command:
Code:

grep -e "|+.*(.*|" ~/.packages/Packages-ubuntu-*

Edit: Latest Woof as of 21th Feb 2013 also has this bug.
Cross-posting this from the 5.4.3 thread, 5.5beta has this bug, too.
I have hunted through all of the 'precise' and 'precise-updates' pkg database files, and none of them have this problem.

Every db entry has a space between package name and version requirement, also between version operator and version, ex:

udev (>= 2.3

If there are some rogue debs out there with this problem, then the developers should be contacted. It does not affect Woof or the PPM.
[url]https://bkhome.org/news/[/url]

User avatar
tater
Posts: 32
Joined: Sat 29 May 2010, 18:13
Location: Michigan, USA

#227 Post by tater »

@rcrsn51

I have tried all of your codes in YASSM and still no connection to my Samba shares.

I booted puppy pfix=ram in various puppy distros and running Pnethood.

1) lupu 528.005 connected yes
2) precise 5.4.93 connected no
3) puppy 431 connected no
4) puppy 214X connected yes
5) slacko 5.4 connected no

I've also looked at the logs and I can't see why I'm not connecting to my samba shares.

Every thing else in precise 5.4.93 seems great.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#228 Post by rcrsn51 »

@tater: That's too bad. But it sounds to me like you have a different problem than the kernel 3.8 - Samba-TNG issue.

For example, Slacko 5.4 works fine with Samba-TNG without requiring a sec= option.

Run dmesg. Are there any error codes from CIFS?

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#229 Post by pemasu »

pemasu,
Would you mind sending me your .config file?

I'll do another compile of the 3.8.0 kernel.
Sorry that I didnt post it earlier.
Here is it is in attachment. I added those missing multimedia - dvb drivers. Especially support for analog TV is important. The name is misleading. That support creates ivtv driver and also enables several hybrid analog-digital dvb tuner sticks to work ( like mine )
I fixed the brcmsmac support and unticked that overlapping support so that the wireless chip is not recognized by B43 driver. If brcmsmac has been included, that option should be unticked.
I removed poulsbo stub driver ie poulsbo.ko.
Couple of new or missing drivers were added elsewhere, like new staging crs wlan driver....there are posts asking it in the aether. I believe it will need firmware to work.

I confess....I did add samba new SMB2 support in the cifs section. I have used it in my kernels, like 3.6.2 and 3.7.2 and it has not done harm.

Only section which is quite obscure for me is under multimedia: encoders, decoders, sensors and other helper chips. It has decoder modules which are needed and useful like for Hauppage chips and TV watching, but some support are for boards with incorporated chips I am not familiar with.

Also I was afraid that some modules probably have dependency to that section. So....I have enabled most of them. But surely some of them are not so useful. I just dont have experience to mess with them.

I did add also 'usb over ip' - support. There is one pet in the murga-forum utilizing it: http://www.murga-linux.com/puppy/viewto ... d87b9cc3d7
It was fun to test it when rcrsn51 created it. It is also one of the few which have kernel source userspace binary components included. Anyway...it is for single-user usb sharing over ip. ....dont print with other computer attached usb printer with it though. Use Cups printer sharing for that one.
Attachments
DOTconfig-pemasu-3.8.gz
(27.9 KiB) Downloaded 229 times
Last edited by pemasu on Sun 24 Feb 2013, 08:12, edited 5 times in total.

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#230 Post by Sage »

bright yellow on black
Back in 1980, Alan Sugar took best advice on readability, resolution & co. on cga monitors from the world's clinical and optical experts for his upcoming CPC range (Arnold/Joyce were green-screen). All answers came back to him: yellow text on royal blue background. It works for everyone, colour-blind, partially sighted, in bright light, you-name-it.

Still a good combo for troublesome card-monitor-OS systems.

Post Reply