Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
lucho115 wrote:i use sysvconfig , rcconf and sysv-rc-conf but i cant remove from the init the avahi and hal daemons, where i have to look to disable to load at boot time, anybod knows?
thks
OK, thanks but if you look my first post i said " i use sysvconfig , rcconf and sysv-rc-conf but i cant remove ...."
I remove avahi and hal at rc levels and at rcS, but still up with the system boot.
Any other tip??
lucho115 wrote:OK, thanks but if you look my first post i said " i use sysvconfig , rcconf and sysv-rc-conf but i cant remove ...."
I remove avahi and hal at rc levels and at rcS, but still up with the system boot.
Any other tip??
What else do you have running? Some other daemons depend on it and start it if they need it.
Why does my boot try to start some modules twice? I can't say which because the screen goes by too fast, but there are seven or eight modules that it attempts to double load. This has only been happening with the 2.4.6-18.3 & 4 kernels. I've hunted through /var/log but haven't seen it. Any idea which log I should look in?
I've been trying to streamline the boot as much as possible and would like to stop the duplication.
make sure the bootlogd package is installed. then edit /etc/default/bootlogd as root to enable the service.
issue the following as root:
ln -s /etc/init.d/bootlogd /etc/rcS.d/S00bootlogd
On next boot youll find a log in /var/log/boot of everything that was output to the screen during bootup.
Also, /etc/modules (or maybe /etc/modules-<kernel version>) is the list of all modules loaded at boot by modutils and the like.. though other init scripts in /etc/rc*.d may also be trying to load your dupes... Look through the bootlog and youll be able to narrow it down to what may be loading them and when.
Would removing the unused xserver dependencies make Debian's binary xorg go any faster?
i A xserver-xorg-video-tga - X.Org X server -- TGA display driver
i A xserver-xorg-video-trident - X.Org X server -- Trident display driver
i A xserver-xorg-video-tseng - X.Org X server -- Tseng display driver
i A xserver-xorg-video-v4l - X.Org X server -- Video 4 Linux display dr
i A xserver-xorg-video-vesa - X.Org X server -- VESA display driver
i A xserver-xorg-video-vga - X.Org X server -- VGA display driver
i A xserver-xorg-video-via - X.Org X server -- VIA display driver
i A xserver-xorg-video-vmware - X.Org X server -- VMware display driver
i A xserver-xorg-video-voodoo - X.Org X server
After running it through aptitude --simulate, it seems that removing any of those drivers would break the xserver-xorg package. I guess I'll just leave it alone then.
Sun May 13 17:04:30 2007: Cleaning up ifupdown....
Sun May 13 17:04:30 2007: Loading kernel module ide-floppy.
Sun May 13 17:04:30 2007: Loading kernel module ide-cd.
Sun May 13 17:04:30 2007: Loading kernel module psmouse.
Sun May 13 17:04:30 2007: Loading kernel module mousedev.
Sun May 13 17:04:30 2007: Loading kernel module usbhid.
Sun May 13 17:04:30 2007: Loading kernel module i2c-isa.
Sun May 13 17:04:30 2007: Loading kernel module eeprom.
Sun May 13 17:04:30 2007: Loading kernel module w83627ehf.
Sun May 13 17:04:30 2007: Loading device-mapper support.
Sun May 13 17:04:30 2007: Will now check all file systems.
. . . . . . .
Sun May 13 17:04:30 2007: Detecting hardware...Discovered hardware for these modules: amd64_agp i2c_viapro tulip sata_via via82cxxx snd_via82xx uhci_hcd ehci_hcd
Sun May 13 17:04:30 2007: ^[[33m*^[[39;49m Skipping already loaded module amd64_agp.
Sun May 13 17:04:30 2007: ^[[33m*^[[39;49m Skipping already loaded module i2c_viapro.
Sun May 13 17:04:30 2007: ^[[33m*^[[39;49m Skipping already loaded module tulip.
Sun May 13 17:04:31 2007: ^[[33m*^[[39;49m Skipping already loaded module sata_via.
Sun May 13 17:04:31 2007: ^[[33m*^[[39;49m Skipping already loaded module via82cxxx.
Sun May 13 17:04:31 2007: ^[[33m*^[[39;49m Skipping already loaded module snd_via82xx.
Sun May 13 17:04:31 2007: ^[[33m*^[[39;49m Skipping already loaded module uhci_hcd.
Sun May 13 17:04:31 2007: ^[[33m*^[[39;49m Skipping already loaded module ehci_hcd.
It looks to me that the kernel is loading, or has pre-loaded, modules and then hardware detection is trying to do it all over again. Or am I mis-interpreting?
Every cloud has a silver lining, except for the mushroom shaped ones, which have a lining of Strontium 90.
---------------------------------------------
umop apisdn
After running it through aptitude --simulate, it seems that removing any of those drivers would break the xserver-xorg package. I guess I'll just leave it alone then.
I removed them with apt (two or three months ago) - i had no problems with xorg.
After running it through aptitude --simulate, it seems that removing any of those drivers would break the xserver-xorg package. I guess I'll just leave it alone then.
I removed them with apt (two or three months ago) - i had no problems with xorg.
Did it increase your speed though?
And is there any way to tell which ones are in use so I don't remove something I'm using?
I don`t think there was a noticeable increase in speed. I did it becuase at that time i had decided to remove everything i didn`t need and i obviously didn`t need these packages. For example i dodn`t have a via video card so i don`t need xserver-xorg-video-via - X.Org X server . The same goes for all the xorg packages - just see their description and decide for for yourslef. I removed most of the xserver-xorg-video-* packages (i kept only xserver-xorg-video-intel,vesa,v4l and vga). Also i removed most of the xserver-xorg-input packages (i kept packages like evdev, kbd, mouse, synaptics and wacom). The point is you can safely remove such packages, even if there is no speed increase you don`t need them.
it looks to me that the kernel is loading, or has pre-loaded, modules and then hardware detection is trying to do it all over again. Or am I mis-interpreting?
It looks like those modules are loaded by modutils because they are already listed in /etc/modules.... then later on discover tries to load all needed modules... etc
2 ways to approach this depending on your taste.
Either keep discover: edit /etc/modules and remove all the modules that its complaining about since they will be loaded by discover.
Or ditch it in favor of a faster bootup. though you may have to edit /etc/modules from time to time if your hardware changes.