I installed Scribus yesterday, which is a Qt4 desktop publishing application. It is so nice as Qt-based apps now come up with the same theme as GTK apps, makes them look so much better.Billtoo wrote:Installed lots of applications with ppm.
Precise 5.6 is working well, no problems.
Precise Puppy 5.6.1-final, May 29, 2013
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Precise Puppy 5.6-final, May 21, 2013
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Probably there is no clash.peebee wrote:In parallel with BK's changes for nvidia described here, Shinobar has released getnvidia 0.9.2 which creates an sfs which loads successfully onto the current Precise 5.6 and after a reboot the nvidia driver is being used and also is displayed as an option by xorgwizard.
Hopefully the changes made by BK and Shinobar will prove to be complementary....
Cheers
peebee
But, not having looked at what shinobar has done, I cannot be certain.
The latest xorgwizard will work with the official NVIDIA installer, regardless of whether the installation chooses to blacklist the 'nouveau' kernel module or not.
Also, the wizard will now work with NVIDIA PETs that don't do anything to blacklist the nouveau module.
...the above is referring to the very latest xorgwizard-cli script that I have posted about above.
[url]https://bkhome.org/news/[/url]
Further to my earlier post I've put 5.6 on a CD instead of a USB stick but the problem remains (although I can now opt to save to the HD):
Everything works fine but it hangs after X has closed and the saving message is on screen. I've rebooted and tried it with acpi off but no joy. A save file is created but it obviously doesn't get finished properly.
This is on a non-PAE Thinkpad T42 that runs all other versions of Puppy that I've tried to date, right up to the latest Slacko.
Paul
Everything works fine but it hangs after X has closed and the saving message is on screen. I've rebooted and tried it with acpi off but no joy. A save file is created but it obviously doesn't get finished properly.
This is on a non-PAE Thinkpad T42 that runs all other versions of Puppy that I've tried to date, right up to the latest Slacko.
Paul
Yes, I get the black screen AFTER the boot-up.BarryK wrote:Does the black screen occur after the boot-up? That is, do you get all the startup messages, then finally it starts up Xorg and the graphical desktop -- but not in your case, but if you do get the messages right up to that point, then it does mean that Xorg is trying to start.lvds wrote:Hi Barry,
I've tested the new xorg crash recovery mechanism (as explained here)
...tested on my Asus 1225c which is equiped with Atom cedar trails. And it does not work for me. At first pass: black screen. Reboot. Second pass: black screen.The Woof-level notes above state that this pup has a new Xorg Video Wizard and a "recovery mechanism". if you bootup and do not get a graphical desktop, and the keyboard/mouse have hung, which can happen with some troublesome old video hardware, press the 'reset' button on the PC or hold down the 'power' button for 4 seconds to force a shutdown -- at next startup the "recovery mechanism" kicks in, forcing the Xorg Video Wizard to run. Then, you can try an alternate Xorg driver.
As this is a new feature, I welcome feedback, especially tweaks for the /usr/sbin/xorgwizard-cli script, if you know Bash coding!
So far, the only puppies that could boot were Racy v5.5 and upup-precise 3.8.3. These two boots into 1024x768. Then when running xorg video wizard manually and ask for a probe, will allow the 1366x768 ; Important to note: the screen in text mode to chose between probe, test... is too big and goes out of the screen ! So you need to type in blind (enter the first time, because hopefully this is the default, then enter again when the screen resolution is selected) because you don't see the buttons. It seems the issue is common and most people when having video problems get down to 1024x768 so maybe it would be good to adapt the message for that size so anyone can see the buttons to press.
Best regards
Laurent
If you get the black screen earlier, then it would seem that you have an incompatibility with the Linux kernel.
- dennis-slacko531
- Posts: 100
- Joined: Wed 18 Jan 2012, 21:53
- Location: Oregon
- Contact:
I'm mirroring Precise too...
If anyone wants to get the ISO from my Godaddy server, it's pretty fast.
http://www.beok.com/lnux
NICE JOB BARRY -- thanks man
devx_precise_5.6.sfs also ready
fyi, LNUX.COM also has the download & video!
http://www.beok.com/lnux
NICE JOB BARRY -- thanks man
devx_precise_5.6.sfs also ready
fyi, LNUX.COM also has the download & video!
Last edited by dennis-slacko531 on Sat 25 May 2013, 02:23, edited 2 times in total.
Barry, perhaps you have ideas about a problem I've experienced on one
of my computers .... a old Dell Dimension 8200 having a P4 2 ghz cpu and
768 meg RAM. This PC runs earlier pups and Windows XP ok. With later pups
such as your Precise, the machine hangs during the initial startup.
The last screen message is: Recognising media devices... optical input_
I found that pfix=nox on the kernel line gives me a workaround. I can
then run xorgwizard and get a GUI. After creating a Save file, I delete
pfix=nox and the pup then starts up straight to the GUI thereafter (frugal
install).
Art
of my computers .... a old Dell Dimension 8200 having a P4 2 ghz cpu and
768 meg RAM. This PC runs earlier pups and Windows XP ok. With later pups
such as your Precise, the machine hangs during the initial startup.
The last screen message is: Recognising media devices... optical input_
I found that pfix=nox on the kernel line gives me a workaround. I can
then run xorgwizard and get a GUI. After creating a Save file, I delete
pfix=nox and the pup then starts up straight to the GUI thereafter (frugal
install).
Art
Precise Puppy 5.6 Won't Boot in a VirtualBox (Win7 64 Bit)
Hi Guys,
It's my first post on the Puppy forum, firstly my thanks & complete admiration for what you have all achieved, especially Barry K, it's completely awesome...
Anyway, my apologies if this has already been logged as an issue or is otherwise inappropriately filed.
The Isuue:
I tried booting Precise Puppy 5.6 in a VirtualBox (4.2.12) under Win 7 64 bit Ultimate on an HP XW6200 (Dual 3.2 GHz Xeons, 4GB ram, NVidia 9500GT graphics)
It fails during boot on the following step
"Making the Filesystem usable..."
Setting loglevel=7 doesn't display anything after that either.
For reference 5.5.93 didn't boot on the same rig but 5.4.90 did.
Also booting directly from a CD with 5.6 worked.
I'm more than happy to provide further info if that would help.
Thanks again for an amazing demonstration of what collaborative efforts can achieve when people come together. Truly heartening.
It's my first post on the Puppy forum, firstly my thanks & complete admiration for what you have all achieved, especially Barry K, it's completely awesome...
Anyway, my apologies if this has already been logged as an issue or is otherwise inappropriately filed.
The Isuue:
I tried booting Precise Puppy 5.6 in a VirtualBox (4.2.12) under Win 7 64 bit Ultimate on an HP XW6200 (Dual 3.2 GHz Xeons, 4GB ram, NVidia 9500GT graphics)
It fails during boot on the following step
"Making the Filesystem usable..."
Setting loglevel=7 doesn't display anything after that either.
For reference 5.5.93 didn't boot on the same rig but 5.4.90 did.
Also booting directly from a CD with 5.6 worked.
I'm more than happy to provide further info if that would help.
Thanks again for an amazing demonstration of what collaborative efforts can achieve when people come together. Truly heartening.
Poulsbo driver needs work, at least for me... "TEST_X_NOW" results in some sorta logfile that basically means it doesn't like me today. Consistently.
Axiomtek PICO820 motherboard
Atom Z530 CPU
US15W chipset (GMA500)
2gb RAM
SATA (in IDE mode because that's all the board can do) 16gb SSD
Output is VGA
Running from CD with a USB CD setup that the board can handle. I used it to install Upup Precise 3831 (kernel 382 in my version) and it worked fine... of course the glibc in that version of Upup isn't new enough for jejy69's GNOME2.32 SFS... hence the desire to upgrade a little...
Sorry if I sound ticked off, I'm not -- just frustrated and disappointed. I was really hoping this would be working now. Oh well
Axiomtek PICO820 motherboard
Atom Z530 CPU
US15W chipset (GMA500)
2gb RAM
SATA (in IDE mode because that's all the board can do) 16gb SSD
Output is VGA
Running from CD with a USB CD setup that the board can handle. I used it to install Upup Precise 3831 (kernel 382 in my version) and it worked fine... of course the glibc in that version of Upup isn't new enough for jejy69's GNOME2.32 SFS... hence the desire to upgrade a little...
Sorry if I sound ticked off, I'm not -- just frustrated and disappointed. I was really hoping this would be working now. Oh well
report-video for Precise Puppy 5.6-final - success with both nv and
nouveau video driver
When I booted up a fresh frugal install...
and then launching 'xorgwizard-cli'
I installed the nv video driver and rebooted as instructed.
Here is report-video
nouveau video driver
When I booted up a fresh frugal install...
Then I tried booting with pfix=fsck,noxChip description:
VGA compatible controller: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1440x900
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri dri2 exa extmod fb glx kbd mouse record shadowfb
and then launching 'xorgwizard-cli'
I installed the nv video driver and rebooted as instructed.
Here is report-video
__________________________________________________________Chip description:
VGA compatible controller: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Drivers requested to be loaded: nv
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nv
Loaded modules: dbe ddc dri dri2 extmod fb glx i2c int10 kbd mouse ramdac record vgahw xaa
Hi !
Maybe my question is naiv .
To make it clear Precise is an awsome distro .
What makes me wonder is ...when testing Glxgears on Lucid Puppy 528 or Threeheadeddog or Macpup or Dpupexprimo --it gives me ten times higher framerate than on Precise Puppy . I am using a Toshiba 3000 notebook .
Same situation for my Desktop Pc .
What could make the difference ?
How to accomplish same good results with Precise .
Anybody some advice ?
Maybe my question is naiv .
To make it clear Precise is an awsome distro .
What makes me wonder is ...when testing Glxgears on Lucid Puppy 528 or Threeheadeddog or Macpup or Dpupexprimo --it gives me ten times higher framerate than on Precise Puppy . I am using a Toshiba 3000 notebook .
Same situation for my Desktop Pc .
What could make the difference ?
How to accomplish same good results with Precise .
Anybody some advice ?
Last edited by backi on Sat 25 May 2013, 19:21, edited 1 time in total.
To find video driver type in console...backi wrote:it gives me ten times higher framerate than on Precise Puppy
Code: Select all
report-video
You should boot with option 'pfix=nox' and then type 'xorgwizard-cli'
to launch Barry's new xorgwizard. See what video drivers are available.
_________________________________________
Dell D410 problems, partial update
BK wrote: One question, does the problem occur if you choose ext2 for the
save-file?
The problem with not finding the desktop icons (and consequently showing
them as red triangles with a "?" inside) seems to be due to the savefile
existing but not being correct. As soon as I delete the savefile (from
another installed puppy) and reboot into precise-5.6, I'm back to the
first-time boot situation and the desktop icons are there and ok.
To answer your question, the incomplete shutdown problem is the same
whether I choose ext3 or ext2 for the savefile. However, looking at the
savefile, I find that although I always selected 512M for the savefile size,
that wasn't the size I got, which was about 32M for ext3 and about 8M for
ext2. (With the Lucid 511 and 528 installs on the same machine, which
are still there and still work, when one requested 512M, one got 512M
In this particular case, there must be an additional problem with writing
(or reading) the savefile, since even though it's not the size I requested,
the amount of state I was trying to save was tiny - just the timezone
setting. I can't tell if the TZ is restored correctly (until the other problems
get fixed) as I keep my hw clock in local time.
@rjbrewer - thank you for your clue about acpi; I tried applying it naively,
but it didn't work for me. Can someone point me to documentation about
what the acpi status (as read from /var/log/messages and/or the /proc
filesystem) _should be_ to obtain correct shutdown, and what the exact
usage of pfix with grub (0.97) is? I've read the boot message files in the
precise-5.6 iso image, and they are way too terse and incomplete to
include the obscure details which seem to be needed here.
save-file?
The problem with not finding the desktop icons (and consequently showing
them as red triangles with a "?" inside) seems to be due to the savefile
existing but not being correct. As soon as I delete the savefile (from
another installed puppy) and reboot into precise-5.6, I'm back to the
first-time boot situation and the desktop icons are there and ok.
To answer your question, the incomplete shutdown problem is the same
whether I choose ext3 or ext2 for the savefile. However, looking at the
savefile, I find that although I always selected 512M for the savefile size,
that wasn't the size I got, which was about 32M for ext3 and about 8M for
ext2. (With the Lucid 511 and 528 installs on the same machine, which
are still there and still work, when one requested 512M, one got 512M
In this particular case, there must be an additional problem with writing
(or reading) the savefile, since even though it's not the size I requested,
the amount of state I was trying to save was tiny - just the timezone
setting. I can't tell if the TZ is restored correctly (until the other problems
get fixed) as I keep my hw clock in local time.
@rjbrewer - thank you for your clue about acpi; I tried applying it naively,
but it didn't work for me. Can someone point me to documentation about
what the acpi status (as read from /var/log/messages and/or the /proc
filesystem) _should be_ to obtain correct shutdown, and what the exact
usage of pfix with grub (0.97) is? I've read the boot message files in the
precise-5.6 iso image, and they are way too terse and incomplete to
include the obscure details which seem to be needed here.
If you want to compare different Puppies, use the benchmarksbacki wrote:Hi don570 !
Followed your advice (pfix=nox etc. )
used another xorg option with no vesa drivers ...but only increased glxgear rates to some degree but not as high as lucid puppy or Threeheaded Dog .
Is there away to increase Framerates further ?
in menu > hardinfo.
GLXgears is completely meaningless as a benchmark or
performance indicator.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
puppyinstaller has trouble reading GPT partition map
Barry,
New forum member souliaq had trouble installing Puppy on a GPT drive, as reported here: http://www.murga-linux.com/puppy/viewto ... 303#701303
Karl asked for output from the appropriate commands, and based on souliaq's response I suggested a fix here: http://www.murga-linux.com/puppy/viewto ... 919#704919
souliaq has now verified that the suggestion worked: http://www.murga-linux.com/puppy/viewto ... 357#705357
New forum member souliaq had trouble installing Puppy on a GPT drive, as reported here: http://www.murga-linux.com/puppy/viewto ... 303#701303
Karl asked for output from the appropriate commands, and based on souliaq's response I suggested a fix here: http://www.murga-linux.com/puppy/viewto ... 919#704919
souliaq has now verified that the suggestion worked: http://www.murga-linux.com/puppy/viewto ... 357#705357
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: /usr/sbin/loginmanager
But I don't want a user to be able to change back to root without knowing the password.L18L wrote:robwoj44 has not been able to let fido change back to login as root, see http://murga-linux.com/puppy/viewtopic. ... 4&start=45
I have found thatdoes not work at all. fido stays fido.Code: Select all
# echo "$ADMINPASSWORD" | su root
So I tried our (good old ) sudo -A ${0} ${@} ...
... and it works.
Code: Select all
#!/bin/sh #note, root2user called via shutdownconfig, changes root to fido. #110507 TaZOC bug fix. #120201 rodin.s: internationalized. #120323 replace 'xmessage' with 'pupmessage'. #120409 if using minit instead of busybox init. #130523 L18L: HOMEUSER, sudo, without ADMINPASSWORD export TEXTDOMAIN=loginmanager export TEXTDOMAINDIR=/usr/share/locale export OUTPUT_CHARSET=UTF-8 #HOMEUSER="`whoami`" [ "`whoami`" != "root" ] && exec sudo -A ${0} ${@} #130523 HOMEUSER="`grep autologin /etc/inittab | cut -d ' ' -f3`" #130523 [ $HOMEUSER ] || HOMEUSER=$USER #130523 CHANGE2ROOT="" if [ "$HOMEUSER" != "root" ];then # without ADMINPASSWORD CHANGE2ROOT="<text><label>$(gettext 'However, if you wish, you can change to the administrator (root) permanently on the next boot. Just tick this box and it will be so:')</label></text> <checkbox> <label>$(gettext 'Tick box to become administrator permanently')</label> <default>false</default> <variable>CHECKADMIN</variable> </checkbox> <text><label>$(gettext 'This will take affect after reboot.')</label></text> " fi export MAIN_DIALOG=" <window title="LoginManager" icon-name="gtk-execute"> <vbox> <text use-markup="true"><label>"<b>$(gettext 'Currently you are logged in as') '${HOMEUSER}'</b>"</label></text> ${CHANGE2ROOT} <hbox> <button ok></button> <button cancel></button> </hbox> </vbox> </window> " RETSTRING="`gtkdialog3 --program=MAIN_DIALOG --center`" [ $? -ne 0 ] && exit #echo "$RETSTRING" eval "$RETSTRING" [ "$EXIT" != "OK" ] && exit #if [ "$CHANGE2ROOT" != "" ];then if [ "$CHECKADMIN" = "true" ];then # echo "$ADMINPASSWORD" | su root #130523 #if [ $? -ne 0 ];then # pupmessage -bg red -title "$(gettext 'LoginManager: error')" -center "$(gettext 'Sorry, admin password is wrong')" # exit #fi #130523 rootEXPR="s%^tty1.*%tty1::respawn:/sbin/mingetty --autologin root tty1%" sed -i -e "$rootEXPR" /etc/inittab #110507 TaZOC bug fix. #120409 if using minit instead of busybox init... if [ -f /etc/minit/getty/1/params ];then #see my minit pet pkg. EXPR2='s%^fido$%root%' sed -i -e "$EXPR2" /etc/minit/getty/1/params fi pupmessage -bg green -center -title "$(gettext 'Login Manager: OK')" "$(gettext 'Ok, you will be administrator at next boot')" fi #fi
It may be that you have set things up to run Puppy as fido as you may be letting a less-trusted person use your pup.
[url]https://bkhome.org/news/[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: /usr/sbin/loginmanager
The less-trusted person will not know (root's and fido's) password.BarryK wrote:...But I don't want a user to be able to change back to root without knowing the password.
It may be that you have set things up to run Puppy as fido as you may be letting a less-trusted person use your pup.
I hope the following can convince you ...
... that without password it cannot be changed back to autologin as root.console wrote:# whoami
fido
# loginmanager
Sorry, try again.
Sorry, try again.
Sorry, try again.
sudo: 3 incorrect password attempts
#
Anyone have any info on this? Is it specific to my machine and works elsewhere? Can it be fixed, in either case?starhawk wrote:Poulsbo driver needs work, at least for me... "TEST_X_NOW" results in some sorta logfile that basically means it doesn't like me today. Consistently.
Axiomtek PICO820 motherboard
Atom Z530 CPU
US15W chipset (GMA500)
2gb RAM
SATA (in IDE mode because that's all the board can do) 16gb SSD
Output is VGA
Running from CD with a USB CD setup that the board can handle. I used it to install Upup Precise 3831 (kernel 382 in my version) and it worked fine... of course the glibc in that version of Upup isn't new enough for jejy69's GNOME2.32 SFS... hence the desire to upgrade a little...
Sorry if I sound ticked off, I'm not -- just frustrated and disappointed. I was really hoping this would be working now. Oh well