Cannot get the script to run:
:: Code :: cd /usr/local/bin && wget -Nc smxi.org/smxi.zip && unzip smxi.zip && smxiRuns OK, asks to kill X (option 1) I log onto ctrl+alt+f1, change to root: :: Code :: n5010 bin # ./sgfxi -! 32
ERROR: (250) You must be out of X/Desktop (like KDE, Gnome, Flux, LXDE etc) to run this feature. Exiting script now. Completely stuck! Back to top |
One thing, resist the urge to use the ./sgfxi start when sgfxi is in /usr/local/bin
/usr/local/bin should be in your PATH, if it is not, expect sgfxi/smxi to fail in strange ways. So it should start with: sgfxi -! 32 Next: the 250 error is caused by $DISPLAY variable being non null, ie, a value exists for it in your current console session. Use: :: Code :: echo $DISPLAYin console to see this. In X it will show something like: :: Code :: echo $DISPLAY
:0 In a standard terminal, ie: ctrl alt F1 it should so this: :: Code :: echo $DISPLAY
ie, null. If you getting a non null display value in terminal, whether or not X is running, either there is something very weird or wrong with your setup, or Nouveau, if running, is showing up as a DISPLAY, which would be a horrible thing if true. I'd have to run a test box nouveau install / reboot etc to verify this myself for nouveau, since I refuse to run that garbage on any of my real systems. Back to top |
ran smxi again, echo $DESKTOP returns null, In a terminal after running startx:
:: Code :: molly@n5010~ $ echo $DESKTOP
molly@n5010~ $ Noveau??? I thought that was Nvidia? I am have an ATI card. :Edit: Rebooted, still returns null in a normal boot. Back to top |
echo $DISPLAY
is not what you typed. Sorry, I forgot, assumed nouveau, this would be radeon issue, same problem more or less though. However unrelated to typing in the wrong command. Back to top |
Sorry, long day at work, will try again:
:: Code :: molly@n5010~ $ echo $DISPLAY
:0.0 Is reported in a normal boot, back in a tick. After running smxi it returns 22:0.0 Apologies for the stupid error, been up since 5:30, starting to flag :) Back to top |
fully updated lmde 64 and ran sgfxi
installed xorg.conf pastebin.com/fgFPL3iL xorg.conf downloaded driver 260.19.36 FAILED to remove nouveau pastebin.com/kkWSer0c Xorg.0.log reboot as requested.. flashing cursor of death edited grub with 'vesa' and removed xorg.conf booted, in tty did sgfxi again pastebin.com/9Mb20vKp xorg.conf pastebin.com/eCBse9fM Xorg.0.log nearly forgot, pastebin.com/JKNZT9m2 sgfxi.log pastebin.com/5ZEy0JJd sgfxi.log.1 it did install the driver, but the fact I had to edit grub with 'vesa' in order to boot is not good... my inxi -F pastebin.com/wEiiQpr9 < Edited by gazza :: Feb 24, 11, 16:50 > Back to top |
I see now.
what's happening is that lmde used runlevel 2 as the default runlevel, which creates a bad situation where to recover you need to do some arcane debian tricks. I thought sgfxi added vesa to xorg.conf with nouveau reboot, it should, I'll have to double check that. Back to top |
excellent bug report, there was in fact a bug that prevented the vesa driver being forced in xorg.conf, that should now be fixed in sgfxi.
If all bug reports were done this well there's be very few unreported bugs, heh. Back to top |
All times are GMT - 8 Hours |