I have got to the root of the gtk+3 bug with audacious. It is a problem upstream with PACKAGES.TXT from Salix. I have posted a bug report on their forum. I'm sure they will be eager to fix it._________________Puppy Linux Blog - contact me for access

To clarify the issue that I am experiencing with my WN111v2, the connection is dropping out in the middle of active downloads, which is when it is most obvious because everything comes to a visible halt. It's the wireless connection failing, not the internet connection - other devices on the network will continue working normally and in the Puppy session I can't even ping the router until I re-run the Network Wizard.

I've had similar problems with other builds of Slacko before, possibly something to do with kernel or drivers since Lupu has been fine. When the wireless is working properly, speed seems to be the same as with other Puppies._________________Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 HardInfo Report
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0

Other distros, like TinyCore or Fatdog, have a "wait" boot argument to handle this problem with USB devices.

If the same situation is occurring with your hard drive, it would be useful to know if my "sleep 5" suggestion makes any difference.

I need to return to my problem of my booting a frugal install of Fatslacko requiring PMEDIA to be removed to make it work - to let you know what I have found out.

I have found that the source of the problem was nothing to do with PMEDIA or it requiring a sleep parameter in the init to wait for detection. The real problem was that my PC builder installed Windows on the 2nd hard drive - leaving the first drive unformatted. This was not how I wanted it, of course, but I did not realise it until I started playing with Puppy and seeing the drive partition icons coming up sdb?.

In this configuration I had expected grub to require references to (hd1,4) but in fact that failed and (hd0,4) was still required. My original kernel line in menu.lst was then something like:

kernel (hd0,4)/vmlinuz PMEDIA=atahd PDEV1=sda5 psubdir=fatslacko ...

This failed to find the sfs file and eventually removing the PMEDIA=atahd made it work. I thus assumed PDEV1=sda5 was correct (working on my knowledge of the init logic in Puppy4). However the recent discussion here and rcrsn51's suggestion that, if PMEDIA is omitted, Puppy now ignores all other search boot codes and looks everywhere led me to conclude that when I got it working by removing PMEDIA, PDEV1 was not in fact doing anything.

I questioned in my mind whether perhaps, originally, PDEV1 was wrong and, despite grub referring to (hd0,4), Puppy still detected the drives properly and my sfs was actually on sdb.

GRUB gets its information from the BIOS. You would think that the BIOS would be aware of a drive even if it was unformatted.

But I once had a situation where GRUB ignored a drive simply because no partition on it had a boot flag set - even though GRUB doesn't use the boot flag! I concluded that the BIOS was skipping the drive because it didn't appear to be bootable.

Maybe the same thing is happening with your sda. Try putting a little dummy partition on it and flagging it bootable. Does (hd1,0) now work as expected?

This may be a red herring, but looking at your last post did you actually use:

PMEDIA= or pmedia=

Similarly did you use:

PDEV1= or pdev1=

If the former in both cases, puppy may have simply ignored those boot codes, relied on its own search algorithms and come to the right or wrong conclusion itself. If puppy does not recognise a boot code it simply ignores it and AFAIK the case matters.

Apologies if I am barking up the wrong tree and you were just emphasizing those codes._________________Regards ETP

Thank you for including Bibletime 2.9.1-s in the puppy-slacko repository, however, I've had a few problems installing it with the PPM. All the files appear to be present however the program can't find some dependencies. Also the Bibletime.desktop file needs a minor edit so it can find the correct icon. Change /usr/share/applications/bibletime.desktop Icon from Icon=mini-Personal to:

Code:

Icon=/share/bibletime/icons/bibletime.png

This is on a fresh frugal installation with no software installed except Bibletime. In order to provide pictures during troubleshooting, I did install radky's PupSnap screen capture.

Thanks again for your finest Slacko to date, it's solid on my hardware.

I haven't updated anything in PPM just yet. All those packages are compat with 13.37 versions of Slacko, so YMMV in whatever you install from PPM at this stage.

I'm still waiting on a resolution to a critical issue before I upload anything to the main repo. With the next beta, if this isn't resolved by then, I'll have to announce that PPM testing should be restricted to slackware repos only. Apologies for any inconvenience.

---------------------------------------------------------------------

Jades

Netgear dongles are notorious for poor Linux support. It took many years for the kernel developers to get it right for the netgear-wg111-v2, which they eventually did. The symptoms were similar to what you say and the solution for stable connection was to reduce the rate of the thing from full speed to a fraction. I'm not sure what would be optimal for a, IEEE-802.11n dongle though as they ramped up the speed significantly. To change the rate:

I have slacky.eu repo working . Not much there yet as mentioned but they just keep on adding stuff to it over the life of the the distro.

I just installed rekonq (a kde webkit browser) and it worked first go, correct menu and all, but I had all the deps from kdegames already.. interesting to see how it goes from scratch, I'll try when the next beta is ready.

Attached is the pet to add Slacky to PPM. You'll need to update PPM but NOT THE SLACKO REPO (it will break at this stage), then you'll need to configure PPM.

Hi 01micko, here's a qt web browser that works well.
I downloaded the newest flash plugin and put it in
/usr/lib/mozilla/plugins so it plays videos at cnn.com but you may
have to use the refresh item to get the video started.

Still busy on other projects but just time for a brief interjection.
I've also had a lot of grief with my Netgear wg111 USB dongle, aka Cohiba3887/WistonNewebURo54g/IntelsilISL3887/w.h.y.
There have been three issues:
-doesn't connect at all
-lights up but doesn't persist
-some connection utilities far too complex to unravel
Many, but not all, of these features have been observed with Puppy variants.
On the other hand some distros behave perfectly with it. Why should they not because they all have Prism054g (p54g) embedded and functional in their kernels of almost all ages.
Not being a coder, I have absolutely no idea where the problems lie. However, I would strongly recommend everyone on this Forum, using the NG dongle or not, to take a gander at PCLOS 2012-02 Phoenix Xfce edition. This has to be an exercise from Tex on how-to-do-it - Netgear wi-fi, par excellence. Even an HW geek like me can follow it. Moreover, it works and keeps working - rock solid.
Those who understand popping, peeking and poking might do well to study this guy's handiwork, even though he has had detractors on the InterWeb in the past. The fella really understands users like no-one else.

grub4dos want to install on sda1 but generates an error because sda1 gets the following message:

The ntfs-3g driver was unable to mount the NTFS
partition and returned this error message:
Failed to read vcn 0x2: Input/output error
Failed to mount '/dev/sda1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

So, the inbuilt kernel NTFS driver has been used
to mount the partition read-only.

Does anyone understand this? This is a new machine AspireOne AO756. I can still boot windows 7, but the boot files are on sda2. I can boot from slacko from usb but can't boot frugal and don't want to destroy windows.

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