[gentoo-user] [OT] online collaboration, sharing desktop or separate windows over the net?
Hi folks, I'm planning to recruit two masters students for a development project starting summer/autumn. I'm rummaging the web for some nice collaboration tools since I'm planning on trying to recruit from wherever I can find good people, and it will be too expensive to relocate people to my site for the entire project duration. So far I've found: ssh/scp/rsync email jabber/icq/... gnomemeeting(ekiga?)/gnumeeting/skype The above lot takes care of file, text, and voice, but I would like more. Jarnal seems to have support for some sort of collaborative sketching, if everyone has tablet hardware. It would be nice to share a desktop. I found Collaborative VNC http://www.benjie.org/software/linux/collaborative-vnc/ But I haven't found anything that can share just one or several windows, similar to if you just open windows on a regular remote X session. Does anyone know of such a tool? If you have experience with collaborative tools that have worked fine I would love to hear more about it. Thanks Jimmy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] resource mapping wrong? pci-x nvidia fails to load
On Thursday 16 March 2006 06.01, Richard Fish wrote: On 3/14/06, Jimmy Rosen [EMAIL PROTECTED] wrote: Now, this is an NVidia GeForce 6600 PCI-X card on an Intel SE7525RP2 Have you tried updating the motherboard BIOS? According to the thread here: http://www.nvnews.net/vbulletin/showthread.php?t=46824 We had feedback from Intel and it's common PCI problem with SE7525GP2 Hopefully Intel fixes (their) firmware so I can use the two SE7525GP2s now sitting in the cabinet. This was over a year ago, and it looks like intel has done a couple of BIOS updates since then. http://downloadfinder.intel.com/scripts-df-external/filter_results. aspx?strTypes=allProductID=2095OSFullName=SuSE*+Linux+Enterprise+S erver+9.0lang=engstrOSs=127submit=Go%21 Of particular interest in the release notes: - SP/GP Tracker 20204 : [X] nVidia graphics cards do not work on GP2. Ok, so everything references a GP2, and you have an RP2, but maybe they have the same problem/fix? -Richard Thanks a bunch guys. Really helpful. Saved the day you did. Now I'm really happy, because I can finally bring my personal workstation home to my apartment, instead of keeping it in the lab to be able to do any real work. I finally got the approval from the sysadmins to flash the bios with the xxx04xxx18xxx update, and ... it worked like a charm. The problem is gone and all is well, so far at least. If anyone is considering this kind of setup based on the Intel SE7525GP2 or SE7525RP2, I would recommend going with a cheaper dual core athlon or opteron setup instead. This thing is way overpriced and doesn't give enough bang for the bucks. Harebrafolk Jimmy -- gentoo-user@gentoo.org mailing list
[gentoo-user] resource mapping wrong? pci-x nvidia fails to load
Hi folks, perhaps someone can shed some light on this problem? nvidia driver fails to load. In dmesg I find this: nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt :03:00.0[A] - GSI 16 (level, low) - IRQ 16 PCI: Setting latency timer of device :03:00.0 to 64 NVRM: The IO regions for your NVIDIA card are invalid. NVRM: Your system BIOS may have misconfigured your graphics card. NVRM: bar1 (framebuffer) appears to be wrong: 0x0 0x0 ACPI: PCI interrupt for device :03:00.0 disabled nvidia: probe of :03:00.0 failed with error -1 NVRM: the NVIDIA probe routine was not called for 1 device(s)!! NVRM: no devices probed, aborting! NVRM: this often occurs when rivafb is loaded and claims the device's resources. NVRM: try removing the rivafb module (or reconfiguring your kernel to remove NVRM: rivafb support) and then try loading the NVIDIA kernel module again. Now, this is an NVidia GeForce 6600 PCI-X card on an Intel SE7525RP2 motherboard with 1GB ram. Kernel 2.6.15 gentoo sources r1, nvidia drivers nvidia-kernel 1.0.6629-r5 and nvidia-glx 1.0.6629-r6. According to what little I've found on the web, there seems to be something weird with bios? I've tried cmos clear, and restarting with all cards unplugged, but I can't get it to work. Some sites suggested there might be some bios settings left if the pci-x had been plugged in before the ram expansion, which was the case here. Any suggestions? Thanks Jimmy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] resource mapping wrong? pci-x nvidia fails to load
On Tuesday 14 March 2006 15.08, Daniel da Veiga wrote: On 3/14/06, Jimmy Rosen [EMAIL PROTECTED] wrote: Hi folks, perhaps someone can shed some light on this problem? nvidia driver fails to load. In dmesg I find this: nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt :03:00.0[A] - GSI 16 (level, low) - IRQ 16 PCI: Setting latency timer of device :03:00.0 to 64 NVRM: The IO regions for your NVIDIA card are invalid. NVRM: Your system BIOS may have misconfigured your graphics card. NVRM: bar1 (framebuffer) appears to be wrong: 0x0 0x0 ACPI: PCI interrupt for device :03:00.0 disabled nvidia: probe of :03:00.0 failed with error -1 NVRM: the NVIDIA probe routine was not called for 1 device(s)!! NVRM: no devices probed, aborting! NVRM: this often occurs when rivafb is loaded and claims the device's resources. NVRM: try removing the rivafb module (or reconfiguring your kernel to remove NVRM: rivafb support) and then try loading the NVIDIA kernel module again. Have you tried doying what the module message told you to? Remove rivafb from you kernel and then load the nvidia module. Now, this is an NVidia GeForce 6600 PCI-X card on an Intel SE7525RP2 motherboard with 1GB ram. Kernel 2.6.15 gentoo sources r1, nvidia drivers nvidia-kernel 1.0.6629-r5 and nvidia-glx 1.0.6629-r6. According to what little I've found on the web, there seems to be something weird with bios? I've tried cmos clear, and restarting with all cards unplugged, but I can't get it to work. Some sites suggested there might be some bios settings left if the pci-x had been plugged in before the ram expansion, which was the case here. I don't think its your BIOS, probably a imcompatibility between riva framebuffer support and nvidia module. As I remember, you can use just VESA for framebuffer and disable this specific framebuffer driver. That might solve your problem. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ 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+ y++ --END GEEK CODE BLOCK-- Hello, Yes, I have removed all riva support from the kernel, which didn't help, and also tried with a small and clean 2.6.14 kernel that doesn't have rivafb as module or compiled in. The motherboard also has an ATI card, which I have tried disabling in bios, but that doesn't help either. And in response to the other post by Mike Williams, it is of course a PCI Express card, my whimsical mind... I updated to nvidia drivers 8178, which give a slightly different dmesg, but still don't work. dmesg: nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt :03:00.0[A] - GSI 16 (level, low) - IRQ 16 NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR1 is 0M @ 0x (PCI:0003:00.0) NVRM: The system BIOS may have misconfigured your graphics card. nvidia: probe of :03:00.0 failed with error -1 NVRM: The NVIDIA probe routine failed for 1 device(s). NVRM: None of the NVIDIA graphics adapters were initialized! --- cut some other non-related usb stuff --- ACPI: PCI Interrupt :03:00.0[A] - GSI 16 (level, low) - IRQ 16 NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR1 is 0M @ 0x (PCI:0003:00.0) NVRM: The system BIOS may have misconfigured your graphics card. nvidia: probe of :03:00.0 failed with error -1 NVRM: The NVIDIA probe routine failed for 1 device(s). NVRM: None of the NVIDIA graphics adapters were initialized! It does seem odd that the new 8178 driver probes the card twice and thinks it has found adapter_s_. Thankful for any further suggestions... I'm quite lost as to what to do at the moment. Jimmy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What is recommended behavior for complete updating of an old system ?
Hi Assembling a guide of recommended update usage seems like a good idea. Unfortunately I don't have much time (or much knowledge) on the matter, and submitting the cluster setup as docs and ebuild has higher priority (which doesn't mean I have much time for that either). Do you know if there is a working pipline for newbie started docs or ebuilds, where more experienced people can make a sanity check and much needed corrections before it gets submitted to the rest of the world (including other clueless newbies who would not recognize the author's madness)? Jimmy BTW thanks for the info Bob, helps a lot. I got the use flags in order, and after the last --newuse update even revdep-rebuild stopped complaining. On Monday 14 November 2005 05.36, [EMAIL PROTECTED] wrote: If ever there was a frequently asked question, it's this, or the general family of what's the best way to do an update in this situation?, like: What is a recommended way to update an old system to minimize the amount of broken ebuilds? What's the best way to do an update of an old machine that takes a long time to compile, or an embedded system? What's the best way to keep a machine completely up-to-date with the very latest, stability be damned?? What's the best way to keep a machine reasonably up-to-date, while keeping the machine stable and running? I couldn't find any of these in a FAQ on the gentoo website. Perhaps it's there and I missed it. But if indeed this FAQ lacks an answer, can we compose one from this discussion? Michael On Fri, 11 Nov 2005, Bob Sanders wrote: On Fri, 11 Nov 2005 16:46:41 +0100 Jimmy Rosen [EMAIL PROTECTED] wrote: Primary: What is a recommended way to update an old system to minimize the amount of broken ebuilds? Is emerge --emptytree world a good idea? Is it better than a clean install? Or is the documentation's way good enough even for a very old system: emerge --update --deep --newuse world emerge --depclean revdep-rebuild For an old machine that takes a long time to compile, or an embedded system - emerge sync once per week and let it run over the weekend doing updates. About once per year - - emerge sync - ufed and check out the USE flags. Some changes occur and they need a bit of cleaning. - emerge -eav system (no need to d world.) - emerge -uDNav world - python-updater - perl-cleaner all - revdep-rebuild I have an unexplainable fobia against --depclean though. Then don't. All you care about is the programs you currently use, those others just sit there taking some space. If you're not obsessive about a little disk space, why wipe them off the disk? And updating everything at once seems a bit reckless, I mean with the age of the system it would update almost everything. The package list was a mile long, and you never know what will break. That's why you should keep on a regular update schedule. A lot of programs get fixed, USE flags change, dependencies change, configuration options get updated. Secondary: How often should one update the system to minimize hassles with broken packages? Me? I do most of my working systems daily - takes about 10 minutes for all 4 systems. Home systems - daily or weekly. Laptop monthly. Better to see a small problem show up than wait for it to be buried in a lot of updates and then have to find out which of 10 or 20 packages caused the issue. Too often, and the hassle of constant upgrading can get tedious even if it works ok, and too late, and some odd dysfunctional version combinations start showing up that the packages were not really tested for, leading to broken ebuilds. Have you run other distributions where you get the massive binary updates 3 times per year? Have you had to fun of doing minor package updates in between the massive updates and then find that the massive update leaves your system completely borked because of conflicts with the minor updates? And I mean you don't see these until the system tries to reboot, and then it sometimes won't do that. I did like this: I didn't want to run a clean install or an --emptytree thingie. I wanted to take it a few steps at a time, so that if something broke I might have an idea about what new packages it was that broke it. 1) take a backup of the system. I have some modifications in /etc/init.d scripts and some extra non-gentoo stuff for clustering installed that I didn't want to risk, and I was pretty sure something would bork and leave me clueless. lol 2) emerge sync. Nice, worked. emerge *only the most important stuff* (oh, I'm really chicken btw): portage, baselayout, etc. That brought in some dependencies, but it worked out all right
Re: [gentoo-user] [OT] Is a wiki what I'm after?
On Saturday 12 November 2005 17.11, Chris White wrote: On Saturday 12 November 2005 16:33, Andrew Lowe wrote: Hi all, The wife has finally put her foot down and said I have to clean up the mess that inhabits my office which occupies our second bedroom. I probably would tell you the same thing sadly ;P A wiki is one of the first things to come to mind. I'm contemplating setting a wiki up on my trusty little firewall/email/squid/dns server, scanning the clipping, creating an entry in the wiki, placing, say, the first para of the clipping in the wiki page, maybe via OCR software, and then attaching the scanned image to the page. This way I can search the wiki looking for stuff, the first paragraph of the article will probably tell me if its the page I'm after and if so, look at the scanned image for the full article. Yes, I'd recommend tikiwiki for that, as I know they have a file gallery, which pretty much does what you've suggested. I also noticed that tikiwiki is generally really easy to setup. Does this sound like a suitable use for a wiki or am I wasting my time and there are more application specific packages out there that would suit my needs better? Anyone done anything like this before? Any thoughts greatly appreciated, Andrew My 2 Cents Chris White I'm regularly scanning most dead-tree info that comes my way, and filing it away. I bought a cheap HP all in one gadget (d125xi ~200€) that has a document feeder on top which works really well up to ~40 pages per batch. Its operation is easily scriptable and together with imagemagick you can do some nice post-processing. However, I haven't found a good OCR program yet. That is the major hurdle. Searchability is the really important thing. The space saving and portability is nice enough though, for the moment. I heard that Adobe has a windoze only software that can do this reasonably well, but I haven't researched it further. Jimmy -- gentoo-user@gentoo.org mailing list
[gentoo-user] What is recommended behavior for complete updating of an old system ?
Hi folks I recently went through the (minor hell) of updating my old workhorse gentoo box. I hadn't touched the system much (apart from open services like ssh) for about 1.5 years due to a series of facts: 1) It just worked so darned nice. 2) My phd endstretch didn't leave much time to computer fiddling, and the cluster just worked so darned nice (diskless SSI booting from the original gentoo machine (see above)). 3) It lived behind a nice firewall which I trust enough (yes I'm a bit naive) and the open services such as ssh had been updated more regularly. Now I had a bit of time and sice I had moved to France for my post doc I had to get skype in/out working, which didn't want to install nicely. So I thought a thorough general system update was overdue. First, my questions, then (if you really want) the arduous story on how I did it. Feel free to comment, give tips and point out my mistakes. Primary: What is a recommended way to update an old system to minimize the amount of broken ebuilds? Is emerge --emptytree world a good idea? Is it better than a clean install? Or is the documentation's way good enough even for a very old system: emerge --update --deep --newuse world emerge --depclean revdep-rebuild I have an unexplainable fobia against --depclean though. And updating everything at once seems a bit reckless, I mean with the age of the system it would update almost everything. The package list was a mile long, and you never know what will break. Secondary: How often should one update the system to minimize hassles with broken packages? Too often, and the hassle of constant upgrading can get tedious even if it works ok, and too late, and some odd dysfunctional version combinations start showing up that the packages were not really tested for, leading to broken ebuilds. I did like this: I didn't want to run a clean install or an --emptytree thingie. I wanted to take it a few steps at a time, so that if something broke I might have an idea about what new packages it was that broke it. 1) take a backup of the system. I have some modifications in /etc/init.d scripts and some extra non-gentoo stuff for clustering installed that I didn't want to risk, and I was pretty sure something would bork and leave me clueless. lol 2) emerge sync. Nice, worked. emerge *only the most important stuff* (oh, I'm really chicken btw): portage, baselayout, etc. That brought in some dependencies, but it worked out all right after a while and a lot of figuring out the /etc/init.d and config file changes that has happened for the last 1.5 years. And some other changes as to where certain configs go, and how, and so on. But most was easily searchable in docs or forums.gentoo or on this list. Reboot here to see if it even booted any more... YEEAAAH! 3) emerge basic user packages like gcc, glibc, xorg (yes I was still on xfree) kernel, etc. note: I have to stay on 2.4 because I use openmosix for the clustering, and I don't yet trust 2.6om. For this I started using --update --deep since I did want an updated system, but not all at once. This still worked out all right, with just some minor headaches of broken ebuilds. And some config files again. hrmmpf kernel change means reboot. darned. 4) emerge --update --deep desktop stuff like KDE, openoffice, browsers, etc... This started generating Lots of broken packages. I have spent many hours looking through the _VERY_NICE_ bugs.gentoo.org. I still get bitten by bugs that are filed fixed in mid 2003. lol Some more config file updates, and restarting all significant services to use the new software. 5) Now, muahaha, emerge --update --deep world. Aiaiai. Another batch of broken packages, but not the critical ones, since most everything necessary has already been updated. Some more config files. I _really_ like dispatch-config and cfg-update by now. 6) Well, I'm here now. The system works just fine. And yes, I recently remembered that I had forgotten to update the USE flags to cover the current situation (stooopid teflon memory). But I hope I can wait until the current few remaining problems are out of the way, and then I can perhaps (hope and pray) use the eminent and functional(?) --newuse (and I do so very much hope works with/as --deep). I still have some problems, mainly with skype, which works but have some odd dependency thingie with dbus that emerge doesn't like. And revdep-rebuild tries to bring in some stuff that are no longer in portage. Interesting, though, is that equery depends '=pack-group/packagename-x.y.z' doesn't report anything depending on those old packages any more after all the updates. How can I figure out what wants them? revdep-rebuild? is it safe to use, and safe with --package-names (since just about every single package it's trying to bring in is no longer in the portage tree) What somethingsomething-update programs should I run during the process? python-updater
[gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?
Hi, during my recent battle with updating my system I ran across an old problem I haven't figured out. How to CONFIG_PROTECT /sbin/rc and /sbin/functions.sh ? Is there a way. Just putting them in CONFIG_PROTECT doesn't help and gentoo complains about them not beeing directories. I have a work around that is ok, to softlink them from /sbin/rc.safe and /sbin/functions.sh.safe. Anyone know? Thanks Jimmy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?
Hi, Well, it's not that I don't want them modified by new baselayout. It's just that I would like to have the convenience of using etc-update to remind me that I need to update them manually. I have some modifications in those files that allow me to boot a diskless cluster from a single regular gentoo installation. Right now I always watch very carefully when I have to bring in a new baselayout since I have to keep those two scripts working. But I have been known to forget. I also have modifications in a few of the critical /etc/init.d scripts as well, but they are caught by the CONFIG_PROTECT and I'm immediately reminded to update and manually merge my functionality changes when a new version is in. So this is essentially just for me to get autoreminders when they need attention. My teflon memory is dangerous enough, and I need all the help I can get from automated tools and reminders. Thanks Jimmy On Friday 11 November 2005 19.03, Richard Fish wrote: On 11/11/05, Jimmy Rosen [EMAIL PROTECTED] wrote: Hi, during my recent battle with updating my system I ran across an old problem I haven't figured out. How to CONFIG_PROTECT /sbin/rc and /sbin/functions.sh ? Is there a way. Just putting them in CONFIG_PROTECT doesn't help and gentoo complains about them not beeing directories. I have a work around that is ok, to softlink them from /sbin/rc.safe and /sbin/functions.sh.safe. I think that trying to CONFIG_PROTECT these is a _very_ bad idea. They are part of baselayout, and pretty much go hand-in-hand with the /etc/init.d and /lib/rcscripts scripts. If a new version of baselayout is merged with an old functions.sh, you risk ending up with an essentially unbootable system. If you don't want those modified, mask out newer versions of baselayout in /etc/portage/package.mask. -Richard -- gentoo-user@gentoo.org mailing list
