You may need to do some research and find out which kernel module is needed for that particular intel device, and load it using Control Panel-->System-->Configure Kernel Modules. I believe it's i915, but you may want to research that further to be sure.

FWIW, In Slacko 533 the card is detected as hda-intel device 1e20 (rev04) and that's with alsa 1.0.24.2

Geoffrey and elroy: I suggest making PupControl available for Carolina,
I use it all the time when I am tweaking my system. It gives me easy access to most
of the items I need without having to dig into the guts of Carolina.

For others who might not know about pupcontrol; take a look at what it can do:
|http://murga-linux.com/puppy/viewtopic.php?t=61961

I think that pupshutdown would also be a great asset for Carolina.
It would give the shutdown routine a very polished look.
http://www.murga-linux.com/puppy/viewtopic.php?t=56077
Pete

pete,

I had a look at pupcontrol and pupshutdown, I see radky has added xmenumaker as an option in lieu of menumaker, though the shutdown gui still isn't fully compatible, I wouldn't think it would be something that will be added to Carolina at this time, without full compatibility.

We are sorting out the problems with wireless firmware at the moment and should have a fix very soon, I've managed to to get b43 and rt2800 working as they are the only devices I have to test, I've passed on the information to elroy, he will be able to update you on any progress._________________Carolina:Recent Repository Additions

- the b43 firmware has definitely gone walk-about and is missing (I know you are on the case here)

- it's a big download (by Puppy standards) - but it is already modular with the a and z drives - have you thought of providing separate downloads for each module? I know this doesn't work for burning a cd but will many people be doing this during testing?? I never burn cd's - always do manual frugal installs from the iso to test.

- your bespoke update mechanism seems to be causing some problems - any reason why you can't use the tried and tested pet or delta file routes to provide updates (delta files would need xdelta3 included in the base system).

- I installed the kernel-source and devx sfs's onto a pfix=ram frugal install (no savefile) to compile and got 2 strange loop4 and loop5 devices on the desktop....

Many of you have posted internet connectivity issues with Carolina. There is definitely some missing firmware. We hope to have addressed much of that by making the firmware available as a pet for now. It's located on the first post of this thread above the 'Patches' section. This firmware will be added to the next release, but this will allow some of you to sort out your connection issues at present.

When installing this pet, you will get file overwrite errors; ignore them, and choose to install anyway. The files that are overwritten are the firmware files already included with the beta release.

I have uploaded the delta file to allow the Broadcom wl wifi driver to be installed onto Carolina...Note - like Saluki (but unlike most other puppies) Carolina does not have xdelta3 included. Can I request that this is made part of the base system otherwise delta files are not supported?

I would recommend that you include both
rerwin_woof_fixes-delta-3f.pet and
broadcom_wl_delta-k3.2.13-ski.pet

in your base system to allow the multi-kernel Broadcom wl driver pet to be easily installed for anybody wanting this driver.

- the b43 firmware has definitely gone walk-about and is missing (I know you are on the case here)

We just released a firmware.pet that does include this (although you’re right, it was missing at the time of your post). It’s on the first post of this thread near the “Patches” section.

peebee wrote:

- it's a big download (by Puppy standards) - but it is already modular with the a and z drives - have you thought of providing separate downloads for each module?

That’s how Geoffrey and I originally did some testing before releasing 001. It certainly may be possible going forward for those that are strictly doing testing. But for those creating savefiles, it could render their savefile useless depending on the changes made to the other modules.

peebee wrote:

- your bespoke update mechanism seems to be causing some problems - any reason why you can't use the tried and tested pet or delta file routes to provide updates (delta files would need xdelta3 included in the base system).

I think the problem was more of a case of unfamiliarity; we discussed using pets, and if there are more issues, we may have to revisit the idea. Delta file support will be in the next release. We’ll have to look into using that for updates at that point.

peebee wrote:

- I installed the kernel-source and devx sfs's onto a pfix=ram frugal install (no savefile) to compile and got 2 strange loop4 and loop5 devices on the desktop....

That’s a peculiarity of the puppy-volume-monitor. Hopefully future versions of that package address that issue. Thankfully it doesn’t affect the functionality.

Sorry for my English ... I'm using an online translator.
xarchiver not give me the option to enter the password to extract. Not if I'm doing something wrong.
I love Carolina. I want to contribute what I can.
A hug.

" Many of you have posted internet connectivity issues with Carolina. There is definitely some missing firmware. We hope to have addressed much of that by making the firmware available as a pet for now. It's located on the first post of this thread above the 'Patches' section. This firmware will be added to the next release, but this will allow some of you to sort out your connection issues at present."

I downloaded the Carolina iso and I noticed that the /etc/modules/firmware.dep.3.2.13-ski file was missing in zdrv sfs. It is crucial file which steers the driver to find the corresponding firmware from the Puppy firmware location in /lib/modules/all-firmware/*

Also the b43 firmware folder content was empty, due to it has been replaced in Saluki to the /lib/firmware. It was because there was initial failure in one woof installed script. I suppose nowadays it can be as well in /lib/modules/all-firmware location.

Lets make a test. I created the firmware fix pet....which has that missing firmware.dep file and that missing b43 firmware content located to the /lib/modules/all-firmware.
Reboot is needed ( I suppose ) after installing this pet. Not sure if the firmware.dep file is absolutely correct, I copied it from dpup and just renamed it. But it gives you possibiity to test.

I downloaded the Carolina iso and I noticed that the /etc/modules/firmware.dep.3.2.13-ski file was missing in zdrv sfs. It is crucial file which steers the driver to find the corresponding firmware from the Puppy firmware location in /lib/modules/all-firmware/* ...

Thank you for your efforts, pemasu! I've added the above missing file to the firmware.pet on the 1st post of this thread.

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