Pristine frugal install of Precise 5.4.90 - added frisbee-1.0-20130207.pet and network_tray-2.6-20130203.pet - successfully established wifi connection which was persistent through a reboot using the Broadcom wl driver.

The move or copy actually succeeds although I understand that permissions may have changed.

As an experiment, I edited the init file in the initrd.gz as suggested by sfr for Slacko 5.4.0.2 which got rid of the error and did not seem to change behaviour in any other way - my test was to install the development sfs's and to compile the broadcom wl driver - all went as expected.

About your wireless problem. Rerwin`s logistic offers wl driver for your 14e4:4727 broadcom chip. brcmsmac supports it better, I think. Just blacklist wl, create savefile and try again. Now brcmsmac should be loaded. The needed firmware should be there for it.

Or...you can test it in console:
modprobe -r wl
modprobe brcmsmac

and test your wireless. If it is not found or working, post the pdiag after that manual wl removal and brcmsmac loading.

I believe that Rerwin`s logic would have loaded brcmsmac after savefile creation and rebooting anyway, but there can be bug.

and Seamonkey would not display the forum when accessed from the splash page - it was displayed when I opened another tab._________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).Last edited by raffy on Sun 10 Feb 2013, 20:43; edited 1 time in total

...but rerwin can probably advise how to quieten that "slamr" message.

I added "2>/dev/null" to the modinfo commands in the initialization scripts and updated the 20121004 firmware package. Because the package exceeds the 256K upload limit, I attach a tarball of only the /lib directory portion of the package, which now should be named
firmware_linux_module_slmodem-20130210.pet
Richard

The move or copy actually succeeds although I understand that permissions may have changed.

As an experiment, I edited the init file in the initrd.gz as suggested by sfr for Slacko 5.4.0.2 which got rid of the error and did not seem to change behaviour in any other way - my test was to install the development sfs's and to compile the broadcom wl driver - all went as expected.

Is there anything else I should test?

Cheers
peebee

I have had discussions with npierce about this and we are in agreement that it is a bug in the OLD static ntfs-3g binary and rox. I intend to inform Thomas Leonard about this issue to see if rox can be fixed.

My solution would be to remove the "no_def_opts" arg in the init script to ntfs-3g BUT this may affect the detection of an error ridden or hibernated ntfs partition so could be dangerous.

It is not my habit, I do not ask others to do the job for me, but since I can not do it alone (and I'm not the only one) ...

I think I begin to be familiar with Puppy, but I'm not good with Woof.
I tried several times to create an iso file (Precise base), but I still get the same result: the boot liveCD gives me error messages.
I tried to get a Woof iso really light (at the main sfs). For this, I wanted to create a zdrv.sfs

My request for the next version of Puppy Precise, would it be possible to offer users/contributors a version with a file zdrv.sfs ? So that we can test its operation.

The move or copy actually succeeds although I understand that permissions may have changed.

As an experiment, I edited the init file in the initrd.gz as suggested by sfr for Slacko 5.4.0.2 which got rid of the error and did not seem to change behaviour in any other way - my test was to install the development sfs's and to compile the broadcom wl driver - all went as expected.

...but rerwin can probably advise how to quieten that "slamr" message.

I added "2>/dev/null" to the modinfo commands in the initialization scripts and updated the 20121004 firmware package. Because the package exceeds the 256K upload limit, I attach a tarball of only the /lib directory portion of the package, which now should be named
firmware_linux_module_slmodem-20130210.pet
Richard

I'm assuming this requires PAE? Currently running RetroPrecise 5.4.3 on a 1.4Ghz Intel Celeron Mobile processor - 2005 laptop. Still perfectly usable for day to day use with non PAE kernels (been using Lupu for last two years) so hoping for a Retro build of 5.5. No problem if I have to wait for a final release.

Thanks for all your amazing work

Answering my own question I see the non PAE build is now there. Thanks.Last edited by Hogweed on Mon 11 Feb 2013, 18:56; edited 4 times in total

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