Saluki
Testing Saluki – 020
Manual fugal install to fat32 USB2 flash with syslinux 4.04 boot & ext4 save.
Pets loaded:
Nvidia driver, conky,smplayer & tickr.
In another thread I commented:
http://postimage.org/image/3wybonz3b/
Pets loaded:
Nvidia driver, conky,smplayer & tickr.
In another thread I commented:
Link to full size image:With regard to these pups they both have fantastic merit and IMHO BOTH should become official pups. (Why not two?)
Slacko is likely to appeal more to hardcore enthusiasts and Saluki to newcomers due to its user friendliness and easy configurability.
http://postimage.org/image/3wybonz3b/
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Speaking of Opera, came across a nice little extension called 'Turn off The Lights' https://addons.opera.com/en-gb/extensio ... display=en
Spup Frugal HD and USB
Root forever!
Root forever!
-
- Posts: 106
- Joined: Fri 22 Dec 2006, 08:30
- Location: Rome, Italy
-
- Posts: 106
- Joined: Fri 22 Dec 2006, 08:30
- Location: Rome, Italy
Virtualbox progress
I recreated the virtual machine from scratch, and reinstalled Saluki. It seems that when installing under Virtualbox Saluki chooses to run in Vesa mode (no X). It also starts @ 1600x1200 which is a sort of pain for those of us that have smaller monitor, but this is fixable in the first run dialog).
However I reasoned that maybe it would have been better to have X running before attempting to compile the Guest Additions, so I went to the command prompt and ran xorgwizard. Choosing the Vesa driver was a no go, but Probe, although apparently unsuccessful (it just exits to the prompt), does generate a xorg.conf that actually puts X in a working state - I can run startx, and now in the firstrun panel I see Xorg:Vesa instead of just Vesa, ditto in hwinfo.
Then I redid the GA compile steps, and this time everything went fine: no error messages, no warnings, no rogue modules. So, I rebooted.
After rebooting the status is as follow:
- Virtualbox does acknowledge that the GA are installed (good).
- the video driver is now Xorg:vboxvideo (good)
- the shared folders work (good)
- 3D acceleration is apparently enabled (glxgear does 333 fps) (good)
- the screen can be resized by pulling the borders with the mouse (good)
- mouse integration is still broken and must be disabled - now the mouse does move seamlessly in and out the screen, but clicks in the Saluki screen happen in a random location (not good)
So basically the only things that need to be fixed is mouse integration, then we could collect all the GA files into a nice pet for one-click Virtualbox support...
However I reasoned that maybe it would have been better to have X running before attempting to compile the Guest Additions, so I went to the command prompt and ran xorgwizard. Choosing the Vesa driver was a no go, but Probe, although apparently unsuccessful (it just exits to the prompt), does generate a xorg.conf that actually puts X in a working state - I can run startx, and now in the firstrun panel I see Xorg:Vesa instead of just Vesa, ditto in hwinfo.
Then I redid the GA compile steps, and this time everything went fine: no error messages, no warnings, no rogue modules. So, I rebooted.
After rebooting the status is as follow:
- Virtualbox does acknowledge that the GA are installed (good).
- the video driver is now Xorg:vboxvideo (good)
- the shared folders work (good)
- 3D acceleration is apparently enabled (glxgear does 333 fps) (good)
- the screen can be resized by pulling the borders with the mouse (good)
- mouse integration is still broken and must be disabled - now the mouse does move seamlessly in and out the screen, but clicks in the Saluki screen happen in a random location (not good)
So basically the only things that need to be fixed is mouse integration, then we could collect all the GA files into a nice pet for one-click Virtualbox support...
Re: slimp
That's not a feature slimp has.elroy wrote:anyone know how to create a usable playlist for slimp?
Re: Evince - Comic Book support
These file types open with Evince OOTB, heres some sample files to test it with.jemimah wrote:They should open in evince. I doubt the mime types are there though.josepinto wrote:Hi,
Could comic book support (.cbz and .cbr files) be enable in Saluki.
Is some extra package necessary or only myme types?
José Pinto
http://oldbugs.calibre-ebook.com/raw-at ... 011cbr.cbr
http://oldbugs.calibre-ebook.com/raw-at ... 011cbz.cbz
-
- Posts: 106
- Joined: Fri 22 Dec 2006, 08:30
- Location: Rome, Italy
No, that's for running other OSes inside Puppy, and I am sure it's ok .jemimah wrote:I'm assuming you did try the vitualbox sfs from the repo?
(works fine on puppeee, btw ).
What I'm trying to do is running Saluki as a guest, ie inside another OS (at the moment I am using Win64, but could be anything else). The Guest Additions come with Virtualbox and are supposed to be installed in the guest OS, in order to enable such features as 3d acceleration, shared folders, mouse integration and so on. Without the GA the guest OS runs in a degraded mode and is much less useful/efficient/fun.
Ideally in order to install the GA you just run a script from the Virtualbox supplied iso,but I've seen that working only in Slackware (which is not even in the supported guest OS list, go figure). All the other distros I'm playing with (Mint, Salix, Arch) supply a package that installs the GA without having to jump thru hoops. Mint even figures out it's running in VB and notifies the user to install the GA package, which is a nice touch.
As for Puppy (which btw is a awesome guest system because of speed and small footprint) mileages vary, and you have to create a user, run the compile script and mess around with services and startup files. In some cases you have to do that without being able to use the mouse or see portions of the screen (depends on which puppy you are using, sometime you just get a black screen at first boot, sometimes vesa works fine but X doesn't and so on - the most frequent problem is mouse breakage).
At the moment I only managed to make the GA work reasonably well on the latest Wary, probably because of the older Xorg, with Saluki a close second (everything is fine but mouse integration, on the other hand screen resize works much better...).
I have had no success compiling ATi drivers om 328 kernel. so i will try this when i have time. I have some questions before thoughshevan wrote:for saluki wiki
compiling ati with oficial amd installer
1. wget http://www2.ati.com/drivers/linux/amd-d ... x86_64.run
2. Load SFS - Dev & kernel sources (tested with kernel 3.2.8 which is default)
3. Exit to promt
4. sh amd-driver-installer-12-3-x86.x86_64.run --keep
if compiling fails then
5. cd /lib/modules/fglrx/build_mod/
6. patch -p1 < /path/to/patch
7. ./make.sh
8. cd .. && ./make_install.sh
9. aticonfig --initial
xwin to load desktop. reboot not required
on point 6 : can you put the patch file in the lib/modules/fglrx/build_mod/ folder ?
on point 7: is that all you type : ./make.sh ?
on point 8 : same as 7, i am a linux noob but cd stands for change directory . to where ?
and finaly can you make a SFS or .pet file ?
thanks for the guide, sorry for my noobness
Einar
Isn't fuse something that is needed by ntfs 3g?jemimah wrote:No idea. Barry made the package that way. I'll fix it and see if anything breaks.mavrothal wrote:Out of curiosity, why init.d/fuse is in /sbin?
leftover? magic?...
I do hope you haven't 'fixed' 020 so that you cannot frugal install on ntfs file systems!
I'm not a dev so I may be talking a load of rubbish - on the other hand I might not!
Re: Evince - Comic Book support
Thanks!Geoffrey wrote:These file types open with Evince OOTB, heres some sample files to test it with.jemimah wrote:They should open in evince. I doubt the mime types are there though.josepinto wrote:Hi,
Could comic book support (.cbz and .cbr files) be enable in Saluki.
Is some extra package necessary or only myme types?
José Pinto
http://oldbugs.calibre-ebook.com/raw-at ... 011cbr.cbr
http://oldbugs.calibre-ebook.com/raw-at ... 011cbz.cbz
Gotcha. I will add it to my request list.mdisaster2 wrote:No, that's for running other OSes inside Puppy, and I am sure it's ok .jemimah wrote:I'm assuming you did try the vitualbox sfs from the repo?
(works fine on puppeee, btw ).
What I'm trying to do is running Saluki as a guest, ie inside another OS (at the moment I am using Win64, but could be anything else). The Guest Additions come with Virtualbox and are supposed to be installed in the guest OS, in order to enable such features as 3d acceleration, shared folders, mouse integration and so on. Without the GA the guest OS runs in a degraded mode and is much less useful/efficient/fun.
Ideally in order to install the GA you just run a script from the Virtualbox supplied iso,but I've seen that working only in Slackware (which is not even in the supported guest OS list, go figure). All the other distros I'm playing with (Mint, Salix, Arch) supply a package that installs the GA without having to jump thru hoops. Mint even figures out it's running in VB and notifies the user to install the GA package, which is a nice touch.
As for Puppy (which btw is a awesome guest system because of speed and small footprint) mileages vary, and you have to create a user, run the compile script and mess around with services and startup files. In some cases you have to do that without being able to use the mouse or see portions of the screen (depends on which puppy you are using, sometime you just get a black screen at first boot, sometimes vesa works fine but X doesn't and so on - the most frequent problem is mouse breakage).
At the moment I only managed to make the GA work reasonably well on the latest Wary, probably because of the older Xorg, with Saluki a close second (everything is fine but mouse integration, on the other hand screen resize works much better...).
There is a file firegl_public.c in a folder lib/modules/fglrx/build_mod/, which needs patching.einar wrote: on point 6 : can you put the patch file in the lib/modules/fglrx/build_mod/ folder ?
on point 7: is that all you type : ./make.sh ?
on point 8 : same as 7, i am a linux noob but cd stands for change directory . to where ?
and finaly can you make a SFS or .pet file ?
thanks for the guide, sorry for my noobness
Einar
script make.sh located in the same folder will compile the fglrx.ko module
(./make.sh or sh make.sh to run it)
Then go to the upper directory with command 'cd ..' and you should be in the lib/modules/fglrx/
make_install.sh script install module to the sys folder
Sorry, I can't create a sfs or pet ( I am not that good with puppy yet
I've compiled the new midori against the new webkitgtk-1.8 and it looks promising.
Unfortunately 1.8 won't compile without a glib update - which means it's not backwards compatible.
I'm thinking to postpone the release to wait for xfce 4.10 and the new midori. I'm not keen on maintaining two repos.
I've purchased saluki-linux.com so stay tuned for more info about the new website.
Unfortunately 1.8 won't compile without a glib update - which means it's not backwards compatible.
I'm thinking to postpone the release to wait for xfce 4.10 and the new midori. I'm not keen on maintaining two repos.
I've purchased saluki-linux.com so stay tuned for more info about the new website.
Super cool....jemimah wrote:I've compiled the new midori against the new webkitgtk-1.8 and it looks promising.
Unfortunately 1.8 won't compile without a glib update - which means it's not backwards compatible.
I'm thinking to postpone the release to wait for xfce 4.10 and the new midori. I'm not keen on maintaining two repos.
I've purchased saluki-linux.com so stay tuned for more info about the new website.
Spup Frugal HD and USB
Root forever!
Root forever!
i did it wooptitooo thanks a bunchshevan wrote:There is a file firegl_public.c in a folder lib/modules/fglrx/build_mod/, which needs patching.einar wrote: on point 6 : can you put the patch file in the lib/modules/fglrx/build_mod/ folder ?
on point 7: is that all you type : ./make.sh ?
on point 8 : same as 7, i am a linux noob but cd stands for change directory . to where ?
and finaly can you make a SFS or .pet file ?
thanks for the guide, sorry for my noobness
Einar
script make.sh located in the same folder will compile the fglrx.ko module
(./make.sh or sh make.sh to run it)
Then go to the upper directory with command 'cd ..' and you should be in the lib/modules/fglrx/
make_install.sh script install module to the sys folder
Sorry, I can't create a sfs or pet ( I am not that good with puppy yet
if you have a Ati card, its a must to install these drivers. the defaults that loads in saluki gave me 250 frames per second, these gave me 5700 frames per second in glxgears. and now XBMC 11 is working properly. it was unusable with the default drivers.
quick synergy
i am loving quicksynergy. it is awesome when you have several test machines. is there a way to make it auto start ? and auto use / share ?