Click to See Complete Forum and Search --> : fluxbox startup script


nolimit974
05-26-2008, 07:38 PM
I have been trying to start an aterm when fluxbox startsup but when i add the line to the script and restart fluxbox it doesn't start the aterm the line i am adding is
aterm -tr -trsb -sh 80 -sb -bl
but like i said that never works here is my complete start up script

# fluxbox startup-script:
#
# Lines starting with a '#' are ignored.

# You can set your favourite wallpaper here if you don't want
# to do it from your style.
#
wallsetter=feh fbsetbg /home/nolimit974/.fluxbox/backgrounds/darklight.jpg
#
# This sets a black background

# /usr/bin/fbsetroot -solid black

# This shows the fluxbox-splash-screen
# fbsetbg -C /usr/share/fluxbox/splash.jpg

# Other examples. Check man xset for details.
#
# Turn off beeps:
# xset -b
#
# Increase the keyboard repeat-rate:
# xset r rate 195 35
#
# Your own fonts-dir:
# xset +fp "/home/nolimit974/.fonts"
#
# Your favourite mouse cursor:
# xsetroot -cursor_name right_ptr
#
# Change your keymap:
# xmodmap "/home/nolimit974/.Xmodmap"



# Applications you want to run with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
#
# unclutter -idle 2 &
# wmnd &
# wmsmixer -w &
# idesk &
conky &
aterm -tr -trsb -sh -80 -sb -bl &

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.

exec /usr/bin/fluxbox
# or if you want to keep a log:
# exec /usr/bin/fluxbox -log "/home/nolimit974/.fluxbox/log"
i know if you are around blackbelt_jones you can help me with this.

bwkaz
05-27-2008, 09:29 PM
If you fire up an xterm (or any other terminal program), can you run this aterm command manually? I.e., just copy:

aterm -tr -trsb -sh -80 -sb -bl &

into another terminal and see if you get any errors. :)

nolimit974
05-28-2008, 08:12 PM
yes i get an error

Failed to initialize TTM buffer manager. Falling back to classic.

bwkaz
05-28-2008, 09:18 PM
Googling around for that error (and related stuff: "TTM" in particular) shows that it seems to be related to Intel graphics cards or something? It looks like it's some kind of memory manager for video memory? Lots of people are getting errors similar to that when they try to start OpenGL-using programs (e.g. glxinfo, etc.). I don't think aterm uses OpenGL, but it might be worth checking to see if your glxinfo prints the same error.

But as for fixing the actual error; hmm. Does it help if you turn off the transparency temporarily? What about the "borderless" option? Since you're turning off the scrollbar entirely, does it make any difference to remove the scrollbar-transparency option?

nolimit974
05-29-2008, 07:04 PM
I just upgraded to FC9 which doesn't have any support for nvidia drivers at the moment so i can't use my nvidia card.

I did glxinfo and no errors were printed but nvidia drivers should be coming out soon for fc9 so for now i want even worry about a transparent terminal till then.

and yes i am using intel graphics so i suppose that is the problem.

bwkaz
05-31-2008, 09:31 AM
Any particular reason not to use the nvidia drivers from:

http://www.nvidia.com/Download/Find.aspx?lang=en-us

instead? ;) You might need your kernel sources, though.

(I'm not sure that the Intel graphics is the problem, specifically. I think this TTM thing just needs to be worked on some more; I think something like it will definitely be needed eventually. It'd be nice if you could just disable TTM, but I don't see any way to do that. :()

nolimit974
05-31-2008, 09:43 PM
I guess i could try the nvidia graphics drivers. I tried the kmod-nvidia drivers from livna but they don't work.

nolimit974
06-07-2008, 12:57 AM
Well i have tried to install the nvidia drivers. When in hit CTRl+Alt+F1 and try to do the init 3 command hit stops after starting anacron and just sits there.

When i tried using the kmod-nvidia it would install but when I rebooted it would come up with an error. It says that it has found 2 possible primarry display devices (my onboard intel and my nvidia graphics card). Then it tries to initialize the primary display device and it the says ERROR no devices found. Anyone care to point me in the right direction?

happybunny
06-07-2008, 01:54 AM
reboot....at grub menu, hit e to edit, then put an "s" at the end of the kernel line to boot into single user mode.

Once there, /path/to/NVIDIA.xxxx and let it do it's thing.

Like someone said though, you might need kernel-headers to compile so start networking (/etc/init.d/network start) or get it before hand.

nolimit974
06-07-2008, 11:48 AM
well i tried again. I says that i have now pre compiled kernel so i let it compile one. Like i said before when I rebooted it would come up with an error. It says that it has found 2 possible primary display devices (my onboard intel and my nvidia graphics card). Then it tries to initialize the primary display device and it the says ERROR no devices found. That is the error that i keeping things for going smoothly. I have searched the internet and found nothing.

happybunny
06-07-2008, 05:33 PM
dpkg-reconfigure x-server-xorg? i think?
or
X --configure?

bwkaz
06-08-2008, 09:08 PM
It says that it has found 2 possible primarry display devices (my onboard intel and my nvidia graphics card). Is there any chance you can disable the onboard Intel video device without causing other problems? (Look around in your BIOS setup.) If so, that may be worth a try. Of course, it'll be a pain to have to keep enabling and disabling it if you need to switch back and forth, so maybe it's not a great idea, but it might work.

Alternately, this isn't a great fix if you can get anything else to work, so ... hey, whatever. :)

nolimit974
06-09-2008, 08:47 PM
Well from what i have noticed in the bios after i insert my card is that the onboard video is automaticly disabled.

bwkaz
06-09-2008, 09:27 PM
Well from what i have noticed in the bios after i insert my card is that the onboard video is automaticly disabled. Not according to whatever tool was telling you that "it found 2 possible primarry display devices". ;)

Maybe it's disabled according to the BIOS, but it's still showing up on the PCI/AGP/PCIe bus, and since Linux doesn't use the BIOS, it's still showing up to the kernel? Not sure. If you can disable it completely, some other way than just plugging in the nvidia card, it might be worth trying. :)

nolimit974
06-10-2008, 08:24 PM
i could probably disable intel graphics support in the kernel couldn't i?

bwkaz
06-11-2008, 07:30 PM
Probably, yeah. I've never set up an Intel GPU, though, so I don't know what all is involved. You can probably turn off DRI entirely if you think you can get away with it. Otherwise maybe just the Intel DRI driver. :)

(Of course, then you'll end up with failed udev events, when it tries to load a driver for the Intel GPU but the module doesn't exist. That's probably not a huge deal though; they're easy enough to ignore. You don't normally even see them, unless you go looking in your /dev/.udev/failed/ directory. :))