Newyearspup 02 Micro, Mini, Midi, and Maxi RC10
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Try to reconnect your mouse while X is running Xinput hotplug must reconfigure it. If it still refuses to work play around with mouse "protocol" in xorg's config file:iscraigh wrote:A regular mouse works fine in New Years the problem seems to be my wireless microsoft mouse
http://ftp.x.org/pub/X11R7.0/doc/html/mouse.4.html
Another workaround might be to install pciutils from slackware, a new pci.ids file and restart X.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
MU, I can't download puppybasic-2.6 source code from noforum.de (Failed to Connect) , I just wondering if you can upload it to somewhere else or apply the rgba patch to it (in main() and before draw the window):
Code: Select all
/* Set rgba colormap */
GdkScreen *screen = gtk_widget_get_screen(window);
GdkColormap *colormap = gdk_screen_get_rgba_colormap (screen);
if (colormap && gdk_screen_is_composited (screen)){
gtk_widget_set_default_colormap(colormap);
}
/* End set rgba colormap */
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
ok Dave, no problem
I just wanted to explain the differences.
Hope, you have success!
Wow, I attach the recompiled gtkbasic (for /usr/bin/).
I use this ode:
This gets the screen, even if you defined no window yet.
Muppyfiler is transparent then.
Now off to the Javacourse.
Mark
I just wanted to explain the differences.
Hope, you have success!
Wow, I attach the recompiled gtkbasic (for /usr/bin/).
I use this ode:
Code: Select all
/* Set rgba colormap */
GdkScreen *screen = gdk_screen_get_default();
GdkColormap *colormap = gdk_screen_get_rgba_colormap (screen);
if (colormap && gdk_screen_is_composited (screen)){
gtk_widget_set_default_colormap(colormap);
}
/* End set rgba colormap */
Muppyfiler is transparent then.
Now off to the Javacourse.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Mouse Won't Work
Nice! I do have a problem though. The USB mouse doesn't work. I do have a Puppy Exton 2009 installed also and the mouse works there. What can I do?
Thank's to everyone, Barry K.,Lobster, MU, and everyone who have worked for the last few years on the greatest OS i know to date.
Thank's to everyone, Barry K.,Lobster, MU, and everyone who have worked for the last few years on the greatest OS i know to date.
screenshot
Here is my latest look with your new icons and themes:
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Hi Mark,
Couldn't try your suggestion until now. Distracted by other issues this week plus had a strange problem on my test PC.
I have been using Full install up until Wow's message so tried to do a Frugal install but kept getting:
"Error 18" on boot up. Put it down to something wrong on the disk space where this partition resides. Changed partitions and all well.
Okay, made a new install (new save file), frugal this time, and added your deskicons002, rc1-service pack 1 and nvidia-173 pets.
Rebooted.
Selected nvidia-173 driver for the FX5200 card.
(Many thanks for adding a guide on Xorgwizard screen as to what to use where. Very helpful).
This is what I noticed:
1. Selected "LXDE MU with compiz" it went to a white screen. Needed to ctlr+alt+bkspace and run xorgwizard.
2. "LXDE MU" ran okay but screen resolution no higher than 1024x768x52 which seems quite low and there is a continual flicker.
3. Selecting "OpenBox+LXpanel+CairoDock" it runs with some but less flicker but same low-ish resolution.
4. Then I switched off xcompmangr. It still flickers but now LXDE MU +compiz works!!!
Well done Mark!!! Fantastic.
I know Compiz is quite complex and not very intuitive to set up so am not too sure if everything is working...
However so far I have noticed:
5. I am getting a lot of white screen and the edges of many applications aren't there. I think this is termed "Windows decorations." eg the title bar and x,-, + icons at the top right are missing.
6. Some just give a completely white screen. eg "My Documents" "PBurn" and "Preferences>Network Wizard".
7. I have also had instabilities where by selecting an application (sorry can't remember which ones) I get thrown back to the "choose a desktop environment" screen.
I guess it's a setting issue but at least it's working now so nearly there.
In addition:
8. Also noted that if I set up to automount devices on boot-up then selecting the System icon (PCMan file manager) if I right click on a volume to unmount it I get "Unable to unmount...the volume was probably mounted manually on the cmd line"
Whereas if I choose not to auto-mount on reboot then using PCman if I right click on a volume to mount it I get 3 messages:
"unable to mount device..Error, org.freedesktop.hal.device.volume.unknown failure"
I click on Okay and get:
"unable to mount device..."same as before
I click on okay again and get
"Error ..Directory doesn't exit".
9. One small issue: like Dingo 4.1.2 and, I think, other 4.x versions I have had to add "acpi=force" to the kernel line in grub otherwise I can't Power-Off nor will ctlr+alt+backspace exit from X cleanly. I believe it affects SiS chipset mobos mainly.
@Wow:
Thank you for your suggestion. I appreciate your help. Luckily it looks as if MU has now got it working.
@techtype:
Very nice!
For others perhaps it might be helpful if you could tell us which themes, icons etc you used. Although experimentation is always good.
Thanks to all contributors for everything so far.
Dave
Couldn't try your suggestion until now. Distracted by other issues this week plus had a strange problem on my test PC.
I have been using Full install up until Wow's message so tried to do a Frugal install but kept getting:
"Error 18" on boot up. Put it down to something wrong on the disk space where this partition resides. Changed partitions and all well.
Okay, made a new install (new save file), frugal this time, and added your deskicons002, rc1-service pack 1 and nvidia-173 pets.
Rebooted.
Selected nvidia-173 driver for the FX5200 card.
(Many thanks for adding a guide on Xorgwizard screen as to what to use where. Very helpful).
This is what I noticed:
1. Selected "LXDE MU with compiz" it went to a white screen. Needed to ctlr+alt+bkspace and run xorgwizard.
2. "LXDE MU" ran okay but screen resolution no higher than 1024x768x52 which seems quite low and there is a continual flicker.
3. Selecting "OpenBox+LXpanel+CairoDock" it runs with some but less flicker but same low-ish resolution.
4. Then I switched off xcompmangr. It still flickers but now LXDE MU +compiz works!!!
Well done Mark!!! Fantastic.
I know Compiz is quite complex and not very intuitive to set up so am not too sure if everything is working...
However so far I have noticed:
5. I am getting a lot of white screen and the edges of many applications aren't there. I think this is termed "Windows decorations." eg the title bar and x,-, + icons at the top right are missing.
6. Some just give a completely white screen. eg "My Documents" "PBurn" and "Preferences>Network Wizard".
7. I have also had instabilities where by selecting an application (sorry can't remember which ones) I get thrown back to the "choose a desktop environment" screen.
I guess it's a setting issue but at least it's working now so nearly there.
In addition:
8. Also noted that if I set up to automount devices on boot-up then selecting the System icon (PCMan file manager) if I right click on a volume to unmount it I get "Unable to unmount...the volume was probably mounted manually on the cmd line"
Whereas if I choose not to auto-mount on reboot then using PCman if I right click on a volume to mount it I get 3 messages:
"unable to mount device..Error, org.freedesktop.hal.device.volume.unknown failure"
I click on Okay and get:
"unable to mount device..."same as before
I click on okay again and get
"Error ..Directory doesn't exit".
9. One small issue: like Dingo 4.1.2 and, I think, other 4.x versions I have had to add "acpi=force" to the kernel line in grub otherwise I can't Power-Off nor will ctlr+alt+backspace exit from X cleanly. I believe it affects SiS chipset mobos mainly.
@Wow:
Thank you for your suggestion. I appreciate your help. Luckily it looks as if MU has now got it working.
@techtype:
Very nice!
For others perhaps it might be helpful if you could tell us which themes, icons etc you used. Although experimentation is always good.
Thanks to all contributors for everything so far.
Dave
Dave,
as it works better in Ubuntu, we might get help from that.
You might try to copy the /etc/X11/xorg.conf from Ubuntu to Puppy.
Then exit X, and type:
xwin
Maybe it includes some options required by the driver 173.
If that does not help, please attach your /var/log/Xorg.0.log.
Both, the one from Puppy, and that from Ubuntu.
And also xorg.conf from Ubuntu.
I am not certain, that I will find something helpfull in it this time.
But maybe by comparing both, a special setting can be found.
To confgure compiz, you have 2 utilities in the menu, compiz-config to setup effects, and Emerald theme manager, to set up the decor (window-titles and buttons).
Maybe with a different decor you can avoid the white edges.
And use the Gtk-Themeselector, to activate a different Gtk-Theme.
Try those called "norgba". They have no transparency.
Maybe the transparency feature is incompatible with compiz on your card.
It is a bit experimental, also Muppyfiler and the Analogclock work incorrect in compiz, if I compile Gtkbasic with this feature (I attached such a patched Gtkbasic further above on this page).
They show no pictures then, just white areas.
Mark
as it works better in Ubuntu, we might get help from that.
You might try to copy the /etc/X11/xorg.conf from Ubuntu to Puppy.
Then exit X, and type:
xwin
Maybe it includes some options required by the driver 173.
If that does not help, please attach your /var/log/Xorg.0.log.
Both, the one from Puppy, and that from Ubuntu.
And also xorg.conf from Ubuntu.
I am not certain, that I will find something helpfull in it this time.
But maybe by comparing both, a special setting can be found.
To confgure compiz, you have 2 utilities in the menu, compiz-config to setup effects, and Emerald theme manager, to set up the decor (window-titles and buttons).
Maybe with a different decor you can avoid the white edges.
And use the Gtk-Themeselector, to activate a different Gtk-Theme.
Try those called "norgba". They have no transparency.
Maybe the transparency feature is incompatible with compiz on your card.
It is a bit experimental, also Muppyfiler and the Analogclock work incorrect in compiz, if I compile Gtkbasic with this feature (I attached such a patched Gtkbasic further above on this page).
They show no pictures then, just white areas.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
When I try to write to my XP partition in Newyearspup it will not let me, only gives me an error message. NOP 412 and standard Dingo 412 will allow me to write with no issues. I only use XP for X to DVD as I still have some issued with it in Wine.
I haven't found any change in file manager settings. Kind of strange as NOP uses Thunar and Dingo Rox.
I haven't found any change in file manager settings. Kind of strange as NOP uses Thunar and Dingo Rox.
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Hi Mark,
I have tried before to use the Ubuntu xorg.conf file in NYPup but it didn't improve things. Tried again just now and still it makes no
difference. Interestingly the Ubuntu file is much smaller that the puppy one so I assume there are auto detection events going on as well.
The Ubuntu is version 8.10 using xorg 7.4 as well and kernel 2.6.27-11.
Also tried various changes to Emerald and played around with MU-gtk-Themechoser but made no difference either.
I am attaching the ubuntu and puppy xorg.conf and log files in case they can be of help.
However a few of observations:
1. using nv driver I still get some flicker.
2. I can only get it to work setting up from the "select graficsdriver" window if I select the 173 driver (or nv of course.) But I see that,
selecting 173, the nvidia-x server-settings window tells me that it is using the 96.43.09 driver!! I confirm I did load the nvidia-173 pet
you made.
3. The cairo windows are all white when LXDE + Compiz is selected. Otherwise all okay.
Thanks once more.
Dave
I have tried before to use the Ubuntu xorg.conf file in NYPup but it didn't improve things. Tried again just now and still it makes no
difference. Interestingly the Ubuntu file is much smaller that the puppy one so I assume there are auto detection events going on as well.
The Ubuntu is version 8.10 using xorg 7.4 as well and kernel 2.6.27-11.
Also tried various changes to Emerald and played around with MU-gtk-Themechoser but made no difference either.
I am attaching the ubuntu and puppy xorg.conf and log files in case they can be of help.
However a few of observations:
1. using nv driver I still get some flicker.
2. I can only get it to work setting up from the "select graficsdriver" window if I select the 173 driver (or nv of course.) But I see that,
selecting 173, the nvidia-x server-settings window tells me that it is using the 96.43.09 driver!! I confirm I did load the nvidia-173 pet
you made.
3. The cairo windows are all white when LXDE + Compiz is selected. Otherwise all okay.
Thanks once more.
Dave
- Attachments
-
- davesurrey_xorg.tar.gz
- (5.51 KiB) Downloaded 357 times
Dave,
I made a small error in xorgwizard.
If you select the "173" driver, then "96" is installed.
If you select the "96" driver, then "173" is installed.
I will upload an updated pet this evening, when I'm back home.
For now, please try the "96" (which in reality will install the 173).
As you wrote, it will not work, then please do this:
After X fails to start, type:
cp -ax /var/log/Xorg.0.log /root/
Then start X with a working driver, and attach /root/Xorg.0.log here.
This is required to find out, why the 173 driver does not work for you.
Mark
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Hello Mark,
xorg.log file (selecting 96) attached.
HTH
Dave
xorg.log file (selecting 96) attached.
HTH
Dave
- Attachments
-
- Xorg.0.log.tar.bz2
- (2.5 KiB) Downloaded 346 times
Re: screenshot
Which theme did you use to show the drive icons on the desktop?techtype wrote:Here is my latest look with your new icons and themes:
Thanks
Automount
Should the usb bootable version automount all drives?
It appears that only the usb drive is auto-mounted. Not sure if I changed anything, or if it's normal for the auto-mount not to function with a USB bootable.
Thanks for any help
Thom
It appears that only the usb drive is auto-mounted. Not sure if I changed anything, or if it's normal for the auto-mount not to function with a USB bootable.
Thanks for any help
Thom
Re: Automount
I did not heck it with bootable usb-drives.tlchost wrote:Should the usb bootable version automount all drives?
It appears that only the usb drive is auto-mounted. Not sure if I changed anything, or if it's normal for the auto-mount not to function with a USB bootable.
Thanks for any help
Thom
I just use non bootable usb-harddisks, that get mounted.
It basically will mount all drives you see with:
fdisk -l
or
muppyfinddisks -m
----------------------
I updated the nvidia173 pet, now the menu entries in xorgwizard should work as expected.
Now I will have a look at Daves logfiles.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Dave,
your log shows:
Then when X fails, type:
modprobe nvidia
Note down the error you get, please.
And type:
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko
Please note down the number it returns.
And type:
dmesg >/root/dmesg.txt
cp -ax /var/log/messages /root/
Then attach here:
/root/dmesg.txt and
/root/messages
Then try it again, but first type:
depmod -a
But I think, this will not help, it is just a try.
Maybe with the things you note down, I will have a better idea.
Mark
your log shows:
So please again, try this driver.(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0): that the NVIDIA device files have been created properly.
(EE) NVIDIA(0): Please consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
Then when X fails, type:
modprobe nvidia
Note down the error you get, please.
And type:
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko
Please note down the number it returns.
And type:
dmesg >/root/dmesg.txt
cp -ax /var/log/messages /root/
Then attach here:
/root/dmesg.txt and
/root/messages
Then try it again, but first type:
depmod -a
But I think, this will not help, it is just a try.
Maybe with the things you note down, I will have a better idea.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Re: screenshot
No particular theme does it. I created the symlinks myself in "Desktop". That is why the icons for the drives show as folders.tlchost wrote:Which theme did you use to show the drive icons on the desktop?techtype wrote:Here is my latest look with your new icons and themes:
Thanks
Last edited by techtype on Sat 07 Feb 2009, 13:09, edited 1 time in total.
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Hi Mark,
Hope your first week on java was interestng and that I didn't distract you from your studies.
I didn't see any pointer to a new driver-pet that you mentioned so I assumed it was at the same place as the previous one. It had the same name but the MD5 checked out different.
When I originally installed the original driver it said that it was not possible to un-install it. Gave it a try anyway but PetGet took forever and then froze. So installed the new driver over the old one. Hope this was okay.
Or did you mean start afresh with a new install?
Anyway, restarted and did xorgwizard selecting the 173 and it failed to start.
Restarted with the 96 driver and started but nvidia says using 96 driver.
So I assume the selection now does select the driver it says it is going to, but still works only with 96 and not 173. Not sure if that is what you were expecting.
Okay...
modprobe nvidia returns nothing..back to prompt.
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko returns
"7700 /the file above"
Files attached have suffix _first
ie message_first.
Then did xorgwizard with 173 again.
Then did depmod -a
modprobe nvidia returns nothing..back to prompt.
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko returns
"5300....." this time
File saves now have suffix "second"
By the way Ubuntu uses the 173.14.12 driver whereas I see you are using the 173.14.15. It probably is irrelevant but I would prefer to give you too much info than too little.
Enjoy the weekend
Dave
Hope your first week on java was interestng and that I didn't distract you from your studies.
I didn't see any pointer to a new driver-pet that you mentioned so I assumed it was at the same place as the previous one. It had the same name but the MD5 checked out different.
When I originally installed the original driver it said that it was not possible to un-install it. Gave it a try anyway but PetGet took forever and then froze. So installed the new driver over the old one. Hope this was okay.
Or did you mean start afresh with a new install?
Anyway, restarted and did xorgwizard selecting the 173 and it failed to start.
Restarted with the 96 driver and started but nvidia says using 96 driver.
So I assume the selection now does select the driver it says it is going to, but still works only with 96 and not 173. Not sure if that is what you were expecting.
Okay...
modprobe nvidia returns nothing..back to prompt.
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko returns
"7700 /the file above"
Files attached have suffix _first
ie message_first.
Then did xorgwizard with 173 again.
Then did depmod -a
modprobe nvidia returns nothing..back to prompt.
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko returns
"5300....." this time
File saves now have suffix "second"
By the way Ubuntu uses the 173.14.12 driver whereas I see you are using the 173.14.15. It probably is irrelevant but I would prefer to give you too much info than too little.
Enjoy the weekend
Dave
- Attachments
-
- dave.tar.bz2
- (9.56 KiB) Downloaded 288 times
yes, the course is ok, thanks
When I tried to learn Java 10 years ago, I did not undertand it. Meanwhile, thanks to my experience with Perl and C, I find it pretty simple to understand.
Just a pity that it is so huge and slow on older computers, so it is not interesting for Puppy.
It was correct, to install the updated driver over the old one.
Ok, the messages give us important hints.
Maybe it cannot be unloaded?
I vaguely remember, I also had a similar issue once.
You should do:
1.) select in xorgwizard the driver 173.
2.) Try to start X.
3.) when you arrive back at the prompt, type "reboot" or hit CTRL-ALT-DEL.
4.) hope and prey, that after the reboot, xorg works now, as now no old module still is in memory.
5.) If it does not start, type again:
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko
It should return approx. 7700.
6.) I need again then the current dmesg and messages.
Mark
When I tried to learn Java 10 years ago, I did not undertand it. Meanwhile, thanks to my experience with Perl and C, I find it pretty simple to understand.
Just a pity that it is so huge and slow on older computers, so it is not interesting for Puppy.
It was correct, to install the updated driver over the old one.
Ok, the messages give us important hints.
This means, that the 96 kernelmodule still is loaded, when you select the 173 driver.Feb 6 20:49:01 (none) user.warn kernel: NVRM: API mismatch: the client has the version 173.14.15, but
Feb 6 20:49:01 (none) user.warn kernel: NVRM: this kernel module has the version 96.43.09. Please
Feb 6 20:49:01 (none) user.warn kernel: NVRM: make sure that this kernel module and all NVIDIA driver
Feb 6 20:49:01 (none) user.warn kernel: NVRM: components have the same version.
Maybe it cannot be unloaded?
I vaguely remember, I also had a similar issue once.
You should do:
1.) select in xorgwizard the driver 173.
2.) Try to start X.
3.) when you arrive back at the prompt, type "reboot" or hit CTRL-ALT-DEL.
4.) hope and prey, that after the reboot, xorg works now, as now no old module still is in memory.
5.) If it does not start, type again:
du /lib/modules/2.6.27.5/kernel/drivers/video/nvidia.ko
It should return approx. 7700.
6.) I need again then the current dmesg and messages.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
- Posts: 1198
- Joined: Tue 05 Aug 2008, 18:12
- Location: UK
Hi Mark,
And the answer is.......yes, it works!!!!
This is really great.
Just to be specific, if I select driver-173 on reboot it loads the 173-driver as confirmed by the "nvidia X-server settings" app. It offers me resolutions up to 1400x1050.
Unfortunately I still get unacceptable screen flicker at 1024x768 and some other resolutions but it seems fine at 1280x960 so I have selected that; (sorry to mention it again but never had this prob with the ubuntu driver, although it is a diff version of driver they use).
The borderless windows problem is now fixed on all the apps I have tested so far. This makes the whole thing workable now.
There is still a lot I need to experiment with as I am unfamiliar with this WM and many things to learn how to adjust (quite diff from the 412 I am used to)
My main concern is there still seems to be some instability on switching desktops but until I can be more specific I know that general comments
like that are not very helpful.
Many thanks again Mark.
Dave
And the answer is.......yes, it works!!!!
This is really great.
Just to be specific, if I select driver-173 on reboot it loads the 173-driver as confirmed by the "nvidia X-server settings" app. It offers me resolutions up to 1400x1050.
Unfortunately I still get unacceptable screen flicker at 1024x768 and some other resolutions but it seems fine at 1280x960 so I have selected that; (sorry to mention it again but never had this prob with the ubuntu driver, although it is a diff version of driver they use).
The borderless windows problem is now fixed on all the apps I have tested so far. This makes the whole thing workable now.
There is still a lot I need to experiment with as I am unfamiliar with this WM and many things to learn how to adjust (quite diff from the 412 I am used to)
My main concern is there still seems to be some instability on switching desktops but until I can be more specific I know that general comments
like that are not very helpful.
Many thanks again Mark.
Dave