Back
[01:24:10] <cradek> that separate firmware package sounds nice.
[01:29:05] <cradek> jmkasunich: is your computer finally working?
[01:29:12] <jmkasunich> no
[01:29:17] <jmkasunich> it's getting worse my the minute
[01:29:18] <cradek> heck
[01:29:23] <jmkasunich> xorg
[01:29:40] <jmkasunich> remember at the workshop when my mouse was flakey and I got a new one
[01:30:03] <cradek> yes
[01:30:05] <jmkasunich> the new one is showing the same symptoms, which is too weird to be a coincidence
[01:30:20] <jmkasunich> the scroll wheel seems to be issuing the wrong events
[01:30:39] <cradek> bizarre
[01:30:47] <cradek> but it worked all this time?
[01:30:47] <jmkasunich> I'm looking at events with xev, and also catting /dev/input/mouse0 thru hd
[01:31:03] <jmkasunich> it worked until I rebooted
[01:31:13] <cradek> huh
[01:32:26] <jmkasunich> when I scroll down, apps seem to behave more-or-less normally
[01:32:43] <jmkasunich> and xev says I'm getting button 5 press and release events (which seems weird, but who knows)
[01:32:53] <cradek> that's correct
[01:33:03] <jmkasunich> when I scroll up, the cursor jumps to the right about 10-20 pixels at a time
[01:33:07] <cradek> that's not
[01:33:25] <cradek> call me crazy, but I'd just try another mouse
[01:33:41] <jmkasunich> and I get button2 events
[01:33:48] <jmkasunich> I've been considering that
[01:33:58] <jmkasunich> but the only other mice I have are ancient
[01:34:09] <jmkasunich> no scroll wheels at all - so not a suitable test really
[01:34:40] <jmkasunich> oh, I have a wireless USB mouse for the laptop
[01:36:50] <jmkasunich> can two mice co-exist, or should I unplug the PS2 mouse?
[01:37:36] <jmkasunich> apparently they can
[01:37:54] <jmkasunich> and the USB one scrolls just fine
[01:38:59] <jmkasunich> I find it extremely astonishing that two mice would have such similar failures
[01:39:16] <jmkasunich> this one isn't some $3.95 cheapo - it is a logitech
[01:41:02] <jmkasunich> I wonder if mice suffer from memory leaks like windows does, and need to be rebooted every so often
[01:41:33] <jmkasunich> the mouse is plugged into the KVM, which is UPS powered - so the mouse has been up for at least 132 days
[01:41:48] <jmkasunich> I unplugged it from the kvm, plugged it into the PC, worked
[01:41:54] <jmkasunich> back into the kvm, still worked
[01:42:10] <jmkasunich> moral of the story, reboot your mouse once in a while
[01:42:15] <cradek> haha
[01:42:25] <cradek> I have to reboot my toaster sometimes
[01:42:34] <jmkasunich> thats sad
[01:42:38] <cradek> it won't let go of the toast, it locks up and keeps toasting forever
[01:42:55] <jmkasunich> it's electronic?
[01:43:00] <cradek> I put a "Designed for Windows 2000" sticker on it (pried off my laptop)
[01:43:06] <jmkasunich> lol
[01:43:07] <cradek> yes apparently
[01:43:28] <jmkasunich> well, now I can pop one issue off my stack
[01:43:32] <jmkasunich> only about 998 left
[01:43:46] <cradek> got my compressor wired to power!
[01:43:52] <jmkasunich> yay
[01:44:06] <cradek> looks like the barn will be done tomorrow!
[01:44:22] <jmkasunich> what are you doing to/with/in the barn?
[01:44:23] <cradek> seems like we're always racing the cold weather this time of year
[01:44:44] <cradek> it's for the critters - they didn't have much shelter for winter.
[01:44:55] <jmkasunich> oh, you're building another barn?
[01:44:59] <cradek> yeah
[01:45:04] <cradek> almost done
[01:45:14] <jmkasunich> you had one, but it is all full of crap, right?
[01:45:24] <cradek> oh we still have it :-)
[01:45:35] <cradek> it's fully enclosed - we've never had animals in it
[01:45:38] <jmkasunich> you have two now, you had one before
[01:45:42] <cradek> yes
[01:46:30] <jmkasunich> is studying Xorg.log the only way to figure out what is actually going on driver-wise?
[01:46:45] <jmkasunich> I think I'm using nv
[01:46:53] <cradek> depends. if you're concerned about GL stuff, check the output of glxinfo
[01:47:15] <cradek> OpenGL vendor string: Tungsten Graphics, Inc.
[01:47:15] <cradek> OpenGL renderer string: Mesa DRI Radeon 20050528 AGP 1x TCL
[01:47:20] <jmkasunich> right now I don't have any GL
[01:47:29] <jmkasunich> jmkasunich@mahan:~$ glxinfo
[01:47:29] <jmkasunich> name of display: :0.0
[01:47:29] <jmkasunich> Xlib: extension "GLX" missing on display ":0.0".
[01:47:29] <jmkasunich> Xlib: extension "GLX" missing on display ":0.0".
[01:47:29] <jmkasunich> Xlib: extension "GLX" missing on display ":0.0".
[01:47:30] <jmkasunich> Error: couldn't find RGB GLX visual
[01:47:31] <cradek> oh
[01:47:34] <jmkasunich> but that is a few levels up the stack
[01:47:45] <jmkasunich> I have weirdness in plain old X
[01:48:01] <cradek> how did you break it so badly just adding ram?
[01:48:10] <jmkasunich> I rebooted
[01:48:10] <cradek> oh, new kernel
[01:48:21] <cradek> no new kernel?
[01:48:40] <jmkasunich> I was running -51 desktop, an update to -52 desktop was pending (had been installed but not rebooted)
[01:48:56] <jmkasunich> I've also installed -52 server, trying to access all 4g
[01:49:03] <jmkasunich> all three kernels have X issues tho
[01:50:07] <cradek> do you have linux-restricted-modules-`uname -r` installed?
[01:50:14] <jmkasunich> the issues are hard to explain, and not terribly consistent
[01:50:47] <jmkasunich> yes, for 51 and 52
[01:51:53] <jmkasunich> the blinking text cursor in some (but not all) text boxes/windows is deformed
[01:52:02] <cradek> huh. this stuff just always works for me now...
[01:52:05] <jmkasunich> arrow keys work strangely in some but not all text windows
[01:52:25] <jmkasunich> backspacing leaves vertical lines between chars in some windows
[01:53:07] <jmkasunich> I probably have some unholy mixture of nv and nvidia drivers running (drivers or pieces of drivers)
[01:53:14] <jmkasunich> or it is a driver version thing
[01:53:15] <cradek> yeah
[01:53:29] <cradek> nvidia libraries + non-nvidia driver
[01:53:37] <CIA-37> EMC: 03tissf 07TRUNK * 10emc2/src/po/fr_rs274_err.po: *** empty log message ***
[01:53:40] <jmkasunich> hence my question about how to identify what is going on
[01:53:44] <CIA-37> EMC: 03tissf 07TRUNK * 10emc2/docs/src/motion/pid_theory_fr.lyx: *** empty log message ***
[01:53:49] <jmkasunich> or, how to get a clean slate
[01:54:28] <cradek> Section "Device"
[01:54:29] <cradek> ...
[01:54:32] <cradek> Driver "nvidia"
[01:54:36] <cradek> EndSection
[01:54:50] <cradek> if you don't have this, try adding it
[01:55:26] <jmkasunich> Section "Device"
[01:55:26] <jmkasunich> Identifier"NVIDIA Corporation NVIDIA Default Card"
[01:55:26] <jmkasunich> #Driver"nvidia"
[01:55:26] <jmkasunich> Driver"nv"
[01:55:26] <jmkasunich> BusID"PCI:1:0:0"
[01:55:27] <jmkasunich> EndSection
[01:55:37] <cradek> aha
[01:55:41] <jmkasunich> that is what I've had since the update
[01:55:51] <jmkasunich> I _want_ to be running nv, at least for now
[01:55:52] <cradek> what happens when you put it back?
[01:55:54] <cradek> oh
[01:56:07] <cradek> uh what is your goal again?
[01:56:15] <jmkasunich> I changed from nvidia to nv when X refused to start after the reboot
[01:56:27] <jmkasunich> probably because the binary nvidia doesn't match the new kernel
[01:56:31] <cradek> oh so nvidia won't load
[01:56:45] <cradek> you should have the matching one if you have the matching linux-restricted-modules
[01:56:53] <jmkasunich> you'd think
[01:57:10] <cradek> did you do some terrible thing like run the crappy nvidia installer sometime in the past?
[01:57:27] <jmkasunich> I dunno, that was in the past
[01:57:41] <jmkasunich> last time I did anything with X on here was probably two years ago
[01:57:49] <jmkasunich> I _did_ have nvidia working
[01:58:05] <jmkasunich> jmkasunich@mahan:~$ dpkg -l | grep restricted
[01:58:05] <jmkasunich> rc linux-restricted-modules-2.6.15-26-386 2.6.15.11-4 Non-free Linux 2.6.15 modules on 386
[01:58:05] <jmkasunich> rc linux-restricted-modules-2.6.15-28-386 2.6.15.12-28.1 Non-free Linux 2.6.15 modules on 386
[01:58:05] <jmkasunich> rc linux-restricted-modules-2.6.15-28-686 2.6.15.12-28.2 Non-free Linux 2.6.15 modules on PPro/Celero
[01:58:07] <jmkasunich> rc linux-restricted-modules-2.6.15-29-686 2.6.15.12-29.1 Non-free Linux 2.6.15 modules on PPro/Celero
[01:58:12] <jmkasunich> ii linux-restricted-modules-2.6.15-51-686 2.6.15.12-51.2 Non-free Linux 2.6.15 modules on PPro/Celero
[01:58:15] <jmkasunich> ii linux-restricted-modules-2.6.15-52-686 2.6.15.12-52.3 Non-free Linux 2.6.15 modules on PPro/Celero
[01:58:18] <jmkasunich> ii linux-restricted-modules-686 2.6.15.53 Restricted Linux modules on PPro/Celeron/PII
[01:58:21] <jmkasunich> ii linux-restricted-modules-common aj1 Non-free Linux 2.6.15 modules helper script
[01:58:28] <jmkasunich> lots-o-versions
[01:58:32] <cradek> what's uname -r say?
[01:58:42] <jmkasunich> 2.6.15-52-686
[01:58:58] <cradek> so you do have the matching one
[01:59:02] <jmkasunich> yes
[01:59:45] <jmkasunich> getting nvidia working is step 2 I think - shouldn't it be easier to get nv working?
[02:00:20] <jmkasunich> btw, it _is_ distinctly possible that I ran some nvidia installer, I just don't remember
[02:00:33] <cradek> sounds like nv just has crap support for your particular card and it gives bogus little display problems
[02:00:40] <cradek> I'd say don't waste time on that
[02:01:02] <jmkasunich> hmm
[02:01:25] <cradek> $ cat /etc/default/linux-restricted-modules-common
[02:01:32] <jmkasunich> I guess I was thinking of nv as "slow, but solid" and nvidia as "hw acceleration, but binary and hoops to jump thru"
[02:01:37] <cradek> does it have DISABLED_MODULES including nv?
[02:02:33] <jmkasunich> # DISABLED_MODULES="ath_hal fc fglrx ltm nv"
[02:02:33] <jmkasunich> DISABLED_MODULES="fglrx"
[02:02:46] <cradek> ok, that's not it
[02:03:55] <jmkasunich> * jmkasunich digs thru old boxes to find out what graphics card I have
[02:04:33] <jmkasunich> hmm
[02:04:49] <jmkasunich> seems I have a GeForce 7100S
[02:05:18] <cradek> $ cd /lib/modules/`uname -r`/volatile; ls -l nv*
[02:05:23] <jmkasunich> synaptic says re: nvidia-glx "If you have a TNT, TNT2, or older GeForce, you may need the nvidia-glx-legacy
[02:05:23] <jmkasunich> package instead of this one."
[02:05:57] <jmkasunich> jmkasunich@mahan:~$ cd /lib/modules/`uname -r`/volatile; ls -l nv*
[02:05:57] <jmkasunich> -rw-r--r-- 1 root root 5176514 2008-11-01 21:15 nvidia.ko
[02:05:57] <jmkasunich> -rw-r--r-- 1 root root 4410619 2008-11-01 21:15 nvidia_legacy.ko
[02:06:23] <jmkasunich> the nvidia-glx-legacy package is NOT installed
[02:07:18] <jmkasunich> jmkasunich@mahan:/lib/modules/2.6.15-52-686/volatile$ dpkg -l | grep " nv"
[02:07:18] <jmkasunich> ii nvidia-glx 1.0.8776+2.6.15.12-52.3 NVIDIA binary XFree86 4.x/X.Org driver
[02:07:18] <jmkasunich> rc nvidia-glx-dev 1.0.8776+2.6.15.12-52.3 NVIDIA binary XFree86 4.x/X.Org driver devel
[02:07:18] <jmkasunich> ii nvidia-kernel-common 20051028+1 NVIDIA binary kernel module common files
[02:07:23] <cradek> modinfo /lib/modules/`uname -r`/volatile/nvidia.ko|grep vermagic
[02:07:38] <cradek> if you didn't need -legacy before a minor update, I doubt you need it now
[02:07:55] <jmkasunich> vermagic: 2.6.15-52-686 SMP preempt 686 gcc-4.0
[02:08:08] <jmkasunich> it might have been installed earlier
[02:08:16] <cradek> does that vermagic match uname -a?
[02:08:22] <jmkasunich> I think both were, and I uninstalled them while trying to get back to just the nv driver
[02:08:35] <jmkasunich> Linux mahan 2.6.15-52-686 #1 SMP PREEMPT Wed Oct 22 19:11:33 UTC 2008 i686 GNU/Linux
[02:08:37] <cradek> oh, hmmmmm
[02:08:51] <cradek> maybe you are right then.
[02:09:05] <jmkasunich> no mention of gcc version in uname -a, and the case of PREEMPT doesn't match
[02:09:16] <cradek> so the modules are getting built and they match
[02:09:23] <cradek> I think that's normal
[02:10:00] <jmkasunich> lemme comment out nv and uncommend nvidia in xorg.conf, install the legacy package, and restart x
[02:10:08] <cradek> change your Driver back to "nvidia", and try to run X, and save the log
[02:11:03] <jmkasunich> driver changed, I'll try it first without installing -legacy
[02:11:10] <jmkasunich> ctrl-alt-bksp, right?
[02:11:16] <cradek> yes
[02:11:19] <jmkasunich> here goes
[02:12:13] <jmkasunich> woot, it works
[02:12:23] <jmkasunich> I have glx too
[02:12:26] <jmkasunich> * jmkasunich is sad
[02:12:36] <cradek> any idea what you did to fix it?
[02:12:46] <jmkasunich> used the binary driver instead of nv
[02:12:49] <jmkasunich> thats why I'm sad
[02:13:40] <jmkasunich> so, a couple more things popped off the stack
[02:14:01] <jmkasunich> at the moment I'm running ubuntu's latest desktop kernel and the nvidia binary driver, everything seems to work
[02:14:12] <jmkasunich> however, I only have 3.1G of RAM
[02:14:29] <jmkasunich> I know (tried it) that the -server kernel will recognize and use all the ram
[02:14:40] <jmkasunich> but I don't think there is a restricted-modules package for it
[02:14:50] <cradek> surely there is
[02:15:15] <cradek> ... or not
[02:15:17] <cradek> huh
[02:15:40] <jmkasunich> they probaby figure servers don't need accelerated graphics and the other stuff that restricted gives you
[02:16:25] <jmkasunich> one solution would be to compile my own kernel using the settings from -52-desktop, but change only the -PAE and -64G settings
[02:16:48] <jmkasunich> but I guess that still means I don't have a nvidia driver
[02:17:02] <jmkasunich> unless the binary by some miracle would work with the kernel I make
[02:20:21] <cradek> have you tried leaving these l-r-m and booting -server?
[02:20:50] <cradek> I can't divine from the dependencies whether that's supposed to work
[02:21:10] <jmkasunich> what do you mean by "leaving"?
[02:21:30] <cradek> don't worry about l-r-m, just install and boot -server and see what happens
[02:21:36] <jmkasunich> I can try
[02:21:56] <jmkasunich> I never did worry about l-r-m, there are a bunch installed and it apparently can figure out which to use
[02:22:07] <jmkasunich> probably won't find the one it wants, but I'll try
[02:22:08] <cradek> yeah it does magic at boot time
[02:23:26] <jmkasunich> http://ubuntuforums.org/showpost.php?p=4296321&postcount=6
[02:23:37] <jmkasunich> this guy is trying to do the same thing
[02:24:13] <jmkasunich> rebooting to server kernel
[02:24:17] <jmkasunich> * jmkasunich crosses fingers
[02:30:00] <jmkasunich> no joy
[02:30:20] <jmkasunich> I saved the dmesg and xorg logs, booted back into the desktop kernel
[02:30:36] <cradek> I wish I had a clue how to build l-r-m-...-server but I don't
[02:30:44] <jmkasunich> (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
[02:30:44] <jmkasunich> (
[02:31:25] <jmkasunich> I wish there was a free (even if a bit slow) driver for my card
[02:31:37] <jmkasunich> * jmkasunich makes a note - never buy nvidia again
[02:31:43] <cradek> vesa...
[02:31:57] <jmkasunich> does that have any support (even SW) for glx?
[02:32:03] <cradek> sure
[02:32:09] <cradek> a billion emc users can't be wrong
[02:32:31] <jmkasunich> so what is the downside of using vesa instead of nv?
[02:32:39] <cradek> it's slow
[02:32:51] <cradek> oh, nv? I thought nv had rendering artifacts
[02:32:59] <jmkasunich> nv has artifacts
[02:33:01] <cradek> (nv should have glx too unless someting is screwy)
[02:33:17] <jmkasunich> it doesn't
[02:33:27] <cradek> then something is screwy
[02:33:28] <jmkasunich> dunno if the artifacts and the lack of glx are related or not
[02:33:36] <jmkasunich> we decided not to mess with nv, remember?
[02:33:37] <cradek> try uninstlaling nvidia-glx
[02:33:38] <jmkasunich> ;-)
[02:33:43] <cradek> then run vesa
[02:34:03] <cradek> in your place I'd get on ebay and order a video card, and use 3.1G until it shows up
[02:34:16] <jmkasunich> try uninstalling nvidia-glx, then run vesa? or were those two different thoughts
[02:34:25] <cradek> those are the same thought
[02:34:34] <cradek> without nvidia-glx, vesa/nv will give you software gl
[02:34:38] <cradek> I think
[02:34:46] <jmkasunich> vesa _and_ nv?
[02:34:50] <jmkasunich> now I'm lost
[02:35:11] <jmkasunich> I thought my three driver choices were nvidia, nv, or vesa
[02:35:12] <cradek> yes either one should do software gl, if you remove the nvidia libraries
[02:35:17] <jmkasunich> not "nv _and_ vesa"
[02:35:23] <cradek> right
[02:35:34] <jmkasunich> oh, ok
[02:35:45] <cradek> both nv and vesa, of which you only use one or the other, will do software gl
[02:35:45] <jmkasunich> I misread "vesa/nv will give you software gl"
[02:36:16] <jmkasunich> "but only if the binary nvidia-glx is removed to it doesn't interfere"
[02:36:23] <jmkasunich> that is probably the issue I've been having all along
[02:36:31] <cradek> http://shop.ebay.com/items/_W0QQ_nkwZmatroxQ20g450QQ_armrsZ1QQ_fromZR40QQ_mdoZ
[02:37:20] <cradek> I have these on everything - they work great even with relatime
[02:37:23] <jmkasunich> I need pci-express, are all 450's AGP?
[02:37:28] <cradek> oh, crap
[02:37:52] <cradek> I don't know anything about PCIe, I've never had one
[02:38:12] <jmkasunich> lemme check mobo manual, I'm pretty sure it has only pci-E and pci
[02:38:56] <cradek> there are some pci ones for $20...
[02:39:00] <jmkasunich> yep, two PCI, one PCI-E x16, one x8, one x4
[02:39:08] <jmkasunich> plain PCI?
[02:39:11] <cradek> I have regular pci in some of my machines
[02:39:16] <cradek> yeah but you probably don't want that.
[02:39:20] <jmkasunich> right
[02:39:29] <jmkasunich> for a machine controller, sure
[02:39:36] <jmkasunich> but not for my primary desktop system
[02:40:15] <cradek> http://cgi.ebay.com/Matrox-Millennium-G550-PCIe-32Mb-Dual-Head-G55-MDDE32_W0QQitemZ120315419879QQcmdZViewItem?_trksid=p3286.m20.l1116
[02:40:24] <cradek> no idea if this would work as well
[02:40:34] <cradek> (what a funky slot)
[02:40:42] <cradek> I thought PCIe was a normal looking slot
[02:40:57] <jmkasunich> that is an x1 PCIe
[02:41:19] <cradek> the rest of these are $x00.00
[02:41:20] <jmkasunich> PCI express is a serial bus, and they run varying numbers of channels depending on the bandwidth needed
[02:41:43] <jmkasunich> "normal" video cards are one of the highest bandwidth things in the computer and go in x16 slots
[02:42:14] <cradek> I have no more advice for you, you might be relieved to hear
[02:42:20] <jmkasunich> well
[02:42:36] <jmkasunich> I still have a couple things to try
[02:42:58] <cradek> it must be possible for you to build lrm-...-server somehow
[02:43:01] <jmkasunich> one really, nv is out, the artifacts suck
[02:43:39] <jmkasunich> I thought the whole point of lrm is that they are binaries - how can I build them?
[02:43:57] <cradek> umm
[02:44:03] <jmkasunich> I'm gonna try uninstalling nvidia-glx, and setting xorg.conf to vesa
[02:44:08] <cradek> ok
[02:44:10] <jmkasunich> then see how slow glxgears is
[02:44:18] <jmkasunich> that doesn't require a reboot, right? just an x restart?
[02:44:59] <cradek> not sure
[02:45:09] <jmkasunich> oh, non-reboot would give me desktop kernel, vesa, software glx
[02:45:17] <jmkasunich> good enough to test speed
[02:45:27] <jmkasunich> then reboot to get server kernel, vesa, adn software glx
[02:46:47] <jmkasunich> I think it might be a good idea to shut down X, then remove nvidia-glx
[02:47:04] <jmkasunich> I can do alt-F1 to get a text terminal, how to I stop X?
[02:47:26] <jmkasunich> gdm-stop I think
[02:47:51] <cradek> /etc/init.d/gdm stop
[02:48:46] <cradek> Package: linux-restricted-modules-2.6.24-21-server
[02:48:52] <cradek> Provides: nvidia-kernel-169.12, nvidia-kernel-71.86.04, nvidia-kernel-96.43.05
[02:49:01] <cradek> I notice hardy has what you want
[02:49:27] <jmkasunich> I was thinking about biting that bullet
[02:49:42] <jmkasunich> I'm sure hardy has a lot of other things I want too
[02:49:58] <cradek> I don't really notice any difference day-to-day
[02:50:03] <jmkasunich> better support for my mobo's sensors, maybe a newer gimp that can handle my camera's raw files, etc
[02:50:16] <cradek> I hear ff3 is nice
[02:50:51] <jmkasunich> are you running hardy?
[02:50:56] <cradek> only on the lathe
[02:51:09] <jmkasunich> can you do that grep for the MEM*G config flags?
[02:51:21] <jmkasunich> I wonder if they are setting the 64G flag in the newer kernels?
[02:51:40] <jmkasunich> or isn't the lathe powered right now?
[02:51:46] <cradek> all I have installed is -rtai
[02:51:51] <jmkasunich> oh, ok
[02:52:09] <cradek> oh wait I can get to another hardy
[02:52:24] <jmkasunich> I did a man gdm, and it says there should be something called "gdm-stop"
[02:52:30] <jmkasunich> but that doesn't seem to exist
[02:52:54] <jmkasunich> I'll use the init.d method, but I wonder why the other is missing
[02:53:18] <jmkasunich> oh well, here goes
[02:54:24] <jmkasunich> that didn't work
[02:54:49] <jmkasunich> "GDM already running. Aborting!"
[03:00:34] <jmkasunich> vesa gave me 1024x768 instead of 1600x1200, I assume that can be fixed
[03:00:54] <jmkasunich> glxgears works, at a few frames per second
[03:02:17] <jmkasunich> lol:
http://www.cs278.org/blog/2007/01/14/glxgears-fps/
[03:02:55] <cradek> ha
[03:03:19] <jmkasunich> something is whacked - it is reporting over 1000 fps, but the image is clearly jerky
[03:03:27] <cradek> ignore it
[03:03:33] <cradek> real apps will probably be fine
[03:05:28] <jmkasunich> wow, you're right - the HBM vismach model (rather complex) pans, rotates and zooms with only minor jerkiness, as does the axis preview
[03:06:05] <jmkasunich> the vismach model has a bad case of the jaggies that I don't recall from before, I wonder if the HW acceleration was doing anti-aliasing
[03:06:11] <cradek> possibly
[03:06:44] <cradek> is your lcd still at a non-native resolution?
[03:06:49] <cradek> that will make everything look like hell
[03:06:57] <jmkasunich> I have the LCD configured for non-scaling
[03:07:02] <cradek> ah
[03:07:07] <jmkasunich> so I have a small image in the middle of the screen
[03:07:17] <cradek> I prefer that too
[03:07:33] <jmkasunich> vesa doesn't have the text window artifacts that nv had
[03:08:18] <jmkasunich> I wonder why I'm not getting my 1600x1200? nothing in xorg.conf changed
[03:09:02] <jmkasunich> gonna go back to nvidia for a sec, I want to check that jaggies thing
[03:19:25] <jmkasunich> vesa has 4 modes, all with 16 in the 'dp/th' field
[03:19:57] <jmkasunich> glx has about 40 modes
[03:20:03] <jmkasunich> I mean nvidia
[03:25:37] <jmkasunich> https://www.linuxquestions.org/questions/linux-hardware-18/cannot-get-nv-driver-to-work-and-the-vesa-driver-is-limited-598696/
[03:25:46] <jmkasunich> I just love helpfull replies like the one in that thread
[03:26:23] <cradek> so polite: "Thanks for responding, but apparently you didn't read any of my post."
[03:27:14] <jmkasunich> ;-)
[03:28:06] <jmkasunich> trying to figure out what incantations are needed to make vesa use 1600x1200
[03:28:34] <cradek> patebin log?
[03:28:41] <cradek> I can't type today.
[03:28:54] <jmkasunich> duh
[03:29:01] <jmkasunich> I need to restart back into vesa again
[03:31:17] <jmkasunich> http://www.pastebin.ca/1242865
[03:33:32] <jmkasunich> #
[03:33:32] <jmkasunich> (II) VESA(0): Not using mode "1600x1200" (no mode of this name)
[03:34:25] <jmkasunich> there are two "standard" vesa modes that are 1600x1200, one is 8 bits/pixel, one is 16
[03:34:40] <cradek> (II) VESA(0): VESA VBE DDC read failed
[03:34:41] <jmkasunich> I believe my xorg.conf has a default depth of 24
[03:34:56] <jmkasunich> that's where it reads the monitor specs, right?
[03:35:00] <cradek> yes
[03:35:27] <jmkasunich> it might always fail, because of my KVM switch (not sure)
[03:35:34] <cradek> oh, bet so
[03:35:37] <cradek> those always screw it up
[03:35:43] <cradek> find your monitor specs and hardcode them
[03:35:50] <cradek> (II) VESA(0): Generic Monitor: Using hsync range of 28.00-80.00 kHz
[03:35:52] <jmkasunich> I explicitly define horiz and vert freq ranges in my xorg.conf, it shouldn't need the DDC data
[03:35:56] <cradek> I think this is what's killing that mode
[03:36:02] <cradek> oh - ok
[03:36:09] <jmkasunich> lemme pastebin my xorg.conf
[03:37:17] <jmkasunich> http://www.pastebin.ca/1242872
[03:37:58] <jmkasunich> monitor info line 99
[03:38:06] <cradek> ok, you're hardcoding a modeline that gives 75kHz
[03:38:25] <cradek> I'd think there is a vesa mode that matches that, but maybe not
[03:38:48] <jmkasunich> I didn't think that modeline was 75Hz
[03:38:56] <cradek> 75kHz, 60Hz
[03:39:02] <jmkasunich> oh
[03:39:39] <jmkasunich> the xorg log has a big list of "standard vesa modes"
[03:39:40] <cradek> that is, within your specified rates
[03:39:49] <jmkasunich> only two are 1600x1200, and they don't have the right memory depth
[03:40:04] <jmkasunich> I don't think the modes care about refresh rate, just memory layout
[03:40:43] <cradek> worth a shot
[03:41:17] <jmkasunich> what is? commenting out my modeline?
[03:41:30] <cradek> and changing the depth to 16
[03:41:46] <jmkasunich> I'll change one thing at a time ;-)
[03:44:35] <Jymmmm> DCC has a tendancy to screw up more than it does good usually.
[03:44:54] <jmkasunich> commenting the modeline didn't help
[03:44:59] <jmkasunich> changing depth to 16 did
[03:45:08] <jmkasunich> restoring the modeline it still works
[03:45:54] <jmkasunich> so, I'm running a 3.8megabyte mode on my 128 megabyte video card
[03:45:58] <jmkasunich> that sucks
[03:46:14] <Jymmmm> which vga mode are you using?
[03:46:48] <jmkasunich> I think 146
[03:47:56] <jmkasunich> the vesa driver only supports pre-defined vesa modes, and there simply aren't any large deep ones
[03:49:19] <Jymmmm> 1600x1200x24 = 799
[03:49:32] <jmkasunich> eww - icky moire (sp?) patterns on the ways of the HBM vismach model, it must be trying to dither to make up for the lack of color depth
[03:49:43] <Jymmmm> http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
[03:50:19] <jmkasunich> Jymmmm: your math is funky
[03:50:27] <Jymmmm> lol
[03:51:30] <jmkasunich> oh, I see, that is a mode number
[03:53:19] <jmkasunich> interesting that my mode 146 doesn't appear in any of those tables
[03:55:10] <jmkasunich> so it looks like my choices for now are:
[03:55:13] <jmkasunich> 1) use the generic kernel, get 3.2G of my 4G total ram, use the nvidia driver and have fast high-quality graphics
[03:55:34] <jmkasunich> 2) use the server kernel, get all 4G of ram, use the vesa driver, and have slower low-quality graphics
[03:56:07] <jmkasunich> other options that may or may not work include:
[03:56:33] <jmkasunich> 3) somehow come up with a binary nvidia driver that plays nice with the server kernel
[03:57:07] <jmkasunich> 4) build a kernel that is like the generic one, but has the 64G and PAE config switches set, and plays nice with the existing nvidia binary driver
[04:00:26] <jmkasunich> oh, forgot 5) update to 8.04, which has a restricted-modules package that goes with the server kernel
[04:01:01] <jmkasunich> that will be rather painfull but is probably the best long term solution - dapper is getting a bit crusty around the edges
[04:02:48] <jmkasunich> logger_dev: bookmark
[04:02:48] <jmkasunich> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-11-02.txt
[04:19:30] <jmkasunich> goodnight
[04:40:15] <Jymmmm> jmkasunich: I typically use vga=791 (or 794) during startup of Ubuntu in grub, then just add to the bootloader line: nosplash verbose vga=791
[04:40:49] <Jymmmm> jmkasunich: You cna do this temporarily at bootup I think by hitting F6
[04:41:39] <Jymmmm> jmkasunich: as far as mode 146 goes, I've never heard of it, might be an nvidia specific thing, but I wasn't really paying attention to the whole conversation either.
[04:44:59] <jepler_> huh, that's interesting -- my program shows in top as a zombie, but it's still consuming about 200% CPU
[04:45:14] <jepler_> (it's a pthread program in which the original thread has called pthread_exit, but there are still two threads working)
[05:16:42] <Jymmmm> jepler_: Wouldn't that sorta-kinda be a zombie?
[05:16:53] <Jymmmm> kinda alive, but kinda not
[05:19:23] <jepler_> Jymmmm: there's a specific definition of a "zombie process" (one that has exited, but its exit value hasn't been read by the parent process through wait() or waitpid()) and I think this doesn't quite qualify (since only one thread has exited, not the whole process)
[05:19:41] <Jymmmm> ah, ok.