The K2.6.39.4(PAE), was it compiled by you or originally by BK? The reason I ask is that (now, quite) a while ago I attempted to recompile it with the only compile-time change as to make it non-PAE; wouldn't even boot .

Yes, I do run the K2.6.39.4 slackos, due to highly(?) improved graphics compared to K2.6.37 - yes, BROOKDALE, but would, just for the sake of it , like to run this, more modern kernel, in a non-PAE fashion.

The K2.6.39.4(PAE), was it compiled by you or originally by BK? The reason I ask is that (now, quite) a while ago I attempted to recompile it with the only compile-time change as to make it non-PAE; wouldn't even boot

Me. The DOTconfig is in /etc/modules, I guess you know

I compiled in a full install using BK's exact instruction for 2.6.39.4 but I altered the kernel configuration to add some scsi drivers suggested by tempestuous and something else I forget, anyways you can diff mine as is to BK's. PAE should be easy to turn off. BTW, I use Xconfig as my full install of the early alpha 130 or sumthing ( ) is still rock solid with kde4 and I'm lazy! It's had a about 10 different kernels , each worked ok, except an early attempt where I did something realy, really stoopid (re some thread by l0wt3ch, too lazy to find link )

Hi. I downloaded Slacko and created a bootable USB stick. I am using it on an older laptop without a hard drive. When I first booted with Slacko, the sound worked fine on the computer. At some point the sound stopped working. The volume control disappeared from the bottom of the screen. I deleted Slacko from the stick and created another bootable version on the stick. When I used this on the laptop, the sound worked fine initially but then after some time it stopped working again.
Anyone experienced this on their machines?
Any suggestions?
Thanks,
Dave

Does this happen on second boot or several after? The answer to this is critical.

I ask this because sound is reconfigured on every boot so should be consistent. It may be that some file system corruption has crept in. What type of filesystem is on the root of the stick? FAT32 is ok but I prefer ext2 linux. It does seem more robust and is a maintained technology._________________Puppy Linux Blog - contact me for access

Lost sound is in heavy troubleshooting in the Lucid Puppy 528 topic. Same type problems are happening, as stated above. It starts on around page 40 of topic.
You can look at last 3 or 4 pages, of topic, for latest discussions. Your ideas needed.
It seems, Lucid 528, is not the only version of Puppy, having these lost sound issues.
Does seem to be tied to USB devices.
http://www.murga-linux.com/puppy/viewtopic.php?p=582845#582845

About format of a USB stick.
Some computers will not boot from a USB stick formatted in any Linux format. It has to be Vfat. It is a bios thing. I have one._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

I should point out that these 3 new drivers are kernel modules. This means that Fusion MPT interfaces will only be accessible after Puppy has booted, so you will still need to boot Puppy from a "conventional" interface (IDE, SATA, USB) and then just use drives connected to Fusion MPT interfaces as secondary drives.

Would it be possible to boot from a Fusion MPT interface? Yes, but that would require either the drivers were built directly into the Puppy kernel image, or alternatively that the new kernel modules were included in Puppy's initial ramdisk.
This is extra work, for another day.

Would it be possible to boot from a Fusion MPT interface? Yes, but that would require either the drivers were built directly into the Puppy kernel image, or alternatively that the new kernel modules were included in Puppy's initial ramdisk.
This is extra work, for another day.

Barry has an option in Woof.. Boot scsi, I accepted this for k2.6.29.4 and in this release k2,6,37.6

Aitch has reported success on an old server box of his a few pages back.

Here is the list of /lib/modules/2.6.39.4/kernel/drivers/scsi in the initial ramdisk of k2.6.39.4 version of slacko-5.3.1

I have also lost sound but fail to remember if it was on Asus using ext3 or if it was on Acer with NTFS formatting.

I do remember that suddenly after some restart of xorg to get the resolution I wanted then suddenly I had no speaker icon in the tray.

So I got back to using Snow puppy 5 instead. And did forget all about it._________________I use Google Search on Puppy Forum
not an ideal solution thoughLast edited by nooby on Mon 12 Dec 2011, 11:14; edited 1 time in total

(2) Pfilesearch - did not seem to be included in the Menu
*** SEE ADDENDUM for update
------------------------------------------------------------------------------------
I installed the SeaMonkey 2.5 Slacko pet and all seems well.
Pfilesearch runs from the Console, but I did not quickly (or at all)
find its version number.
-------------------------------------------------------------------------------------

My regards

I was using 5.3 Main full time and it remained stable, fast and totally trouble free. I expect to use 5.3.1 Main full time now and will advise if there is anything you may wish to know about.

PS Having used Firefox and Thunderbird for a year and more, I very quickly got used to SeaMonkey and its email program - and I'm well pleased.

ADDENDUM:

Pfind is under Menu>Filesystem and Pfilesearch can be obtained using the "Advanced" option of Pfind (as well as directly from the Console).Last edited by Jasper on Wed 14 Dec 2011, 06:07; edited 1 time in total

Barry has an option in Woof.. Boot scsi, I accepted this for k2.6.29.4 and in this release k2,6,37.6

I'm unfamiliar with Woof, but that's interesting. It appears that a basic set of SCSI drivers (as specified by Barry) is then included in the initrd.

Obviously the 3 new Fusion SCSI drivers are not included, so if desired these would need to be manually inserted (and modules.dep updated) ...
or maybe the Woof script could be modified to automatically include these new modules?
But anyway, no one has specifically asked for boot support from a Fusion SCSI interface at this stage.

01micko wrote:

Aitch has reported success on an old server box of his a few pages back.

Yes, it appears that booting from SCSI works, that's great ...
but of course Aitch's SCSI hardware uses the aic7xxx SCSI driver, nothing to do with the 3 new drivers.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum