ath5k_pci for wireless of the eeePC works out of the box, but the atl ethernet driver not. (This will be a good time to learn compiling of driver modules. Also, I wonder if fan control exists in the kernel?)
Audio works, including the microphone.
The Seamonkey page disappeared at full screen, reappeared when I restored the window (but this could be a seamonkey issue).
Hotpup does not automatically load the USB flash drive when inserted, but that is fine with me - I used pmount. EDIT: My SD card is not automatically loaded by hotpup, but USB flash is.
The line "MU sleep 4" appears at boot time. Booting was fast (I used Grub), the only noticeable delay was during the loading of kernel drivers.
EDIT re SD card only not being auto-loaded by hotpup.
Kernel 2.6.27 and squashfs 3.4 patch problem [solved]
ath5k_pci for eeePC
Last edited by raffy on Tue 14 Oct 2008, 20:38, edited 1 time in total.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
I updated the Iso, it now includes the updated firmware files.
raffy
I hope someone will have a look at the delay I added.
I described that issue in detail in the former messages.
Maybe it could be replaced with some intelligent code to check, if all drives were detected.
Delays are just a workaround.
We might gain 3-4 seconds like that
Loading the kerneldrivers will be a bit slower, as there are more included now.
I tried to add as many as I could.
Mark
raffy
yes, this is intended.The line "MU sleep 4" appears at boot time.
I hope someone will have a look at the delay I added.
I described that issue in detail in the former messages.
Maybe it could be replaced with some intelligent code to check, if all drives were detected.
Delays are just a workaround.
We might gain 3-4 seconds like that
Loading the kerneldrivers will be a bit slower, as there are more included now.
I tried to add as many as I could.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
@MU:
Well done!
My dual-Xeon system does not suffer the "missing hyperthread" and "slowdown in zlib" problems which I reported here.
***EDITED Nov. 20: it _does_ show the 4 hyperthreads...which is as it should be, i.e. hardinfo considers each hyperthread as a separate CPU)***
Oddly, PMount shows my SCSI drives as usb devices (same as Barry's "stock 4.1").
Seamonkey runs extremely fast...now to try ttuuxx's Firepup-.02 with this kernel...
(***edited) Firepup is fast indeed...but, Seamonkey is fast too...
Well done!
My dual-Xeon system does not suffer the "missing hyperthread" and "slowdown in zlib" problems which I reported here.
***EDITED Nov. 20: it _does_ show the 4 hyperthreads...which is as it should be, i.e. hardinfo considers each hyperthread as a separate CPU)***
Oddly, PMount shows my SCSI drives as usb devices (same as Barry's "stock 4.1").
Seamonkey runs extremely fast...now to try ttuuxx's Firepup-.02 with this kernel...
(***edited) Firepup is fast indeed...but, Seamonkey is fast too...
Last edited by Sit Heel Speak on Fri 21 Nov 2008, 02:26, edited 1 time in total.
Here's the promised lzma patch for 2.6.27. The good news is taht it looks like this feature will soon be pulled into the main kernel branch. the bad nes is that the patch is till being reworked to please the kernel devs. It has already been updated 5 times, but the attached patch is an earlier version that works. the latest revisions are still having problems since they move lots of exiting kernel code around. to my credit, before I found these later patches, I got the old one working on my own. But I have attached the best alternative(for the moment) from the guy who is writing the patch. His work is based on an earlier idea which added bzip2 support to the 2.4 kernel. I use the original patch with my 2.4 kernels and it works fine.
If you want to try this patch, apply it after the other patches you are using with 2.6.27.
If you want to try this patch, apply it after the other patches you are using with 2.6.27.
....
If you want to try this patch, apply it after the other patches you are using with 2.6.27.
Sorry, I had trouble attaching the patch. Here it is:
If you want to try this patch, apply it after the other patches you are using with 2.6.27.
Sorry, I had trouble attaching the patch. Here it is:
- Attachments
-
- updated-lzma-2.6.27.diff.gz
- (26.66 KiB) Downloaded 316 times
Hi Mark,
I tested your updated iso (updated in response to aragon) on my work laptop, a toshiba with dual-core Core CPUs. Everything works fine except the wireless - which uses iwl3945 driver, just like aragon, same error message.
I did a little bit of investigation, the /lib/firmware doesn't contain anything that sounds like iwl or 3945, so I mounted the original pup_410.sfs from 4.1 release, copy all the /lib/modules/all-firmware directory from there to the same location.
Then I tried to bring the wlan0 up, still the same error. I did a quick look at the this newly-copied /lib/modules/all-firmware, I found iwlwifi.tgz which sounds like the correct driver, and I extracted it to /lib/firmware. Then I tried to bring wlan0 up again. This time it works !!!
So I guess we need to copy the all-firmware directory from 4.1 release, but I wonder why the auto-loading doesn't work ... why it has to be manually expanded. Or perhaps we should just expand it ... since it's contained within pup_410.sfs, which is already compressed.
cheers!
EDIT: I tried to boot from original 4.1, and I confirm the firmware is automatically detected and extracted into /lib/firmware.
I tested your updated iso (updated in response to aragon) on my work laptop, a toshiba with dual-core Core CPUs. Everything works fine except the wireless - which uses iwl3945 driver, just like aragon, same error message.
I did a little bit of investigation, the /lib/firmware doesn't contain anything that sounds like iwl or 3945, so I mounted the original pup_410.sfs from 4.1 release, copy all the /lib/modules/all-firmware directory from there to the same location.
Then I tried to bring the wlan0 up, still the same error. I did a quick look at the this newly-copied /lib/modules/all-firmware, I found iwlwifi.tgz which sounds like the correct driver, and I extracted it to /lib/firmware. Then I tried to bring wlan0 up again. This time it works !!!
So I guess we need to copy the all-firmware directory from 4.1 release, but I wonder why the auto-loading doesn't work ... why it has to be manually expanded. Or perhaps we should just expand it ... since it's contained within pup_410.sfs, which is already compressed.
cheers!
EDIT: I tried to boot from original 4.1, and I confirm the firmware is automatically detected and extracted into /lib/firmware.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Hey Mark
I was doing a lot of downloads yesterday
so today I had a chance to boot into your new test iso
all booted fine and seems to be working fine
I included my bootkernel.log so you can look over it
and see what was detected
P.S after looking at all you had to do to compile on puppy
its good you got it working so quickly
it took me two days to apply it and getting it working on Slackware using a different kernel (slackware 12.1 )
so I understand the effort you invested
great work
big_bass
I was doing a lot of downloads yesterday
so today I had a chance to boot into your new test iso
all booted fine and seems to be working fine
I included my bootkernel.log so you can look over it
and see what was detected
P.S after looking at all you had to do to compile on puppy
its good you got it working so quickly
it took me two days to apply it and getting it working on Slackware using a different kernel (slackware 12.1 )
so I understand the effort you invested
great work
big_bass
- Attachments
-
- bootkernel_logs.tar.gz
- (5.59 KiB) Downloaded 331 times
jamesbond
I found:
/etc/modules/
It includes a file called
firmware.dep.2.6.25.16
I wonder how this file is created?
I think it had to be renamed to
firmware.dep.2.6.27
It also should be updated to the firmware that comes with the new kernel, but for a first test, we could ignore that.
I wonder, if your firmware now gets extracted correctly?
Who knows, how this file is created?
And what is /etc/modules/DOTconfig-K2.6.25.16 needed for?
Is it there for documentation, or is it scanned by some scripts?
Mark
I found:
/etc/modules/
It includes a file called
firmware.dep.2.6.25.16
I wonder how this file is created?
I think it had to be renamed to
firmware.dep.2.6.27
It also should be updated to the firmware that comes with the new kernel, but for a first test, we could ignore that.
I wonder, if your firmware now gets extracted correctly?
Who knows, how this file is created?
And what is /etc/modules/DOTconfig-K2.6.25.16 needed for?
Is it there for documentation, or is it scanned by some scripts?
Mark
Last edited by MU on Wed 15 Oct 2008, 19:25, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
yes, so we had to copy /lib/modules/2.6.27/.config to
/etc/modules/DOTconfig-K2.6.27
For those who did not download the source sfs, here is the config:
http://www.murga-linux.com/puppy/viewto ... 215#239215
Now I must find from which files the firmware.dep is created.
Maybe I have to write a small script, that generates it.
Mark
/etc/modules/DOTconfig-K2.6.27
For those who did not download the source sfs, here is the config:
http://www.murga-linux.com/puppy/viewto ... 215#239215
Now I must find from which files the firmware.dep is created.
Maybe I have to write a small script, that generates it.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
MU wrote:jamesbond
I found:
/etc/modules/
It includes a file called
firmware.dep.2.6.25.16
I wonder how this file is created?
I think it had to be renamed to
firmware.dep.2.6.27
It also should be updated to the firmware that comes with the new kernel, but for a first test, we could ignore that.
I wonder, if your firmware now gets extracted correctly?
Who knows, how this file is created?
And what is /etc/modules/DOTconfig-K2.6.25.16 needed for?
Is it there for documentation, or is it scanned by some scripts?
Mark
Hey Mark
in the unleashed createpuppy script there is a reference to /lib/modules
not etc/modules
this all gets built in unleashed
********************************cut and pasted relevant lines of createpuppy script************
--------------------------------not the complete script ----------------------------------------
cp -a kernels/$USEKERNEL/firmware.dep.$USEKERNEL
echo "" >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
echo '#These are the directories and files in each firmware pkg...' >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
echo "Adding $ONEFIRM filelist to modules-complete/lib/modules/firmware.dep.$USEKERNEL..."
cp -af kernels/$USEKERNEL/all-firmware/$ONEFIRM/* modules-complete/
#need a list of all files in the package...
echo -n "${ONEFIRM}|" >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
cd kernels/$USEKERNEL/all-firmware/$ONEFIRM
find ./ -mount | sed -e 's/^\.//g' | grep -v '^/$' | tr ' ' '_' | tr '\n' ' ' >> $PUPPYDIR/modules-complete/lib/modules/firmware.dep.$USEKERNEL
sync
echo >> $PUPPYDIR/modules-complete/lib/modules/firmware.dep.$USEKERNEL
cd $PUPPYDIR
done
sync
******************************************************************************************************
hope that helps btw that was a code snipit from 3.01 unleashed I dont know if in version
4.00 that got changed
big_bass
ok thanks, that might help...
I encountered other issues in this context.
1.) I could not find out, where the firmware comes from.
I could not find it in the Kernelsource, that has much less firmware files.
So I think the firmware files are something, that Barry got somewhere else.
For example iwl3945.ko IS part of the Kernelsource 2.6.27.
But /lib/firmware/iwlwifi-3945-1.ucode is NOT.
That file is only available in Puppy 4.1.
I also could not find it in the 3rd party modules at:
http://puptrix.org/sources/kernel-2.6.25.16/
So I then wanted to use the /lib/modules/all-firmware/ from Puppy 4.1.
But I encountered the same problem as jamesbond.
When I type:
modprobe iwl3945
then the
/lib/modules/all-firmware/iwlwifi.tar.gz
is NOT extracted.
I then thought it might have to do with a new kerneloption
CONFIG_FIRMWARE_IN_KERNEL = y
http://cateee.net/lkddb/web-lkddb/FIRMW ... ERNEL.html
So I deactivated it, and recompiled the Kernel.
But without success.
2.) Then I ran Puppy 4.1 original again (2.6.25.16).
Here I had the same problem:
When I type:
modprobe iwl3945
then the
/lib/modules/all-firmware/iwlwifi.tar.gz
is NOT extracted.
Same is with
modprobe dvb-usb
That problem was reported by linuxcbon here:
http://www.murga-linux.com/puppy/viewtopic.php?p=237657
So it seems, there is something wrong with the extraction of the firmware modules.
I then thought, that I might extract them all.
But that would work just in Puppy 3, that has a modified modprobe script.
It executes installation scripts, that are included in the firmware packages.
Like pinstall.slmodem.sh.
In Puppy 4, this mechanism is no longer used, instead, it is executed by the new (for me nonworking) event based extraction.
Fortunately, only some modems seem to have these scripts:
pinstall.dgcmodem.sh
pinstall.ltmodem.sh
pinstall.mwavem-1.0.2.sh
pinstall.pgprs.sh
pinstall.slmodem.sh
So I think I will rebuild the iso with the extracted firmware, and accept, that these modems will not work, unless the scripts are executed by hand.
This seems the best compromize, until a solution/bugfix is found.
The disadvantage is, that some firmware packages put scripts in /etc/init.d/ , what might slow down startup.
But I will test it, Muppy Live uses this solution, too.
Mark
I encountered other issues in this context.
1.) I could not find out, where the firmware comes from.
I could not find it in the Kernelsource, that has much less firmware files.
So I think the firmware files are something, that Barry got somewhere else.
For example iwl3945.ko IS part of the Kernelsource 2.6.27.
But /lib/firmware/iwlwifi-3945-1.ucode is NOT.
That file is only available in Puppy 4.1.
I also could not find it in the 3rd party modules at:
http://puptrix.org/sources/kernel-2.6.25.16/
So I then wanted to use the /lib/modules/all-firmware/ from Puppy 4.1.
But I encountered the same problem as jamesbond.
When I type:
modprobe iwl3945
then the
/lib/modules/all-firmware/iwlwifi.tar.gz
is NOT extracted.
I then thought it might have to do with a new kerneloption
CONFIG_FIRMWARE_IN_KERNEL = y
http://cateee.net/lkddb/web-lkddb/FIRMW ... ERNEL.html
So I deactivated it, and recompiled the Kernel.
But without success.
2.) Then I ran Puppy 4.1 original again (2.6.25.16).
Here I had the same problem:
When I type:
modprobe iwl3945
then the
/lib/modules/all-firmware/iwlwifi.tar.gz
is NOT extracted.
Same is with
modprobe dvb-usb
That problem was reported by linuxcbon here:
http://www.murga-linux.com/puppy/viewtopic.php?p=237657
So it seems, there is something wrong with the extraction of the firmware modules.
I then thought, that I might extract them all.
But that would work just in Puppy 3, that has a modified modprobe script.
It executes installation scripts, that are included in the firmware packages.
Like pinstall.slmodem.sh.
In Puppy 4, this mechanism is no longer used, instead, it is executed by the new (for me nonworking) event based extraction.
Fortunately, only some modems seem to have these scripts:
pinstall.dgcmodem.sh
pinstall.ltmodem.sh
pinstall.mwavem-1.0.2.sh
pinstall.pgprs.sh
pinstall.slmodem.sh
So I think I will rebuild the iso with the extracted firmware, and accept, that these modems will not work, unless the scripts are executed by hand.
This seems the best compromize, until a solution/bugfix is found.
The disadvantage is, that some firmware packages put scripts in /etc/init.d/ , what might slow down startup.
But I will test it, Muppy Live uses this solution, too.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
I updated the Iso.
The Kernel now uses the lzma patch provided by Amigo.
I included the firmware from the original Puppy.
It is extracted, except these modem firmware packages:
dgcmodem.tar.gz
ltmodem.tar.gz
mwavem-1.0.2.tar.gz
pgprs.tar.gz
slmodem.tar.gz
Those have these pinstallscripts described above, so simply extracting them would make no sense.
Instead, the extraction script should be enhanced to work on every computer.
So Puppys firmware also should work, if on your computer the automatic extraction does not work.
The files in /etc/modules were updated/renamed.
I also upgraded the networkwizard to oct-11th.
And added the Glint xorg driver.
And I modified init again.
I removed the 4 seconds delay (and also the 3 seconds for classmate), and instead added a check, if usb-storage had finished to scan for drives.
Barry already had such code there, but for me, it did not work. I think, that is also, why he had added the 3 seconds for the classmate.
So I replaced it with own one, I hope this works for everybody.
Mark
The Kernel now uses the lzma patch provided by Amigo.
I included the firmware from the original Puppy.
It is extracted, except these modem firmware packages:
dgcmodem.tar.gz
ltmodem.tar.gz
mwavem-1.0.2.tar.gz
pgprs.tar.gz
slmodem.tar.gz
Those have these pinstallscripts described above, so simply extracting them would make no sense.
Instead, the extraction script should be enhanced to work on every computer.
So Puppys firmware also should work, if on your computer the automatic extraction does not work.
The files in /etc/modules were updated/renamed.
I also upgraded the networkwizard to oct-11th.
And added the Glint xorg driver.
And I modified init again.
I removed the 4 seconds delay (and also the 3 seconds for classmate), and instead added a check, if usb-storage had finished to scan for drives.
Barry already had such code there, but for me, it did not work. I think, that is also, why he had added the 3 seconds for the classmate.
So I replaced it with own one, I hope this works for everybody.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
hi mark,
i will test this evening.
one more question: did you compile the kernel with the "tickless idle"?
cheers
aragon
i will test this evening.
one more question: did you compile the kernel with the "tickless idle"?
cheers
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
Thanks Mark,
I'm downloading and once finished, I'll test it.
However, your point about this is strange:
http://puppylinux.com/blog/?viewDetailed=00406
and this:
http://puppylinux.com/blog/?viewDetailed=00108
and this:
http://puppylinux.com/blog/?viewDetailed=00121
and this:
http://puppylinux.com/technical/module-loading.htm
Seems to be that the module extraction is done prior to modprobe, therefore, the example you show, by doing modprobe iwl3945 doesn't work because you don't have the actual iwl3945 hardware? (which is the one that triggers the uevent and therefore extract the module)?
Anyway - as long as it works - I don't mind
cheers!
I'm downloading and once finished, I'll test it.
However, your point about this is strange:
The laptop I'm using to test has this iwl3945 device. With Puppy 4.1 original, after boot up is finished, iwlwifi-3945-1.ucode is already extracted into /lib/firmware. I'm not sure of the mechanism - a few searches in Barry's blog such as this:MU wrote: 2.) Then I ran Puppy 4.1 original again (2.6.25.16).
Here I had the same problem:
When I type:
modprobe iwl3945
then the
/lib/modules/all-firmware/iwlwifi.tar.gz
is NOT extracted.
http://puppylinux.com/blog/?viewDetailed=00406
and this:
http://puppylinux.com/blog/?viewDetailed=00108
and this:
http://puppylinux.com/blog/?viewDetailed=00121
and this:
http://puppylinux.com/technical/module-loading.htm
Seems to be that the module extraction is done prior to modprobe, therefore, the example you show, by doing modprobe iwl3945 doesn't work because you don't have the actual iwl3945 hardware? (which is the one that triggers the uevent and therefore extract the module)?
Anyway - as long as it works - I don't mind
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I tested. The wireless iwl3945 works now.
(well, actually, it doesn't work from the network-wizard - I noted that you have thrown in the oct11 version --- I had to manually hack wpa_supplicant.conf, but that's another problem which doesn't belong in this thread).
Thanks !
(well, actually, it doesn't work from the network-wizard - I noted that you have thrown in the oct11 version --- I had to manually hack wpa_supplicant.conf, but that's another problem which doesn't belong in this thread).
Thanks !
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
-
Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Hi Mark,
This third version incorrectly shows my rig as having 4 processors in "System-->Hardinfo-->Summary" and "-->Processor" as I reported here.
Your second version correctly shows 2 processors.
***EDITED November 20: 4 processors _should_ be shown. Not sure why the 2nd was showing only 2.***
(rest deleted by poster)
This third version incorrectly shows my rig as having 4 processors in "System-->Hardinfo-->Summary" and "-->Processor" as I reported here.
Your second version correctly shows 2 processors.
***EDITED November 20: 4 processors _should_ be shown. Not sure why the 2nd was showing only 2.***
(rest deleted by poster)
Last edited by Sit Heel Speak on Fri 21 Nov 2008, 03:58, edited 1 time in total.
Sit Heel Speak
this is very astonishing.
I just made a change in this firmware option, and added lzma.
The change then required, to answer some more questions concerning firmware.
So I think, the issue will be here. I could not imagine, that the lzma patch would cause a slowdown.
On the other hand, it just saves around 350 kb.
I think the best will be, to take version 2 again.
Then add my initrd patch, and the compressed firmware.
Barry explained why the firmware was not extracted, it would require a reboot:
http://www.puppylinux.com/blog/?viewDetailed=00421
I just bought a DVBT Stick, so that I can check on my own, if the extraction works.
If I have success, I'll use this scenario for a new iso tomorrow.
Mark
this is very astonishing.
I just made a change in this firmware option, and added lzma.
The change then required, to answer some more questions concerning firmware.
So I think, the issue will be here. I could not imagine, that the lzma patch would cause a slowdown.
On the other hand, it just saves around 350 kb.
I think the best will be, to take version 2 again.
Then add my initrd patch, and the compressed firmware.
Barry explained why the firmware was not extracted, it would require a reboot:
http://www.puppylinux.com/blog/?viewDetailed=00421
I just bought a DVBT Stick, so that I can check on my own, if the extraction works.
If I have success, I'll use this scenario for a new iso tomorrow.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
it's /etc/modules/firmware.dep.<kernel version>.big_bass wrote:MU wrote:jamesbond
I found:
/etc/modules/
It includes a file called
firmware.dep.2.6.25.16
I wonder how this file is created?
I think it had to be renamed to
firmware.dep.2.6.27
It also should be updated to the firmware that comes with the new kernel, but for a first test, we could ignore that.
I wonder, if your firmware now gets extracted correctly?
Who knows, how this file is created?
And what is /etc/modules/DOTconfig-K2.6.25.16 needed for?
Is it there for documentation, or is it scanned by some scripts?
Mark
Hey Mark
in the unleashed createpuppy script there is a reference to /lib/modules
not etc/modules
this all gets built in unleashed
********************************cut and pasted relevant lines of createpuppy script************
--------------------------------not the complete script ----------------------------------------
cp -a kernels/$USEKERNEL/firmware.dep.$USEKERNEL
echo "" >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
echo '#These are the directories and files in each firmware pkg...' >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
echo "Adding $ONEFIRM filelist to modules-complete/lib/modules/firmware.dep.$USEKERNEL..."
cp -af kernels/$USEKERNEL/all-firmware/$ONEFIRM/* modules-complete/
#need a list of all files in the package...
echo -n "${ONEFIRM}|" >> modules-complete/lib/modules/firmware.dep.$USEKERNEL
cd kernels/$USEKERNEL/all-firmware/$ONEFIRM
find ./ -mount | sed -e 's/^\.//g' | grep -v '^/$' | tr ' ' '_' | tr '\n' ' ' >> $PUPPYDIR/modules-complete/lib/modules/firmware.dep.$USEKERNEL
sync
echo >> $PUPPYDIR/modules-complete/lib/modules/firmware.dep.$USEKERNEL
cd $PUPPYDIR
done
sync
******************************************************************************************************
hope that helps btw that was a code snipit from 3.01 unleashed I dont know if in version
4.00 that got changed
big_bass
You should be looking in the latest Unleashed, that is, for 4.1.
The firmware.dep files are manually created and are in Unleashed, in puppy-unleashed/kernels/<kernel version>/firmware.dep.<kernel version>
For 2.6.27, you can just copy all of puppy-unleashed/kernels/2.6.25.16/all-firmware, and copy firmware.dep.2.6.25.16 (and rename to firmware.dep.2.6.27) to puppy-unleashed/kernels/2.6.27/.
[url]https://bkhome.org/news/[/url]