| View previous topic :: View next topic |
| Author |
Message |
romalong
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Kiev
|
 Posted: Sun Aug 14, 2005 8:21 pm Post subject: can't get rid of some modules?[solved] |
 |
|
everything was working properly before, but when i turned on iptables in kernel, my machine stopped working
i booted from livecd, killed /lib/modules/2.6.11-gentoo-r11/ directory and run these commands:
| Code: |
# zcat /proc/config.gz > /usr/share/genkernel/x86/kernel-2.6
# genkernel --udev all
|
now i can boot my box, but some errors about iptables still present during start up.
could someone explain me why?
Last edited by romalong on Tue Aug 16, 2005 7:34 am; edited 1 time in total |
|
| Back to top |
|
 |
romalong
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Kiev
|
| Posted: Sun Aug 14, 2005 8:49 pm Post subject: Re: can't get rid of some modules? |
|
|
| and also, initially, when i installed gentoo, my network and hd didn't work until i enabled support for them runnung # make menuconfig, but they're working after my aforementioned steps. i thought that if i clean modules and re-run genkernel, it should bring me my very first configuration. |
|
| Back to top |
|
|
Spiffster
Tux's lil' helper
Joined: 27 Jun 2004
Posts: 119
Location: Nærum, Denmark
|
| Posted: Sun Aug 14, 2005 8:56 pm Post subject: Re: can't get rid of some modules? |
|
|
| romalong wrote: | | now i can boot my box, but some errors about iptables still present during start up. |
What kind of errors? Are they kernel-errors from trying to load iptables-modules, or could they be due to the iptables init-script trying to load some rules?
_________________
Mikkel Holm Olsen
AKA Spaceman Spiff
http://symlink.dk |
|
| Back to top |
|
|
romalong
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Kiev
|
| Posted: Sun Aug 14, 2005 9:02 pm Post subject: Re: can't get rid of some modules? |
|
|
| Spiffster wrote: | | romalong wrote: | | now i can boot my box, but some errors about iptables still present during start up. |
What kind of errors? Are they kernel-errors from trying to load iptables-modules, or could they be due to the iptables init-script trying to load some rules? |
hold on please...
i need to understand why the things i've added manually before are still present in kernel |
|
| Back to top |
|
|
Spiffster
Tux's lil' helper
Joined: 27 Jun 2004
Posts: 119
Location: Nærum, Denmark
|
| Posted: Sun Aug 14, 2005 9:13 pm Post subject: Re: can't get rid of some modules? |
|
|
| romalong wrote: | hold on please...
i need to understand why the things i've added manually before are still present in kernel |
Well, if you get your configuration from /proc/config.gz, that would be the configuration of the running kernel (since the proc-filesystem is a virtual filesystem providing interfaces to the kernel).
So if you do this command while being booted from a LiveCD you would get the kernel-configuration of the LiveCD, and if you do it while being booted from your harddrive with some kernel you have configured in some way, you would get that configuartion.
I have never really used genkernel myself, but are you sure the kernel you are booting is newly compiled. What does "uname -a" say??
_________________
Mikkel Holm Olsen
AKA Spaceman Spiff
http://symlink.dk |
|
| Back to top |
|
|
romalong
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Kiev
|
| Posted: Sun Aug 14, 2005 9:23 pm Post subject: Re: can't get rid of some modules? |
|
|
| Spiffster wrote: | | romalong wrote: | hold on please...
i need to understand why the things i've added manually before are still present in kernel |
Well, if you get your configuration from /proc/config.gz, that would be the configuration of the running kernel (since the proc-filesystem is a virtual filesystem providing interfaces to the kernel).
So if you do this command while being booted from a LiveCD you would get the kernel-configuration of the LiveCD, and if you do it while being booted from your harddrive with some kernel you have configured in some way, you would get that configuartion.
I have never really used genkernel myself, but are you sure the kernel you are booting is newly compiled. What does "uname -a" say?? |
| Code: |
tux ~ # uname -a
Linux tux 2.6.11-gentoo-r11 #1 SMP Sun Aug 14 22:59:41 GMT 2005 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
|
i suppose, it's better to fix it manually rather loosing bunch of things i've configured earlier in my kernel, right?
where/how can i find an errors appeared during bootup?
i'cant catch them as it boots very fast   |
|
| Back to top |
|
|
Spiffster
Tux's lil' helper
Joined: 27 Jun 2004
Posts: 119
Location: Nærum, Denmark
|
| Posted: Mon Aug 15, 2005 7:35 pm Post subject: Re: can't get rid of some modules? |
|
|
| romalong wrote: | i suppose, it's better to fix it manually rather loosing bunch of things i've configured earlier in my kernel, right?
where/how can i find an errors appeared during bootup?
i'cant catch them as it boots very fast
|
All kernel messages go to the dmesg-ringbuffer. Once your system logger starts, the ringbuffer will be copied to the system logs, and the logger will keep dumping kernel messages.
If they are kernel-messages you see during bootup, you can dump them to a terminal by using the command dmesg. They should also be available in your kernel log, but this depends on which system logger you are using. For syslog-ng they would be in /var/log/messages, but if you are using a different logger, they may be in a differen file (although most likely in /var/log or perhaps /var/log/kernel/).
A different approach is to pause the bootup after the error is printed. This can be done by hitting CTRL-S (or scrolllock). You can now scroll back, by using shift-pgup to see the message. To continue press CTRL-Q (or scrolllock again). Actually CTRL-S is Xoff, which tells the terminal to stop outputting data, and CTRL-Q is Xon. So if you ever had a terminal hang (eg. if hitting CTRL-S in vi after being used to a different editor where CTRL-S is save), try hitting CTRL-Q, and there is a good chance it will come back to life.
When attempting the scrollback trick mentioned above, remember that switching virtual consoles clears the buffer, so if your system boots up directly into X, you need to pause it before X starts. After X has started, if you switch back to the first console (CTRL-ALT-F1), you will not be able to scroll back.
Hope this helps, at least diagnosing the problem. 
_________________
Mikkel Holm Olsen
AKA Spaceman Spiff
http://symlink.dk |
|
| Back to top |
|
|
romalong
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Kiev
|
| Posted: Tue Aug 16, 2005 7:33 am Post subject: Re: can't get rid of some modules? |
|
|
| Spiffster wrote: | | romalong wrote: | i suppose, it's better to fix it manually rather loosing bunch of things i've configured earlier in my kernel, right?
where/how can i find an errors appeared during bootup?
i'cant catch them as it boots very fast
|
All kernel messages go to the dmesg-ringbuffer. Once your system logger starts, the ringbuffer will be copied to the system logs, and the logger will keep dumping kernel messages.
If they are kernel-messages you see during bootup, you can dump them to a terminal by using the command dmesg. They should also be available in your kernel log, but this depends on which system logger you are using. For syslog-ng they would be in /var/log/messages, but if you are using a different logger, they may be in a differen file (although most likely in /var/log or perhaps /var/log/kernel/).
A different approach is to pause the bootup after the error is printed. This can be done by hitting CTRL-S (or scrolllock). You can now scroll back, by using shift-pgup to see the message. To continue press CTRL-Q (or scrolllock again). Actually CTRL-S is Xoff, which tells the terminal to stop outputting data, and CTRL-Q is Xon. So if you ever had a terminal hang (eg. if hitting CTRL-S in vi after being used to a different editor where CTRL-S is save), try hitting CTRL-Q, and there is a good chance it will come back to life.
When attempting the scrollback trick mentioned above, remember that switching virtual consoles clears the buffer, so if your system boots up directly into X, you need to pause it before X starts. After X has started, if you switch back to the first console (CTRL-ALT-F1), you will not be able to scroll back.
Hope this helps, at least diagnosing the problem. |
yes, you've been very helpful!
thank you! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
