Quirky 1.4 bug reports and feedback

[BarryK]

More PPM oddities.

1) I noted on Barry's blog that I'm getting results in a package search even if I have a repo selected that should return no results. I have figured this out. findnames.sh does not search only the selected repo; it searches all active repos. Not only that; within the search loop it leaves /tmp/petget_filterversion pointing at a repo other than the one that is selected.

There is one other place that writes directly to /tmp/petget_filterversion (rather than going through /tmp/filterversion.sh, which I think is innocent), and that is within pkgchooser.sh. I don't know if that one is OK or not.

I think findnames.sh should only search within the selected repo. Otherwise, if several things are found, you have no idea which repo they are in. The way it is now, they appear to be in all the repos, because whatever repo you have selected, you get the same search results.

2) I am using this in Lupu511. I am guessing, because I am using these large repos, I should have the alphabetic radiobuttons displayed. At least that's what the code says, that I can tell. But I don't see them. I haven't chased this one down yet.

3) In pkg_chooser.sh, it almost looks like the file /tmp/filterversion.sh is used (in the radiobuttons) before it has been created. Just my impression, could be wrong on this...

I just checked, the search in PPM only searches currently-selected repo. Yep, works as expected. I tested by searching for "abiword".

Note, I have posted some bugfixes for PPM since Quirky 1.4 was released. That might make a difference.

[CHLee]

[quote="BarryK"]

Ah, ok. I will show you how to find out more about this...

If you type this:

[code]# modinfo 8139too[/code]

...you will see an "alias" line that looks like the correct one for your card. Now do this, inserting that alias value:

[code]# modprobe --show-depends pci:v000010ECd00008139sv*sd*bc*sc*i*
insmod /lib/modules/2.6.31.14/kernel/drivers/net/mii.ko
insmod /lib/modules/2.6.31.14/kernel/drivers/net/8139too.ko
insmod /lib/modules/2.6.31.14/kernel/drivers/net/mii.ko
insmod /lib/modules/2.6.31.14/kernel/drivers/net/8139cp.ko [/code]

...Puppy will choose the last one on the list. If you type 'lsmod' in a terminal, you will probably confirm that 8139cp loaded. This is known to be a crappy module.

There are various ways to fix this. I have put a permanent fix into Woof (actually, only in my zzz pkg for now). In /etc/rc.d/MODULESCONFIG, add entry as shown:

[code]#PREFLIST: sometimes there are two hits, that is, two modules match the same
#'modalias' (that is, they are both claiming the same hardware). In such a case,
#here we can specify a preference. Each entry here is of the form
#'module1:module2' where module2 is the preferred choice.
#note, list needs a space char at beginning and at end.
#w471 removed: ath5k:ath_pci martian_dev:ltserial r8169:r8101
PREFLIST=' 8139cp:8139too rtl8180:r8180 rtl8187:r8187 rt2500usb:rt73usb orinoco_nortel:hostap_plx orinoco_plx:hostap_plx orinoco_tmd:hostap_plx orinoco_pci:hostap_pci bcm43xx:ssb prism54:p54pci tulip:dmfe option:hso hcfpcihw:hsfpcibasic2 dgcusbdcp:cdc_acm slamr:snd_intel8x0m '[/code]

...you can try this for yourself in Wary or Quirky.[/quote]

Barry,
Thank for you helping. I made a woof build base on the Quirky1.4 yesterday, I added the 8139cp:8139too in the PREFLIST of the /etc/rc.d/MODULESCONFIG. ( First in rootfs-skeleton,but wrong. Second in zzz pkg, this time OK.)
When first boot, I don't know why the 8139cp module still loaded. Then I saved a save file and second boot, this time the 8139too loaded, the network OK. I double checked with the BootManager, my PREFLIST was right.
Are there some different between first boot and second boot (the MODULESCONFIG handling)?

Thank you very much.
C.H. Lee

[PaulBx1]

I just checked, the search in PPM only searches currently-selected repo. Yep, works as expected. I tested by searching for "abiword".

I searched abiword too. It was found in every repo, even those that do not have it such as ubuntu-lucid-main.

I'm pretty sure I have the latest findnames.sh. It shows a modify time of 30 Nov, and a change/access time of 6 Dec. I'm never quite sure what the difference is between "change" and "modify" though. (I'm also assuming this PPM code works in Lupu 511 which is what I'm running.) Here is the code in question:

Code: Select all

#!/bin/sh
#(c) Copyright Barry Kauler 2009, puppylinux.com
#2009 Lesser GPL licence v2 (http://www.fsf.org/licensing/licenses/lgpl.html).
#called from /usr/local/petget/pkg_chooser.sh
#  ENTRY1 is a string, to search for a package.
#101129 checkboxes for show EXE DEV DOC NLS. fixed some search bugs.

. /etc/DISTRO_SPECS #has DISTRO_BINARY_COMPAT, DISTRO_COMPAT_VERSION
. /root/.packages/DISTRO_PKGS_SPECS #has PKGS_SPECS_TABLE.
. /root/.packages/DISTRO_PET_REPOS #has PET_REPOS, PACKAGELISTS_PET_ORDER

entryPATTERN='^'"`echo -n "$ENTRY1" | sed -e 's%\\-%\\\\-%g' -e 's%\\.%\\\\.%g' -e 's%\\*%.*%g'`"

CURRENTREPO="`cat /tmp/petget_filterversion`" #search here first.
REPOLIST="${CURRENTREPO} `cat /tmp/petget_active_repo_list | grep -v "$CURRENTREPO" | tr '\n' ' '`"

