Saluki
I admit my mistake...I noticed that even though bluetooth was enabled...I forgot to check that the subsection content was enabled.
They werent. Luckily these bluetooth modules can be compiled afterwards and they are compatible. I have done same mistake before...so I knew I can compile them afterwards. I also checked in Saluki-013 that they load correctly with modprobe.
This pet will install the needed bluetooth modules to the:
/lib/modules/3.2.8-ski/kernel/net/bluetooth under 3 folders, 3 bluetooth needed communication modules alltogether:
bnep.ko, hidp.ko and the most important rfcomm.ko
For those who want to play with bluetooth connections. I know that Jemimah has done it a lot
I am truly sorry of my unforgettable mistake, but I try to correct the failure by posting the solution.
Anyway...Saluki-013 has now been tested for kernel compiling.
They werent. Luckily these bluetooth modules can be compiled afterwards and they are compatible. I have done same mistake before...so I knew I can compile them afterwards. I also checked in Saluki-013 that they load correctly with modprobe.
This pet will install the needed bluetooth modules to the:
/lib/modules/3.2.8-ski/kernel/net/bluetooth under 3 folders, 3 bluetooth needed communication modules alltogether:
bnep.ko, hidp.ko and the most important rfcomm.ko
For those who want to play with bluetooth connections. I know that Jemimah has done it a lot
I am truly sorry of my unforgettable mistake, but I try to correct the failure by posting the solution.
Anyway...Saluki-013 has now been tested for kernel compiling.
- Attachments
-
- bluetooth-modules-k.3.2.8-saluki-0.0.1.pet
- (34.81 KiB) Downloaded 214 times
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
using Saluki-013
tried to use the universal installer
to put the DVD contents on to a USB Flash drive.
Did not work. Told me the DVD files were read only
- does that mean not copyable?
May be an error on the flash drive - gonna try another Puppy
Anyone else try Universal installer with success?
Thanks Jemimah. Improving with each release.
tried to use the universal installer
to put the DVD contents on to a USB Flash drive.
Did not work. Told me the DVD files were read only
- does that mean not copyable?
May be an error on the flash drive - gonna try another Puppy
Anyone else try Universal installer with success?
Thanks Jemimah. Improving with each release.
Re: upgrade
this was because zdrv sfs not found at bootshevan wrote: First I try to boot with my pupsave (it give me a message to update or not)
Seems ok, but there is no network (no etch dev -> no kernel module loaded)
I try then with new pupsave- the same network problem.
I'm doing the wrong things?
I just reinstalled puppy keeping the partition data (no ask for upgrade while running installer?)
About graphic driver - need to reinstall for new kernel.
Is it planned to use more automated tools in next releases?
scsijon wrote:1/ could you explain why you chose to build a preemptive kernel please?
2/ I'm (with 012) having problems with reinstalling grub (legacy) to mbr after 'another linux' overwrote the box with it's. It says it's done it and it's installed a blank set in the right /boot/grub, but it's not booting there, but still in the overwritten place! I'll have another go after food, if no go will go back to wary and try that out.
Will download 13 am tomorrow.
regards
scsijon
re:grub problem, could fix with wary, however your 012grub doesn't seem to be rewriting the mbr if it's already happened before, but no error messages, even when using a console???, sorry.
You want low latency for good multimedia performance."Preemptible Kernel (Low-Latency Desktop) (PREEMPT)
This option reduces the latency of the kernel by making
all kernel code (that is not executing in a critical section)
preemptible. This allows reaction to interactive events by
permitting a low priority process to be preempted involuntarily
even if it is in kernel mode executing a system call and would
otherwise not be about to reach a natural preemption point.
This allows applications to run more 'smoothly' even when the
system is under load, at the cost of slighly lower throughput
and a slight runtime overhead to kernel code.
Select this if you are building a kernel for a desktop or
embedded system with latency requirements in the milliseconds
range.
Legacy grub is not supported - only grub4dos.
I think the headers are there, reboot and try again. Some environment variables do not get set until after a reboot.mavrothal wrote:Saluki013 looks very nice.
I would think however that makes more sense for custom_builder to be in the base instead of adrv. So starting with the minimum you build what you need.
Also looks like that X dev files are left out of the devx again. Compailing a driver I get:Finally, looks like that jwm files in /etc/xdg/templates/ jwm-xdgmenu and .jwmrc is still there.Code: Select all
configure: error: Package requirements (xorg-server, xproto xvmc fontsproto ) were not met: No package 'xorg-server' found No package 'xproto' found No package 'xvmc' found No package 'fontsproto' found
BTW what IceWM config files are doing in the build?
The jwm and icewm config files are part of a combination xdg package that needs to stay.
Re: upgrade
I just rename the save file to something like old.4fs and update the frugal install. You might need to run grub4dos again after the update.shevan wrote:Hi to all
How is it right to upgrade my frugal instalation (ext3 partition)?
1. burn iso to cd/usb, then upgrade using universal installer
or
2. just extract iso contents and replace files on partition
How to deal with save file in both situations?
thanks
If you want to try an upgrade, then don't rename the save file. But upgrading isn't all that reliable.
Thanks. I'll add these to the next release.pemasu wrote:I admit my mistake...I noticed that even though bluetooth was enabled...I forgot to check that the subsection content was enabled.
They werent. Luckily these bluetooth modules can be compiled afterwards and they are compatible. I have done same mistake before...so I knew I can compile them afterwards. I also checked in Saluki-013 that they load correctly with modprobe.
This pet will install the needed bluetooth modules to the:
/lib/modules/3.2.8-ski/kernel/net/bluetooth under 3 folders, 3 bluetooth needed communication modules alltogether:
bnep.ko, hidp.ko and the most important rfcomm.ko
For those who want to play with bluetooth connections. I know that Jemimah has done it a lot
I am truly sorry of my unforgettable mistake, but I try to correct the failure by posting the solution.
Anyway...Saluki-013 has now been tested for kernel compiling.
i trying demo pdf-cube, its work..jemimah wrote:Lucky 13 has been released.
New in 013:
new kernel
Thunar archiver plugin
many new plugins for gstreamer
saluki custom puplet builder
pdf-cube
lsalarm
various fixes and enhancement
but i try to open my pdf file, its not working..
thanks jemimah..
this my report video
# report-video
Saluki, version 013 on Sun 4 Mar 2012
Chip description:
2.0 VGA compatible controller
Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
oem: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS
product: Intel(r) 82945GM Chipset Family Graphics Controller Hardware Version 0.0
X Server: Xorg
Driver used: intel
X.Org version: 1.11.0
dimensions: 1280x800 pixels (338x211 millimeters)
depth of root window: 24 planes
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Saluki update report
My Dell Pentium M Dell D610, old as it is, must be in the sweet spot for Saluki. 013 run pfix=ram, save file updated and run with and without Adrive. No issues at all with the kernel change. Wireless, panels, themes, fonts backgrounds all handled flawlessly. On rebooting without Adrive after running with, in a quick look, I now found no stranded directories, themes etc.
# report-video
VIDEO REPORT: Saluki, version 013
Chip description:
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
Driver used by Xorg:
intel
Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"
A plug here for grub4dos. Once installed (in my case on an ide cf card), it makes it very easy to fold in an upgrade, run it as pfix=ram for a reality check, then update the save file and slowly phase out the previous version. The menu.lst is pretty much self explanatory.
# report-video
VIDEO REPORT: Saluki, version 013
Chip description:
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
Driver used by Xorg:
intel
Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"
A plug here for grub4dos. Once installed (in my case on an ide cf card), it makes it very easy to fold in an upgrade, run it as pfix=ram for a reality check, then update the save file and slowly phase out the previous version. The menu.lst is pretty much self explanatory.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
ati amd installer not working for me
amd-driver-installer-12-1-x86.x86_64.run
devx_luki_013.sfs & kernel_sources-3.2.8-ski.sfs loaded
(md5sum successfull checked)
error log /usr/share/ati/fglrx-install.log
driver run without any errors on Saluki 0.12 with 2.6.39-ski kernel
amd-driver-installer-12-1-x86.x86_64.run
devx_luki_013.sfs & kernel_sources-3.2.8-ski.sfs loaded
(md5sum successfull checked)
error log /usr/share/ati/fglrx-install.log
Code: Select all
Uninstalling any previously installed drivers.
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Error] Kernel Module : Kernel module build environment not found - please consult readme.
Loading onto an USB Dongel
Hi All
@Lobster
Is it the old permissions problem identified by Shinobar well over a year ago?
Have you tried to run bootflash from the console?
If it fails to run do as Shinobar says, change the permissions of /tmp by typing in the console:
chmod -R 1777 /tmp
and then try again with bootcamp.
Cheers
@Lobster
Is it the old permissions problem identified by Shinobar well over a year ago?
Have you tried to run bootflash from the console?
If it fails to run do as Shinobar says, change the permissions of /tmp by typing in the console:
chmod -R 1777 /tmp
and then try again with bootcamp.
Cheers
I've successfully upgraded to 013 (frugal install) and decided to test out the Saluki Custom Puplet Builder with 013. I removed a few things and added a few things. I used my own 012 save file (not with adrive, just as a savefile) because I really liked the setup I have (transparent panel bar, custom clock font colors, custom wallpaper, links, etc). Anyways, it was easily and automatically upgraded to 013. Everything went swimmingly until I rebooted; the xfce window manager loaded (desktop and wallpaper), but while Frisbee was doing it's thing (popup notifications), I got kicked out to the terminal with the prompt "puppy1365 login as root". I tried again without a save file but had the same result (I did not have this problem with the included adrive file for 013, only with my custom adrive). So I removed a package that I had installed with my custom adrive that I suspected may be the culprit, remade the custom adrive - and sure enough, it was Compiz-0.8.4-test.pet. I removed it, re-created my custom adrive without it, and everything worked fine after that. So, that's my Compiz-0.8.4-test.pet story, and I'm sticking to it...granted it does have "test" in its' name, so therefore I cannot be too heartbroken because of it. Either way, I thought it might be valuable to pass this along...