Re: [gentoo-user] System Locking Up
On Tue, 2005-11-08 at 23:11 -0800, Cliff Wells wrote: On Tue, 2005-11-08 at 22:43 -0500, Shawn Singh wrote: Hello all, Over the course of the past 2 weeks I've come home to a zombie machine two times. Here are the symptoms: It does sound like hardware. I'd check three things first: 1) Are all the fans in the system working? 2) Check for swollen or leaking capacitors (see http://www.trendit.co.za/capacitor.htm). This is *really* common, so don't discount it until you've checked. An added note on this: you can actually repair boards like this (you can replace any capacitor with a capacitor of equal or greater capacity), but I've found that it's not worth it. It can take a couple hours and is pretty hit or miss (I once replaced half the caps on a dead board which got it working, then replaced the other half and it never worked again :P). Regards, Cliff -- gentoo-user@gentoo.org mailing list
RE: [gentoo-user] Out of portage
Renat Golubchyk mailto:[EMAIL PROTECTED] wrote: You can copy the ebuild to your overlay and patch postfix from there. If you don't have to do anything else before compiling it then it's as trivial as epatch /path/to/postfix.patch somewhere in src_unpack(). Doing it this way has the benefit of letting portage manage your packages. This seems to be the best way. And indeed it is trivial. You'll just have to keep an eye for upgrades, because they will probably come without this patch. If you want this patch to be included in postfix create a bug in bugzilla with the request. I don't think it is a good idea. I would not second guess Wietse (author of postfix) for the suitability of the patch for general consumption. Thank you for your help. Eray -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Out of portage
On Wed, 9 Nov 2005 10:23:31 +0200 Eray Aslan [EMAIL PROTECTED] wrote: Renat Golubchyk mailto:[EMAIL PROTECTED] wrote: You'll just have to keep an eye for upgrades, because they will probably come without this patch. If you want this patch to be included in postfix create a bug in bugzilla with the request. I don't think it is a good idea. I would not second guess Wietse (author of postfix) for the suitability of the patch for general consumption. He may change his mind some time in the future. Anyway, if you suggest it on Gentoo bugzilla it may be included, so that it is possible to enable it with a USE-Flag. Cheers, Renat -- Probleme kann man niemals mit derselben Denkweise loesen, durch die sie entstanden sind. (Einstein) pgpTnuJqpdL7k.pgp Description: PGP signature
Re: [gentoo-user] Developmnet Environment for PHP and PERL
On Wednesday 09 November 2005 05:21, Michael Shaw wrote: gentuxx wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Shaw wrote: What editor do people use for PHP and Perl development. I'm looking for something with syntax highlighting and such, so that rules ut vi or gedit. Thanks, Mike I seems like you've got a lot of good suggestions here, so I'll just throw my 2ยข out into the pot too! For perl, I use vim for quick edits and kate for larger projects. It doesn't auto-tab the way I think it should, but that's probably just a configuration that I haven't given it yet. ;-) I like bluefish for HTML|PHP|CSS, but the CSS and PHP colorization is a little jumpy. Sometimes it'll do it, sometime it won't. So then I started using gphpedit for JUST PHP. bluefish is nice for (X)?HTML, and OK for CSS, but more often than not, I find myself comfy with PHP and CSS in gphpedit. I might have to look into eclipse though.that sounds interesting. And I worked with emacs while I was working on some documentation for the Fedora Documentation Project, I could probably handle that if the plug-ins worked right. Anyway, my top pick for perl is kate, for PHP is gPHPEdit. Cheers! - -- gentux echo hfouvyAdpy/ofu | perl -pe 's/(.)/chr(ord($1)-1)/ge' gentux's gpg fingerprint == 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A 6996 0993 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDcVqOLYGSSmmWCZMRAk8tAJ4zn4IRuwmgx/rOIAwi701dti+aJQCfS3jt 8czaaR9XrRvTJW2p2WNBTwY= =9/bd -END PGP SIGNATURE- I found Bluefish, but the syntax hilighting didn't work. gPHPEdit looks good. I'll give it a try. Even if only for syntext hilighting. Thanks, Mike From the free/open editors Quanta is the one that suits me best. The gratest editor ever tried is Zend's IDE. This is for writing HTML/PHP, I don't do Perl -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] About sed
On Tue, 8 Nov 2005 23:37:52 -0500, Walter Dnes wrote: That is not what sed is designed to do. sed is Streaming EDitor. You specify an input file, and the changed file goes to STDOUT. If you want to change the original file, you need to use ed. Or use sed's -i or --in-place argument. -- Neil Bothwick Never drink coffee that's been anywhere near a fish. signature.asc Description: PGP signature
Re: [gentoo-user] Out of portage
On Wed, 9 Nov 2005 10:23:31 +0200, Eray Aslan wrote: You'll just have to keep an eye for upgrades, because they will probably come without this patch. If you want this patch to be included in postfix create a bug in bugzilla with the request. I don't think it is a good idea. I would not second guess Wietse (author of postfix) for the suitability of the patch for general consumption. The patch could be made optional, enabled by a USE flag. -- Neil Bothwick It compiled? The first screen came up? Ship it! -- Bill Gates signature.asc Description: PGP signature
[gentoo-user] How to make a portage mirror
Hello I working In idg.pl and i want to make a portage mirror, but i don't know how to do it ? Can you tell me, how can I do it on gentoo linux ? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
Peter Ruskin wrote: ebegin Checking that /usr/src/linux is linked to booted kernel... if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut -f2 -d\|cut -f2,3,4 -d' ') ] This looks more complicated than it really should be. Just run ln on reboot (stolen from your post): rm -f /usr/src/linux ln -s /usr/src/linux-$(uname -r) /usr/src/linux Best regards, -- Norberto wants an AMD64 system right now! Bensa 4544-9692 Ciudad de Buenos Aires, Argentina -- gentoo-user@gentoo.org mailing list
[gentoo-user] Only seem to be able to get on digest verison of this list
I have now tried sending a message to [EMAIL PROTECTED] twice and all I seem to be able to subscribe to is the digest version. Could someone please email be off list to tell me how to get on the normal version. This is really odd because getting on gentoo-media was easy. Regards, Ben -- Ben Edwards - Bristol, UK, England WARNING:This email contained partisan views - dont ever accuse me of using the veneer of objectivity If you have a problem emailing me use http://www.gurtlush.org.uk/profiles.php?uid=4 (email address this email is sent from may be defunct) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge kino problem
Nick Rout schreef: On Wed, 09 Nov 2005 13:34:59 +1000 Richard Watson [EMAIL PROTECTED] wrote: !!! If you need support, post the topmost build error, NOT this status message. In other words, please post the 10-20 lines *above* the lines you posted (which were the status report); the actual compile error will be found there. And there's no way to know what happened without seeing the error itself. Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
Norberto Bensa schreef: Peter Ruskin wrote: ebegin Checking that /usr/src/linux is linked to booted kernel... if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut -f2 -d\|cut -f2,3,4 -d' ') ] This looks more complicated than it really should be. Just run ln on reboot (stolen from your post): rm -f /usr/src/linux ln -s /usr/src/linux-$(uname -r) /usr/src/linux Thanks for the tip-- but (no offense meant) who cares? Can someone tell me on what basis this *needs* to be done as a standard operation? -- If you have some external module that compiles against the kernel source, you most likely need it against *all* kernel sources, not just the running one (so redirecting the link is only of limited usefulness); -- If you need some external module compiled against the kernel source and you don't have it (thus needing to compile it against the currently running kernel), then there's likely to be something seriously wrong with that boot anyway (you don't have 3D hardware acceleration, you don't have wireless networking, you don't have sound-- whatever the external module in question is), so you're much less likely to boot it as a matter of course... Not that you wouldn't want to try to fix it, and if you did try, you would naturally want to compile the external modules against that kernel source, but that doesn't by a long shot add up to redirecting the /linux symlink every time you boot; --makes no provision for newly-installed/upgraded kernel sources, which imo need the symlink more than old, already compiled kernels. Or rather, if you redirect the symlink to the currently running kernel at boot, you have to redirect it again to your about-to-be-installed kernel in order to compile the external modules against it anyway, so why do extra work-- either you wait till you compile and boot the new kernel to redirect the symlink (at which point you've got a half-broke system because the needed external modules have not yet been compiled because the symlink was not redirected unless you use the symlink USE flag when emerging, which rather negates the point of having redirected the symlink to the currently-running kernel), then compile the external modules, then reboot to load the external modules (depending on the module), or you redirect the symlink manually before compiling the newly-installed source, which (again) negates the purpose of redirecting the symlink automatically at boot (rather than via the USE flag during emerge) in the first place? Not getting it at all. How many kernels does one keep in a bootable state, anyway-- and use commonly, without needed external modules, no less-- that this would be necessary? Really, truly, not getting the point. Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Developmnet Environment for PHP and PERL
On 11/8/05, Michael Shaw [EMAIL PROTECTED] wrote: What editor do people use for PHP and Perl development.I'm looking forsomething with syntax highlighting and such, so that rules ut vi or gedit.Thanks,Mike-- gentoo-user@gentoo.org mailing listEclipse is the ultimate IDE from my perspective. I am running 3.1 with Pydev[1], Colorer[2], Web Standards Tools[3], C++[4], EPIC (Perl)[5], and PHPEclipse[6] which lets me do just about everything. The only thing with Eclipse (and it may just be me) is that there seems to be a bit of learning involved to figure out what it means by perspectives and natures and such, after that its the best IDE I have ever used. [1] http://pydev.sourceforge.net/[2] http://colorer.sourceforge.net/[3] http://eclipse.org/webtools/wst/main.xml[4] http://www.eclipse.org/cdt/[5] http://e-p-i-c.sourceforge.net/[6] http://www.phpeclipse.de/tiki-view_articles.php-Mike-- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationLinux takes junk and turns it into something useful. Windows takes something useful and turns it into junk.
Re: [gentoo-user] use of /usr/src/linux symlink
051109 Holly Bostick wrote: Can someone tell me on what basis this *needs* to be done as a standard operation? Not getting it at all. How many kernels does one keep in a bootable state, anyway -- and use commonly, without needed external modules, no less -- that this would be necessary? Really, truly, not getting the point. Switching kernels is not like using a different browser or editor. I now have 2.6.14 working ok (still ~x86), but am keeping 2.6.12 (may be soon to go) 2.6.9 around in case something unexpected happens with 2.6.14 . However, if I want to use 2.6.12 , I will have to recompile Nvidia reset the display for Gkrellm might even find something else needs doing. Some apps do depend on the version of the kernel you are using. Maybe I'm not getting what you're not getting ... (smile) -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
My Box sometime locks ups during high load, but it's really strange. For example emerging ~30 ebuilds in xfce Terminal: after 2h of emerging PC locked up during kcontrol. After rebooting and again trying to build kcontrol it locked up 4 times in a row, but compiling it from shell(without running xorg(xfce)) worked fine. I've tested RAM with bootable cd, disk with extended smart tests and got no errors... -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Wed, Nov 09, 2005 at 10:28:04AM -0500, Philip Webb wrote: 051109 Holly Bostick wrote: Can someone tell me on what basis this *needs* to be done as a standard operation? Not getting it at all. How many kernels does one keep in a bootable state, anyway -- and use commonly, without needed external modules, no less -- that this would be necessary? Really, truly, not getting the point. Switching kernels is not like using a different browser or editor. I now have 2.6.14 working ok (still ~x86), but am keeping 2.6.12 (may be soon to go) 2.6.9 around in case something unexpected happens with 2.6.14 . However, if I want to use 2.6.12 , I will have to recompile Nvidia reset the display for Gkrellm might even find something else needs doing. Some apps do depend on the version of the kernel you are using. Maybe I'm not getting what you're not getting ... (smile) Why do you have to recompile NVidia? Every time I do a kernel upgrade, I compile NVidia against the kernel. But so long as you don't remove the old kernel module or do a new compile of the old kernel, you should be able to book back into the old kernel just fine. On my laptop for example, /lib/modules/2.6.7-(something) and /lib/modules/2.6.10-(something) both exist and each contains its version of bcm5700, ipw2200. With the exception that I use the Xorg drivers for radeon on .10 and fglrx on .7, the setup is identical. The small difference can be easily overcome by commenting out some lines in modules.autoload /usr/src/linux is not used AT ALL in the boot process. There's no need to change that symlink if you just need to boot into another kernel to troubleshoot your machine. It is purely compile-time, and aside from kernel-hackers, most of us usually only compile one kernel one time followed by ext. modules. So I agree with Holly that changing the symlink on every boot is silly and a waste of effort SO LONG AS you (the user) remember to update the symlink before you compile stuff against the kernel. W -- Yan Can Cook and George Lucas have a new joint-venture web site, titled eWok. Sortir en Pantoufles: up 6 days, 17:15 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Thu, 10 Nov 2005 04:54, Holly Bostick wrote: Secondly, you're *using* 2.6.14, and you're keeping 2.6.12 around as a fallback. It's very unlikely you're going to actually boot into 2.6.9, and while you may boot into 2.6.12, you are not in fact doing so (because 2.6.14 is working OK). So what is the need for this symlink redirection? For my part I'm playing round with the kernel source in several custom versions and rebooting often when testing for some things. Doing that several times in an hour, re-making the simlink manually can be tedious. So it just takes some of the drudgery out of manually performing this every time. And you know that when you boot the kernel source is in a sane state even if you forgot that you had booted back into your stable kernel and for example there is a new nvidia version available. -- Isn't it ironic that many men spend a great part of their lives avoiding marriage while single-mindedly pursuing those things that would make them better prospects? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Wed, Nov 09, 2005 at 03:35:42PM +0100, Holly Bostick wrote: Norberto Bensa schreef: Peter Ruskin wrote: ebegin Checking that /usr/src/linux is linked to booted kernel... if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut -f2 -d\|cut -f2,3,4 -d' ') ] This looks more complicated than it really should be. Just run ln on reboot (stolen from your post): rm -f /usr/src/linux ln -s /usr/src/linux-$(uname -r) /usr/src/linux Thanks for the tip-- but (no offense meant) who cares? Norbertos suggestion and Peters refinement were useful to me as examples of one plausible interpretation of what /usr/src/linux symlink should be - a shorthand way of finding the source for the running kernel. I was glad to see that I was not the only one who was not clear on its intended use, and hence how it should be maintained. Can someone tell me on what basis this *needs* to be done as a standard operation? If it were done as standard, then it would make the commonly held assumption that it points to the currently running kernel correct unless an explicit action had been taken by a super user since the last reboot... But that is a justification or argument for doing so - it appears from what you say that there is no *need* for it to be so (although the same could be said about an awful lot of the Unix/Linux filesystem organization - it is arbitrary until some application or process that you use is written to depend on it).. -- If you have some external module that compiles against the kernel source, you most likely need it against *all* kernel sources, not just the running one (so redirecting the link is only of limited usefulness); Ok - this seems to be the bit that I am a little unclear on. If there are, as indicated in your earlier response (which I was still mulling over) applications, libraries and external kernel modules that need to be compiled against a kernel, and we want to be able to use grubs ability to select from a choice of kernels, what is the mechanism by these we ensure the correct applications, libraries and external kernel modules (lets call them 'objects' to avoid having to list the possibilities each time - not to be confused with the current trendy programming paradigm) are used for the currently running kernel? If the binaries are to be stored in a kernel dependent location, like the kernel modules build within the kernel source tree that are built to /lib/modules/kernel-version, then /usr/src/linux cannot really be being used as a symlink (ie a way of accessing the kernel files without needing to know which version it is) because the build process will need to know the target kernel version in order to make the directory names or tag. In effect, it could equally well be a file called '/usr/src/build-kernel' which contains the version number of the kernel being compiled for...? Anyway, if I understand you correctly, if you are not building anything, then it doesn't matter. And there is certainly no justification is assuming you are building for the kernel that is currently running. Right? Presumably these kernel dependent objects only need emerge to download the source once, but then must be rebuilt once for each kernel you want to install - right? And somehow the binaries will be kept separate and the correct ones chosen at boot time based on the active kernels knowledge of its own version identity. Is this what 'sys-kernel/module-rebuild' is intended to take care or for us? So we just /usr/src/linux to the newly installed kernel and run module-rebuild and the kernel dependent modules will all be made for the new (or modified) kernel. It seems that the desirablility of having the boot process automatically update the symlink depends on how much you want to be able to use /usr/src/linux as a shorthand for manually typing /usr/src/linux-`uname -r`, which is probably a bit arcane for a nieve user... Not getting it at all. How many kernels does one keep in a bootable state, anyway-- and use commonly, without needed external modules, no less-- that this would be necessary? I typically have 3-4. The current which I think is fully working, the previous kernel just in case I discover I was wrong and had forgotten to test something vital, and the new kernel which I am in the process of installing but havn't finished testing enough to use when doing something important or letting others on the system.. I also have several kernels which boot to different filesystems (eg the old SuSE system because its crypto filesystem is not compatible with the gentoo one) and alternate operating systems such as BSD/Plan9/Inferno/OS-9000 - can't think of any others worth running just now ;) But being different filesystems, they arn't relevent to the /usr/src/linux link question. Regards, DigbyT -- Digby R. S. Tarvin [EMAIL PROTECTED] http://www.digbyt.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Screen is being a CPU hog, big time!!!
Dale wrote: I posted a thread on the folding forums. If no one replies before to long, I'm going to delete and start over with a fresh install. Maybe I got a bug or something. Knowing me, I just screwed up something. LOL It happens, especially with me. :( The best thing that has happened to me in a very long time is finding my new lady, after 15 years of looking I might add. Thanks Dale :-) Well, the folks on the forums couldn't figure it out either. I deleted the folding stuff and re-installed it. It works fine now. I guess it had a bug in it's butt or something. Strange though. Thanks Dale :-) -- To err is human, I'm most certainly human. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Peper wrote: My Box sometime locks ups during high load, but it's really strange. For example emerging ~30 ebuilds in xfce Terminal: after 2h of emerging PC locked up during kcontrol. After rebooting and again trying to build kcontrol it locked up 4 times in a row, but compiling it from shell(without running xorg(xfce)) worked fine. I've tested RAM with bootable cd, disk with extended smart tests and got no errors... I'm no guru here but when I had the some thing happening to me a good while back, I had the wrong chipset selected in my kernel. I ran hdparm -Tt /dev/hd* back to back using the thing and it locked up after about the third or forth run. It would not respond any more either. I have had to pull the plug, even the power switch wouldn't work. I would push it and hold it for 10 seconds or so and it would still be locked up. Just to make sure, for primary master: hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda That's the idea. It works the hard drive pretty good. Just a thought. Dale :-) -- To err is human, I'm most certainly human. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Last time I had these locks up it was a dying power suppy fault. Dying RAM or mobos are another common cause. Check your memory with memtest86 overnight, as already suggested. If memtest86 gives no errors, it's probably the power supply. If it's the mobo or the RAM, memtest should detect it. m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Well, had some lockups here too, most caused by: 1) Heat, that's a known problem. 2) Memory, guessing what stick is dying makes me ill. 3) MoBo, that Soyo mobo and its inflating capacitors. I came to the conclusion that a PC must have special treatment in order to keep up night and day (wich is my case), so, a good environment and sane settings are welcome. Good fans, maybe a water cooler for heat control, strict control over static eletricity and dust (yeah, hate it), and not playing around with flags for super duper velocity that may hang the system. Anyway, I would check all the stuff the other people mentioned, and also check my video card for any problem (once it turned out to be a memory problem AT THE VIDEO CARD). Good luck. -- 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-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
On 11/9/05, Peper [EMAIL PROTECTED] wrote: My Box sometime locks ups during high load, but it's really strange. For example emerging ~30 ebuilds in xfce Terminal: after 2h of emerging PC locked up during kcontrol. After rebooting and again trying to build kcontrol it locked up 4 times in a row, but compiling it from shell(without running xorg(xfce)) worked fine. Forgot to mention that I had the same problem as Peter with X terminals, from that day on compiles and high demand shell stuff only with tty console. I've tested RAM with bootable cd, disk with extended smart tests and got no errors... -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list -- 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-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
Rumen Yotov wrote: On Tue, 2005-11-08 at 17:18 +, Digby Tarvin wrote: Something which I havn't found any explicit elaboration of in the documentation... The convention in the Linux/gentoo filesystem seems to be to have a unique directory for each installed kernel in /usr/src, with a symbolic link to the 'current' kernel directory named /usr/src/linux.. The question is - is this just a user convenience, or will parts of the system break if it is not maintained correctly? The reason I ask is that if I have several kernels which I have configured grub to allow me to select from at boot time, where should this symlink point? The newest kernel? An experimental one being worked on? The one most recently booted from. If the latter case then it is likely to be wrong for a finite period following boot until the system has come up far enough to allow me to update it. Anyone know what is likely to break (if anything) if I boot from a kernel other than the one which corresponds to the directory /usr/src/linux points to, and neglect to update the link? Does it direct (for instance) the target directory for an emerge of new kernel components? Or does it perhaps have to point to the kernel being built during any recompile? Regards, DigbyT -- Digby R. S. Tarvin [EMAIL PROTECTED] http://www.digbyt.com Hi, There seems to exist at least two current kernels - one is the kernel to which /usr/src/linux points, this one is used by most (all ?) kernel-module programs (i have 3 of them: nvidia, arpstar, loop-aes; had also alsa-driver). When you compile/recompile any one of them they use the kernel sources pointed by /usr/src/linux. Patch kernel sources too (e.g. l7-filter). The second kernel is your running kernel (available by uname -r) this one is the one actually running at any givenn time. Don't have any examples of something using this one. Anybody here? HTH.Rumen Changed my symlink to point to 2.6.12-gentoo-r10, compiling ndiswrapper 1.5 is using running kernel 2.6.13 #ls -al lrwxrwxrwx 1 root root 24 Nov 8 12:57 linux - linux-2.6.12-gentoo-r10/ #make make -C driver make[1]: Entering directory `/root/ndiswrapper-1.5/driver' make -C /lib/modules/2.6.13-gentoo-r3/build SUBDIRS=/root/ndiswrapper-1.5/driver \ DRIVER_VERSION=1.5 make[2]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3' Building modules, stage 2. MODPOST Chris -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Wed, 9 Nov 2005 16:34:03 +, Digby Tarvin wrote: Norbertos suggestion and Peters refinement were useful to me as examples of one plausible interpretation of what /usr/src/linux symlink should be - a shorthand way of finding the source for the running kernel. But it is not. As soon as you install a new kernel source, even before you configure and compile it, the symlink no longer indicates the current kernel. uname -r shows the current kernel, with it's source at /usr/src/linux-$(uname -r) -- Neil Bothwick If you think the problem is bad now, just wait until we've solved it. signature.asc Description: PGP signature
Re: [gentoo-user] use of /usr/src/linux symlink
Digby Tarvin schreef: On Wed, Nov 09, 2005 at 03:35:42PM +0100, Holly Bostick wrote: -- If you have some external module that compiles against the kernel source, you most likely need it against *all* kernel sources, not just the running one (so redirecting the link is only of limited usefulness); Ok - this seems to be the bit that I am a little unclear on. If there are, as indicated in your earlier response (which I was still mulling over) applications, libraries and external kernel modules that need to be compiled against a kernel, Not against a kernel. Against a kernel *source*. These are not the same thing. The kernel you actually boot is a binary file, compiled from the source in /usr/src/whatever. When it is compiled, you copy the binary to /boot, and that is what you boot. That is the meaning of 'make install'. Like any binary, once compiled it is 'detatched', let us say, from the source, and is no longer related to it in that any changes to the source do not affect the compiled binary-- if you make a change to the source, you have to recompile the binary to reflect the changes in the new binary. and we want to be able to use grubs ability to select from a choice of kernels, what is the mechanism by these we ensure the correct applications, libraries and external kernel modules (lets call them 'objects' to avoid having to list the possibilities each time - not to be confused with the current trendy programming paradigm) are used for the currently running kernel? If you compiled the objects against the source of the kernel under consideration -- and this is the purpose of the /usr/src/linux symlink, to tell the emerge which kernel source the objects should be compiled against, then they are compiled against the source of the kernel Let me put it this way. ati-drivers (the proprietary drivers for ATI video cards) are an external kernel module. External, because they are not contained in the kernel source (being proprietary), but a kernel module because they 'hook' into the kernel as a normal module. When I compile them, here is the beginning of the output: Determining the location of the kernel source code Found kernel source directory: /usr/src/linux Found sources for kernel version: 2.6.13-gentoo-r4 Checking for MTRR support enabled ... Checking for AGP support enabled ... Checking for DRM support disabled ... X11 implementation is xorg-x11. | Unpacking source... Unpacking Ati drivers ... The drivers, like all other drivers, need certain kernel functions to be available (or not available) in order to operate correctly; so because this driver must compile against the kernel source, the script checks to confirm that the necessary kernel functions are enabled/disabled prior to compiling.This is why you must compile against a *configured* kernel source (it need not be compiled, but it must be configured, so that the script can determine what functions will be available in the kernel binary). As you see, this emerge of the ATI drivers compiled against the source of 2.6.13-gentoo-r4, because that was where the /usr/src/symlink was pointing when I performed the emerge. This was in fact an upgrade to the driver, and 2.6.13-r4 was my currently-running kernel. However, later, I downloaded and configured 2.6.14, and re-emerged the ATI drivers (I use the symlink USE flag, so the symlink was automatically redirected): Determining the location of the kernel source code Found kernel source directory: /usr/src/linux Found sources for kernel version: 2.6.14-gentoo Checking for MTRR support enabled ... Checking for AGP support enabled ... Checking for DRM support disabled ... X11 implementation is xorg-x11. | Unpacking source... This emerge compiled against the source of 2.6.14-gentoo, because the /usr/src/linux symlink was redirected to the source of that kernel. Both kernels now have the ATI drivers compiled for them, because when compiled (either during a kernel compile, or an external module compile), modules are placed in a kernel-specific directory: la /lib/modules totaal 9 drwxr-xr-x 12 root root 384 nov 7 15:43 . drwxr-xr-x 12 root root 5688 nov 7 16:34 .. drwxr-xr-x 5 root root 472 mei 25 17:29 2.6.11-ck8-r1 drwxr-xr-x 4 root root 448 jul 24 00:04 2.6.11-gentoo-r11 drwxr-xr-x 5 root root 472 jun 15 03:06 2.6.11-gentoo-r6 drwxr-xr-x 5 root root 472 jul 7 02:17 2.6.11-gentoo-r8 drwxr-xr-x 6 root root 496 okt 13 14:53 2.6.12-gentoo-r10 drwxr-xr-x 4 root root 448 aug 19 06:36 2.6.12-gentoo-r6 drwxr-xr-x 4 root root 448 sep 2 05:39 2.6.12-gentoo-r9 drwxr-xr-x 6 root root 496 nov 7 18:30 2.6.13-gentoo-r4 drwxr-xr-x 6 root root 496 nov 7 19:03 2.6.14-gentoo and within it: la /lib/modules/2.6.13-gentoo-r4/video totaal 317 drwxr-xr-x 2 root root 72 nov 7 18:00 . drwxr-xr-x 6 root root496 nov 7 18:30 .. -rw-r--r-- 1 root root 321951 nov 7 18:00 fglrx.ko la /lib/modules/2.6.14-gentoo/video totaal 317
Re: [gentoo-user] use of /usr/src/linux symlink
- Original Message - From: Philip Webb [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Wednesday, November 09, 2005 10:28 AM Subject: Re: [gentoo-user] use of /usr/src/linux symlink 051109 Holly Bostick wrote: Can someone tell me on what basis this *needs* to be done as a standard operation? Not getting it at all. How many kernels does one keep in a bootable state, anyway -- and use commonly, without needed external modules, no less -- that this would be necessary? Really, truly, not getting the point. Switching kernels is not like using a different browser or editor. I now have 2.6.14 working ok (still ~x86), but am keeping 2.6.12 (may be soon to go) 2.6.9 around in case something unexpected happens with 2.6.14 . However, if I want to use 2.6.12 , I will have to recompile Nvidia reset the display for Gkrellm might even find something else needs doing. Some apps do depend on the version of the kernel you are using. Maybe I'm not getting what you're not getting ... (smile) I've compiled many hundreds of kernels over the years on lots of linux distros, including Gentoo ~x86 systems, and it's perfectly acceptable to compile as user in /home/user/kernels, and then su to root for modules install and copying/renaming over bzImage to /boot. I generally have anywhere from 4-8 experimental kernels listed in grub.conf. I use to not worry about making the linux symlink in /usr/src point to my currently running kernel every time, but lately I've taken to redoing it each time I compile a new kernel, as I've found more and more that emerging programs look for a kernel symlink in /usr/src, and if it isn't there, emerge fails. I guess it depends on how much updating and compiling you do as too how aggrevating this would become, but since it's no big deal to change it, I'd recommend doing it as a matter of course, so you don't have to stop and do it during an emerge session. Robert Crawford -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.12.8/163 - Release Date: 11/8/2005 -- gentoo-user@gentoo.org mailing list
[gentoo-user] Boot Problems: /dev/sda3 is not a valid root device
Hi all, I just tried to install Gentoo 2005.1 on a computer with one 9GB SCSI. When booting, I get the following error: ~ Block device /dev/sda3 is not a valid root device The root block device is unspecified or not detected ~ I tried other block devices (dev/sda1 etc) to no avail My grub.conf.is as follows: ~ default 0 timeout 30 splashimage=(hd0,0)/grub/splash.xpm.gz title=Woohoo Gentoo root (hd0,0) kernel /kernel-genkernel-x86-2.6.13-gentoo-r5 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3 udev initrd /initramfs-genkernel-x86-2.6.13-gentoo-r5 ~ My fstab is as follows: ~ /dev/sda1/bootext2noauto,noatime1 2 /dev/sda3/ ext3noatime 0 1 /dev/sda2noneswapsw 0 0 /dev/hdc/mnt/cdromiso9660noauto,ro0 0 #/dev/fd0 /mnt/floppyautonoauto 0 0 proc/procprocdefaults0 0 shm/dev/shmtmpfsnodev,nosuid,noexec0 0 ~ Hope someone can help, as it's getting awfully irritating using a CD-ROM to boot the system (which isn't necessary very often). Mike -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Wed, Nov 09, 2005 at 11:59:43AM -0500, Chris Fairles wrote: Changed my symlink to point to 2.6.12-gentoo-r10, compiling ndiswrapper 1.5 is using running kernel 2.6.13 .. make[2]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3' Building modules, stage 2. MODPOST Oops - seems like even kernel code developers are not all of one mind when it comes to what the convention is regarding the /usr/src/linux sym link. I think my preference would be to make the intention more explicit - it a symlink is for use by scripts and makefile then it can be verbose, such as /usr/src/current_buid_kernel which can be accompanied with a separate link to be used a shorthand for the current kernel by human users, such as /usr/src/sys which could be set correctly during boot. (linux would really need to be left as a confusing link for compatability) Regards, DigbyT -- Digby R. S. Tarvin [EMAIL PROTECTED] http://www.digbyt.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Forgot to mention that I had the same problem as Peter with X terminals, from that day on compiles and high demand shell stuff only with tty console. My pc locked up several times when compiling in tty, but with running xorg(xfce). Really strange for me, maybe it is the power supply but i have no idea how to connect PS with difference(never had a lock up without running xorg, but i rarely don't have running xorg) in running software. I will try the memtest86+, maybe it will find something(please no!). But how can i deeply test hd? And maybe some idea to test PS? Next time i'll try to monitor sensors output for PS voltage. -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list
[gentoo-user] Beautified kernel config
G'afternoon, list, silly question for you. Often here or in the forums, a user will post a snippet of his kernel configuration, a la snip Bus options PCCARD * PCCard (PCMCIA/CardBus) [ ] Enable PCCARD debugging * 16-bit PCMCIA support * 32-bit PCMCIA support /snip and so forth. Assuming it hasn't been typed by hand, where does the pretty formatting come from? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda hdparm -Tt /dev/hda Works fine on my pc. -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On 11/9/05, Robert Crawford [EMAIL PROTECTED] wrote: I use to not worry about making the linux symlink in /usr/src point to my currently running kernel every time, but lately I've taken to redoing it each time I compile a new kernel, as I've found more and more that emerging programs look for a kernel symlink in /usr/src, and if it isn't there, emerge fails. No _program_ should be looking at kernel sources. If there is a userspace program that fails to compile without a link to the current kernel sources, you should file a bug report against it. Only external kernel modules should require a link to the kernel sources, and then only for the sources you want to build the module against, not the currently running version. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Beautified kernel config
On 11/9/05, ellotheth rimmwen [EMAIL PROTECTED] wrote: G'afternoon, list, silly question for you. Often here or in the forums, a user will post a snippet of his kernel configuration, a la snip Bus options PCCARD * PCCard (PCMCIA/CardBus) [ ] Enable PCCARD debugging * 16-bit PCMCIA support * 32-bit PCMCIA support /snip and so forth. Assuming it hasn't been typed by hand, where does the pretty formatting come from? Copy-n-paste from 'make menuconfig' helps some, but mostly, I type them by hand. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Boot Problems: /dev/sda3 is not a valid root device
On Wed, 09 Nov 2005 10:00:49 -0800, Michael Shaw wrote: I just tried to install Gentoo 2005.1 on a computer with one 9GB SCSI. When booting, I get the following error: ~ Block device /dev/sda3 is not a valid root device The root block device is unspecified or not detected ~ Do you have the drivers for your SCSI controller compiled into the kernel, not as modules. -- Neil Bothwick There are two standards for anything... One for the U.S. and one for the rest of the world. signature.asc Description: PGP signature
Re: [gentoo-user] Boot Problems: /dev/sda3 is not a valid root device
On 11/9/05, Michael Shaw [EMAIL PROTECTED] wrote: Hi all, I just tried to install Gentoo 2005.1 on a computer with one 9GB SCSI. When booting, I get the following error: ~ Block device /dev/sda3 is not a valid root device The root block device is unspecified or not detected ~ Most likely you need to reconfigure and rebuild your kernel with SCSI disk support and the driver for your SCSI controller compiled into the kernel, not as a module (=Y, not =M). -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Beautified kernel config
On 11/9/05, Richard Fish [EMAIL PROTECTED] wrote: On 11/9/05, ellotheth rimmwen [EMAIL PROTECTED] wrote: G'afternoon, list, silly question for you. Often here or in the forums, a user will post a snippet of his kernel configuration, a la snip Bus options PCCARD * PCCard (PCMCIA/CardBus) [ ] Enable PCCARD debugging * 16-bit PCMCIA support * 32-bit PCMCIA support /snip and so forth. Assuming it hasn't been typed by hand, where does the pretty formatting come from? Copy-n-paste from 'make menuconfig' helps some, but mostly, I type them by hand. -Richard Cut-n-paste and then a bit of hand editing for me. - Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Boot Problems: /dev/sda3 is not a valid root device
Neil Bothwick wrote: On Wed, 09 Nov 2005 10:00:49 -0800, Michael Shaw wrote: I just tried to install Gentoo 2005.1 on a computer with one 9GB SCSI. When booting, I get the following error: ~ Block device /dev/sda3 is not a valid root device The root block device is unspecified or not detected ~ Do you have the drivers for your SCSI controller compiled into the kernel, not as modules. Not to the best of my knowledge. I guess that would do it. I just assumed they would be there, in the genkernel. I'll give it a whirl and see what I can find. Thanks -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
051109 Holly Bostick wrote: Philip Webb schreef: I have 2.6.14 working ok (still ~x86), but am keeping 2.6.12 2.6.9 around in case something unexpected happens with 2.6.14 . However, if I want to use 2.6.12 , I will have to recompile Nvidia. Why? Yes (pink face): as I now realise after reading eg Willie Wong's comment, external modules are stored in /lib/modules/kernel-version/ remain there for the appropriate kernel to use (unless you delete them). I could not get Nvidia to work with 2.6.9 (problem with Nvidia version), so 12 - 14 is the 1st time I've updated Nvidia for a new kernel version. reset the display for Gkrellm There is a bug in Gkrellm (Gentoo # 104805): the temperature + fan display disappears whenever you change the kernel you have to R-click configure it to display again. Maybe I'm not getting what you're not getting ... (smile) Now I am ... (smile) -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Beautified kernel config
Mark Knecht schreef: On 11/9/05, Richard Fish [EMAIL PROTECTED] wrote: On 11/9/05, ellotheth rimmwen [EMAIL PROTECTED] wrote: G'afternoon, list, silly question for you. Often here or in the forums, a user will post a snippet of his kernel configuration, a la snip Bus options PCCARD * PCCard (PCMCIA/CardBus) [ ] Enable PCCARD debugging * 16-bit PCMCIA support * 32-bit PCMCIA support /snip and so forth. Assuming it hasn't been typed by hand, where does the pretty formatting come from? Copy-n-paste from 'make menuconfig' helps some, but mostly, I type them by hand. -Richard Cut-n-paste and then a bit of hand editing for me. - Mark Ditto, usually select-copy and middle-click-paste from make menuconfig to the compose window, and then hand-edit. Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Beautified kernel config
On 11/9/05, Mark Knecht [EMAIL PROTECTED] wrote: On 11/9/05, Richard Fish [EMAIL PROTECTED] wrote: Copy-n-paste from 'make menuconfig' helps some, but mostly, I type them by hand. Cut-n-paste and then a bit of hand editing for me. Interesting, thanks. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Boot Problems: /dev/sda3 is not a valid root device
Richard Fish wrote: On 11/9/05, Michael Shaw [EMAIL PROTECTED] wrote: Hi all, I just tried to install Gentoo 2005.1 on a computer with one 9GB SCSI. When booting, I get the following error: ~ Block device /dev/sda3 is not a valid root device The root block device is unspecified or not detected ~ Most likely you need to reconfigure and rebuild your kernel with SCSI disk support and the driver for your SCSI controller compiled into the kernel, not as a module (=Y, not =M). -Richard Thanks. I'll trt it. Have to wait for an opportunity to reboot the machine to see how well it works Mike -- gentoo-user@gentoo.org mailing list
[gentoo-user] vlc dies on GL
Hello, upon emerging several different video based applications: vlc, mythtv etc, I run into a common problem now: for vlc heres the error message that is essentially identical to other packages that are complaining: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lGL I know 'GL' is not a use flag, but I cannot seem to find what i need to install to fix this problem. Or the package that contains GL. I run KDE 3.4. Ideas? James -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Tue, 08 Nov 2005 19:40:59 +0200 Rumen Yotov wrote: Hi, There seems to exist at least two current kernels - one is the kernel to which /usr/src/linux points, this one is used by most (all ?) kernel-module programs (i have 3 of them: nvidia, arpstar, loop-aes; had also alsa-driver). When you compile/recompile any one of them they use the kernel sources pointed by /usr/src/linux. Patch kernel sources too (e.g. l7-filter). The second kernel is your running kernel (available by uname -r) this one is the one actually running at any givenn time. Don't have any examples of something using this one. Anybody here? HTH.Rumen What i think you mean is that there are two ways of referencing what may be the correct kernel to compile against :-). However In addition to: /usr/src/linux ; (method 1) and /usr/src/linux-`uname -r` (method 2) There are many packages out there that find the linux sources by looking for: /lib/modules/`uname -r`/build - (method 3) which is a symlink to the sources those modules were built from. Not all ebuilds use method 1 to find the kernel version. cd /usr/portage grep uname -r * -r reveals any number of ebuilds that refer to uname -r as a way of determining the kernel version. Also many packages use either method 2 or method 3 in their internal config script or makefile. -- Nick Rout [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vlc dies on GL
On Thursday 10 Nov 2005 1:22 am, James wrote: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ ld: cannot find -lGL I know 'GL' is not a use flag, but I cannot seem to find what i need to install to fix this problem. Or the package that contains GL. I run KDE 3.4. You are having problems with OpenGL. Did you compile xorg with opengl support? What is the output of these two commands? emerge -pv xorg-x11 opengl-update --get-implementation Abhay -- gentoo-user@gentoo.org mailing list
[gentoo-user] DVD:rip problem
Hello, I'm using DVD:rip on a Mepis/Debian installation with no problem. I don't remeber exactly the versions of DVD:rip and transcode, but it just plain works. On my new Gentoo install DVD:rip starts OK, but then all goes wrong: ripping fails with message could not read this frame, then transcode simply won't work with any codec (but this may just mean it can't handle what's been ripped). Ad mentioned, ripping and encoding works with Mepis (same DVD, same drives, same hardware). Any idea what could be wrong? Thierry -- The problem with the world is stupidity. Not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself? Frank Zappa -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Peper wrote: (never had a lock up without running xorg, but i rarely don't have running xorg) Sounds like a problem with the video driver then -- painting a graphical screen takes quite some resources and DMA access, which can lockup the bus... So switch back to a kernel of several weeks ago, and see if the problem goes away. Benno -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: vlc dies on GL
abhay abhay.ilugd at gmail.com writes: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ ld: cannot find -lGL I know 'GL' is not a use flag, but I cannot seem to find what i need to install to fix this problem. Or the package that contains GL. I run KDE 3.4. You are having problems with OpenGL. Did you compile xorg with opengl support? I tried to install mythtv and it failed because of -lGL. I then tried to update vlc, and it failed with the error message above. I then discover that I had 'v4l' in my make.conf file, so I change it to 'v4l2' and ran emerge -uD --newuse world' which again dies on the missing GL. I even tried USE=opengl emerge mythtv which failed at the same point. What is the output of these two commands? emerge -pv xorg-x11 [ebuild R ] x11-base/xorg-x11-6.8.2-r4 -3dfx +3dnow +bitmap-fonts -cjk -debug -dlloader -dmx +doc -font-server -insecure-drivers +ipv6 -minimal +mmx +nls -nocxx +opengl +pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv opengl-update --get-implementation ati I guess I need to rebuild xorg-x11, and put opengl in make.conf? Here are the latest USE flags in make.conf: USE=-gtk -gnome java qt kde dvd cdr sse mmx 3dnow alsa apache2 calendar cups divx4linux encode ethereal aac jack perl php mysql postgres spell ssl tiff xv ffmpeg mplayer v4l2 dvdr jpeg lm_sensors quicktime xmms xvid mozilla mpeg scanner doc xine theora nsplugin Note vlc has been installed for a while. It's the rebuild, now that I changed v4l to v4l2 that causing it to die. media-video/vlc Latest version available: 0.8.1-r1 Latest version installed: 0.8.1-r1 emerge -uDp world --newuse These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild R ] dev-java/blackdown-jre-1.4.2.02 [ebuild R ] dev-java/blackdown-jdk-1.4.2.02 [ebuild R ] media-video/vlc-0.8.1-r1 [ebuild R ] media-video/mjpegtools-1.6.2-r4 [ebuild R ] media-video/transcode-0.6.14-r2 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] mainactor - which build is likely to work best?
On November 6, 2005 10:07 pm Nick Rout was like: The suse build works fine here. Thanks Nick. SuSE was the one I decided to try out first and it has been running without any problem for me too. I'm still looking for something that will do quite a bit more than this, so I'm trying out various windows apps under wine. I'll post if I get something to work reasonably well. Robert -- Robert Persson Don't use nuclear weapons to troubleshoot faults. (US Air Force Instruction 91-111, 1 Oct 1997) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] DVD:rip problem
On Wednesday 09 November 2005 22:04, Thierry de Coulon wrote: On my new Gentoo install DVD:rip starts OK, but then all goes wrong: ripping fails with message could not read this frame, then transcode simply won't work with any codec (but this may just mean it can't handle what's been ripped). Check the logs, and run the last command it did manually (the whole lot, mkdir blahblahblah cd blahblahblah dr_exec blah... etc), and tell us if you get a glibc error. -- Mike Williams -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] mainactor - which build is likely to work best?
On Wed, 9 Nov 2005 13:43:35 -0800 Robert Persson wrote: On November 6, 2005 10:07 pm Nick Rout was like: The suse build works fine here. Thanks Nick. SuSE was the one I decided to try out first and it has been running without any problem for me too. I'm still looking for something that will do quite a bit more than this, so I'm trying out various windows apps under wine. I'll post if I get something to work reasonably well. what are you looking to do that main actor cannot do? -- gentoo-user@gentoo.org mailing list
[gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
Hi - can anyone tell from the attached why media-video/avifile-0.7.41.20041001-r1 failed? I'm a bit stuck at the moment. I'm trying to emerge kino and this is one of the required packages. I'm not good enough to diagnose the problem so any help would be great. -- Thanks, Richard I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c flvdec.c i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c flic.c -fPIC -DPIC -o .libs/flic.o i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c flvdec.c -fPIC -DPIC -o .libs/flvdec.o /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c flvenc.c flvdec.c: In function `flv_read_packet': flvdec.c:63: warning: `st' might be used uninitialized in this function /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c framehook.c i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c flvenc.c -fPIC -DPIC -o .libs/flvenc.o /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c gif.c i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c framehook.c -fPIC -DPIC -o .libs/framehook.o /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c gifdec.c i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c gif.c -fPIC -DPIC -o .libs/gif.o i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c gifdec.c -fPIC -DPIC -o .libs/gifdec.o /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c http.c /bin/sh ../../libtool --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c idcin.c i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c http.c -fPIC -DPIC -o .libs/http.o i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -DHAVE_AV_CONFIG_H -I./../libavcodec -I./.. -Wall -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -pipe -c idcin.c -fPIC -DPIC -o
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
I am not sure what the problem is, but you are probably better off without avifile. It is about to be removed from portage: see: http://marc.theaimsgroup.com/?l=gentoo-devm=112940871726601w=2 http://bugs.gentoo.org/show_bug.cgi?id=111336 I am guessing (based on your email about kino yesterday) that avifile is being dragged in by the +avi flag in mjpegtools (which is being dragged in by kino). I therefore suggest that you try: echo media-video/mjpegtools -avi /etc/portage/packages.use and then try again, avifile should be left out now On Thu, 10 Nov 2005 09:39:01 +1000 Richard Watson wrote: Hi - can anyone tell from the attached why media-video/avifile-0.7.41.20041001-r1 failed? I'm a bit stuck at the moment. I'm trying to emerge kino and this is one of the required packages. I'm not good enough to diagnose the problem so any help would be great. -- Thanks, Richard -- Nick Rout [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
New debug info: when locked up my pc responses to ping and ssh connection(I get only login respone, i cannot actually log in). Moreover ssh logs sshd: fatal: Timeout before authentication for IP. I am not sure what to think about it... -- Best Regards, Peper -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] System Locking Up
Peper wrote: New debug info: when locked up my pc responses to ping and ssh connection(I get only login respone, i cannot actually log in). Moreover ssh logs sshd: fatal: Timeout before authentication for IP. I am not sure what to think about it... I had a similar thing happen with mine. Turned out it was a dying HDD. I assumed the behaviour was caused by things like sshd trying to write to the log about a connection attempt, but it would block because it couldn't write to the disk. Same for logging into to a console. But network traffic was still passing through the machine, and it could still be pinged. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
On 11/9/05, Richard Watson [EMAIL PROTECTED] wrote: Hi - can anyone tell from the attached why media-video/avifile-0.7.41.20041001-r1 failed? I'm a bit stuck at the moment. I'm trying to emerge kino and this is one of the required packages. I'm not good enough to diagnose the problem so any help would snip -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE You didn't post the output of emerge --info, but it looks like you may have -mmx, -msse2, and -mfpmath in your CFLAGS. If so, take them out, and it should compile just fine. -Richard -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: vlc dies on GL
abhay abhay.ilugd at gmail.com writes: On Thursday 10 Nov 2005 1:22 am, James wrote: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../ ../../../i686-pc-linux-gnu/bin/ ld: cannot find -lGL You are having problems with OpenGL. Did you compile xorg with opengl support? What is the output of these two commands? System 1 where niether vlc or mythtv install: emerge -pv xorg-x11 x11-base/xorg-x11-6.8.2-r4 -3dfx +3dnow +bitmap-fonts -cjk -debug -dlloader -dmx +doc -font-server -insecure-drivers +ipv6 -minimal +mmx +nls -nocxx +opengl +pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv 0 kB opengl-update --get-implementation ati System 2 where mythtv installs but vlc does not: emerge -pv xorg-x11 x11-base/xorg-x11-6.8.2-r4 -3dfx +3dnow +bitmap-fonts -cjk -debug -dlloader -dmx +doc -font-server -insecure-drivers +ipv6 -minimal +mmx +nls -nocxx +opengl +pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv opengl-update --get-implementation xorg-x11 I'm not so sure. I have a second system with the same (USE) flags set, and mythtv installs but vlc fails without the GL error: make[2]: Entering directory`/var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1/mozilla' usr/bin/xpidl -I/usr/share/idl/mozilla \ -I/usr/lib/mozilla/include/idl \ -m header -o vlcintf ./vlcintf.idl make[2]: /usr/bin/xpidl: Command not found make[2]: *** [vlcintf.h] Error 127 make[2]: Leaving directory var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1/mozilla' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1' make: *** [all] Error 2 On system 1 having a problem with 'GL' I ran revdep a month or so ago and I've had minor problems with several packages. Nothing very memorable but the running of revdep is the only significant difference in the 2 systems. On system 2 where mythtv works, vlc fails, it's unable to find: usr/bin/xpidl: Command not found Not sure what the problem really is as vlc fails for 2 different reasons on 2 different systems. Ideas? James -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] DVD:rip problem
Mike Williams wrote: On Wednesday 09 November 2005 22:04, Thierry de Coulon wrote: On my new Gentoo install DVD:rip starts OK, but then all goes wrong: ripping fails with message could not read this frame, then transcode simply won't work with any codec (but this may just mean it can't handle what's been ripped). Could also be a permission problem. What are the permissions on your dvd device (not the mount point, the device!)? m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
On 11/9/05, Richard Watson [EMAIL PROTECTED] wrote: You didn't post the output of emerge --info, but it looks like you may have -mmx, -msse2, and -mfpmath in your CFLAGS. If so, take them out, and it should compile just fine. -Richard Hi Richard, thanks very much for your reply. Yes I do have -mmx -mmse2 and -mfpmath. I'll try your suggestion. As a matter of interest if I change my CFLAG setting how would I apply it to the whole system? Would I use the emerge --newuse option or do I have to bootstrap the system again from scratch. --newuse doesn't take CFLAGS into account. If you really want to rebuild your whole system, the standard way is: emerge -e world But I don't think it is really necessary. These flags can cause build failures, but not really any runtime problems, AFAIK. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
--newuse doesn't take CFLAGS into account. If you really want to rebuild your whole system, the standard way is: emerge -e world But I don't think it is really necessary. These flags can cause build failures, but not really any runtime problems, AFAIK. -Richard Thank you very much for your assistance. -- Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] use of /usr/src/linux symlink
On Thu, 10 Nov 2005 06:37, Robert Crawford wrote: I guess it depends on how much updating and compiling you do as too how aggrevating this would become, but since it's no big deal to change it, I'd recommend doing it as a matter of course, so you don't have to stop and do it during an emerge session. Robert Crawford Exactly. Well said. On that note I don't think it needs to be something for the gentoo init scripts to implement, its more a handy thing for users to implement if they wish to, making their day easier :) -- ...all the good computer designs are bootlegged; the formally planned products, if they are built at all, are dogs! bo-- David E. Lundstrom, A Few Good Men From Univac, MIT Press, 1987 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
Richard Watson schrieb: Hi - can anyone tell from the attached why media-video/avifile-0.7.41.20041001-r1 failed? It fails, because nobody cares anymore about avifile and nobody cares to fix the problem. Thus, it'll be removed from portage pretty soon. But it fails, because it doesn't compile with the new ffmpeg. Search bugzilla. Oh. In your case, it fails because of mmx, it seems. Alexander Skwar -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge avifile -0.7.41.20041001-r1 failed
On Wed, Nov 09, 2005 at 05:47:58PM -0700, Richard Fish wrote On 11/9/05, Richard Watson [EMAIL PROTECTED] wrote: Hi - can anyone tell from the attached why media-video/avifile-0.7.41.20041001-r1 failed? I'm a bit stuck at the moment. I'm trying to emerge kino and this is one of the required packages. I'm not good enough to diagnose the problem so any help would snip -Wno-unused -I../../include -O2 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse,387 -pipe -D_LARGEFILE_SOURCE You didn't post the output of emerge --info, but it looks like you may have -mmx, -msse2, and -mfpmath in your CFLAGS. If so, take them out, and it should compile just fine. I'd try changing -mfpmath=sse,387 to -mfpmath=sse first. The gcc compiler documentation says about -mfpmath=sse,387... Use this option with care, as it is still experimental, because the gcc register allocator does not model separate functional units well. That may be the problem right there. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: vlc dies on GL
On Thursday 10 Nov 2005 2:38 am, James wrote: I tried to install mythtv and it failed because of -lGL. I then tried to update vlc, and it failed with the error message above. When you compiled ati drivers did you enable opengl use flag? you can check by passing this command. emerge -pv ati-drivers Once you re-compile the drivers with opengl, pass the command opengl-update ati If you have already compiled the drivers with OpenGL then pass the above-mentioned update command to make sure that your system uses the driver's opengl. If it still doesn't work then you can pass -opengl use flag for vlc and mythtv to disable opengl. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: vlc dies on GL
On Thursday 10 Nov 2005 7:31 am, James wrote: I'm not so sure. I have a second system with the same (USE) flags set, and mythtv installs but vlc fails without the GL error: make[2]: Entering directory`/var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1/mozilla' usr/bin/xpidl -I/usr/share/idl/mozilla \ -I/usr/lib/mozilla/include/idl \ -m header -o vlcintf ./vlcintf.idl make[2]: /usr/bin/xpidl: Command not found make[2]: *** [vlcintf.h] Error 127 make[2]: Leaving directory var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1/mozilla' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/vlc-0.8.1-r1/work/vlc-0.8.1' make: *** [all] Error 2 Do you use vlc in mozilla to play videos? If you don't, then pass -mozilla use flag for vlc on this system. Abhay -- gentoo-user@gentoo.org mailing list
