Saluki
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
nouveau is the one that works for me. nv failed.
By the way, my .pet for Scratch seems to work fine on Saluki.
Do you think I should re-build it from Saluki, or do you want to test it to check if it is okay as it is?
Scratch is used a lot in UK schools to teach kids basic programming.
Scratch-1.4
By the way, my .pet for Scratch seems to work fine on Saluki.
Do you think I should re-build it from Saluki, or do you want to test it to check if it is okay as it is?
Scratch is used a lot in UK schools to teach kids basic programming.
Scratch-1.4
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
- minesadorada
- Posts: 68
- Joined: Sun 11 Sep 2011, 19:10
I fired up Saluki 14 as a frugal install.
Quad-core/16GB RAM desktop machine with many hard disks.
Good first impressions, but as a distro ostensibly aimed at ex-windows users it was puzzling to access the hard drives, and it took a while before discovering the icon on the system tray.
Is there an absolutely compelling reason for drives to be labelled 'sda1, sb1, sdc' etc
Would it be a terrible thing is Saluki displayed the drives as 'C, D, E' etc?
Would it be a terrible thing if Saluki alone had a 'My Computer' icon which when clicked mimicked the drives icon in the system tray?
This is not a complaint - merely a suggestion. As a new Puppy user of course I now have no problem with the Linux conventions, and I appreciate the unpaid work puppy distro-developers do.
Sometimes though, a good idea is simply a good idea. Microsoft's 'My Computer' desktop icon is simply a good idea worth copying IMO.
I really like the way mounted drives are displayed in file save/open dialogs. A big step forward for puppy IMO.
Quad-core/16GB RAM desktop machine with many hard disks.
Good first impressions, but as a distro ostensibly aimed at ex-windows users it was puzzling to access the hard drives, and it took a while before discovering the icon on the system tray.
Is there an absolutely compelling reason for drives to be labelled 'sda1, sb1, sdc' etc
Would it be a terrible thing is Saluki displayed the drives as 'C, D, E' etc?
Would it be a terrible thing if Saluki alone had a 'My Computer' icon which when clicked mimicked the drives icon in the system tray?
This is not a complaint - merely a suggestion. As a new Puppy user of course I now have no problem with the Linux conventions, and I appreciate the unpaid work puppy distro-developers do.
Sometimes though, a good idea is simply a good idea. Microsoft's 'My Computer' desktop icon is simply a good idea worth copying IMO.
I really like the way mounted drives are displayed in file save/open dialogs. A big step forward for puppy IMO.
Last edited by minesadorada on Tue 13 Mar 2012, 20:32, edited 1 time in total.
A little graphics comparison.....
Saluki 014 live pfix=ram. Booted to an incorrect 1280x1024 resolution. Used xorgwizard from first run to achieve desired 1366x768.
# report-video
Saluki, version 014 on Tue 13 Mar 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: nouveau
X.Org version: 1.11.0
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
Latest Slacko 5.3.2.7 live pfix=ram.Booted to the correct 1366x768 resolution.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 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: nouveau
X.Org version: 1.9.5
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
Latest Exprimo 5.X.3.2.9.2 live pfix=ram. Booted to the correct 1366x768 resolution.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
d.0 VGA compatible controller
nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
X Server: Xorg
Driver used: nv
X.Org version: 1.7.7
dimensions: 1368x768 pixels (414x232 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
Saluki 014 live pfix=ram. Booted to an incorrect 1280x1024 resolution. Used xorgwizard from first run to achieve desired 1366x768.
# report-video
Saluki, version 014 on Tue 13 Mar 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: nouveau
X.Org version: 1.11.0
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
Latest Slacko 5.3.2.7 live pfix=ram.Booted to the correct 1366x768 resolution.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 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: nouveau
X.Org version: 1.9.5
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
Latest Exprimo 5.X.3.2.9.2 live pfix=ram. Booted to the correct 1366x768 resolution.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
d.0 VGA compatible controller
nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
X Server: Xorg
Driver used: nv
X.Org version: 1.7.7
dimensions: 1368x768 pixels (414x232 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
Fedora 16 live pfix=ram. Booted to the correct 1366x768 desktop. And I can't stand Gnome 3.
X.Org X Server 1.11.1
Release Date: 2011-09-24
[ 61.425] X Protocol Version 11, Revision 0
[ 61.425] Build Operating System: x86-04 2.6.32-131.2.1.el6.x86_64
[ 61.425] Current Operating System: Linux localhost.localdomain 3.1.0-7.fc16.i686 #1 SMP Tue Nov 1 21:00:16 UTC 2011 i686
[ 61.425] Kernel command line: initrd=initrd0.img root=live:CDLABEL=Fedora-16-i686-Live-Desktop.iso rootfstype=auto ro liveimg quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0
[ 61.425] Build Date: 26 September 2011 06:32:25PM
[ 61.425] Build ID: xorg-x11-server 1.11.1-1.fc16
[ 61.425] Current version of pixman: 0.22.2
X.Org X Server 1.11.1
Release Date: 2011-09-24
[ 61.425] X Protocol Version 11, Revision 0
[ 61.425] Build Operating System: x86-04 2.6.32-131.2.1.el6.x86_64
[ 61.425] Current Operating System: Linux localhost.localdomain 3.1.0-7.fc16.i686 #1 SMP Tue Nov 1 21:00:16 UTC 2011 i686
[ 61.425] Kernel command line: initrd=initrd0.img root=live:CDLABEL=Fedora-16-i686-Live-Desktop.iso rootfstype=auto ro liveimg quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0
[ 61.425] Build Date: 26 September 2011 06:32:25PM
[ 61.425] Build ID: xorg-x11-server 1.11.1-1.fc16
[ 61.425] Current version of pixman: 0.22.2
A bit older Nvidia graphics card.
Saluki 014 live pfix=ram. Booted to a black desktop with a monitor out of range message. Heard the bark but missed out on first run settings. Three- finger-salute to xorgwizard, probe and got desired 1440x900 resolution.
# report-video
Saluki, version 014 on Mon 12 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 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
Slacko 5.3.2.7 live pfix=ram. Booted straight to the correct 1440x900 resolution. Sound and internet good ootb.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: nouveau
X.Org version: 1.9.5
dimensions: 1440x900 pixels (380x238 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
Exprimo 5.3.2.9.2 live pfix=ram. Boots straight to the correct 1440x900 desktop.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: is
X.Org version: 1.7.7
dimensions: 1440x900 pixels (380x238 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
Actually using the "nv" driver.
VGA compatible controller : nVidia Corporation G98 [GeForce 8400 GS]
Time for a break.......
Saluki 014 live pfix=ram. Booted to a black desktop with a monitor out of range message. Heard the bark but missed out on first run settings. Three- finger-salute to xorgwizard, probe and got desired 1440x900 resolution.
# report-video
Saluki, version 014 on Mon 12 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 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
Slacko 5.3.2.7 live pfix=ram. Booted straight to the correct 1440x900 resolution. Sound and internet good ootb.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: nouveau
X.Org version: 1.9.5
dimensions: 1440x900 pixels (380x238 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
Exprimo 5.3.2.9.2 live pfix=ram. Boots straight to the correct 1440x900 desktop.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation G98 [GeForce 8400 GS] (rev a1)
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev
X Server: Xorg
Driver used: is
X.Org version: 1.7.7
dimensions: 1440x900 pixels (380x238 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
Actually using the "nv" driver.
VGA compatible controller : nVidia Corporation G98 [GeForce 8400 GS]
Time for a break.......
Re: Python 3.1.4 with Pygame .pet
The dependencies look good except I don't think you should put any spaces between them.antiloquax wrote:Here's my .pet for Python 3.1.4 with Pygame.
No menu, but typing "python3" or "idle3" at the console will take you to the Python prompt or shell.
I've not included the Pygame "examples" folder - hope that is okay.
I plan to have a go at pygame for the Saluki version of Python2.7, maybe tomorrow.
You need tk, tcl and all the SDL bits. I have put them in dependencies list (hope I did it right!)
Python 3.1.4
Would it be much trouble to build it with '--prefix=/usr'? I like to reserve /usr/local for users if at all possible.
This is good. I have added it to the repo.antiloquax wrote:Here's my .pet for pygame in Python2.7.
You'll need the Saluki Python2.7, python-tk, tk, tcl, and all the SDL bits.
Pygame for Python2.7.2
I did strip the libs.
For python2 the dependency should be "+Python". I think I'll name python 3 "+Python3" to keep them separate.
This is now fixed in the repo.jemimah wrote:Ok, I will take care of this tonight.Tman wrote:I don't think uzbl is ready for general use, as I haven't figured out how to get the key bindings working, so you can surf, but the keyboard functions don't seem to be working (not very useful atm)..I'm taking a look at /root/.config/uzbl/config , trying to figure it out.jemimah wrote: I've uploaded this to the repo.
EDIT: okay, the website says it needs xclip installed for keybindings to work, but something is still wrong...
Okay, I figured it out...the first lines in uzbl-event-manager and uzbl-tabbed needed to be changed from "env python2" to
"env python". I don't know why that is, becuase python2 is installed in Saluki, but it works now.
Jemimah, please remove the old Uzbl pet from the repo. The keyboard functions work with this one out of the box...
I may make a new pet with a custom uzbl homepage, for easier use in the future.
-
- Posts: 7
- Joined: Fri 06 Aug 2010, 17:05
- Location: middleofnowheretexas
Loaded saluki 011 on my old HP dv1000 laptop and it works like it was custom made for it. Added Clementine music player deleted xnoise, added firefox 10 deleted midori, added vlc. All programs added are working perfectly. Cricket usb a600 modem working fine. Loaded saluki 013 on my hp pavillion 3200+ desktop works good except rear sound with soundblaster audigy se. Have tried most of the suggestions in murga forums. If anyone knows how to get 5.1 sound working with clementine please guide me in the right direction. Saluki looks like a real gem. Thanks to all involved...
@Tman,Geoffrey wrote:AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ : 2310.33MHzTman wrote:Geoffery,
I am not sure if this is a factor or not, but I am curious; what cpu do you have? And I always choose the Nvidia driver manually, after I install the pet; Xorgwizard sometimes chooses the wrong driver.
Thanks James..I guess it's a Midori thing. Okay I'll stop complaining about Midori now, lest I incur someone's wrath.. yikes!
VGA compatible controller : nVidia Corporation G84 [GeForce 8600 GT]
-OpenGL-
Vendor : NVIDIA Corporation
Renderer : GeForce 8600 GT/PCI/SSE2/3DNOW!
Version : 3.3.0 NVIDIA 290.10
Direct Rendering : Yes
glxgears
22829 frames in 5.0 seconds = 4565.664 FPS
23525 frames in 5.0 seconds = 4703.248 FPS
23963 frames in 5.0 seconds = 4792.497 FPS
23523 frames in 5.0 seconds = 4704.451 FPS
I need to try the 290.20 driver to compare
Well, I tried installing the NVIDIA-Linux-x86-290.20.run and I get the same result as the the pet package, a total lockup when running glxgears.
The GeForce 8600 GT is stable using the NVIDIA-Linux-x86-290.10.run driver.
This looks fun but it complains about missing libpulse-simple and libv4l2. So it should probably get recompiled.antiloquax wrote:nouveau is the one that works for me. nv failed.
By the way, my .pet for Scratch seems to work fine on Saluki.
Do you think I should re-build it from Saluki, or do you want to test it to check if it is okay as it is?
Scratch is used a lot in UK schools to teach kids basic programming.
Scratch-1.4
Quick tip: if you want to rename the package, you should rename the directory before running dir2pet. Otherwise the pet.spec file has wrong information in it and I think it results in pets to can't be uninstalled properly.
One last comparison test with an older Nvidia card on my main Linux box.
Saluki 014 live pfix=ram. Booted to 1280x1024 and used xorgwizard from first run to get desired 1440x900.
# report-video
Saluki, version 014 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 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
Slacko 5.3.2.7 live pfix=ram. Booted straight to the correct 1440x900 desktop.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.9.5
dimensions: 1440x900 pixels (380x238 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
Exprimo 5.X.3.2.9.2 live pfix=ram. Booted straight to the correct 1440x900 desktop.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: is
X.Org version: 1.7.7
dimensions: 1440x900 pixels (411x263 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
Saluki 014 live pfix=ram. Booted to 1280x1024 and used xorgwizard from first run to get desired 1440x900.
# report-video
Saluki, version 014 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 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
Slacko 5.3.2.7 live pfix=ram. Booted straight to the correct 1440x900 desktop.
# report-video
Slacko Puppy, version 5.3.2.7 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.9.5
dimensions: 1440x900 pixels (380x238 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
Exprimo 5.X.3.2.9.2 live pfix=ram. Booted straight to the correct 1440x900 desktop.
# report-video
Dpup Exprimo, version 5.X.3.2.9.2 on Tue 13 Mar 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: is
X.Org version: 1.7.7
dimensions: 1440x900 pixels (411x263 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
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Re: Python 3.1.4 with Pygame .pet
Thanks Jemimah - I'll re-do this pet when I get a chance.jemimah wrote: The dependencies look good except I don't think you should put any spaces between them.
Would it be much trouble to build it with '--prefix=/usr'?
Glad that one was okay. Sorry, but what do you mean by "strip the libs"?I did strip the libs.
For python2 the dependency should be "+Python". I think I'll name python 3 "+Python3" to keep them separate.
Right - I'll have a look at this too! Thanks for the advice.jemimah wrote: This looks fun but it complains about missing libpulse-simple and libv4l2. So it should probably get recompiled.
Quick tip: if you want to rename the package, you should rename the directory before running dir2pet. Otherwise the pet.spec file has wrong information in it and I think it results in pets to can't be uninstalled properly.
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
Well, James, after all that testing, sadly the result is incontravertible - there's something different about Saluki ! It's the only one that consistently boots into the wrong default resolution. Same result that I reported using less rigourous methods, although long and bitter experience with masses of HW tends to let one sniff a wrong 'un at an early stage.
For anyone coming into this game afresh, it's a show stopper. Could be worse - could deflect interest away from other Puppies and that would frustrate the efforts of a bunch of hard working developers.
Black screens, video cards, monitors, etc may bore the pants of some, but, at the moment, it's the most important issue confronting the breed.
For anyone coming into this game afresh, it's a show stopper. Could be worse - could deflect interest away from other Puppies and that would frustrate the efforts of a bunch of hard working developers.
Black screens, video cards, monitors, etc may bore the pants of some, but, at the moment, it's the most important issue confronting the breed.
Indeed hardware compatibility hits you way before interface usability/package availability.Sage wrote:Black screens, video cards, monitors, etc may bore the pants of some, but, at the moment, it's the most important issue confronting the breed.
Saluki may choose to focus only on machines that work or rediscover the wheel as luci, slacko, exprimo, fatdog, etc before it.
Maybe is time for a coherent, collaborative, development model (git/subversion/mercurial) with "clear" commits, branches, pulling, merging, etc?...
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Saluki 14 - wine, icewm, compiz
I am testing the new Saluki 14 on my AsusEEE 1215n
I like what I see! Some small things:
Wine 1.4 does not automatically install all its missing libs yet
I am not sure if I want to make the transition from icewm to xfce. Is there a version of icewm recommended for this puplet?
OTOH - xfce is able to work with compiz right? I know it is pure eye candy but it looks nice. What do I need to install to get compiz (rotating desktop cube!) working in Saluki?
I like what I see! Some small things:
Wine 1.4 does not automatically install all its missing libs yet
I am not sure if I want to make the transition from icewm to xfce. Is there a version of icewm recommended for this puplet?
OTOH - xfce is able to work with compiz right? I know it is pure eye candy but it looks nice. What do I need to install to get compiz (rotating desktop cube!) working in Saluki?
Just took saluki for a test drive on my toshiba nb200 (standard atom 10 inch netbook). All hardware appears to work! Some initial thoughts:
- Splash screens that pop up are a bit obtrusive, especially listing all the partitions etc.
- The mouse is enormous
- starting frisbee from the control panel, managed to open up two instances. Both running in the tray. This should be avoided I think.
- configuring wireless in frisbee, informed me that it failed. Seconds later got an IP assigned and everything works.
- can't change mouse speed / accelleration either using gui or xset. Both don't work.
- I created a desktop icon (using right mouse click, send to > desktop, I think??) to a script, which runs the opera browser. (/home/opera-11.blah/opera). Clicking it on the desktop does nothing. The script does work if clicked directly.
- managing of mounting/unmounting: Would be nice if could open each partition in file manager from the tray once mounted.
I have to say, my compliments on a nice looking puppy! I think good choice of default desktop environment (although personally prefer rox/icewm). May try out the remaster script later.
-Thomas
- Splash screens that pop up are a bit obtrusive, especially listing all the partitions etc.
- The mouse is enormous
- starting frisbee from the control panel, managed to open up two instances. Both running in the tray. This should be avoided I think.
- configuring wireless in frisbee, informed me that it failed. Seconds later got an IP assigned and everything works.
- can't change mouse speed / accelleration either using gui or xset. Both don't work.
- I created a desktop icon (using right mouse click, send to > desktop, I think??) to a script, which runs the opera browser. (/home/opera-11.blah/opera). Clicking it on the desktop does nothing. The script does work if clicked directly.
- managing of mounting/unmounting: Would be nice if could open each partition in file manager from the tray once mounted.
I have to say, my compliments on a nice looking puppy! I think good choice of default desktop environment (although personally prefer rox/icewm). May try out the remaster script later.
-Thomas
[color=green]An expert is just a beginner with experience.[/color]
Shamelessly representing [url=http://www.tdem.co.nz]TdeM[/url]!
Shamelessly representing [url=http://www.tdem.co.nz]TdeM[/url]!
Great, thank you. So it is the Nvidia driver itself then that is having problems with your hardware. I will package an older Nvidia driver at a later date, for you to try.Geoffrey wrote:Geoffrey wrote: @Tman,
Well, I tried installing the NVIDIA-Linux-x86-290.20.run and I get the same result as the the pet package, a total lockup when running glxgears.
The GeForce 8600 GT is stable using the NVIDIA-Linux-x86-290.10.run driver.