FNDIT=no
for ONEREPO in $REPOLIST
do
 FNDENTRIES="`cat /root/.packages/Packages-${ONEREPO} | grep -i "$entryPATTERN"`"
 if [ "$FNDENTRIES" != "" ];then
  FIRSTCHAR="`echo "$FNDENTRIES" | cut -c 1 | tr '\n' ' ' | sed -e 's% %%g'`"
  #write these just in case needed...
  ALPHAPRE="`cat /tmp/petget_pkg_first_char`"
  #if [ "$ALPHAPRE" != "ALL" ];then
  # echo "$FIRSTCHAR" > /tmp/petget_pkg_first_char
  #fi
  #echo "ALL" > /tmp/petget_filtercategory
  echo "$ONEREPO" > /tmp/petget_filterversion #ex: slackware-12.2-official
  #this is read when update TREE1 in pkg_chooser.sh...
  echo "$FNDENTRIES" | cut -f 1,10 -d '|' > /tmp/filterpkgs.results
  FNDIT=yes
  break
 fi
done

Note the for loop where the search is done through every repo in the variable REPOLIST. REPOLIST holds every active repo.

At least, it looks like it is searching through every repo, to me. It does break out of the loop the first time it finds something in a repo, but it's not confining itself to the selected repo. It makes it look like every repo has the same searched packages in it, because no matter which repo you select, you always get the same results.

Note also that CURRENTREPO depends on what is in petget_filterversion, but petget_filterversion is modified in the loop. So next time the search happens...

[shinobar]

@Barry
See the topic on a bug in rc.shutdown:
http://www.murga-linux.com/puppy/viewtopic.php?t=62804

[BarryK]

Barry,
Thank for you helping. I made a woof build base on the Quirky1.4 yesterday, I added the 8139cp:8139too in the PREFLIST of the /etc/rc.d/MODULESCONFIG. ( First in rootfs-skeleton,but wrong. Second in zzz pkg, this time OK.)
When first boot, I don't know why the 8139cp module still loaded. Then I saved a save file and second boot, this time the 8139too loaded, the network OK. I double checked with the BootManager, my PREFLIST was right.
Are there some different between first boot and second boot (the MODULESCONFIG handling)?

Thank you very much.
C.H. Lee

I don't know. Anyway, this is an area where I have been making many changes, try my next Wary.

[BarryK]

@Barry
See the topic on a bug in rc.shutdown:
http://www.murga-linux.com/puppy/viewtopic.php?t=62804

shinobar,
Thanks, I have fixed this in Woof.

[BarryK]

duplicate post

[marquitico]

No sound with a Riptide Rockwell audio controller. Doing lspci and lsmod do not show anything significantly different from doing same on other Linuxes on this hardware: snd-riptide is correctly loaded and dependencies fulfilled, and the audio controller is located. Adding the riptide.hex file to /lib/firmware produces no effect. Alsa wizard repeatedly reports "no PnP or PCI cards". Not any kind of expert, so don't know what else to try.

But sound works fine in Quirky 1.2 Retro.

[PaulBx1]

In the bit of code I mentioned above, in findnames.sh, I changed

Code: Select all

for ONEREPO in $REPOLIST 

to

Code: Select all

for ONEREPO in $CURRENTREPO

(and also commented out the write to /tmp/petget_filterversion). Now the search works properly, only looking within the selected repo. Of course the whole for loop probably should be removed.

If this is done you might also think about putting "Within selected repo" above the find box. Or "In chosen repo" if you needed it shorter.

There might be a way to keep the search more global as you originally intended. You could first search in the selected repo and display results, then search the other active repos and if anything is found, have a popup appear saying something like "Results were (also) found in these repos:" however if you do that you need to somehow take care of the case where nothing is found in the selected repo. Seems kinda messy...

[gcmartin]

Barry Help! Please.
I am trying to get a PET to run and don't understand what's occurring. I sent a PM to you.

[Sage]

BK blog:

Note, I'm in holiday-mode right now, in Melbourne.

We need to give the fella a break?!

We are all related ...

Indeed - and we are all black, too, even if some of us have faded a bit! Vide Lucy.

[gcmartin]

Thanks Sage...I didn't know.

[tubeguy]

Messing with 1.4 all morning.

[withoutpity]

Quirky 1.4 Always ask for set up country setting,time zone setting and hardware clock setting every thime when boot , while Quirky 1.3 not.
If I choose my locale as en_US or some other , this will not happen .
But after I change my locale to zh_CN, it shows again.

[tlchost]

Quirky 1.4 does not recognize the sound chip on my motherboard.

Can I copy files from 1.2 that do work, or can someone tell me how to identify the chip so that I can request specific help in this thread?

Thanks

Thom

[Sage]

Ah yes, HardInfo doesn't do sound chips. Someone reported a CLI but I never remember those. Quickest and most certain is to open the box + torch + watchmakers eye-magnifier; don't necessarily even trust the book or website as they often fit chips from a range of stock. Great thing about opening the box is that it gives you the option of doubling the lifetime by judicious use of the vacuum cleaner.

[tlchost]

Quickest and most certain is to open the box + torch + watchmakers eye-magnifier;

Easier and less destructive is to use an older OS that works.

Someone pointed me to some of Barry's statements about support for Quirky....kinda sums it all up.

But...1.2 seems to work fine.

Thom

[Sage]

Easier and less destructive

Not so. Only someone from transatlatica could possibly conceive that sliding the side/lid is 'destructive'. A healthy PC requires a Spring clean at least twice a year even if you're not swapping stuff more often. My most heavily used boards don't even live in a box.

[fluxit]

Quirky 1.4 does not recognize the sound chip on my motherboard.

Can I copy files from 1.2 that do work, or can someone tell me how to identify the chip so that I can request specific help in this thread?

This topic should help you.

[gyro]

Quirky 1.4 is missing the link "/usr/lib/libgee.so.0".

gyro