Re: [vox-tech] time jumps 8 hours
On Fri, 15 Feb 2002, eric nelson wrote: > Thanks. I did find today that there is nothing in the cron. I'll check > inetd. Do you recommend setting the bios clock to local time? I guess I > should use a high debug level of logging, so there's lots of data. What > other files besides /var/log/messages? > I'll be away from work 3 days, might get back to you if I still can't figure > it out. make files don't work too well with this situation :~( Not all jobs will always show up in cron as by root or local users. I have found /etc/cron.*/* anacrontab cron.d cron.daily cron.monthly cron.weekly crontab cvs-cron.conf See if you have these, and review them too. If after checking /var/spool/cron, /etc/cron*, /etc/at* and verifying that you have no other at/cron packages (cron, anacron, etc) installed, and no daemonized ntp clients, and reviewing log files to see when the date/time-stamps change (the change in time should tell you *when* the problem is occuring) and none of these helps you to find the offending app, perhaps it is being called into being by another system update tool.(?) This makes it more difficult. The time that the event occurs should help you to narrow the group of apps that could call it. Disable half and see if it goes away, if it does, then examine the half you disabled and re-enable half. If it comes back, then suspect the 25% you have left. Continue in this binary search and divide till you find it. Also? Maybe do a man -k date and man -k clock and man -k time looking for applications that can change the clock. Then mv these to different names (like $0.oirg) and then write a bash wrapper that records PPID and date/time into a file as well as a ps -auxw | grep $PPID to see the name of the process and dump this info into a file, and then pass on the args $@ to the real application $0.orig) This seems time consuming, but is one of the many many approaches you have available at your disaposal to solve this problem. Others here may have other alternatives. If you have found all clock/date modifying binaries on your system, and wrapped them to still find nothing, suspect multiple personality disorder or someone pulling a prank on you. (Hope my general joke is not offensive.) When you all were talking about Linux newbies: I still consider myself a *NIX newbie. ]:> Yatta! -ME -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z? --END GEEK CODE BLOCK-- decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
i have only been able to get jpilot working, but it does work very well :-) Rusty On Friday 15 February 2002 20:42, you wrote: > On Fri, 15 Feb 2002, Peter Jay Salzman wrote: > > i still can't sync the visor though. coldsync segfaulted. recompiled > > it with -g, did a backtrace, found a null pointer dereference and sent a > > bug report to the developers. > > Are you using the PalmOS sync programs? I've read they're flaky, if it > works at all, when using USB connections. Apparently you can get serial > connectors that work. > > If you get it working, let me know -- I could use syncing on my Clie :) > > > btw, i found the problem with the /proc/bus/usb entries, or lack > > thereof. i needed to set > > > > CONFIG_USB_DEVICEFS is not set > > > > and then mount the device filesystem in fstab: > > > > none /proc/bus/usb usbdevfs default0 0 > > After mounting /proc/bus/usb, what does usbview show? > > -Mark ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] time jumps 8 hours
On Thursday 14 February 2002 09:59 pm, you wrote: > On Thu, 14 Feb 2002, eric nelson wrote: > > It is supicious about the 8 hour offset. I had ntp running, but turned > > it off about a week ago when I saw this problem. I don't think there are > > any other cron jobs, but I'll check tomorrow. > > Things to check out: > > tzconfig > > exaine your log files. Most are date/time stamped. If your clock changes, > you should be able to see around the time this took place according to > the logs files. > > Log files may also let you know what application/service may have been > changing your clock. > > inspect your clock (in BIOS) to see if it is in GMT. > > See if you have somehow installed more than one ntp client (one that say > only starts up via cron job every 24 hours vs one that is > daemonized/inetd(on demand). > > -ME Thanks. I did find today that there is nothing in the cron. I'll check inetd. Do you recommend setting the bios clock to local time? I guess I should use a high debug level of logging, so there's lots of data. What other files besides /var/log/messages? I'll be away from work 3 days, might get back to you if I still can't figure it out. make files don't work too well with this situation :~( > > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
On Fri, 15 Feb 2002, Peter Jay Salzman wrote: > i still can't sync the visor though. coldsync segfaulted. recompiled > it with -g, did a backtrace, found a null pointer dereference and sent a > bug report to the developers. Are you using the PalmOS sync programs? I've read they're flaky, if it works at all, when using USB connections. Apparently you can get serial connectors that work. If you get it working, let me know -- I could use syncing on my Clie :) > btw, i found the problem with the /proc/bus/usb entries, or lack > thereof. i needed to set > > CONFIG_USB_DEVICEFS is not set > > and then mount the device filesystem in fstab: > > none /proc/bus/usb usbdevfs default0 0 After mounting /proc/bus/usb, what does usbview show? -Mark -- Mark K. Kim http://www.cbreak.org/mark/ PGP key available upon request. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] misc. XF86 4 upgrade and accel 3D issues
On Fri, Feb 15, 2002 at 09:33:32AM -0800, Peter Jay Salzman wrote: > > > Now, however, rather than complaining and aborting, running the 'tuxracer' > > executable actually kills my X server! > > definitely contact the author. Actually, I noticed that switching video modes (ie, CTRL-ALT-Num-Plus/Minus) did the same thing. I compared my XF86Config and XF86Config-4, and it looked like I gave the wrong video timings. ;) Now TuxRacer loads and the menu runs much more quickly, but polygon rendering is still slow... > satan# auto-apt search glx.h > usr/include/GL/glx.hdevel/mesag-dev But I think installing this may fix it: The following extra packages will be installed: mesag3 The following packages will be REMOVED: xlibmesa3 Off to test more! Thanks! -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
begin Jeff Newmiller <[EMAIL PROTECTED]> > On Fri, 15 Feb 2002, Peter Jay Salzman wrote: > > >of course, it's _possible_ that the cable is bad, but i seriously > >doubt it. i'm trying to set the visor up on rhonda's windows machine > >right now, but i'm nearly certain it will work. > > Note that the driver said it had detected two ports in your hub. If you > have ports in both the front and back of your computer, try using only the > front ports or only the back ports. That is, unplug all cables but the > one you are working with if possible. i *suspect* the problem may have been usb code interacting with smp code. tried it on lucifer and usb seems to be functional. wild claim and i don't have much evidence to back it up other than it "worked" on a UP machine, and i read that USB needs special attention on SMP machines. i still can't sync the visor though. coldsync segfaulted. recompiled it with -g, did a backtrace, found a null pointer dereference and sent a bug report to the developers. i need to take a break from this. i've been at it since noon. i'll try again using pilot-link and other software. but at LEAST i can now make FIRST CONTACT with the visor over usb. now all i need to do is coax the vulcans to come out of their ship. btw, i found the problem with the /proc/bus/usb entries, or lack thereof. i needed to set CONFIG_USB_DEVICEFS is not set and then mount the device filesystem in fstab: none /proc/bus/usb usbdevfs default0 0 i did all this on lucifer, my UP machine. i'll try recompiling the kernel and mounting the devfs on satan and try again to see if i get that wierd "bad cable" message. it might clear things up. btw, has anyone gotten 2.5.2, 2.5.3, 2.5.4 to compile? i'm getting really stupid compiler warnings like "int format, long int arg" that finally bomb out. kernel cousin warns that not many people have been able to compile 2.5.4, but the the previous 2 don't seem to want to compile for me either[1]. btw, the visor prism is selling for 220 at fry's. it's pretty darn awesome. i can't wait to get this thing working under linux! pete [1]: not the linking problem. i learned how to fix that. if anyone is interested, edit arch/i386/vmlinux.lds and comment out the line that says *(.text.ext) from the DISCARD section. fixed the linker error for me. -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
On Fri, 15 Feb 2002, Peter Jay Salzman wrote: > hello all, > > i have *never* played with usb at all. last night was my first attempt, > (just bought a handspring visor prism) and i'm afraid it failed. [...] > 4. here's dmsg output: > [...] >Product: USB UHCI Root Hub >SerialNumber: d000 >hub.c: USB hub found >hub.c: 2 ports detected [...] > 1. it's my understanding that there should be a file /proc/bus/usb. > this file is missing. i _thought_ it should be created upon > successful initialization of usb.c. but it's simply not there. Dunno. > 2. when I settle the visor into the cradle: > > hub.c: Cannot enable port 2 of hub 1, disabling port. > hub.c: Maybe the USB cable is bad? > >of course, it's _possible_ that the cable is bad, but i seriously >doubt it. i'm trying to set the visor up on rhonda's windows machine >right now, but i'm nearly certain it will work. Note that the driver said it had detected two ports in your hub. If you have ports in both the front and back of your computer, try using only the front ports or only the back ports. That is, unplug all cables but the one you are working with if possible. --- Jeff NewmillerThe . . Go Live... DCN:<[EMAIL PROTECTED]>Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] misc. XF86 4 upgrade and accel 3D issues
begin nbs <[EMAIL PROTECTED]> > On Fri, Feb 15, 2002 at 09:33:32AM -0800, Peter Jay Salzman wrote: > > > > too bad you didn't look in the linux gamers' howto. it would've saved > > you from head-pounding and ircing!:) > > Actually, I did hit your howto various times (both via Google... even got > the Russian version once :), and while doing a 'zgrep' in my local HOWTO > dir :) ) oops. that section got deleted. i purged the document of debian specific information, and i was too aggressive. should've left in the section on configuring video cards. bleah. thanks for mentioning this! i'll put that stuff back in for the next version. thank god for cvs! wonderful application! > > > use auto-apt. i think i posted this once before, but it's such a nice > > trick that it deserves to be posted again. > > Kewl. Thanks! this little tidbit came across debian-user. the thing about debian-user is if you read it religiously, you're bound to become a linux expert within a month. but just be prepared to lose your job and fail your classes. that list gets ALOT of traffic! :) pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] misc. XF86 4 upgrade and accel 3D issues
On Fri, Feb 15, 2002 at 09:33:32AM -0800, Peter Jay Salzman wrote: > > too bad you didn't look in the linux gamers' howto. it would've saved > you from head-pounding and ircing!:) Actually, I did hit your howto various times (both via Google... even got the Russian version once :), and while doing a 'zgrep' in my local HOWTO dir :) ) > use auto-apt. i think i posted this once before, but it's such a nice > trick that it deserves to be posted again. Kewl. Thanks! -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] Customizing Emacs
A minor little question, really. I know that with a terminal window I can set the window to "transparent" so that I can see my desktop image through the window. Is there a way to do that with Emacs as well? -- Sliante, Richard S. Crawford mailto:[EMAIL PROTECTED] http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: [EMAIL PROTECTED] "It is only with the heart that we see rightly; what is essential is invisible to the eye." --Antoine de Saint Exupery "Push the button, Max!" ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
begin Erik Mullinix <[EMAIL PROTECTED]> > > Heya. > Ive been finding that the USB sometimes comes accross as a SCSI device. > Dont know why. but it is and my dual Celeron 500 is using it. what exactly do you mean? you access usb devices using scsi device files? or your usb devices get registered by scsi drivers? can you post dmesg (or lsmod)? pete -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
Heya. Ive been finding that the USB sometimes comes accross as a SCSI device. Dont know why. but it is and my dual Celeron 500 is using it. Dont know the particulars but I hope this sends you in the right direction. > hello all, > > i have *never* played with usb at all. last night was my first attempt, > (just bought a handspring visor prism) and i'm afraid it failed. > here's what i did: > > > 1. compiled 2.5.1 with the following options: > >CONFIG_USB (Support for USB) >CONFIG_USB_DEBUG (USB verbose debug messages) >CONFIG_USB_UHCI (UHCI: Intel, PIIX4, VIA, ...) >CONFIG_USB_SERIAL_VISOR (USB Handspring Visor / Palm m50x) > >this is on an dual celeron 550, so i believe UHCI is correct. > > > 2. created the appropriate device files: > >crw-rw-rw- root root 188, 0 Feb 14 23:41 /dev/ttyUSB0 >crw-rw-rw- root root 188, 1 Feb 14 23:41 /dev/ttyUSB1 >crw-rw-rw- root root 188, 2 Feb 14 23:43 /dev/ttyUSB2 >crw-rw-rw- root root 188, 3 Feb 14 23:43 /dev/ttyUSB3 >lrwxrwxrwx root root 12 Feb 14 23:43 /dev/pilot -> /dev/ttyUSB1 >lrwxrwxrwx root root 12 Feb 14 23:52 /dev/visor -> /dev/ttyUSB1 > > > 3. after rebooting, here were the assigned IRQ's: > >CPU0 CPU1 >0: 12128 0 XT-PIC timer >1: 81 0 XT-PIC keyboard >2: 0 0 XT-PIC cascade >5: 4 0 XT-PIC soundblaster >8: 2 0 XT-PIC rtc >10: 0 0 XT-PIC usb-uhci >11: 33 0 XT-PIC eth0 >12: 10 0 XT-PIC PS/2 Mouse >14: 29553 0 XT-PIC ide0 >15: 6227 0 XT-PIC ide1 > > > 4. here's dmsg output: > >usb.c: registered new driver hub >usb-uhci.c: $Revision: 1.268 $ time 17:52:42 Feb 14 2002 >usb-uhci.c: High bandwidth mode enabled >PCI: Assigned IRQ 11 for device 00:07.2 >usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 11 >usb-uhci.c: Detected 2 ports >usb.c: new USB bus registered, assigned bus number 1 >usb.c: kmalloc IF cddbcb00, numif 1 >usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1 >usb.c: USB device number 1 default language ID 0x0 >Product: USB UHCI Root Hub >SerialNumber: d000 >hub.c: USB hub found >hub.c: 2 ports detected >hub.c: standalone hub >hub.c: ganged power switching >hub.c: global over-current protection >hub.c: Port indicators are not supported >hub.c: power on to power good time: 2ms >hub.c: hub controller current requirement: 0mA >hub.c: port removable status: RR >hub.c: local power source is good >hub.c: no over-current condition exists >hub.c: enabling power on all ports >usb.c: hub driver claimed interface cddbcb00 >usb-uhci.c: v1.268:USB Universal Host Controller Interface driver >usb.c: registered new driver serial >usbserial.c: USB Serial Driver core v1.4 >usbserial.c: USB Serial support registered for Handspring Visor/Palm 4.0 >usbserial.c: USB Serial support registered for Sony Clié 3.5 >visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.7 > > > so this all looks great, doesn't it? looks perfect. how here is where > the problems begin. > > > 1. it's my understanding that there should be a file /proc/bus/usb. > this file is missing. i _thought_ it should be created upon > successful initialization of usb.c. but it's simply not there. > > 2. when I settle the visor into the cradle: > > hub.c: Cannot enable port 2 of hub 1, disabling port. > hub.c: Maybe the USB cable is bad? > >of course, it's _possible_ that the cable is bad, but i seriously >doubt it. i'm trying to set the visor up on rhonda's windows machine >right now, but i'm nearly certain it will work. > > 3. ever since compiling usb into my kernel, the system hangs when i >reboot or halt. during the reboot/halt sequence, when "sending TERM >to all processes" the system just hangs. hitting return puts a >newline onto the console, so i assume the kernel is just fine and >dandy. it's probably waiting for something to happen. perhaps if i >waited long enough, something would time out. but i haven't waited >more than than 3 minutes (too impatient). in any event, it shouldn't >be doing this. > > 4. hotsyncing, of course, doesn't work. the visor reports that it can't >connect to the computer (with coldsync. i assume the same thing will >happen using pilot-link. these problems are kernel problems, not >application problems). at the same time, the kernel prints alot of >debugging info and finally says it's disabling the usb port. > > i'd like to concentrate on problem 1; it seems more fundamental than the > other problems, but at this point, i'm stuck other than to try this on > another system. ANY advice, thoughts
[vox-tech] usb woes
hello all, i have *never* played with usb at all. last night was my first attempt, (just bought a handspring visor prism) and i'm afraid it failed. here's what i did: 1. compiled 2.5.1 with the following options: CONFIG_USB (Support for USB) CONFIG_USB_DEBUG (USB verbose debug messages) CONFIG_USB_UHCI (UHCI: Intel, PIIX4, VIA, ...) CONFIG_USB_SERIAL_VISOR (USB Handspring Visor / Palm m50x) this is on an dual celeron 550, so i believe UHCI is correct. 2. created the appropriate device files: crw-rw-rw- root root 188, 0 Feb 14 23:41 /dev/ttyUSB0 crw-rw-rw- root root 188, 1 Feb 14 23:41 /dev/ttyUSB1 crw-rw-rw- root root 188, 2 Feb 14 23:43 /dev/ttyUSB2 crw-rw-rw- root root 188, 3 Feb 14 23:43 /dev/ttyUSB3 lrwxrwxrwx root root 12 Feb 14 23:43 /dev/pilot -> /dev/ttyUSB1 lrwxrwxrwx root root 12 Feb 14 23:52 /dev/visor -> /dev/ttyUSB1 3. after rebooting, here were the assigned IRQ's: CPU0 CPU1 0: 12128 0 XT-PIC timer 1: 81 0 XT-PIC keyboard 2: 0 0 XT-PIC cascade 5: 4 0 XT-PIC soundblaster 8: 2 0 XT-PIC rtc 10: 0 0 XT-PIC usb-uhci 11: 33 0 XT-PIC eth0 12: 10 0 XT-PIC PS/2 Mouse 14: 29553 0 XT-PIC ide0 15: 6227 0 XT-PIC ide1 4. here's dmsg output: usb.c: registered new driver hub usb-uhci.c: $Revision: 1.268 $ time 17:52:42 Feb 14 2002 usb-uhci.c: High bandwidth mode enabled PCI: Assigned IRQ 11 for device 00:07.2 usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 usb.c: kmalloc IF cddbcb00, numif 1 usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1 usb.c: USB device number 1 default language ID 0x0 Product: USB UHCI Root Hub SerialNumber: d000 hub.c: USB hub found hub.c: 2 ports detected hub.c: standalone hub hub.c: ganged power switching hub.c: global over-current protection hub.c: Port indicators are not supported hub.c: power on to power good time: 2ms hub.c: hub controller current requirement: 0mA hub.c: port removable status: RR hub.c: local power source is good hub.c: no over-current condition exists hub.c: enabling power on all ports usb.c: hub driver claimed interface cddbcb00 usb-uhci.c: v1.268:USB Universal Host Controller Interface driver usb.c: registered new driver serial usbserial.c: USB Serial Driver core v1.4 usbserial.c: USB Serial support registered for Handspring Visor/Palm 4.0 usbserial.c: USB Serial support registered for Sony Clié 3.5 visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.7 so this all looks great, doesn't it? looks perfect. how here is where the problems begin. 1. it's my understanding that there should be a file /proc/bus/usb. this file is missing. i _thought_ it should be created upon successful initialization of usb.c. but it's simply not there. 2. when I settle the visor into the cradle: hub.c: Cannot enable port 2 of hub 1, disabling port. hub.c: Maybe the USB cable is bad? of course, it's _possible_ that the cable is bad, but i seriously doubt it. i'm trying to set the visor up on rhonda's windows machine right now, but i'm nearly certain it will work. 3. ever since compiling usb into my kernel, the system hangs when i reboot or halt. during the reboot/halt sequence, when "sending TERM to all processes" the system just hangs. hitting return puts a newline onto the console, so i assume the kernel is just fine and dandy. it's probably waiting for something to happen. perhaps if i waited long enough, something would time out. but i haven't waited more than than 3 minutes (too impatient). in any event, it shouldn't be doing this. 4. hotsyncing, of course, doesn't work. the visor reports that it can't connect to the computer (with coldsync. i assume the same thing will happen using pilot-link. these problems are kernel problems, not application problems). at the same time, the kernel prints alot of debugging info and finally says it's disabling the usb port. i'd like to concentrate on problem 1; it seems more fundamental than the other problems, but at this point, i'm stuck other than to try this on another system. ANY advice, thoughts or streams of consciousness would be appreciated. thanks, pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] misc. XF86 4 upgrade and accel 3D issues
begin nbs <[EMAIL PROTECTED]> > So today I decided it was about time I got 3D working on my box again > (I have a Voodoo 3 2000, and am running Debian testing). > > I started with the innocent looking: > > apt-get install xserver-xfree86 > > > That bumped me up to XFree86 Version 4.1.0.1. Yay! > However, accelerated 3D still didn't work. A bit of head-pounding and IRCing > later, I finally found the answer on Google Groups: > > apt-get install xlibmesa3 too bad you didn't look in the linux gamers' howto. it would've saved you from head-pounding and ircing!:) > Now, however, rather than complaining and aborting, running the 'tuxracer' > executable actually kills my X server! definitely contact the author. > Also, now, my virtual consoles (the text consoles accessible via Ctrl-Alt-F1 > thru Ctrl-Alt-F6) can't be seen. (Instead, I just see a frozen 640x480 > zoom-in of the upper righthand corner of what was on the X screen (C-A-F7) > when I switched. I can still log in and so forth, but I'm blind. I may as > well have the monitor turned off :^( -- Note... once upon a time, under > Red Hat, I had the same issue.) you're probably using a frame buffer. recompile the kernel without it. i would think this problem would be "searchable". > Finally... and this is a dumb question (but I was having a hell of a time > finding anything using dselect), when I try to compile one of my OWN 3D > games from source, I get complaints about glx.h, gl.h, glu.h, and glut.h > missing. What do I need to apt-get to get those fellows on my box? use auto-apt. i think i posted this once before, but it's such a nice trick that it deserves to be posted again. satan# auto-apt search glx.h usr/include/GL/glx.hdevel/mesag-dev satan# auto-apt search glu.h usr/include/GL/fglu.h devel/glutg3-dev usr/include/GL/glu.hdevel/mesag-dev satan# auto-apt search glut.h usr/include/GL/glut.h devel/glutg3-dev usr/include/GL/fglut.h devel/glutg3-dev pete -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] misc. XF86 4 upgrade and accel 3D issues
On Friday 15 February 2002 03:04 am, nbs wrote:
> ...
> Terminus, unfortunately, won't run due to a libstdc++ conflict. (A
> simple symblink won't fix it, so I've had to resort to e-mailing
> Vicarious Vision's support address.)
It's unfortunate that the libstdc++ so in various versions of gcc-2.9x
have exactly the same name, yet are incompatible. This makes it a pain
to use, for example, gcc-2.95.3 alongside Red Hat's various 2.96 versions.
What you can do is install the needed gcc and rename all occurrences of
libstdc++ to something else (like libstdx++) in both this gcc installation
and in the apps that need it. Here's a little script I wrote that helps
with this:
#!/bin/bash
#
# Replace 'libstdc++' with 'libstdx++' in all "regular" files in
# the current directory tree.
#
touch rodsgarbage1 rodsgarbage2
echo " "
echo "Be patient, this may take a few minutes..."
sleep 1
echo "Scanning for 'libstdc++'..."
perl -pi -e 's/libstdc[+][+]/libstdx++/g' rodsgarbage2 `find -type f -exec grep -q
libstdc[+][+] {} \; -print`
echo "Scanning for '-lstdc++'..."
perl -pi -e 's/-lstdc[+][+]/-lstdx++/g' rodsgarbage2 `find -type f -exec grep -q
lstdc[+][+] {} \; -print`
echo " "
echo "The following files were changed:"
echo " "
rm rodsgarbage2
find -type f -newer rodsgarbage1
rm rodsgarbage1
echo " "
-- Rod
http://www.sunsetsystems.com/
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] misc. XF86 4 upgrade and accel 3D issues
So today I decided it was about time I got 3D working on my box again (I have a Voodoo 3 2000, and am running Debian testing). I started with the innocent looking: apt-get install xserver-xfree86 That bumped me up to XFree86 Version 4.1.0.1. Yay! However, accelerated 3D still didn't work. A bit of head-pounding and IRCing later, I finally found the answer on Google Groups: apt-get install xlibmesa3 Now, the "glxgears" demo runs at ~80fps, even in fullscreen! Yay! But now, I'm having a few issues. The first, and most apparent, is that my fonts are... umm... different. For example, in Konsole (the x-term in KDE), the default font is some sans-serif proportional font which is coming out anti-aliased, and in non-proportional space (which, of course, looks very odd). I'm guessing I need to apt-get install some other fonts. I'll probably get that figured out if I spend more time (and time while I'm /awake/ :) ) I installed Terminus and TuxRacer today (two of the many commercial Linux games I've ended up buying or being given, which require accel'd 3D). Terminus, unfortunately, won't run due to a libstdc++ conflict. (A simple symblink won't fix it, so I've had to resort to e-mailing Vicarious Vision's support address.) TuxRacer, at first, didn't run, because I didn't have a 'matching GLX visual.' Checking their website, I discovered that for some reason the default '.rc' file for TuxRacer asks for 32bpp, but my screen's at 16bpp. I just changed the .rc file to use whatever my current color depth was. Now, however, rather than complaining and aborting, running the 'tuxracer' executable actually kills my X server! Also, now, my virtual consoles (the text consoles accessible via Ctrl-Alt-F1 thru Ctrl-Alt-F6) can't be seen. (Instead, I just see a frozen 640x480 zoom-in of the upper righthand corner of what was on the X screen (C-A-F7) when I switched. I can still log in and so forth, but I'm blind. I may as well have the monitor turned off :^( -- Note... once upon a time, under Red Hat, I had the same issue.) Finally... and this is a dumb question (but I was having a hell of a time finding anything using dselect), when I try to compile one of my OWN 3D games from source, I get complaints about glx.h, gl.h, glu.h, and glut.h missing. What do I need to apt-get to get those fellows on my box? Does any of this sound familiar? And if so, does anyone have any suggestions? In the meantime, I guess I'll leave my invisible consoles, my akward X11 fonts, and my broken 3D games, and head to bed. :) G'nite, and thanks! -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
