(old)Puppy Linux Discussion Forum

If you happen to be using a Realtek ALC268, you should use "acer" as your model.

It's a Realtek 8185.

I can only get it to connect to one wireless network so far, the one at Yaks Koffee Shop, which I don't need a key for. It fails to connect to any network that I need a wireless key for.

solxyz and jcagle, you are talking at cross purposes.

Realtek ALC268 is an audio chipset, based on the Intel HDA specification.
Realtek 8185 is a wifi chipset.

solxyz wrote:If you happen to be using a Realtek ALC268, you should use "acer" as your model.

jcagle's audio chipset is not Realtek ALC268, it's SigmaTel STAC9200.

jcagle wrote:It fails to connect to any network that I need a wireless key for.

Then you probably need to manually load the relevant encryption module.
For WEP encryption - For WPA - For WPA2 - This is explained in more detail in "How to configure wifi from the commandline"
http://www.murga-linux.com/puppy/viewto ... 339#159339
"PART 4: Troubleshooting, encryption problems"

From what it tells me, the Linux driver for the wireless on the Gateway laptop doesn't support WPA.

Anyway, I'm not even trying to connect to a WPA encrypted network, it's all WEP. I think I'll give it a try.

FATAL: Module ieee80211_crypt_wep-rt1 not found.

That's "rtl" not "rt1".

ok, I changed it from rt1 to rtl. But I still get the error.

I don't know about Puppy4, but Puppy3 definitely contains the ieee80211_crypt_wep-rtl module.
If you get the "Module not found" error message when trying to load this module in Puppy3, it means that Puppy cannot access the zdrv file, which is the compressed collection of modules.

This is an all-too-common problem, but it doesn't seem to affect most experienced Puppy users, and inexperienced users seem unable to grasp the significance of the fault.

If you have a frugal installation, you should check that the zdrv file can be seen at /mnt/home
Beyond this simple check, I don't know how to solve the problem.

If you have a full HD installation, the zdrv file must be uncompressed into the filesystem. This is somewhat complex, and I don't wish to attempt to explain it here. There are instructions elsewhere on the forum.

I'm running from live CD.

Just so you know, I've been a Puppy user for a couple of years now.

Now I see I am not alone. I was wondering why ALSA on puppy 3 could not detect and install my Dell GX1's audio. So I have to use puppy 4 on three PCs to use its audio then. Ok, I go to download puppy 4. Lets see. Tks.
/wyn/

I'm giving the laptop back to the friend I was borrowing it from, as I have bought my own laptop. I am running Dingo on it now, and everything works fine.

It's an Aspire 3690.

I rock!

The laptop has Vista home edition. Despite all the bad things I've heard about Vista, it runs quite well on this laptop, especially with only 502 meg of RAM. I couldn't believe it myself.

Miracles happen!

hello i installed puppy 3.01 to my pen drive.but i am not getting sound.
my codec is alc262.
i tried all the options for the model in the above list.no change.
however i got while booting from cd by making puppy acpi=off. but no such option available for pen drive boot. is there any way to make acpi permanently off?
i got sound in my fedora 8 by adding fujitsu as model parameter.

To Tempestuous,

Many thanks notes made from for your post I was able to get sound working on Acer Inspire 5315.

I also passed on what I did to help another forum user in the hardware forum. I couldn't for the life of me remember where I'd found this information until I re found it here.

Sorry that I was not able to attribute it to your post at the time. I will correct that omission.

John Lewis

I read your thread. It made sense, but left me unable to completely figure it out myself.

# cat /proc/asound/card0/codec#* | grep Codec
Codec: Realtek ALC662 rev1

So I check the list and see:
ALC662
3stack-dig 3-stack (2-channel) with SPDIF
3stack-6ch 3-stack (6-channel)
3stack-6ch-dig 3-stack (6-channel) with SPDIF
6stack-dig 6-stack with SPDIF
lenovo-101e Lenovo laptop
auto auto-config reading BIOS (default)

I edit /etc/modprobe.conf to add:
options snd-hda-intel model=3stack-6ch-dig

At this point I'm told to reboot or restart the service. I don't want to reboot, that's slow, but nobody mentions how to restart the service. So I just ran:
# alsamixer

alsamixer: function snd_mixer_load failed: Invalid argument

Maybe I am on the right track, so I try all model names, getting the same results. I then remove the line I added and run alsamixer with the original modprobe.conf and it fails with the same invalid argument excuse.

Can you guide me through?

Restarting ALSA can get complex. I don't want to attempt an explanation.
Just reboot.

Hi there,

I've been fighting my soundproblem for about 24h now, getting tired of it.

Tried everything (and more), I was aware of this model issue because I used it before in my other Linux distro (PCLinuxOS) and it works like a charm in that distro.
But NOT in puppy 403 and 404.

When running the livecd Dmesg says model unknown for codec AC883 AND model unknown for codec AC268. When I change the modprobe.conf file model=laptop-eapd (same as I use in PCLinuxOS) and reboot dmesg says model unknown for codec AC268. In other words it recognizes the model for the AC883 codec. The speaker icon appears in the tray, but that's all.
Can't start alsamixer and still no sound!
When changing model to 3stack (for AC268) same story.

Why would it work in PCLinuxOS and not in puppy, I like puppy very much but it would be nicer with sound.

Any other ideas to get the sound working??

@Kaljo

Have you used the official release of Puppy version 4.00, and if so, does sound work for you with that version?

I'm gonna give that a trie right now, btw just read something about ALSA broken/fix in the developers blog.

I'm gonna logout Vista (ughh) and trie 4.0 get back to you in a min

No difference

I was to quick to give you an answer, I only looked at the output from dmesg and alsamixer.
When I tried playing a google/youtube video the sound was there!

Only lost my wireless, but using XP drivers with ndiswrapper solved the problem.

When upgrading from 400 to 404 the sound is still there with only one big difference: its half as loud (drop from 100% to 50%) as in 400.

Thanks for your superb idea on this one.

Offtopic: most distros have a button to go directly to the Desktop is this also possible in Puppy or should I open a new thread for this one?