BIOS: One of those 'specials' by the Phoenix division. When I acquired the beast I made the mistake of flashing the last BIOS. It turned out to be a truncated variety - nothing of interest to twiddle. The previous version (which I didn't save) had a few more options, but nothing worthwhile.
As for workarounds with the router GW and addresses, I really don't want to go there as I use split addressing, viz. 2.....100 reserved for static, 101...254 for DHCP. Works on absolutely everything else, including Wary, Quirky, Fluppy on desktops and internal NIC on a newer Acer laptop (with broken lid!). The LAN l.e.d. never lights up, as it does with every other system, including this laptop under WME. Regardless of the OS 'seeing' the card, the port is never interrogated. That cannot be - there must be another line of code needed for this device and I've no idea about such things. It must be a pcmcia issue because the TDK 10baseT doesn't get activated either. The LAN l.e.d. should light up before the 'online' one? It doesn't.
I don't keep this laptop readily available for testing, so I might see if I can add the extra pcmcia/cardbus NIC to the Acer. There is a PCI card that accepts these units into the backplane on a desktop but I don't have one.
There really isn't any point in laptops, they are a failed marketing ploy. I said that years ago, but the marketing push was so heavy that millions of punters fell for it. Everything can be done more effectively from a smart mobile. But as I also pointed out, important people have a secretary back in the office to deal with phone calls, letters and all that office trivia. Great minds only need food to plot the future...
Wary Puppy 5.0-final feedback
This pertains to a full-install and maybe frugal installs using wary_102
Live CD to full install, compaq slim-line PC (not a laptop) 350 Mhz 64MB ram to full install fs:ext3 internal onboard agp ati 4MB video, 1.44 floppy drv, 2GB laptop HD, CD/dvd drive via flex cable
Live-CD, chose 640*460*16 resolution (less overhead on this low-end machine) (800*600*16 also works, default proposed values)
actual full-install setup : CD/DVD drive on primary controller (short flex cable to modern cd/dvd drive)/ 3"1/2 laptop ide drive HD on sec controller
- found this out by switching drive setup around after sucessfull working full install -> grub working setup: HD was on 1st controller and CD was on 2nd controller
1st prob: neither grub or dos fdisk expect a single CD/DVD drive on the prim controller with the only Boot HD on the sec controller
grub throws a stage 1.5 21 error and DOS fdisk reports no drv found : a solution in this particular case, use a recent grub4dos using UUID
proceeded to upgrade RAM from 64MB to 2*128MB sync (256MB) for the full-install to be reasonably usable, no swap for testing purposes
- hit a next prob, was wondering why tune2fs doesn't seem to run fsck if count or date are exceeded on ext2/3/4
.. bootkernel.log and dmesg contain lines to run fsck
the flag is there (fsckme) comment out to forcefully run it. Are all conditions specified/met ?
I was looking at the date output compared to date/dmesg/tune2fs with an extra particular condition -> my PC doesn't have a cmos batt,
as long as it's powered up, date/time are correct, if unplugged it uses BIOS default values
# date (reboot full-install unplugged, BIOS time/date defaults are used)
Fri Jan 4 00:10:54 GMT 1980
# date -f 1980.txt +%s
Jan 4 00:05:44 -> 315792344
# tune2fs -l /dev/sda2 (snip-it, sda2 is the full install HD PDEV1 pupstate=2)
tune2fs 1.41.9 (22-Aug-2009)
Filesystem created: Sun Jan 2 22:34:06 2011
Last mount time: Sun Nov 28 17:37:12 1943 #-823414968 (wow a neg nber)
Last write time: Sun Nov 28 17:37:12 1943
Mount count: 11
Maximum mount count: 60
Last checked: Tue Feb 15 23:59:35 2011
Check interval: 15552000 (6 months)
Next check after: Sun Aug 14 23:59:35 2011
I'm testing a bit of code, don't remove the flag if certain tune2fs/ext_234 conditions are met on full install's
On this slow but usable full install machine, sometimes the floppy icon won't appear or the speaker icon, sometimes both appear.
if i try to play a music file, I get no sound, running the alsa wizard again restores sound output. The sound level isn't muted and the alsa.conf file is valid and there.
Stopping alsa then restarting removes the speaker icon, but sound is restored.
Wary has restored this older piece of kit to a usefull purpose.
Live CD to full install, compaq slim-line PC (not a laptop) 350 Mhz 64MB ram to full install fs:ext3 internal onboard agp ati 4MB video, 1.44 floppy drv, 2GB laptop HD, CD/dvd drive via flex cable
Live-CD, chose 640*460*16 resolution (less overhead on this low-end machine) (800*600*16 also works, default proposed values)
actual full-install setup : CD/DVD drive on primary controller (short flex cable to modern cd/dvd drive)/ 3"1/2 laptop ide drive HD on sec controller
- found this out by switching drive setup around after sucessfull working full install -> grub working setup: HD was on 1st controller and CD was on 2nd controller
1st prob: neither grub or dos fdisk expect a single CD/DVD drive on the prim controller with the only Boot HD on the sec controller
grub throws a stage 1.5 21 error and DOS fdisk reports no drv found : a solution in this particular case, use a recent grub4dos using UUID
proceeded to upgrade RAM from 64MB to 2*128MB sync (256MB) for the full-install to be reasonably usable, no swap for testing purposes
- hit a next prob, was wondering why tune2fs doesn't seem to run fsck if count or date are exceeded on ext2/3/4
.. bootkernel.log and dmesg contain lines to run fsck
the flag is there (fsckme) comment out to forcefully run it. Are all conditions specified/met ?
I was looking at the date output compared to date/dmesg/tune2fs with an extra particular condition -> my PC doesn't have a cmos batt,
as long as it's powered up, date/time are correct, if unplugged it uses BIOS default values
# date (reboot full-install unplugged, BIOS time/date defaults are used)
Fri Jan 4 00:10:54 GMT 1980
# date -f 1980.txt +%s
Jan 4 00:05:44 -> 315792344
# tune2fs -l /dev/sda2 (snip-it, sda2 is the full install HD PDEV1 pupstate=2)
tune2fs 1.41.9 (22-Aug-2009)
Filesystem created: Sun Jan 2 22:34:06 2011
Last mount time: Sun Nov 28 17:37:12 1943 #-823414968 (wow a neg nber)
Last write time: Sun Nov 28 17:37:12 1943
Mount count: 11
Maximum mount count: 60
Last checked: Tue Feb 15 23:59:35 2011
Check interval: 15552000 (6 months)
Next check after: Sun Aug 14 23:59:35 2011
I'm testing a bit of code, don't remove the flag if certain tune2fs/ext_234 conditions are met on full install's
On this slow but usable full install machine, sometimes the floppy icon won't appear or the speaker icon, sometimes both appear.
if i try to play a music file, I get no sound, running the alsa wizard again restores sound output. The sound level isn't muted and the alsa.conf file is valid and there.
Stopping alsa then restarting removes the speaker icon, but sound is restored.
Wary has restored this older piece of kit to a usefull purpose.
You seem to have an LS120 FDD? As I said, many Cq machines were fitted with them. That accounts, partly, for the strange cabling - sometimes LS120 s are fussy. Cq also puts hidden boot files on one of the HDD s. If you never plan to use 'doze again, you can confidently replace the LS120 (put it in an M$ machine if you have one in which it'll be a lot less trouble, or just use it for storage) with a regular floppy. It should be possible to replace the entire OS on HD s with Puppy BUT as a precaution, save the hidden partition. Some folks claim the hidden boot files are essential to make the whole thing work, but I've never found that to be the case. A BIOS flash may be needed; try to find who made the board (MSI made a lot for Cq) and what its oem designation was/is.The info is often on the InterWeb. If you find it flash with the oem BIOS and all your problems will vanish. Cq claimed their proprietary booting obviated some issues but it was a nasty capitalist ruse to gain leverage.
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: FireFox vs: SeaMonkey
I have re-uploaded the FF PET, think it should fix the problem:Bill253 wrote:So I noticed on Barry's blog that:I just tried it and, unfortunately at least for me, it takes over SeaMonkey just like the last one (Firefox 3.6.9-w5) did.Firefox 3.6.13
I have compiled Firefox 3.6.13 for Wary. I have created a PET, and I think that I have addressed the concerns expressed by users of the previous Firefox PET -- that included SeaMonkey no longer working after Firefox was installed, and/or SM not working after the Firefox PET is uninstalled.
After downloading/installing the new pet from:
All my Firefox and SeaMonkey menu links and the browse and email screen icons now bring up the new Firefox named Namoroka version 3.6.13.Posted on 25 Jan 2011, 8:53 by BarryK
Firefox now uploaded
I can now upload to ibiblio:
http://distro.ibiblio.org/pub/linux/dis ... .13-w5.pet
What I did discover is that SeaMonkey rerturns upon uninstalling Firefox, including my 'lost' mail.I never would have thought to do the uninstall, had Barry not mentioned it in his blog. Plus I learned how to uninstall a package, so there's that...
Here I am referring to Barry like I know him, when feel I should be bowing toward Australia in reverence for all the hard work and wonderful things that he and the all the rest of the developers/contributers have done with Puppy Linux. Thanks to you all!!!
http://bkhome.org/blog/?viewDetailed=02118
[url]https://bkhome.org/news/[/url]
Update : the TDK pcmcia 10baseT in the Acer laptop will run. It is detected in Lupu5.2 in SNS, but doesn't fire up. It was necessary to plug-unplug and use the the complete network wizard, it shows as eth1, with the internal NIC as eth0. The driver is already loaded, highlighting it works. Not so much luck with the Xircon - it is double-height and doesn't fit! So Lupu has the necessary complement of drivers and, crucially, the essential code to make them function. Hopefully, this will give BK the necessary clues.
-
its-me-again
- Posts: 109
- Joined: Thu 29 Apr 2010, 05:23
Hi i have trouble with the latest version of firefox here http://bkhome.org/blog/?viewCat=Wary
after installing it first it is not traditional firefox it is another version based on it.
2nd there is still the problem with seamonkey not working after the install. clicking on seamonkey opens the firefox version.
also another thing can wary use quirky pets if so this would rock as quirky pets are great
after installing it first it is not traditional firefox it is another version based on it.
2nd there is still the problem with seamonkey not working after the install. clicking on seamonkey opens the firefox version.
also another thing can wary use quirky pets if so this would rock as quirky pets are great
Wary does not boot on my Acer D250 that have an Intel Atom N270 CPU.
If I use acpi=off on Lupu 520 then that one boot but not shut down.
Could someone suggest a better boot code that would allow me to both boot and shut down properly?
Fluppy though always boot and shut down properly. So Jemimah has done something that works on my gear.
When it fails to boot it report
b44-pci-bridge and sometimes it shows ssb0 ssb1 ssb2 ssb3 which may be cores on the CPU? Could that explain why it does not boot?
My crazy stomach or gut feeling is that it has to do with IRQ16 but I know nothing so that could be a dead alley whim thing.
If I use acpi=off on Lupu 520 then that one boot but not shut down.
Could someone suggest a better boot code that would allow me to both boot and shut down properly?
Fluppy though always boot and shut down properly. So Jemimah has done something that works on my gear.
When it fails to boot it report
b44-pci-bridge and sometimes it shows ssb0 ssb1 ssb2 ssb3 which may be cores on the CPU? Could that explain why it does not boot?
My crazy stomach or gut feeling is that it has to do with IRQ16 but I know nothing so that could be a dead alley whim thing.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Minor modem cleanup
Barry,
I have noticed a few details that can be cleaned up easily. They are attached. The only logic change is to the SL modem driver firmware tarball. It now has separate init scripts for the slusb driver and the others.
In testing my SL USB modem, the bootup listing shows a set of traceback messages that seem related to the slusb driver module. (And the modem is unusable.) The message log is also attached. Considering that support for that module seems to have ended for kernels later than 2.6.30, maybe that module should be removed from wary and woof.
I am currently updating all of the PCI-modem pinstall scripts to better handle the cases where an appropriate driver is absent from puppy. They remove the init script if there is no driver module. Although I am changing all of them, the usefulness of this is only where the module is invoked by a udev rule instead of a modalias (e.g., agrsm and intel537). They are not needed for wary (which has all the drivers), but seem appropriate for woof and any distros that would allow the user to add PCI modem drivers.
EDIT: I just discovered a subtle bug in /usr/sbin/remasterpup2. It causes a message to omit the CD/DVD burner device name in a message. Line 173 begins with:
The burner drive is /dev/$BURNERDRV,
but should escape the "$" as done in all the other messages using that variable, to become:
The burner drive is /dev/\$BURNERDRV,
Richard
I have noticed a few details that can be cleaned up easily. They are attached. The only logic change is to the SL modem driver firmware tarball. It now has separate init scripts for the slusb driver and the others.
In testing my SL USB modem, the bootup listing shows a set of traceback messages that seem related to the slusb driver module. (And the modem is unusable.) The message log is also attached. Considering that support for that module seems to have ended for kernels later than 2.6.30, maybe that module should be removed from wary and woof.
I am currently updating all of the PCI-modem pinstall scripts to better handle the cases where an appropriate driver is absent from puppy. They remove the init script if there is no driver module. Although I am changing all of them, the usefulness of this is only where the module is invoked by a udev rule instead of a modalias (e.g., agrsm and intel537). They are not needed for wary (which has all the drivers), but seem appropriate for woof and any distros that would allow the user to add PCI modem drivers.
EDIT: I just discovered a subtle bug in /usr/sbin/remasterpup2. It causes a message to omit the CD/DVD burner device name in a message. Line 173 begins with:
The burner drive is /dev/$BURNERDRV,
but should escape the "$" as done in all the other messages using that variable, to become:
The burner drive is /dev/\$BURNERDRV,
Richard
- Attachments
-
- messages-slusb_traceback.tar.gz
- SmartLink USB driver crash during bootup.
- (7.26 KiB) Downloaded 740 times
Last edited by rerwin on Wed 02 Feb 2011, 00:40, edited 2 times in total.
Personally I am 100% with BarryK on his 'minimalist' approach. (My favorite wallpaper is the 'light grey' one ... can there really be such sad people out there as want to sit staring at wallpaper all day I think to myself .. ah, wait, that fella Bill thought so). However, when I saw the current Wary default wallpaper the faint splodges in the background had me genuinely worried that I had a faulty screen. I therefore plead that the default wallpaper be changed.
I have disliked icons ever since Bill invented their use in order to turn the world into his mushroom farm .... all too successfully .... very often they are more confusing than helpful (the essence of good mushroom farming perhaps). The only one which really appealed to me was the PET-in-a-box one - inspired! - always good for a smile. It has now been replaced by a briefcase - how meaningful is that?! - a case for reversion IMHO.
It took me a long time to figure out that the strange hieroglyph, bottom right, might be an allusion to a Winchester stack .. of about that era .. and when the Rosetta stone finally dropped on my foot -ouch!- to understand that it had something to do with storage capacity. Not newbie-friendly .... things were better in the 431 epoch. (More serious note, it gives markedly different display v/v lupu on the same installation).
The biggest niggle is the mute 'cell' icon, in laptop mode. Some might go through life and die without knowing that if you click on it you will see a table of figures - "with the unfounded ring of high precision" (right, Sage?). This presentation seems vastly inferior to the % indicator in 431 which - however inaccurate - I really found very much more useful. (OTOH the progressive laptop screen dimming with the 431 version was a serious nuisance, anyone know how to override that?).
I have disliked icons ever since Bill invented their use in order to turn the world into his mushroom farm .... all too successfully .... very often they are more confusing than helpful (the essence of good mushroom farming perhaps). The only one which really appealed to me was the PET-in-a-box one - inspired! - always good for a smile. It has now been replaced by a briefcase - how meaningful is that?! - a case for reversion IMHO.
It took me a long time to figure out that the strange hieroglyph, bottom right, might be an allusion to a Winchester stack .. of about that era .. and when the Rosetta stone finally dropped on my foot -ouch!- to understand that it had something to do with storage capacity. Not newbie-friendly .... things were better in the 431 epoch. (More serious note, it gives markedly different display v/v lupu on the same installation).
The biggest niggle is the mute 'cell' icon, in laptop mode. Some might go through life and die without knowing that if you click on it you will see a table of figures - "with the unfounded ring of high precision" (right, Sage?). This presentation seems vastly inferior to the % indicator in 431 which - however inaccurate - I really found very much more useful. (OTOH the progressive laptop screen dimming with the 431 version was a serious nuisance, anyone know how to override that?).
1. I have no sound on Wary-500. 
2. PCI sound card is shown in hardinfo->devices->PCI_devices as:
Multimedia Audio Controller
C-Media Electronics Inc CM8738
3. "Alsa Sound wizard" cannot find any supported PCI card.
4. "Probe for legacy ISA sound cards/chips" finds no suitable drivers!
5. Are there any drivers I can install?
2. PCI sound card is shown in hardinfo->devices->PCI_devices as:
Multimedia Audio Controller
C-Media Electronics Inc CM8738
3. "Alsa Sound wizard" cannot find any supported PCI card.
4. "Probe for legacy ISA sound cards/chips" finds no suitable drivers!
5. Are there any drivers I can install?
Those things are ubiquitous! Couple of things you could try:CM8738
- use another CM number close to 8738
- just run through a selection of other drivers to see if one fires up
If none works, time to knock (loudly) on BK's door because there will be thousands (millions?!) also requiring support.
But you should already have checked whether it's running on the PCI or ISA bus; see my discussions in another thread for ISA cards.
Hope Springs Eternal.Sage wrote:If none works, time to knock (loudly) on BK's door because there will be thousands (millions?!) also requiring support.
While I have knocked on the door at least once in the forum, and perhaps another time or so, no one has said "Yes, who's there?" or "Try this." or any response that I could see.
So in the spirit on knocking loudly:
Wary5 will not detect my onboard audio chip. Puppies that do see it tell me it is and hda-intel Intel Corp 82801G (ICH7 Family).
I'd love to try Wary....but it simply does not see my sound chip. I'll assume I have no technical skills and request that someone give me some hints on what to do, other than try other drivers that the sound wizard detects, since none of them work.
Thanks
Thom
Presume that it runs in Mint? Most HW does. That is a *buntu/Deb derivative, so it might be possible to copy their driver into Lupu (if Lupu doesn't do it direct) then copy it to Wary, in which it might still not work directly, but may need less breathing on? There are a dozen or so really clever guys around here whom you might PM? Tux, o1micro, Tazoc - the guys in Queensland are going to be too busy for a while.
I speak in ignorance of coding constraints, as usual...
I speak in ignorance of coding constraints, as usual...
tlchost: I have the Intel 82801G audio chip in my desktop machine and it works for me on Wary 500. Having said that I think there is something wrong with Wary's sound setup because on my laptop Wary does not detect a very common Via sound card. I gave up after a few tries - it may just be temperamental! I wonder if Barry has tweaked/broken the Alsa Sound Wizard recently?
I'm sure there are folks that enjoy trouble shooting....I don't at all. So, unless I hear something that would lead to a fix, Wary will be yet another OS that I can not use.Terryphi wrote:tlchost: I have the Intel 82801G audio chip in my desktop machine and it works for me on Wary 500. Having said that I think there is something wrong with Wary's sound setup because on my laptop Wary does not detect a very common Via sound card. I gave up after a few tries
Thom
I was a bit vague in my last post so did a bit of digging, hope this bit of feedback will help some others.
Compaq deskpro EN series SFF 350Mhz, working o/b snd chip en18xx (alsa isa legacy card detection)
Wary-500 live-cd and no sound: ran alsawizard (aka alsaconf), it drops to isa legacy detection with all card/modules ticked.
No isa cards found : en18xx o/b snd card isn't detected.
..the snd card database file isn't populated in /var/tmp during and after the run.
../etc/alsa.conf file contains default values from alsaconf.
2nd run of alsaconf with only the es18xx module ticked, card is detected then configured and test snd is played, ok.
Next step, clean slate hd puppy full install to a ext3 fs using grub4dos, no sound
ran alsaconf (alsawizard), /var/tmp snd card database is populated, the script ran searching for snd card with progress bar (this seem logical)
(full_install ran a diff fnct cmpd to live-cd, live-cd proposed to tick/untick cards/modules)
chose es18xx snd-es18xx from list, sound ok
checked volume levels in /etc/asound.state (contains PCM & PCM1) and retrovol full window values are correct.
2nd boot of wary full install, rechecked volume levels in /etc/asound.state (contains PCM & PCM1) same as initial values,
but retrovol full window value of pcm was muted (that's why I got no sound) & pcm1 value was at ~50% (also reduced)
.. running 'alsactl -f /etc/asound.state restore' on 2nd boot will put the levels up to norm in retrovol.
This just seems to delay by 1 boot, the mute of retrovol pcm ie: no sound with /etc/asound.state values reduced.
/etc/asound.state file changes seem to be taken into account after following boot (it doesn't seem to be the gouverner file)
snipit from 1st & 2nd boot of full install /etc/asound.state file
control.11 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
value.0 14
value.1 14
}
control.12 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
index 1
value.0 14
value.1 14
}
and snipit from 3rd boot of full install
control.11 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
value.0 0
value.1 0
}
control.12 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
index 1
value.0 8
value.1 8
}
edited 1 time
Compaq deskpro EN series SFF 350Mhz, working o/b snd chip en18xx (alsa isa legacy card detection)
Wary-500 live-cd and no sound: ran alsawizard (aka alsaconf), it drops to isa legacy detection with all card/modules ticked.
No isa cards found : en18xx o/b snd card isn't detected.
..the snd card database file isn't populated in /var/tmp during and after the run.
../etc/alsa.conf file contains default values from alsaconf.
2nd run of alsaconf with only the es18xx module ticked, card is detected then configured and test snd is played, ok.
Next step, clean slate hd puppy full install to a ext3 fs using grub4dos, no sound
ran alsaconf (alsawizard), /var/tmp snd card database is populated, the script ran searching for snd card with progress bar (this seem logical)
(full_install ran a diff fnct cmpd to live-cd, live-cd proposed to tick/untick cards/modules)
chose es18xx snd-es18xx from list, sound ok
checked volume levels in /etc/asound.state (contains PCM & PCM1) and retrovol full window values are correct.
2nd boot of wary full install, rechecked volume levels in /etc/asound.state (contains PCM & PCM1) same as initial values,
but retrovol full window value of pcm was muted (that's why I got no sound) & pcm1 value was at ~50% (also reduced)
.. running 'alsactl -f /etc/asound.state restore' on 2nd boot will put the levels up to norm in retrovol.
This just seems to delay by 1 boot, the mute of retrovol pcm ie: no sound with /etc/asound.state values reduced.
/etc/asound.state file changes seem to be taken into account after following boot (it doesn't seem to be the gouverner file)
snipit from 1st & 2nd boot of full install /etc/asound.state file
control.11 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
value.0 14
value.1 14
}
control.12 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
index 1
value.0 14
value.1 14
}
and snipit from 3rd boot of full install
control.11 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
value.0 0
value.1 0
}
control.12 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'PCM Playback Volume'
index 1
value.0 8
value.1 8
}
edited 1 time
- Attachments
-
- retrovol-1b.png
- retrovol levels on 2nd full install boot
- (3.94 KiB) Downloaded 1330 times
I too have had sound issues with Wary (and others as well) so you're not alone. I've been doing some regression testing to try to see when the problem occurred in hopes of fixing it myself. My problem is that sound IS detected when I start with a clean warysave file, but disappears sometime after a handful of reboots. I'm going to post my results in another post.tlchost wrote:Hope Springs Eternal.Sage wrote:If none works, time to knock (loudly) on BK's door because there will be thousands (millions?!) also requiring support.
While I have knocked on the door at least once in the forum, and perhaps another time or so, no one has said "Yes, who's there?" or "Try this." or any response that I could see.
So in the spirit on knocking loudly:
Wary5 will not detect my onboard audio chip. Puppies that do see it tell me it is and hda-intel Intel Corp 82801G (ICH7 Family).
I'd love to try Wary....but it simply does not see my sound chip. I'll assume I have no technical skills and request that someone give me some hints on what to do, other than try other drivers that the sound wizard detects, since none of them work.
Did you try running Puppy 4.3.1 - I have absolutely no sound issues with it.