You are not logged in.

#1 2008-12-04 03:04:51

ssl6
Member
From: Ottawa, ON, CA
Registered: 2007-08-30
Posts: 594

daemon startup order?

i managed to setup splashy, saw someone posted about it recently, so i decided to try it. now its bugging me, i seem to always have daemons fail to stop on shutdown, so the splash screen says something fails and kills the splash screen. it also says the same thing on startup, though none of the daemons seem to fail to start except ushare which i disabled. but it fails because it can't find eth0?

anyway, im more worried about the shutdown thing. listed below are the deamons i have, its hal that doesnt want to stop. im just wondering if theres a better order i should have them in rc.conf, maybe that would make a difference?
DAEMONS=(syslog-ng hal network netfs crond cpufreq networkmanager samba !ushare bluetooth kdm)

this is out of my errors log from my last reboot a few minutes ago, not sure if it helps

Dec  3 21:48:21 urmom-pc Aperture beyond 4GB. Ignoring.
Dec  3 21:48:21 urmom-pc Error: Driver 'pcspkr' is already registered, aborting...
Dec  3 21:48:32 urmom-pc uShare[3152]: Can't find interface /etc/eth0.
Dec  3 21:48:32 urmom-pc uShare[3152]: Recheck uShare's configuration and try again !
Dec  3 21:48:35 urmom-pc hcid[3190]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
Dec  3 21:48:36 urmom-pc hcid[3190]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Dec  3 21:48:36 urmom-pc hcid[3190]: Failed to listen on control channel
Dec  3 21:48:36 urmom-pc pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Dec  3 21:48:36 urmom-pc hcid[3282]: Can't set link policy on hci0: Operation not supported (95)
Dec  3 21:48:44 urmom-pc kdm_greet[3306]: Cannot open default user face
Dec  3 21:49:13 urmom-pc NVRM: Xid (0001:00): 13, 0002 beef3097 00004097 0000020c 40320000 00000002
Dec  3 21:49:35 urmom-pc uShare[3501]: Can't find interface /etc/eth0.
Dec  3 21:49:35 urmom-pc uShare[3501]: Recheck uShare's configuration and try again !
Dec  3 21:49:46 urmom-pc uShare[3526]: Can't find interface /etc/eth0.
Dec  3 21:49:46 urmom-pc uShare[3526]: Recheck uShare's configuration and try again !

maybe something from the deamons.log would help too?

Last edited by ssl6 (2008-12-04 03:05:53)


this is a signature

Offline

#2 2008-12-04 07:50:41

MindTooth
Member
From: Norway
Registered: 2008-11-11
Posts: 331

Re: daemon startup order?

Could you try add a @ infront of crond, bluetooth. And I guess it is safe to disable netfs.

Birger smile

Offline

#3 2008-12-04 10:47:40

deej
Member
Registered: 2008-02-08
Posts: 395

Re: daemon startup order?

Does disabling 'uShare' have any effect ?
I'd also disable 'pcspkr' and try adding 'iommu=noaperture' to the end of your kernel line in /boot/grub/menu.lst .
That will solve the 'Aperture beyond 4GB. Ignoring.' problem.

I take it that you compiled uShare yourself ?

Deej

Offline

#4 2008-12-04 17:16:30

ssl6
Member
From: Ottawa, ON, CA
Registered: 2007-08-30
Posts: 594

Re: daemon startup order?

i did compile ushare, i have the daemon disabled. the error in that log i posted above was /dev/eth0 that it can't find, i was saying before that it couldn't find eth0, so i tried giving it something more specific which didn't work either. so it wont load during boot. but i can start the daemon manually just fine after im logged in

where would i disable pcspkr?

and ill try the noaperture and see what happens. this is a 64 bit install btw if that makes a difference?


this is a signature

Offline

#5 2008-12-04 17:48:23

bgc1954
Member
From: Edmonton, AB, Canada
Registered: 2006-03-14
Posts: 1,160

Re: daemon startup order?

Disable pcspkr by adding it with a ! in front to MODULES=() in /etc/rc.conf.  Also add snd_pcsp as that has been causing trouble for people as well.

MODULES=(!pcspkr !snd_pcsp)

Last edited by bgc1954 (2008-12-04 17:48:45)


Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz

Offline

#6 2008-12-04 19:49:47

ssl6
Member
From: Ottawa, ON, CA
Registered: 2007-08-30
Posts: 594

Re: daemon startup order?

its not in there, this is all i have for the modules section

# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(forcedeth ac97_bus snd-mixer-oss snd-pcm-oss snd-seq-oss 
snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc 
snd-pcm snd-rawmidi snd-timer snd snd-ac97-codec snd-emu10k1 soundcore 
snd-util-mem powernow_k8 cpufreq_ondemand cpufreq_powersave vboxdrv)

and the noaperture line seemed to fry my splash screen. should that have been put in before splashy or after? what does that setting do anyway? im not sure why it would be beyond 4gb, i only have 2gb ram, and from what i've briefly read about that its to do with agp aperture, my video card is pci-e and its only 256mb. but this is what i have that i think will work again if i reboot

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/55fc7dce-8e40-44d2-82d9-25c0f183cf26 ro quiet vga=791 splash
initrd /kernel26.img

that aperture thing toasted my splash screen, and i get some message on startup about the video mode, it asks me to hit enter to choose a different mode and space to continue. how can i fix that now...

the fallback kernel doesnt give that error and if i remove " quiet vga=791 splash" the normal kernel works fine. but with it i get that video mode error

the error i get is "undefined video mode : 317" which is something to do with teh vga=791, i've tried 773, and 792 for example, and still get the error, and it only started doing that after i added the noapertureswitch, now i've removed that, but im still getting the error, so i need to fix that

Last edited by ssl6 (2008-12-04 20:30:26)


this is a signature

Offline

#7 2008-12-05 21:08:33

bgc1954
Member
From: Edmonton, AB, Canada
Registered: 2006-03-14
Posts: 1,160

Re: daemon startup order?

Sorry, somehow my point didn't get across.  !pcspkr and !snd_pcsp won't be in your MODULES line until you add it there yourself.


Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz

Offline

#8 2008-12-10 04:58:28

ssl6
Member
From: Ottawa, ON, CA
Registered: 2007-08-30
Posts: 594

Re: daemon startup order?

oh, cool, i ended up getting around my last problem, the video mode thing, it was caused by an external drive for some reason, i did some googling and eventually found a forum post somewhere that someone said they had that problem caused by a usb key, so i unplugged some stuff and it worked


this is a signature

Offline

Board footer

Powered by FluxBB