<SOLVED>Remove hardware drivers from Puppy-is it possible?
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
<SOLVED>Remove hardware drivers from Puppy-is it possible?
I need to remove (uninstall) hardware drivers (ex. all hard-drive drivers or all sound drivers or all ) from Puppy Linux.
Is this possible?
Thank you for any help!
Is this possible?
Thank you for any help!
Last edited by laurentius77 on Wed 04 May 2011, 08:33, edited 1 time in total.
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
Thank you for information. Now I have to ask you something: how can I do that?abushcrafter wrote:Yes.
I have Puppy 5.2 installed on usb drive (frugal install) and I want to remove all hard-drive drivers. I want to do this because I don't want my Puppy Linux to touch (access) computers hard-drive (where I boot Puppy an run it). Same thing for network cards or sound cards or other hardware it will be great. The fact is that I want a Puppy distribution with customized hardware drivers.
Can you help me, please?
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
I found this article http://www.cyberciti.biz/faq/add-remove ... l-modules/ about removing module from kernel in Linux. The problem is I didn't identified hard-drive modules after lsmod command. I don't know for sure if rmmod command is for my needs but I have a start point...
Drivers come in 2 flavours:
a) those which are stored outside the kernel, these are called kernel module. The purpose of kernel modules is to allow them do be loaded/unloaded at will.
b) those which are compiled inside kernel, they are part of vmlinuz. These drivers are always activated when the kernel is running (ie you use the OS).
For a), it's easy to remove them - just go to /lib/modules/`uname -r` and start deleting those files that ends with .ko (.ko stands for "kernel object", ie, kernel modules).
"rmmod" command does not remove modules - it's used to "unload" a module.
For b) it's impossible to remove them without recompiling the kernel.
You're in bad luck then. I think most puppies have the harddisk drivers (ATA/SATA drivers) compiled in as part of the kernel.
cheers!
a) those which are stored outside the kernel, these are called kernel module. The purpose of kernel modules is to allow them do be loaded/unloaded at will.
b) those which are compiled inside kernel, they are part of vmlinuz. These drivers are always activated when the kernel is running (ie you use the OS).
For a), it's easy to remove them - just go to /lib/modules/`uname -r` and start deleting those files that ends with .ko (.ko stands for "kernel object", ie, kernel modules).
"rmmod" command does not remove modules - it's used to "unload" a module.
For b) it's impossible to remove them without recompiling the kernel.
You're in bad luck then. I think most puppies have the harddisk drivers (ATA/SATA drivers) compiled in as part of the kernel.
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]
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
Thank you jamesbond for you response. I found a link with a tutorial for recompiling the kernel in Puppy, I hope it will work for my Puppy 5.2.5.
This is the link
http://pateo.wordpress.com/2009/12/25/h ... inux-dpup/
The only distribution that I know with modules outside the kernel is pupeee.
But I remember there is an option (I never used this option and I don't know if it's present in puppy 5.2) when remastering the Puppy .iso to put the drivers in a separate .sfs, maybe this can be a trick to avoid recompiling the puppy kernel.
I will try both methods.
This is the link
http://pateo.wordpress.com/2009/12/25/h ... inux-dpup/
The only distribution that I know with modules outside the kernel is pupeee.
But I remember there is an option (I never used this option and I don't know if it's present in puppy 5.2) when remastering the Puppy .iso to put the drivers in a separate .sfs, maybe this can be a trick to avoid recompiling the puppy kernel.
I will try both methods.
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
I compiled a new puppy kernel without hard-drive modules using this great tutorial:
http://brainwavedesigncentral.net/dima/ ... nel-howto/
I found some minor typing mistakes which i solved myself.
Thanks to the author for this great tutorial, this is real a compiling kernel tutorial for beginners.
After having the modules installed and kernel ready there is a command for installing the kernel modules into a directory, which will be turned into a PET package later:
make INSTALL_MOD_PATH=linux_kernel-2.6.45.9-bfs install
But after run this command i got an error:
sh /root/linux_kernel-2.6.45.9-bfs/linux-2.6.35.9/arch/x86/boot/instal.sh 2.6.35.9 arch/x86/boot/bzImage \
System.map "boot"
/root/linux_kernel-2.6.35.9-bfs/linux-2.6.35.9/arch/x86/boot/install.sh: line 49
: /boot/vmlinuz: No such file or directory
cp: cannot create regular file '/boot/System.map': No such file or directory
Cannot find LILO.
I'm stuck... Please help in solving this problem!
http://brainwavedesigncentral.net/dima/ ... nel-howto/
I found some minor typing mistakes which i solved myself.
Thanks to the author for this great tutorial, this is real a compiling kernel tutorial for beginners.
After having the modules installed and kernel ready there is a command for installing the kernel modules into a directory, which will be turned into a PET package later:
make INSTALL_MOD_PATH=linux_kernel-2.6.45.9-bfs install
But after run this command i got an error:
sh /root/linux_kernel-2.6.45.9-bfs/linux-2.6.35.9/arch/x86/boot/instal.sh 2.6.35.9 arch/x86/boot/bzImage \
System.map "boot"
/root/linux_kernel-2.6.35.9-bfs/linux-2.6.35.9/arch/x86/boot/install.sh: line 49
: /boot/vmlinuz: No such file or directory
cp: cannot create regular file '/boot/System.map': No such file or directory
Cannot find LILO.
I'm stuck... Please help in solving this problem!
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
Found the reason! The right command islaurentius77 wrote:I compiled a new puppy kernel without hard-drive modules using this great tutorial:
http://brainwavedesigncentral.net/dima/ ... nel-howto/
I found some minor typing mistakes which i solved myself.
Thanks to the author for this great tutorial, this is real a compiling kernel tutorial for beginners.
After having the modules installed and kernel ready there is a command for installing the kernel modules into a directory, which will be turned into a PET package later:
make INSTALL_MOD_PATH=linux_kernel-2.6.45.9-bfs install
But after run this command i got an error:
sh /root/linux_kernel-2.6.45.9-bfs/linux-2.6.35.9/arch/x86/boot/instal.sh 2.6.35.9 arch/x86/boot/bzImage \
System.map "boot"
/root/linux_kernel-2.6.35.9-bfs/linux-2.6.35.9/arch/x86/boot/install.sh: line 49
: /boot/vmlinuz: No such file or directory
cp: cannot create regular file '/boot/System.map': No such file or directory
Cannot find LILO.
I'm stuck... Please help in solving this problem!
make INSTALL_MOD_PATH=linux_kernel-2.6.45.9-bfs modules_install
Thanks to Pemasu who posted a solution to this topic
http://www.murga-linux.com/puppy/viewtopic.php?t=67118
I have the kernel pet, now I have to test it using Woof builder
- RetroTechGuy
- Posts: 2947
- Joined: Tue 15 Dec 2009, 17:20
- Location: USA
I recall that some of the educational folks here (i.e. people involved in education, using Puppy as their platform) are working on some akin to that -- However, I don't know if they have solved it. They typically want either no access to the HDD, or read-only access -- for obvious reasons.laurentius77 wrote:Thank you for information. Now I have to ask you something: how can I do that?abushcrafter wrote:Yes.
I have Puppy 5.2 installed on usb drive (frugal install) and I want to remove all hard-drive drivers. I want to do this because I don't want my Puppy Linux to touch (access) computers hard-drive (where I boot Puppy an run it). Same thing for network cards or sound cards or other hardware it will be great. The fact is that I want a Puppy distribution with customized hardware drivers.
Can you help me, please?
Sorry, I can't find a thread right now.
I believe that gcmartin may be one of them -- I forget the other name at the moment...
I just did a search for "gcmartin turn off hard drive", I don't know if there is anything here that will help:
http://www.google.com/cse?cx=0159956439 ... =FORID%3A0
[url=http://murga-linux.com/puppy/viewtopic.php?t=58615]Add swapfile[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]
-
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
It seems that I finally have the kernel following tutorial from http://brainwavedesigncentral.net/dima/ ... nel-howto/ , using command
make INSTALL_MOD_PATH=linux_kernel-2.6.35.9-bfs modules_install instead of
make INSTALL_MOD_PATH=linux_kernel-2.6.35.9-bfs install
I couldn't yet compile a Puppy 525 distribution because there is a problem with the last Woof builder. The problem is that if no HD is found Puppy built with Woof can't boot and display an error "searching deeper" and "lupu_525.sfs not found". The problem was reported by user perthie on Barry's blog
http://bkhome.org/blog/?viewDetailed=02231
I will be able to test the kernel when Barry will fix this issue. Please let me know when you found out about fixing the issue, I will follow Barry's blog too.
Thanks for your help![/url]
make INSTALL_MOD_PATH=linux_kernel-2.6.35.9-bfs modules_install instead of
make INSTALL_MOD_PATH=linux_kernel-2.6.35.9-bfs install
I couldn't yet compile a Puppy 525 distribution because there is a problem with the last Woof builder. The problem is that if no HD is found Puppy built with Woof can't boot and display an error "searching deeper" and "lupu_525.sfs not found". The problem was reported by user perthie on Barry's blog
http://bkhome.org/blog/?viewDetailed=02231
I will be able to test the kernel when Barry will fix this issue. Please let me know when you found out about fixing the issue, I will follow Barry's blog too.
Thanks for your help![/url]