Precise Puppy RC2, October 20, 2012
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Hello 01micko
I tried having a look at what the xorgwizard was doing, as soon as I installed 5.3.91. But my knowledge on linux commands was inadequate.
The Radeon driver works OK as long as I don't run xorgwizard except that it is 16bit colour
If I select Radeon then X does not start because there are no drivers in:
/usr/lib/xorg/modules/drivers.
That is the same a 5.2.60
If I then run xorgwizard and select VESA, X still does not start although vesa_drv is put in the drivers directory.
That is different from 5.2.60 where VESA would work.
I had already saved a renamed version of the xorg log, but I didn't know the commands that I needed to put it outside the save file, so that I could delete the save file and start again.
If you are working on fixing xorgwizard, I'll have another go, but learn a few more commands first.
I tried having a look at what the xorgwizard was doing, as soon as I installed 5.3.91. But my knowledge on linux commands was inadequate.
The Radeon driver works OK as long as I don't run xorgwizard except that it is 16bit colour
If I select Radeon then X does not start because there are no drivers in:
/usr/lib/xorg/modules/drivers.
That is the same a 5.2.60
If I then run xorgwizard and select VESA, X still does not start although vesa_drv is put in the drivers directory.
That is different from 5.2.60 where VESA would work.
I had already saved a renamed version of the xorg log, but I didn't know the commands that I needed to put it outside the save file, so that I could delete the save file and start again.
If you are working on fixing xorgwizard, I'll have another go, but learn a few more commands first.
@LateAdopter
If you choose a driver it seems all other drivers are moved to /usr/lib/x/drivers-alternate. That's where your radeon driver is hiding but still should be selectable from xorgwizard where it will be shifted back to it's usual place of residence.
I had no problem switching to 24 bit colours using xorgwizard in beta5. I chose the "probe" option. I don't know why 16 is the default, in the current Slacko beta we are defaulting to 24. Same kernel series, similar config.
-
@jplt
Thanks for your reports. There is definitely an error relating to the screen mode which shows up in both logs. On some searching I could not find any definitive answer.
If 'vesa' is ok then stick with it, otherwise, I posted the 'nv' driver a few pages back, it should work but the performance will be on a par with 'vesa', depending on your card. You may find it is better.
Alternatively, you could install shinobar's nvidia sfs posted a a few pages back, or shinobar also has an app called 'get_nvidia' which compiles the nvidia driver automatically, however it does require the devx and the kernel source sfs to be installed. You would need to check if your card is supported by the latest nvidia driver.
When release gets closer I can make an nvidia pet, reason I don't right now is in case Barry changes something, then it's a waste of time.
-
I doon't thiink spl chck iz workin
-
I'll attach some of my reports/benchmarks with 16 bit and 24 bit enabled. (radeon)
---------------------------------------------------------------
EDIT.
report-video and glxgears from my main machine with radeon unplugged, using onboard nvidia
# report-video
Precise Puppy, version 5.2.73 on Wed 5 Sep 2012
Chip description:
d.0 VGA compatible controller
NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev
X Server: Xorg
Driver used: vesa
X.Org version: 1.11.3
dimensions: 1366x768 pixels (361x203 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5359 frames in 5.0 seconds = 1071.608 FPS
5364 frames in 5.0 seconds = 1072.773 FPS
If you choose a driver it seems all other drivers are moved to /usr/lib/x/drivers-alternate. That's where your radeon driver is hiding but still should be selectable from xorgwizard where it will be shifted back to it's usual place of residence.
I had no problem switching to 24 bit colours using xorgwizard in beta5. I chose the "probe" option. I don't know why 16 is the default, in the current Slacko beta we are defaulting to 24. Same kernel series, similar config.
-
@jplt
Thanks for your reports. There is definitely an error relating to the screen mode which shows up in both logs. On some searching I could not find any definitive answer.
If 'vesa' is ok then stick with it, otherwise, I posted the 'nv' driver a few pages back, it should work but the performance will be on a par with 'vesa', depending on your card. You may find it is better.
Alternatively, you could install shinobar's nvidia sfs posted a a few pages back, or shinobar also has an app called 'get_nvidia' which compiles the nvidia driver automatically, however it does require the devx and the kernel source sfs to be installed. You would need to check if your card is supported by the latest nvidia driver.
When release gets closer I can make an nvidia pet, reason I don't right now is in case Barry changes something, then it's a waste of time.
-
I doon't thiink spl chck iz workin
-
I'll attach some of my reports/benchmarks with 16 bit and 24 bit enabled. (radeon)
---------------------------------------------------------------
EDIT.
report-video and glxgears from my main machine with radeon unplugged, using onboard nvidia
# report-video
Precise Puppy, version 5.2.73 on Wed 5 Sep 2012
Chip description:
d.0 VGA compatible controller
NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev
X Server: Xorg
Driver used: vesa
X.Org version: 1.11.3
dimensions: 1366x768 pixels (361x203 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5359 frames in 5.0 seconds = 1071.608 FPS
5364 frames in 5.0 seconds = 1072.773 FPS
- Attachments
-
- report.16.txt.gz
- radeon
- (1.63 KiB) Downloaded 267 times
-
- report.24.txt.gz
- radeon
- (6.72 KiB) Downloaded 270 times
Puppy Linux Blog - contact me for access
Hi Lobster,
Generally, to get the XFCE4 desktop started one would type from the prompt:
You can check in usr/bin to see whether or not this file exsists. If it doesn't - where they've gone through several upgrades - then look for a file "xfce4-session" and at the prompt give this a try:
On the latter I'm just guessing as I've never used anything higher in Puppy than version 4.6 and that's always used the former command. However, many are now using the latter command I've discovered and perhaps they've recently changed over to that one for all I know?
If you could let us know how it went for you I personally would appreciate it where I've been assisting someone else on the forum with a plethora of different desktop environments on Precise.
Thanks in Advance Lobster!
Amicalement/Cheers!
Eyes-Only
"L'Peau-Rouge"
Generally, to get the XFCE4 desktop started one would type from the prompt:
Code: Select all
xwin startxfce4
Code: Select all
xwin xfce4-session
If you could let us know how it went for you I personally would appreciate it where I've been assisting someone else on the forum with a plethora of different desktop environments on Precise.
Thanks in Advance Lobster!
Amicalement/Cheers!
Eyes-Only
"L'Peau-Rouge"
*~*~*~*~*~*
Proud user of LXpup and 3-Headed Dog.
*~*~*~*~*~*
Proud user of LXpup and 3-Headed Dog.
*~*~*~*~*~*
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Hello 01micko
Thanks for the suggestion.
You are right that "Probe" will set 24 bit without breaking anything. And it leaves all of the drivers in /usr/lib/xorg/modules/drivers
But if you select "Choose" and "Radeon" then it moves all of the drivers to /usr/lib/x/drivers-backup and there are none in /usr/lib/xorg/modules/drivers. So X won't start.
I notice that you have done a PET for fglrx Catalyst 12.8. If you and BarryK have settled on 3.2.28 kernel, would you be willing to do one for either 12.6 Legacy version or 12.4, please?
The reason I ask is that, by some miracle and going round in a few circles, I have managed to use the PPM to install XBMC-XVBA from the PPA on launchpad.net. And it now works.
It is currently the only media player with direct XVBA GPU acceleration. I would like to test it out, but it needs fglrx.
Thanks
Thanks for the suggestion.
You are right that "Probe" will set 24 bit without breaking anything. And it leaves all of the drivers in /usr/lib/xorg/modules/drivers
But if you select "Choose" and "Radeon" then it moves all of the drivers to /usr/lib/x/drivers-backup and there are none in /usr/lib/xorg/modules/drivers. So X won't start.
I notice that you have done a PET for fglrx Catalyst 12.8. If you and BarryK have settled on 3.2.28 kernel, would you be willing to do one for either 12.6 Legacy version or 12.4, please?
The reason I ask is that, by some miracle and going round in a few circles, I have managed to use the PPM to install XBMC-XVBA from the PPA on launchpad.net. And it now works.
It is currently the only media player with direct XVBA GPU acceleration. I would like to test it out, but it needs fglrx.
Thanks
The command is startxfce4, to log out of xfce4 click just to the right of Applications Menu, there is a small rectangular area with no icon but you can logoff to the prompt there.Lobster wrote:Tried installing xfce from PPM
. . . 'installation' fast
but when I ran 'xwin xfce4' from the prompt - which might be the wrong command . . . I returned to jwm
Then I could not get to the prompt from the keyboard or the menu.
In fact the keyboard was not working at all . . .
ay chihuahua
Lots of icons missing here and there but useable, most all the applications are in the Other section of the menu.
Edit: thunar isn't working, missing libs, guess there's plenty missing.
- Attachments
-
- xfce4scrn.jpg
- (33.72 KiB) Downloaded 954 times
There's a missing GTK icon in the distribution
Both in pmirror and puppy clock
The line of script is
___________________________________________
Both in pmirror and puppy clock
The line of script is
Code: Select all
<input file icon="gtk-open"></input>
___________________________________________
Puppy Backup
When I tried to install puppy backup
I found that the .desktop file had been changed. The category had
been changed from 'Archiving' to 'X-Archiving' .
This prevented the app from displaying in the Start menu.
_______________________________________________________
I found that the .desktop file had been changed. The category had
been changed from 'Archiving' to 'X-Archiving' .
This prevented the app from displaying in the Start menu.
_______________________________________________________
Yozo_office,The Chinese people often use. I use Yozo Office 2009 Professional (Linux) http://en.yozosoft.com/rcrsn51 wrote:Please give an example.tiangeng wrote:Some application printing need RAW,what should I do?
It doesn't make any sense that this product would require RAW printing. That would mean that it can only work with Postscript printers and no other models.tiangeng wrote:Yozo_office,The Chinese people often use. I use Yozo Office 2009 Professional (Linux) http://en.yozosoft.com/rcrsn51 wrote:Please give an example.tiangeng wrote:Some application printing need RAW,what should I do?
What happens if you use the Gutenprint driver?
In the Yozo_office,onclick 'print',the HP5200 nothing happens.rcrsn51 wrote:It doesn't make any sense that this product would require RAW printing. That would mean that it can only work with Postscript printers and no other models.tiangeng wrote:Yozo_office,The Chinese people often use. I use Yozo Office 2009 Professional (Linux) http://en.yozosoft.com/rcrsn51 wrote: Please give an example.
What happens if you use the Gutenprint driver?
I reinstalled the Yozo Office both Racy530 and Precise,then test it.rcrsn51 wrote:What happens if you use Yozo Office with the Gutenprint driver in other Puppies?
make: HP
model: HP LaserJet 5200L - CUPS+Gutenprint v5.2.7
print, Nothing happens. Both Racy530 and Precise.
make: RAW
model: RAW Queue
print, it works.Both Racy530 and Precise.
Yozo Office maybe a bug.
thank you very much!
Another module-loader fix - INVALID, withdrawn!
Barry,
While testing my upgraded HSF modem support, I find that sometimes the HSF modem is discovered on first boot after installation or "pupdial erase", and other times not detected! I added trace logging to backend_modprobe to monitor its actions. I find that the trace log is identical (except for some of the ordering of unrelated events) whether the modem is detected or not. I suspect that the firmware package and extensive file changes made by the pinstall.hsfmodem script do not get made visible to other processes (i.e., /etc/init.d/hsfmodem) by the time they are needed.
I notice that the "backend_modprobe" script does not contain any 'sync' commands. I understand that command to force writing of file changes to the "device", where it becomes visible to all processes. My "rule of thumb" is to use 'sync' after writing a file that is intended to be used by other processes, on the assumption that the changes are visible only to the current process until the kernel decides to flush the buffers. Considering that several seconds appear to elapse before the initialization (init.d) script runs, it appears that the buffers do not get flushed even when the creating process (backend_modprobe's process) ends.
Because of the random nature of the detection/nondetection cases, it is difficult to verify absolutely that adding 'sync' results in success that could also happen by chance. But, since I added it, I have not seen a repeat of the detection failure.
My recommended fix is to add "sync" after the writing of the "lock1" and "protect1" files, and then after writing the "devpath" file. The latter would be effective for the files affected by a firmware package, which is where I suspect the HSF detection problem originates.
I attach a package containing only "backend_modprobe" with the 2 added 'sync' commands, in case anyone wants to try it. To test it, remove the files copied from the appropriate subdirectory in /lib/modules/all-firmware, from wherever they end up (usually /lib/firmware). Also remove /etc/modules/firmware.dep.inst.* (to cause reloading of the "firmware package"), then reboot.
Here is the unified difference listing:
UPDATE 9/10/12: The fix turns out to be associated with the problem, but not as a cure! The 'sync' command should not be used with module loading, at all. Please uninstall the "delta-3c" package if you used it. The problem appears to be caused by 'sync' commands within the HSF package, which are being removed.
While testing my upgraded HSF modem support, I find that sometimes the HSF modem is discovered on first boot after installation or "pupdial erase", and other times not detected! I added trace logging to backend_modprobe to monitor its actions. I find that the trace log is identical (except for some of the ordering of unrelated events) whether the modem is detected or not. I suspect that the firmware package and extensive file changes made by the pinstall.hsfmodem script do not get made visible to other processes (i.e., /etc/init.d/hsfmodem) by the time they are needed.
I notice that the "backend_modprobe" script does not contain any 'sync' commands. I understand that command to force writing of file changes to the "device", where it becomes visible to all processes. My "rule of thumb" is to use 'sync' after writing a file that is intended to be used by other processes, on the assumption that the changes are visible only to the current process until the kernel decides to flush the buffers. Considering that several seconds appear to elapse before the initialization (init.d) script runs, it appears that the buffers do not get flushed even when the creating process (backend_modprobe's process) ends.
Because of the random nature of the detection/nondetection cases, it is difficult to verify absolutely that adding 'sync' results in success that could also happen by chance. But, since I added it, I have not seen a repeat of the detection failure.
My recommended fix is to add "sync" after the writing of the "lock1" and "protect1" files, and then after writing the "devpath" file. The latter would be effective for the files affected by a firmware package, which is where I suspect the HSF detection problem originates.
I attach a package containing only "backend_modprobe" with the 2 added 'sync' commands, in case anyone wants to try it. To test it, remove the files copied from the appropriate subdirectory in /lib/modules/all-firmware, from wherever they end up (usually /lib/firmware). Also remove /etc/modules/firmware.dep.inst.* (to cause reloading of the "firmware package"), then reboot.
Here is the unified difference listing:
Code: Select all
# diff -u /initrd/pup_ro2/sbin/pup_event_backend_modprobe /initrd/pup_rw/sbin/pup_event_backend_modprobe
--- /initrd/pup_ro2/sbin/pup_event_backend_modprobe 2012-08-28 03:25:20.000000000 -0400
+++ /initrd/pup_rw/sbin/pup_event_backend_modprobe 2012-09-06 12:03:01.000000000 -0400
@@ -16,6 +16,7 @@
#120823 rerwin: $FIRMPKG always written.
#120823 rerwin: --use-blacklist to apply the blacklist commands in the configuration files (if any) to module names as well.
#120828 rerwin: --use-blacklist again.
+#120906 rerwin: Add sync after writing lock/protect and devpath files to ensure files and firmware packages seen by all immediately.
export LANG=C
. /etc/rc.d/PUPSTATE
@@ -182,6 +183,7 @@
touch /tmp/pup_event_backend/lock1-${$} #start lock region.
mREGEX=" ${MODULE} "
echo "${$} ${MODULE} " > /tmp/pup_event_backend/protect1-${$}
+sync #120906
for NUM in 1 2
do
SIMULT="`cat /tmp/pup_event_backend/protect1-* | grep "${mREGEX}"`"
@@ -216,6 +218,7 @@
#log to file. rc.sysinit needs this info to find out if any modaliases missed (also above)...
echo "MODULE=$MODULE DEVPATH=$DEVPATH MODALIAS=$MODALIAS" >> /tmp/pup_event_backend/pup_event_module_devpath_log${$}
+sync #120906
cd /sbin #v408 rerwin thinks this is needed for slamr module.
exec /sbin/modprobe $MODULE
Last edited by rerwin on Tue 11 Sep 2012, 13:44, edited 1 time in total.
Address Not Foundrcrsn51 wrote:I have one more suggestion. In Racy, upgrade Ghostscript from here..Yozo Office maybe a bug.
Then try the Gutenprint driver again.
www.datafilehost.com could not be found.
Probably blocked in China.tiangeng wrote:Address Not Foundrcrsn51 wrote:I have one more suggestion. In Racy, upgrade Ghostscript from here..Yozo Office maybe a bug.
Then try the Gutenprint driver again.
www.datafilehost.com could not be found.
Try here.
Puppy Linux Blog - contact me for access
nvidia and radeon
Tried Beta 5 with the Nvidia FX 5200 graphics card. Same results as before with Beta 4 (see also bigpup's report on page 34). Beta 5 boots into a desktop with broken menus and icons due to the nouveau driver.
Banning nouveau by adding nouveau.modeset=0 to the kernel line in grub boots into a perfect desktop with vesa, but too slow (glxgears = ca. 60 fps).
The Nvidia-173 driver compiles, but cannot be installed.
---------
Tried Beta 5 with my ThinkPad R60 (ATI Mobility Radeon X1400). The radeon driver was selected. Once again, very slow (glxgears 60 fps). After about 3 minutes, the display begins to disintegrate (pixels change color), leading to paralysis of the mouse and keyboard. Resurrection with hardware reboot.
Attempt to ban radeon driver with radeon.modeset=0 fails, radeon selected anyway. Attempt to opt out to vesa via xorgwizard also unsuccessful.
Since vesa really does do a reasonably good job for tasks that are not video intensive, assuring that the vesa driver can be installed is rather important. No distribution can be all things for all hardware, but I would be gratified to see performance equal to my main dog, Slacko-5.3.2.7 (kernel 3.1.10), which runs at 350 fps.
Banning nouveau by adding nouveau.modeset=0 to the kernel line in grub boots into a perfect desktop with vesa, but too slow (glxgears = ca. 60 fps).
The Nvidia-173 driver compiles, but cannot be installed.
---------
Tried Beta 5 with my ThinkPad R60 (ATI Mobility Radeon X1400). The radeon driver was selected. Once again, very slow (glxgears 60 fps). After about 3 minutes, the display begins to disintegrate (pixels change color), leading to paralysis of the mouse and keyboard. Resurrection with hardware reboot.
Attempt to ban radeon driver with radeon.modeset=0 fails, radeon selected anyway. Attempt to opt out to vesa via xorgwizard also unsuccessful.
Since vesa really does do a reasonably good job for tasks that are not video intensive, assuring that the vesa driver can be installed is rather important. No distribution can be all things for all hardware, but I would be gratified to see performance equal to my main dog, Slacko-5.3.2.7 (kernel 3.1.10), which runs at 350 fps.